1. Eric Bryant Joe Brooks Matt Delgadillo

2.  The RCT is a mobile training platform designed in response to the need for modular and interactive training resources that can reduce costs associated with facilitating multiple training efforts by providing reusable system resources, (racks, power, sensors, cooling, etc), within configurable modules that are built from specified system requirements. The 30-foot RCT will be positioned at various key locations of the working facility based on scheduled training sessions to provide a fully functional customer training environment while alleviating certain space limitations that a host facility may have.

3.  1) Versatility – Simulation training areas typically have one customer using its resource at one time which often causes other equally important customers to either wait to have their employees trained on new technology or they are forced to “learn as they go”.  2) Replacement Cost – History has proven that when the simulation space becomes vacant and a new customer is set to inhabit the area there is a delay which costs the company money for every day the area stays vacant and when a customer assumes ownership of the space then replacement of non modular system components must be undertaken.  3) Inventory Management – Every respectable company wants to offer their clients the greatest variety of products possible. However, the degree of complexity of inventory management grows proportionately with the number of products that the customer requests. This problem becomes more serious just before delivery when the logistics of keeping track of spare items going to/from the plane becomes a nightmare.  4) Ease of meeting and exceeding client expectations – Modular training facilities allow you to meet the demands of any customer. You can use modular training facilities to utilize the same basic components to create varied looks for a truly unique training experience.  5) Economical Storage, Shipment and Assembly – Unique module combinations really make reconfiguring simpler due to several components that can be easily disassembled and packed tightly into a storage trailer or used on another platform.

4.  Short development efforts ◦ Training Material ◦ Facilities Layout  Self Contained  Mobile  Customizable  Easy Installation  Determinate Size – Scalable  Limited Facility Impact

5. Proactive  Power Requirements  Cooling Requirements  Different Mounting Systems  Easy Software Integration  Repair-ability  Number of Operators  Known Security Threats  Various Languages  Various Configurations  Known Knowledge Bases

6. Reactive  New Sensor Sets/Requirements  Vendor LRU Revisions  Maintainability (Broken LRU’S)  New Security Threats  Unknown Knowledge Bases  User Schedule Requirements  Road Accidents and Nature Events

7. Correction Variation Reconfigu- ration Expansion (and Contraction of Capacity) Migration Improvement Modification (Add/Sub Capability) Creation (and Elimination) Proactive Reactive Change Domain Training cycle time Hardware and software integration Cost Efficiency Creates individual system modules (what are the individual things the system needs to create)? Creates vehicle mounts (what does employers need to create?) Creates training plans Creates system backbone (power, cooling) Facility layout Vendor Requirements Sensor and LRU obsolescence (modifications) New platforms and technology Packing factors Cooling and power routing Software integration Structural reinforcement Component failures (What process can break? What in the system activities can break? (bad plan) New security attacks (high level things that impair the system to respond to customer) Power/cooling loss Extreme damage Type of sensors Location of service Customer requirements Infinite scalability (must give a range) Mass production Data storage Multi language users Number of operators Schedule changes Change/Response Issue Environmental aspects Cyber attacks Maintenance time and cost

8. Encapsulated Modules LRU Racks Operator Seats Sensor Mounts Training Plans Power Distribution Boxes Cooling Distribution Lines Security Module User Stations Cockpit Operators – (not pilot) Evolving Infrastructure Standards Sockets Standard Rack Spacing (1.75 inch, 1U) Rack Slides/internal mounts Seat/rack attachment to floor Electrical Interface standards/code Signals Sensor ICD’s Training Curriculum Security Crypto Standards Safety Human factor regulations Service Training Certification Standards Scalable Reusable (Think … Drag-and-Drop / Plug-and-Play)

9. Racks Cooling Lines User StationsPower Boxes Training PlansSensor Payloads Infrastructure evolution System assembly Module mix evolution Module inventory readiness Infrastructure Sensor Operator Trainer Mission Commander TrainerPilot Trainer Components/Modules Rules/Standards Integrity Management Active Passive Sockets Signals Security Safety Service RCT Project Engineer Design Engineer Manager Program Manager RCT System Engineer Rack size std, Seat track std, Pwr Codes RF/Video std, Training Curriculum, LAN network Crypto standards Human factor regs Min Training Completion Requirements

10. Reconfigurable Scalable Reusable Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure. Power Management Cooling Mounting Training Program User Station Sensors Attachment Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal. Seat track attachments Slotted racks Standard installations (inside racks and outside) Defined connectors Standard operating system GUI Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules. Basic Training plan template (modular) Defined interface control (swappable between RCT units) Common Sensor Mounts mix/match to customer requirements Peer-Peer Interaction Modules communicate directly on a peer-to- peer relationship; parallel rather than sequential relationships are favored. Trainer teaching the trainee Software integration between modules (ICD/defined data packets) Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary. New configurations/capability added when purchased by customer Modules not purchase/develop until ordered (just in time) Defer material procurement (use just in time) Evolving Infrastructure Standards Module interface and interaction standards and rules that evolve slowly. Standard Rack Spacing Seat Attachments Internal Rack Attachments Electrical interface standards Human factors standards Crypto standards Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options. Basic rack design, different sizes Universal installations (actual container and inside racks) Opportunities for spare modules Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure. Number of operators adjustable (1-6) Sensors adjusted to training needs (add/sub capability) Cooling and power adjustable to component needs # of Training plans unlimited Unlimited System Scalability (multiple RCT units) Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Inventory requests for parts supplied to system Remote connection between multiple trainers/trainer types Security network controls distribution of info Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated. Software determines how sensor modules communicate (LAN) Regulated firmware updates and maintenance (autonomous) Automatic controls (temp, power, mechanical)

11. Reality Factors Organizational Behavior – Survival rules rule, nobody's in absolute control... Schedule for quick reconfiguration can put small budgets at risk. Internal system advisory bulletins not communicated throughout organization causing further damage. Organizational installation standards prohibit correct or new sensor integration and modularity. Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance... Repetitive component builds/installations can lead to complacency in assembly lines and component damage during manufacturing Customer may not follow system limitations causing damage to simulator (power up process). Customer may use system for unintended use (playing war games) Customer expectations exceed system capabilities Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing... New sensor installs beyond the skills of current workforce. New development of sensors can slow down new product/configuration offerings. Time to develop proven training for new technologies conflicts with schedules. System Complexity – Incomprehensible, highly networked, unintended consequences, emergence... Integration of more systems causes known and reliable systems to fail. Writing software becomes more difficult and timely. Understanding of installation tolerances leads to failed systems. Unnecessary software or hardware capabilities cause systems to be more complex than needed. Globalization – Partners with different ethics, values, infrastructures, cultural assumptions... User interfaces in different cultures or countries can vary. Varying cultural schedules/holidays. Different cultures learn/train in different ways. Language barriers can cause software to become hard to incorporate. Other? ? Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative... Customer requirements can change Competition ghosts the product to undercut price and capabilities Conflicts of interest with sensor manufacturer and user Customer requirements bound solution (can’t be agile) Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects... Using COTS can alter functionality if obsolescence occurs Using subcontractors to develop systems Product transparency can lead to proprietary information leaks. Policies and procedures cause inefficiencies in manufacturing.

12. Easy installation Self Contained Mobile Short development efforts Customizable Scalable Uses modular racks Uses separately designed system modules Installed on common platform Proprietary SW package Shortened procurement and dev of mounts Uses LRU based Arch Uses std 18 wheeled fleet Limited Facility Impact Uses std generator power Uses std physical connection s

13. Frequent Audits High Quality data releases Configuration Control Change Management Configuration Identification Streamlined Process Check part numbers and SW version Incorporate all documented SW fixes Remove/Return obsolescent items Formal CCB guidance SW labeling conventions Limited use of SIL space Joseph Brooks

14. Proven, tested and Qualified Working Groups Simultaneous Peer CAD Design And drafting Uses Open working environment QuickReaction On the job Shadowing Plans of other SME’s Instantaneous Project progress DiverseKnowledgeBase High Quality Engineering (Low Error Rates) SubjectMatterExperts Matthew Delgadillo Self Driven and Motivated Uses Real Time Notifications To detect design Issues /Conflicts Scalable Group sizes And number Of groups

15. Accurate Solid Model agile Mechanical design Automatic solid model generation Leverages Existing Efforts Intuitive Clean GUI Reliable Initial ScheduleEstimate Searchable Database Suggests most similar to for new modular schedules Interference Detection Multi-PlatformCapability Low Cost Quick Concept Turnaround Easy to Use byInexperiencedEngineer Strategic Values/Objectives Functional Activity Strategic Activity ConOps Web