HC1028-18-R-0024_0002_10_Dec_2018.pdf

831710078

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

A. The purpose of this amendment is to:

1. Include RFP Amd 0001 Questions and Answ ers highlighted in red in Attachment L1.

2. Update IDIQ, TO 0001, and TO 0002 PWSs.

3. Update Sections L and M.

B. All else remains unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 40

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 10-Dec-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC102818R0024

X 9B. DATED (SEE ITEM 11)

11-Oct-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

10-Dec-2018

CODE

DISA/DITCO-SCOTT-PL83

2300 EAST DRIVE, BUILDING 3600

SCOTT AFB IL 62225-5406

HC1028 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC102818R0024

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PWS - IDIQ

PERFORMANCE WORK STATEMENT (PWS)

As of 10 Dec 2018

Contract Number: (completed by the KO at time of contract award)

TO Number: N/A

Contractor Name (completed by the KO at time of contract award)

Tracking Number: HC1028-18-R-0024/831710078 (GSM-O II)

Follow-on to Previous Contract and TO

Number:

HC1028-12-D-0021

1. Contracting Officer’s Representative (COR).

a. Primary COR.

Name:

Organization:

Department of Defense Activity

Address Code (DODAAC):

HC1047

Address: 6910 Cooper Ave, Ft. Meade MD 20755

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Name:

Organization:

DODAAC: HC1047

Address: 6910 Cooper Ave, Ft. Meade MD 20755

Phone Number:

Fax Number:

E-Mail Address:

2. Contract Title. Global Solutions Management – Operations (GSM-O) II

3. Background. This acquisition is designed to provide global operations solutions that are needed to support the

Department of Defense (DoD) Information Network/ Defense Information System Network (DODIN/DISN), under the direction of the Defense Information Systems Agency (DISA), for both DoD and non-DoD entities. This is a follow-on to the Global Information Grid (GIG) Services Management (GSM) effort that successfully provides the services to operate, defend, and sustain DoD information networks. DISA’s Acquisition approach will consist of three distinct programs, currently known as: Operations (GSM-O II); Engineering, Transition, and Implementation

(GSM-ETI); and Projects and Support (GSM-P&S). This PWS defines requirements for GSM-O II.

Each program (GSM-O II, GSM-ETI, and GSM-P&S) will include the requisite labor, equipment, and consumables associated with the provision and sustainment of services. These three efforts are integrally linked. GSM-O II will receive integration requirements from other programs. DISA wants to ensure industry understands that requirements may be generated from an implementation engineered contract under other DISA contracts, GSM-ETI or provisioning task under GSM-P&S.

The DoD DODIN/DISN is an all-encompassing information and communication technology project of the DoD. It is the globally-interconnected, end-to-end set of information capabilities, processes, and personnel needed to collect, process, store, disseminate, and manage information on-demand to joint warfighters, policymakers, and support personnel. Moreover, the DODIN/DISN enables the implementation of network-centric warfare doctrine. That doctrine provides an information advantage, enabled by information technology (IT), and creates a competitive warfighting advantage by networking well-informed, geographically dispersed forces.

The DODIN/DISN includes the set of information capabilities and associated processes for collecting, processing, storing, disseminating, and managing information on-demand to warfighters, policy makers, and support personnel, whether interconnected or stand-alone, including owned and leased communications and computing systems and services, software (including applications), data, security services, other associated services, and national security systems.

The DODIN/DISN supports information superiority and provides capabilities to DoD, national security, and related intelligence community missions and functions (strategic, operational, tactical, and business) in both contingency and peacetime environments. It provides interfaces to coalition, allied, and non-DoD users and systems and capabilities from all connected operating locations, including bases, posts, camps, stations, facilities, mobile platforms, and deployed sites.

The three GSM capability categories support customers in multiple functional mission areas and are detailed in

Figure 1.

FIGURE1: GSM SCOPE

GSM-O II is designed to provide global solutions that are needed to support the DODIN/DISN for both DoD and non-DoD entities. This is a follow-on to the Global Information Grid (GIG) Services Management – Operations

(GSM-O) effort that successfully provided the services to operate, defend, and sustain DoD information networks.

Operations and Sustainment (O&S) of the DODIN/DISN will be executed through the implementation of GSM-O II.

These requirements involve the day-to-day delivery support for telecommunications capabilities, including operating and sustaining the network, defending the network, providing access to new customers, monitoring network health, restoring service (as necessary), and implementing minor adjustments and improvements to existing capabilities.

Fundamentally, these activities are necessary to keep the DODIN/DISN operational 24/7. O&S efforts do not include the implementation of large-scale network improvements and changes. Sustainment will consist of adjustments to the infrastructure (e.g., card replacements, read-only memory replacements, or software and hardware upgrades of existing equipment).

GSM-O II will replace the GSM-O contract. To date, GSM-O has been leveraged by DISA to acquire the services necessary to carry out the day-to-day operations and sustainment of DISA’s networks and related services. GSM-O

II will continue to provide this support, ensuring the DODIN/DISN meets the needs of its customers and supports both contingency and peace-time operations.

4. Objectives: GSM-O II provides the support necessary to carry out the day-to-day operations and sustainment of the DODIN/DISN, DISA Data Centers and related services. The core telecommunications and IT Services capabilities supported by GSM-O II enable the warfighter to meet operational needs by providing world-wide telecommunications, IT Services, supporting natural disaster relief, and conducting humanitarian assistance in peace time crises, regional conflicts, and at the same time executing on-going strategic deterrence activities. In addition, the Government seeks to achieve seamless and efficient processes for integrating all costs of services due to GSM-O

II efforts to allow an accurate allocation of those costs to users, to support improved accuracy, and to promote a reduction in the costs of subscription services over time.

Key Objectives for GSM-O II:

1: Use tools to enhance and automate event correlation – The Government needs to know which events and alarms to key on, where problems are located, and who/what customers are impacted

2: Autogenerate tickets, particularly on significant and major events

3: Enhance application and user experience monitoring – provide the capability to identify when users have problems and what services are impacted

4: Automate Defensive Cyber Operations and implement Data Parsing – Use automation to effectively sort and analyze data sets (which are large and difficult to manage) in a timely manner, so as to provide value to event responses

5: Integrate ticketing systems and service desks that are both upstream and downstream of GSM-O II

6: Use efficiencies and automation to continually reduce manual labor to operate and maintain the DISN.

5. Scope. In addition to supporting the day-to-day operation and sustainment of DISA’s networks, Data Centers, and related services, GSM-O II will provide services designed to improve DODIN/DISN operations and make network operations more efficient and effective, to include cybersecurity activities and computer network defense initiatives. Additionally, the GSM-O II contract will provide support to a wide variety of technical initiatives that have been or will be integrated into the DODIN/DISN, including those migrating from GSM-ETI and GSM-P&S efforts. Standalone and companion network activities, such as those supporting the Missile Defense Agency, may also be supported by the GSM-O II contract. Emerging activities, including aspects of DISA’s ecosystem construct, may be supported by GSM-O II, enabling a more efficient approach to agency-wide network operations and sustainment. Finally, GSM-O II will embrace network modernization initiatives and support a proactive approach to network operations and sustainment, including the integration of an enhanced tool suite and enabling synchronized approaches with other DISA enterprise stakeholders.

5.1 Functional Scope:

a. The functional scope of this effort includes requirements that provide the following sets of capabilities needed to support DISA-provided networks and infrastructure:

Program Management to enable and support the contractor’s task execution.

Transition capabilities to ensure that DISA-provided DISN services support is smoothly transferred from the previous service contractor to the GSM-O II contractor.

Network Operations capabilities, including the following task areas:

o Order Processing and Service Activation o Incident and Problem Management o Configuration Management o Performance Management o Network Operations, Operational Engineering, Administration & Security o Network Maintenance and Repair o Integrated Operations Support o Support to Government Development of Networking Capabilities, Network Operations Centers, and OSSs o Contingency/Emergency Response capabilities to provide comparable support under variable execution conditions o Network Active-Active Support

Cybersecurity required capabilities including the following Cybersecurity Service Provider (CSSP)

Activities:

o CSSP Protect o CSSP Monitor, Analyze and Detect o CSSP Respond o CSSP Sustain

Cybersecurity for the DISN o Protect o Monitor, Analyze and Detect o Respond o Sustain

User Selected Services required capabilities: includes a set of customer services that are qualitatively superior to those currently available as part of the DISA- provided DISN services subscription, and will be made available to customers as the requirements become known and are funded.

b. To clarify the PWS functional scope, as depicted in Figure 1, some networking activities critical to overall effectiveness of DISA-provided DISN/DODIN services are executed in the GSM context by the GSM-O II contractor, while other activities are executed by other contractors, with the goal of integrated support.

Examples of activities include the following:

Deployment of new capabilities originally developed by a GSM-ETI contractor shall be implemented by the GSM-O II contractor.

Technology Refreshment actions for both hardware and software capabilities will be implemented by a

GSM-ETI contractor and activated by the GSM-O II contractor.

Resolution of hardware troubles and associated repair actions shall be initiated by the GSM-O II contractor and may require support from a GSM-ETI contractor.

The functional capabilities prescribed in this PWS shall be applied to the DISA-provided DISN/DODIN infrastructure that is installed and used worldwide.

5.2 Technical Scope:

a. GSM-O II support shall be provided to the following named network/system capabilities, at a minimum

(additional details will be provided as GFI):

CENTRIXS Cross Enclave Requirement (CCER)

Customer-controlled (non-DISN) networking capabilities

Data Communications Network (DCN)

Defense Message System (DMS)

Defense Red Switch Network (DRSN including Voice over Secure Internet Protocol (IP) (VoSIP)

Defense Research and Engineering Network (DREN)

Defense Switched Network (DSN) Voice over IP (VoIP) on DISA supported IP based networking services

(DISA managed portion only)

Designated DISN Transport capabilities (circuits) (excluding leased circuits)

DISN Enhanced Mobile Satellite Services (EMSS)

DISN encrypted traffic (if necessary)

DISN Leading Edge Services (DISN-LES)

Global Video Services (GVS)

DoD Messaging Capabilities

Gateway Service Desks (3 regions)

GIG Control Network (GCN)

Ground-based Midcourse Defense (GMD) Communications Network (GCN)

GSM-OSS capabilities

Internet Access Point Network (IAPNet)

IP Converged Solution Support—Everything over IP (EoIP) Evolution

Leased transport circuits

DoD Mobility Classified Capability (DMCC), Mobility Unclassified Capability (DMUC), and DoD

Enterprise Classified Travel Kit (DECTK) (for DMCC and DMUCNon-classified but Sensitive Internet

Protocol Router Network (NIPRNet)

Secret Internet Protocol Router Network (SIPRNet)

Secure Mobile Environment Personal Electronic Device (SME-PED)

Timing and Synchronization (T&S) assets

Unified Capabilities (UC)

Joint Regional Security Stack (JRSS) Operations, Maintenance, and Integration

DISN De-Militarized Zone (DMZ) capabilities for the Combined Enterprise Regional Information

Exchange System (CENTRIXS) Network DMZ:

o DoD DMZ o Federal (FED) DMZ, o Globally Reaching Interactive Fully Functional Information Network (GRIFFIN) DMZ o Multinational Information Sharing (MNIS) DMZ o NIPR DMZ, o Releasable (REL) DMZ o SIPR DMZ

Cloud cybersecurity services support for all variants (IaaS, PaaS, SaaS, Levels 1, 2, 3, 4, 5, and 6) as required by the Cloud Computing Security Requirements Guide (SRG)

All other capabilities and locations as required to protect and defend the DODIN

b. Detailed asset and performance data pertaining to the PWS scope are contained in the classified addendum

(via a DISA SIPR DEPS site) to this PWS.

c. The specific system and site-by-site networking capabilities to be supported by each GSM-O II TO will be identified by the GSM asset inventory data to be provided with specific TO(s) as historical information. Note that this will change as DISN capabilities evolve over the life of the GSM-O II contract.

d. Some capabilities that are provided by third party service providers do not require hands-on repair and maintenance services; those capabilities will be identified in each applicable TO.

5.3 Administrative Requirements

No deliverables will be required under this PWS. Deliverables will be defined and required at the TO PWS level.

5.3.1 General Requirements

a. Functional Requirements: GSM-O II network operations, maintenance and security services are required to be performed on the Government-designated installed networking infrastructure as located in Government-designated sites and facilities. The contractor may use the Government’s GSM-OSS in the performance of operations and support activities. The contractor shall introduce tools in accordance with section 6 of this

PWS.

b. Coordination of Execution Outcomes: The GSM-O II contractor will be directed by the Government to coordinate and interact with other contractors who support DISA's mission and as such will be required to incorporate Government-accepted capabilities into the DISA-provided DISN/DODIN services configuration baseline as deemed appropriate by the GSM-O II Program Manager (PM). When the Government accepts new capabilities that are the result of work by another contractor, and incorporates those capabilities into the

DISA-provided DISN/DODIN services configuration baseline, the GSM-O II contractor shall then become responsible for operation, security, maintenance and repair actions of those capabilities.

c. The contractor shall comply with DISA training, reporting, security, and personnel requirements. These include but are not limited to Personnel Access Management (PAM) reporting, security training, and safety training.

d. For overseas locations, the contractor shall manage all customs processes to include preparing custom documentation and shipping and receiving materials, equipment and parts.

e. Enabling Facilities: As specified by the applicable TO, the contractor shall provide temporary to long term storage/staging facilities to accomplish the receipt, inventory, integration and shipping as/when needed to accommodate the receipt and protection of materials being received pending the receipt of further materials, and shall also provide enabling work space as may be needed to accomplish the requirements of the TO.

f. Due to changes in the organization of DoD, specific titles (e.g., Commander JFHQ-DODIN) are subject to change. Such titles shall be interpreted in the PWS as meaning, “… or the successor to this office, if applicable."

g. The contractor shall provide support to IPv6 and similar initiatives from The Office of Management and

Budget (OMB) and other authoritative sources. DISA points of contact will provide necessary implementation guidance applicable to the contractor's service as GFI.

h. The contractor shall organize its workforce to align with the DoD-applicable Information Technology

Service Management (ITSM) service areas and ensure appropriate lines of communication are established to respond to Government needs.

i. Throughout the period of performance, the Contractor shall organize its workforce to align with the following:

DoDI 8440.01 DoD Information Technology (IT) Service Management (ITSM), dated December 24, 2015

The DoD Enterprise Service Management Framework (DESMF), dated June 22, 2016

5.3.2 Mission Constraints on Operations, Administration and Maintenance Execution

a. Network Tools – The contractor shall establish and implement Network tools in accordance with PWS

Paragraph 6.2.4 – Support to Network Operations Centers and OSS (OSS).

b. Active-Active – The contractor shall implement the Active-Active continuity of operations construct

c. The contractor shall provide on-site support at Government locations in order to effectively and efficiently deliver GSM-O II outcomes. The contractor shall utilize contractor-owned spaces, as approved by the

Government, to support ongoing GSM-O II activities and an efficient and cost-effective manner.

d. The contractor shall provide maintenance coverage for designated DODIN/DISN infrastructure equipment and software. The contractor shall provide coverage to meet Service Level Agreements (SLAs) with no gaps.

e. The contractor shall perform the activities described in this PWS in a manner that enables any new action

(e.g., a new request, a trouble-induced action, a maintenance action) to be “rolled back” (i.e., to reinstate the network configuration and the operational state from which such action was started) when directed by the

Government.

f. The contractor shall cease all actions on network support upon Government direction of a network “freeze” condition (see Appendix A for definition).

g. The contractor shall provide to the Government, as needed, read-write access to all network elements (NEs) being supported. The Government will provide as GFI, and maintain, the list of such authorized staff.

h. The contractor shall use the DISA Approved Products List (APL) and associated oversight processes when specifying or purchasing equipment for use in repair and similar functional activities.

i. Individual TOs may include additional constraints specific to the work performed.

j. Operational Support agreements with telecommunications, server, and services developers remain in effect and shall be used for technician dispatch for faults that are identified in elements of the DISA-provided

DISN/DODIN services that are not under direct contractor control.

k. All changes shall conform to DISA approved Change Management processes and be approved by the DISA

Change Advisory Board (CAB). The contractor can assume that a Standard Change action conforms to DISA

CAB guidance, hence no further CAB action is required. Other-Than-Standard actions may require CAB action for work to proceed.

l. Configuration changes shall be coordinated with DISA’s mission partners and the Designated Accreditation

Authority. Configuration change processes will be further articulated at the TO level.

m. The contractor shall provide all equipment associated with, or required for, the execution of a TO, except for items having unit cost greater than $10,000.00. The Government will approve the procurement of such equipment prior to its procurement. Such equipment shall become Government property if/when installed in the DISA-provided DISN/DODIN services infrastructure. The Government may, at its discretion, use various other sources, including separate contract sources, for the procurement of equipment to be installed; in such situations the equipment shall be managed as Government Furnished Property (GFP).

n. Items of telecommunications/IT equipment and associated integral components having unit cost greater than

$10,000.00 will be procured by the Government and provided to the contractor for installation/implementation and transition, in accordance with the TO. The Government will update this cost threshold, as appropriate.

o. Equipment installed at DISA-provided DISN/DODIN services interface points shall comply with existing

DISA-provided DISN/DODIN services architecture, GSM-OSS, and Authority to Operate (ATO).

Additional instructions and information will be provided as GFI at the TO level. This shall not restrict how the service external to the DISA-provided DISN/DODIN Services-owned components (Military Departments or Defense Agencies) is performed (commercial vendor cloud). Equipment and software installed on the

DISA-provided DISN/DODIN services side of the extended demarcation point shall become Government property.

p. When the Government accepts a new networking capability into the installed DISN infrastructure, for subsequent operation and sustainment by the GSM-O II contractor, the Government will provide, as added

GFI, the manufacturer’s recommended spare parts lists, user manuals, operator guides, and training materials, as applicable, that are associated with the newly-installed capability.

q. Actions that may require a visit to a Government site to perform duties of the contract shall be coordinated in advance of the visit in accordance with the Government access procedures provided as GFI.

5.3.3 Definitions

Appendix A provides definitions that are applicable to all TO work under this PWS.

5.3.4 Directives and Instructions

Appendix B provides directives and instructions which shall be applicable to the GSM-O II effort and are included as constraints in this effort. The PWS provides the contractor with flexibility to conceive and propose innovative approaches and solutions. However, in some cases, there may be constraints that the Government must place on those solutions.

5.3.5 Required Data Inputs

The Government requires that the contractor provide data inputs (called Data Capture Records) to established tool repositories, and provide data records (called Data Extracts) of accomplished tasks in a manner that can be directly viewed by the Government. These data inputs and extracts are actions that shall be performed by the contractor during required tasks using Government-directed tools (some of which will be part of the GSM-OSS). These data inputs will be defined at the TO level, including applicable Contract Data Requirements List (CDRL) items.

5.3.6 Reporting

The contractor shall provide GSM-O II contract level reporting, as defined in Section 11 of this PWS.

5.3.7 Cost Management and Reporting

The contractor shall maintain accurate records of the costs of services provided for each DISA managed network and service. Applicable standards from the Acceptable Levels of Performance (ALP) at the TO Level shall be used to manage cost for services. The contractor’s invoicing procedures shall be prompt.

The contractor shall identify and recommend potential productivity improvements and cost efficiency recommendations that can be implemented throughout the term of the contract and TOs to reduce cost. The contractor shall report the achieved results of efficiencies gained by the Government quarterly.

5.3.8 Business Performance-Related Metrics

a. The contractor shall recommend, for Government approval, business performance metrics as required per TO.

Examples could include the following:

Number of invoices within the preceding 12 months that were late (i.e., outside the 30-day submission period).

Percentage of assigned contractor or subcontractor staff having all required security clearances.

Percentage of reported outages during past quarter/year where the required repair parts and materials were not available within the required time limit specified at the TO Level.

Analysis of inventory levels of spare/repair parts within the contractor’s control to ensure that response times are met while holding inventory costs to a minimum.

Analysis of staff travel associated with outage repair activities to ensure appropriate balance between full-time staffing at hub locations and “get-there” responses to reported troubles.

b. The contractor shall provide a Performance Management Working Group to coordinate changes to ALPs, re-view ALPs, and adjust the performance baseline metrics to ensure end-user satisfaction. The Performance

Management Working Group will meet monthly or on an as needed basis. The Performance Management

Working Group shall yearly review the ALP thresholds, adjusting thresholds as needed when ALPs are continuously met or exceeded.

c. The contractor may introduce ALP revisions intended to increase efficiencies and drive down costs. Any savings realized through these revisions may be shared between the contractor and the Government.

5.3.9 Performance Based Management

a. The contractor shall employ a yearly financial analysis developing basis of estimates to take advantages of efficiencies and to identify inefficiencies.

b. The contractor shall employ periodic lean and process improvement events (i.e., Lean Six Sigma, Kaizen activities) with cross-functional teams to examine requirements within specific or identified areas in order to accomplish certain functions with more efficiency (better, faster, and cheaper).

5.4 Task Areas:

GSM-O II Task Areas:

Task Area 1 – Transition

Task Area 2 – Operations and Sustainment

Task Area 3 – Maintenance and Repair

Task Area 4 – Cybersecurity

Task Area 5 – Joint Force Headquarters DODIN Support

Task Area 6 – DISA Command Center (DCC) Support

Task Area 7 – Joint Customer Support

Task Area 8 – Operational Support System (OSS)

Task Area 9 – Innovations and/or Optimizations

Task Area 10 – Premium Services (e.g., White House Communication Agency (WHCA), Africa Command

(AFRICOM), Army Central (ARCENT))

Task Area 11 – Data Center Operations

Task Area 12 – Program Management

Task Area 13 – Overseas Support

Task Area 14 – Logistics Support

Task Area 15 – DoD IT Reform

6. Performance Requirements.

a. The contractor shall provide GSM-O II service capabilities under three related but separate sets of mission conditions, as follows:

Stable (but not static) conditions

Contingency/Emergency Response conditions

Active / Active Operating Model

b. The contractor shall provide GSM-O II service capabilities as described in this PWS, including all subparagraphs thereof, under various implementation modes of execution, as described in Table 1, based on the criteria of the “Standard Change” definition. The implementation modes are as follows:

Some requested work, if it exceeds the criteria of the Standard Change definition, will be transferred by the

Government for support via a non-GSM-O II source of support.

Some requested work will remain GSM-O II work but will be executed via Other-than-Standard procedures. In these situations, Standard Change procedures are not applicable, in order to give the

Government a greater degree of control over the required process outcome. Note that, as a mode of implementation, an Other-than-Standard work outcome is not different per se, but the degree of

Government participation is. The Government may, at its option at any time, change the category of work from a Standard Change action to one under this paragraph, by notification to the contractor by an authorized Government person (e.g., by a COR or comparable authority.)

Requested work, if it satisfies all of the criteria of the Standard Change definition below, will be categorized as Standard Change work and shall be performed by the contractor via that activity path.

c. Standard Change: A Standard Change is defined as the actions that the contractor may execute on its own, without discretionary approval of the Government, to accomplish the following functional outcomes. Note that actions other than those described below require a Government determination as to how to proceed (i.e., an uncertain situation is not within the scope of Standard Change by default). Standard Change actions apply to the following:

I. Order Processing & Service Activation (formerly referred to as “request fulfillment”): The contractor may immediately work to fulfill a Request For Change (RFC) provided that such work satisfies ALL of the following:

a) Must follow approved Government PWS guidance (e.g., for use of the DISA APL)

b) Does not result in changed facility support requirements (e.g., floor space footprint, HVAC, power)

c) Does not change backbone at the applicable DISN point of presence

d) Does not involve contingency/emergency support as described in PWS paragraph 6.3

e) The requesting DISN customer has provided approval in accordance with DISN Order

Processing & Service Activation procedures.

II. Trouble resolution/repair actions: The contractor may immediately work to repair a trouble provided that such work satisfies ALL of the following:

a) May repair or replace equipment on a one-for-one basis as needed, for items of equipment up to and including an individual chassis

b) Plus: criteria (a) – (f) from item I, above

III. Service restoration actions (i.e., workarounds while repairs are being made): The contractor may immediately work to restore services provided that such work satisfies ALL of the following:

a) Same as item II.

IV. Maintenance actions: same as item I, criteria (a)-(f).

d. Table 1 provides a decision rule table, based on the definition of “Standard Change” (see Appendix A) indicating which source or PWS requirement will be used by the Government to obtain GSM support.

Table 1. GSM Work Allocation Table

GSM Work Assignment/Allocation Table

Read top to bottom in sequence

Step Criterion YES NO

1 Support not in GSM-O II scope: Does the work involve Program/ Admin

Support; Software development/modification; Training

Services?

Refer to Government

COR for support via non-GSM-O II Sources:

e.g., GSM-P&S

Go to step 2

2 Support not in GSM-O II scope: Does the work involve engineering design and implementation of new DISN capabilities?

Refer to Government

COR for support via non-

GSM-O II Sources e.g., GSM-ETI

Go to step 3

3 Within GSM-O II scope: Has the

Government declared the work to be

Contingency or Emergency Response work (PWS 6.3)?

Refer to Government

COR for Support via a

GSM-O II (Other-Than-

Standard mode) or other

Government-designated source

Go to step 4

Step Criterion YES NO

4 Within GSM-O II scope: Is this COOP support work (PWS 6.4)?

Execute as applicable in the Other-Than-Standard work mode

Go to step 5

5 Is the work any of the following:

a. Order Processing & Service

Activation work

b. Trouble Management (Repair or

Restoral) work

c. Maintenance work

Go to step 6A Go to step 10

6A Does the work require changes in facilities, floorspace footprint, power/HVAC? E.g., new node; new equipment?

Refer to Government

COR for Support via

GSM-ETI or other

Government-designated source

Go to step #6B

6B Does the work change backbone bandwidth (see definition Appendix A) at the applicable DISN point of presence?

Refer to Government

COR for Support via

GSM-ETI or other

Government-designated source

Go to step #6C

6C Are any requested/needed equipment/capabilities not on the DISA

APL?

Refer to Government

COR for Support via

GSM-ETI or other

Government-designated source

Go to step #6D

6D Has the Government declared that this work is to be done as an Other-than-

Standard action via PWS 6?

Execute as an Other-than-

Standard action

Go to step #7

7 Within GSM-O II scope: Is this Order

Processing & Service Activation (PWS

6.2.1)?

go to step #7A Go to step 8

7A Has the requesting DISN customer provided approval in accordance with

DISN Order Processing & Service

Activation procedures?

Perform GSM-O II

Standard Change action:

PWS 6.1.2a(3

Execute as an Other-than-Standard action

8 Within GSM-O II scope: Is this Trouble

Management (Repair or Restoral) work

(PWS 6.2.2)?

go to step #8A Go to step 9

8A For repair or restoral/workaround actions: does it involve replacement of an item beyond the range of items of equipment up to and including an individual chassis?

Execute as an Other-than-

Standard action

Perform GSM-O II

Standard Change action:

PWS 6.1.2a(3)

9 Within GSM-O II scope: Is this

Maintenance work (PWS 6.2.6)?

Perform GSM-O II

Standard Change action:

PWS 6.1.2a(3)

Go to step 10

10 Within GSM-O II scope: Does the work activity involve any of the following?

Execute as applicable in the Other-Than-Standard

Stop. Review facts of situation.

Step Criterion YES NO

a. Program Management work (PWS

6.12)

b. Transition work (PWS 6.1)?

c. CM work (PWS 6.2.3)?

d. Ops Center Support work (PWS

6.2.4)?

e. OSS support work (PWS 6.2.4)?

f. Performance Management work (PWS

6.2.5)?

g. Network Integration work (PWS

6.2.7)?

h. Support for Govt Functional

Applications (PWS 6.2.8)?

i. Cybersecurity work (PWS 6.4)

j. DMS work (PWS 5.2)

k. User Selected Services work (PWS

6.7, 6.10)?

l. Integrated Operations Support work

(PWS 6)?

work mode (by PWS definition)

Steps 1-10 cover all logical paths

e. The contractor shall provide support to operate and sustain DISA-provided DISN services capabilities under

GSM-O II “Stable” conditions. Stable (but not static) conditions are the overall norm of DISA-provided

DISN services global activities, characterized by planned activities that are budgeted and coordinated prior to execution. This condition state reflects the fact that overall DISA-provided DISN services capabilities are intended to be operated indefinitely into the future, with continuing changes driven by mission tasks and technology evolution.

6.1 Task Area 1 – Transition. The contractor shall oversee and execute all transition planning and transition activities required to enable successful operations of GSM-O II systems within six (6) months of contract award.

The contractor shall conduct all efforts needed to correct any issues or deficiencies that occur during the transition process. Transition activities shall occur following the award of the GSM-O II Indefinite Delivery, Indefinite

Quantity (IDIQ) Operation and Sustainment of the DODIN/DISN Infrastructure TO and Maintenance and Repair of the DODIN/DISN infrastructure TO..

6.1.1 Subtask 1.1 – Transition Planning: The contractor shall plan for an effective transition from the incumbent.

Transition planning shall include schedule planning, resource planning, and test and evaluation planning. The contractor shall provide effective communication with the Government, including presenting the transition plan and providing regular updates. Communication shall include discussions that ensure effective Government oversight, including discussions of tasks, progress, constraints, dependencies and issues.

a. To ensure that both Government and contractor understand the terms of the contract, as required by TO, the contractor shall organize and present a one-time Contract Initiation Review (CIR) of the contract’s or TO’s terms, objectives, tasks, constraints, standards, and deliverables. The CIR shall address at minimum the following topics:

Government objectives and requirements as documented in the solicitation.

The purpose, content, structure/format, media, and submission schedule of each deliverable (CDRL) to be provided as a result of activities of the PWS.

The structure of Contract Line Item Number (CLIN) items and tasks driving contractor performance for the first year.

Data and resources needed by either side as conditional prerequisites to complete the design of deliverables and the execution of initial tasks.

A list of issues to be resolved by each side within the first 30, 60, and 90 days of contract execution.

See Operations and Sustainment of the DODIN/DISN TO Transition Task for timing and execution of CIR

b. To establish an appropriate and effective transition environment immediately following award of the contract, as required by TO, a Transition Plan shall be submitted as a deliverable to provide the basis for the execution of all transition activities throughout the transition period. Attributes of the Transition Plan include the following:

The Transition Plan shall use a contractor recommended design and format, include the activities of the

CIR requirements as described above, and be submitted for Government review and approval within 3 weeks of contract start date (as established by the Contracting Officer).

As part of the Transition Plan, within 30 days after assuming responsibility, the contractor shall schedule an independent test and evaluation period lasting up to one week, within each Region on a phased basis, to assess the Government’s and contractor Staff’s ability to meet the PWS standards, within 30 days after assuming responsibility. This requirement may be individually waived by the Government.

The Transition Plan shall account for possible Government-directed Performance Acceptance Test (PAT) execution, at the Government’s option.

As part of the Transition Plan, the contractor shall schedule regional transitions (to be completed no later than 180 calendar days after contract award) to minimize risks associated with Transition. This requirement may be validated by the Government through acceptance of the Transition Plan.

As part of the Transition Plan, the contractor shall include a Transition Readiness Checklist to ensure execution of all transition preparation activities.

The Transition Plan shall contain the contractor's staffing strategy to include the goal for incumbent rehiring.

The Transition Plan shall include the contractor's identified transition risks and mitigation plans to ensure a low risk disruption to operations.

As part of the Transition Plan, the contractor shall provide a communications approach for both outreach and in reach communications. Attributes of the Communications approach include the following:

o The contractor shall provide a communication mechanism (e.g., war room) for transitioning employees, new hires, Transition Team members, and DISA if issues arise.

o The CIR agenda shall be developed by the contractor for Government approval. The CIR shall be conducted at a Government-approved facility. All named key personnel of the contractor team shall attend. The contractor shall submit draft sample deliverables, for coordination of content and format, for Government review one week prior to the CIR. The Government’s target is to have the

CIR presented within 3weeks following award of the contract and applicable TOs.

6.1.2 Subtask 1.2 – Transition Execution: In accordance with the approved Transition Plan, the contractor shall execute all transition activities required to ensure that services are smoothly transferred from the incumbent service contractor to the GSM-O II contractor.

a. During the Transition Period, the contractor shall provide the following:

Executive oversight support from the Program Executive and Executive Steering Committee during transition.

A dedicated transition manager to execute the Transition Plan and ensure Government objectives and requirements agreed to at the CIR are met during transition.

Conduct a Transition Readiness Review prior to the official cutover of each site to demonstrate readiness.

Implement a Soft Launch of the Transition Plan to ensure that unforeseen issues that may inhibit the employees' ability to perform their work are identified prior to each regional cutover.

Utilizing a Step by Step Deployment Preparation Process, successfully deploy qualified personnel into outside the Continental United States (OCONUS) environments and address and mitigate risks in meeting

Status of Forces Agreement (SOFA) requirements and Host Nation Laws and Regulations.

Deploy a Program Integration Team to ensure the successful transition of in process projects with the

Government as well as the GSM-ETI and GSM-P&S teams.

b. Within the Transition Period, as required by TO, the contractor shall develop and provide a Transition schedule that will have the capability for real-time tracking and access of transition information in a SharePoint site within a centralized location that must be accessible to the Government. Capability should include the ability to view current staffing levels, work plans, skill sets, assignments, and metrics information related to transition activities.

The contractor shall make the Transition schedule and SharePoint accessible to the Government via a GSM-O II

SharePoint portal or an alternative means that the Government can access. DISA will not pay for an outside tool or portal. The contractor shall provide and utilize:

Scheduling tools in support of the development of the Integrated Master Schedule to communicate key milestones and deliverables.

Communications Planning Tool to track the communications process during Transition.

Transition Readiness Checklist which a mechanism to provide status on Transition activities.

Risk/Enhancement Management System Tool (REMS) and Transition issue and risk tracker to proactively manage risks and issues daily throughout transition.

Governance Reporting Template providing a consolidated view of key activities, timelines, and issues through-out all Transition Work stream efforts.

Employee Staffing Dashboard to communicate the positions that are filled by either incumbent or newly-hired employees.

c. Within the Transition Period, the contractor shall provide a training program and employee training plan to delineate the training requirements for each employee including:

DISA Change Management Process Training as changes to the technical environment, operational processes, contract or organization occur during Transition.

Customer-specific training to enhance customer service and program performance.

The contractor shall execute post-award transition preparation actions in the following areas: requirements traceability and validation; draft deliverables; CLIN Structure and Tasks documentation; information/resources needs; and risks/opportunity identification and work off plans

6.1.3 Subtask 1.3 – Transition-out Support: The contractor shall plan for and effectively support transition to a follow-on contractor at the end of the GSM-O II contract. The contractor shall affect an orderly and efficient transition to a succeeding vendor. A Transition-Out Plan shall be provided in conjunction with contract transition-out activities. Upon notification by the Government the contractor shall provide a list with the total number and names of employees performing on the Contract, outlining any applicable suitability and certifications expiration dates in preparation of a new solicitation for follow-on services. During the transition-out process, the contractor shall turn over all required incumbent equipment inventory, deliverables, training certificates, test plans, test reports, test scripts, suitability information and security records. The contractor shall transfer all hardware, software, and technical data to the follow-on contractor. The contractor shall provide GSM-O II subject matter expertise to the follow-on contractor throughout transition-out period.

6.2 Task Area 2 – Operations & Sustainment

The contractor shall use standardized and optimized tool suites needed for network monitoring, network management, configuration management, and the execution of other GSM-O II functions. In cases where tools are provided as GFE, the contractor shall integrate these GFE tools into their approach. The contractor shall standardize tool sets to eliminate localized processes, extend network tools to a global environment, and minimize duplication of tool suite functionalities. The Government also must have access and training of these tools and may be integrated to/from other Government tools.

6.2.1. Subtask 2.1 – Order Processing and Service Activation: The contractor shall provide order processing and service activation support to include the full range of tasks and activities from initial receipt of a telecommunications customer requirement, processing the service order, order fulfillment, installation, test and acceptance, activation and deactivation, and service transition to include configuration management and release/deployment. The contractor shall apply workflow automation to ensure timely completion and monitoring of service activation activities.

6.2.2 Subtask 2.2 – Incident and Problem Management: The contractor shall continuously execute network monitoring and incident/problem resolution processes on a 24x7x365 basis. Incident and Problem Management includes the following, at a minimum:

Operational Help Desk (in accordance with subtask 2.8)

Record, assess, track, monitor, and escalate incident tickets created and escalated for incident/resolution for operational infrastructure.

Network Surveillance and Reporting

Incident and Fault Analysis

Fault Isolation

Network and Service Restoration

Fault Correction

Customer-Specific Technical Support

Situational Awareness and Reporting

6.2.3 Subtask 2.3 – Configuration Management (CM): The contractor shall monitor and control the configuration of assigned NetOps infrastructure including hardware, software, and inter-connecting transport facilities. The contractor shall perform activities including, but not limited to:

Configuration Management Planning

Configuration Identification

Configuration Control

Configuration Change Management

Configuration Status Accounting

Configuration Verification and Audit

Configuration Status Reporting

6.2.4 Subtask 2.4 – Support to Network Operations Centers and OSS: Within DISA-provided DODIN services networking sites including DISA NetOps Centers (DNC) facilities, the contractor shall provide support, on a continuing 24/7/365 basis, that assures the availability of the suite of applications, servers, and network devices that make up the OSS including:

Operations-Local Area Network (LAN) applications operation, Administration, maintenance and security functions, (to include Order Entry Systems).

The contractor shall support the GSM-OSS by providing the following capabilities:

Server and Application Operation Support

Operational LAN Support

Operational Data Communications Network (DCN) Support

GSM-OSS Baseline Support

GSM-OSS Information Sharing Interface Support

GSM-OSS Enclave Security

GSM-OSS Global Support Desk

GSM-OSS Tool Integration

The contractor may provide new tools and controls that would make operating the DODIN easier or more effective or results in some other positive improvement, to include a reduction in resources (i.e., FTE) required a reduction in tool complexity, and/or a reduction in costs. The contractor may also provide new configurations, modules, or licensing of current OSS tools which could result in a positive benefit for operating the DODIN, to include a reduction in resources required (i.e., FTEs), a reduction in tool complexity, and/or a reduction in costs.

All tools shall be appropriately tested and be approved by the Government prior to…