1. Joint Information Environment
The Way Ahead

2. Joint Information Environment What is it, anyways!?
Shared IT infrastructure
Enterprise services
Single Security Architecture

3. JIE is NOT a Program of Record
JIE is NOT a turn-key solution
JIE is NOT an independent “way of doing things”
Uses existing architectures and services

4. JIE Core Principles – the BIG Rocks
Joint Governance
“IT Task Force”
Network Normalization
Standardization
Data Center Consolidation
Reduced IT Footprint
Identity and Access Management
Trusted authentication
Enterprise Services
, collaboration, file storage, etc.
FIRST PROBLEM: GET BUY IN FROM THE AOR IT EXPERTS

5. JIE – What are we trying to achieve?
Improved Mission Effectiveness/Operational Flexibility
AGILE
Includes mobile, deployed
Works in Disconnected, Intermittent and Low Bandwidth
Increased Cyber Security
Confidentiality, integrity and availability
Works with ALL Mission Partners
IT Efficiencies/Joint Information Services
Interoperable
Maximum performance, reliability and extensibility

6. JIE’s Three Lines of Operation
Governance
Operations
Technical Synchronization

7. JIE Relationships

8. Enterprise Operations Center
JIE Increment I EUCOM
Builds on existing network consolidation efforts
Heavily reliant on cloud architectures
Move Massive Application Silo’s to more flexible, responsive infrastructure
Enterprise Operations Center
Stuttgart, Germany

9. JIE Increment 2 - PACOM

10. JIE Increment 2 - PACOM
Coalition capability “built-in” and not “added-on”
Common Mission Network Transport must support network security enclaves to accommodate many communities-of-interest to support user-to-user coalition connectivity
A wide-area neutral network is needed to connect the networks of sovereign nations
Robust identity authentication and authorization management for each nation to maintain trust in the system

11. Discretionary Information Sharing
Trusted personnel Identification and authorization service
Agile virtual enclaves
Information conditioning
Strength of separation required

12. JIE Challenges Multiple Enterprises Multiple Data Types
Military Services, Intelligence Community, Agencies, CCDRS Multiple Partners, Allies, Coalitions, States, NGAs, OGAs, PVOs, etc.
Multiple Data Types
Public, Releasable, Private, Controlled, and Classified Information
Austere Connectivity Over Very Large Distances
Not just robust high-capacity public infrastructure
Mobile Forces & People
Huge Populations & Communities
Partners with varying levels of trust

13. Upcoming JIE Event
JIE Mission Partner Symposium 2014 at the Baltimore Convention Center, Baltimore, Maryland from May 12 to May 14, 2014.

14. Jesse Adams Chief Architect – US NAVY NGEN/NMCI, HP Enterprise Services
Jesse has been with HP (EDS) since 2007.
Jesse started as a Solutions Architect on the NMCI account, then became HP’s Chief Architect for the account in early 2010.
Responsible for working with the Echelon II commands to understand their objectives and help shape strategies.
He joins us from the Dallas Fort Worth area.

15. JIE Challenges under NGEN
Not a Program – perceived as an “unfunded mandate”
Program Office may pick-and-choose elements of JIE to be adopted
LPTA Limits Innovation
Technology Refresh and Insertion Program will be largely responsible for moving existing designs into compliance with JIE, extending timeline for adoption over several years.
“Not Designed Here” Syndrome
Must minimize the “drift” likely to occur from differing opinions on how to apply JIE

16. JIE Opportunities under NGEN
Adoption of SSA will help mitigate ever-increasing circuit strains
The introduction of the SSA at primary site boundaries will enable NMCI to stand down their Boundary 1’s, which are overloaded today largely due to media-rich Internet traffic.
On average, up to 90% of Internet traffic crossing the NMCI Boundary 1’s is MWR-related.
By facilitating Internet access closer to the users, the volume of traffic can be distributed across more points, reducing its impact on any individual WAN circuit.

17. JIE Opportunities under NGEN
Server Farm Consolidation revisited
Move from a simple fork-lift approach to a modernization / transformation strategy
Consolidate to standardized platforms
Maximize virtualization for greatest service density
Move to a common reference architecture – potentially enable seamless migration of services between various data centers to meet evolving mission requirements.
Introduction of “XaaS”
Technologies reviewed/revised to better enable “confederation” of services and data, in order to better position them to best support the users.

18. Jerry Bass Customer Solutions Architect – CISCO Federal
Jerry has been with CISCO since 1999.
Primary focus is Air Force.
He is an expert in network security and information assurance.
He joins us from the Boston area.