Technology Today 2006 Issue 3 - Raytheon

More documents

Recommendations

Info

Feature Continued from page 5 Reference Architectures, complimented with flexible and responsive M&S capabilities, are critical components to the Raytheon Enterprise Architecture Process (REAP). REAP was created to address both the needs of our customer and of Raytheon as a Mission System Integrator. The primary industry and government standards unified within REAP include the Department of Defense Architecture Framework (DoDAF), the Open Group Architecture Framework (TOGAF), the Zachman Framework for Enterprise Architecture, the Federal Enterprise Architecture Framework (FEAF), and the Software Engineering Institute’s Architecture Tradeoff Analysis Method (ATAM ® ). REAP is a systems architecting process extended with concepts and techniques to support enterprise architecting. Enterprise architecting is the interrelation and integration of business architectures and technical architectures. The business architecture models the enterprise’s mission, needs, strategies, goals, business rules, business processes, information flows and supporting organizational structure. The Technical Architecture models the technically focused architectural aspects of the system (e.g. data, applications, enabling technologies). Clearly, EMS is an integral need for both the business and technical architecture 4 . In addition, EMS is supporting commercial efforts to develop model-driven architectures (MDA) using Unified Modeling Language (UML) and System Modeling Language (SysML) through process/workflow modeling and logical model development support 5,6 . Systems Engineering, System Architecture Development, and Modeling and Simulation are tightly intertwined, as illustrated in Figure 2. The development of “executable models” is a key enabler for system design and implementation success using the iterative process depicted in the figure. EMS supports major contributions to: Operational, process and workflow modeling Logical architecture modeling Physical modeling System prototyping 6 2006 ISSUE 3 RAYTHEON TECHNOLOGY TODAY Raytheon Enterprise Architecture Process (REAP) Capabilities Database Integration and Test System Build Platform- Specific Model (PSM) DODAF Operational View Operational View (Use Cases, Threads) System Prototype, MS&A, Trades, CAIV Physical (Components, Integration Platform) DODAF Technical View In fact, as the acquisition process progresses, the system prototype evolves from high level M&S system model abstractions to an operationally representative prototype that includes hardware and human in-the-loop capabilities that significantly reduce program risk. An additional benefit is that components of the design prototype can be reused as part of an operational engineering testbed. The engineering testbed becomes a key operational component for: Operational performance/capacity analysis Operational planning and scheduling Support for operational anomaly resolution Realistic hands-on operator training New HW/SW verification and validation Proof of concept technology insertion Since this operational engineering testbed is an evolutionary extension of the system prototype, significant cost savings, schedule compression and risk reduction benefits are realized through the extensive reuse of verified, validated and accredited components (VV&A). EMS Process EMS is not simply an integration of Raytheon’s world-class M&S components. More importantly, EMS encompasses a process that ensures responsive, low-cost solutions. This process is shown in Figure 3. Platform-Independent Model (PIM) Objective Architecture Logical View (Class/Sequence/ Diagrams, SOA) DODAF System View One Architecture/EMS Strategy Enterprise Modeling and Simulation (EMS) Operational, Process and Workflow Modeling Logical Architecture Modeling Physical Modeling Figure 2. EMS is an integral component of the systems engineering/architecture process. The left-hand side of Figure 3 shows the Systems of Elements TM where Raytheon possesses full spectrum high-fidelity M&S components. The gray box encompasses the process for integrating and deploying those capabilities in a responsive cost-efficient fashion to solve customer problems. The implementation of these broad-based legacy and contemporary M&S capabilities requires a simulation architecture that facilitates the interoperability between legacy infrastructures using distributed interactive simulation and high-level architecture backbones with commercial solutions, such as Java TM messaging services and other web service implementations, such as serviceoriented architectures and high transaction rate protocols. EMS has demonstrated this full-scale integration capability through the deployment of a number of modeling and simulation experiments, referred to as Raytheon Distributed Experiments (Ray DX ). With a variety of components, or federates composing a simulation or a simulation federation, Simulation Control is a critical component to successful execution. The ability to add or delete components or federates on the fly, display simulation status, provide time management, and control data acquisition with a single control con-
Sensors and their platforms C 2 data processing Communications BMC 3 planning and control Weapons and their platforms EMS Simulation architecture • Companywide standard interface Uses tactical message formats Operates over ORION Figure 3. Comprehensive EMS deployment process sole is vital to successful M&S experimentation. Effective Simulation Control is also necessary when distributed simulations are executed from multiple geographically separated sites. A single seat simulation control integrates multiple simulations into an effective end-to-end simulation, analysis and visualization capability that allows experiments to be run from any Raytheon site with access to ORION or over the Internet via virtual private networks. To be effective, a simulation must provide problem understanding and decision quality information to end users. To this end, EMS has developed a design of experiments approach that clearly codifies and documents scenarios, available system resources and relevant MOE/MOP/KPPs for each experiment. The resulting experiments provide decision quality information that allows key leadership personnel to make architectural and system decisions based on data, facts and figures. In addition, extensive visualization displays are generated to facilitate an increased understanding of the executed experiments. The visualizations are critical to enhancing communications and understanding between decision makers, designers and end users. Visualization Simulation control Design of experiments Simulation repository Single and multiple display operation Remote viewing anywhere in Raytheon using ORION External viewing at customer site Single person semi-automatic control Supportive live demonstrations Facilities integration and test Scenario Tailorable ConOps Flexible architecture compositions MOE/MOP/KPP Change Control Board Architecture process Standards Reusable simulations and data EMS maintains a simulation repository that archives existing models, scenarios, experiments, measures of effectiveness/performance (MOE/Ps), and key performance parameters. This repository facilitates reuse and leads to shorter development times with lower costs. EMS Value Proposition Raytheon’s future growth lies with developing NoDoubt solutions and implementations to customer challenges. Raytheon is migrating from being a system provider (radars, missiles, EW, radios) to a system-of-systems provider. This requires a companywide synergistic approach with Mission Systems Integration (MSI) and Mission Assurance strategy leading the way. Successful MSI and Mission Assurance are built upon the successful deployment of proven system architectures and time-tested systems engineering methodologies. Underpinning this successful deployment is a comprehensive approach to M&S. An evolutionary development of system M&S across the system-of-systems life cycle ensures the following benefits. Enhanced Communication/ Understanding – The development of system models enforces collaboration among end users, acquisition professionals and system designer/developers. While architectural artifacts (DoDAF or otherwise) provide documentation and a communication vehicle, executable models exercise these artifacts and drive model verification, validation and accreditation. Invariably, models and their execution lead to new questions addressing system requirements and deployments. Executable models provide visualizations and data to support concepts of operations, requirements validation, data content and flow (routing/distribution) identification, and interface requirements. All of these are critical to facilitating the understanding achieved across all communities of interest. Risk Reduction – Early and comprehensive VV&A of executable models is key to achieving overall system success. A VV&A integrated product team consisting of all discipline functionalities and representing all communities of interest is vital to ensuring that executable models address appropriate concerns and appropriately represent the desired system. Early executable models are extended and enhanced with additional functionalities and details. Continuous VV&A leads to results that are dependable and accurately represent system performance. Continuous executable model enhancement combined with continuous VV&A reduces risk throughout the life-cycle development. Cost/Schedule Savings – The reuse of executable models that have undergone continuous VV&A leads to high-fidelity system prototypes. Operationally representative system prototypes reduce cost and support schedule compression with reduced test and evaluation efforts, rapid training development, faster HW/SW validation and accelerated operational testbed deployment. Daniel Gleason dgleason@raytheon.com 1 Technology Today, Volume 3, Issue 2. 2 Leadership Perspective, Technology Today, Volume 3, Issue 2, pg. 24. 3 Technology Today, 2006, Issue 1. 4 Raytheon Enterprise Architecture Process, Revision F, Document No. 416-15683, May 2005. 5 “Mission Assurance and the UML Profile for DoDAF/MoDAF (UPDM),” Technology Today, 2006, Issue 1, pgs. 18-19. 6 “System Modeling Languages (SysML) and Mission Assurance,” Technology Today, 2006, Issue 1, pgs. 6-7. RAYTHEON TECHNOLOGY TODAY 2006 ISSUE 3 7
Page 1 and 2: Technology Today HIGHLIGHTING RAYTH
Page 3 and 4: Technology Today is published quart
Page 5: Raytheon’s One Architecture/ EMS
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 and 20: naval surface and sub-surface traff
Page 21 and 22: Figure 2. When adopted at the start
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?