Attachment 4 - GSM ETI Sample Task Order v6 05-12-2010.doc
DOC document 3 MB Posted
- Attached to
- Cancel Presolicitation HC1028-10-R-2001
- Solicitation number
- HC1028-10-R-2001
- Issued by
-
Defense Information Systems Agency
About this file
Attachment 4 - GSM-ETI Sample Task Order (TO) ES-1 - DISN CONUS Optical 100Gb/s Upgrade
View the file
Other files
Show 40 more
Latest 50 of 58 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
HC1028-10-R-2001-Attachment 4
Global Information Grid (GIG) Services Management (GSM) –
Engineering Transition and Implementation (GSM-ETI)
Sample Task Order (TO) #ES-01
DISN CONUS Optical 100Gb/s Upgrade
As of 12 May 2010 Based on GSM-ETI SOO dated 07 May 2010
| 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 #ES-01 |
Contents of this Task Order:
| 1 |
| Task Monitors ………………………………………………………..……… |
| 1 |
| 2 |
| Task Order Title ………………………………………………..…………… |
| 1 |
| 3 |
| Background ………………………………………………………….……… |
| 1 |
| 4 |
| Objectives ……………………………………………………….………….. |
| 2 |
| 5 |
| Scope …………………………….……………………………….…..…….. |
| 3 |
| 6 |
| Performance Requirements ……………………………….……………… |
| 6 |
| 7 |
| Performance Standards ……………………………………….………….. |
| 7 |
| 8 |
| Incentives …………………………………………………………………… |
| 7 |
| 9 |
| Place of Performance ……………………………………………………… |
| 7 |
| 10 |
| Period of Performance …………………………………………..………… |
| 8 |
| 11 |
| Delivery Schedule ………………………………………………..………… |
| 8 |
| 12 |
| Security ……………………………………………………………………… |
| 8 |
| 13 |
| Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) …………………………………………………………… |
| 18 |
| 14 |
| Other Pertinent Information or Special Considerations ……………….. |
| 9 |
| 15 |
| Section 508 Accessibility Standards ……………………………………… |
| 10 |
| Appendix A – Definitions …………………………………………………………… |
| A-1 |
| Appendix B – DISN Infrastructure Data ………………………….…………….… |
| 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 – Draft QASP for this TO ……………………………………….....… |
| H-1 |
| Appendix I – DD Form 1423 (CDRL) Set for this TO …………………………… |
| I-1 |
Notes for Contracting Officer (for development of CLINs, delete when complete):
There are three TO tasks:
6.1 general management of the effort
6.2 Phase One which is planning and documentation prep
6.2 Phase Two which includes ordering of equipment and then installation of the equipment.
The Phase Two equipment list will be approved by the Government at the milestone which completes Phase One; the offeror cannot know for sure at the time of proposal development what the list will be until it does the analysis during execution of Phase One. Therefore it would appear that Phase Two would need to be Cost-Plus Performance Incentives (to permit the cost of equipment to be an ODC) rather than fixed price per se. This also allows the Government to obtain some or all of the equipment via other sources (as provided by the ETI SOO) if the Government chooses to do that.
If there is just one CLIN that covers all of the TO work, then because of Phase Two it would appear that the CLIN would be Cost Plus Performance Incentive.
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.
DISN CONUS Optical 100Gb/s Upgrade
3. Background.
a. DISA provides networking support to its national security customers via DISN capabilities which are deployed and operated worldwide. DISN capabilities are functionally a system-of-systems entity that is in a continuing sustainment phase of its life cycle.
b. The DISN enables the Warfighter to establish information dominance by interconnecting the deployed forces and sustaining bases to the highest command authority in full support of mission requirements. The DISN also provides the wide area network component of tactical, strategic and enterprise information systems. The DISN strategy has been evolutionary in scope and based on anticipated changes in user requirements and advances in technology to keep pace with standards, developments, and implementations.
c. 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-ETI contract, and other GSM capabilities, will replace services from the existing DGS contract upon its expiration.
d. 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-ETI multiple-award contract (the basis for this TO) which provide engineering, transition services and implementation services in support of the DISN infrastructure
· Contractor support from the GSM-O source (the basis for the GSM-O TOs), providing operation, sustainment and security 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
e. To effectively support delivery of network services to the warfighter, DISA has a need to upgrade the bandwidth of four optical circuit links; all located in the Continental United States; each to be upgraded from 10 Gb/s to 100Gb/s. This task order is separated into two distinct phases as described below. Phase Two cannot begin until the Government has approved all Phase One deliverables and the Government authorizes the Contractor to proceed to Phase Two.
f. Detailed mandates and constraints, both administrative and technical, are described within this TO. The primary constraint for implementation planning and execution is that the links are currently in active service, providing service at the 10G level. The work described in this TO must be planned and then executed in a manner that minimizes the down-time of each link, and that results in the minimum disruption to related ongoing operations at each of the affected locations.
4. Objectives:
a. The Contractor shall establish a task management environment, consistent with the requirements of SOO paragraphs 3, 4, and 5.1, to enable, support, and control the execution of the work of this Task Order.
b. In Phase One work, the Contractor shall analyze the existing DISN configuration and loading (using data to be provided as GFI), to include development of a M&S model of the configuration and its traffic, and provide an analysis of alternatives and recommendation for the approach to be used to upgrade the four identified network links from the current capacity of 10 Gb/s to 100 Gb/s; following Government approval of the selected approach, the Contractor shall then develop engineering designs to implement the approach, to include recommendations for technology/equipment, implementation planning, and test planning. Phase One ends with Government milestone approval of all plans needed to commence acquisition of equipment and execution of implementation actions.
c. In Phase Two work, the Contractor shall order (or obtain from the Government, as provided in the approved planning) all equipment needed to implement the approved design; and the Contractor shall execute the approved implementation plan to install the new network links and de-install the old links. Phase Two ends with final Government milestone approval of all installation data, test results, and acceptance of the new links into the DISN installed infrastructure.
d. The overall quality and completeness of task activity is more important than schedule adherence per se; but the Government’s objective is to complete all work in this TO within 360 calendar days of the date of issue of the TO, including an allowance of up to eight weeks total for Government assessment and decision activities at the milestone points.
5. Scope.
a. Overall this TO requires application of the following GSM-ETI SOO sub-paragraphs:
· 4 Administrative Requirements
· 5.1 Management
· 5.2 Telecommunications Network Engineering
· 5.3 Service Transition and Implementation
· 5.4 Integration Services
· 5.6 Limited Scope Projects
· 5.7 ITIL-Derived Technical Support
b. The work and scheduling of this TO make it, by definition, a Limited-Scope Project; but the task activities require application of capabilities from other parts of the SOO.
c. An association matrix relating TO task activities to the capabilities of the ETI SOO is provided here to indicate the primary areas of focus of this support.
| SOO |
| Capability/Service |
| TO 6.1 |
Mgmt
TO 6.2
Phase One
TO 6.3
Phase Two
| 4 all |
| Administrative Requirements |
| YES |
| YES |
| YES |
| 5.1 |
| Management |
| YES |
| 5.2 |
| Telecommunications Network Engineering |
YES
| 5.2.1 |
| Engineering Analysis and Design |
YES
| 5.2.2 |
| Technical Research and Development |
YES
| 5.2.3 |
| Standards Development and Analyses |
| 5.2.4 |
| Modeling and Simulation (M&S) |
YES
| 5.2.5 |
| Network Security Engineering |
| YES |
| YES |
| 5.3 |
| Service Transition and Implementation |
| YES |
| YES |
| 5.3.1 |
| IT/IS System Expansion and Technology Refresh |
| YES |
| YES |
| 5.3.2 |
| Networking/IT Facilities Changes |
| YES |
| YES |
| 5.3.3 |
| Circuit/Service/System Deployment and Transition |
YES
| 5.3.4 |
| Last Mile Connections |
| 5.4 |
| Integration Services |
| 5.4.1 |
| Integration Engineering |
| YES |
| YES |
| 5.4.2 |
| Operational Level Agreement (OLA) Support |
| 5.6 |
| Limited Scope Projects |
| YES |
| YES |
| YES |
| 5.7 |
| ITIL-Derived Technical Support |
| YES |
| YES |
| 5.7.1 |
| Service Design Process Support |
YES
| 5.7.2 |
| Service Transition Process Support |
| YES |
| YES |
| 5.7.3 |
| Problem Management Process Support |
c. The functional activities of this TO shall be executed in support of specific DISN backbone networking links as described in Appendix B of this TO. The four CONUS links are relatively comparable but the details of each site environment are as described in the Appendix B data.
6. Performance Requirements.
6.1 Management
a. The Contractor shall establish a task management environment, consistent with the requirements of SOO paragraphs 4 and 5.1, to enable, support, and control the execution of the work of this Task Order.
b. Deliverables (CDRLs) produced by this work are as listed in TO Appendix G.
6.2 Phase One
a. In Phase One, the Contractor shall analyze the existing DISN configuration and loading (using data to be provided as GFI), to include development of a M&S model of the configuration and its traffic, and provide an analysis of alternatives and recommendation for the approach to be used to upgrade each of the four identified network links from the current capacity of 10 Gb/s to 100 Gb/s; following Government approval of the selected approach, the Contractor shall develop engineering designs to implement the approach, to include recommendations for technology/equipment, implementation planning, and test planning. Phase One ends with Government milestone approval of all plans needed to commence acquisition of equipment and execution of implementation actions.
b. Figure 1 depicts an overview of the types of activities and flow of work needed to accomplish the objectives of Phase One and Phase Two.
Figure 1. Overview of Phase One and Phase Two Activities
c. As depicted in Figure 1, the Contractor shall perform a sequence of engineering planning and design activities leading to eventual Government approval of a specific recommended engineering plan for the upgrade of each of the existing network links. The Contractor may develop an approach that is different from that shown, but shall provide supporting analysis to demonstrate that the recommended approach will address the required activities of Phase One, which include at minimum the following:
(1) Perform Engineering Analysis: identify data collection requirements; collect and verify data
(2) Develop a model of link performance, using Modeling & Simulation processes and tools, sufficient to support the development of an analysis of alternative for providing the required capability at each link site
[Government review of the model with revisions if necessary]
(3) Develop an analysis of alternatives that identifies a recommended engineering solution
(4) Develop a preliminary engineering design of the recommended alternative/approach
(5) Develop a complete DISA Business Case (using procedure guidance provided as GFI) that addresses the benefits of the recommended approach and design, while mitigating technical, functional and business risks
[Government review of the design and Business Case with revisions if necessary]
(6) Develop a final engineering design that implements the approved approach, consistent with the approved business case
(7) Complete the engineering design and implementation package which includes at least the following types of outputs:
a. Engineering Design
b. Architectural Topology of the design
c. Bill of Materials for all required materials and equipment
d. Acceptance Criteria and Test Plans
e. Site Prep Plan
f. Implementation Plan
g. Integration Planning Data (to facilitate the transfer of the completed link to the DISN operations contractor)
(8) Prepare, using GFI formats and procedures, the DISN Change Management Process data necessary to obtain Government approval of the planned upgrade
[Government approval of the design, implementation package and Change Management action. This approval completes Phase One work.]
d. Standards applicable to this work are described in TO Appendix F.
e. Deliverables (CDRLs) required by this work are as listed in TO Appendix G.
6.3 Phase Two
a. The Contractor shall implement the approved design and implementation plan for the upgrade of each network link, as approved from Phase One of this TO. The primary outcome resulting from Phase Two is a completed network 100 Gb/s link at each site, accepted into performance according to Government commissioning standards for DISN, with supporting documentation and CM data ready to be processed by the operations contractor. The upgrade also includes de-commissioning and removal of any capabilities no longer being used at each link site.
b. The Contractor shall purchase materials and equipment according to the approved plan. The Government may at its option provide equipment on the Bill of Materials from other Government sources; this will be determined by the Government as part of the analysis and approval process prior to or at the end of Phase One.
c. Activities from Figure 1 that shall be addressed by Phase Two include the following:
(1) Finalize transition and implementation plans, if required, based on guidance received at the end of Phase One
(2) Coordinate and perform site preparation activities
(3) Obtain materials via purchase or as provided by the Government
(4) Stage, test and prepare equipment as applicable
(5) Deploy the equipment to each link when site preparations have been completed
(6) Perform site installation activities
(7) Perform testing according to the approved plans
(8) Perform transition activities for the new links
(9) Perform service validation and testing according to approved plan
(10) Prepare CM data for update of Government CM resources
[Government review; make corrections as needed]
(11) Complete required technical documentation
[Government review; make corrections as needed]
(12) Execute actions under Government direction to transfer the completed link to DISN operations staff
[Transfer of link to the Government completes Phase Two]
d. Standards applicable to this work are described in TO Appendix F.
e. Deliverables (CDRLs) produced by this work are as listed in TO Appendix G.
7. Performance Standards.
Performance Standards are as described in Appendix F. Each standard is referenced to the applicable task activity from TO paragraph 6.
8. Incentives.
Performance Incentives apply to TO tasks 6.2 and 6.3. See draft QASP at Appendix H.
9. Place of Performance.
a. Place of Performance: Unless otherwise stated in a given task order, the place of performance shall be a combination of Contractor-provided facilities and the DISA facility at Ft. Meade, MD per the Base Realignment and Closure (BRAC) act. The use of Contractor facilities requires Government approval. Other work locations within and outside the Continental United States shall be as specified in each Task Order..
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, in cases of unforeseen conditions or situations (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Monitor (TM) approval is required. 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 outcomes as stated in this TO. 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.
11. Delivery Schedule.
a. Within the overall TO period of performance, Contractor activities and the delivery of outcomes and CDRLs shall be in accordance with the schedule for Phase One and Phased Two that was contained in the Contractor’s proposal for this TO.
b. Deliverables from task performance are identified in Appendix G to this TO. Each CDRL is referenced to the task activity of this TO that requires it.
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 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 Appendix C.
b. GFI provided to enable the Contractor to perform under this TO is described in Appendix D.
14. Other Pertinent Information or Special Considerations.
a. 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.
b. The contractor shall cease all actions on network support upon Government direction of a network “freeze” condition (see Appendix A for definition).
c. The new 100 Gb/s link at each site, comprised of equipment purchased by the Contractor and/or provided by the Government, as applicable in the approved design, shall become Government property at the time the link becomes operative following completion of acceptance testing. Equipment warranties shall be transferred to the Government as part of this process.
d. 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
e. The Contractor shall provide equipment incidental to the execution of this task order. 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.
f. Major items of telecommunications/IT equipment and associated integral components 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.
g. 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 (vendor cloud). Equipment and software installed on the DISA-provided GIG services side of the extended demarcation point shall become Government property.
h. Safety Requirements: The contractor shall implement and adhere to safety policies in accordance with DISA and DoD policies. The contractor shall minimize safety incidents.
c. Designs shall be in concert with GFI DISA-provided GIG services architectures and topologies.
i. Configuration changes shall be coordinated with the Designated Accreditation Authority.
j. All designs for implementation shall include Risk Mitigation planning and are subject to Government review and approval prior to implementation.
15. Section 508 Accessibility Standards.
Section 508 standards are not applicable to this TO.
GSM-ETI SAMPLE TASK ORDER #ES-1
APPENDIX A – Definitions Applicable to this TO
The following definitions shall be applicable to this TO.
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 and engineering functions. These capabilities are not classified as Government Furnished Capabilities/Equipment (GFC/GFE) because the Government retains control over them; the Contractor’s role is to operate and sustain those capabilities – thus the installed infrastructure is comparable to a facility or system which is categorized as “Government-Owned, Contractor-Operated.”
“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 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.
Incidental Item: In the GSM-ETI context for engineering implementation purposes, a new item of equipment to be provided by the Contractor shall be considered ‘incidental’ if it is on the DISA Approved Products List (APL) and is below the threshold of a “major item of equipment” as described in DISN support policies.
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 Limited-Scope Project: The Government may also, from time to time, require support within the functional scope of ETI work that is not of a continuing nature, has a defined beginning and end, and has defined outcomes, deliverables and controls. These work efforts are termed “limited-scope projects” to differentiate them from the other ETI functional capabilities. An example of a limited-term project would be a Government effort to plan for and execute the installation, on-site configuration, and acceptance testing of a set of 1800 new networking switches at 120 DISN sites world-wide. Although the engineering work involved is comparable to that already described in the SOO, the Government will order it separately and the Contractor will execute it by use of a separate team.
GSM-ETI SAMPLE TASK ORDER #ES-1
APPENDIX B – DISN Infrastructure Data
a. This appendix provides technical data that supplements the general Scope statement provided in TO paragraph 5.
b. Table 1 lists the DISN current Optical Transport System (OTS) parameters that are relevant for DISN links capacity upgrade from 10G to 100G.
Table 1. DISN Optical Transport System Parameters
| # |
| Parameter |
| Value |
| 1 |
| Terminal Equipment: |
· Ch Bit Rate
· Modulation Format/ Detection
· FEC Coding Gain
· WDM Mux/DeMux Ch Spacing
· # of equipped 10G ’s 10 Gb/s (up to 96 ch’s)
OOK- NRZ/ Direct Detection
8 dB
50 GHz, ITU Grid
Varies from link to link (10 - 40 ’s)
| 2 |
| In-line Optical Amplification: |
· EDFA
· Gain
· Optical BW
· Input Power range
· Total output Power
· Raman (for long spans only) 3-stage, w/ mid-stage access (9dB) & 3 VOA’s
Up to 25 dB. Flattened (~0.8 dB), C-band (1527.3 nm to 1565.6 nm)
-31 to 5.5 dBm
+21 dBm
Backward-pumped, 9-13 dB of gain
| 3 |
| Fiber Plant |
· Fiber Types
· Dispersion map
· Launch Power/ch
TW-C, TW-P, TW-RS, ELEAF, NDSF
Typical terrestrial map
+1 dBm (nominal)
| 4 |
| OADM (2-Degree) |
| -Selectable, RBF-based |
c. Table 2 lists the relevant parameters of the 4 CONUS links (to be upgraded from 10Gb/s to 100Gb/s).
Table 2. Technical Parameters of CONUS Links
| Link |
| Site name |
| Site type |
| Raman Gain |
(dB) DCM dispersion
Ps/nm Span Length (km) Span Loss (db) Fiber Type
| Link 1A |
| 1 |
| Terminal |
| 0 |
| -250 |
| 38.16 |
| 10 |
| TruewaveClassic |
| 2 |
| OLA |
| 0 |
| -500 |
| 88.4 |
| 20.1 |
| TruewaveClassic |
| 3 |
| OLA |
| 0 |
| -333 |
| 93.57 |
| 23.2 |
| TruewaveClassic |
| 4 |
| OLA |
| 0 |
| 0 |
| 70.8 |
| 17.3 |
| TruewaveClassic |
| 5 |
| OLA |
| 0 |
| 0 |
| 93.5 |
| 24.8 |
| TruewaveClassic |
| 6 |
| S-OADM |
| 0 |
| 0 |
| 87.22 |
| 21.6 |
| TruewaveClassic |
| 7 |
| OLA |
| 0 |
| -500 |
| 99.13 |
| 23.3 |
| TruewaveClassic |
| 8 |
| OLA |
| 10 |
| -500 |
| 95.93 |
| 23.3 |
| TruewaveClassic |
| 9 |
| OLA |
| 8.9 |
| -167 |
| 13.1 |
| 15.3 |
| TruewaveClassic |
| 10 |
| S-OADM |
| 0 |
| 0 |
| 131.56 |
| 29.7 |
| TruewaveClassic |
| 11 |
| Terminal |
| 10 |
| -250 |
| Link 16A |
| 1 |
| Terminal |
| 0 |
| -333 |
| 84.58 |
| 18.1 |
| eLeaf |
| 2 |
| S-OADM |
| 0 |
| 0 |
| 104.85 |
| 22.3 |
| eLeaf |
| 3 |
| OLA |
| 0 |
| -500 |
| 117.68 |
| 25.2 |
| eLeaf |
| 4 |
| S-OADM |
| 0 |
| 0 |
| 33.22 |
| 18.5 |
| eLeaf |
| 5 |
| S-OADM |
| 0 |
| -167 |
| 28.33 |
| 18.8 |
| eLeaf |
| 6 |
| S-OADM |
| 0 |
| -83 |
| 27.26 |
| 17.2 |
| eLeaf |
| 7 |
| S-OADM |
| 0 |
| -83 |
| 6 |
| 18.5 |
| eLeaf |
| 8 |
| Terminal |
| 0 |
| 0 |
| Link |
| Site name |
| Site type |
| Raman Gain |
(dB) DCM dispersion
Ps/nm Span Length
(km) Span Loss
(db) Fiber Type
| Link 19B |
| 1 |
| Terminal |
| 0 |
| -500 |
| 92.97 |
| 19.1 |
| eLeaf |
| 2 |
| OLA |
| 6.7 |
| -500 |
| 108.55 |
| 23.3 |
| eLeaf |
| 3 |
| OLA |
| 9 |
| -500 |
| 105.93 |
| 22.3 |
| eLeaf |
| 4 |
| OLA |
| 8.5 |
| -417 |
| 105.61 |
| 21.4 |
| eLeaf |
| 5 |
| OLA |
| 8.3 |
| 0 |
| 32.67 |
| 15.7 |
| eLeaf |
| 6 |
| S-OADM |
| 0 |
| 0 |
| 134.4 |
| 23.3 |
| eLeaf |
| 7 |
| OLA |
| 9 |
| -500 |
| 108.1 |
| 22.4 |
| eLeaf |
| 8 |
| OLA |
| 9 |
| -500 |
| 109.83 |
| 22.8 |
| eLeaf |
| 9 |
| OLA |
| 9 |
| -500 |
| 107.89 |
| 22.1 |
| eLeaf |
| 10 |
| OLA |
| 7.5 |
| -417 |
| 93.94 |
| 19 |
| eLeaf |
| 11 |
| OLA |
| 0 |
| -500 |
| 107.7 |
| 23 |
| eLeaf |
| 12 |
| OLA |
| 7.9 |
| -500 |
| 95.49 |
| 19.5 |
| eLeaf |
| 13 |
| OLA |
| 6.5 |
| -500 |
| 94.51 |
| 19.6 |
| eLeaf |
| 14 |
| OLA |
| 0 |
| -167 |
| 98.48 |
| 20.4 |
| eLeaf |
| 15 |
| OLA |
| 6.6 |
| -500 |
| 93.28 |
| 19.3 |
| eLeaf |
| 16 |
| OLA |
| 7.3 |
| -500 |
| 93.35 |
| 19.1 |
| eLeaf |
| 17 |
| OLA |
| 0 |
| -500 |
| 110.16 |
| 22.8 |
| eLeaf |
| 18 |
| Terminal |
| 9 |
| -83 |
| Link 6A |
| 1 |
| Terminal |
| 0 |
| -500 |
| 72.2 |
| 19.55 |
| TruewaveClassic |
| 2 |
| OLA |
| 0 |
| -500 |
| 89.9 |
| 21.07 |
| TruewaveClassic |
| 3 |
| OLA |
| 0 |
| 0 |
| 84.5 |
| 22.54 |
| TruewaveClassic |
| 4 |
| OLA |
| 0 |
| 0 |
| 91.59 |
| 21.37 |
| TruewaveClassic |
| 5 |
| OLA |
| 0 |
| 0 |
| 77.57 |
| 18.98 |
| TruewaveClassic |
| 6 |
| OLA |
| 0 |
| -500 |
| 55.09 |
| 13.91 |
| TruewaveClassic |
| 7 |
| OLA |
| 0 |
| -500 |
| 99.52 |
| 26.03 |
| TruewavePlus |
| 8 |
| OLA |
| 10 |
| -417 |
| 79.96 |
| 19.38 |
| TruewavePlus |
| 9 |
| OLA |
| 0 |
| -83 |
| 103 |
| 24.28 |
| TruewaveRS |
| 10 |
| OLA |
| 8.3 |
| 0 |
| 127.45 |
| 29.76 |
| TruewavePlus |
| 11 |
| OLA |
| 10 |
| -500 |
| 72.88 |
| 17.39 |
| TruewaveRS |
| 12 |
| OLA |
| 0 |
| -500 |
| 79.27 |
| 20.16 |
| TruewaveRS |
| 13 |
| OLA |
| 0 |
| -642 |
| 107.5 |
| 26.03 |
| TruewaveRS |
| 14 |
| OLA |
| 10 |
| -83 |
| 96.8 |
| 22.26 |
| TruewaveRS |
| 15 |
| OLA |
| 0 |
| 0 |
| 81.92 |
| 19.84 |
| TruewaveRS |
| 16 |
| OLA |
| 0 |
| -552 |
| 46.88 |
| 11.78 |
| TruewaveRS |
| 17 |
| OLA |
| 0 |
| -552 |
| 76.4 |
| 17.27 |
| TruewaveRS |
| 18 |
| Terminal |
| 0 |
| -92 |
GSM-ETI SAMPLE TASK ORDER #ES-1
APPENDIX C – Government Furnished Equipment/Capabilities (GFE)
a. The specific list of GFE for this TO is attached hereto and includes but is not limited to the following:
(1) Site-specific support tools and test tools to be used in the TO task activities
(2) Other capabilities TBD as specified in the attachment to this herein
b. Note: As described in the definition “DISN Infrastructure” in Appendix A of this TO, the actual DISN installed infrastructure is not conveyed as GFE to the Contractor. The Contractor uses its expertise and GFE tools to operate and sustain the installed infrastructure.
GSM-ETI SAMPLE TASK ORDER #ES-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 SOO, all of which are applicable to this TO.
(2) GSM-ETI reference materials originally provided as part of the GSM-ETI RFP.
(3) Site security access requirements for each site where work is to be done
GSM-ETI SAMPLE TASK ORDER #ES-1
APPENDIX E – Functional Requirements
[Appendix not used this TO]
GSM-ETI SAMPLE TASK ORDER #ES-1
APPENDIX F – Table of Acceptable Levels of Performance (ALPs) GSM-ETI Acceptable Levels of Performance
| TO Task |
| Objective |
| Standard |
| Acceptable Level of Performance |
| Positive/ Negative Incentives |
| Surveillance |
Method/
Measure
Note:in the rows of the table, column 6 from the left identifies up to four regions of performance for incentive purposes:
A Blue region, where performance is Above-Satisfactory to a degree that merits Incentive;
A Green region, where performance is Satisfactory;
A Yellow region, where performance is not yet Satisfactory, but no incentive penalty is applicable;
A Red region, where performance is sufficiently below the Satisfactory level to justify an incentive penalty.
The “Standard” of satisfactory performance is minimally attained at the lower value of the Green/Satisfactory range.
An example of these relationships is as follows, using Row 7 values:
0% -- [Red: penalty applicable] – 90% -- [Yellow: not yet Satisfactory] – 97% -- [Green: Satisfactory] – 99% -- [Blue: Above-Satisfactory, Incentive earned] – 100%
6.2c(1) 6.2c(2)
6.2c(3)
6.2c(4)
6.2c(5)
6.2c(6)
6.2c(7)
6.2c(8)
| Produce high quality results from each Phase One planning activity, considered separately |
| 98-99% |
| The work will be completed with only minor corrections, at most, needed in the CDRLs (with respect to the quality and completeness of the content) |
| 100% = Blue 98-99% =Green |
90-97% = Yellow
<90% = Red
Frequency—Monthly, Surveillance Type—100% monitoring; Method of surveillance— Data analysis.
| 2 |
| 6.2c(1) |
6.2c(2)
6.2c(3)
6.2c(4)
6.2c(5)
6.2c(6)
6.2c(7)
6.2c(8)
| Delivery of results on schedule for each Phase One planning activity, considered separately |
| 98-99% |
| The work will be completed within 2 weeks of the approved schedule. |
100% = Blue 98-99% =Green
Frequency—Monthly, Surveillance Type—100% monitoring; Method of surveillance— Data analysis.
6.3c(1)
6.3c(2)
6.3c(3)
6.3c(4)
6.3c(5)
6.3c(6)
6.3c(7)
6.3c(8)
6.3c(9)
6.3c(10)
6.3c(11)
6.3c(12)
| Produce high quality results from each Phase Two implementation activity, considered separately |
| 98-99% |
| The work will be completed with only minor corrections, at most, needed in the CDRLs (with respect to the quality and completeness of the content) |
| 100% = Blue 98-99% =Green |
Frequency—Monthly, Surveillance Type—100% monitoring; Method of surveillance— Data analysis.
| 4 |
| 6.3c(1) |
6.3c(2)
6.3c(3)
6.3c(4)
6.3c(5)
6.3c(6)
6.3c(7)
6.3c(8)
6.3c(9)
6.3c(10)
| Delivery of results on schedule for each Phase Two implementation activity, considered separately |
| 98-99% |
| The work will be completed within 2 weeks of the approved schedule. |
100% = Blue 98-99% =Green
Frequency—Monthly, Surveillance Type—100% monitoring; Method of surveillance— Data analysis.
APPENDIX G – List of Contract Data Requirements List (CDRL) Items Applicable to this TO
Table 1. CDRLs Required by Each TO Task Activity
CDRLs Required by Each TO Task Activity
| TO Task |
| Figure 1 |
Activity Number
| Activity Title |
| Applicable CDRLs |
| 6.1 |
| N/A |
| Management |
| A001 |
Technical Management Work Plan
A002 Quarterly Program Review
A003 Quarterly Fiscal Review
A004 Invoice Supporting Data Spreadsheet
A005 Activity Based Cost Report
| 6.2c(1) |
| A.1 |
| Perform Engineering Analysis |
| A017 Network Capacity Analysis Report |
A019 Network/System Performance Analysis Report
A024 Technical Analysis Report
A026 Network Technology Evaluation Report
A033 Network Traffic Analysis and Report
A034 Network/Service Optimization Analysis and Report
A035 Network Security Assessment and Report
| 6.2c(2) |
| A.2 |
| Develop and Perform M&S |
| A017 Network Capacity Analysis Report |
A019 Network/System Performance Analysis Report
A024 Technical Analysis Report
A026 Network Technology Evaluation Report
A033 Network Traffic Analysis and Report
A034 Network/Service Optimization Analysis and Report
A035 Network Security Assessment and Report
| Milestone |
| Government Review and Approval |
| 6.2c(3) |
| A.3 |
| Formulate Engineering Solutions |
| A006 Customer Requirements and Solution Proposal |
A007 Technical Design Documentation
A018 Capacity Plan
A020 Network/System Design and Implementation Plan
A054 Technologies Upgrade Studies and Reports
| 6.2c(4) |
| A.4 |
| Preliminary Engineering Designs |
| A006 Customer Requirements and Solution Proposal |
A007 Technical Design Documentation
A018 Capacity Plan
A020 Network/System Design and Implementation Plan
A054 Technologies Upgrade Studies and Reports
| 6.2c(5) |
| A.5 |
| Develop Business Case |
| A062 Business Case Analysis and Recommendations |
A063 Analysis of Alternatives
A046 Site Upgrade Cost Proposals
| Milestone |
| Government Review and Approval |
| 6.2c(6) |
| A.6 |
| Develop Final Solution/Engineering Design |
| A006 Customer Requirements and Solution Proposal |
A007 Technical Design Documentation
A008 Test Management Plan
A009 Implementation Plan
A013 Site Equipment Installation Plan and Bills of Materials (BOM)
A014 Site Installation Checklist and Test Plans
A018 Capacity Plan
A020 Network/System Design and Implementation Plan
A024 Technical Analysis Report
A027 Network Architecture and Engineering Master Plan
A031 Service Level Agreement (SLA) Standards
A032 Operational Level Agreement (OLA) Standards
A036 Network Security Implementation Plan
A042 Implementation Project Plan
A043 DISN Implementation Schedule
A046 Site Upgrade Cost Proposals
A064 Transition Plan
| 6.2c(7) |
| A.7 |
| Final Engineering Design Package |
| A006 Customer Requirements and Solution Proposal |
A007 Technical Design Documentation
A008 Test Management Plan
A009 Implementation Plan
A013 Site Equipment Installation Plan and Bills of Materials (BOM)
A014 Site Installation Checklist and Test Plans
A018 Capacity Plan
A020 Network/System Design and Implementation Plan
A024 Technical Analysis Report
A027 Network Architecture and Engineering Master Plan
A031 Service Level Agreement (SLA) Standards
A032 Operational Level Agreement (OLA) Standards
A036 Network Security Implementation Plan
A042 Implementation Project Plan
A043 DISN Implementation Schedule
A046 Site Upgrade Cost Proposals
A064 Transition Plan
| 6.2c(8) |
| A.8 |
| Perform Change Management Process |
| A023 Change Management Request |
A046 Site Upgrade Cost Proposals
A055 Facility Change Request
| Milestone |
| Government Review and Approval |
End of Phase One
| 6.3c(1) |
| B.1 |
| Finalize Transition and Implementation Plan |
| A014 Site Installation Checklist and Test Plans |
A037 Telecommunication Site Implementation Plan (TSIP)
A038 MBOM
A039 IBOM
A040 Site Preparation Engineering Package
A042 Implementation Project Plan
A064 Transition Plan
| 6.3c(2) |
| B.2 |
| Perform Site Preparation and Coordination |
| A011 Site Survey Data and Report |
A015 Completion Reports
A041 Implementation Status Report
A045 Site Visit Request Message
A047 Site Preparation/Upgrade In-Progress Status Report
| 6.3c(3) |
| B.3 |
| Resource Acquisition |
| A038 MBOM |
A039 IBOM
| 6.3c(4) |
| B.4 |
| Equipment Staging and Testing |
| A010 Test report |
A015 Completion Reports
| 6.3c(5) |
| B.5 |
| Equipment Deployment |
| A015 Completion Reports |
| 6.3c(6) |
| B.6 |
| Perform Site Installation |
| A012 As-built Drawing Updates |
A014 Site Installation Checklist and Test Reports
A015 Completion Reports
A051 In-Effect Report (IER)
A052 Ready for Use (RFU)
A053 Exception Report (ER)
| 6.3c(7) |
| B.7 |
| Perform Node/Segment Testing |
| A010 Test report |
A015 Completion Reports
A022 Monthly Problem Review
A051 In-Effect Report (IER)
A052 Ready for Use (RFU)
A053 Exception Report (ER)
| Milestone |
| Government Review and Approval |
| 6.3c(8) |
| B.8 |
| Perform End-to-End Circuit and Customer Transition |
| A015 Completion Reports |
A022 Monthly Problem Review
A064 Transition Plan
A065 Transition Results Report
| 6.3c(9) |
| B.9 |
| Perform End-to-End Service Validation and Acceptance Testing |
| A010 Test report |
A015 Completion Reports
A022 Monthly Problem Review A044
A048 Completion Reports (with detailed circuit engineering diagrams)
A050 Delayed Service Report (DSR)
A051 In-Effect Report (IER)
A052 Ready for Use (RFU)
A053 Exception Report (ER)
| Milestone |
| Government Review and Approval |
| 6.3c(10) |
| B.10 |
| Perform CM Data and System Updates |
| A012 As-built Drawing Updates |
A015 Completion Reports
A016 DPAS Data Entry
| 6.3c(11) |
| B.11 |
| Finalize Technical Documentation |
| A007 Technical Design Documentation |
A008 Test Management Plan
A015 Completion Reports
A018 Capacity Plan
A027 Network Architecture and Engineering Master Plan
A031 Service Level Agreement (SLA) Standards
A032 Operational Level Agreement (OLA) Standards
A036 Network Security Implementation Plan
| Milestone |
| Government Review and Approval |
| 6.3c(12) |
| B.12 |
| Turn-Over to Operations |
| A015 Completion Reports |
End of Phase Two
Table 2. Complete List of All CDRLs Cited in This TO
Deliverables –CDRLS Used in This TO
| Item # |
| Title |
| Subtitle |
| Frequency |
| Classification |
| TO |
Task SOO Reference
| A001 |
| Technical Report |
| Technical Management Work Plan |
| One-time |
| FOUO |
| 6.1 |
| 5.1.1 |
| A002 |
| Administrative Report |
| Quarterly Program Review |
| Quarterly |
| FOUO |
| 6.1 |
| 5.1.1 |
| A003 |
| Administrative Report |
| Quarterly Fiscal Review |
| Quarterly |
| FOUO |
| 6.1 |
| 5.1.1 |
| A004 |
| Administrative Report |
| Invoice Supporting Data Spreadsheet |
| Monthly |
| FOUO |
| 6.1 |
| 5.1.1 |
| A005 |
| Administrative Report |
| Activity Based Cost Report |
| Monthly |
| FOUO |
| 6.1 |
| 5.1.2 |
| A006 |
| Technical Report |
| Customer Requirements and Solution Proposal |
| Per Task Order |
| FOUO |
| 6.2c(3) |
6.2c(4)
6.2c(6)
6.2c(7) 5.2
| A007 |
| Technical Report |
| Technical Design Documentation |
| Per Task Order |
| FOUO |
| 6.2c(3) |
6.2c(4)
6.2c(6)
6.2c(7)
6.3c(11) 5.2
| A008 |
| Technical Report |
| Test Management Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(11) 5.2
| A009 |
| Technical Report |
| Implementation Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7) 5.2
| A010 |
| Technical Report |
| Test Report |
| Per Task Order |
| FOUO |
| 6.3c(4) |
6.3c(7)
6.3c(9) 5.2
| A011 |
| Technical Report |
| Site Survey Data and Report |
| Per Task Order |
| FOUO |
| 6.3c(2) |
| 5.2, |
5.3.2, 5.3.4
| A012 |
| Technical Report |
| As-built Drawing Updates |
| Per Task Order |
| FOUO |
| 6.3c(6) |
6.3c(10) 5.2, 5.3.2, 5.3.4
| A013 |
| Technical Report |
| Site Equipment Installation Plan and Bills of Materials (BOM) |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7) 5.2, 5.3.2, 5.3.4
| A014 |
| Technical Report |
| Site Installation Checklist and Test Reports |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(1)
6.3c(6) 5.2, 5.3.2, 5.3.4
| A015 |
| Technical Report |
| Completion Reports |
| Per Task Order |
| FOUO |
| 6.3c(2) |
6.3c(4)
6.3c(5)
6.3c(6)
6.3c(7)
6.3c(8)
6.3c(9)
6.3c(10)
6.3c(11)
6.3c(12) 5.2, 5.3.2, 5.3.4
| A016 |
| Technical Report |
| DPAS Data Entry |
| Per Task Order |
| FOUO |
| 6.3c(10) |
| 5.2, |
5.3.2, 5.3.4
| A017 |
| Technical Report |
| Network Capacity Analysis Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.1
| A018 |
| Technical Report |
| Capacity Plan |
| Per Task Order |
| FOUO |
| 6.2c(3) |
6.2c(4)
6.2c(6)
6.2c(7)
6.3c(11)
5.2.1
| A019 |
| Technical Report |
| Network/System Performance Analysis Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.1, 5.2.4
| A020 |
| Technical Report |
| Network/System Design and Implementation Plan |
| Per Task Order |
| FOUO |
| 6.2c(3) |
6.2c(4)
6.2c(6)
6.2c(7) 5.2.1
| A021 |
| Not Used This TO |
| A022 |
| Technical Report |
| Monthly Problem Review |
| Per Task Order |
| FOUO |
| 6.3c(7) |
6.3c(8)
6.3c(9) 5.2.1
| A023 |
| Technical Report |
| Change Management Request |
| Per Task Order |
| FOUO |
| 6.2c(8) |
| 5.2.1 |
| A024 |
| Technical Report |
| Technical Analysis Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2)
6.2c(6)
6.2c(7) 5.2.2
| A025 |
| Not Used This TO |
| A026 |
| Technical Report |
| Network Technology Evaluation Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.2
| A027 |
| Technical Report |
| Network Architecture and Engineering Master Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(11) 5.2.3
| A028 – A030 |
| Not Used This TO |
| A031 |
| Technical Report |
| Service Level Agreement (SLA) Standards |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(11)
5.2.3
| A032 |
| Technical Report |
| Operational Level Agreement (OLA) Standards |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(11) 5.2.3
| A033 |
| Technical Report |
| Network Traffic Analysis and Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.4
| A034 |
| Technical Report |
| Network/Service Optimization Analysis and Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.4
| A035 |
| Technical Report |
| Network Security Assessment and Report |
| Per Task Order |
| FOUO |
| 6.2c(1) |
6.2c(2) 5.2.5
| A036 |
| Technical Report |
| Network Security Implementation Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(11) 5.2.5
| A037 |
| Technical Report |
| Telecommunication Site Implementation Plan (TSIP) |
| Per Task Order |
| FOUO |
| 6.3c(1) |
| 5.3, |
5.3.1
| A038 |
| Technical Report |
| MBOM |
| Per Task Order |
| FOUO |
| 6.3c(1) |
6.3c(3) 5.3, 5.3.1
| A039 |
| Technical Report |
| IBOM |
| Per Task Order |
| FOUO |
| 6.3c(1) |
6.3c(3) 5.3, 5.3.1
| A040 |
| Technical Report |
| Site Preparation Engineering Package |
| Per Task Order |
| FOUO |
| 6.3c(1) |
| 5.3, |
5.3.1
| A041 |
| Technical Report |
| Implementation Status Report |
| Per Task Order |
| FOUO |
| 6.3c(2) |
| 5.3, |
5.3.1, 5.3.3
| A042 |
| Technical Report |
| Implementation Project Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(1) 5.3, 5.3.1, 5.3.3
| A043 |
| Technical Report |
| DISN Implementation Schedule |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7) 5.3, 5.3.1, 5.3.3
| A044 |
| Not Used This TO |
| A045 |
| Technical Report |
| Site Visit Request Message |
| Per Task Order |
| FOUO |
| 6.3c(2) |
| 5.3, |
5.3.1, 5.3.3
| A046 |
| Technical Report |
| Site Upgrade Cost Proposals |
| Per Task Order |
| FOUO |
| 6.2c(5) |
6.2c(6)
6.2c(7)
6.2c(8) 5.3, 5.3.1, 5.3.2
| A047 |
| Technical Report |
| Site Preparation/Upgrade In-Progress Status Report |
| Per Task Order |
| FOUO |
| 6.3c(2) |
| 5.3, |
5.3.1
| A048 |
| Technical Report |
| Completion Reports (with detailed circuit engineering diagrams) |
| Per Task Order |
| FOUO |
| 6.3c(9) |
| 5.3, |
5.3.1
| A049 |
| Not Used This TO |
| A050 |
| Technical Report |
| Delayed Service Report (DSR) |
| Per Task Order |
| FOUO |
| 6.3c(9) |
| 5.3, |
5.3.1
| A051 |
| Technical Report |
| In-Effect Report (IER) |
| Per Task Order |
| FOUO |
| 6.3c(6) |
6.3c(7)
6.3c(9) 5.3, 5.3.1
| A052 |
| Technical Report |
| Ready for Use (RFU) |
| Per Task Order |
| FOUO |
| 6.3c(6) |
6.3c(7)
6.3c(9) 5.3, 5.3.1
| A053 |
| Technical Report |
| Exception Report (ER) |
| Per Task Order |
| FOUO |
| 6.3c(6) |
6.3c(7)
6.3c(9) 5.3, 5.3.1
| A054 |
| Technical Report |
| Technologies Upgrade Studies and Reports |
| Per Task Order |
| FOUO |
| 6.2c(3) |
6.2c(4) 5.3.1
| A055 |
| Technical Report |
| Facility Change Request |
| Per Task Order |
| FOUO |
| 6.2c(8) |
| 5.3.2 |
| A056 – A061 |
| Not Used This TO |
| A062 |
| Technical Report |
| Business Case Analysis and Recommendations |
| Per Task Order |
| FOUO |
| 6.2c(5) |
| 5.2.1 |
| A063 |
| Technical Report |
| Analysis of Alternatives |
| Per Task Order |
| FOUO |
| 6.2c(5) |
| 5.2.1 |
| A064 |
| Technical Report |
| Transition Plan |
| Per Task Order |
| FOUO |
| 6.2c(6) |
6.2c(7)
6.3c(1)
6.3c(8) 5.2.1
| A065 |
| Technical Report |
| Transition Results Report |
| Per Task Order |
| FOUO |
| 6.3c(8) |
| 5.2.1 |
APPENDIX H – Draft Quality Assurance Surveillance Plan (QASP) for this TO
A draft QASP for this TO is attached hereto. Upon TO award, the draft QASP will be finalized.
Global Information Grid Services Management – Engineering, Transition and Implementation
(GSM-ETI)
Quality Assurance Surveillance Plan (QASP)
For GSM-ETI Sample Task Order #ES-01
12 May, 2010
1 INTRODUCTION
a. The Global Information Grid (GIG) Services Management (GSM) – Engineering, Transition, and Implementation (GSM-ETI) Quality Assurance Surveillance Plan (QASP) will evaluate the performance of the GSM-O contractor in meeting the program’s requirements as described in the GSM-ETI Statement of Objectives (SOO). The contractor, and not the government, is responsible for management and quality control actions to meet the terms of the contract. The government will perform quality assurance and surveillance to verify contract performance standards are achieved.
b. This TO QASP includes: (1) the specific requirements from the SOO applicable in this TO, (2) the applicable performance metrics, (3) the applicable acceptable level of performance, (4) the surveillance methodology used to evaluate performance, (5) incentives/disincentives, and (6) personnel and mechanisms responsible for performance surveillance.
2 PURPOSE
a. This QASP provides a quality surveillance strategy for the GSM-ETI contract. The primary intent of the plan is to provide a basis for the government to evaluate performance quality. Oversight of contractor performance will assure quality performance. The plan will also allow the Contracting Officer and Contracting Officer’s Technical Representative a mechanism to preclude major deficiencies in performance, provide input for annual contractor past performance evaluations, and assist in the decisions pertaining to the exercise of contract options.
b. This TO QASP is intended to accomplish the following:
· Discuss the process of performance measurement;
· Describe the incentive award plan;
· Establish a governance structure for monitoring performance, comparing actual performance against the performance standards, and authorizing the invoicing (payments) for earned incentives (or the disincentive credits); and,
· Identify the key performance standards and acceptable performance levels that will be used as both a measure of success and as a basis for incentive awards. This initial draft of the QASP will contain a notional list of performance standards that will be reconciled with the contractor’s proposed performance standards and subject to mutual agreement between the parties. The consolidated, negotiated standards and measures will be included in the final QASP.
3 BACKGROUND
a. The GSM-ETI solicitation is one of three solicitations (or equivalent efforts) that make up the GSM Acquisition of Services (AoS). In general, the GSM-ETI solicitation provides the engineering support necessary to sustain the day-to-day operations of GIG networks and related services. The core telecommunications capabilities supported by GSM-ETI enable the Warfighter to meet operational needs by providing world-wide telecommunications, 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.
b. The GSM-ETI contract has an ID/IQ structure with a Statement of Objectives (SOO that describes primary requirement areas. Task orders issued within the scope of the SOO provide a table of Acceptable Levels of Performance Levels (ALPs) that provide the basis for the QASP Matrix shown in paragraph 8 of this document. Each task order may include additional appropriate measures/metrics/incentives and methods of surveillance within the QASP associated with the objectives in the individual task orders.
c. Categories of task work where QASP surveillance and incentives are applicable are described in paragraph 4. Primary methods of surveillance to be used are described in paragraph 5. Roles and responsibilities, as well as how this draft QASP will be finalized after award, are described in paragraph 6. The incentive structure is described in paragraph 7. The QASP Matrix of performance standards, measures, and associated information is provided in paragraph 8.
4 WORK REQUIRING SURVEILLANCE
a. The Contractor’s work performance shall be monitored and evaluated in accordance with the contract and task order requirements. The QASP ties the performance standards and incentives of each TO back to the GSM-ETI SOO. ETI SOO requirements that shall be subject to QASP surveillance, according to the specific scope of a given task order, include the following:
· Management
· Telecommunications Network Engineering
· Service Transition and Implementation
· Network Assurance Operations
· Integration Services
· Connection Approval Services
· Limited Scope Projects
· ITIL-Derived Technical Support
· Combatant Command (COCOM) Support
b. The specific performance standards and acceptable performance levels for each of these areas are provided in paragraph 8 Table 1.
c. Each GSM-ETI SOO requirement has associated performance standards that are of the following types:
(1) Discrete Binary (DB). The DB category describes those performance standards that do not have a definable range of acceptable performance but rather have a finite objective that will be evaluated as either achieved or not achieved. The Government has attempted to limit the use of this “pass/fail” measure in favor of measures that recognize the value of performance over a range of possible values.
(2) Discrete Variable (DV). The DV category begins with a minimum satisfactory level of performance that is below the theoretical 100% level, and then adds one or more levels above the satisfactory condition to provide targets that recognize superior performance. In the GSM-O context, examples of this could be measures of the quality of data recorded or in the response time recorded for resolving a fault. In some instances, where the required acceptable level is 100%, the levels below that are noted to provide the basis for disincentives should that be necessary.
(3) Discrete Deliverables (DD). For some administrative deliverables such as summary reports, where the content is typically accepted as stated, the Government can assess the timeliness of submission of such items in terms of early/on-time/late. The DD category can be used for individual occurrences or any logical grouping of occurrences. (Note: in the GSM-O context there are no developmental activities and thus no milestones typically associated with a date of completion of a phase of the development of a new capability.)
5 PRIMARY METHODS OF SURVEILLANCE
a. As outlined in FAR Part 46.4, Government Contract Quality Assurance, the QASP specifies the method and location of surveillance to ensure that the services conform to contract requirements. The place of performance will be as designated in the applicable Task Order.
b. The primary methods of quality surveillance are addressed below. This list may be revised based on the contractor’s recommendations in a final negotiated QASP.
(1) 100 Percent Data Capture. If the performance of a PWS requirement (such as logging of help desk calls or resolving confirmed troubles) is documented via automated systems that capture descriptive and status data, that data can be used for QASP assessment purposes.
(2) Random or Periodic Sampling or Data Capture. The Government PMO can direct that data associated with the performance of a specific requirement be collected for purposes of…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .