1 June 2007
Integration for a competitive organization
Here is a use case example for the integrated application. Track the flow on the diagrams.
When enterprise applications receive a customer order, an order management activity triggers a request to a production planning activity. The site and area applications ascertain from production operations and maintenance tracking activities on the likelihood of delivering the
order on time based on the available capability and cap-acity of the production resources. The actors involved in the scenario are here in a unified modeling language rendering.
Now consider: A customer order for delivery at some time passes between Levels 4 and 3 as production definitions and production re-quests information exchanges.
To obtain a delivery date, the capability assessment and order fulfillment application involving the production resource management and the maintenance tracking activities evaluates the likelihood of fulfilling the order based upon the expected availability of the required types of resources.
Both the production data collection and the maintenance data collection activities obtain status and forecasting data from the Level 2 asset prognostics and health assessment application and share these with the production and maintenance planning and scheduling applications.
Here, the Level 3 applications of production operations planning and scheduling, capability assessment and order fulfillment, and maintenance planning and scheduling can operate in terms of the detailed generic activity model.
The work center and unit activities at Levels 2, 1, and 0 can also model following the definitions provided by ISO 13374 as we can see here.
The signals received from a sensor are for diagnostics, asset condition monitoring, prognostics, and asset health assessment.
The formats for the signals acquired, I/O conditioning, computed data measurements, and information about an asset's remaining useful life come from the interfaces selected to handle the required performance of the applications.
The signal, data, and information flows provide a fresh status of the production assets on the plant floor.
The response from the manufacturing system is a "capability assessment" that indicates to the business planning system the production system's ability to respond to the production request.
By using the information descriptions and semantics of ISO 13374, the assessment of the capability of the assets required for a particular production scenario is possible.
These information exchanges can take place if the resources involved implement the required interoperability interfaces. These interfaces and their specific configurations to support the application scenario are the interoperability profiles.
Another activity interaction diagram can show the information exchanges among the Level 2 applications, as well as, the exchanges between the applications at different levels.
When the information exchanges among all the activities have been accounted for, every resource at each level in the application hierarchy will have an associated set of interfaces.
These interfaces provide not only the communications connectivity (e.g. EtherNet/IP, Foundation Fieldbus) but also the common data syntax (e.g. CIP, XML, OPC) and semantics (e.g. MIMOSA OSA-EAI, ebXML) required by the applications.
The interoperability among the various applications at the different functional and physical levels of an organization lead to a more effective, responsive, integrated, and competitive enterprise.
The integration of diagnostics, maintenance, capability assessment, production, and control applications can be described using the combined aspects of ISO 18435, IEC 62264, ISO 15745, and ISO 13374 standards.
The interoperability interfaces are delineated and defined in ISO 18435 using the application integration framework of ISO 15745, the levels and activity models of IEC 62264, and the diagnostics and condition-monitoring framework provided by ISO 13374.
ISO 18435 also provides a scheme to define the activities, resources, and information exchange interfaces to aid in specifying interoperability profiles based on the ISO 15745 templates.
Nicholas Sheble (firstname.lastname@example.org) edits the Channel Talk department. The sources for this content are The Advanced Technology Group and Rockwell Automation. Read more about the ISO 18435 project at http://www.isa.org/intech/jan07/integration.
ISA-95 is three standards in a series that define the interfaces between enterprise activities and control activities. Enterprise-Control System Integration, Part 1: Models and Terminology provides standard terminology and a consistent set of concepts and models for integrating control systems with enterprise systems that will improve communications between all parties involved.
ISO 13374 establishes general guidelines for software specifications related to data processing, communication, and presentation of machine condition monitoring and diagnostic information.
ISO 18435 standard is under development. It is Industrial automation systems and integration-Diagnostics, capability assessment, and maintenance applications integration-Part 1: Overview and general requirements.
UML: In software engineering, Unified Modeling Language is a non-proprietary, third-generation modeling and specification language. However, the use of UML is not restricted to software modeling. It works for modeling hardware (engineering systems) and for business process modeling and organizational structure modeling.
ISO 15745 defines an application integration framework-a set of elements and rules for describing integration models and application interoperability profiles.
This international standard is applicable to industrial automation applications such as discrete manufacturing, process automation, electronics assembly, semiconductor fabrication, and wide-area material handling.
It may also be applicable to other automation and control applications such as utility automation, agriculture, off-road vehicles, medical and laboratory automation, and public transport systems.
ISO 15745-1:2003 defines the generic elements and rules for describing integration models and application interoperability profiles, together with their component profiles-process profiles, information exchange profiles, and resource profiles.
Parts 2, 3 and 4 of ISO 15745 define the technology specific elements and rules for describing both communication network profiles and the communication related aspects of device profiles based upon particular fieldbus technologies; these parts can be used in conjunction with this part to form an application integration framework for a specific fieldbus technology.