Maintain an Asset Hierarchy Using the Plant Information Catalog in SAP MII

  • by Rohit Negi, Senior Consultant, Cibersites India
  • June 9, 2015
Learn how to create, maintain, and consume a Plant Information Catalog (PIC) hierarchy in SAP Manufacturing Integration and Intelligence (SAP MII). Discover how to integrate shop floor data and enterprise data from SAP ERP in the PIC.
Learning Objectives

Reading this article, you will learn how to:

  • Create and maintain a Plant Information Catalog (PIC) hierarchy
  • Use various features of the PIC to create the hierarchy and store the information in the hierarchy
  • Use change management in the PIC
  • Consume information in the PIC
Key Concept
Plant Information Catalog (PIC) is a framework provided by SAP Manufacturing Integration and Intelligence (SAP MII) version 14.0 and above that enables organizations to create and maintain their asset hierarchies in SAP MII. The PIC is a hierarchical or logical representation of various assets in a plant or the entire enterprise. This hierarchy is integrated with real-time shop floor data and the business assets maintained in SAP ERP production planning (PP) and plant maintenance (PM) modules. The PIC provides not only the functionality to create a logical asset hierarchy of the shop floor assets but also the business context to the shop floor assets by integration with the PP and PM module hierarchies of SAP ERP.

All manufacturing organizations have a lot of data in their shop floor systems. This data is stored in the shop floor systems without any relevant business context. Imagine that you are using a historian for storing a lot of data points. When you see the data in the historian, can you figure out for whom this data is relevant? Can you tell the work center or functional location for which this data is relevant? The answer is no if you don’t have a place or mechanism in which you can maintain this relationship. The Plant Information Catalog (PIC) framework in SAP Manufacturing Integration and Intelligence (SAP MII) helps you maintain this relationship.

On a plant’s shop floor, many systems store or capture data for various data points, such as temperature or pressure for various types of equipment. This data is usually stored as a flat structure and therefore has no relationship with other data or any business context associated with it. For example, consider a scenario in which you have temperature readings for a boiler, but you do not know to which work center in the ERP system this boiler is mapped. The data is also usually stored with strict technical naming formats, making it very difficult to search or fetch this data if you don’t know the exact technical name of the data point in the shop floor system.

The pain point here is that you have data available, but this data is named in a very technical manner, making it difficult to understand and search for it. This data does not have a business sense or context associated with it, thus making it difficult for you to analyze it or use it for analytics.

The SAP MII PIC is helpful in this situation because it provides the framework for creating a hierarchical, plant-specific catalog of data points or tags from different shop floor systems. The PIC also provides a business context to this hierarchy from the SAP ERP system. Therefore, you can group shop floor assets logically and also by business rules defined in the ERP system. Additionally, you can have business-friendly naming conventions for the objects and data points so that it makes it easier for you and also for the business user to understand the hierarchy.

In this article, I take you through all the steps for creating an SAP MII PIC hierarchy and consuming it.

Rohit Negi

Rohit Negi is a senior consultant at Cibersites India with around seven years of experience in the IT industry. He is currently providing SAP MII-based solutions to clients. Rohit was a part of the SAP MII Product Development Team at SAP Labs Bangalore and has worked on 12.2, 14.0, and 15.0 releases of SAP MII as a senior developer.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.