Constantin
Beginner
Where can machine data collection and plant data collection, as known from an MES, be found in Bridge API?
Where can machine data collection and plant data collection, as known from an MES, be found in Bridge API?
Share
In an MES, the term “machine data collection” generally refers to the operating states and quantities recorded at the individual workplaces (machines). These can be found in the resources
workplaces/{id}/recordedOperatingStates
respectively
workplaces/{id}/recordedOutputQuantities
A summary is provided by the resources:
workplaces/{id}/operatingStateSummary
respectively
workplaces/{id}/quantitySummary
Concerning the process data collected on the machines, please refer to the link below.
In an ERP system, plant data collection means the projection of the recorded machine data onto the individual operations of a production order. These can be found in the resources
operations/{id}/recordedOperatingStates
respectively
operations/{id}/recordedOutputQuantities
A summary is provided by the resources:
operations/{id}/operatingStateSummary
respectively
operations/{id}/quantitySummary
Why are there not simply the two interfaces machine data collection and order data collection?
Alexander
An additional basic explanation:
FORCE Bridge API was designed as a digital image of production facilities based on the semantics commonly used in production. Bridge API strictly avoids confronting the user with unnecessary technical buzzwords or marketing terms. Instead, entities from the production domain (such as production orders, operations, workplaces, tools or staff members) are mapped directly as the primary resources of the application programming interface. Primary resources contain the header data required to identify the resource and the status of the resource. All other details can be found in the sub-resources, whereby most sub-resources can be flexibly and dynamically embedded in the primary resources. Example: GET operations?embed=specification&embed=scheduledDates.
As an IoT platform for production, FORCAM FORCE Bridge stands in contrast to an MES, for which the providers have defined a fixed scope of functions. Instead, Forcam Force Bridge is intended to enable all production companies to make unrestricted use of today’s and tomorrow’s top applications in the field of Smart Manufacturing. In order to enable such an unlimited application spectrum, an API must not explicitly predefine individual application cases.
Patrick
You will find this in
workplaces/{id}/recordedOperationPhases
workplaces/{id}/recordedOutputQuantities
workplaces/{id}/recordedOperatingStates
and in
operations/{id}/recordedOperationPhases
operations/{id}/recordedOutputQuantities
workplaces/{id}/recordedOperatingStates