ASME Y14.47-2019 pdf free.Model Organization Practices.
4 SCHEMA FRAMEWORK OVERVIEW 4.1 General Most CAD software contains several tools for organizing product data. The framework in this Standard provides an organized formatwhen creating the productdata for ease ofuse and communication to downstream users and systems. Defining data in a consistent manner is necessary for the communication of shared data. 4.2 Defining a Data Set Using MBD The goal ofMBD is to provide complete productdefinition to downstream users and systems. This means all required engineering information is communicated from one source, the annotated model. Consistency is needed in the creation and presentation ofeach productto ensure information is communicated effectively. See Figure 4-1 foran example ofan annotated model in MBD. MBD is created with all information that facilitates model-specific information extraction, aids in navigating through model data, and provides for or facilitates efficient MBE that uses MBD for the life cycle of a product. Maintaining the integrity of model information is the responsibility of anyone who creates or revises the model. 4.3 Mapping Between Schemas Unless otherwise stated, aschemaotherthan the one defined bythis Standard maybe usedto organize the model data; however, all elements ofthe differing schema shall be mapped to schema elements defined by this Standard. A separate documentdefiningthese relationships and anydifferences shall be provided to the recipientofthe dataset. Each element shallhaveaone-to-one,one-to-many,ormany-to-onerelationshipwithanequivalentelementdefinedbythisStandard.If the data type (e.g., numeric, string) is different, thatshall also be documented so recipients ofthe data are clearlynotified of the difference. Furthermore, if any element is not used or if new elements are included, it shall be documented. 5 DATA SET COMPLETENESS STATES 5.1 General Adatasetmaycontainamodel orotheritems thatare atdifferentstates ofcompleteness. These states ofcompleteness may be documented in the data set. Whenthe completeness states are includedinthe dataset, thedatasetcompleteness states shall be keptas codes inthe critical metadata items for data set. Nonmandatory Appendix A provides application examples ofdata set completeness states. When used, data setcompleteness states shall consistofthree categories, each given a specific code thatdescribes the state of completeness for that category. The three categories are: maturity state, geometry state, and annotation and attribute state. Each category is defined as follows. 5.2 Maturity State The maturitystate describes the intended use ofa data setforthe productlife cycle. The maturitystate consists offour completeness levels: M1, M2, M3, and M4. M1 (conceptual): a data setthatis used when there is a need to verifypreliminarydesign and engineeringand to confirm thatthetechnologyis feasibleandthatthedesignconcepthas thepotentialto be usefulinmeetingaspecificrequirement. See Figure 5-1, illustration (a). M2(developmental): adatasetthatis used fortestingorexperimentationandforthe analytical evaluationofthe inherent ability of the design approach to attain the required performance. See Figure 5-1, illustration (b). M3(production): adatasetthatis used forthe commission, operation, service, anddecommissionofaproduct. See Figure 5-1, illustration (c). M4 (archive): a data set that is used to store the product information for preservation. 5.3 Geometry State The geometrystate describes thelevel ofdetailofthe iteminthemodel.ASME Y14.47 pdf download.