the evolution & global deployment of desktop to data center
TRANSCRIPT
1
The Evolution & Global Deployment of Desktop to Data Center Session #120, 7 March, 2018
Mr. Mark Goodge, Division Chief, Architecture, Advanced Concepts & Engineering (AACE)
COL Beverly Beavers, Division Chief, Infrastructure & Operations (I&O)
Deputy Assistant Director Information Operations (DAD IO)/J-6 Directorate | Defense Health Agency (DHA)
2
Speaker IntroductionMr. Mark Goodge
Chief Technology Officer, Military Health System
Division Chief, Architecture, Advanced Concepts & Engineering (AACE) Division | DAD IO/J-6| DHA
Mr. Goodge is responsible for the program management of technical projects, as well as the identification and research of innovative health IT tools and solutions that can be deployed enterprise-wide to help improve Department of Defense (DoD) patient & provider experience. He is the leader of the deployments efforts for Desktop-to-Datacenter (D2D) throughout the Military Treatment Facilities (MTFs) across the Services.
3
Speaker Introduction
COL Beverly Beavers
Division Chief, Infrastructure & Operations (I&O) Division | DAD IO/J-6 | DHA
COL Beavers is the leader for the sustainment strategy and efforts for the D2D. COL Beavers joined the DAD IO/J-6 after serving as the Army Medicine CIO/G6 from February 2015 until July 2017. Prior to this assignment COL Beavers served as the Information Technology Strategic Sourcing Analyst, Component Acquisition Executive for the Defense Health Agency, in Arlington, Virginia.
4
Conflicts of interest
Mr. Mark Goodge, has no real or apparent conflicts of interest to
report
COL Beverly Beavers, has no real or apparent conflicts of
interest to report
5
Agenda
• Overview
• History / Evolution
• Core Capabilities
• Transitioning to Medical Community of Interest (Med-COI)
• Global Deployments
• Sustainment Strategy
• Questions
6
Learning Objectives
• Describe the overall objective & core capabilities of D2D
• Discuss the benefits and overall impact of D2D Implementation on MTFs
• Demonstrate the D2D Execution Plan as an Increment Approach
• Identify Key Dependencies and Critical Success Factors for D2D Implementation
• Propose the plan for future Global D2D Deployments
Delivering D2DThe D2D program is the coordinated effort for DHA’s IT efficiencies and capabilities
in order to streamline Health Information Technology infrastructure service lines
across the Military Health System (MHS) enterprise to improve business and
clinical needs in response to the infrastructure requirements necessary to support
the Department of Defense in preparation for deployment of the new electronic
health record and MHS Genesis.
Evolution of Military Health System (MHS) Information Technology (IT) Infrastructure Consolidation
D2D Drivers
Consolidation & Standardization of Infrastructure Variance to “One” Health System
One
Health
System
Leveraging Staged, Incremental Approach
Typical D2D Implementation Timeline
13
Pre-Implementation Checklist
• Outlines preparation activities that sites can complete prior to start of D2D installations for such projects as Med-COI and DS/EM
• Helps site prepare for the transition prior to the first site installation coordination call
• Reduces site-level workload during the actual installation process
• Improves the completeness of information exchanged between the site and DHA
• Ultimately reduces the possibility of system downtimes
D2D Core Infrastructure Components
Transition to Med-COI
Site Specific Transition Plan (SSTP)• STTP provides documents and
information used to transition the MTF; includes:
– DHA points of contacts (POCs)
– Site and its geographically separated units (GSUs)
– Roles and Responsibilities
– Communication and documentation tools
– Virtual Local Area Network (VLAN) transition sequence
– Risk Management Framework (RMF) Tracker
– Internet Protocol (IP) Plan
– Rollback Plan
17
Key Dependencies & Critical Success Factors
• D2D and MHS GENESIS integration
• Daily scrum attendance and tracker reporting
• Coordination with program management offices (PMOs) and vendors in
a timely fashion
• Flexibility with parties
• Completing D2D Pre-Implementation Checklist
• Preparing for RMF assessment
• Ensure currency of applications
• Identify support vendors for site-purchased clinical systems
18
Stakeholder Management• D2D program is comprised of a range of external stakeholders
• Since components of the program span across the enterprise, program management can be challenging
• D2D cannot be executed without the partnership and participation of the Services, Sites, and the expertise of their staff
Regional Approach• For reporting and management purposes, Military Treatment Facilities (MTFs) are aligned
under six regions:
– Northeast
– Southeast
– Central
– Western
– Pacific
– Europe
• Regional representatives facilitate communication & serve as DHA customer service to the
services and MTFs.
• Implementation of D2D services will occur in many regions simultaneous
– For instance Med-COI enclave transition may be occurring within Western Region
while DS/EM is implementing within Northeast Region
D2D Benefits
21
D2D Sustainment
Sustainment Strategy
I&O’s support is evolving to meet
changing environment:
• Maturing DHA organization
– DHA reorganization
– Impacts of Zero-based
Budget Reviews
– National Defense
Authorization Act (NDAA)
• Implementation of MHS GENESIS
• Deployment of D2D changes
Key principles of the I&O
operational support approach
include:
• Support the DHA overarching
strategy
• Standardize products and
services across DHA
• Using D2D implementation
• Base on Information
Technology Infrastructure
Library (ITIL) foundation
I&O Division oversees operations and sustainment of the D2D infrastructure
Sustainment Strategy: ITIL Foundation
24
Sustainment Strategy: Partnership of Multiple Organizations
• DHA
– I&O
– Regional Offices - Future
• Services
• MTFs
• DISA
• Vendors
Sustainment ComponentsNetwork / Circuits
• Scope: Med-COI / Wide Area Network (WAN) /
Network Protection Suite (NPS) devices
• Approach: Central support through the DHA
Network Operations Center (DNOC)
• Key Responsibilities:
– DHA – Routing operations and management:
Regional Gateway NPS/Border Router
Management, Information Assurance
Vulnerability Management (IAVM), Web
Cache and Content Filtering (WCCF)
Management, Network Monitoring
– DISA – Circuit provisioning and management
LAN / WLAN
• Scope: LAN and WLAN operation,
management and monitoring
• Approach: Central support through the
DNOC
• Key Responsibilities:
– DHA
• Enterprise switch management
• LAN/WLAN operation,
standardization and transport
• LAN/WLAN monitoring and
management
– MTF
– Site administrators perform on site
maintenance and monitoring
Sustainment Components
CSMS
• Scope:
– Storage services infrastructure and
support
– Compute infrastructure and support
– Virtualization infrastructure and
support
• Approach: Centrally managed
• Key Responsibilities:– DHA
– Operations and maintenance through
DHA Enterprise Tier 2 and Tier 3
support organizations
DS/EM
• Scope:
– Authentication and access control
– Active Directory forest management
– Group Policy Objects (GPOs) support and
services
– Domain Name Server (DNS) support
• Approach: Initially central management of enterprise-
level aspects with on site support for MTF-specific
aspects
– Shift to central management post SCCM
• Key Responsibilities:
– DHA - Support of enterprise standard
services, including servers
– MTF - Support of MTF-specific aspects,
including users, groups and workstations
Sustainment ComponentsDaaS
• Scope:
– End user device management
– Account management
– Application and license management
– Image management
– SCCM management
– DNS management
– Vulnerability management
• Approach: Combination of central and on site support, defined by specific task
• Key Responsibilities:
– DHA: Overall management through I&O
– MTF
– Support for on site tasks working with central support
28
Overarching Service Management• Scope:
– Incidents and requests for services
– Service maintenance
• Approach:
– Centrally managed
• Key Responsibilities:
– DHA
– Managed through DHA GSC following standard, defined processes
Tiered Support Model
DHA provides an integrated, enterprise tiered support model
Enterprise Tiered Support
Model
30
Infrastructure Life Cycle Management• Scope:
– Asset management
– Contract management
– Warehouse and logistics management
– Equipment lifecycle management
– Software management
• Approach:
– Centrally managed
• Key Responsibilities:
– DHA
– Central planning, tracking, and acquisition management working with AACE,
Portfolio and Resource Management (PRM), and contracting offices
31
Status & Implementation• Key support services in place today
– Adjusting to support new systems and D2D architecture
– And legacy systems through the transition
• Implemented operational improvements in advance of D2D
– Creation of the Field Operating Guide
• Define key activities, roles and responsibilities
– Development of the Roles Based Access Control (RBAC) model
• Defines permissions
– Implementation and tailoring of SCCM
• Supports central management of the D2D components
Lessons Learned to Date • Significant variation in the as-is environments: Across Services and MTFs
• Operations requires partnership with multiple organizations to succeed: Sites, other DHA
agencies, regions, and support providers
• Circuit management related lessons included:
– Coordinate early with senior leadership of base/post communications organizations to
make aware of the criticality and secure assistance from their organizations
– Ensure base/post identify alternate escorts to ensure timely access for vendors to
locations
• GSC lessons and improvements included:
– Improvements for the Dashboard drill down pages
– Request programs coordinate with GSC prior to release of new capabilities at the sites
– Recommendations regarding handling of paper tickets used at the test sites ahead
33
Way Ahead• Support operations and sustainment of
D2D components as transitioned
• Expect more responsibilities to shift from MTF
• Deployment of D2D and SCCM
• Definition and implementation of the Regional Operations model
• Central management with decentralized execution
• On site support will continue to play a key role
• I&O will partner and work with the sites
Key Takeaways• Plans are focused on standardizing systems
to the desktop
– Provide a consistent level of support
and performance
• MTFs must begin preparing for the transition
– Review implementation schedules
– Review the preparation checklists and
guides
– Begin local activities and tasks
34
Questions
Emailing this inbox will ensure your questions get directed to and answered by:
• D2D Project Managers
• AACE Division Support