1. Three Maintainers and a *ing Op
Greg “The Hammer” Hamilton
Meghan “Wonder Wo”Manelski
“Magic” Mike Johnson
“Woody” Bridges

2. Team members: The Hammer; Wonder Womanelski; Magic Mike; Woody
Team: Three Maintainers and a *ing Op System: Remote Maintenance System (RMS)
Strategic Values/Objectives:
Low cost
Secure
Reliable
Low manpower overhead
Expandable/Reconfigurable
Descriptive Statement
The Remote Maintenance System (RMS) enables real-time monitoring, troubleshooting, and repair/restoration of airborne mission systems. This allows technicians to maximize system readiness by scheduling work, ordering replacement parts, and returning off-line systems to service in real-time. The RMS allows specialized off-board maintenance technicians to address system anomalies for which on-board crewmembers may not possess the necessary technical proficiency and training.
Team members: The Hammer; Wonder Womanelski; Magic Mike; Woody

3. Three Maintainers and a *ing Op – Remote Maintenance System (RMS)
CURVE High-Level System/Process Environment Consider both reactive needs & proactive opportunities to seize, within mission
Capriciousness: unknowable situations
System anomalies (reactive)
Automated troubleshooting development (proactive)
Uncertainty: randomness with unknowable probabilities
Network availability (reactive)
Quantity of aircraft supported at any given time (reactive)
Risk: randomness with knowable probabilities
Performance of remote maintainers (reactive)
Ability/Inability of supported aircraft to accomplish mission (reactive)
Variation: knowable variables and variance range
Qualified personnel availability (reactive)
Operating location of supported aircraft versus supporting RMS (reactive)
Performance measures of COTS equipment (proactive)
Defining required skillsets for high-interest mission profiles (proactive)
Evolution: gradual (relatively) successive developments
Development of new testing modules/support equipment (reactive)
Deployment of more RMS (reactive)
Technical maturity over time (proactive)

4. System: Remote Maintenance System (RMS)
Reality Factors
Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance...
Fatigue
Attention to detail
Task Saturation
Experience level
Organizational Behavior – Survival rules rule, nobody's in absolute control...
Over confidence; arrogance
High workload/low manpower
Under/Over reporting maintenance problems
Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing...
Application-based products
Security
Loss of control
System Complexity – Incomprehensible, highly networked, unintended consequences, emergence...
Networking complexities
Detailed documentation
Training
Globalization – Partners with different ethics, values, infrastructures, cultural assumptions...
Time differential
Support prioritization
Denied areas of service (link availability/unavailability based on area of operation)
Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects...
COTS upgrades (unplanned firmware upgrades)
Outsourced web services/network connectivity
Reliability of trend analysis data
Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative...
Unrealistic customer expectations
Funding for necessary upgrades
Competition from other companies
Other?
Cost – will this approach be cost-prohibitive?

5. Response Situation Analysis for System: Remote Maintenance System
with [t,c,p,s] metric-priorities for each issue, t = time of change, c = cost of change, p = predictability of change, s = scope of change
Change Domain
Change/Response Issue
Proactive
Reactive
Creation
(and Elimination)
What must the system be creating or eliminating in the course of its operational activity?
Eliminate system down time (p)
Eliminate unnecessary expenses (c)
Create intuitive UI (s)
Improvement
What performance characteristics will the system be expected to improve during operational life cycle?
Speed of identifying/fixing system anomalies (t)
Enhanced network availability/performance (s)
Enhanced troubleshooting techniques (p)
Migration
What major events coming down the road will require a change in the system infrastructure?
Atmospherics (sunspots, weather, etc.) (t,c)
Network outages (s)
World events (t,c,p,s)
Modification
(Add/Sub Capability)
What modifications in resources-employed might need made as the system is used?
Enhanced technical data (t,c,s)
Improved COTS equipment (c,s)
Redundant communications systems (c,s)
Correction
What can go wrong that will need an automatic systemic detection and response?
Link loss (p)
Intrusion (c,p,s)
Environmental factors (fire, smoke, natural disaster, etc.) (t,c,s)
Variation
What process variables will range across what values and need accommodation?
Technician skillsets (t,c)
Attrition (t,c,s)
RMS location in relation to supported aircraft (c,p,s)
Expansion
(and Contraction
of Capacity)
What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?
Number of aircraft supported at once (s)
Scalability of RMS (c)
Link bandwidth and throughput (c,p,s)
Reconfigu-ration
What types of resource relationship configurations will need changed during operation?
Updated ROE & TTP (t,s)
Operating location (t,c)
Personnel (s)

6. System: Remote Maintenance System
(Think … Drag-and-Drop / Plug-and-Play)
Encapsulated Modules
Racks
Power supplies
Software applications
Encryption path
Cooling fans
Scalable
Reusable
Evolving Infrastructure Standards
Sockets:
Power cabling
Crypto devices
RMS module interconnects
Signals:
SATCOM/LOS communications
Security:
Common training and terminology
Standardized ICDs
Safety:
EMI regulations
OSHA standards
FAA standards
Service:
Troubleshooting tool ConOps
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)

7. System: Remote Maintenance System
Sample Graphics for your modification into your system needs
Resources
Integrity
Management
Technicians
Developers
Network
Communications
Software
RMS
Structure
Test
Equipment
Situational awareness
Resource mix evolution
Resource readiness
Activity assembly
Infrastructure evolution PM
FM, Warehouse Mgr PE
Developers
Lead Maintenance Tech (LMT)
Active
Infrastructure
Passive
Config 1
Config 2
Config n
Sockets
Signals
Security
Safety
Service
What?
Rules/Standards