ISO 10303 is grouped by scope: • Part 1 Overview and fundamental principles • Part 2 Vocabulary • Parts 11 to 19 : Description methods:
EXPRESS, EXPRESS-X • Parts 21 to 29 : Implementation methods:
STEP-File,
STEP-XML,
SDAI, C/C++/Java language bindings interfaces, • Parts 31 to 39 :
Conformance testing methodology and framework • Parts 41 to 62 (99) : Integrated generic resources (IR) • Parts 101 to 199 : Integrated application resources • Parts 201 to 299 : Application protocols (AP) • Parts 301 to 399 : Abstract test suites (ATS) • Part 400 : Reference schema for sysml mapping • Parts 401 to 499 : Application protocol modules (Implementation modules for APs) • Parts 501 to 599 : Application interpreted constructs (AIC) • Parts 1001 to 1999 : Application Modules (AM) • Parts 3001 to 3099 : Business object models • Part 4000 : Core model • Parts 4401 to 4499 : Domain models, and • Parts 5001 to 5999 : Usage guides
Overview In total STEP consists of several hundred parts and every year new parts are added or new revisions of older parts are released. This makes STEP the biggest standard within ISO. Each part has its own scope and introduction. In
Description methods STEP defines data models using the EXPRESS modeling language. Application data according to a given data model can be exchanged either by a
STEP-File,
STEP-XML or via shared database access using
SDAI. The
APs are the top parts. They cover a particular application and industry domain and hence are most relevant for users of STEP. Every AP defines one or several Conformance Classes, suitable for a particular kind of product or data exchange scenario. To provide a better understanding of the scope, information requirements and usage scenarios an informative application activity model (AAM) is added to every AP, using
IDEF0. In APs with several
Conformance Classes the top data model is divided into subsets, one for each Conformance Class. The requirements of a conformant STEP application are: • implementation of either a
preprocessor or a
postprocessor or both, • using one of the STEP implementation methods STEP-File, STEP-XML or SDAI for the AIM/MIM data model and • supporting one or several conformance classes of an AP. Originally every APs was required to have a companion
Abstract test suite (ATS) (e.g. ATS 303 for AP 203), providing
Test Purposes,
Verdict Criteria and
Abstract Test Cases together with example STEP-Files. But because the development of an ATS was very expensive and inefficient this requirement was dropped and replaced by the requirements to have an informal validation report and recommended practices how to use it. Today the recommended practices are a primary source for those going to implement STEP.
Application Interpreted Models Every AP defines a top data models to be used for data exchange, called the
Application Interpreted Model (AIM) or in the case of a modular AP called
Module Interpreted Models (MIM). These interpreted models are constructed by choosing generic objects defined in lower level data models (Parts 4x, 5x, 1xx, 5xx) and adding specializations needed for the particular application domain of the AP. The common generic data models are the basis for interoperability between APs for different kinds of industries and life cycle stages.
Application Reference Models The
Application Reference Models (ARM) is the mediator between the AAM and the AIM/MIM. Originally its purpose was only to document high level application objects and the basic relations between them.
IDEF1X diagrams documented the AP of early APs in an informal way. The ARM objects, their attributes and relations are mapped to the AIM so that it is possible to implement an AP. As APs got more and more complex formal methods were needed to document the ARM and so EXPRESS which was originally only developed for the AIM was also used for the ARM. Over time these ARM models got very detailed till to the point that some implementations preferred to use the ARM instead of the formally required AIM/MIM. Today a few APs have ARM based exchange formats standardized outside of ISO TC184/SC4: • PLM-Services within the
OMG for AP 214 •
ISO 14649 Data model for computerized numerical controllers for AP 238 • PLCS-DEXs within
OASIS (organization) for AP 239 There is a bigger overlap between APs because they often need to refer to the same kind of products, product structures, geometry and more. And because APs are developed by different groups of people it was always an issue to ensure interoperability between APs on a higher level. The
Application Interpreted Constructs (AIC) solved this problem for common specializations of generic concepts, primarily in the geometric area. To address the problem of harmonizing the ARM models and their mapping to the AIM the
STEP modules were introduced. They contain a piece of the ARM, the mapping and a piece of the AIM, called MIM. Modules are built on each other, resulting in an (almost) directed graph with the AP and conformance class modules at the very top. The modular APs are: • AP 209,
Composite and metallic structural analysis and related design • AP 210,
Electronic assembly, interconnect and packaging design • AP 221,
Functional data and schematic representation of process plants • AP 236,
Furniture product data and project data • AP 239,
Product life cycle support • AP 242,
Managed model based 3d engineering The modular editions of AP 209 and 210 are explicit extensions of AP 242.
Coverage of STEP Application Protocols (AP) The STEP APs can be roughly grouped into the three main areas design, manufacturing and life cycle support. Design APs: • Mechanical: • AP 207,
Sheet metal die planning and design • AP 209,
Composite and metallic structural analysis and related design • AP 235,
Materials information for the design and verification of products • AP 236,
Furniture product data and project data • AP 242,
Managed model based 3d engineering • Connectivity oriented electric, electronic and piping/ventilation: • AP 210,
Electronic assembly, interconnect and packaging design. The most complex and sophisticated STEP AP. • AP 212,
Electrotechnical design and installation. • AP 227,
Plant spatial configuration • Ship: • AP 215,
Ship arrangement • AP 216,
Ship moulded forms • AP 218,
Ship structures • Others: • AP 225,
Building elements using explicit shape representation • AP 232,
Technical data packaging core information and exchange • AP 233,
Systems engineering data representation • AP 237,
Fluid dynamics has been cancelled and the functionality included in AP 209 Manufacturing APs: • AP 219,
Dimensional inspection information exchange • AP 223,
Exchange of design and manufacturing product information for cast parts • AP 224,
Mechanical product definition for process plans using machining features •
AP 238 - Application interpreted model for computer numeric controllers • AP 240,
Process plans for machined products Life cycle support APs: • AP 239,
Product life cycle support • AP 221,
Functional data and schematic representation of process plants • AP 241,
Generic Model for Life Cycle Support of AEC Facilities (planned) The AP 221 model is very similar to the ISO 15926-2 model, whereas AP 221 follows the STEP architecture and ISO 15926-2 has a different architecture. They both use ISO-15926-4 as their common reference data library or dictionary of standard instances. A further development of both standards resulted in the
Gellish English dictionary, representing a general product modeling language that is application domain independent and that is proposed as a work item (NWI) for a new standard. The original intent of STEP was to publish one integrated data-model for all life cycle aspects. But due to the complexity, different groups of developers and different speed in the development processes, the splitting into several APs was needed. But this splitting made it difficult to ensure that APs are interoperable in overlapping areas. Main areas of harmonization are: • AP 212, 221, 227 and 242 for (electro)technical drawings with extension in AP 212 and 221 for schematic functionality • AP 224, 238 and 242 for machining features and for
Geometric dimensioning and tolerancing For complex areas it is clear that more than one APs are needed to cover all major aspects: • AP 212 and 242 for electro-mechanical products such as a car or a transformer. This will be addressed by the second edition of AP242 that is currently under development • AP 242, 209 and 210 for electro/electronic-mechanical products • AP 212, 215, 216, 218, 227 for ships • AP 203/214, 224, 240 and
238 for the complete design and manufacturing process of piece parts. ==See also==