Technology Today 2006 Issue 3 - Raytheon

More documents

Recommendations

Info

onTechnology Simulation Based Acquisition as Part of Enterprise Modeling and Simulation Simulation Based Acquisition (SBA) is a strategic development method based on sound systems architecting principles that applies modeling and simulation to all the phases of a weapon system’s life cycle: requirements generation, concept development, design, build, test, operation and adaptation. The method uses modeling and simulation to provide an early, virtual prototyping environment and a common frame of reference for developers, analysts, end-users and managers. Requirements and performance are addressed as early as possible in development. The parallels between Simulation Based Acquisition and systems architecting can be shown with some definitions from literature. Note: Italicized words and numbers within the following boxed paragraphs concerning working definitions of systems architecture and Simulation Based Acquisition, are used in conjunction with Figure 1 to illustrate the parallels between the two. A good working definition of systems architecture is as follows 1 : “An architecture is the set of information (1) that defines a systems value (2), cost (3), and risk (4) sufficiently for the purposes of the systems sponsor (5).” Conversely, a good working definition of Simulation Based Acquisition (SBA) can be found in the Defense Systems Management College publication, Simulation Based Acquisition: A New Approach 2 : 20 2006 ISSUE 3 RAYTHEON TECHNOLOGY TODAY ARCHITECTURE & SYSTEMS INTEGRATION “SBA is about using simulation (1) to explore the design space, to validate (4) designs, and to verify (4) that the proposed design will meet (2) the end-user’s (5) expectations (2) and is manufacturable, supportable, and affordable (3).” The parallels between these two definitions help to show how Simulation Based Acquisition is related to systems architecting. These parallels are depicted in Figure 1. Systems Architecture 1) information 2) value 3) cost 4) risk 5) systems sponsor The Benefits of Simulation Based Acquisition The benefits of Simulation Based Acquisition are to facilitate early reduction of cost, risk and uncertainty, while at the same time increasing confidence. It follows from adoption of an iterative development process that fosters an environment of using incremental building and testing. Risks are addressed early, exposed consistently and visited regularly. In addition, customers and end users can develop a good feel for the product’s endstate by getting previews of the end-state in a piecemeal fashion. This is done through smart application of modeling and simulation to provide an early, virtual prototyping environment of the system and a common communication tool for developers, analysts, end users and managers. Figure 2 compares development “With SBA” versus development “Without SBA,” showing how progress, risk, confidence and cost are affected. Figure 2 shows how Simulation Based Acquisition facilitates early and regular mitigation of cost, risk and uncertainty, while at the same time it steadily increases confidence throughout development. Note that at the integration point of development, progress and confidence actually decrease without Simulation Based Acquisition. This is because many of the risks and issues that Simulation Based Acquisition as a Systems Architecture Simulation Based Acquisition 1) simulation 2) meet ... expectations 3) affordable 4) validate and verify 5) end-user Figure 1. The parallels between Simulation Based Acquisition and systems architecting. The numbered words correspond to the italicized numbered words in the definitions given in the previous paragraphs for systems architecture and Simulation Based Acquisition. would have been discovered early by the incremental development aspect of Simulation Based Acquisition lie dormant until the software and hardware pieces join together in the integration phase. The Spiral Development Aspect of Simulation Based Acquisition In an ideal application of Simulation Based Acquisition, simulations extend from lowfidelity aggregate models to detailed engineering prototypes. United Defense Limited Partnership calls this Simulate, Emulate, Stimulate4 . This fits well with the concept of spiral development. This spiral nature is shown in Figure 3. YESTERDAY…TODAY…TOMORROW
Figure 2. When adopted at the start of development, Simulation Based Acquisition reduces cost, risk and uncertainty, while at the same time it increases confidence. Without Simulation Based Acquisition, risk is carried longer, progress falters at integration, and the slope of the cost curve increases late in the development cycle 3 . Figure 3 shows how simulation fidelity keeps pace with system design maturity. Through the development cycle — design, test, analyze and revise — the spiral ascends as design maturity increases. Along the spiral, the simulation’s fidelity increases as it tightens along the vertical axis. When the spiral is low and wide, design maturity and simulation fidelity are both low. When the spiral is high and tight, design maturity and simulation fidelity have both increased. Simulation models are developed in parallel with the hardware and software to allow developers, analysts and end users to regularly refine system requirements and analyze performance. Involvement of the end users allows them to be an integral part of Figure 3. United Defense Limited Partnership’s Simulate, Emulate, Stimulate concept illustrates how simulation fidelity keeps pace with the system’s maturity. the design process. The common framework allows the program’s technical lead to establish a level playing field for consistent comparisons among alternative concepts and designs. The Elements of Simulation Based Acquisition From a verification and validation perspective, Simulation Based Acquisition makes use of three elements that interplay to produce natural validation points. In the missile business, the three elements are: i) integrated flight simulation (IFS), ii) processor-inthe-loop (PIL) and iii) hardware-in-the-loop (HIL or HWIL). IFS, sometimes called a 6-DOF simulation (six degrees of freedom), is typically the first step along a program’s simulation path. At this first step, digital models are run with early versions of embedded code at low fidelity on a computer platform. PIL, sometimes called a CIL (computer-in-the-loop), involves emulating or prototyping the processors that eventually end up in the final product. Real embedded code is run in real time on representative hardware. And finally, HIL brings as much real hardware into the simulation as possible. For some programs, such as a tactical missile, this might involve the missile airframe and seeker interfaced with rotary tables and scene projectors. The pieces and the interrelation are shown by the Venn Diagram 5 in Figure 4. It is YESTERDAY…TODAY…TOMORROW Hardware in the Loop Processor in the Loop Integrated Flight Sim Figure 4. The Venn Diagram shows the interrelation of three important elements to Simulation Based Acquisition. The overlapping areas are key to simulation validation. important to note that the overlapping sections of the circles are natural validation points for one simulation against another. Flight tests provide yet another validation anchor point, and are particularly efficient in the area where all three circles overlap. Conclusion By adopting the concepts of Simulation Based Acquisition — making use of modeling and simulation, and following an iterative development process of incremental build and test — programs can reduce cost, risk and uncertainty early on, thereby increasing confidence. End users and developers can use the models and simulations of Simulation Based Acquisition as communication tools to provide early course correction. Saving cost, managing risk, reducing uncertainty and increasing confidence in the system are all key aspects of a successful systems architecture, something that is certainly relevant in today’s competitive business environment. Jeff Wolske jswolske@raytheon.com 1 Maier and Rechtin (2002). The Art of Systems Architecting. Florida: CRC Press. 2 Lt. Col. M. V. R. Johnson, Sr.; Lt. Col. M. F. McKeon; Lt. Col. T. R. Szanto (1998). Simulation Based Acquisition: A New Approach. Defense Systems Management College Press, Virginia. 3 Adapted from: Booch, Jacobson and Rumbaugh (1999). The Unified Software Development Process. Boston: Addison-Wesley. 4 Adapted from: Lt. Col. M. V. R. Johnson, Sr., Lt. Col. M. F. McKeon, Lt. Col. T. R. Szanto (1998). Simulation Based Acquisition: A New Approach. Defense Systems Management College Press, Virginia. 5 Adapted from personal communication with Jeff Lucas; Aviation and Missile Research, Development and Engineering Center; System Simulation Development Directorate, April 2006. RAYTHEON TECHNOLOGY TODAY 2006 ISSUE 3 21
Page 1 and 2: Technology Today HIGHLIGHTING RAYTH
Page 3 and 4: Technology Today is published quart
Page 5 and 6: Raytheon’s One Architecture/ EMS
Page 7 and 8: Sensors and their platforms C 2 dat
Page 9 and 10: Over 44 models and simulations from
Page 11 and 12: - A/GMTI Communications - Link avai
Page 13 and 14: Networked Sensing Devices Part of t
Page 15 and 16: CiscoVPN client from anywhere in th
Page 17 and 18: ExCon Server ExCon Web Page Figure
Page 19: naval surface and sub-surface traff
Page 23 and 24: Figure 2. Sample engagement. A clos
Page 25 and 26: onTechnology The conceptual design
Page 27 and 28: Events Technology Integration Week
Page 29 and 30: Congratulations to the 2005 Excelle
Page 31 and 32: Events The Farnborough Air Show Mis
Page 33 and 34: differentiating between alerts caus
Page 35 and 36: Supplier Rating System team 2005 Qu
Page 37 and 38: Help Students get Back 2 Math Rayth
Page 39 and 40: VERNON R. GOODMAN TIMOTHY R. HOLZHE

Technology Today 2006 Issue 3 - Raytheon

Create successful ePaper yourself

Delete template?

Save as template?