Scenario: What should you do when you have 2 separate orders but are producing the same product? To Changeover or Not to Changeover? That is the question.
When you are building one product or product order, finish building the required amount to complete that order, and then begin running a different product, the system recognizes this and initiates a change over. However, In the scenario above, where you are building two separate orders of the same product, the line is not really changing over. So, the system will not detect a change over. These product builds are being integrated via API, and your Production Settings prohibit manually updates at the Operator Portal. So what now?
We have API methods that were designed with scenarios like this in mind: You have 2 eKanban Cards from the same Product, although these eKanban Cards are for different orders. You can use your integration to manually kick off (trigger) a change over. While we have logic in place to not change over if the two products are the same, you can use these methods to initiate a change over:
Look at the API Documentation found under the Support tab from anywhere inside Dispatch. Click on Record Areas. Locate Build Sequences in the list. Click on Build Sequences.
Scroll to the end of the Build Sequences API Documentation and you will see these among the Methods.
URL Example: /api/1.0/buildsequence/method_name/id(optional)/?auth=<API_Key>&...
- start_change_over - /api/1.0/buildsequence/start_change_over/
- finish_change_over - /api/1.0/buildsequence/finish_change_over/
Here is a Tips and Trick Video on Capturing Changeover Time for SMED.