BS ISO 14258-1998 Industrial automation systems - Concepts and rules for enterprise models《工业自动化系统 企业模式概念和规则》.pdf

1、BRITISH STANDARD BS ISO 14258:1998 Industrial automation systems Concepts and rules for enterprise models ICS 25.040.40; 35.240.50BSISO14258:1998 This British Standard, having been prepared under the directionof the DISC Board, waspublished under the authorityof the Standards Boardand comes into eff

2、ect on 15 December1998 BSI 05-1999 ISBN 0 580 30879 0 National foreword This British Standard reproduces verbatim ISO14258:1998 and implements it as the UK national standard. The UK participation in its preparation was entrusted to Technical Committee AMT/5, AMT reference model, which has the respon

3、sibility to: aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the UK interests informed; monitor related international and European developments and promulgate them in the UK. A li

4、st of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “Internatio

5、nal Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a Briti

6、sh Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pagesi andii, theISO title page, pages ii to iv, pages1 to12 and a back cover. This standard has been updated (see copyright date) and may have had am

7、endments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No. Date CommentsBSISO14258:1998 BSI 05-1999 i Contents Page National foreword Inside front cover Foreword iv Text of ISO 14258 1ii blankBSISO14258:1998 ii BSI 05-

8、1999 Contents Page Foreword iv Introduction 1 1 Scope 1 2 Definitions 1 2.1 Definitions of enterprise concepts 1 2.2 Definitions of model concepts 1 3 Concepts and rules 2 3.1 Purpose of enterprise models (informative) 2 3.2 System theory as a basis for enterprise models 2 3.2.1 Methodologies derive

9、d from system theory (informative) 2 3.2.2 Factors of production 2 3.2.3 Scope of enterprise models 2 3.2.4 Availability and format of model information 3 3.2.5 Semantics and syntax of an enterprise model 3 3.2.6 Management of constituent parts 3 3.3 Concepts for life-cycle phases (informative) 3 3.

10、3.1 Issue-solving activities 3 3.3.2 Life cycle of systems 3 3.3.3 Recursion 4 3.3.4 Iteration 4 3.3.5 Naming 4 3.4 Hierarchy 4 3.4.1 Concepts of hierarchy (informative) 4 3.4.2 Usages of hierarchy 4 3.5 Structure 4 3.5.1 Concepts of structure (informative) 4 3.5.2 Compatibility of structuring appro

11、aches 7 3.6 Behavior 7 3.6.1 Concepts of behavior (informative) 7 3.6.1.1 Time representation 7 3.6.1.2 Static representation 7 3.6.1.3 Dynamic representation 7 3.6.1.4 Short-term and long-term behavioral change 7 3.6.1.5 Sequentiality 7 3.6.2 Representation of behavior 7 3.7 Relating the real world

12、 to enterprise models through views 7 3.7.1 Purposes of models (informative) 7 3.7.2 Real world (informative) 8 3.7.3 Observers (informative) 8 3.7.4 Views 8 3.7.4.1 Information view 8 3.7.4.2 Function view 8 3.7.5 Rules for model views 8 3.8 Requirements for standards on model interoperability 9 3.

13、8.1 Concepts of model integration (informative) 9 3.8.2 Forms of interoperability (informative) 9 3.8.3 Need for standards to support interoperability 10 4 Compliance and conformance 10BSISO14258:1998 BSI 05-1999 iii Page Annex A (informative) A context and vision for enterprise models 11 Bibliograp

14、hy 12 Figure 1 Mapping between system life-cycle phases and system activities W, H, and D 3 Figure 2 Decompose “Design Product” activity to show recursiveness of activities W, H, and D 5 Figure 3 Iterating the “Design Product” activity to show feedback used for process improvement 6 Descriptors: Aut

15、omation, automation engineering, computer applications, manufacturing, companies, models, rules (instructions).BSISO14258:1998 iv BSI 05-1999 Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of prep

16、aring International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in

17、liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Public

18、ation as an International Standard requires approval by at least75% of the member bodies casting a vote. International Standard ISO14258 was prepared by Technical Committee ISO/TC184, Industrial automation systems and integration, Subcommittee SC5, Architecture and communications. Annex A of this In

19、ternational Standard is for information only.BSISO14258:1998 BSI 05-1999 1 Introduction The major objective of this International Standard is to define concepts and rules for enterprise models (see clause3) with the intent to guide and constrain other standards or implementations that do or will exi

20、st on the topic. It accomplishes this by defining the elements to use when producing an enterprise model (see3.2), concepts for life-cycle phases (see3.3), and how these models describe hierarchy (see3.4), structure (see3.5), and behavior (see3.6). This International Standard provides guidelines and

21、 constraints for enterprise models to anyone attempting to model an enterprise or to model processes (see3.7). The users of this International Standard are primarily the standards bodies making more detailed standards about a part of the integration and modeling domain. Systems implementers may also

22、 find value in the structure developed in this International Standard so that their developments parallel the concepts outlined herein. If conforming implementation designs have the same technology areas and nomenclature, or are able to map to them readily, the information of one enterprise or proce

23、ss can be more readily shared with information of another enterprise or process (see3.8). The rationale for this International Standard is that other well-designed standards in the domain of enterprise integration and modeling are needed to provide a known environment to enterprise designers. Thus,

24、the risk of investing in islands of integration can be significantly reduced. Where an island does exist, then these standards assist the designer to create the translation required for the island to interact with the known environment. A standard for enterprise models should enhance interoperabilit

25、y by establishing the elements that must be present in an enterprise model. These elements will come into play when there is need for one process to communicate with another. 1 Scope This International Standard specifies concepts and rules for computer-understandable models of a manufacturing enterp

26、rise to better enable enterprise processes to interoperate. This International Standard does not define standard enterprise processes, standard enterprises, standard organizational structures, or standard enterprise data. In addition, this International Standard does not specify the enterprise-model

27、ing process, but forms the basis by which enterprise-modeling standards can be developed where they are needed. 2 Definitions For the purposes of this International Standard, the following terms and definitions apply. 2.1 Definitions of enterprise concepts 2.1.1 enterprise a group of organizations s

28、haring a set of goals and objectives to offer products, services or both 2.1.2 environment the uncontrollable part of a system which is widened to the extent that a decision-taking procedure cannot be conceived for the control of such a system 2.1.3 factors of production that which is required to tr

29、ansform, transport, store, and verify raw materials, parts, (sub-) assemblies, and end products 2.1.4 user of standard one who applies the requirements of this International Standard for whatever purpose EXAMPLE 1 Enterprise planners, builders, modifiers, and analyzers using the requirements to chec

30、k completeness of their activity. EXAMPLE 2 Enterprise-model builders using the requirements to assure consistency between models to enable model interoperability. EXAMPLE 3 Developers of standards for enterprise representation using the requirements to assure consistency between their standards and

31、 this International Standard. 2.2 Definitions of model concepts 2.2.1 abstraction a shortening in duration or extent with no sacrifice of sense, used to differentiate between a real-world system and a model of the real world 2.2.2 behavior how an element acts and reacts 2.2.3 constraint restrictions

32、 and limitations on the system which can come from inside or outside the system under consideration 2.2.4 element a basic system part that has the characteristics of state, behavior, and identificationBSISO14258:1998 2 BSI 05-1999 2.2.5 enterprise model a representation of what an enterprise intends

33、 to accomplish, how it operates and possibly how it is organized, which is used to improve the effectiveness and efficiency of the enterprise NOTEAn enterprise model is an abstraction that represents the basic elements of an enterprise and their decomposition to any necessary degree. It also specifi

34、es the information requirements of these elements, and provides the information needed to define the requirements for integrated information systems. 2.2.6 model a representation of something else expressed in mathematics, symbols, or words NOTEA model is an abstraction that represents ones understa

35、nding of a system or situation, and of the relevant elements and relationships. It represents the system elements and the connectivity between the elements. 3 Concepts and rules 3.1 Purpose of enterprise models (informative) Enterprise models are used as tools to describe and represent an enterprise

36、 in the context of a given purpose. Enterprises are systems that can be analyzed and modeled using systems theory. These models can be constructed to analyze, guide the engineering of, and manage the operation of enterprises. The rules presented in clause3 are designed to support these usages and to

37、 allow information transfer between enterprise models. 3.2 Systems theory as a basis for enterprise models Enterprise models conforming to this International Standard shall be constructed to conform to the relevant elements of systems theory. The normative concepts and rules presented in clause3 des

38、cribe these relevant elements of systems theory and relate them to model content and characteristics. 3.2.1 Methodologies derived from systems theory (informative) In literature 1)there are various methodologies derived from general systems theory which emphasize different aspects. The three most fr

39、equently used aspects are the structural aspect, behavioral aspect, and hierarchical aspect. The structural aspect is based on the principle that elements are not isolated but have multiple interdependencies with other elements of the system. The interdependencies are the explanation why the whole (

40、system) exhibits properties different from the properties of its parts (elements). The behavioral aspect is based on the identification of variables and their functional or other relationships. If the variables are restricted to input and output variables the system is considered as a black box. The

41、 hierarchical aspect is based on the principle that an element of a system can itself be regarded as a system, which is then called a subsystem. Similarly the system under consideration can be regarded as an element of another system, which is then called a supersystem. This implies the assignment o

42、f levels of abstraction to systems. Because of interdependence new properties can emerge at a higher level in the hierarchy. Steps to lower levels allow one to obtain more detailed description of the system under consideration and how it achieves its purpose. Steps to higher levels allow one to unde

43、rstand the role of the system within its environment. Each level is describable in terms of structure and behavior. Depending on the desired purpose particular methodologies are applicable. Steps downward expose the inner structure of the subsystem. This could be achieved by observation, by logical

44、conclusion, or by design in the case of systems under development. Steps upward expose the behavior of the system in its environment. Similarly this could be achieved by observation, by logical conclusion, or by making assumptions in the case of systems under development. 3.2.2 Factors of production

45、 Enterprise models shall address what happens to the factors of production (such as people, capital, material, information, energy, and tools) during the phases of the enterprise or product life cycle. 3.2.3 Scope of enterprise models Enterprise models shall define relevant aspects of the enterprise

46、 necessary to conceive, design, procure for, and construct an enterprise consisting of any set of related chosen processes, manage and operate an enterprise so that it can meet its objectives, support an enterprise to design, modify, operate, or dismantle it. 1) An Approach to General Systems Theory

47、, George J. Klir (1969); An Introduction to General Systems Thinking, Gerald M. Weinberg (1975).BSISO14258:1998 BSI 05-1999 3 3.2.4 Availability and format of model information In an operating scenario the information captured by an enterprise model shall be available to humans or machines responsib

48、le for successful operations. The information shall be either in a neutral format (preferable) or as specified by the using application. 3.2.5 Semantics and syntax of an enterprise model Models, as representations of enterprises, shall carry syntax and semantics. The syntax of a model refers to the

49、permissible arrangements of the representations of the elements and to the permissible kinds of relations. The semantics of a model encompass the meanings of the elements and relations with respect to enterprise-model concepts. The syntactic form and semantic content of a model will be different depending, for example, on the purpose of the model and on the boundary and the environment of the enterprise. 3.2.6 Management of constituent parts Enterprise models shall be designed in such a way as to allow their constituent parts to be managed by an automated c