1 UNCLASSIFIED Army Enterprise Migration to DISA LTC Peter Barclay, CIO/G6 Mr. Kevin Mott, NETCOM Mr. Jose Ortega, PEO EIS Mr. Donald Greenlee, PEO EIS

2 UNCLASSIFIED Agenda Service Overview How does DoD Enterprise (DEE) work? DEE solution details Army/DEE Service Desk operations Stakeholders NETCOM Operational Update Questions

3 UNCLASSIFIED Service Overview The Department of Defense’s (DoD) Enterprise service provides secure cloud-based to the DoD enterprise that is designed to increase operational efficiency and facilitate collaboration across organizational boundaries Provides secure access to your anywhere, at anytime, from any place, whether stationary or mobile Supports coordination efforts by sharing individual, organizational, and resource calendars across the Department of the Defense and its mission partners Reduces the cost of by eliminating unnecessary administration and inefficient network configurations, enabling resources to focus on other priorities Replicates your data in highly-secure Defense Enterprise Computing Centers (DECCs) in order to provide your organization with the level of assurance required to know that your communications are secure

4 UNCLASSIFIED DEE is designed to support the deployment of capability for 4.5 million users and a global address list (GAL) scaled to support 10 million objects (e.g., DoD Common Access Cards personas and Non Person Entities). How does DoD Enterprise work?

5 UNCLASSIFIED DEE Solution Details Complete local and remote redundancy PKE OWA and Outlook client Mailbox location assigned by geography 4GB mailbox for business class users and 512MB mailbox for basic class users (NIPR only) Every DoD CAC holder in the GAL (3.9M) Unclassified Network (NIPRNET) NIPRNET only for Outlook access RPC over HTTPS protocol Utilize the EMSG for Internet traffic and McAfee GroupShield for all Modular pod build in blocks of 77K users Classified Network (SIPRNET) Utilize all-in-one Exchange servers McAfee GroupShield for mail sanitization Modular pod build in blocks of 50K users Service diversity through replication and load balancing One distributed system with full NetOps visibility Enterprise GAL with shared calendars Enterprise address and display name OWA (CAC required) DISN IA architecture compliant NIPR Blackberry and Windows Mobile 9 DECCs (7 CONUS, 2 OCONUS) and mini-pods NIPRNET and Internet accessible SIPR 6 DECCs (4 CONUS, 2 OCONUS) and mini-pods OWA (smart card required SME PED support DESIGN DETAILSCHARACTERISTICS

6 UNCLASSIFIED DEE Service Desk Operations

7 UNCLASSIFIED Stakeholders DISA: (Service Provider) PEO EIS (Product Director EE): Acquisition oversight to monitor performance. Coordinate with CIO/G-6 on requirements CIO/G-6: Define requirements and get them validated. Provide policy and POM for funding NETCOM: Manage migration schedule and task for all SIPR / NIPR migrations. ARCYBER: Receive/validate requirements from all Commands and provide to CIO/G6. Ensure the security of Army’s portion of network Theater Signal Commands NECs and users supported by NECs Functional Commands Users and commands not supported by NETCOM, TSCs, and NECs USACE, ARNG, USAR, INSCOM, MEDCOM, etc.

8 UNCLASSIFIED Army has migrated legacy data for 371,146 users with a total 453,960 transitioned from legacy systems Planned migrations for the next 14 days: 1,158 users and 167 Blackberry devices Army deadline to complete migrations (both NIPR and SIPR) NLT 31 Mar 13 Waivers. The only extensions that extend beyond that date are:  Corps of Engineers  USMA Issues/Challenges  Getting all of the varied commands and organizations scheduled for NIPR migrations  Posturing SIPRNet migration schedule to align with token delivery, pod/mini-pod readiness, and CONUS circuit upgrades  Increasing the migration OPTEMPO to ensure completion by 31 Mar 13 8 NETCOM Operational Update

9 UNCLASSIFIED Questions ??