GSM-O Task Order-1 Final RFP 02-09-2011.pdf

HC1028-10-R-2000

Amendment 0001 i

GIG Services Management (GSM) – Operations (GSM-O) Task Order #GSM-O-01

Operation and Sustainment of the DISN Infrastructure

Based on GSM-O PWS

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

Task Order Number: (completed by the KO at time of TO award)

GSM-O Tracking Number: TO #GSM-O-01

Contents of this Task Order:

1 Task Monitors ………………………………………………………..……… 1 2 Task Order Title ………………………………………………..…………… 1 3 Background ………………………………………………………….……… 1 4 Objectives ……………………………………………………….………….. 2 5 Scope …………………………….……………………………….…..…….. 2 6 Performance Requirements ……………………………….……………… 3 7 Performance Standards ……………………………………….………….. 8 8 Incentives …………………………………………………………………… 9 9 Place of Performance ……………………………………………………… 9 10 Period of Performance …………………………………………..………… 10 11 Delivery Schedule ………………………………………………..………… 10 12 Security ……………………………………………………………………… 10 13 Government-Furnished Equipment (GFE)/Government-Furnished

Information (GFI) …………………………………………………………… 10 14 Other Pertinent Information or Special Considerations ……………….. 11 15 Section 508 Accessibility Standards ……………………………………… 13

Appendix A – Definitions …………………………………………………………… A-1 Appendix B – DISN System and Infrastructure Asset Inventory …………….… B-1 Appendix C – Government Furnished Equipment/Capabilities ……………...… C-1 Appendix D – Government Furnished Information (GFI) …………….………… D-1 Appendix E – Functional Requirements …………………………………….…… E-1 Appendix F – Table of Acceptable Levels of Performance (ALPs) …………… F-1 Appendix G – Contract Data Requirements List (CDRLs) Items ………..…..… G-1 Appendix H – List of Data Capture Reports and Data Extracts ….……….....… H-1 Appendix I – Draft QASP for this TO ……………….……………………….....… I-1 Appendix J – DD Form 1423 (CDRL) Set for this TO …………………….....… J-1

1. Task Monitors (TMs).

a. Primary TM.

Name: TBD

Organization: TBD

Department of Defense Activity Address Code (DODAAC):

TBD

Address:

Phone Number: TBD

Fax Number: TBD

E-Mail Address: TBD

b. Alternate TM.

Name: TBD Organization: TBD

DODAAC: TBD

Address: TBD Phone Number: TBD Fax Number: TBD E-Mail Address: TBD

2. Task Order Title.

Operation and Sustainment of the DISN Infrastructure

3. Background.

a. DISA provides networking support to its national security customers via GIG/DISN capabilities which are deployed and operated worldwide. GIG/DISN capabilities are functionally a system-of-systems entity that is in a continuing sustainment phase of its life cycle.

b. The Government (DISA) acts in the role of “the provider of DISN services” to its DISN customers; support from existing contract(s) contributes to this overall mission by outsourcing much of the labor effort needed to plan, evolve, operate and sustain the DISN capabilities. The GSM-O contract, and other GSM capabilities, will replace services from the existing DGS contract upon its expiration.

c. The GSM Program supports the GIG/DISN infrastructure (see definition in Appendix A of this Task Order (TO)) through the combined efforts of contractors from the following sources:

• Contractor support from the GSM-O contract (the basis for this TO), providing operation, sustainment and assurance of the DISN infrastructure

• Contractor support from the GSM-ETI multiple-award sources (the basis for the ETI TOs) which provide engineering and implementation services in support of the DISN infrastructure

• Contractor support from the GSM-P&S multiple-award sources which provide projects and support services in support of the DISN infrastructure

d. Contractor capabilities from GSM-O, -ETI and –P&S TOs are needed to succeed those from existing TOs from previous contracts (primarily the DGS contracts) as those contracts reach the expiration of their respective periods of performance.

e. The specific GIG/DISN system capabilities to be supported in this TO are as described in the Scope paragraph below.

4. Objectives:

The Contractor shall provide network support services, as described in paragraph 6, to satisfy the performance standards stated in paragraph 7 of this TO. The services are necessary on a continuing basis to enable the Government to provide DISN services to DISN customers.

5. Scope.

a. As detailed in paragraph 6 below, the Contractor shall provide network support services by performing the functional activities that are described in the following GSM-O PWS sub-paragraphs:

• 4 Program Management Activities

• 5 Transition Activities

• 6.2.1 Order Processing & Request Fulfillment

• 6.2.2 Trouble Management (except repair actions: see paragraph 5c of this TO)

• 6.2.3 Configuration Management (CM)

• 6.2.4 Support to Network Operations Centers and Operational Support Systems

(OSS) (except repair/maintenance actions: see paragraph 5c)

• 6.2.5 Performance Management

• 6.2.6 Network Maintenance, Operational Engineering, Administration and

Security (except repair/maintenance actions: see paragraph 5c)

• 6.2.8 Support to Government Development of Functional Applications

• 6.4 COOP Execution

b. Note: Requirements of PWS paragraph 3 are not cited in the list above because those requirements, which apply to the performance of this TO, are all addressed by portions of this Task Order template. Requirements of PWS paragraphs 6.2.7, 6.3 and 7 are addressed in separate task orders.

c. In the current DGS environment, the DGS contractor, at the Government’s request, has established and re-awards annually, with no break in coverage, Maintenance Agreements with equipment manufacturers to provide certified parts and repairs for GIG hardware and software. The DGS contractor is the party to these agreements and includes their costs within its invoiced billing to the Government. All of the agreements are for 12-month periods of support, renewed annually effective January of each year.

To preclude costs of early termination of these agreements, the Government is requiring the current DGS contractor to continue to provide repair/maintenance support to the entire DISN infrastructure through the end of the applicable Agreement period of performance. It is anticipated by the Government that this GSM-O TO will have been issued to the new GSM-O Contractor at a date prior to mid-2012. To facilitate this split in the commencement of support by the GSM-O Contractor, the total set of work described by PWS paragraph 6.2 has been split into two task orders: this TO orders the work described above, and a second TO (“Maintenance and Repair of the DISN Infrastructure”) orders the work associated with repair/maintenance support as described in the applicable portions of PWS 6.2.2, 6.2.4, and 6.2.6 as noted above. That second TO will contain instructions to have the support start date arranged to be aligned with the re-award of the Agreements by the GSM-O contractor. The portions of the PWS cited have not been separated out into “Non-Maintenance Work” and “Maintenance Work” because the flow of trouble management and operational support needs to be integrated as described in the PWS. When both TOs are operative it will not be a source of confusion to the GSM-O contractor; it does result in different commencement dates for work in the first year. As noted in PWS paragraph 6, initially the GSM-O contractor shall execute the support described in this TO by coordinating with the DGS contractor for repair/maintenance support as necessary until the GSM-O TO for Maintenance and Repair becomes operative.

d. With respect to network maintenance and repair activities, where an existing Maintenance Agreement is not controlling, the Government may decide to utilize unallocated equipment from existing GFE; in which case the Contractor’s proposed materials list for that action will be reduced accordingly.

e. The functional activities of this TO shall be executed in support of the named DISN system capabilities, and the specific DISN infrastructure capabilities that enable those systems, as described in TO Appendix B, plus new or modified capabilities as ordered by the Government during the period of this TO. TO Appendix B data is at the site-by-site level of detail and is contained in the separate classified addendum (a CD-ROM) to this TO.

6. Performance Requirements.

The performance requirements of this TO are derived from the corresponding requirements of the GSM-O PWS. The requirements described below are subject to the following conditions:

• The definitions stated in Appendix A of this TO shall be applicable to all task work.

• The Contractor is required to use the Government’s Operational Support Systems (OSS) as applicable in the performance of this TO.

6.1 Program Management Requirements

The Contractor shall satisfy the requirements of Appendix E paragraph 4, including all subparagraphs thereto, of this TO.

6.2 Transition Requirements

a. The Contractor shall satisfy the requirements of Appendix E paragraph 5, including all subparagraphs thereto, of this TO.

b. The scope of the Contract Initiation Review, responding to Appendix E paragraph 5.1, shall be based on the scope of work of this task order (i.e. TO tasks 6.1 and 6.3 including all subordinate paragraphs thereto, and 6.4). There will be CIR-related activities in the other GSM-O task orders; those activities may be combined if scheduling permits; the Government’s intent is to provide complete coverage of all PWS activities with minimal duplication of start-up actions.

c. The scope of the Transition Plan and its execution, responding to Appendix E paragraphs 5.2 and 5.3, shall be based on the scope of work of this task order (i.e. TO tasks 6.1 and 6.3 including all subordinate paragraphs thereto, and 6.4) that the Contractor recommends be subject to verification as the basis for commencing actual work. The Government’s intent is that transition-related activities be eventually planned and executed in an integrated effort where conditions permit.

6.3 Network Operation, Administration, Maintenance and Security (OAMS)

The Contractor shall provide support under this TO task in four parts, to align the work on a regional basis, for the CONUS, Europe, SWA, and Pacific regions respectively.

Within each regional subtask, the nature of the functional requirements is the same (e.g.

trouble management activities are performed in the same manner and under the same performance standards in all regions); the specific DISN systems and infrastructure in each region to be supported are as described in Appendix B of this TO.

6.3.1 Network OAMS for Region-1 = CONUS

The Contractor shall provide OAMS capabilities in support of applicable DISN infrastructure located within the CONUS region.

6.3.1.1 Order Processing & Request Fulfillment:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.1, including all subparagraphs thereto, of this TO.

6.3.1.2 Trouble Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.2, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.1.3 Configuration Management (CM):

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.3, including all subparagraphs thereto, of this TO.

6.3.1.4 Support to Network Operations Centers and Operational Support Systems

(OSS):

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.4, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.1.5 Performance Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.5, including all subparagraphs thereto, of this TO.

6.3.1.6 Network Maintenance, Operational Engineering, Administration and Security:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.6, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.1.7 [Header not used this TO]

6.3.1.8 Support to Government Development of Functional Applications:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.8, including all subparagraphs thereto, of this TO.

6.3.2 Network OAMS for Region-2 = Europe

The Contractor shall provide OAMS capabilities in support of applicable DISN infrastructure located within the Europe region.

6.3.2.1 Order Processing & Request Fulfillment:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.1, including all subparagraphs thereto, of this TO.

6.3.2.2 Trouble Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.2, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.2.3 Configuration Management (CM):

6.3.2.4 Support to Network Operations Centers and Operational Support Systems

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.4, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.2.5 Performance Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.5, including all subparagraphs thereto, of this TO.

6.3.2.6 Network Maintenance, Operational Engineering, Administration and Security:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.6, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.2.7 [Header not used this TO]

6.3.2.8 Support to Government Development of Functional Applications:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.8, including all subparagraphs thereto, of this TO.

6.3.3 Network OAMS for Region-3 = South-West Asia

The Contractor shall provide OAMS capabilities in support of applicable DISN infrastructure located within the South-West Asia region.

6.3.3.1 Order Processing & Request Fulfillment:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.1, including all subparagraphs thereto, of this TO.

6.3.3.2 Trouble Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.2, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.3.3 Configuration Management (CM):

6.3.3.4 Support to Network Operations Centers and Operational Support Systems

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.4, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.3.5 Performance Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.5, including all subparagraphs thereto, of this TO.

6.3.3.6 Network Maintenance, Operational Engineering, Administration and Security:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.6, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.3.7 [Header not used this TO]

6.3.3.8 Support to Government Development of Functional Applications:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.8, including all subparagraphs thereto, of this TO.

6.3.4 Network OAMS for Region-4 = Pacific

The Contractor shall provide OAMS capabilities in support of applicable DISN infrastructure located within the Pacific region.

6.3.4.1 Order Processing & Request Fulfillment:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.1, including all subparagraphs thereto, of this TO.

6.3.4.2 Trouble Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.2, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.4.3 Configuration Management (CM):

6.3.4.4 Support to Network Operations Centers and Operational Support Systems

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.4, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.4.5 Performance Management:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.5, including all subparagraphs thereto, of this TO.

6.3.4.6 Network Maintenance, Operational Engineering, Administration and Security:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.6, including all subparagraphs thereto, of this TO. The Contractor shall coordinate with the DGS contractor for repair/maintenance support until such time as the GSM-O Contractor assumes that responsibility via separate task order, as discussed in TO paragraph 5c.

6.3.4.7 [Header not used this TO]

6.3.4.8 Support to Government Development of Functional Applications:

The Contractor shall satisfy the requirements of Appendix E paragraph 6.2.8, including all subparagraphs thereto, of this TO.

6.4 COOP Support

The Contractor shall satisfy the requirements of Appendix E paragraph 6.4, including all subparagraphs thereto, of this TO.

7. Performance Standards.

The performance standards applicable to the requirements of paragraph 6 of this TO are initially identified in the Appendix E activities to be controlled. The table of standards is provided at the end of the draft QASP at Appendix I of this TO.

8. Incentives

a. Incentive payments, as described in the QASP for this TO, are applicable to the following tasks of this TO:

TO

Paragraph

Incentive? Type Description

6.1 Yes QASP Perf

Incentive

Management

6.2 with all subparas thereto

Yes QASP Perf Incentive

Transition

6.3.1 with all subparas thereto

Yes QASP Perf Incentive

OAMS - CONUS

6.3.2 with all subparas thereto

Yes QASP Perf Incentive

OAMS - Europe

6.3.3 with all subparas thereto

Yes QASP Perf Incentive

OAMS - SWA

6.3.4 with all subparas thereto

Yes QASP Perf Incentive

OAMS - Pacific

6.4 Yes QASP Perf

Incentive

COOP

b. Specific required standards, metrics, measures, surveillance, and associated details including the composition of the incentive pool and how specific awards are to be made, are as described in the QASP.

9. Place of Performance.

a. Place of Performance: The duties of the GSM-O contractor shall be performed at Contractor Facilities (CF) and Government Facilities (GF). The list of sites where TO-1 support is required to be provided is shown at Appendix B to this TO. The use of Contractor facilities requires Government approval.

b. Alternate Place of Performance – Unforeseen Conditions: Contractor employees may be required to work at home, at another approved activity within the local travel area, or at the Contractor’s facility with Government approval, in cases of unforeseen conditions or situations (e.g., pandemic conditions, exercises, etc.). Any Government equipment such as laptops or phones provided to Contractor personnel shall be returned at a time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Monitor (TM) approval is required. The Contractor shall prepare all deliverables and other contract documentation utilizing Contractor resources. To the extent possible, the Contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the Contractor may request an equitable adjustment.

10. Period of Performance.

This TO period of performance is for a period of 365 calendar days after TO award. The Government, at its option, may extend the original period of performance.

11. Delivery Schedule.

a. The schedule for performance of service capabilities as described in Task Order paragraph 6 is continuous. Network Operations activities in Government Network Operations Centers are required to be performed on a continuing 24x7 basis.

b. Each task (sub-paragraph) of paragraph 6 above identifies (in TO Appendix E) the required services outcomes. Deliverables to be provided as evidence of required performance are also identified in each task and are listed in the table at Appendix G to this TO. Each CDRL is referenced to the task activity of this TO that requires it.

c. In addition (see PWS 3.7) 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 (most of which will be part of the GSM-OSS). Where such required data inputs and records are applicable, the TO Appendix E paragraph identifies these immediately following the identification of CDRLs. These required data inputs are listed in this task order at Appendix H.

12. Security.

a. Security shall be in accordance with the GSM-O DD254. Performance required by this TO will be up to the TOP SECRET level.

b. Security access requirements for each Government site to be supported will be provided as TO Appendix D GFI.

c. The contractor shall implement and adhere to security policies and classifications of the networks in accordance with the DISA and DoD classification guides.

d. Storage and reporting of information shall be in accordance with the classification guides. The contractor shall minimize security incidents.

13. Government-Furnished Equipment (GFE)/Government-Furnished Information

(GFI).

a. The Government will provide GFE to the Contractor for the Contractor’s use in the performance of this TO, as described in TO Appendix C.

b. GFI provided to enable the Contractor to perform under this TO is described in TO Appendix D.

14. Other Pertinent Information or Special Considerations.

a. Coordination of Execution Outcomes: The GSM-O 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 GIG services configuration baseline as deemed appropriate by the GSM-O Program Manager. Of note for the GSM-O Contractor, when the Government accepts new capabilities that are the result of work by another contractor and incorporates those capabilities into the DISA-provided GIG services configuration baseline, the GSM-O Contractor shall then become responsible for operation and security of those capabilities under this TO.

b. The Contractor shall comply with all locally directed training, reporting, security, and personnel requirements. These include but are not limited to Personnel Access Management (PAM) reporting, security training, and safety training.

c. The Contractor shall perform the activities described in this TO in a manner that enables any new action (e.g. a new request, a trouble-induced action, a maintenance action, etc) to be “rolled back” (i.e. to reinstate the network configuration and operative state from which such action was started) when evidence is received that an action is adversely affecting the stability of the network.

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

e. The GSM IP Address List shall be managed and provided by the Government.

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

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

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

i. Enabling Facilities: The Contractor shall provide temporary 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 task order.

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 GIG services that are not under direct Contractor control.

k. All changes shall conform to DISA approved Change Management processes and be approved by DISA Change Advisory Board (CAB). The contractor can assume that a Standard Change action conforms to DISA Change Advisory Board 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 customer(s) and the Designated Accreditation Authority.

m. The Contractor shall provide all equipment associated with, or required for, the execution of a task order, except for items having unit cost greater than $10,000.00 (see paragraph 14n). The Government shall approve the procurement of such equipment prior to its procurement. Such equipment shall become Government property if/when installed in the DISA-provided GIG 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 property.

n. Items of telecommunications/IT equipment and associated integral components) having unit cost greater than $10,000.00 (as of September 2010) will be procured and provided by the Government in accordance with the DISA Acquisition Strategy and provided to the Contractor for installation/implementation/ transition according to the task order. The Government will update this cost threshold annually. All software purchases shall be Government executed.

o. Equipment installed at DISA-provided GIG services interface points shall comply with existing DISA-provided GIG services architecture, GSM-OSS, and Authority to Operate (ATO). This shall not restrict how the service external to the DISA-provided GIG services -owned components is performed (commercial vendor cloud). Equipment and software installed on the DISA-provided GIG services side of the extended demarcation point shall become Government property.

p. The directives and instructions listed in PWS Appendix B apply, as applicable, to the requirements of this TO.

q. When the Government accepts a new networking capability into the installed DISN infrastructure, for subsequent operation and sustainment by the GSM-O 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.

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

s. Due to changes in the organization of DoD announced in August 2010, specific titles (e.g. Commander JTF-GNO, etc) are subject to change. Such titles shall be interpreted in the PWS as meaning, “… or the successor to this office if applicable."

t. In compliance with U.S. Office of Management and Budget (OMB) guidance dated 28 September 2010, federal agencies are required to ensure that procurements of networked information technology comply with Federal Acquisition Regulation requirements for using the U.S. Government version 6 (USGv6) profile and testing program for the completeness and quality of Internet Protocol version 6 (IPv6) capabilities. The DISA IPv6 POC will provide necessary implementing guidance applicable to the Contractor's service as GFI.

15. Section 508 Accessibility Standards.

Section 508 standards are not applicable to this TO.

Page A - 1

GSM-O TASK ORDER #1

APPENDIX A – Definitions Applicable to this TO

The following definitions shall be applicable to this task order.

Access Bandwidth: A circuit, or segment of a circuit, that offers transport bandwidth between a user location at a B/P/C/S (or other facility) to the DISN Service Delivery Nodes (SDNs). See also definition for Backbone Bandwidth.

Backbone Bandwidth: A circuit, or segment of a circuit, that offers transport bandwidth between two DISN Service Delivery Nodes (SDNs). Bandwidth is defined as size or capacity of a circuit (e.g. DS-1, DS-3, OC-3, etc). See also definition for Access Bandwidth.

DISN Infrastructure: The total set of installed networking/service capabilities as listed in the GSM asset inventory data provided as part of a draft Task Order. This includes transport fiber/circuits/services, equipment, software (both software imbedded within devices as well as functional software applications), functional services, Government-designated facilities including network control centers, and associated tools used in the performance of networking O&M functions.

“Freeze” Condition: Restriction of any configuration changes, scheduled maintenance actions, and any access to the network for a period before and during scheduled mission events or real world contingency operations. This includes close coordination with commercial and Government service providers, canceling/rescheduling maintenance, and the physical security of facilities, power, and network equipment.

GSM-OSS: The federated set of not-fully integrated tools, completely-integrated capabilities, and networks utilized to monitor, manage and achieve positive control of the GSM-Infrastructure elements, systems and services, as provided by the Government to the GSM-O contractor. The complete list of tools and software suites encompassing this suite is as listed in the GSM asset inventory data provided as part of a draft Task Order.

The functions covered by this control tool set include, but are not limited to, trouble ticketing, configuration management, reporting, element management, network management, and the tools necessary to maintain, monitor and control the security/net assurance/mission assurance capabilities. These capabilities are not categorized as Government Furnished Capabilities/Equipment (GFC/GFE) because the Government retains control over them; the Contractor’s role is to utilize the tools to operate and sustain the GSM capabilities. The vendor is authorized to make recommendations for improvement or modification to the governing authority as necessary.

ITIL®-Derived Definitions: This TO uses terms that are defined within documentation of the current version (currently v3) of the ITIL® Framework for Services Management. Note that ITIL® materials are trademarked; some materials are available only through subscription or comparable for-payment processes. The web link to the ITIL® governing body site is pasted here:

http://www.best-management-practice.com/officialsite.asp?DI=575004&FO=1230366

Page A - 2

Net Assurance: The DoD activities, conducted consistent with applicable directives, focused on the protection and security of designated capabilities. The term Computer Network Defense (CND) is included within the context and definition of Net Assurance.

NetOps: The DoD-wide operational, organizational, and technical capabilities for operating and defending the GIG. NetOps includes, but is not limited to, enterprise management, net assurance, and content management.

Order Entry System: The order processing capability, the request fulfillment capability, and the tools supporting those capabilities.

Project Designation: The Government may, at its option, declare an effort to be a GSM “Project” which requires support from a non-GSM-O (typically the GSM-ETI) contract.

Criteria that determine when an effort is a project are any one or more of the following:

• It results in changing the footprint at the expected DISN POP

• It relates to BRAC in any way

• It relates to technology change (tech refresh, new service, new provider contract)

• The requirement has DISA Director level attention

• The customer has declared the requirement to be part of a project

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 are considered outside the scope of a Standard Change and 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:

a. Request fulfillment actions: The Contractor may immediately work to fulfill a request for change provided that such work satisfies ALL of the following:

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

Approved Products List, etc.)

(2) Does not result in changed facility support requirements e.g. floorspace footprint, HVAC, power etc.

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

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

(5) The Government has not declared PWS paragraph 4.2.1b for other- than-standard support to be operative

(6) The requesting DISN customer has provided approval in accordance with

DISN request fulfillment procedures.

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

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

(2) Plus: criteria (1) – (5) from paragraph a. above

Page A - 3

c. 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:

(1) Same as paragraph b.

d. Maintenance actions: same as item a criteria (1)-(5).

Whitelist Registry: A central database list of Internet-facing servers (for specific protocols) that are permitted to accept inbound access from the Internet in accordance with Government (JTF-GNO) policy. DoD servers not on the Whitelist are not permitted to accept such traffic. This is a continual process as servers are registered, JTF-GNO directives are received, then changes are implemented into the routers to allow traffic flow.

Page B - 1

APPENDIX B – DISN System and Infrastructure Asset Inventory Data

1. This TO shall support the following system capabilities that are part of the DISN. Note that this list is a sub-set of the larger list in PWS paragraph 2.2b.

a) Customer- controlled (non-DISN) networking capabilities

b) Data Communications Network (DCN)

c) Defense Red Switch Network (DRSN including Voice over Secure Internet

Protocol (IP) (VoSIP) (DISA managed portion only)

d) Defense Research and Engineering Network (DREN)

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

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

g) DISN encrypted traffic (if necessary)

h) DISN Leading Edge Services (DISN-LES)

i) Gateway Service Desks (3 regions)

j) GIG Control Network (GCN)

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

l) GSM Operational Support Systems (GSM-OSS) capabilities

m) Internet Access Point Network (IAPNet)

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

o) Leased transport circuits (via DATS and other sources)

p) Nonclassified but Sensitive Internet Protocol Router Network (NIPRNet)

q) Secret Internet Protocol Router Network (SIPRNet)

r) Timing and Synchronization (T&S) assets

2. The DISN Infrastructure capabilities (see definition in Appendix A of this TO) that comprise, enable, or control the system capabilities are described on a site-by-site basis in the asset and performance data contained in the classified addendum (a CD-ROM) to this TO.

3. Task Order-1 support is required to be provided at the following locations where DISN infrastructure is present:

• Skyline 7 (DISA building), Arlington VA;

• 701 S. Courthouse Road (DISA building) Arlington VA.

• Future Government facility at Ft. Meade, MD (spring 2011)(replacing the two

Arlington facilities)

• DISA Continental United States (CONUS) Field Command Scott AFB, IL

• U.S. Northern Command (USNORTHCOM) Field Office Peterson AFB, CO

• U.S. Pacific Command (USPACOM) Field Command Wheeler Army Airfield, HI

• U.S. Central (USCENTCOM) Field Command MacDill AFB, FL

• U.S. European Command (USEUCOM) Field Command Vaihingen, Germany

• DISA Central Field Office Manama, Bahrain

Page C - 1

APPENDIX C – Government Furnished Equipment/Capabilities (GFE)

a. The specific list of GFE for this TO is provided hereto and includes but is not limited to the following:

(1) Site-specific support tools and test tools to be used in the operation and management of DSN infrastructure

(2) Other capabilities TBD as specified in the attachment to this herein

Page D - 1

APPENDIX D – Government Furnished Information (GFI)

GFI provided to enable the Contractor to perform under this TO includes the following:

(1) The directives listed in Appendix B of the PWS, all of which are applicable to this

TO.

(2) GSM-O reference materials originally provided as part of the GFI associated with the GSM-O RFP.

(3) DISN Infrastructure data as provided in Appendix B of this TO

(4) Site security access requirements for each site to be supported

(5) DISN performance data from representative periods to support analysis of the effort required for performance-based task work

(6) Warranty/Maintenance Agreement information in effect during calendar year

Page E - 1

APPENDIX E – Functional Requirements

a. This Appendix describes functional task requirements applicable to this Task Order. To facilitate use of references in the PWS, the same paragraph numbers from the PWS are used in this Appendix. Note that details of outcomes, deliverables, and performance standards are provided in the description of requirements where they are applicable.

b. The term “Appendix” refers to an Appendix of this TO unless noted otherwise.

The term “paragraph” refers to a paragraph of this Appendix E unless noted otherwise.

1. [This header not used in this TO.]

2. [This header not used in this TO.]

3. [This header not used in this TO.]

4. PROGRAM MANAGEMENT REQUIREMENTS

4.1 Primary Management Documents

To establish an appropriate and effective execution environment immediately following award of the contract, the Contractor shall provide the following deliverables:

a. Program Management Plan (PMP): The Contractor shall provide a PMP document, for Government review and approval, which addresses all GSM-O activities and assigned tasks of the contract .The PMP shall identify and describe all required deliverables. Deliverables (CDRLs) resulting from this work are as follows:

A001 Program Management Plan (PMP)

b. Concept of Operations (CONOPS): The Contractor shall provide a final draft CONOPS document, for Government review and approval, which addresses all GSM-O functional and administrative activities, roles, and responsibilities.

Deliverables (CDRLs) resulting from this work are as follows:

A002 Concept of Operations (CONOPS)

4.2 Security Requirements

a. Overall Security Classification Requirements for the work conducted under this TO are as described in the DD Form 254. Classification level requirements for this work will vary, and for some activities will include up to Top Secret/Sensitive

Page E - 2

Compartmented Information (TS/SCI). Specific classification level requirements will be detailed within each Task Order.

b. The Contractor shall implement and adhere to security policies and classifications of the networks in accordance with the DISA and DoD classification guides. Storage and reporting of information shall be in accordance with the classification guides. The Contractor shall minimize security incidents and “spillage.” Applicable standards from the Acceptable Levels of Performance (ALP) table in Appendix C is/are row number 1.

c. The Contractor shall establish and implement security aspects of the contract execution environment (i.e. policies, procedures, standards, resources, controls, and outcomes to include applicable verification testing) that are compliant, effective, and reliable in the areas of personnel security (for clearances and access), information security and assurance, and physical security and protection of facilities and infrastructure. Applicable standards from the Acceptable Levels of Performance (ALP) table in Appendix C is/are row number 2.

d. The Contractor shall provide, for Government review and approval, a GSM-O Administrative Security Plan that addresses, at minimum, the following:

(1) Identification of applicable Federal, DoD, Allied/Coalition, and DISA security-related policies and directives that are applicable to the DISA-provided GIG services environment

(2) Security activities, procedures, controls, and outcomes to be incorporated into other GSM-O functions and tasks

(3) Risk assessment and mitigation for applicable GSM-O areas as designated by the Government

(4) Periodic measures and controls to verify that policies, standards and practices are being executed as assigned

(5) Personnel security (for clearances and access)

(6) Information security and assurance

(7) Physical security and protection of facilities and infrastructure

e. Deliverables (CDRLs) resulting from this work are as follows:

A003 Administrative Security Plan A004 Annual Administrative Security Report

4.3 Reports and Controls

a. The Contractor shall provide, at minimum, the following types of reporting controls:

(1) Each one-time or periodic report or reporting process needed for effective control of all contract activities, including at minimum the following:

Page E - 3

• One-time conditional reports or deliverables that document the results of an activity

• Periodic reports that provide data and other documentation on a daily, weekly, monthly, quarterly, or annual basis as applicable

• Periodic meetings and reviews conducted to review status and task outcomes

(2) The Contractor shall prepare and present a Quarterly Program Review following a Contractor’s recommended process and presentation template.

(3) The Contractor shall prepare and present a Quarterly Fiscal Review whose content covers all invoice data for the period as well as issues identified from previous reviews.

(4) When required by the applicable task order, the Contractor shall prepare and provide an Invoice Supporting Data Spreadsheet whose content and design have been approved by the Government; the intent is to provide supplementary data for Government analysis that shows how the summary data presented in the formal invoice format were derived.

(5) The Contractor shall prepare and present an annual Review of Deliverables to verify that the purpose, content and format of each deliverable is still relevant and necessary.

(6) The Contractor shall provide, annually, a planning baseline of activities and criteria to assist the Government in planning for future transition-out actions at the end of the life of the GSM-O contract.

b. Deliverables (CDRLs) resulting from this work are as follows:

A005 Quarterly Program Review A006 Quarterly Fiscal Review A007 [Not applicable this TO] A008 Annual Review of Deliverables A009 Report of GFE A010 Annual Termination Planning Report

4.4 Cost Management and Reporting

a. A Government objective for effective DISA-provided GIG services management is to provide seamless and efficient processes for integrating all costs of services due to GSM-O 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. 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) table in Appendix C is/are row number 3. In managing costs for services, the following constraints shall apply:

(1) The Contractor’s invoicing procedures shall include prompt payment discounts and penalties for late billing outside the 30-day period.

Page E - 4

(2) The Contractor shall provide activity based cost reports provided quarterly within 30 days after the end of each Calendar Quarter with all costs accurately applied to cost drivers and cost elements for reportable systems.

b. The Contractor shall identify and recommend potential productivity improvements and cost efficiency recommendations that can be implemented throughout the term of the contract to reduce cost. The Contractor shall report the achieved results of efficiencies gained to the Government annually, as an appendix to the annual update of the Program Management Plan (CDRL A001).

c. Deliverables (CDRLs) resulting from this work are as follows:

A011 Activity Based Cost Report

4.5 Business-Related Metrics

a. The Contractor shall recommend, for Government approval, business metrics.

Examples could include the following:

(1) Number of invoices within the preceding 12 months that were late (i.e.

outside the 30-day submission period).

(2) Percentage of assigned Contractor or subcontractor staff having all required security clearances.

(3) Percentage of reported outages during past quarter/year where the required repair parts and materials were not available within the required time limit specified in Appendix C.

(4) 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.

(5) 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. Applicable standards from the Acceptable Levels of Performance (ALP) table in Appendix C is/are row number 4. Deliverables (CDRLs) resulting from this work are as follows:

A012 Quarterly Business Metrics Report

5. TRANSITION REQUIREMENTS

5.1 Contract Initiation Review (CIR)

a. To ensure that both Government and Contractor understand the terms of the contract, and where applicable a task order, and are ready to launch and

Page E - 5 manage effective contract execution, the Contractor shall organize and present a one-time Contract Initiation Review (CIR) of the contract’s or task order’s terms, objectives, tasks, constraints, standards, and deliverables. The CIR shall address at minimum the following topics:

(1) Government objectives and requirements as documented in the solicitation (to ensure that all participants actually know what is in the solicitation)

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

TO

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

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

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

b. 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 dummy 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 three weeks following award of the contract and applicable task orders.

A013 Contract Initiation Review (CIR)

5.2 Transition Plan

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

(1) 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 20 days of contract start date (as established by the Contracting Officer).

(2) As part of the Transition…