Digital standards enable a user to pull data and requirements from a standard into the tools they use to develop their products. Whether it is a requirements-tracking system, a model-based simulation tool, or some other tool used during the product life cycle. The data is referenceable and reusable to support multiple use cases.
Digital transformation is changing how standards are written. Existing documents do not always translate into a digital database. Problems can arise with sentence structure, table layouts and variable naming. When writing standards, authors should consider how documents are searched and retrieved – not just how they are read. Watch our prerecorded webinar to learn more about writing digital-ready standards. Presented by Leslie McKay, Senior Product Manager at SAE International and Uxue Zurutuza, Senior Data Scientist at Cognistx.
How to Write a Digital-Ready Standard
In the first webinar, Leslie McKay, a Senior Product Manager at SAE International, talks about how industry standards must evolve so that they can be more easily integrated within a product’s digital thread. New products need to be designed and tested to meet requirements from several sources—industry standards, internal standards, customer requirements, market requirements, etc. PDFs do not provide the digital interoperability required to fit into this new product development environment. This webinar shows how digital standards can be used throughout the product development lifecycle to reduce product development costs and timelines, increase innovation across engineering disciplines, and maintain high standards of quality.
Part two of the three-part series is led by Aleczander Jackson, founder and CEO of Enola Technologies. Aleczander discusses how accessing standards from a reusable requirements database eliminates the time and effort required to parse a standard from a PDF, which can take up to 35 hours per standard. Digitization into compliant system architectures enables you to capture the behavioral aspects of systems and pull the parametric constraints from digital standards to validate that system architectures are compliant with the standards prior to moving to detailed design.
Aleczander shares a MBSE sample model package (leveraging SysML), created in Catia System of Systems Architect tool, that he demonstrates in this webinar so that users can how the validates adherence to the SAE AS5669A standard.
Part three is led by Saulius Pavalkis of Dassault Systèmes. Saulius focuses on the transition from digital standards in MBSE to a full model-based engineering solution, covering model-based design, analysis and validation and verification for certification. Saulius demonstrates the latest in MBSE and engineering ecosystem for requirements management, baseline, traceability, and 3DCAD.
Summary of DoD Instruction 50000.97