All Collections
Quality Control & Management
Parameters & Checklists
Quality forms & Checklists - Advanced Example
Quality forms & Checklists - Advanced Example

Get insights on our recommendations for replicating your quality forms in Autodesk Fusion Operations

David Andrade avatar
Written by David Andrade
Updated over a week ago

Checklists are an excellent way to collect additional information about production in Autodesk Fusion Operations. If this is your first time reading about quality forms / checklists, beware that you can learn how checklists can be created and associated with operations here. You can check here how these entities show up on the tablet.

We’ll be using an example so you can better understand how to set checklists in Autodesk Fusion Operations with a dummy scenario. On the image below, we can identify different types of checklist information:

  • (1) The header, in which the checklist code, version, and additional details are specified,

  • (2) Production order details, with important details such as the code, product and the quantity to be produced,

  • (3) Consumption details, where workers input the consumed products and lots,

  • (4) Production specific information, where workers input data for each production step,

  • (5) Final details and observations.

(1) Checklist header

On the header, a few specifications are provided:

  • Document name, which we suggest to translate to the checklist name,

  • Document reference, which we suggest to translate to the checklist code, along with the operation to which the checklist refers to,

  • Date, which can be added either on the checklist text (displayed on the tablet), or concatenated with the checklist code.

(2) Production order details

The six fields on the image above refer to the information entered when creating the production orders and therefore they shouldn't be filled on the checklist.

(3) Consumption details

Below the production order details, you can see the ingredients to be used and their lots. You shouldn’t add consumptions in Autodesk Fusion Operations as checklists, and we advise you to use bills of materials (BoM) and to receive your products with the corresponding lot numbers. Check here how to use our bills of materials feature.

(4) Operation-specific details

Adding information about specific operations is undoubtedly where you’ll get value from checklists. You can check our tips below.

i. Greasing operation has four fields for data introduction:

  • Worker: this information is provided by the worker itself when inserting production on the tablet. Therefore, you shouldn’t include this on the checklist,

  • Tool: there are two ways to model tools. They can be a parameter (and be added to the checklist), or a machine (associated to the operation). We suggest the first option if tool usage and tool production time is not relevant for you. If you’d like to have live details about if the tool is being used, for how long it was used and what it produced, we suggest you to use a machine,

  • Quantity produced: this information is provided by workers on the production checkout. Therefore, you shouldn’t include the quantity produced on the checklist,

  • Date: this information is collected by Autodesk Fusion Operations, since the system collects the check in and check out date and time. Therefore, you shouldn’t include this on the checklist.

ii. Mixing operation has five fields for data introduction:

  • Worker, duration, quantity produced, date: the logic applied at the greasing operation can be applied here as well. Therefore, you shouldn’t include this on the checklist,

  • Signature: this field is a parameter commonly added to checklists, by using the signature parameter type. We advise you, however, to use signatures with moderation as asking them frequently may overwhelm workers. Moreover, if the worker number is introduced during check in, this may be a redundant step. We leave this choice to you.

iii. Baking operation has ten fields for data introduction:

  • Worker, quantity produced, date, start time, and end time shouldn’t be added for the reasons explained above,

  • Oven: shouldn’t be considered a parameter but a machine linked to the ”Baking” operation instead. Information about machine usage is important in most scenarios, and therefore you shouldn’t include this on the checklist,

  • Start temperature: this information should be set as a parameter, associated with a checklist displayed in production check-in. This way workers will be prompted with this field when starting the baking operation,

  • End temperature: likewise the start temperature, this should be a parameter, associated with a checklist displayed in production check-out. This will make workers to be asked about this field when finishing the baking operation,

  • Overcooked / undercooked: these fields refer to production considered waste and therefore they shouldn’t be set as parameters, but as wastes instead. These wastes must be linked to the “Baking” operation. If that’s the case, they’ll be prompted on the production check-out. Please check this article to revise how to add wastes in Autodesk Fusion Operations.

iv. Packing operation has three fields for data introduction:

  • Worker, date, and quantity produced. As explained, these should not be added as parameters. Therefore, “Packing” operation won’t have any checklist associated with it.

v. 2nd baking operation has ten fields for data introduction:

  • Since these fields match the ones for baking, the same principles apply. Therefore, it becomes unnecessary to create a new checklist, and the one used for regular baking can be linked to this operation. Despite not being the case, it is possible to set a checklist for regular production, and another for rework production, as explained in this article.

(6) Final details and observations

Finally, on the bottom, you can see observations, signature and date, and the lot.

  • Observations: this information can either be collected on the last operation, or alternatively written by someone with access to the back office, on the production order notes,

  • Signature: the same principles for “observations” apply to this field,

  • Date: the same principles for “observations” apply to this field,

  • Lot: we advise you not to use lots as parameters since Autodesk Fusion Operations has a specific feature that allows you to have full lot traceability by creating lot numbers during production - either on an automated or manual basis. If you’d like to learn more about how to set lot traceability into your account, please take a look at this article.

Checklist examples for “Baking” operation

As mentioned above, “Baking” operation will have two checklists: one of them shown at check-in, and another one shown at check-out.

Baking check-in checklist

Baking check-out checklist

We hope this article has helped you to understand and create checklists in Autodesk Fusion Operations. If any questions persist, don’t hesitate to reach out to your account manager or to our live support chat!

Need help? Request a Fusion Operations expert to contact you here.

Did this answer your question?