Downloaded from https://www.everyspec.com MIL-STD-31000A APPENDIX B B.3 SCHEMA ARCHITECTURE OVERVIEW. Modern CAD software contains several tools for organizing product data. This schema uses the organizational elements listed below to format the product data for ease of viewing by downstream users. Utilizing these tools in a consistent manner provides the foundation for consistent data sharing by downstream users. Defining data in a consistent manner is necessary for successful extraction to light weight viewers used for viewing shared data. views may be saved to quickly navigate through all the required product definition data.
Combination Views are used to combine multiple model display states. Multiple combination View States are used to manage the orientation position of the product that best presents the product definition details. They can include the following display options: orientation, model cross-sections, model display style, simplified representations of the model, and assembly exploded displays. Logical Groups are used to manage the display of annotation data and support definition for combination views. Examples in use by CAD software are layers and groups. geometry. They may include both dimensional types and note types. Annotations are used to provide complete product definition.
Annotations are a graphic or semantic text entity created to store model information without Notes are used to capture supplemental data related to the model. This includes General Notes and other notes associated to the model. Additional notes will be created to support data previously displayed on the 2D drawing. Meta Data is data that supports the definition, administrative or supplemental data package. Metadata includes all relations, parameters and system information used in a model. This data resides at the model and feature level. Throughout this document standard naming conventions will be used for the various organizational elements.
This will allow for future expansion of other model based venues. B.4 SOLID MODELING PHILOSOPHY. The goal of a solid model is to create and provide all design and detailed information, including design intent, to downstream users. This means all the required engineering information is communicated to everyone from one source, the Solid Model. In order for this communication to be effective, consistency is needed in the creation and presentation of each product. Models are created using “start models” to ensure that “start model information” is present.
Using a start part ensures a common beginning for all models, facilitates model specific information extraction, aids navigating thru model data, and sets you up for efficient MBD creation. Maintaining the integrity of model information is the responsibility of all engineers/designers and anyone else who may add or change the model during its creation and revision. All start part models should contain the following organizational elements to accommodate MBD: Standard MBD Combination Views Supporting MBD View States Supporting MBD Logical Groups Required MBD Notes Required MBD Metadata 37