PRODUCT SUPPORT
and use cases) and include gov - ernment reference architectures and digital system models. 2. In place of drawings, 3D CAD models are used for product defi - nition and include native, neutral, or Standard for the Exchange of Product Data formats. Native for - mats include industry-owned and -managed formats such as CATIA, Creo, NX, Solidworks, AutoCAD, etc. Formats vary widely by Ser - vice, program, and original equip - ment manufacturers (OEMs)—and DoW has not established a prefer - ence for any specific vendor tools or formats (although individual Services or commands have). 3. Point cloud models, produced by scanning technologies such as light detection and ranging or lasers, create a pixelated but highly accurate (within a few mil - limeters) model that can serve as an intermediate step toward a solid geometry CAD model. Oth - er scans result in digital mockups or manufacturing quality models. 4. Mathematical models and Dis - crete Event Simulations (DES) op - erationalize the dynamic aspect of models for predicting behav - ior of complex systems. These can
be implemented in spreadsheets, databases, or sophisticated soft - ware applications requiring high- performance computing labs. The above model types can fur - ther be classified as “Descriptive” or “Analytical-Computational.” CAD and point cloud models generally fit into the descriptive category. Math - ematical models, DES, and other physics-based modeling such as com - putational fluid dynamics and finite element analysis, fit into the analyt - ical-computational category. Graphi - cal modeling languages, including some simulation capabilities, fit into both categories. Offering sound ad - vice for practitioners, MBSE expert Ryan Naguchi said, “Regardless of category, employ a virtuous cycle, where models are highly valued, fre - quently used, and maintained.” Digital Product Support in Action Beyond approaches and terminol - ogy, what about “actionable results?” This section, organized by the 12 in - tegrated product support elements, provides concrete examples in use today by DoW programs. Product support management. The Army’s Future Long-Range As -
sault Aircraft (FLRAA) program built a DES that enabled trade studies to “dial in” their optimum PSS. For ex - ample, the DES enabled identification of line replaceable units for which it made best sense to pursue robust in - tellectual property rights for organic or competed depot repair. The Air Force’s Logistics Composite Model Analysis Toolkit is another DES ca - pable of informing a program’s re - liability, availability, maintainabil - ity, and cost, including establishing confidence levels for setting realistic objectives and thresholds. Model- based T&E, including supportability T&E, can reduce the required physical testing and help programs fix poten - tial problems early in development before designs and high costs are locked in. Design interface. A model-based Human Engineering Design Approach Document-Maintainer (Data Item De - scription DI-HFAC-80747), prepared by the OEM, can assist the PSM and maintenance subject-matter experts in evaluating maintainability (e.g., ac - cess, component removal and instal - lation, and servicing) across the range of maintainer anthropometric classes. For example, maintainers evalu - ated the Air Force’s B-52 Commercial
JANUARY FEBRUARY 2026 | DEFENSE ACQUISITION MAGAZINE 29 –
Made with FlippingBook - Online Brochure Maker