ISO/TC 184/SC 5
STRATEGIC PLAN
NOTE This version of the strategic plan was reviewed and approved both by SC 5 and TC 184 at their respective plenary meetings in May 1998. More information regarding this document can be obtained from either Greg Winchester, SC 5 Secretary (email: gre_winchester@nema.org) or Em dela Hostria, SC 5 Chairman (email: egdelahostria@ra.rockwell.com).
1 About this plan
This SC 5 strategic plan has been developed by the SC 5 Strategy Planning Group (SPG), which is the advisory body to SC 5 tasked to define and review SC 5’s standards strategy. The SPG will meet on an as-needed basis with an appropriate membership to ensure the strategic plan is relevant, focused, and enhances participation in the SC 5 work program.
This document is based on the strategic plan of TC 184 and takes into account input primarily from the following groups:
a) ISO/TC 184/SC 4/WG 8;
b) CEN/TC 310;
c) SC 5/WG 1;
d) ICEIMT Metrics;
e) CALS/HLSG;
f) ISO/TC 184/SC 1/WG 7;
g) ISO/TC 184/SC 4/WG 10;
h) ISO/TC 184/AG.
This document acknowledges that SC 5 has been chosen by TC 184 to provide the integrating overview across the areas of industrial automation identified in TC 184’s scope and strategic plan. As such, TC 184 will rely upon SC 5 as the developer of standards that integrate the standards of the other TC 184 SCs, as well as the standards of other relevant bodies. Therefore, this plan will make references to work under the responsibility of TC 184 SCs and other bodies, as SC 5 must also rely on these bodies to produce standards to fulfill SC 5’s stated objectives.
This strategic plan is a living document and shall be considered by the SC 5 Chairman as the guidelines for the development of architecture and communications standards required by the SC 5 P-members and the industrial automation and integration industry they serve. For users of these standards, this plan can be considered as a comprehensive summary and schedule of emerging SC 5 standards. This plan can also be used to identify potential and actual delays in the SC 5 standards development process and assist in the formulation of solutions to overcome these delays.
2 Implementation of this plan
The tasks associated with implementing this plan (with those responsible within SC 5 for these tasks shown in parentheses), are as follows:
a) Reporting of SC 5’s progress per the strategic plan (SC 5 Secretariat);
b) Analysis of progress reports and authorization of any necessary corrective actions (SC 5 P-members);
c) Standards development/revision (WGs or project leaders as assigned by SC 5 Secretariat);
d) Work/resources planning (SC 5 SPG).
3 Industrial and economic environment in which SC 5 operates
3.1 Prevailing conditions
The following conditions are assumed for the planning period (3 to 6 years from now):
a) manufacturing enterprises, due to competition, must deliver increased customer satisfaction and quality, with increased efficiency, at lower production and ownership costs in a shorter lead time;
b) customers are moving away from traditional process-oriented standards to an overall performance-related approach to products, which gives businesses some flexibility in determining how the required performance is to be delivered;
c) industry is allocating more resources to increase its awareness of the status and usefulness of existing standards;
d) industry implementation of existing standards (which apply only to the current or next generation of systems) is at a low level, thus leading to a growing base of vendor-specific solutions.
e) the contents and descriptions in standards are very complex and not understandable to most experts in end-user organizations, and guidance and implementation documentation for these end users is generally poor, difficult to use, or non-existent;
f) in the planning period (3 to 6 years from now), computer and information technologies will continue to change and progress very rapidly;
g) the ISO Directives call for a maximum of three years from NP to FDIS approval, new standards proposals to be very well defined at the start, and, as is currently the case, a minimum of five countries to agree to participate (with individual experts identified) in new proposals before further standardization steps can occur.
3.2 Enterprise-level trends
The following enterprise-level trends are expected based on the assumed conditions noted in 3.1:
a) there will be increased use of collaborative structures, involving partnerships, that may be created and dissolved rapidly to meet changing market needs;
b) the various business functions throughout the lifecycle of a product will be undertaken by increasingly integrated processes, which will continue to be optimized to drive down costs and timescales;
c) manufacturing equipment will need to be capable of being deployed more flexibly to support manufacture of a variety of products.
3.3 Technologies and associated standards
The following technologies and associated standards are expected to be needed to support the enterprise-level trends noted in 3.2:
a) specification of business information requirements and information flows optimized to form the backbone of both internal communication and delivery to the customer;
b) specification of the elements of manufacturing equipment that are designed for easy integration through local and remote networks;
c) modular sets of IT tools, used as building blocks, which can be assembled into systems with a minimum of integration costs;
d) simulation tools to model business processes and operations, and to evaluate the business impact of proposed changes;
e) real-time management and maintenance of assets, using multimedia technology for the delivery and presentation of information.
3.4 Needs from the standardization process
In general, the standardization process will need to make more efficient use of its resources, and to work to develop its market in parallel with the standards process. More specifically, the standardization process should provide for the following:
a) features and functionality that are based on actual and future needs of the users;
b) confirmation of industry interest through nomination of experts and/or endorsement of the need for the work;
c) funding resources that are managed and directed to match industry priorities;
d) cooperation with other standards bodies to avoid duplication and conflict;
e) development work undertaken with careful project planning using small working groups and using phases where first results can be achieved rapidly;
f) close cooperation with ongoing research and development work;
g) supplementary guidance information for industry (users and vendors) that can be given in an easily readable and understandable short form;
h) management of standards to ensure consistency of changes;
i) implementors involved from the start of the process, and pilot implementations encouraged in parallel with the standardization process;
j) monitoring of implementations and addressing of barriers to their progress by standards bodies.
4 Standardization objectives, scope, and priorities of SC 5
4.1 Overall standardization objective
The overall objective of SC5’s standardization activity is to ensure the following:
a) the work of SC5 supports and influences the TC184 strategic objectives;
b) the interests of SC5 P-members are served.
4.2 Standardization responsibilities of SC 5 supporting the overall objective
In addition to the stated responsibilities of TC184 appropriate to SC5 (see TC184/AG N153), SC 5 has the following responsibilities:
a) to work with TC184, its Advisory Group, and other bodies that identify and define standardization requirements in the area of integration (e.g., communications) and architecture for industrial automation;
b) to develop standards to enable integration of the control domain with other enterprise domains;
c) to work with bodies (e.g., CALS/HLSG, UN/EDIFACT) that coordinate standards in the area of electronic commerce relying on industrial automation standards;
d) to develop a framework for industrial automation profiles derived from the OSE guidelines developed by JTC1/SGFS;
e) to develop industrial automation application profiles that are based on IEC/ISO industrial automation standards, PASs, IT profiles, and OSI profiles;
f) ensure that resulting SC5-developed profiles enable interoperability and portability, and describes methods of conformance.
4.3 SC 5 title and scope
The title of SC 5 embodying the above responsibilities is as follows:
Architecture, Communications, and Integration Frameworks
The scope of SC 5 embodying these responsibilities is as follows:
Standardization in the field of enterprise architecture, communications, and processes to enable manufacturing system integration, interworking, and interoperability. This standardization will include:
· an automation glossary;
· process representations (i.e., exchange/negotiation in manufacturing enterprises);
· requirements for a global programming environment;
· manufacturing profiles likely to be utilized by industry.
4.4 SC 5 priorities regarding work items
When considering new work item proposals and giving direction to its WGs, the first priority of SC 5 will be for standards that enable integration within the manufacturing domain. SC 5’s second priority will be for standards that enable integration of the manufacturing domain with other enterprise domains. Proposals not at all concerned with the manufacturing domain will not be considered by SC 5.
5 Work program and objectives
5.1 Enabling enterprise agility
5.1.1 Objective
To enable enterprise agility and extension through architecture, data/information model, physical model, and profile standards for the integration of systems within an enterprise and between enterprises.
5.1.2 Needed areas of work to achieve objective
Areas of work, along with their status and priority are shown in Table 1.
5.2 Enabling interworking of systems
5.2.1 Objective
To enable interworking of systems through communications standards that address meta-data and meta-information, negotiation/brokering, and representation.
5.2.2 Needed areas of work to achieve objective
Areas of work, along with their status and priority are shown in Table 2.
Table 1 – Areas of work for enabling enterprise agility
|
Area of Work |
Status |
Priority |
|
a) Concepts and rules for enterprise models |
available Q1, 1998 |
1 |
|
b) Requirements for enterprise reference architectures and methodology |
available Q1, 1999 |
1 |
|
c) Enterprise modeling execution and integration services |
CEN work occuring; no SC 5 NP submitted |
3 |
|
d) Neutral representation of manufacturing ontologies |
no NP submitted |
3 |
|
e) Management and reconciliation of context-dependent semantics; alignment of context-driven semantics across enterprise domains |
no NP submitted |
3 |
|
f) Modeling of sharing and exchange processes in the extended enterprise |
no NP submitted |
3 |
|
g) Enterprise-control integration focusing on interfaces in industrial automation as shown in IEC Sector Board 3 document SB3/4/INF, page 3 |
ISA work occuring; no SC 5 NP submitted |
2 |
|
h) Rules and instances of manufacturing profiles |
no NP submitted |
2 |
|
i) Manufacturing automation programming environment (MAPLE) – MAPLE functional architecture |
ISO 13281 published |
– |
|
j) Manufacturing Automation Programming Environment (MAPLE) – MAPLE services and interfaces |
CD 15399 available Q4, 1998 |
1 |
|
k) Further detailing of the internal MAPLE components |
under discussion, but no NP submitted |
3 |
|
l) Process modeling of "descriptive" to "prescriptive" domain sharing/transfers; generation of manufacturing data from product data |
no NP submitted |
2 |
|
m) Generation of operating/maintenance data from manufacturing data and product data |
contribution to CALS; no NP required |
3 |
|
NOTE Priorities are as follows: 1 = in progress, with planned completion by 2000; 2 = to be started before 1999; 3 = to be worked on as resources are available. |
||
Table 2 – Areas of work for enabling interworking of systems
|
Area of Work |
Status |
Priority |
|
a) User requirements and network management in time-critical communications systems |
TR 13283 available Q1, 1998 |
1 |
|
b) Manufacturing message specification – Protocol specification; Manufacturing message specification – Service definition |
Revision to ISO/IEC 9506-1/-2 available Q1, 1999 |
1 |
|
c) International Standardized Profile AMM21: MMS robotic application base profile |
Awaiting DISP 15357 from S-liaison |
3 |
|
d) Use of multimedia delivery systems in the extended manufacturing enterprise |
no NP submitted |
2 |
|
NOTE Priorities are as follows: 1 = in progress, with planned completion by 2000; 2 = to be started before 1999; 3 = to be worked on as resources are available. |
||
5.3 Ensuring consistent, integrated standards
5.3.1 Objective
To ensure consistent, integrated standards that can be used by the industrial automation community, including other standards developers.
5.3.2 Needed areas of work to achieve objective
Areas of work, along with their status and priority are shown in Table 3.
Table 3 – Areas of work for ensuring consistent, integrated standards
|
Area of Work |
Status |
Priority |
|
a) develop list of industrial automation standards, PASs, reference documents to confirm/verify need for work items and to define their scope |
no standards development involved |
3 |
|
NOTE Priorities are as follows: 1 = in progress, with planned completion by 2000; 2 = to be started before 1999; 3 = to be worked on as resources are available. |
||
5.4 Providing technical oversight for TC 184 on integration
5.4.1 Objective
To provide technical oversight on behalf of TC 184 concerning integration of areas of industrial automation identified by TC 184.
5.4.2 Needed areas of work to achieve objective
Areas of work, along with their status and priority are shown in Table 4.
Table 4 – Areas of work for providing technical oversight
|
Area of Work |
Status |
Priority |
|
a) Application program dictionary and data dictionary, including semantics |
no NP submitted |
3 |
|
b) Inter-SC model integration |
no NP submitted |
3 |
|
c) Joint SC experts meeting |
no standards development involved |
– |
|
NOTE Priorities are as follows: 1 = in progress, with planned completion by 2000; 2 = to be started before 1999; 3 = to be worked on as resources are available. |
||