1. Team Name: Team 1 Modular Test Unit (MTU)
Mike Morell, Zac Fisher, Tony Busby, Brandon Miller

2. STRATEGIC VALUES / OBJECTIVES
Portable
Universal connectivity
Capable of interfacing w/ multiple platforms
Rapid reconfiguration
Adaptable with minor modification
DESCRIPTIVE STATEMENT
The MTU is a mobile testing unit that allows for verification and validation of multiple aircraft system. This unit will be rapidly configurable using a multi-band antenna array to support multiple aircraft platforms. The MTU will use MIL standardized input power disconnects and rack configuration to ensure that the MTU will be ready to accommodate customer needs.

3. CURVE System/Process Environment
Capriciousness – unknowable situations
Software incompatibilities (reactive)
Design system to be adaptable to changes in “universal” standards (proactive)
Uncertainty – randomness with unknowable probabilities
Weather conditions (reactive)
Equip MTU with Solar Cells to take advantage of environmental conditions (proactive)
Risk – Randomness with knowable probabilities
Plan site location to ensure surplus of parts and storage, and rapid delivery of parts (proactive)
Operator error during configuration change (reactive)
Variation – Knowable variables and variance range
Real estate constraints to support many configurations (proactive)
Scheduling constraints for resources (reactive)
Evolution – gradual (relatively) successive developments
Software and hardware upgrades to keep pace with technology/standard changes (proactive)
Purchase new testing equipment as it becomes available, even if not currently necessary for use with the MTU (proactive)
System security patches (reactive)

4. Reality Factors Human Behavior Organizational Behavior Technology Pace
Fatigue
Configure system for incorrect platform requirements
Security issues, sending wrong classification of data to aircraft
Organizational Behavior
Pressure from management induces errors
Prioritization of resource availability
Poor quality assurance processes
Technology Pace
Complications of software compatibility
Insufficient time to fully verify system prior to deployment
System Complexity
Too many variables between tested system and final
Highly trained personnel required

5. Reality Factors (continued)
Globalization
Deployment location legal constraints
Language differences
Partially-Agile Enterprise Faddish Practices
Using COTS
Reliance on existing infrastructure (i.e., internet availability, network design)
Agile Customers / Competitors / Adversaries
Customer will require and expect adaptability
Protection from spies and adversaries
Other

6. RS Analysis for MTU PROACTIVE REACTIVE Creation (and elimination)
Eliminate unnecessary parts [c, p, s]
Specialized teams [p, s]
Improvement
Decreased configuration time [t, c]
Increased team effectiveness [t, c]
Migration
Update to upcoming technology [p]
Increased training & certification [p, s]
Modification (Add/Sub Capability)
Upgrade to new aircraft platforms [p, s]
Increased environmental suitability [p]
REACTIVE
Correction
Hardware incompatibility [s]
Test outcomes [s]
Variation
Manpower demand [c, t]
Skill level [c, t]
Expansion (and Contraction) of Capacity
Real estate and resources [s, c]
New antenna types [s, c, p]
Reconfiguration
Requirements changes [c, t, s]

7. System: MTU (Think … Drag-and-Drop / Plug-and-Play)
Encapsulated Modules
Servers
Racks
Conex
Power Disconnects
LRUs
Scalable
Reusable
Evolving Infrastructure Standards
Sockets:
Power
LAN
Patch Panels
Signals:
Data Bus (429, 1553, 422, etc.)
Power & Control
Security:
Aircraft Platform to MTU
Quality
Configuration Management
Safety:
Conex Design
Overload Protection
Service:
First Article Test Plan & Procedure
Periodic Software Updates
sockets (physical interconnect)
signals (data/stuff flow between modules)
security (trust interconnect)
safety (of user, system, and environment)
service (system assembly ConOps and evolutionary agility sustainment)

8. RRS Principles for the MTU
(Think: Plug-and-Play, Drag-and-drop)
Reconfigurable
Scalable
Reusable
Encapsulated Modules Modules are encapsulated independent units loosely coupled through the passive infrastructure.
-Servers -LRUs
-Racks
-Conex
-Power Disconnects
Evolving Infrastructure ConOps and module interface and interaction standards that evolve slowly.
-Power standards
-Communication / signal protocols
Facilitated Interfacing (Pluggable) Modules & infrastructure have features facilitating easy module insertion/removal.
-Power interface
-Antenna interface
Redundancy and Diversity Duplicate modules provide fail-soft & capacity options; diversity provides functional options.
-Multiple antennas
-Alternate power source
Facilitated Reuse Modules are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules.
-Rack interface
-Patch panels
-Test plans
Elastic Capacity Module populations & functional capacity may be increased and decreased widely within the existing infrastructure.
-Growth to expand within racks as needs change
-Configurable to multiple aircraft
-Test time
Peer-Peer Interaction Modules communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored.
-Airplane-to-MTU communication
-Antenna-to-multiple system (shared)
Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally.
-All parts available and stored within MTU
-Maintain interconnect based on classification
Deferred Commitment Module relationships are transient when possible; decisions & fixed bindings are postponed until necessary.
-Configuration based on aircraft demand
Self-Organization Module relationships are self-determined; and component interaction is self-adjusting or negotiated.
-Encryption between aircraft and MTU (handshake)

9. System: MTU Resources Integrity Management Infrastructure
Conex
operators
ground support
airplane
antennas
LRUs / systems
Situational awareness
Resource mix evolution
Resource readiness
Activity assembly
Infrastructure evolution
PM, PE
Kitters, planners, logistics
Aircraft crew, test crew
Test director
Customers
Active
Infrastructure
Passive
Platform Config 1
Platform Config 2
Platform Config 3
Sockets
Signals
Security
Safety
Service
Power, LAN, patch panel
Databus, power, & control
Quality, config mgmt
Overload protect, conex design
Test proc, SW updates
Rules/Standards