Related
Recommended
ernstamort

Looking at the OSIsoft PI development in recent years it becomes very apparent that PI is now much more that a process database or historian. With the addition of the Asset Framework (AF), Event Framework (EF) and PI Analysis PI now offers powerful tool to contextualize data based on their physical and time structure. These are Meta data mappings that have opened the door for context specific visualization and analysis. The concepts of templates has made it very simple to create large and complex equipment models and perform calculations on any granular level.

The addition of AF and EF also meant that PI now contains data structures that are typically found in a Manufacturing System (MES). This mainly applies to the equipment and batch model, but due to the flexibility of AF and EF also other MES function could exist on the PI system.

There are different options available to combine PI and MES and the primary focus should be to maximize the benefit of both systems. This requires to standardize the configuration in order for both systems to effectively communicate. It is also unavoidable to have redundancies between the MES and PI system and this requires to synchronize a fair amount of data (time series and Meta data).

Over the next couple of week I will describe some best practices around the PI-MES integration and will show some examples.

Parents

  • The PI system (or any other historian) is already part of MES solutions as a data source. The MES system will consolidate the data from different sources and communicate to ERP and control layer (and LIMS and Maintenance) through connectors.

     

    There are already overlaps between the MES and PI system, mainly in the equipment (AF) and batch (EF) model. A good MES architecture should include PI as a data source (PI Server), analytic engine, and visualization tool but also synchronize the two data models. So functionality should be split into real time, relational and transactional data to maximize the benefit of all systems.

     

    I started to describe the system and will also provide some examples:

    PI and MES: Architecture I

    PI and MES: Equipment Model

Comment

  • The PI system (or any other historian) is already part of MES solutions as a data source. The MES system will consolidate the data from different sources and communicate to ERP and control layer (and LIMS and Maintenance) through connectors.

     

    There are already overlaps between the MES and PI system, mainly in the equipment (AF) and batch (EF) model. A good MES architecture should include PI as a data source (PI Server), analytic engine, and visualization tool but also synchronize the two data models. So functionality should be split into real time, relational and transactional data to maximize the benefit of all systems.

     

    I started to describe the system and will also provide some examples:

    PI and MES: Architecture I

    PI and MES: Equipment Model

Children
No Data