Articles in this section

See more

Production API Integration: Working with Product Orders

  • Updated
Follow

Many production lines can be tooled to build more than one product. The L2L Operator Portal User Interface (UI) allows you to easily change over to a new product, submit production actuals and scrap, put an order on hold, and complete an order. You can use the API to change over to a new product as well. This article will explain the different API operations to execute Product Orders.

Starting a Changeover

Objective: Start the next order in a line's eKanban Queue that matches the parameters passed in.
Interval: Submit once at the beginning of a Product Order.
Process Outline:

  1. Change over to the next Build Sequence (Product Order) 
    POST https://[customer].leading2lean.com/api/1.0/buildsequence/start_change_over/?auth=[api key]
    1. POST parameters: site=[site id]&linecode=[line code]&productcode=[product code]
    2. Alternate POST parameters: site=[site id]&linecode=[line code]
    3. Alternate POST parameters: site=[site id]&linecode=[line code]&id=[build sequence id]
    4. See the official API documentation for information on using Line External ID and Build Sequence External ID instead of Line Code and Build Sequence ID

Result: This is just like clicking the "Start Changeover" button in the Operator Portal. It will:

  • Split the current Pitch
  • Start the next order in the eKanban Queue
  • Create a new Changeover Dispatch if the Production "Changeover Dispatch Type" setting is set
  • Set the Pitch Demand if the Line setting "Enable the Setting of Production Demand on Changeover" is enabled

Finishing a Changeover

Objective: Complete a Changeover for a Build Sequence (Product Order)
Interval: Submit when a changeover is complete. Can be skipped if the Planned Changeover Duration on the Build Sequence is 0.
Process Outline:

  1. Complete an open changeover 
    POST https://[customer].leading2lean.com/api/1.0/buildsequence/finish_change_over/?auth=[api key]
    1. See POST parameters and alternate POST parameters for the Starting a Changeover section above

Result: This is just like clicking the "Finish Changeover" button in the Operator Portal. It will complete any open Changeover Dispatches.

Put an Order on Hold

Objective: Place an order on hold to be completed at a later date
Interval: On demand
Process Outline:

  1. Place a Build Sequence (Product Order) on hold 
    POST https://[customer].leading2lean.com/api/1.0/buildsequence/put_order_on_hold/?auth=[api key]
    1. See POST parameters and alternate POST parameters for the Starting a Changeover section above

Complete an Order

Objective: Complete a Build Sequence (Product Order)
Interval: Once per order, when the Build Sequence is complete
Process Outline:

  1. Complete a Build Sequence 
    POST https://[customer].leading2lean.com/api/1.0/buildsequence/complete_order/?auth=[api key]
    1. See POST parameters and alternate POST parameters for the Starting a Changeover section above

Get Current Build Sequence Running on a Line

Objective: Get the current Build Sequence that is running on a Line. This can be used in conjunction with the other buildsequence methods in a more complex integration application.
Interval: On demand
Process Outline:

  1. Retrieve the current open Build Sequence on a Line: 
    GET https://[customer].leading2lean.com/api/1.0/buildsequence/get_current_order_on_line/?auth=[api key]&site=[site id]&linecode=[line code]
    1. See the official API documentation for information about using a Line External ID instead of the Line Code.

Related Articles

Related articles

Comments

0 comments

Please sign in to leave a comment.