Atch 14_CITS STO_NetOps SB.doc

DOC document 147 KB Posted

Attached to
NETCENTS-2 NETOPS AND INFRASTRUCTURE SOLUTIONS (SMALL BUSINESS COMPANION)
Solicitation number
FA8771-09-R-0019
Issued by

About this file

Atch 14_CITS STO_NetOps SB. NOTE In response to the decommissioning of the Hanscom Electronic Request for Proposals Bulletin (HERBB) the following files pertaining to solicitation FA8771-09-R-0019 Network Operations (NetOps) and Infrastructure Small Business Companion are posted directly on FedBizOps. THIS IS NOT A NEW SOLICITATION AND ALL DOCUMENTS POSTED ARE REPRODUCTIONS OF DOCUMENTS PREVIOUSLY POSTED BUT NO LONGER AVAILABLE ON HERBB .

View the file

Other files

File Type Posted
NOSB_FBO_Notice.pdf PDF
NOSB_Amend_0009.pdf PDF
NOSB_QandA_3.pdf PDF
NOSB_Amend_0008.pdf PDF
NOSB_Amend_0008_Cover_Letter.pdf PDF
NOSB_QandA_2.pdf PDF
NOSB_Atch_13_PPIS_Amend_0007.doc DOC document
NOSB_Atch_19_CITS_FFP_Amend_0007.xlsm XLSM spreadsheet
NOSB_Atch_21_Price_Workbook_Amend_0007.xlsm XLSM spreadsheet
0007.pdf PDF
Cover_Letter_NOSB_Amend_0007.pdf PDF
NOSB_Section_K.doc DOC document
NOSB_QandA.pdf PDF
Conformed_FA8771-09-R-0019_thru_Amend_0006.pdf PDF
NOSB_Clause_Update_Matrix_Amend_0006.xls XLS spreadsheet
NOSB_Atch_27_Training_Plan_Template_FFP_STO_Amend_0006.docx DOCX document
20121005_NOSB_Amend_0006_Cover_Letter.pdf PDF
NOSB_Atch_12_PP_Cover_Amend_0006.doc DOC document
NOSB_Clause_Update_Matrix_Amend_0006.pdf PDF
NOSB_Atch_19_CITS_ITS_FFP_Amend_0006.xlsm XLSM spreadsheet
NOSB_Amend_0006.pdf PDF
NOSB_Atch_13_PPIS_Amend_0006.doc DOC document
NOSB_QandA_Amend_0006.xls XLS spreadsheet
NOSB_Atch_21_Price_Workbook_Amend_0006.xlsm XLSM spreadsheet
20120925_-_NOSB_FBO_Announcement.pdf PDF
NetCents 2 NetOps SB Update -7 June 2012.doc DOC document
Atch 1_PWS_NetOps SB.doc DOC document
Atch 8_ITO_NetOps SB.doc DOC document
Amendment 0005.pdf PDF
Atch 25_NAICS_Appeal_Decision.pdf PDF
NETCENTS 2_Amend 0004.pdf PDF
Atch 8_ITO_NetOps SB.doc DOC document
Atch 19_CITS_ITS_Pricing_Model_NetOps SB.xls XLS spreadsheet
NetOps SB - Amend 0003.pdf PDF
Atch 24_Order_Extending_Close_Of_Record.pdf PDF
NetOps - SB Amend 0002.pdf PDF
Atch 17_CITS BPD_NetOps SB.doc DOC document
Atch 10_PP Consent_NetOps SB.doc DOC document
Atch 16_CITS Archit_NetOps SB.doc DOC document
Atch 19_CITS Pricing_NetOps SB.xls XLS spreadsheet
Atch 20_NM ND STO_NetOps SB.doc DOC document
Atch 8_ITO_NetOps SB.doc DOC document
Atch 13_PPIS_NetOps SB.doc DOC document
Atch 9_Eval Criteria_NetOps SB.doc DOC document
Atch 15_CITS Bldg List_NetOps SB.xls XLS spreadsheet
Atch 18_CITS Install Plan_NetOps SB.doc DOC document
Atch 21_Price Workbook_NetOps SB.xls XLS spreadsheet
Atch 12_PP Cover_NetOps SB.doc DOC document
Atch 11_PP Relevancy_NetOps SB.doc DOC document
Atch 1_PWS_NetOps SB.doc DOC document
Show 40 more

Latest 50 of 55 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

NETCENTS-2 NetOps and Infrastructure Solutions

Subfactor 4 - CITS Information Transport System (ITS) Firm Fixed Price Sample Task Order

United States Air Force Site Survey, Integration and Installation

Task Requirements Notice (TRN) for Yokota AFB

The competitive nature of this contract necessitates that each respondent propose a solution to a sample task that will assist the Source Selection Evaluation Team in its efforts to assess the depth and breadth of each contractor's capabilities. This sample task order will be evaluated as a “best value” competition and not solely as a “price” competition. The Government does not expect to receive any deliverable that is CDRL-driven in connection with this sample task order proposal.

The contractor will use the information contained in this sample task order to prepare a proposal for the Government’s evaluation of meeting the stated requirements. Offerors will be technically evaluated on their proposed solution.

For the purposes of this evaluation each respondent shall limit their proposed solution to include an outside plant topology, network topology, and 332 package (the offeror can supply one ITN and one EBN 332 package as long as all associated allied support work (raceways, grounds, electrical, etc) are identified. They will also include a narrative description on how these were developed. In addition, provide a narrative description on how you would implement installation for Yokota AFB.

For evaluation purposes, the recommended format for the Yokota TSIP, 332 package will allow the offeror to include place holders for the Digital Photo, Building Plan and Communication Room Plan which would only be obtained as a result of an onsite survey.

1. Scenario

The baseline documents identified below have been provided to identify requirements associated with Yokota AFB, and should be used in the development of the proposed outside plant topology, network topology, and 332 package:

a. Period of Performance:

Contract award to 30 Mar 2013;

Term 1 30 Mar 2013 to 30 Mar 2014;

Term 2 30 Mar 2014 to 30 Mar 2015;

Term 3 30 Mar 2015 to 30 Mar 2016;

Term 4 30 Mar 2016 to 30 Mar 2017

b. Building List (Section J, Attachment 15)

Note: Respondents should evaluate the information on the bldg. list and adjust their integration plan development accordingly (i.e. are the ITNs logical, are the CEBNs too many, fiber connections, etc.)

c. ITS Architecture (Section J, Attachment 16)

d. Baseline Program Directive (Section J, Attachment 17)

e. Telecommunications Systems Installation Plan (TSIP) (Section J, Attachment 18 )

2. Objective The objective of this hypothetical task order is to develop an Integration Plan to establish an integrated enterprise Air Force Network Operations (AFNetOps) capability at Yokota AFB based on a Government-provided Site Survey. The proposal shall indicate the technique, tools and approach to provide Yokota AFB with an integrated, high bandwidth, information transport capability that will support the war fighters’ current and future mission requirements. Information includes classified and unclassified data, voice, video, sensor and imagery traffic. The contractor shall integrate Commercial Off-the-Shelf (COTS) products to ensure that each integrated base ITS maximizes the cost effective use of existing equipment and facilities and to ensure the solution is fully compliant with the ITS Baseline Program Directive (BPD) and fully integrated into the system. The contractor shall use the CITS Pricing Model (Section J, Attachment 19) to provide a fully priced proposal for the requirements of this sample task. Instructions for using the pricing model are contained in the model itself, as well as in Section L6.2.2.3.1.

3. Assumptions The operational environment is assumed to be Government owned and managed. The sample task order is provided as a sample of a typical ITS task order under the NETCENTS-2 NetOps and Infrastructure contract. Only the paragraphs annotated with an asterisk in the Requirements section of this sample task order need to be addressed for evaluation purposes. They pertain to the critical components that will be evaluated: outside plant topology, network topology, 332 package, and installation approach IAW Section L and M of the RFP. If subparagraphs are marked as well, only those subparagraphs need to be addressed.

4. Scope

The ITS comprises a common, base wide backbone transport network (cable plant, other transmission facilities, and switching components), links from the backbone network to specific end buildings, interfaces to external and internal networks, components required to implement the various transport services ( data, voice, video, etc.) , and interfaces with the NM/ND. The Contractor shall provide all necessary personnel, supervision, management, materials, technical and non-personal technical services, and equipment to interface existing end building systems with the ITS backbone network.

5. INTRODUCTION

5.1 Project Title: Site Survey and Integration (SS&IP) for ITS to the establishment of an integrated enterprise Air Force Network Operations (AFNetOps) capability at Yokota AFB.

5.2 ITS Terminology.

5.2.1 Core/Non Core Buildings.

Buildings on the base are referred to as “core” or “non-core.” Core buildings (category 1, 2, 3) are those that contain activities performing direct or indirect mission support functions (i.e., HQ, control towers, personnel, etc). Non-core buildings are those performing non-mission support functions (i.e., BX, commissary, etc.).

5.2.2 Information Transport Nodes and End Building Nodes

The ITS will provide inter-connectivity between “core” buildings on the base as identified in the installation building list. Buildings will be categorized as Information Transfer Nodes (ITNs), which make up the “backbone” of the network, or End Building Nodes (EBNs), which are directly connected to the backbone.

5.2.3 Distribution System (DS): The DS includes:

a. The Outside Plant (OSP), which includes the outside cable plant Manholes, Handholes and Ducts (MHDS), fiber optic cabling, etc. that runs to the fiber optic distribution panel (FODP) in the first communication equipment location (CEL) in each building.

b. The Inside Plant (ISP) wiring connections between the first CEL and all other CELs in the building and any electrical power, grounding or Heating, Ventilation & Air Conditioning (HVAC) upgrades required in the CELs.

5.2.4 Network System. The Network System, which is the hardware and software for each CEL in each building.

5.2.4.1 Definitions. The contractor shall use the following definitions to comply with work efforts described elsewhere in this document.

5.2.4.2 Spoils. Any non-hazardous liquid or solid material resulting from installation of the ITS System that must be removed from the installation location.

5.2.4.3 Hazardous Material. Any hazardous liquid or solid material resulting from ISP installation and/or Manhole/Handhole entry efforts of the ITS System that must be removed from the installation location.

5.2.4.4 Air Conditioning. The improvement of the quality of the air within a CEL by controlling the:

a. Cooling of the temperature.

b. Particulates suspended in the air.

c. Humidity/water vapor in the air.

5.2.4.5 Ventilation. The movement of air, the circulation and/or removal of which is done to improve the quality of the climate in a CEL

5.2.4.6 Heating. Introduction of energy to raise the temperature of a CEL.

*5.2.4.7 Horse blanket: Overall base map with the ITS design layout overlaid on an “E size” copy of the government furnished record drawing base map that shows the reuse and new distribution system components and demonstrates the backbone route and diversity. This drawing shall be colored and coded to identify ITNs and associated EBNs, existing and new conduit and direct bury routes.

*6. REQUIREMENTS:

*6.1 INTEGRATED PRODUCT TEAM (IPT).

6.1.1 Requirements: The Contractor shall:

a. Chair Site Survey & Integration Planning (SS&IP) & Installation IPTs consisting of contractor representatives, base representatives from the base(s) identified in para. 2.1 , the Program Office, the MAJCOM and all required base personnel.

b. Provide a worldwide “Meet Me” Teleconference capability for the duration of the project.

c. Retain total responsibility for all facets of the integration planning, acquisition, installation, integration, testing, cutover and documentation for each base listed in paragraph 1.1.

*6.1.2 SS&IP IPT

a. The SS&IP IPT shall be used to minimize the integration planning time by bringing the contractor, sites, and program engineering expertise together to collaboratively create an integration plan to near finalized detail, without multiple reviews, deliveries, and comment submissions.

b. The IPT shall:

1. Produce a detailed and coordinated Integration Plan (IP) prior to leaving the site.

2. *Create an updated NW and DS topology diagram with changes necessitated due to site survey information.

3. Develop Box Level planning details required for the Vendor Selection Document (VSD) process.

4. *Develop a detailed card/port level network diagrams on site sufficient to validate a list of material (LOM).

5. *Develop detailed diagrams to integrate changes to the fiber optic distribution system and diagrams on site sufficient to validate a list of material (LOM)

6. The full system design for the RFP contract will be considered fully complete after the Final Document Acceptance (FDA) at the Prime’s facility.

*6.1.3 Installation IPT: The Installation IPT shall be used to:

a. Monitor installation progress.

b. Resolve issues that arise during the installation, cutover and test of the system.

c. Approve contractor developed detailed work schedules.

d. Obtain approval from the base POC for any downtime associated with any activity that will result in temporary disruption of electrical or network service to any building prior to the start of work.

*6.2 SITE SURVEY & INTEGRATION PLANNING

*6.2.1 Topology Development: The Contractor shall for each base:

a. Participate, with Government representatives, in a review of the preliminary list of buildings, funded & designed Military Construction Projects (MCP), Demolitions and major building renovations.

b. Review existing topology at each base.

c. *Develop a topology that identifies the number and location of ITNs and EBNs and the connectivity between them and the host base ITNs for each base.

d. Determine all pertinent items for consideration in vendor selection through discussions with base, MAJCOM, and Program Office with respect to each site.

6.2.2 Site Survey: Using the Government approved building list, the Contractor shall:

a. Conduct a site survey of existing facilities to provide the site with a complete cost effective system IP and associated implementation plan that meets ITS requirements.

b. Survey each building on the approved building list.

c. Verify suitability of government distribution & network equipment/material staging areas.

d. Obtain all data needed to tailor ITS training to the needs of the proposed system operators and maintainers.

e. Identify all environmentally sensitive and hazardous material issues that could affect the system installation and operation.

f. Discuss integration and installation options and document decisions in the HWIPR presentation.

*6.2.3 Outside Plant: Prior to the start of Box Level Collaboration it is expected that the contractor will discuss any issues in this area with the IPT prior to proceeding to the HWIPR. The contractor shall:

a. *Review the existing base OSP system to identify and locate:

1. All existing fiber optic cable that can be used in the IP.

2. All existing manholes, hand holes and ducts that can be used in the design.

b. *For those portions of the MHDS that are proposed for reuse, examine them to:

1. Ensure they are clear of debris, have sufficient capacity and are suitable for use for the proposed ITS cables.

2. Mandrel and, if clear, install a pull rope.

(a) If the duct is not clear, rod and install pull ropes.

(b) If duct cannot be rodded, recommend:

(1) Alternate route or

(2) Repair/replacement.

c. * For all fibers in cables proposed for reuse:

1. Conduct an Optical Time Domain Reflectometer (OTDR) test and maintain a soft copy of test results on site for use during collaborative IP.

2. Measure optical loss in both directions.

3. Provide the results to the government showing planned repairs, replacement, or reuse.

d. If applicable, comply with hazardous material requirements described elsewhere in this document.

*6.2.4 Inside Plant: The contractor shall:

a. * Identify and locate any existing electrical outlets that are proposed for use in the system IP showing planned repairs, extensions, replacement, or reuse.

b. * Identify and test existing communications ground in proposed equipment locations or identify the electrical ground in the building for extension into the proposed equipment locations if a communications ground does not exist or tests bad showing planned repairs, replacement, or reuse.

c. Ensure adequate HVAC, space, cable access and any other requirements for optimal equipment operation and maintenance is provided in all proposed equipment locations.

d. *Survey all existing CELs to determine if they meet the CITS CEL requirements (CELR). If the building has no current existing equipment or the current CEL does not meet CELR conduct a cost benefit analysis to determine whether the solution is to

1. Identify a new location that meets CELR and determine if any or all of the existing premise wiring can be relocated to the new location or

2. Physically modify the CEL to meet CELR.

e. Develop and submit for base approval/IPT concurrence a plan to remove/abate any asbestos and/or lead paint, if during the initial Contractor/Base Environmental meeting or during the review of any AF Form 332 the Base Environmental shop indicates that either is present.

*6.2.5 Network: The contractor shall:

a. Identify and locate all existing network equipment (located in Section J, Attachment 15) that can be used in the IP.

b. Verify all government provided data.

*6.2.6 Box Level Collaboration. The contractor shall review the preliminary Network, ISP & OSP design with the government to verify that all requirements needed to proceed to vendor selection have been identified.

*6.2.7 Vendor Selection. The contractor shall:

a. *Use the results of the topology discussions, the Base’s Vendor Selection Base & MAJCOM Requirements Document Checklist, early high level collaboration with the IPT Members and the results of the site survey, to determine which Network Equipment vendor(s) products shall be deployed at the site providing the site the most cost effective and fully compliant ITS possible.

b. *Make available to all potential vendors all available box level IP information either developed by the IPT or provided from other sources that is necessary for the vendor to propose a network IP and associated Life Cycle Support.

c. *Ensure that vendor prices are valid until prime contractor acquires items under the Material CCP.

*6.3 Engineering/Detailed Collaborative IP Requirements

*6.3.1 General: The Contractor shall:

a. *Integrate the base(s) ITS in accordance with (IAW) the CITS ITS Baseline Architecture, the ITS BPD and the results of the site survey and collaborative IP efforts.

b. *Integrate all proposed, contractor furnished hardware and software with the existing information infrastructure including GFE equipment.

c. *Use best commercial practices and/or standards.

d. *Use COTS equipment.

e. *Ensure that the IP for the backbone includes the capability for all core (including all buildings identified in funded & designed MCPs) and non-core buildings plus expansion as delineated in the Baseline Program Directive.

f. *Where warranted, include technical alternatives and recommendations.

*6.3.2 OSP System Requirements:

*6.3.2.1 Contractor: The contractor shall:

*a. Integrate the OSP fiber optic distribution system to:

1. Interface to the fiber optic distribution panels (demarcation point) for the fiber optic cables in each building.

2. Ensure that the installation of new fiber optic cables and inner duct does not negatively impact the maintenance of existing cabling and cross-connect systems.

*b. Provide an initial Communication Feature Location Data (CFLD) Table IAW the TSIP.

c. Investigate and provide alternatives that would avoid impacting Endangered Species, wetlands, Historical, Cultural, EOD/UXO & Archeological areas in the design.

*6.3.3 ISP System Requirements: The contractor shall:

*a. For each CEL, integrate upgrades required to meet network equipment mounting, electric power, grounding, cable pathway and HVAC requirements.

*b. Ensure that if the existing premise wiring is reworked or relocated, that all existing users have equivalent or improved capabilities.

c. Investigate and provide alternatives that would avoid impacting Historical, Cultural & Architectural areas in the design.

*6.3.4 Network System IP Requirements: The Contractor shall:

a. *Provide an IP that includes all “core” buildings with growth capability to connect all non-core “Category 4” buildings to the ITNs as identified in the approved master building list.

b. *Ensure that the proposed integrated ITS is interoperable with the existing host Network Management/ Network Defense (NM/ND) equipment by:

1. Providing an interface to the existing NM/ND system.

2. Providing new or updated Element Managers needed to configure and manage the ITS. (if required)

3. Coordinating with NM/ND personnel to integrate the ITS provided equipment with the current NM/ND. NM/ND personnel are responsible for implementing any configuration changes to their equipment.

c. *Define all interfaces to existing or planned equipment and software that will be connected to the contractor furnished hardware or software.

d. *Define the logical mapping of the existing and planned IP network onto the ITS configuration.

e. *Define timing and network synchronization for circuit emulation services and provide distributed timing services for use by other network applications and devices.

6.3.5 Reliability, Maintainability & Availability. The contractor shall:

a. Use the following assumptions in calculations verifying reliability requirements:

1. Trained personnel are available on site.

2. LRUs are available on site.

3. Restoration actions are limited to the removal and replacement of plug-in assemblies.

b. Use the following equations for availability calculations:

Ao = MTBF (Level) / [MTBF (Level) + MTTR]

MTBF (Level) = Mean Time Between Failures

MTTR = Mean Time To Repair

Level = The most critical failure identified for a system (e.g., catastrophic or major)

The Ao equation represents the availability performance for each item of equipment used in the network, not the availability performance of the entire network. The network Ao must be calculated using techniques based on network availability theory.

c. Verify by analysis that the :

1. System IP meets the following requirements:

(a) Mean Time To Repair (MTTR) is less than 30 minutes.

(b) Availability is at least 0.9999. The network is considered unavailable when 20 percent of more of the users in EBNs cannot communicate with a minimum of 50 percent of the other network users.

2. Distribution System IP meets a mean time between complete loss of transport capability of 200,000 hours. Complete loss of transport capability occurs when 90 percent or more of the users cannot communicate to the network.

3. Network System design meets a:

(a) Mean Time Between Critical Failure (MTBCF) of 50,000 hours. A critical failure occurs when 20 percent of more of the users in EBNs cannot communicate with a minimum of 50 percent of the other network users

(b) Mean Time Between complete loss of transport capability of 100,000 hours. Complete loss of transport capability occurs when 90 percent of more of the users cannot communicate to the network.

*6.3.6 Hardware Integration Plan Review (HWIPR): The Contractor shall provide a narrative description:

a. *How to conduct an HWIPR on site at the conclusion of the Collaborative IP to:

1. Review the survey and collaboratively developed IPT documentation and IP development efforts integrated network.

2. Provide the government with enough data to issue an Authorization to Proceed (ATP) to the contractor for the final IP efforts and final documentation

b. Have submitted and received approval of the VSD prior to HWIPR

c. *Have submitted to the govt. “read ahead documents” that support the NW and DS implementation design (i.e. topologies, rack elevations, draft TSIP, draft training plan, draft cutover and test plan, horse blanket)

6.3.7 Final Documentation Acceptance (FDA). The contractor shall:

a. Host a document review/final writing conference at the contractor facility to finalize documentation preparation by a “hands on” working meeting of the IPT.

b. Have submitted to the govt. all CDRLs prior to FDA – for review

c. Conduct a line by line review of all documentation at the FDA.

d. Retain responsibility for document finalization, format and presentation.

*6.4 Installation:

6.4.1 Furnish Equipment: The contractor shall acquire and deliver to each base all material and equipment necessary to implement the ITS. The contractor shall install the selected ITS configuration for each base in the integration lab prior to delivery.

6.4.1.1 Installation requirements:

6.4.1.1.1 General. The contractor shall:

a. Install the integrated ITS IAW the Contract Data Package (CDP), BPD, Commercial Standards and Best Commercial Practices.

b. Conduct Quality Assurance inspections IAW ISO 9001 Standards.

c. Remove Spoils and Hazardous Materials encountered during installation IAW the approved Removal Plans.

d. Provide digital photographs (where permitted) of all network equipment locations, cable building entries, utility cuts and reconfigured manholes after completion of the installation.

e. Minimize disruption to base mission activities during installation.

6.4.1.1.2 OSP. The contractor shall:

a. Identify any existing obstructions and repair any damages caused during installation, boring or digging.

b. Restore all improvements such as pavement, curb, gutters, sidewalks, drainage ditches, shrubs, grass, etc. to a like condition.

c. When required to install fiber optic cable, pump all manholes/handholes.

d. When required, coordinate an AF Form 103 (Digging Permit) with the base Civil Engineer.

e. Implement, monitor and manage the NPDES Plan.

f. Comply with the environmental compliance items developed as conditions to the approved AF 813 or EA.

g. Repair any damage resulting from cutting underground utilities identified and marked by the base CE.

h. After base CE has marked underground utilities, maintain the marking until all construction work is completed.

6.4.1.1.3 Government Furnished support: The government will:

a. Sweep the area identified by the contractor and remove any EOD/UXO.

b. Remove any hazardous material encountered during trenching.

6.4.2 Cutover: The contractor shall:

a. Transition and integrate network connections to the ITS IAW the CDP.

b. Transition and integrate reused GFE fiber and equipment providing equivalent capability as would have been provided by contractor procured equipment.

c. Minimize interruption of network services to the base customers during cutover.

d. Coordinate and obtain approval for all planned outages with the designated site representative.

e. Ensure that the integrated ITS system provides users equivalent or improved capabilities after cutover.

6.4.3 Acceptance Test: The contractor shall:

a. Conduct all tests IAW CDP.

b. Dry run all tests prior to scheduling them for formal government approval

c. Conduct all tests on the fully integrated and cutover system, including newly procured and reused (GFE) equipment.

d. Minimize any disruptions of service to the operational network during testing.

e. If applicable, use only certified and / or calibrated test equipment.

f. Notify the government of when the testing in CDP is to be accomplished so that the Program Office representative can be present to witness and sign off successful tests.

g. Remedy any defects in material or workmanship disclosed by the testing procedures and then retest.

h. Maintain all test results on site. Make test results and procedures available to the government representative on request.

6.5 Training: Contractor shall:

a. Develop a comprehensive training plan that meets all requirements of the CDP and is tailored to the current capabilities of the base & NOSC personnel who will receive training.

b. Ensure that the Training requirements of the CDP are included in the vendor Request for Proposal package.

c. Conduct Training IAW the CDP and the approved schedule.

6.6 “As Built” Documentation: During installation the Contractor shall:

a. Maintain on site, electronic copies of the approved design.

b. Update changes to the design (to include redline paper drawings) on site as installation tasks are completed.

c. Be prepared to show the government representative(s) status and results of drawings/changes during the installation.

d. Provide Final As-Built documentation for each base that contains all the changes that occurred during installation.

6.7 Post Installation Support. For a period of 2 calendar months after the base signs the AF Form 1261 accepting the system, the contractor shall provide:

a. On site Network engineering support 8 hours/day, 5 days/week.

b. The support will be provided using a certified network engineer, who participated in the base network test & cutover.

6.8 System Acceptance: Prior to submitting the SF 1449 for Government acceptance of the system at each base, the contractor shall:

a. Ensure the entire system is cutover and operational.

b. Ensure any issues related to system test are resolved to the satisfaction of the government.

c. In coordination with the base, ensure all users are connected to ITS.

d. Have delivered all final CDRLs.

e. Assure the 1261 was signed

*6.9 Product Support:

*6.9.1 The contractor shall provide a narrative description on how to perform the installation for the following:

a. *Initial product support for the operating system, hardware and software for all new network switches and any new network management software. For Cisco reused switches collect the serial numbers and validate with the PMO if these are covered under Cisco SmartNet before applying any initial product support.

b. *Initial product support for all other hardware (GBIC, UPS).

c. *One year workmanship for work accomplished under this TRN.

d. *All relevant equipment product support data.

e. *Reused equipment will be covered under the CITS product support contract.

6.9.2 Hardware: Product support shall provide for repair or replacement of the failed item within:

a. Next Business Day (NBD) for network switches.

b. 48 hours for all other hardware items after the government notifies the vendor of the defect.

6.9.3 Software: The product support shall include:

a. Maintenance patches.

b. Version and/or major upgrades.

c. 24 Hour/day, 7 day/week Telephone support to resolve problems identified after installation.

6.9.4 Workmanship: The contractor shall repair any work defect within 10 workdays after the government notifies the contractor of the defect.

6.9.5 Time Period. The time period shall commence on the date the base representative’s signs the AF 1261 accepting the system from the PMO. If any product support requirement is modified during the Collaborative IP Process described above, the Contractor shall:

a. Revise this paragraph to conform to the agreed upon approach.

b. Submit the revision with the FDA ECP.

6.9.6 Help Desk: The contractor shall;

1. Respond to all CITS Help Desk generated requests for assistance on warranted equipment for the duration of the product support period.

2. Direct any product support calls received from base/MAJCOM personnel to the ENSC Help Desk (Commercial: 334-416-5771 Option 2, 1, 2 / DSN: 596-5771 Option 2, 1, 2.)

6.10 Government Furnished Support: The government will furnish the following support:

a.

Office space

b. Inside and outside storage for material & equipment.

c. Access to the base phone system

6.11 Technical Interchange Meetings(TIMs): If issues occur that would impact the schedule, cost or performance of the ITS, either the contractor or the Government can request a TIM.

6.12 Security Statement: Stated work and associated products shall be performed at the UNCLASSIFIED level. However, since access to classified areas may be required, all personnel who survey, design, install, test and/or cutover network equipment require a minimum of DoD Secret Security Clearance.

6.13 Data Rights: The contractor will furnish all data in accordance with the requirements of their contract or as separately agreed to by the government and the contractor.

12. ACRONYMS

LIST OF ACRONYMNS

ACRONYMN
MEANING
AF
Air Force
CDRL
Contract Data requirements List
CDP
Contract Data Package
CEBN
Critical End Building Node
CEECR
CITS equipment enclosure or communication requirement
CEL
Communications Equipment Location
CFLD
Communications Feature Location Data
CITS
Combat Information Transport System
PHASE
Contract Line Item
COTS
Commercial Off-The-Shelf
DS
Distribution System
DSN
Defense Switched Network
EBN
End Building Node
ENSC
Enterprise Network Support Center
FDA
Final Document Acceptance
FGDC
Federal Geographic Data Committee
FODP
Fiber Optic Distribution Panel
GFE
Government Furnished equipment
GIS
Geospatial Information System
GPS
Global Positioning System
HWIPR
Hardware Integration Plan Review
HVAC
Heating, Ventilation Air Conditioning & Cooling
IAW
In Accordance With
IP
Integration Plan
IPT
Integrated Product Team
ISO
International standards organization
ISP
Inside Plant
ITN
Information Transport Node
ITS
Information Transport System
LAN
Local Area Network
LOI
Letter of Introduction
LOM
List of Material
LRU
Line Replaceable Unit
MAJCOM
Major Command
MCP
Military Construction Program
MHDS
Manhole & Duct System
MTBCF
Mean Time Between Critical Failure
MTBF
Mean Time Between failure
MTTR
Mean Time to Repair
NBD
Next Business Day
NM/ND
Network Management/Network Defense
NPDES
National Pollution Discharge Elimination System
ODC
Other Direct Charge
OSHA
Occupational Safety & Health Administration
OSP
Outside Plant
OTDR
Optical Time Domain Reflectometer
SS&IP
Site Survey & Integration Plan
STEM
System Telecommunications Equipment Manager
SWPPP
Storm Water Pollution Prevention Plan
TIM
Technical Interchange Meeting
TRN
Technical Requirements Notice
TSIP
Telecommunications System Installation Plan

Section J, Attachment 14

FA8771-09-R-0019

File details come from the government source that posted it. Updated .