1. Team: Remote Site
Team: Virtual System Integration Lab (VSIL)
Descriptive Statement: The Virtual System Integration Lab (VSIL) is a development environment that is designed to allow remote teams of software and system engineers to integrate equipment and functionality without the need for local, physical hardware. The VSIL will be multi-faceted, initially allowing remote use of physical hardware for partial testing. Ultimately, the VSIL will use simulators to mimic inputs from actual hardware, and will not require any deliverable hardware for integration. The VSIL development environment will contain generic building blocks (DAUs, sensors, devices, etc.) that can be used in future development environments for different projects or products. The VSIL will allow the system-under-test to be deployed onto target hardware for factory acceptance testing.
Objectives:
-Remote Availability
-High Capacity
-Scalable
-Risk Reduction
-Schedule Efficiency
-Full Test Capability
Team Members: Rob Moeslein, Russ Harper, Bob Rodzewich

2. Put as many points in each category as you feel appropriate)
CURVE High-Level System/Process Environment Consider both reactive needs & proactive opportunities to seize, within mission
Caprice: unknowable situations
Power and network outages (reactive)
Emergency customer utilization (proactive)
Uncertainty: randomness with unknowable probabilities
Hacking (external or insider threat) (reactive)
Become an industry standard (proactive)
Risk: randomness with knowable probabilities
Integrate multiple tools/environments (reactive)
Prohibitive cost or schedule (reactive)
Prevent system corruption (proactive)
Variation: knowable variables and variance range
Configuration Management (reactive)
Workforce response and acceptance (reactive)
Require baseline skills for support (proactive)
Evolution: gradual (relatively) successive developments
Increasing fidelity over time (reactive)
New tools emerge that replace custom tools (proactive)

3. System ___VSIL_________________________
Reality Factors
Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance...
Workforce acceptance and utilization of provide tools
Inadvertent or intentional system corruption
Organizational Behavior – Survival rules rule, nobody's in absolute control...
Short term cost too high
Cost of sustainment
Productization to create a market
Workforce and skills changes
Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing...
Distributed system creates access points and security vulnerabilities
Not location dependent (“cloud” implementation)
System Complexity – Incomprehensible, highly networked, unintended consequences, emergence...
Does not perform exactly like hardware
Elimination of workforce positions
Globalization – Partners/customers/employees with different ethics, values, infrastructures, cultural assumptions...
Lack of urgency due to value differences
Commercial network infrastructure support
Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects...
Adjust internal process to accommodate new environment
Lack of total communication due to distributed team
Overcome by hot-shot web app
Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative...
Increased exposure to competitors and adversaries
Dependence on subcontractors or suppliers
Other? ?

4. Response Situation Analysis for System: Virtual SIL
with [t,c,p,s] metric-priorities for each issue, t = time of response, c = cost of response, p = predictability of response, s = scope of response
Domain
Response Issue
Proactive
Reactive
Creation
(and Elimination)
What artifacts/data/knowledge must the system/process be creating or eliminating during operational activity?
Diagnostic capabilities (problem identification) Change Logs
Data products based upon inputs Configuration Management information
Error Logs Access Control and Security Monitoring reports
Improvement
What process/system performance characteristics will be expected to improve during its operational life cycle?
Connectivity System security
Fidelity Performance (operating speed, throughput)
Communication capability
Migration
What major events coming down the road will require a change in the process/system infrastructure?
Government customer access
Foreign users
Processing power to simulate all hardware in software
Modification
(Add/Sub Capability)
What modifications to employable resources might need made as the process/system is used?
Higher bandwidth communications Physics-based environmental model
VSIL manager (person)
Engineering support
Correction
What will impair/obstruct process/system agility that will need an automatic systemic detection and response?
Insufficient processing power Lack of customer acceptance
Lack of connectivity Lack of workforce acceptance
Classified information
Variation
What process/system variables will range across what values and need accommodation?
Fidelity of results (dummy data – accurate representation of real data)
Number of simultaneous users (1 to N)
Applicability to different system types (n to N)
Expansion
(and Contraction
of Capacity)
What are “quantity-based” elastic-capacity range needs on resources/output/activity/other?
Direct connection to set of physical hardware to a la carte virtual system configuration (expansion)
Elimination of physical hardware (contraction)
Reconfigu-ration
What types of resource relationship configurations will need changed during operation?
Integration of new hardware / functionality New industry standards
Trouble shooting (including field support) New security requirements
Ability to insert faults

5. System: VSIL Operation______________
(Think … Drag-and-Drop / Plug-and-Play)
Encapsulated Resources
Enterprise Service Bus (ESB)
HW System
Virtual System
VSIL Developers
VSIL Testers
Users
Scalable
Reusable
Evolving Infrastructure Standards
Sockets: Communication Channels
Signals: Configuration, Scheduling, Operating Cost
Security: Company Affiliation, Access Control, Data Encryption, User Privileges
Safety: Provided by workplace
Service: Procedures, Product Management
sockets (physical interconnect)
signals (data/stuff flow between resources)
security (trust interconnect)
safety (of user, system, and environment)
service (system assembly ConOps and evolutionary agility sustainment)

6. System ______VSIL Operation___________________
Sample Graphics for your modification into your system needs
Resources
Integrity
Management
ESB
HW System
Virtual System
Developers
Testers (VSIL)
Users
Situational awareness
Resource mix evolution
Resource readiness
Activity assembly
Infrastructure evolution
Project Manager / Chief Engineer
Program Manager / Procurement
Project Engineer
Project Engineer / User
Project Manager / Chief Engineer
Active
Infrastructure
Passive
Config 1
Config 2
Config n
Sockets
Signals
Security
Safety
Service
Communication Channels
Configuration, Scheduling, Operating Cost
Company Affiliation, Access Control, Data Encryption, User Privileges
Provided by workplace
Procedures, Product Management
Rules/Standards

7. RRS Principles for System: __VSIL Operation__
(Think: Plug-and-Play, Drag-and-drop)
Reconfigurable
Scalable
Reusable
Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure.
Enterprise Service Bus (ESB), HW System, Virtual System, VSIL Developers, VSIL Testers, Users
Evolving Infrastructure Key elements of the infrastructure likely to evolve and need to be evolvable.
Computing resources, adapters and translators, tool capabilities, network bandwidth
Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal.
ESB, ESB adapters, HW translator(s), online documentation, online scheduling, remote access
Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options.
Product owner backup, cloud computing and local data center, generic interface adapter
Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate resources.
Adapters and translators, trained users, procedures, virtual elements, system configuration, tools (monitor, debug)
Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within existing infrastructure.
Cloud platform, expandable local data center, VSIL training for users/maintainers, remote operation
Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored.
Instant messaging, virtual blackboard
Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally.
Common data store remotely accessible, online scheduling, online configuration
Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary.
Virtual replacement of constituent hardware, on-demand computing resource allocation
Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated.
[in work]