This collection enables users to take advantage of a sophisticated table structure which organizes work instruction content (tasks) into step-by-step instructions (procedures) which are called upon in a sequence of different stations (routings). Users define the content they’d like to display and can assign it to any number of products whose manufacturing process can then be planned and tracked as jobs/work orders.
This is for you if you are looking to:
- Convert hundreds or thousands of work instructions to digital format
- Scale work instructions across your entire organization
- Want to reduce redundancies (i.e reuse tasks across multiple different SOPs)
If you are looking for something quick and simple, check out the Static Work Instruction Application
The Dynamic Work Instruction Collection contains 2 applications:
The Work Instruction Builder is used to define the content for all work instructions. It allows to create tasks, procedures and routings and link them together. (A procedure will contain one or many tasks and a routing will contain one or main procedures.) Using this app, you build the data backbone of your DWI bundle.
The Operator Terminal is central interface to your operators on the shop floor. After scanning a jobID, it will guide the operator through the steps you have defined in the configurator for each product based on the routing (and therefore the linked procedures and tasks).
Following along in this tutorial to learn how to install and set up your work instructions
How do I assign one of my products or routings to a Job?
The Job Module enables you to create a job that is linked to a particular product. Alternatively, you can always add an entry into the *Jobs table directly. Make sure teh ProductID field and/or the RoutingID field match the configuration you have set up in the Work Instruction Builder.
How do I connect this to my ERP?
The Tulip Tables *Jobs, *Products, *Routings, & *Tasks should be representative of tables/fields that you would pull from an ERP. You can easily swap out the triggers that call to the Table Tables with your ERP once you have the necessary connector functions established.
How should I name my Procedures, Routings, Tasks, etc?
All of these do require a unique ID which is immutable. We recommend defining a naming scheme youd to follow before setting up all of your work instructions. Using a scalable nomenclature will avoid headaches in the long run.
Can I do a mass import?
Yes. . Then, export the *Tasks, *Procedures, *Routings, and *Products tables. Then populate your data and import it back in.
If you are not sure which data is necessary, before exporting we recommend running the Work Instruction Builder application to set up a product and see which fields were populated.
Can I connect my work instructions to collect data from IoT connected devices?
Yes, on the Task Builder step there is a field for 'Task Type'. Depending on the task type, you can add logic into your Viewer step to ensure data entry. For example, you can add a trigger that checks if the Task Type ='IoT' then don't advance to next step unless input field is checked.
How do I add my own fields?
If your task or product etc has different fields than we have outlined, you can modify the *Tasks, *Procedures, *Routings, and *Products tables to have the accurate fields. Then, update the steps to call for the particular fields.
I don't need Routings, I just need Product >Procedures>Tasks is this possible?
Yes, using the Products table, you can exchange the 'Routing ID' field to be the "Procedure ID field'. This will require some logic updates to pull the Procedure filed instead of the Routing, but the flexibility is there - if you have questions on how to do this please reach out to us.