channel talk fodder

7/29/2019 Channel Talk Fodder

1/12

Integration of Production, Diagnostics, Capability Assessment,and Maintenance Information Using ISO 18435

Dan Carnahan, Dukki Chung, Em delaHostria, Charles HooverAdvanced Technology Group, Rockwell Automation, Mayfield Heights, OH 44124

KEYWORDS

ISO 15745, ISO 18435, ISO 13374, IEC/ISO 62264, MIMOSA, integration, framework

ABSTRACT

Emerging standards for the integration of production, diagnostics, and maintenance information (ISO18435) will enable opportunities for improved supply chain collaboration and interoperability ofdiagnostics, control, and maintenance applications to support dynamic production requirements.Changing production requirements and disruptions encountered in the manufacturing process can bemanaged more effectively by using applications that are interoperable. ISO 18435 facilitatesinteroperability by defining a set of integration models and interfaces based on the enterprise-controlsystem integration approach of ISO/IEC 62264 (ISA S95) and emerging standards for condition-basedmonitoring (ISO 13374). The recent publication of ISO 15745, Application Integration Frameworkstandard, provides the basic integration framework for the interoperability of applications.

This paper will describe integration models and interfaces currently defined in ISO 18435 and identifyapplicationsthat can utilize these interfaces to improve interoperability. Benefits of using thesemodels and schemas are improved visibility to manufacturing management not only of the current stateof the manufacturing assets, but also information about the capability of those assets to meet futuremanufacturing requirements. In addition, the use of common descriptions for asset types, locations,status, and capabilities will enable the use of standardized services to locate, assess, and repairmanufacturing disruptions. Another added benefit is the ability to enable new technology insertionwith minimal system design disruption. These models will present different user views for themanufacturing life cycle, as well as different use cases and interaction scenarios depending upon therole of the user (management, operator, maintenance personnel) involved in the system in order to

improve the system reconfiguration management process.

INTRODUCTION

contents

Copyright 2005 by ISA.Presented at ISA EXPO 2005, 25-27 October 2005

McCormick Place Lakeside Center, Chicago, Illinois, www.isa.org
http://../files/main.pdfhttp://../files/main.pdf


2/12

As manufacturers face more competitive demands on their enterprises, production efficiencyimprovements demand more visibility into and better management of manufacturing assets. Improvedawareness about the capability of those assets to meet changing manufacturing requirements is equallyimportant. These changing requirements can be caused by new customer demands, process upsets, orchanges in equipment or process capability. In response to these changing requirements, a

manufacturing system can be responsive and be dynamically reconfigured if it can have currentinformation about the status and capability of the deployed resources. The information can beavailable if the deployed resources provide the required interfaces.

As shown in Figure 1, the production capacity for the manufacturing resources, excluding consumedmaterials, is depicted over time. The variations in height of the current available capacity indicatechanges due to projected asset availability. The current unattainable capacity is due to down time formaintenance, mismatch in production capability and product mix, and other resource related issues.Ideally, the closer one can operate with the current committed capacity to the current availablecapacity, the more efficient the resources are utilized. Better management of the factors impactingunattainable capacity can improve confidence in the available capacity in the future.

FIGURE 1 - PRODUCTION CAPACITY

Different operational and maintenance strategies can be used to ensure that the resources deployed areavailable when needed. In the past, preventive or reactive maintenance strategies were used to ensurethe manufacturing assets were available when needed. More recently, the Condition BasedMaintenance (CBM) approach introduced the ability to diagnose and perform maintenance based uponactual asset conditions and has enabled more responsive maintenance strategies. A goal of theemerging ISO 18435 standards activity is integrating CBM related information along with otheroperating environment information to optimize operating decisions for effective and efficientmanufacturing.

Production Capacity

Time

Unattainable CapacityUnattainable Capacity

Committed CapacityCommitted Capacity

Available CapacityAvailable Capacity

Current Unattainable Capacity

Current Available Capacity

Current Committed Capacity

Production Capacity =Committed +Available +Unattainable

Current Production CapacityCurrent Production Capacity

Copyright 2005 by ISA.

Presented at ISA EXPO 2005, 25-27 October 2005



3/12

The ISO 18435 project in ISO/TC 184/SC 5/WG 7 is intended to describe an integration model toidentify the interfaces needed to improve and facilitate the interoperability of diagnostics, control, andmaintenance applications. This ISO working group is collaborating with the related efforts ofMIMOSA (Machinery Information Management Open System Alliance), ISA S95, and OPC.

Integration BenefitsWhile a typical asset management system can provide the current status of manufacturing assets tosupport a reactive maintenance strategy, better asset utilization can be further achieved by integratinginformation about current capability of these assets and their performance during production. Ideally,the effective and timely maintenance of these assets will enable these to provide the services requiredby the manufacturing production system.

Diagnostics and maintenance applications can use the information about the process, equipment,operator and materials that are already provided by many devices used for production automation andcontrol. With the increasing use of digital signal processing in these devices, the analysis andprocessing of information can be performed closer to the manufacturing process. Information content

originally considered as "noise" in the manufacturing process can now be more effectively analyzed.The information can be presented to other asset health and capability assessment tools via interfacesalready present in the control system, without adding additional sensors.

Other benefits using the ISO 18435 framework that may be gained are as follows:

Facilitate procurement of open, integrated systems by referencing pre-defined diagnostics andmaintenance application interoperability profiles;

Reduce time to assess the suitability of components to develop diagnostics and maintenancesolutions using the framework;

Provide and develop new diagnostics and maintenance products and services using theframework;

In Chapter 2, the approach, purpose, and scope of the ISO 18435 project is briefly described. Chapter 3describes specific extensions to the IEC 62264[1][2] and the ISO 15745[3] standards to be used in theISO 18435 project. In Chapter 4, a use case of this proposed scheme is presented. Conclusions andsome future work are noted in Chapter 5.

2 ISO 18435 - Diagnostic, Capability Assessment, and Maintenance ApplicationsIntegration

2.1 Purpose and approach

ISO 18435 is intended to provide a framework for harmonized use of selected industry andinternational standards in order to enable device suppliers, system integrators, and applicationdesigners to apply common terms and rules for integrating control, diagnostics, prognostics, capabilityassessment, and maintenance applications. By using a common application integration modelingapproach, key interoperability interfaces can be identified and concisely documented in terms ofprofiles. These application interoperability profiles can be used when evaluating whether applicationscan readily integrate with each other.





4/12

The approach involves using (a) an enterprise-control system integration framework defined in IEC62264 that provides information exchange and activity models used to interface control systems tobusiness systems, (b) an application integration framework of ISO 15745 that provides integrationmodels for processes, resources and information exchanges in an application, and (c) an information

model in ISO 13374[4] for asset condition monitoring.

In the ISO 18435 scheme, the ISO 15745 application integration framework is extended to other levelsin application hierarchy, along with the adaptation of the activity models in IEC 62264 to the lowerlevels of the functional hierarchy.

2.2 Scope of the standard

ISO 18435 defines activity reference integration models and their use to integrate diagnostics,capability assessment, and maintenance applications with the applications in production, control, andother manufacturing operations.

An activity reference integration model includes:

activities within the various functional and resource hierarchies in a manufacturing enterprise;

interoperability interfaces used in the integration of these activities;

generic interoperability templates used to denote various types of interfaces and theirconfigurations;

set of interoperability profiles to denote integration across target application domains.

FIGURE 2 - ACTIVITY DOMAIN INTEGRATION DIAGRAM

In Figure 2, an Activity Domain Integration Diagram identifies those activities associated with theapplications of interest. The R-levels in this diagram relate to a resource hierarchy within amanufacturing facility.

Contro l, I/O, DataAcq uis iti on,

Data Historian,Ass et Util izati on,& Panel Displays

Ass et Condit ionMonitoring &Sample/Test/Diagnostic

& Quality Monitoring

Ass etConfiguration,Calibration &

Repair/Replace

Ass et Progno sti cs &Health, Quality, Safety,

& EnvironmentalManagement

MaintenanceExecution &

Tracking

Ass ets (Equ ipm ent / Faci lit ies / Ser iali zed Comp onent s / Senso rsTransducers / Software / Documents), Resources ( Material / Personnel )

Level R Asset

Level R1Work Unit

Level R Work Center

Level R Area

Level R4Enterprise / Sit

SupervisoryControl & Human-Machine Interface

Inter-enterprise activitiesSupply chain Planning and Management,

Logistics Strategy Management

OperationsPlanning &

Scheduling

CapabilityAssessment &

Order Fulfillment

MaintenancePlanning &

Scheduling

ResourceIdentification and Location

Ass etIdentification and Location

Intra-enterprise activitiesBusiness Planning, Order and Production Strategy

and Maintenance Strategy Management





5/12

3 Extensions to IEC 62264 and ISO 15745

3.1 IEC 62264 and ISA S95 : Enterprise-control system integration

A joint working group of the IEC SC65A and the ISO TC184/SC5 technical subcommittees is activelydeveloping a multi-part IEC 62264 standard based on the ISA S95 specifications[7][8][9], that definesan information exchange framework to facilitate the integration of business applications andmanufacturing control applications, within an enterprise.

In Part 3 of the ISA S95 standard, a hierarchy of activity domains within a manufacturing enterprisecan be associated with a hierarchy of applications as shown in Figure 3. At each level in bothhierarchies, a group of functions is performed by a distinct grouping of resources to support a specificoperational level of an enterprise. However, these resource groups form a hierarchy that distinguishesin which physical location and at which organizational level a resource is being used. A combinationof functional and resource hierarchies within an enterprise forms an application hierarchy.

FIGURE 3 - FUNCTIONAL AND RESOURCE HIERARCHIES PER ISA S95

The lower levels 2, 1, 0 comprise the activities of manufacturing operations, automation and control,and physical transformations. The ISA S95 standard defines the information structures and exchangesmanaged by Level 3 activities, applications, processes, resources, and functions, and how theseinformation structures are exchanged with the business applications at Level 4. The ISA S95 standardalso defines a generic activity model for any Level 3 activity (see Figure 4). In ISO 18435, a similargeneric activity model is envisioned for the activities at Levels 2 and below. Each activity at Level 2can be associated with work center resources while each activity at Level 1 involves work units.

ENTERPRISE

SITE

AREA

PROCESS

CELL

PRODUCTION

UNIT

PRODUCTIONLINE

STORAGE

ZONE

UNIT

LOWER LEVEL

RESOURCES IN

CONTINUOUS

OPERATIONS

LOWER LEVEL

RESOURCES IN

BATCH

OPERATIONS

WORK CELL

LOWER LEVELRESOURCES IN

DISCRETEOPERATIONS

STORAGE MODULE

LOWER LEVEL

RESOURCES IN

MATERIAL HANDLING

OPERATIONS

Level 4

Level 3

Levels 2, 1, 0

ENTERPRISE

SITE

AREA

PROCESS

CELL

PRODUCTION

UNIT

PRODUCTIONLINE

STORAGE

ZONE

UNIT

LOWER LEVEL

RESOURCES IN

CONTINUOUS

OPERATIONS

LOWER LEVEL

RESOURCES IN

BATCH

OPERATIONS

WORK CELL


DISCRETEOPERATIONS

STORAGE MODULE

LOWER LEVEL

RESOURCES IN

MATERIAL HANDLING

OPERATIONS

ENTERPRISE

SITE

AREA

ENTERPRISE

SITE

AREA

PROCESS

CELL

PROCESS

CELL

PRODUCTION

UNIT

PRODUCTION

UNIT

PRODUCTIONLINE

PRODUCTIONLINE

STORAGE

ZONE

STORAGE

ZONE

UNITUNIT

LOWER LEVEL

RESOURCES IN

CONTINUOUS

OPERATIONS

LOWER LEVEL

RESOURCES IN

CONTINUOUS

OPERATIONS

LOWER LEVEL

RESOURCES IN

BATCH

OPERATIONS

LOWER LEVEL

RESOURCES IN

BATCH

OPERATIONS

WORK CELLWORK CELL


DISCRETEOPERATIONS


DISCRETEOPERATIONS

STORAGE MODULESTORAGE MODULE

LOWER LEVEL

RESOURCES IN

MATERIAL HANDLING

OPERATIONS

LOWER LEVEL

RESOURCES IN

MATERIAL HANDLING

OPERATIONS

Level 4

Level 3

Levels 2, 1, 0

Level 4

Level 3

Business Planning & LogisticsPlant production planning and scheduling,engineering design, purchasing, customer

order handling, etc.

Manufacturing OperationsManagement

Production, Maintenance, Qualitytesting, Inventory and material flow

management, etc.

Batchcontrol

Continuouscontrol

Discretecontrol




6/12

FIGURE 4 - GENERIC ACTIVITY MODEL PER ANSI/ISA S95

3.2 ISO 15745 : Application integration frameworkIn ISO 15745, an integration model of a manufacturing application is represented as a UML[5]package, as shown in Figure 5.

FIGURE 5 - MANUFACTURING APPLICATION INTEGRATION MODEL

A UML package consists of UML diagrams, classes, and relationships which represent the following:

a set of manufacturing processes that compose a manufacturing application;

a set of manufacturing resources required to conduct these processes,

a set of information exchanges among these resources that manage, control, and enable the

execution of these processes.Manufacturing resources include tools, machines, operators, fuels, devices, and related equipment.These also include raw materials, finished goods, in-process items, piece parts, assemblies, scrap,mixtures, fluid batches, unit loads, and other items used, transported, transformed, or tested in amanufacturing process.

A manufacturing application in Figure 5 represents any of the following:

Manufacturing Application

Manufacturing

Process 1..*

Manufacturing

Information Exchange 1..*

ManufacturingResource

1..*

ManufacturingAutomation Device1..*

Equipment& Machinery 1..*

Manufacturing

Software 0..*

Material &

Manufactured Part

0..*

0..*

CommunicationsNetwork

0..*

ManufacturingPersonnel

IntegrationRequirements

DetailedschedulingDetailedscheduling

Operationsresponse

Operationsrequest

Operationscapability

Operationsdefinitions

Level 2 ActivitiesLevel 2 Activities

Level 4

Level 3

Level 2

ResourcemanagementResource

management

DefinitionmanagementDefinition

management

DispatchingDispatching

TrackingTracking

AnalysisAnalysis

ExecutionExecution

DatacollectionData

collection

Level 4 ActivitiesLevel 4 Activities





7/12

a control application with a control process;

a diagnostics application with a diagnostics process;

a maintenance application with a maintenance process;

Extensions to the ISO 15745 application integration model are shown in Figure 5 with dotted lines, as

optional software resources and an association qualifier that denotes a set of application integrationrequirements. Further, in ISO 18435 the application integration model is used at the other levels in theenterprise application hierarchy.

3.3 Integration model elementsAn application integration model is intended to identify the key interfaces among the resources used inthe processes selected to meet the requirements of a target manufacturing application. A set ofrelationships among the elements of an integration model is shown in Figure 6.

FIGURE 6 - APPLICATION INTEGRATION MODEL ELEMENTS

3.4 Interoperability of resourcesTwo or more resources can interoperate if these can transfer or exchange information, material, orenergyin order to perform their respective tasks. The items are exchanged according to a set of rulesand mechanisms implemented by an interface in each interacting resource. The interoperating

resources have a common understanding of the properties of the items exchanged.

Two or more resources, each with a distinct structure, behavior, and boundary, are integrated whenthese form a system that exhibits its own distinct structure, behavior, and boundary. A task is perceivedto be accomplished by a system and not by the integrated component resources that perform theirindividual roles. The integrated component resources collaborate, coordinate, and exchange

+organizes

Mfg. Resource(S stem)Task +supportedBy

1..*

+perfor s

1..*

Mfg. Process 1

+implements

1..

Activity

1

1..*

Role1..*

+participates

0..*+implements

1..*1..*

Behavior1

+exhibits

0..*+exploits

1..*

1..*

Interface

1

+provides 0..*

Interaction +uses1..*

+supports

1..*

+invokes

ManufacturingAsset Mfg. Resource

(Com onent)

Mfg. InformationExchange




8/12

information, material or energy as needed to perform a systems task. Interoperability amongcomponent resources is a pre-requisite to system integration,

The interoperability of the resources within a process requires the use of compatible interfaces. Theseinterfaces must be configured to support the flow characteristics, such as, quantities, qualities, sources,

destinations, and transfer rates. Other requirements include cost, safety, security, and environmentalcompatibility in order to realize the flows.

Each flow can be modeled as a detailed UML sequence diagram showing the resources involved, theitems transferred among these resources, and each transfers time-related properties (e.g. initiation,ordering, synchronization, completion). Each transfer between resources can be associated with a typeof interface that is configured and deployed in each resource participating in the particular transfer.Examples of these interface types are sensor interfaces for physical signal acquisition, mechanicalinterfaces for material handling, human-machine interfaces for operator commands and displays,electrical interfaces for power supplies, network interfaces for devices, etc. To support the requiredflows, each interface supports a set of required services, where each service offers a certain grade and a

specific quality of service. For each interface, the set of interfaces and configuration settings aredenoted in a corresponding set of resource interoperability profiles.

The information flows among the resources involve data types, meanings, structures, transactionsequences and timing of exchanges that are handled by a set of software and hardware interfaces.These interface specifications and required settings are summarized in a set of information exchangeinteroperability profiles. The combined sets of interoperability profiles for the resources and theinformation exchanges to support a particular manufacturing process form an ISO 15745 processinteroperability profile.

4 Integrated Applications4.1 Interoperability among applications within a levelBy analogy, an activity modeling framework similar to ISA S95 can be constructed for Level 2. TheLevel 2 operations can be modeled in terms of generic activities i.e., identify, move, make, test, andfix. These activities can be organized into application domains, along with a set of processes,resources, and information structures and information exchanges, to perform control, diagnostics, andmaintenance functions as shown in Figure 2. In the ISO 18435 scheme, the integration of twomanufacturing applications within Level 2 can be described in terms of a set of ISO 15745 processinteroperability profiles that support both inter-process and intra-process flows. Some resources areinvolved in both intra-process and inter-process flows and in many cases, the same interfaces support

intra-process, as well as, inter-process information exchanges. To interoperate with all the other Level2 applications, each application needs to offer a set of resource interfaces that are referenced in thecorresponding interoperability profiles. Integrated applications at Level 2 have compatibleinteroperability profiles.

Similarly, the Level 3 activities defined in ISA S95 can be grouped into application domains, such as,production, capability assessment and maintenance shown in Figure 2. Each integrated application can





9/12

be modeled as a set of processes with resources, such as, mainframe computing units, local and widearea networks, manufacturing operations management personnel, and Level 3 software. Theseresources support the intra-process and inter-process flows that are denoted in the associatedinteroperability profiles. Thus, to enable each Level 3 application to interoperate with all the otherLevel 3 applications, a complete set of intra-process and inter-process ISO 15745 interoperability

profiles can be designated for Level 3. The combined set of interfaces referenced in the interoperabilityprofiles will enable production, capability assessment and maintenance applications to beinteroperable, thereby, achieving the desired integration of Level 3 applications.

4.2 Interoperability among applications at different levelsAt Levels 3 and 2, both types of process flows occur within an integrated application or betweeninteroperable applications. Some resources are involved in both intra-process and inter-process flowsand in many cases, the interfaces support intra-application, as well as, inter-application informationexchanges.

When integrating two applications each located at different levels of an application hierarchy, the

respective processes of these applications are expected to satisfy a set of inter-process interoperabilityprofiles, some intra-level and others inter-level. In particular, three applications at Level 3 that need tointer-operate with three applications at Level 2, will comprise nine sets of inter-process interoperabilityprofiles that represent a required integration of Level 3 to Level 2 applications. However, the differenttypes and the instances for each type of resource interface to support the required informationexchanges can be minimized by use of common services and protocols, such as, data syntax andsemantics, data communication networks, data entry and display conventions, security and safetyprocedures.

4.3 Use case exampleWhen a customer order is received byEnterpriseapplications, anOrder Managementactivity triggersa request to aProduction Planningactivity. TheSite & Areaapplications ascertain fromProductionOperationsandMaintenance Trackingactivities on the likelihood of delivering the order on timebased on the available capability and capacity of the production resources. The actors involved in thescenario are illustrated in a UML use case diagram in Figure 7.

FIGURE 7 - CAPABILITY ASSESSMENT USE CASE

Work Centers and UnitApplications

Site & AreaApplicationsProduction

Personnel

MaintenancePersonnel

EnterpriseApplications

ManufacturingManagement

PersonnelProduction Planning &

Operations

Control

Condition Monitoring

MaintenanceTracking

Order Management





10/12

In this example, a customer order for delivery at some time is exchanged between Level 4 and 3 asProduction DefinitionsandProduction Requests information exchanges, as shown in Figure 8.

To obtain a delivery date, theCapability Assessment & Order Fulfillmentapplication involving theProduction Resource Managementand theMaintenance Trackingactivities evaluates the likelihood

of fulfilling the order based upon the expected availability of the required types of resources. Both theProduction Data Collection and theMaintenance Data Collection activities obtain status andforecasting data from the Level 2 Asset Prognostics and Health Assessment application and share thesewith theProduction and Maintenance Planning & Schedulingapplications.

As shown in Figure 8, the Level 3 applications ofProduction Operations Planning & Scheduling,Capability Assessment & Order FulfillmentandMaintenance Planning & Schedulingcan beelaborated in terms of the detailed generic activity model of Figure 4.

FIGURE 8 PRODUCTION AND MAINTENANCE APPLICATION INTEGRATION

The Work Center and Unit activities at Levels 2, 1, and 0 can also be modeled following thedefinitions provided by ISO 13374[4] as shown in Figure 9.

FIGURE 9 - ISO 13374 ACTIVITY DESCRIPTIONS

Level 4

Level 3 ProductionDetailedScheduling

Productionresponse

ProductionDefinition

Management

Production

Dispatching

Production

Tracking

ProductionAnalysis

ProductionExecution

ProductionData

collection

Productioncapability

Productiondefinitions Productionrequest

ProductionResource

Management

MaintenanceDetailed

Scheduling

Maintenance

response

Maintenance

DefinitionManagement

MaintenanceDispatching

Maintenance

Tracking

MaintenanceAnalysis

MaintenanceExecution

MaintenanceData

collection

Maintenancecapability

Maintenancedefinitions

Maintenance

ResourceManagement

Maintenancerequest

Level 2

HealthAssessment

DecisionSupport

Advisory Generation

Level 2

Level 1

Sensor

PrognosticsAssessment

ConditionMonitoring

DataManipulation

Data

Acquisition

Presentation

Level 0





11/12

The signals received from a sensor are used for diagnostics, asset condition monitoring, prognostics,and asset health assessment. The formats for the signals acquired, I/O conditioning, computed datameasurements, and information about an assets remaining useful life are specified by interfacesselected 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.

These information exchanges and the interfaces can be gleaned upon using a UML activity(interaction) diagram, shown in Figure 10.

Production Planning

Production Resource Management

Production Detailed Scheduling

Maintenance Tracking

Maintenance Data Collection

Production Definitions

Production Request

Get Asset Status

Give Asset Status

Get Asset Availability

Give Asset Availability

Production Capacity

Production Capabil ity

FIGURE 10 ACTIVITY INTERACTION DIAGRAM

The response from the manufacturing system is a capability assessment that indicates to the businessplanning system the production systems ability to respond to the production request. By using theinformation descriptions and semantics of ISO 13374, the assessment of the capability of the assetsrequired for a particular production scenario can be done. The information exchanges are denoted bythe messages (horizontal lines) between the time horizons (vertical lines) of the interacting resourcesassociated with each activity domain (top boxes). These information exchanges can be conducted if theresources involved implement the required interoperability interfaces. These interfaces and theirspecific configurations to support the application scenario are represented by the interoperabilityprofiles.

Another activity interaction diagram can show the information exchanges among the Level 2applications, as well as, the exchanges between the applications at different levels. When theinformation exchanges among all the activities have been accounted for, every resource at each level inthe application hierarchy will have an associated set of interfaces. These interfaces provide not only thecommunications connectivity (e.g. Ethernet/IP[10], Foundation Fieldbus[11]) but also the commondata syntax (e.g. CIP[10], XML[6], OPC) and semantics (e.g. MIMOSA OSA-EAI, ebXML) that are




12/12

required by the applications. The interoperability among the various applications at the differentfunctional and physical levels of an organization lead to a more effective, responsive, integrated, andcompetitive enterprise.

5 CONCLUSION and FUTURE WORK

The integration of diagnostics, maintenance, capability assessment, production and control applicationscan be described using the combined aspects of ISO 18435, IEC 62264, ISO 15745, and ISO 13374standards. The interoperability interfaces are delineated and defined in ISO 18435 using theapplication integration framework of ISO 15745, the levels and activity models of IEC 62264, and thediagnostics and condition monitoring framework provided by ISO 13374. ISO 18435 also provides ascheme to define the activities, resources and information exchange interfaces to aid in specifyinginteroperability profiles based on the ISO 15745 templates.

REFERENCES

[1]IEC, Geneva, Switzerland, 2003, IEC 62264-1, Enterprise-control system integration - Part 1:Overview and model terminology.

[2]IEC, Geneva, Switzerland, 2004, IEC 62264-2, Enterprise-control system integration - Part 2: Dataobjects and attributes.

[3] ISO, Geneva, Switzerland, 2003, ISO 15745-1, Industrial automation systems and integration Open systems application integration framework - Part 1: Generic reference description.

[4]ISO, Geneva, Switzerland, 2002, ISO 13374-1, Condition monitoring and diagnostics of machines Data processing, communication and presentation - Part 1: General guidelines.

[5]OMG, Needham, Massachusetts, U.S.A., 2004, UML V2.0, Unified Modeling LanguageSpecification, Version

[6]W3C, Cambridge, Massachusetts, U.S.A., 2000, Rec-XML-20001006, Extensible Mark-upLanguage, 2nd Edition.

[7]ISA, Raleigh, North Carolina, U.S.A., 2000, ANSI/ISA S95.00.01, Enterprise-control systemintegration - Part 1: Models and terminology.

[8]ISA, Raleigh, North Carolina, U.S.A., 2001, ANSI/ISA S95.00.02, Enterprise-control systemintegration - Part 2: Object model attributes.

[9] ISA, Raleigh, North Carolina, U.S.A., 2005, ANSI/ISA S95.00.03, Enterprise-control systemintegration - Part 3: Activity models for manufacturing operations management.

[10] ISO, Geneva, Switzerland, 2003, ISO 15745-4, Industrial automation systems and integration Open systems application integration framework - Part 4: Reference description for Ethernet-basedcontrol systems

[11] IEC, Geneva, Switzerland, 2003, IEC 61784-1, Profile sets for continuous and discretemanufacturing relative to fieldbus use in industrial control systems


M C i k Pl L k id C t Chi Illi i i