1. Standardization Power Christopher Loeser Distribution Statement A: Approved for Public Release

2. Why Specs / Stds? • Document proven solutions to engineering problems. • Don’t have to re-develop requirements, design details • Represents results of years of RDT&E, operating experience and lessons learned • Enable predictable design and construction size, cost and schedule • Key to design integration • Essential for open architectures and modularity

3. Intermodal Container Standard • Prior to 1968 various shipping companies used incompatible containers • Mattson: 24 foot • Sea-Land Services: 35 foot • Standardization required years of effort among many stakeholders • ISO R-668 January 1968 – Terminology, dimensions, ratings • ISO R-790 July 1968 – Markings • ISO R-1161 January 1970 – Corner fittings • ISO R-1897 October 1970 – minimum internal dimensions • Stakeholders: International shipping companies, European and US railroads and US trucking companies. • Result: 90% of all non-bulk cargo worldwide moves by containers.

4. Standardization Effects • Pros: • Increased efficiency of design, construction, transportation • Costs of increased total system size offset by efficiencies • Increases supply of standardized items • Manufacturers confident in market • Competition lowers prices • Enhances innovation • Combinations and permutations of standard parts • Alternate uses: e.g., multiple and innovative uses for USB standard interface • Cons • Generally increases total system size • Acquisition community may invoke standards without tailoring or full understanding • Continuing maintenance process needed to keep pace with technology

5. Attributes for Standards • Articulated • Text • Drawings • Technically Validated and Refined • Performance validated by testing and full scale experience • Interfaces known / stated • Consensus reached among stakeholders • Programmatically Acceptable • Cost • Producibility • Life cycle (costs, maintenance, service life)

6. Technical Architecture • The underlying set of standards applicable to a given product • Design • Structural • Mechanical • Fluids • Interfaces • Environment • Production • Quality • Fabrication processes • Certification • Testing • Analysis • Demonstration • Inspection

7. Who Uses Technical Architectures • Developed by groups that develop, manufacture and regulate the product • Aviation • Automotive • Rail • Construction machines • Marine • Communications • Computing • Biotechnology • Successful companies have develop own formal technical architectures

8. Technical Architecture Design Construction Certification • Parametric estimating relationships • Design calculations • Design criteria • Design process • System and subsystem architectures • Piece-part standards • Fabrication processes (welding, painting, running cable, piping installation, insulation installation) • Quality methods • Cert criteria • Test methods • Based on a given product’s: • Operational requirements: Performance, survivability, HSI, life cycle, • Operating environment: External (salt, temperature, wind, precipitation, seaway), self induced (vibration, EMI), regulatory • Concept of operations: Standard operating methods, training, logistics

9. VALIDATE AND REFINE TECH ARCH • SYSTEM / SUBSYSTEM ARCHITECTURAL STANDARDS • STRUCTURAL • CENTER OF GRAVITY • ARRANGEMENT • INTERFACES • MARGINS • COMPONENT STANDARDS • PIPE • VALVES • PIPE HANGERS • CABLE TYPES • CABLE BEND RADIUS • CABLE HANGERS • FOUNDATION DESIGN METHODS • STRUCTURAL DETAILS • INTERFACES CONCEPT PRELIMINARY • FABRICATION STANDARDS • PIPE SYSTEM ASSEMBLY • CABLE PLANT ASSEMBLY • MECHANICAL ASSEMBLY • WELDING AND FASTENERS • INTERFACES • QUALITY METHODS • CONCEPT DESIGN STANDARDS • WEIGHT RELATIONSHIPS • VOLUME RELATIONSHIPS • COST RELATIONSHIPS • SYSTEM AND SUBSYSTEM CONFIGURATIONS DETAIL PRODUCTION ESTABLISH / REFINE STANDARDS / RDT&E • RETURNED: • WEIGHTS • COSTS • PERFORMACE

10. NEW DEVELOPMENTS • New developments based on technology transformation depend on full understanding of the technical architecture • Identify differences early in development • Plan to fully vet new standards prior to detail design • Analysis • Model tests • Full scale testing • Focus on compatibility with basic technical architecture

11. SUMMARY • Specs and standards ensure predictable and cost effective solutions to requirements • Represents results of years of RDT&E, operating experience and lessons learned • Technical architectures are the collection of related specs and standards • They enable effective design integration • They can foster successful technology transformation