1、 Access to Additional Content for SAE GEIA-STD-927B, Dated: May 2013 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyright hol
2、der of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. GEIASTD927B Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer provides a way for stakeholders to understand their n
3、eeds in relation to the enterprise as a whole; and provides a continuous proactive means of identifying and successfully addressing key challenges for a complex system over time. The third is an evolved culture where enterprise-wide cooperation is the rule and individual contributions are encouraged
4、 and efficiently managed. This GEIA-STD-927 standard specifies the multi-domain data schema as described in the first bullet point above. The remaining two bullet points involve software and user implementation. NOTE: Within the standard, the terms system and product are synonymousGEIA-STD-927-B 1 1
5、. Scope GEIA-STD-927 specifies the data concepts to be exchanged to share product information pertaining to a complex system from the viewpoints of multiple disciplines. It supports the exchange of data across the entire life cycle for the product from the concept stage through disposal. It embraces
6、 several aspects: technical aspects which lead to the definition of functional and physical architectures (what the system is doing, how it is doing it and how well); technical management (work schedule, document generation, concurrent engineering, validation, and verification procedures); project a
7、spects which include project management issues (traceability management, configuration management, and trade-off analysis); industrial management (management of co-operation between partners). The following discipline views are within the scope of GEIA-STD-927: definition of other systems the system
8、 interacts with; context for the system in each life cycle phase; support of hierarchical break down modeling techniques; functional and non-functional requirements of the system in each life cycle phase; definition of the static and dynamic behavior of the system; configuration management of the sy
9、stem and its supporting documentation in each life cycle phase; condition monitoring and correction of the system. The following life cycle aspects are within the scope of GEIA-STD-927: systems engineering; feasibility assessment; requirements definition; domain engineering; system realization; syst
10、em operation; system support; system maintenance; decommissioning of the system. GEIA-STD-927-B 2 The following types of data are within the scope of GEIA-STD-927: data to describe the system; data to specify requirements of the system and their allocation to functional objects, physical objects, an
11、d the physical implementation; data to specify the static behavior of the system in terms of functions and flows between functions; data to specify dynamic behavior of the system; data to describe the functional decomposition of the system; data to support the physical architecture; data to support
12、the partitioning of the system; data to support the verification and validation of the system; data to specify the installation of the equipment, including physical locations and information; data about the shape of the equipment data to support project and industrial management; data to support the
13、 documentation of the system data to support configuration management; data used in domain engineering; data used for structural analysis; data used in feasibility assessment; data used in system realization; data used in and for system operation; data used for system maintenance; data used for deco
14、mmissioning of the system. GEIA-STD-927-B 3 2. Standard Organization GEIA-STD-927 is organized into a set of functionally defined subsets or views. 2.1 Activity View Definition An activity is an action and/or event which brings about change. The activity view presents the structures representing act
15、ivities and the methods to carry out activities. This view includes representations for projects and plans to manage activities, work orders to authorize activities, and resources to perform activities. Key Entities Activity_relationship a relationship between two activity objects Involvement assign
16、ment of an activity to any object in the model Subtypes of activity o Resource_management_activity activity that affects the balance or availability of a resource which is managed by a formal system o Logistics_activity a logistics operation o Process_activity an activity which is a component of a p
17、rocess o Analysis a detailed examination of the elements or structure of a Action_method a way to carry out an activity Action_method_for_activity assignment of an activity to its intended course of action Action_method_assignment assignment of an action_method to any object in the model Subtypes of
18、 action_method o Project/Project Entry a project is an object which identifies a program of work and, optionally, the resource management data associated with it o Task Specification / Task Component units of work needed to carry out an activity, such as loop_until Condition definition of the preced
19、ent that must be fulfilled before a statement or relationship becomes valid Labor this property represents labor provided by human resources. GEIA-STD-927-B 4 Observation historical record of something that has occurred during the lifecycle of system/product Project_assignment a mechanism to associa
20、te a project with activity or product data Resource_definition a specification of needed resources outside of application context, resources may be of any type such as human resources or material items Resource_occurrence specification of needed resources within an application context Resource_insta
21、nce item that can occur in the role of a resource within the application context Resource_assignment association between a resource_instance and the object that is designated as its assigned resource Result end point or objective which will be or has been reached Work_request solicitation for a chan
22、ge or the creation of something Work_order authorization for performing an activity GEIA-STD-927-B 5 2.2 Common View Definition The common view presents structures which are used by all other views. The common_view is used in combination with other functional views, such as product, to support all r
23、equired functionality. For example, one structure in the Common View is generic note which is a method of providing explanatory information for an object. Another example is the contract structure which provides contracting functionality for an object. Key Entities Actor person or organization playi
24、ng a role in association with another object in the model, such as a resource assigned to an activity Actor_assignment a generic relationship between a person or organization and of any type Alias_designation the mechanism to associate an object with an additional designation that is used to identif
25、y the object of interest in a different context, either in another organization, or in some other context Classification_system scheme used to define the categorization of an item, for example the Dewey Decimal system Class_library the identification of a library which provides definition for a clas
26、s Configuration_element_version point in time snapshot of any object for which a change history is maintained Contract binding agreement Contract_assignment assignment of a contract to any object in the model Generic_note explanatory information for an object in the model Item_designation identifier
27、 used to name objects uniquely within their scope, this identification scheme may be a formal classification system Language English, French, and hexadecimal languages are represented by instances of this object Notification a report of the occurrence of an event, an error message is an example of a
28、 notification GEIA-STD-927-B 6 Organization a group of actors (person(s) and/or organization(s) which may function as a single actor by being assigned groupwise the responsibility and/or execution of actions Period_in_time a type of that is all space for part of time a temporal part of the universe
29、Point_in_space a type of that has no spatial extent. Point_in_time whole space extension at an instant in time, for example the time known as 16hrs 31mins 23.56 seconds 13 May 1999 GMT Possible_role indication of the function or part an object can take with respect to some other object, for example
30、employee is a possible_role that indicates what a person has to do in an employment relationship Security_classification level of confidentiality that can be applied to protect activity or product data against unauthorized usage GEIA-STD-927-B 7 2.3 Configuration Management View Definition Configura
31、tion Management documents information captured during the performance of configuration management functions throughout a products lifecycle. The following functional areas of configuration management are supported: Configuration Management Planning and Management Configuration Identification Configu
32、ration Change Management Configuration Audit Configuration Verification Configuration Status Accounting Problem/Enhancement Reporting and Management Key Entities Actor a person or organization Action_method a way to carry out an activity Subtypes of action_method o Project - identifies a program of
33、work and, optionally, the resource management data associated with it o Task_Specification - a specification of work Activity a type of that plays a role in bringing about change. An activity includes the events that define its beginning and end. An activity may also include substates and the events
34、 that define the beginnings and ends of these substates. The roles of the substates are defined directly by classifying each substate or indirectly by classifying the superstate Subtypes of Activity o Configuration_management - controlled management of changes to products, documents, and other items
35、 o Logistics_activity - execution of a logistics operation such as maintenance. o Verification_activity verification an item meets some standard such as its design specification Cm_change_request a change request dealing with configuration management items GEIA-STD-927-B 8 Request_for_variance reque
36、st by a manufacturer or supplier requesting permission to depart from the contracted requirements of a product or service Deficiency - an actual or suspected product anomaly failure, or a recommended enhancement Deficiency_report a report of a product anomaly or failure or the request for an enhance
37、ment Documentation_definition documentation within a particular context such as a technical manual and represented by one or more particular formats File - a file stored on a computer system or in a stack of non-digital documents Property a type of that is a characteristic or quality of a . This cha
38、racteristic or quality is often a degree or magnitude which is quantified by mapping to numbers or units of measure Subtypes of Property o Result - an occurrence, and outcome or an objective. o Recommendation - information about recommendations made for a System_view collection of information about
39、a product such as all the information about the application footprint for an organization Subtypes of system_view o System_definition a type of system_view which represents a specification for some portion of the life cycle of a product/system. The system_definition, via relationships to collections
40、 of detailed entities (partial_system_view, function_definition, etc.), forms the system specification at that point in the product/systemss evolution. The specification may be in any degree of completeness Subtypes of system_definition Requirement_occurrence the specification of a requirement in th
41、e context of a requirement decomposition structure System_instance the depiction of a system specification in a particular context Subtypes of system_instance o Hardware_instance - is the depiction of a hardware specification in a particular context o Software_instance - the depiction of a software
42、specification in a particular context GEIA-STD-927-B 9 Realized_system the reference to a physically realized system produced in accordance with a specification identified by the realization_of attribute Subtypes of realized_system o Realized_hardware - the reference to a physically realized hardwar
43、e item produced in accordance with a specification identified by a hardware_instance o Software_build - executable program created at a specific point in time for a specific purpose by translating the high-level programming language in which the software item was written into its machine language eq
44、uivalents that a computer executes o Licensed_software - individual copy of a software_build which can be licensed and/or tracked o Partial_system_view a system_view which is oriented toward a particular domain, mode, scenario, or application context. The partial_system_view is intended to collect r
45、equirements in the requirements elicitation phase, and to capture domain, state or scenario specific information of a system. A partial_system_view on its own does not represent a specification for a particular system Subtypes of partial_system_view Requirement_instance the manifestation of a requir
46、ement_occurrence in the context of a system Operational_view - information that is common to all disposal, distribution, quality, maintenance, manufacturing, quality management, and training operations for a system or product Testing_view - information developed from product definition information a
47、nd used to exercise a product to identify differences between expected and actual behavior Source_code - computer instructions and data definitions expressed in a form suitable for input into an assembler, compiler, or other translator GEIA-STD-927-B 10 2.4 Documentation View Definition Documentatio
48、n may be a single file or a complex collection of information under version control. This view presents structures to capture, coordinate, and control collections of documentation for an object. For example, an owners manual for a car is represented by documentation structures. Key Entities Actor a person or organization Address specifies the location of a object in some defined space such as parcel, telephone, or email space Applied_information_usage_right application of a particular information usage right to an object Digital_file a dig
