1. Team Name: OCD Solutions
System: Optimized Cloud Data Solutions (OCD Solutions)
Team Members: Mike Moffitt, Ty Bolin, Trey Kanaman, & Kennedy King

2. Strategic Values/Objectives
Quick/Easy Configuration
Quality – Customer Satisfaction
Scalable Performance
Scalable Storage
Reliability
Descriptive Statement
Optimized Cloud Data Solutions provides cloud based storage that can be utilized across platforms and customers. The implementation provides the ability to combine common data structures into a single instance reducing the overhead, and licensing requirements of running multiple instances within one or multiple systems. The system provides the customer the ability to span data storage across platforms that have access to the OCDS system. This also allows for more optimal usage of the processing power within the allocated resources. The OCDS system allows the customer to add storage or increase performance on demand as needed by scaling the hardware the customers storage node can access. This allows the system to meet the customers changing needs. The OCDS system is not hardware specific. This allows the overall capacity of the entire OCDS system to add new hardware without requiring the existing hardware to be replaced.

3. CURVE Capriciousness Uncertainty Risk Variation Evolution
New Technologies (reactive/proactive)
New Customer Environment (reactive)
Uncertainty
Total Storage needed (reactive)
Number of supported platforms (Reactive)
On Demand Expansion (reactive)
Standardize Interfaces (proactive)
Risk
Hardware Availability (reactive)
Customer infrastructure (network) (reactive)
Variation
Variation of Hardware vendors (proactive)
Types of data storage (reactive)
Performance requirements (reactive)
Processing priority (reactive)
Evolution
New platforms (reactive)
New technologies (storage, interfaces, etc) (reactive/proactive)

4. Reality Factors Human Behavior Reality Complacency Lack of experience
Slacktivism
Organizational Behavior
Overselling cloud space to customers that may not need it
Lack of “on-hand” hardware - dependent upon implementation
Employee incentives for selling more hardware/space than is necessary
Technology Pace
Updating security vulnerabilities
Changing OS formats
Maintain legacy support
System Complexity
Excessive accelerated expansion
Supporting multiple evolved technologies
Training
Globalization Reality
Infrastructure – unreliable power source based on the location of service
Language barriers
Export/Import laws
Partially-Agile Enterprise
Use of COTS
Agile Adversaries/Competitors/Customers
Competitors may provide a more agile operation

5. Response Situation Analysis
PROACTIVE
Change Domain
General Issues
Creation (and Elimination)
Provide Data Storage systems to solve customer needs (s)
Consolidate data access location to a common point (s)
Improvement
Data Access Performance (c, t)
Security Enhancements (p, c)
Migration
Incorporation of new technologies (p, t)
Implement smaller hardware form factors (c)
Modification (Add/Sub Capability)
Expand to include services beyond data storage (s, c)
Add functionality to simplify management of system (s, c, t)

6. Response Situation Analysis
Reactive
Change Domain
General Issues
Correction
Add tolerance to power fluctuations (c, t, p)
Continue operation through hardware failures(c, t)
Variation
Variation in hardware availability (t, p)
Customer Priority of processing needs (p)
Expansion (and Contraction of Capacity)
Adding or removing processing and storage capacity (t, p)
Support of more or fewer platforms (p, t)
Reconfiguration
Adjusting of COTS vendors (c, t)
Modification of deployment implementation (p, c, t, s)

7. Encapsulated Modules
REUSABLE
SCALABLE
Evolving Infrastructure
Hardware:
Power
Racks (depending on customer)
Cooling system
Processors
Storage Devices (RAIDS, etc)
Network System
Sockets:
Network Hardware standards – such as transitioning from copper wire to fiber optic
Hard Drive Data types – different interfaces for types of hard drives (SATA, SAS, etc)
Signals:
Network Protocols – Supporting variations in network protocols as technology advances (TCP/IP, UDP, IPv4/6)
Supported Legacy data types – Interface into new platforms may be set and require adjustment from system to support.
Security:
Standardization of Software – common theme of user interface, use of industry standards (where available) for data transfers protocols
Use of Industry standard physical interfaces
Software:
Database Module
Interface/Translation Module
Resource Management Module
Safety:
Adhering to regulatory laws
Temperature monitoring within system
Service:
Provide remote monitoring/maintenance of system to customer

8. Resources Integrity Management Infrastructure Rules/Standards
RACKS
POWER
Database
Modules
Cooling
System
Interface
Module
Resource
Management
Module
Situational awareness
Resource mix evolution
Resource readiness
Activity assembly
Infrastructure evolution
Team Lead
Material Coordinator/Purchaser
Management/Customer Liaison
Product Assemblers
Program Management
Active
Infrastructure
Passive
Single Platform
Multiple Platforms
Centralized OCD-Skynet
Sockets
Signals
Security
Safety
Service
HW Interface
SW Interface
Standards
Regulations
Support Func
Rules/Standards