The system should be able to generate an invoice that will be paid by the student for material use and machine time. Currently there are NO plans to integrate a payment system, as the lab utilizes RazorBuck$ and there is a separate kiosk that is used to charge student accounts.
However, on the invoice for a job there needs to be a way to generate a PDF like the following:
that would have line items for each item printed that could then be emailed to the student or printed for records.
When an object file comes in (STL) it is then put into a slicer (CURA) that will divide the solid object up into layers and generate machine paths in an output file (GCODE). Within this GCODE file there are lines that include the estimated print time as well as the number of grams of plastic that the print will use.
The process of generating the invoices could include manual override from staff in the ticket item, and can also include a search to autofill the fields based on the GCODE file for the job.
This generation should probably happen on the Node side, maybe have a button where a user can request an invoice, the node route is hit, pulls the job info from the DB, and then generates and gives a download link for the PDF.
The system should be able to generate an invoice that will be paid by the student for material use and machine time. Currently there are NO plans to integrate a payment system, as the lab utilizes RazorBuck$ and there is a separate kiosk that is used to charge student accounts.
However, on the invoice for a job there needs to be a way to generate a PDF like the following:
that would have line items for each item printed that could then be emailed to the student or printed for records. When an object file comes in (STL) it is then put into a slicer (CURA) that will divide the solid object up into layers and generate machine paths in an output file (GCODE). Within this GCODE file there are lines that include the estimated print time as well as the number of grams of plastic that the print will use. The process of generating the invoices could include manual override from staff in the ticket item, and can also include a search to autofill the fields based on the GCODE file for the job.
This generation should probably happen on the Node side, maybe have a button where a user can request an invoice, the node route is hit, pulls the job info from the DB, and then generates and gives a download link for the PDF.