Common use of Assumptions and Constraints Clause in Contracts

Assumptions and Constraints. The following statements of assumptions and constraints are relevant to this BPA PWS:  DHA will utilize Information Technology Service Management (ITSM) which covers incident management, problem management, change management, configuration management, knowledge management, service catalog management, and request management capabilities.  DHA will use ServiceNow’s ITSM suite of products to operate and support its infrastructure transition and sustainment according to industry best practices, to include: Information Technology Infrastructure Library (ITIL), Agile, Scrum, and Development and Operations (DevOps) based processes.  DHA will provide an ITSM software solution and licenses for use to the EITSI and other service providers. DHA has acquired ServiceNow as its ITSM tool. Other tools are referenced in 5.2.7 Service Management Systems.  DHA will leverage operational and industry best practices for service delivery and support, including Enterprise ITIL-based practices, such as problem management for recording, managing and eliminating recurrent or chronic failures, configuration baseline management and change control for recording and executing infrastructure changes identified as necessary to meet operational objectives; all while minimizing adverse risks to overall service availability and component and service capacity, demand management, and availability management.  DHA expects to move to the ITIL 4 framework as part of establishing the EITS Environment, and thereby evolve from the current processes that conform to ITILv3 or do not follow ITIL practices at all.  DHA will continue to deliver shared services equal to or better than existing capabilities and service expectations.  All IT infrastructures will have a valid Life Cycle Management Plan (LCMP) in adherence to the corresponding Authority to Operate (ATO).  Once D2D-PEO is complete, the Enterprise will be on a standardized transport via Multiprotocol Label Switching cloud network known as the Medical Community of Interest (Med-COI) and operating on the Medical Joint Active Directory (mJAD). Med-COI is the common network transport for MHS services. mJAD provides single common authentication and centralized identity management framework for the MHS.  DHA will leverage DoD Enterprise Cloud Environment, a multi-cloud, multi-vendor ecosystem of cloud services. Traffic to and from these multi-cloud environments into Med-COI must ingress and egress through Med-COI Cloud Access Points (CAPs) for proper inspection. EITSI may need to work with existing Infrastructure & Operations Division’s (IOD) Branches to migrate or assist MTFs, sites and geographically separated units (GSUs) with migration activities post D2D-PEO and MHS GENESIS Go Live.  Operations will leverage standardized enterprise management tools, as selected by the DAD IO/J-6 Enterprise tools rationalization process.  Tools such as Microsoft Systems Center Configuration Management (SCCM), System Center Operations Manager and Tanium will continue to be used to routinely inventory, centrally manage, and deliver digital content (patches, software, or updates) through distribution points and ensure all device end-points are visible by the Global Network Operations Center (GNOC). These Enterprise tools may change in the future.  DHA will transition from DoD Enterprise E-mail to Defense Enterprise Office Solutions (DEOS) in Fiscal Year (FY) 21.  Some DHA DAD IO/J-6 IT functions overlap between site and Enterprise levels.  Local MTFs, clinics, and GSUs will have local compute capability that will eventually be incorporated into standardized Hosting and Cloud Support Services. Until that occurs, multiple local compute, storage, backup, and virtualization infrastructures will be supported and maintained in adherence to the ATOs.  DHA Customers include Other Lines of Business (OLB) that are either associated with an MTF or provide additional supporting activities to the DHA mission.  The DHA GSC and GNOC is projected to relocate to Port San Antonio in June 2021.  DHA expects to begin work on the 4ENO Transition in 2023, and potentially moving in 2025.

Assumptions and Constraints. The following statements of assumptions and constraints are may be relevant to and have some impact on this BPA PWS: . The below are the Government’s expectations, constraints, and goals but the Government is not bound by these statements.  DHA will utilize Information Technology Service Management (ITSM) which covers incident management, problem management, change management, configuration management, knowledge management, service catalog managementcatalog, and request management capabilities.  DHA will use ServiceNow’s an ITSM suite of products to operate and support its infrastructure transition and sustainment according to industry best practices, to include: Information Technology Infrastructure Library (ITIL), Agile, Scrum, Scrum and Development and Operations (DevOps) based processes.  DHA will provide an ITSM software solution and licenses for use to the EITSI and other service providers. DHA has acquired expects to acquire ServiceNow as its this ITSM, including an Advanced Digital Management Workspace ITSM tooland eventually Software Asset Management. Other tools are referenced in 5.2.7 Service Management Systems.  DHA will leverage operational and industry best practices for service delivery and support, including Enterprise ITIL-based practices, such as problem management for recording, managing and eliminating recurrent or chronic failures, configuration baseline management and change control for recording and executing infrastructure changes identified as necessary to meet operational objectives; all while minimizing adverse risks to overall service availability and component and service capacity, demand management, and availability management.  DHA expects to fully move to the ITIL 4 framework as part of establishing the EITS Environment, and thereby evolve from the current processes that conform to ITILv3 ITILv2011 or do not follow ITIL practices at all.  DHA will continue to deliver shared services equal to or better than existing capabilities and service expectations.  All IT infrastructures will have a valid Life Cycle Management Plan life cycle management plan (LCMP) in adherence to the corresponding Authority to Operate (ATO).  Once D2D-PEO is complete, the Enterprise will be on a standardized transport via Multiprotocol Label Switching cloud network known as the Medical Community of Interest (Med-COI) and operating on the Medical Joint Active Directory (mJAD). Med-COI is the common network transport for MHS services. mJAD provides single common authentication and centralized identity management framework for the MHS.  DHA will leverage DoD Enterprise Cloud Environment, a multi-cloud, multi-vendor ecosystem of cloud services. Traffic to and from these multi-cloud environments into Med-COI must ingress and egress through Med-COI Cloud Access Points (CAPs) for proper inspection. EITSI may need to work with existing Infrastructure & Operations Division’s (IOD) Branches to migrate or assist MTFs, sites and geographically separated units (GSUs) with migration activities post D2D-PEO and MHS GENESIS Go Live.  Operations will leverage standardized enterprise management tools, as selected by the DAD IO/J-6 Enterprise tools rationalization process.  Tools such as Microsoft Systems Center Configuration Management (SCCM), System Center Operations Manager and Tanium will continue to be used to routinely inventory, centrally manage, manage and deliver digital content (patches, software, software or updates) through distribution points and ensure all device end-points are visible by the Global Network Operations Center (GNOC). These Enterprise tools may change in the future.  DHA will transition from DoD Enterprise E-mail to Defense Enterprise Office Solutions (DEOS) in Fiscal Year (FY) 21.  DHA will initially define the service catalogue, quantify expectations, performance measures, expected outcomes and deliver services.  Some DHA DAD IO/J-6 IT Information Technology (IT) functions overlap between site and Enterprise levels.  Local MTFs, clinics, clinics and GSUs will have local compute capability that will eventually be incorporated into standardized Hosting and Cloud Support Services. Until that occurs, multiple local compute, storage, backup, and virtualization infrastructures will be supported and maintained in adherence to the ATOs.  DHA Customers include Other Lines of Business (OLB) that are either associated with an MTF or provide additional supporting activities to the DHA mission.  The DHA GSC and GNOC is projected to relocate to Port San Antonio in June 2021.  DHA expects to begin work on the 4ENO Transition in 2023, and potentially moving in 2025.