AP233 Module Sets

The following identifies and describes the Module Sets for AP233, the STEP Systems Engineering Project

• Product Data Management (PDM) Extensions  – a data model(s) that extends the  STEP PDM Modules resources to service  electro-mechanical, system engineering, product life-cycle, and other non-physical domains.
  

• Work Breakdown Structure – a data model that is used to represent the pieces of work necessary to complete a project.

• Schedule – a data model that identifies activities, dependencies, durations and milestones associated with products described in the WBS.  Includes the information necessary to produce Workflow Diagrams, Network Schedules, Gantt Charts and Resource Leveling.

• Issue Tracking - a data model that provides information related to issue tracking such as title, status, assignment, classification, description, priority, etc.

• Cost Models – a data model that captures financial resource information e.g. direct, indirect, fixed, variable, material, administrative, finance, and contingency costs and provides linkage to system product structure(s).

• Behavioral Models – data models that capture semantics associated with how a system acts or performs (responds to excitation); include functions, inputs, outputs and control operators which define the ordering of functions; includes both Function-based and State-based  behaviors; enables generation of Functional Flow Block Diagrams, Finite State Machines, Causal Chain, Data Flows and Sequence Diagrams, etc.
  

• Requirements – a data model that captures requirements as text strings with traceability, allocation, weighting and  risk identified with each requirement [Text-based Requirements (TBR)] and that describes requirements as structured and quantified formalisms that maybe decomposed from text-based requirements; can include tables, spreadsheets, graphs, charts, pictures and equations [Property-based Requirements (PBR)].

• Structural Models – a data model that captures the organization of a system.e.g how a system is built, static relationships between subsystems, components, or parts that constitute the system; describes what is designed, characterized built and maintained.

• Risk Analysis – a data model that identifies risk status, relationships, likelihood, consequence, impact, approach strategy, and contingencies.

• Rules - a data model that describes the information associated with constraints imposed on a product or process by system requirements, physical limitations and/or environmental restrictions.  The model includes sufficient information to represent and/or support the constraint e.g. predicate calculus, the constraint life-cycle, constraint execution and associated meta-data, such as source, date and time, authorization, justification, description and notes. 

• Validation Model – a data model that captures  theinformation used to demonstrate that the emerging product is consistent with the stakeholder needs.

• AP Interface Models – a data models that provide interfaces between domain specific data models such as mechanical, electronic, structural analysis, thermal analysis, manufacturing, etc. e.g. the transform between engineering analysis (AP209, STEP-TAS, STEP-NRF, AP235, etc.) and any AP233 module set.
  

• Data Presentation  – a data model that provides a consistent set of “presentation mechanisms” and “advanced schematics product model definitions”, that present the computer sensible model data (defined in re presentation model space) onto a human understandable schematic diagram (presentation space), conforming to conventional and/or future draughting standards.

• Measurement – a data model that includes information associated with the product development process quantification and its control and optimization.