ISO 10303 which is STandard for the Exchange of Product model data (STEP) contains a large amount of extremely detailed information. There are no clear and easy instructions for implementing STEP, and the only way to check whether a developed software product actually satisfies STEP requirements is to test it using Conformance Classes (CCs), which are the subsets of STEP’s application protocols (APs). However, existing CCs do not give users any idea about the functional capabilities of a software product conforming to STEP. These deficiencies necessitate the development of new CCs based on functionality, to help both developers and users. In this study, to achieve this goal, the functionalities expected for different product lifecycle (PLC) activities are defined at several functionality levels (FLs), using a layered approach. This approach allows the defining of a composite functionality (higher FLs) through the composition of simple, basic functionalities (lower FLs). Information requirements are defined for each functionality, and these information requirements are mapped to STEP entities. These groups of entities for functionalities constitute our functionality-based CCs. In this paper, tolerancing functionality has been studied to develop functionality-based CCs as an example.
In this study, a functional and behavioral representation model for collaboration in product development is developed to represent assembly-related product knowledge, including its geometry, spatial relationships, function and behavior, which will be used to create a knowledge representation scheme to capture, store, and retrieve product knowledge. In this model, the function, behavior and artifact information is interrelated based on assembly associations. Functional and behavioral inputs and outputs are defined based on the spatial relationships in the assembly, as well as on the geometry of the product. The functional associations among artifacts define the “Behavior Model” with engineering formulas and physical rules. “Behavior Models” then define the behavior of the artifact. Behavior has four different forms for different phases in life cycle: (1) Intended Behavior in the conceptual design phase, (2) Estimated Behavior in the design phase, (3) Observed Behavior in the operation stage, and (4) Evaluated Behavior in the design and operation phases. When an unintended event (behavior) occurs, an additional function can be added to eliminate that effect. As a result, the functional and behavioral model is updated dynamically.