Sample business scenario

In your organization, production orders have been created and released by an LN user.

Your organization has 20 machines that use the tiapi.sfcProductionOrder REST API to perform, among others, these operations for production orders in LN:

• Get Machine Operations

  This operation can be used to read the operations a machine must perform.

• Register machine quantities

  This operation can be used to report the quantities complete for the produced product.

• Register machine hours

  This operation can be used to report the time the machine spent on the produced product.

• Finish Machine Operations

  This operation can be used to indicate that the machine operation is finished.

Each machine performs operations in one company:

• Machines 1- 5 perform operations for production orders in company 0100.
• Machines 6- 12 perform operations for production orders in company 0200.
• Machines 13- 20 perform operations for production orders in company 0300.

Al machines are programmed to connect to LN using the login credentials of the LN Service account: svc_ln. This is a standard service account user that is delivered with LN.

You want to perform traceability and accountability for the different machines: in the LN history you want to see which operations were performed by machine 1, by machine 2, by machine 3, etc.

By default, the requests sent by a machine do not contain any identification of that machine. Therefore, in LN and in the log data, you can only see that the requests were sent by the service account user. You cannot distinguish which request was sent by which machine. All requests sent by the machines are logged as being sent by the LN user of the service user (svc_ln).

To ensure that you can perform traceability and accountability for the different machines, you must set up identity switching.