2 BIM IDIQ PWS IV1.pdf

AFLCMC/HNI Connect Portfolio

Base Infrastructure Modernization (BIM)

Indefinite Delivery Indefinite Quantity (IDIQ)

Performance Work Statement (PWS)

Prepared By:

AFLCMC/HNIB

15 Eglin Street, Building 1607 Hanscom AFB, MA 01731-1700

DD MMMM 202Y

DISTRIBUTION STATEMENT D: Distribution authorized to DOD and US DOD contractors only; Administrative or Operational Use; DD MMMM 202Y. Other requests for this document shall be referred to AFLCMC/HNI (DOD Controlling Office) 15 Eglin Street, Building 1607, Hanscom AFB, MA 01731-1700.

HANDLING AND DESTRUCTION NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of contents or reconstruction of the document.

DRAFT

TABLE OF CONTENTS (TBC)

1. OVERVIEW

1.1. Purpose

The purpose of this Multiple Award IDIQ Contract is to modernize network infrastructure at United States Department of the Air Force (DAF) bases throughout the world.

This PWS describes the overarching scope of work to be performed. Specific requirements will be identified in individual Task Orders (TOs) and may require performance of some, or all, areas of efforts described in this document. The scope of this IDIQ and subsequent TOs will include other work related to, but not necessarily identified in this PWS.

1.2. Background

This IDIQ will be awarded and executed by the Air Force Life Cycle Management Center Enterprise IT & Cyber Infrastructure Division and will act as the overarching effort to modernize the Base Area Network (BAN).

An EITaaS integrated program office was formed with SAF/CN, PEO C3I&N, and ACC/A6 personnel, to conduct a Risk Reduction Effort (RRE) to experiment with commodity EITaaS delivered by commercial service providers. Utilizing the authorities under 10 U.S.C. 2373, EITaaS conducted experiments at eight (8) DAF installations to develop lessons learned that would inform a DAF enterprise-wide acquisition. The EIT Portfolio requirements were split into five (5) distinct portfolios; Compute and Store, Connect, End User Devices, Enterprise Services, and Protect. The acquisition strategy is to respond to the HQ ACC validated requirements in the Connect Portfolio. This effort takes lessons learned from the EITaaS RRE Network-as-a-Service effort as well as lessons learned from existing Base IT Infrastructure modernization efforts to modernize the future Base Area Network (BAN) offering at DAF bases world-wide.

This effort intends to modernize the Non-classified Internet Protocol Router (NIPR) and Secure Internet Protocol Router (SIPR) BAN through an as-a-service model utilizing contractor provided networking services. The contractor will have to modernize, operate and maintain base network infrastructure to meet Service Level Agreements (SLAs). The SLAs will be outlined in the TOs and will be more aggressive than previous DAF networking contracts. This PWS may use the acronym BAN to describe its requirements, this is commonly referred to as Campus Area Networks (CAN) in the industry. The deployment of the modernized base network will provide an infrastructure to support future Zero Trust efforts. The effort will also include the deployment of two-factor authentication (2FA) capabilities, 802.1x and Network Authentication Controls.

1.3. Current Environment

The BAN is the Department of Defense (DoD) Information Network (DoDIN) Non-classified Internet Protocol Router Network (NIPRNet) and Secure Internet Protocol Router Network (SIPRNet) extension within a USAF base. The BAN architecture is comprised of wired network components, wireless network components, inside plant cabling, outside plant cabling, and distribution services. Depending on the configuration, other networks may/may not be tunneled inside NIPR, while other networks will run on parallel V-LANs across the transport-layer of the

BAN.

The BAN network nodes are installed in buildings on base in physically secure areas such as data centers, lockable dedicated rooms (communications closets), or open office areas in lockable cabinets. These node locations in buildings are referred to as Communications Equipment Locations (CEL). The Wireless system is an enterprise capability that provides the DAF BANs a single standard transport for wireless systems. It is an extension of the BAN wired infrastructure and it connects base wireless clients to the Air Force Network (AFNET)/NIPRNet via that Infrastructure. The Secure Internet Protocol Router Network (SIPRNet) is a classified network used by the DoD to communicate classified information. A High Assurance Internet Protocol Encryptor (HAIPE) is a Type 1 encryption device that complies with the National Security Agency's (NSA) Interoperability Specification for tunneling traffic through lower classification level networks. The BAN is commonly used as a backbone for interconnectivity between SIPRNet HAIPE devices on the “BLACK,” or classified, side. The currently deployed wireless and wired systems are monitored and managed by a variety of personnel in the Active-Duty Integrated Network Operations and Security Center (INOSC), Air National Guard Network Operations and Security Center (GNOSC), and base communication squadron personnel. The currently deployed network provides ample capacity for various mission networks on a given base, a contractor shall be expected to provide capacity for mission networks that will be identified in the TOs. The number of mission networks on a particular base/TO will vary.

The state of environment across the DAF is a complex array of fragmented and disconnected approaches to the BAN; caused through an overall lack of integration, direction, prioritization, and dedicated funding. Every base has been responsible for their own network maintenance, which overall, has occurred on an irregular basis, only when critically needed and resolution of this problem has consistently been deferred to out-years. The DAFs BAN has never kept up with industry. Some bases are decades behind the industry in terms of infrastructures, others are only a few years behind. As it currently stands, most bases should have semi-modern hardware across their network. However, that current hardware may consist of multiple routers in a space that only requires one, leading to equipment being dilapidated or misused.

The Government anticipates that the contractor will have to adapt to significantly unique situations at each base. For example, this could include redundant equipment, equipment beyond its end of life or end of service expectation, and/or deficient cabling. This current environment is what this BIM IDIQ will address.

1.4. Goals and Objectives

Modernize and emulate industry best practices for the DAFs BAN. This will be accomplished through this BIM IDIQ vehicle. The BIM IDIQ is a DAF initiative leveraging industry to provide standardized, innovative, and agile Information Technology services across the Air and Space Forces. The goals to increase integration through a modern streamlined network that keeps up with the industry standards, utilizes best practices, performance, and modern management techniques to provide the DAF with a capable network to perform its missions. This IDIQ and subsequent TOs intends for the network to be treated as an investment for future mission sets.

The Government wants to create a unified, performant, and uniformly maintained network environment that will be a game changer for Multi-Domain Operations. This effort intends to meet the overarching goals of the DAF Chief Information Officer (CIO). The goals of the DAF

CIO:

• Innovate for Competitive Advantage

• Optimize for Efficiencies and Improved Capability

• Evolve Cybersecurity for an Agile and Resilient Defense Posture

• Cultivate Talent for a Ready Digital Workforce

• EITaaS RRE Transition

1.5. Scope

Each TO will be issued with a PWS directing the contractor to enable the rapid transformation of the DAF’s base-centric IT to an enterprise approach leveraging industry best practices. TOs could include more than one base assigned, but there will only be one PWS per TO.

The scope of this IDIQ is to furnish, upgrade, test, install and maintain all NIPR and SIPR BAN wired and wireless components and to include monitoring and sustainment of the network according to the EITaaS Production Capabilities Document (PCD). The contractor shall conduct a complete BAN site survey to inform their design, test, installation, and delivery of a network solution that complies with the PCD. Bases with flightline operations may have additional requirements that will be defined in a TO PWS.

The contractor shall provide the Government with services that include taking over operations of the existing base network and running the base network to meet SLAs standards. A base is defined as everything within the boundary of the main base, in addition to the Geographically Separated Units (GSU) and other locations assigned to that base. In addition, the contractor shall be required to provide the following, non-exhaustive, items: technical expertise, technical services, analysis of alternatives, agile schedule adjustments to improve project timeline and recommended best practices.

2. GENERAL REQUIREMENTS (Overarching Requirements)

2.1. Program Management

2.1.1. Government Responsibilities

A Government Program Manager will be assigned to perform a variety of tasks/roles for the Government to manage the performance of the contract and contractor. At a minimum the Government will maintain open communication with a contractor. This communication may occur from on-site personnel and/or the program office. Any official direction from the Government will originate from the program office contracting officer or a delegated representative. Any communication from other Government parties to the contractor should be directed to the program office and contracting officer. This includes base leadership. However, direction from any Government personnel shall be followed when the issue pertains to safety, exercises, or any other urgent matters. The program office may assist the contractor in matters that require a Government representative to liaison, facilitate, organize or mediate with other Government personnel; The Government will not mediate interactions between a contractor and a secondary contractor, only Government to contractor interactions.

2.1.2. Contractor Responsibilities

The Contractor shall be expected to be open, clear, and transparent with the Government on the processes, challenges, successes, and operations needed throughout the life of the IDIQ and any awarded TOs. Clear, accurate and timely communication from the Contractor shall be required to ensure the Government can work to mitigate and reduce implementation problems that may arise.

The contractor shall integrate and coordinate all activity required to execute TOs and manage the timeliness, completeness, and quality of problem identification and resolution. The contractor shall coordinate with the Program Management Office (PMO), TO Representatives at the individual bases, and External Agencies as detailed in TOs.

Contractor employees shall identify and introduce themselves as contractor personnel and display distinguishing badges or other visible identification for meetings with Government personnel. In addition, contracts shall require contractor personnel to appropriately identify themselves as contractor employees in video-teleconferencing, telephone conversations and in formal and informal written correspondence.

The Contractor shall deliver status reports providing corrective action plans, timely identification of issues, and effective management of sub-contractors. The status reports shall also provide planned Contract Data Requirement List (CDRL) deliveries, planned trips, and recommendations for any additional tools, manpower, and support required for successful execution of a TO.

An appropriate Secret or TS/SCI security clearance shall be required and adjudicated for all personnel that will need to access the NIPRNet and SIPRNet. See Section 2.16 for additional security requirements, however, the appropriate clearance level requirements will be specified in the TOs. NIPRNet will require a Common Access Card (CAC) for personnel to be coordinated through the PMO.

2.2. Kick-Off Meeting (KOM)

2.2.1. IDIQ Kick-Off

The Contractor shall participate in a KOM scheduled by the Government. The form the meetings take, whether it’s via teleconference or in-person, will be at the discretion of the Government.

The Government will introduce team members and staff and will discuss administrative operations pertinent to the IDIQ. A general overview of an expected schedule and the overall approach for forthcoming TOs. Additionally, the Government may onboard contractors onto the IDIQ throughout the life of the contract. The Government intends to host these meetings with new contractors but will only conduct them as necessary to meet on-boarding needs. The Contractor shall provide an agenda and minutes for the KOM. (CDRLs A001 & A002)

2.2.1.1. Contractor Briefing

The contractor shall provide a hard copy of a briefing to the Government upon joining the IDIQ.

This briefing shall demonstrate the current organizational structure, primary and secondary contact for the Government, Staffing plan, partnerships with other companies, and geographical footprint. The contractor shall provide contact details to the Government at this KOM (CDRL A003).

2.2.2. Individual TO Kick-Off

The Contractor shall participate in a KOM which will be scheduled by the Government. The form the meetings take, whether its via teleconference or in-person, will be at the discretion of the Government. The Contractor shall introduce team members and staff and shall present and discuss administrative operations pertinent to performing tasks and a general overview of the overall approach to execute this TO. The Contractor shall provide an agenda and minutes for the KOM. The contractor shall provide personnel rosters at the KOMs and shall provide updated rosters when changes occur. Additional specifics for the TO kick-off will be included in each TO.

2.2.3. Installation KOM

An additional KOM shall be conducted between the PMO, TO Representatives at the individual bases, and the contractor prior to any installation or surveying activity being conducted. The goal of the installation KOM is to inform the base leadership and other parties of the contractor actions prior to beginning work. The contractor shall coordinate with Government Representatives for the bases assigned. The Contractor shall present status of base support coordination and the status of all preparations made for the effort. The contractor shall present and review the Cutover and Methodology section of the Telecommunication Systems Installation

Plan (TSIP), along with any added assumptions. The contractor shall present a detailed and completed cutover schedule.

The contractor shall present the plan to minimize network downtime and interruption of services to end-users. The contractor shall identify any tasks, approvals, or scheduling where extraordinary lead time is required. The contractor shall present upgrade diagrams, in DISA format, and supporting technical information. The contractor shall review the verification, audit, and acceptance criteria. The contractor shall prepare and submit KOM minutes IAW Exhibit A instructions (TO CDRL AXXX).

2.3. Integrated Product Team (IPT) Meetings

Per TO direction, the contractor shall host IPT meetings with the Government to provide progress, critical path updates and facilitate risk discussions. The contractor shall provide agendas and minutes for these meetings. The frequency and topic of these IPT meetings will be addressed within the applicable TO PWS; Meeting topics the contractor shall participate in will include, at a minimum, financial forecasting report, Technical Interchange Meetings, Program Management Reviews (PMR), Risk reviews and other meetings at the request of the Government.

This could include various feedback gathering meetings over the course of the IDIQ to evaluate documents, gather contractor feedback, and incorporate changes that the Government deems required. The contractor shall provide an up-to-date personnel organizational chart at each IPT Meeting.

2.4. Associate Contractor Agreements (ACA)

The Contractor shall enter an ACA for any portion of a TO requiring joint participation in the accomplishment of Government requirements. These agreements shall be made in coordination with the Government and conform to all parts of AFFAR 5317.90. Agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to this project, which shall ensure the greatest degree of cooperation to meet the terms of the contract. ACAs shall be delivered to the Government immediately following ratification by all parties.

2.5. Risk Management

Throughout performance of TOs, the contractor shall plan for and establish a process for identifying, tracking, and mitigating project cost, schedule, and performance risks. The contractor shall incorporate risk mitigation strategies into project planning and technical activities. Use of contractor risk reporting tools and format are acceptable. The Government may require the contractor to utilize a standardized format issued by the PMO/Portfolio.

Risk status shall be reviewed periodically, but quarterly, at a minimum, by the Contractor and provided to the Government. The risk review may be conducted in conjunction with existing

Contractor/Government meetings, key milestone events, or upon request. Contractor shall identify risks and develop a recommended mitigation plan. The contractor shall report program risks and risk mitigation strategies in the Monthly Status Report (MSR) in addition to presenting risk report information at the IPT Meetings, PMRs, and document them as appropriate. (TO CDRL AXXX) The contractor shall incorporate risk mitigation strategies into program planning and technical activities.

2.6. Travel

Contractor personnel may be required to travel in support of TOs and will be responsible for making all travel and lodging arrangements to meet TO requirements. Travel may include locations within the continental United States (CONUS) or outside of the continental United States (OCONUS).

Unless otherwise stated within a TO, the contractor shall not exceed the rates identified by the General Services Administration for CONUS travel (https://www.gsa.gov/travel/plan-book/per-diem-rates) or the Department of State for OCONUS travel (https://aoprals.state.gov/web920/per_diem.asp).

Unless otherwise stated within a TO, the contractor shall submit all costs associated with travel to the Contracting Officer to be evaluated for reasonableness prior to incurring the costs. The Government will not reimburse costs determined to be unreasonable. Examples of unreasonable costs include lodging in excess of the limits stated above, excessive types or quantities of rental vehicles, or excessive airfare arrangements. The Joint Travel Regulation (https://www.defensetravel.dod.mil/site/travelreg.cfm) is not applicable to contractors, but it will be referenced in the Government’s evaluation of travel-associated costs.

2.7. Transfer of Equipment Ownership

Any equipment purchases made by a contractor for this contract that will reside, or be installed, on a Government location shall transfer their ownership to the Government before installing, operating, or performing work. All hardware, software, or licenses on this contract and subsequent TOs will be Government owned, and Contractor operated. All equipment purchased under this IDIQ and subsequent TOs will comply with FAR 52.245-1. Any equipment, purchased by the contractor prior to a TO award, that is used in a contractor owned location or in monitoring the network, such as a Network Operations Center (NOC), is not required to be turned over to the Government. However, any Contractor Owned equipment must be approved and authorized by the Government for use with the understanding that known intelligence is dynamic and changes to the authorized environment will be required to change rapidly. However, should a contractor install equipment in a NOC solely to manage, sustain, operate, monitor or otherwise perform work on this contract, it shall be Government owned.

Upon receipt of equipment, the TO Contractor shall establish a property custodian and utilize the currently approved property accounting management system for the equipment. The contractor will then ensure all equipment, and related software license and maintenance agreements are registered with the OEM and ownership transferred to the Government with product support for hardware replacement, software upgrades and patching, licensing, and telephonic technical support, beginning upon transfer of ownership to the Government. The contractor shall be issued the item as Government Furnished equipment (GFE) and will assume responsibility for maintaining any equipment issued. The contractor shall ensure that all Government Furnished materials, whether information, equipment or otherwise, is returned to the Government, under any circumstance. In no circumstances will materials purchased on a cost-reimbursement basis be retained by the Contractor following the end of performance on a TO.

The Contractor shall provide all base specific details regarding contractor product support for hardware replacement, software upgrades and patching, licensing, and telephonic technical support coverage and populate the Government Furnished Information (GFI) Product Support Form ID-0134C IAW the GFI Product Support Instructions. The delivery of the Product Support Form shall follow Government acceptance of a Qualification Test Report.

The contractor shall ensure ownership title has been transferred to the Government following operation, install, and successful test.

2.8. Transition Services

The Contractor shall provide detailed Transition Plans IAW the required TO CDRL. The contractor shall perform transition services necessary to ensure an effective transition-in and transition-out of other contractor and Government support. The contractor shall also ensure continued system operations and maintenance, as well as an orderly transition period without any interruption or loss of proficiency of services within a negotiated timeframe.

The Contractor shall operate the equipment and hardware present at a TO assigned base until the equipment requested has been installed. The contractor shall fix, remedy, and/or otherwise reconfigure the equipment at the base to improve the network performance, integrity, and resilience. If the contractor finds and subsequently removes any duplicative equipment during this time, that equipment may be utilized elsewhere on that base. Should that equipment be deemed obsolete, end-of-life, or end-of-service the contractor shall return that to the Government.

The contractor may continue to utilize hardware currently on base to meet SLAs should the contractor deem the equipment useful and or appropriate. Should the TO contractor propose equipment for a base that the base already has, the contractor shall provide additional rationale for the proposed duplicate equipment.

2.9. Schedule

The contractor shall generate and maintain an overarching Integrated Master Schedule (IMS) for the life of the BIM IDIQ that will be executed in an agile manner. The schedule shall contain and track planned activities, events, milestones, and document accomplishments (progress) from cradle to grave and be delivered in accordance with the CDRL. The contractor shall be expected to provide an IMS at the TO level. The contractor shall provide the Government rationales for schedule changes and slippages, as well as a plan to rectify or adjust schedule delays. The contractor shall evaluate any risks associated with the IMS and provide the Government with mitigation plans.

2.10. Data Management

The contractor shall provide all data in accordance with the TO CDRL, Exhibit (A) (DD 904 Form 1423), and Exhibit (B). The contractor shall manage the control, status accounting and distribution of TO CDRL items and other non-CDRL data. The contractor shall provide automated data feeds IAW TOs. The data feeds shall be made accessible to the Government. The data feeds will encompass data such as cybersecurity, network metrics and other types.

Additional specifics for data feeds, such as, the type of information shown, access to the information by the Government/PMO, and other information requirements will be specified within individual TOs.

The contractor shall provide an organized, online repository. The contractor shall manage the control, status accounting and distribution of CDRL items. The contractor shall provide the PMO with unrestricted electronic access to all document locations and the capability to successfully read and download, and ensure all posted documents are in a searchable format. The contractor shall provide logs and alerts to existing Security Information and Event Management (SIEM) and log management to support analytical and defensive cyber operations (i.e., Enterprise Logging Ingest and Cyber Situational Awareness Refinery (ELICSAR)).

The Contractor shall produce (create/write/edit) Base Infrastructure Modernization (BIM) Operations and Maintenance PTOs as required to support the objective of the Air Force organic system operation and field-level maintenance for the system life cycle - details will be provided with each Task Order (TO).

2.10.1. Data Accession List (DAL)

The contractor shall deliver a DAL to the Government including unrestricted electronic access (downloading capability) to all documents relevant to the execution of the program during a TO for each individual base. Items in the DAL include, but are not limited to:

• Reports • Configuration Item Lists

• Technical Studies and Analysis • White Papers

• Technical Documents • Meeting Briefs

• Technical interchange meeting briefings • Meeting/working group minutes

• Trade Studies • Control Plan (I.E Corrosion Control)

• Lessons Learned • Assessment and authorization (A&A)

• History of Version Upgrades

2.11. Product Support

The contractor shall develop and maintain a Product Support Plan (PSP). The contractor shall also deliver the Product Support Form (PSF) (TO CDRL AXXX). The PSP documents the sustainment plan for the Enterprise IT environment, major areas including but not limited to:

Requirement, Product Support Strategy, Manpower & Training, Maintenance plan & Management, Computer Resources, Design Interface, Sustaining/Systems Engineering, Budget & Funding, Program Transition to Government operators or other contractor operators. The PSP is continually updated throughout the products Life Cycle.

2.12. Supplier Management

The contractor shall develop, execute, and deliver a Supply Chain Risk Management (SCRM) Plan. (TO CDRL AXXX). The contractor shall scan their full spectrum supply chain and identify, assess, plan for, and mitigate actual or potential threats, vulnerabilities, and disruptions to the DAFs BIM supply chain throughout the lifecycle to ensure mission effectiveness. When assessing supply chain risks, the contractor shall consider supply chain risk categories identified by the Department of the Air Force to include but not limited to:

• Technology and Cybersecurity

• Economic

• Transportation and Distribution

• Manufacturing and Supply

• Financial

• Product quality and design

• Political and Regulatory

• Foreign influence

• Human Capital

• Compliance

• Environmental Risks

The contractors SCRM Plan shall include a description of how the contractor shall protect the supply chain from exploitation due to the insertion of counterfeits/malware, unauthorized production, tampering, theft, insertion of malicious software and hardware, functionality alteration, and any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations. The contractor shall inform and include the Government in any mitigations or alterations to the program.

The contractor shall define the process for reporting incidents and shall inform the Government of incidents impacting BIM. In accordance with DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, the contractor shall report cyber incidents to the Defense Industrial Base Cyber Security Program (https://dibnet.dod.mil) and shall also report cyber incidents to the responsible contracting officer, with reporting on the most severe cyber incidents, defined as Common Vulnerabilities & Exposures (CVE) score of 7.0 or higher, not to exceed three (3) days after initial detection. The contractor shall detail how they will be adhering to recommendations found within NIST SP 800-161r1, which focuses on Cybersecurity (C)- SCRM. Specifically, the contractor shall detail how they actively monitor for threats to their, their suppliers, subcontractors and associated integrators supply chains with intent to proactively identify and respond to threats emanating from their supply chain. The contractor shall also establish formal processes and intervals for continuous monitoring and reassessment of their, their suppliers, subcontractors and associated integrators supply chains to proactively identify potential changes to the risk profile; examples of supply chain risk events include items like change in location for manufacturing or software development from domestic to foreign locations. The outcomes of the active monitoring and reassessments of supply chains shall be reported to PMO designated team to include Cyber Security, PM, EN, ISSM and Intelligence. If there are changes to the C-SCRM posture that cannot be adequately mitigated to within acceptable levels, as determined by the PMO, it may be grounds for termination of the contract.

The SCRM Plan shall address the broad spectrum of supply chain risks that have the potential to:

jeopardize the integrity of products, software, services, people, and technologies; compromise intellectual property; disrupt the flow of product, materiel, information, and finances needed for continued Air Force operations; and drive materiel cost increases to the program. The contractor shall develop and execute processes for identifying supply chain risks as early as possible; the persistent and comprehensive tracking, monitoring, and re-evaluation of supply chain risks and their corresponding mitigation actions; and communicating supply chain risks to affected stakeholders and the Government. The contractor shall provide a Supply Chain Risk Tracking Report for identified actual and potential supply chain risks. The contractor's SCRM program Plan and processes shall apply to the prime and their suppliers, subcontractors, associated integrators, and vendors, spanning the entirety of the supply chain, from raw material stage to delivery of a finished product, software, and/or service.

The contractor shall also inform and work with counterintelligence agencies such as Office of Special Investigation and the Federal Bureau of Investigations to address foreign intelligence threats. This shall include allowing counterintelligence agencies access to personnel who work on BIM for the purposes of briefings and debriefings. The contractor shall allow counterintelligence agencies access to personnel and facilities for the purpose of conducting counterintelligence operation and investigations in support of BIM.

2.12.1. Counterfeit Protection

The Contractor shall:

• Manage a risk-based counterfeit detection and avoidance program for all components

• Track components down to the electronic part level, including the associated software and firmware

• Have a process to maintain traceability to enable association with the original manufacturer

• Ensure the use of original manufacturers or sources with verifiable designation of authority from the original manufacturer, including authorized aftermarket manufacturer

• Pass down counterfeit detection and avoidance requirements to subcontractors at all levels of the supply chain

• Deliver only Trade Agreement Act (TAA) compliant hardware IAW FAR Section 52.225-5 and identify white label items

• Quarantine all suspect products pending further direction from the PMO

• Make certain the parts and all members of the lot procured for use on this contract are stored in correct environmental controls

• Within two (2) business days of discovery or lower-level notification, notify the cognizant

Contracting Officer (CO), Contracting Officer Representative (COR) and the System PM of all suspect items identified

• Make certain that the original documentation is secured as evidence and maintain any and all documentation associated with the part to include:

o Part information such as part identifying number, lot date code, manufacturer information and originator/point of contact information.

o Any information reflecting part procurement/acquisition traceability (e.g., a copy of the purchase order, any and all correspondence between the buyer and the supplier to include e-mails, records of phone conversations and paper letters of correspondence).

o Part documentation from the purported original manufacturer, distributors, and suppliers (certificate of compliance and certificate of conformance).

o All visual examination and physical analysis/testing results and the technical data package showing that the parts passed the required screening and qualification tests.

o List of company products affected.

2.13. Place of Performance

This enterprise effort will support the worldwide presence of all USAF, USSF, Reserve, and Guard bases/garrisons and associated GSUs within the CONUS and OCONUS. GSUs will be apportioned out with their respective parent base.

2.14. Government Furnished Equipment, Information and Property

The Government will provide access to requisite program and technical information that is necessary to carry out the requirements of this PWS and/or a TO PWS. The Government will provide access to facilities, equipment, software tools, and technical information necessary for the performance of this contract. Base support items may include, but are not guaranteed, office space, desk, telephone, printer, access to electronic mail, and computers, when deemed appropriate by the Government. In addition, the Government will provide access to appropriate systems. Contractor personnel shall not use Government resources in violation of any Federal, State, or Local statute, regulation, or policy. Contractor personnel that require access to Government networks must obtain access approval. Equipment, Software or materials meeting the definition of Government Furnished Property will be identified in a list attached to the IDIQ.

Individual TOs will more specifically identify the requirements in this section.

The Contractor shall provide the Government with a list of hardware required to transform and modernize the BAN at a given base provided in a TO. A base may include several GSUs that are controlled by the base specified in the TO, the contractor shall include these locations when transforming and modernizing a given base, unless otherwise specified. This list of hardware will be checked and evaluated by the Government for reasonability and then the Government will compete it among the Small Disadvantaged Business (SDB) Hardware Pool. The SDB selected by the Government shall order and deliver the equipment to the Contractor, who takes ownership of the equipment in the Contractors NIL. The Contractor deploys the equipment and, together with the Government, validates the operation of the equipment. The SDB hardware providing contractor may be present for this testing. The presence of the hardware providing contractor will not be reimbursed for travel with the sole purpose of being present for validation. Following validation, the TO Contractor shall turn over ownership of the equipment to the Government.

The TO Contractor will establish a property custodian, utilize the currently approved property accounting management System for the equipment, and sustain the equipment until directed otherwise.

2.15. Other Direct Costs (ODC)

ODCs include materials, software, and other miscellaneous expenses. All ODCs proposed under individual TOs must include cost and basis of estimate and shall be acceptable to the PMO and approved by the Contracting Officer prior to purchase. The contractor shall maximize use of the DoD Enterprise Software Initiative (esi.mil) for any software licenses required. The contractor shall procure any other items needed to accomplish the work spelled out in a TO Work Statement as determined during execution and agreed to by the Government.

2.16. Security

The nature of this work requires access to classified and unclassified information. The work performed by the contractor includes access to classified and unclassified data, information, and spaces, ranging from Secret through and including TS/SCI. The contractor shall be required to attend meetings at classified and unclassified levels. Specific security requirements are part of the DD-254.

All personnel employed by the contractor in the performance of this contract, or any representative of the contractor entering the Governmental Installation shall abide by all security instructions and directives of the base. Employees are responsible for safeguarding all Government property provided for contractor use. At the close for each work period, Government facilities, equipment and materials shall be secured, lights, heat and water turned off and all doors and window secured. This will be included in the Visitor Group Agreement between the contractor and the hosting base.

The contractor and, as applicable, subcontractor shall not employ persons for work on this contract if such employee is identified as a potential threat to the health, safety, security, general wellbeing or operational mission of the installation and its population, nor shall the contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified during the Criminal Background Check (CBI).

Contractors shall ensure their employees and those of their subcontracts have the proper credentials allowing them to work in the United States, as well as the ability to gain access to an installation; IAW Executive Order 14012, Employees and subcontractors later found to be undocumented noncitizens will be remanded to the proper authorities. The contractor shall submit any request for compensation on delays to the Contracting Office for approval. The contractor shall notify the Contracting Office or authorized representative as soon as the contractor realizes/determines of any potential delays in accordance with the terms and conditions of this requirement.

All contractors and subcontractors when working in a Controlled, Restricted, or other sensitive area must be escorted, at all times. All contractors and subcontractors when working on any portion of the network that could generate classified material shall be required, at a minimum, to hold the clearance level associated with the level of potential material generation, including physical or remote work or operations. The military agency or unit responsible for the project area or work is responsible for providing the escorts, the contractor shall be responsible for the coordination required to receive an escort. The contractor shall follow existing procedures and instructions for obtaining entrance to restricted or controlled areas.

2.17. Safety

The contractor shall comply with applicable Occupational Safety & Health Administration (OSHA) federal, state, local and base safety regulations; for any overseas location the contractor may be required to operate under additional guidelines specified by the host nation. The contractor shall coordinate with the base safety office for any additional safety requirements and/or parameters. The contractor shall comply with all confined space OSHA regulations and remediate unsafe practices identified by the PMO, base safety officer, COR, or CO. In addition, the contractor shall notify, both verbally and in writing, to the PMO, base personnel, contract officer representative and contracting officer if equipment is unsafe/work is being performed in an unsafe manner.

2.17.1. Hazardous Waste

The contractor shall dispose of waste IAW with host nation, federal, state, local and base standards/guidelines and remove waste and hazardous materials encountered during installation IAW base approved procedures and obtain written verification to provide to the PMO. The contractor shall provide any and all documentation of any hazardous waste generation, usage, removal, or any other means to the base safety office, PMO, COR and CO, IAW the TO CDRLs.

The contractor shall remove project generated waste (e.g., construction debris, packaging materials) and hazardous materials and obtain written verification to provide to the base. The contractor must use approved methodology to minimize the amount of lead paint or asbestos disturbed in order to install equipment IAW with host nation, federal, state, local and base standards/guidelines. The contractor shall include copies of final receipts and manifests to the PMO in the Hazardous Waste Report (TO CDRL AXXXX).

2.18. Quality Control (QC)

The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with the TO PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program (QCP) is how they assure themselves that their work complies with the requirement of the contract. The contractor shall deliver the QCP to the CO and COR within 30 days after contract award, and within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system. The Contractor shall ensure the accuracy and completeness of all CDRL deliverables. The contractor shall develop and implement procedures to identify, prevent and ensure non-recurrence of defective services.

The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). The QASP will be supplied with each TO.

A QASP may be tailored to each TO. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable performance measures. The contractor shall adhere to the threshold requirements outlines in the QASP.

The Contractor shall be published at Level 3 or higher for Capability Maturity Model (CMM), Capability Maturity Model Integration (CMMI), or CMMI Development using the Software

Engineering Institute's (SEI) Standard CMMI Appraisal Method for Process Improvement (SCAMPI) (Method A) by an SEI-authorized lead appraiser for the entire performance period of the contract, inclusive of options. Formal certifications shall be held at the organizational level performing the contract. Evidence of comparable Systems Engineering (SE) processes will not be accepted. The contractor shall ensure any major subcontractors also must be published at CMMI Level 3 or higher. The Government reserves the right to perform reference checks and/or validate certifications.

2.19. Performance Objectives / Service Delivery Summary / Quality Assurance Surveillance Plan

The Government will provide these objectives, plans and summaries at the TO level. The Government will evaluate the contractor’s performance under this contract in accordance with the QASP. The contractor shall comply with the thresholds outlined in the QASP during all phases of this project. Methods used to assess performance and resolve issues or unacceptable performance will be specified in the QASP.

3. SERVICES SUMMARY

The specific services required will vary and be identified under each TO. While not exhaustive with regards to the details, the following outlines some of the various types of service, performance, and support that will be required by TOs. Develop a plan documenting the roadmap to providing wired and wireless network services on assigned Department of Air Force installations. The Contractor will be performing actions on both NIPRnet and SIPRnet and shall have the ability to create, process, and handle classified information should the requirement arise.

3.1. Documentation Requirements

The documentation requirements of work performed under this IDIQ will vary according to the requirements of each TO. The following list is not exhaustive but represents examples of documentation that will be required by TOs.

• Mark documentation appropriately (STINFO & Classification)

• Develop TSIP for system components

• Develop Qualification Test Plans for system components and overall system

• Develop Qualification Test Procedures for system components and overall system

• Develop System Acceptance Test Plans for system components and overall system

• Develop System Acceptance Test Procedures for system components and overall system

• Develop an overall System/Subsystem Design Document (S/SDD) for each unique configuration item

• Develop an Equipment List Tool for the existing and proposed NIPR & SIPR system components

• Submit a Monthly Man-Hour Expenditure Report

• Submit an MSR

• Develop a Quality Assurance Plan

• Record and distribute formal minutes

• Document all ad hoc discussions

• Document all hazardous waste generation, usage, removal, or any other means

• Record and distribute formal minutes for all meetings (e.g., IPT meetings, TIMs, PMRs, teleconferences, and conferences) with the PMO, base personnel, and other agencies related to this project.

3.1.1. SIPR Documentation Requirements

Any documentation that is required for NIPR network requirements will be required for SIPR, when appropriate. All documentation for SIPR generated by the Government or Contractor shall be classified, controlled and marked in the appropriate manner.

Specific Deliverables not labeled above:

3.2. Base Connectivity

The services with respect to base connectivity will include at a minimum, classified and unclassified wired/wireless infrastructure, other classified and unclassified services, and network performance and health monitoring. Specific details on connectivity measures are available in Appendix A and B.

• Classified Wired/Wireless Infrastructure o Support operation of cryptographic devices.

• Unclassified Wired/Wireless Infrastructure o Support operation of cryptographic devices.

• Classified and Unclassified Services

• Network Performance and Health Monitoring

3.3. Network Design & Engineering Support

The contract shall be given the responsibility to provide and sustain a modernized redundant network design along with engineering support. The contractor shall utilize an appropriate mixture of the following redundancy methods: fault tolerance full hardware redundancy and high availability. The contractor shall be responsible for the maintenance required should any systems fail, break or under any circumstances become inoperable, regardless of circumstance. The contractor shall not reduce any existing wireless coverage. Any existing coverage areas shall continue to have equal or better coverage.

3.4. Site Survey

The goal of the site survey is for the contractor to understand the base at the origin of the contract. The contractor shall perform a detailed site survey and deliver the report to the PMO.

The site survey performed should provide the contractor with enough information to provide the Government/PMO with a Hardware List to purchase equipment for the network.

3.4.1. Survey Requirements Confirmation (SRC)

The contractor shall:

• Participate in a minimum two-day SRC Meeting. The contractor’s Project Manager, lead network engineer, lead wireless engineer and Distribution Systems (DS) engineer shall be present at the SRC meeting.

• Review the Equipment List Tool (ELT) and any Baseline BAN information provided as GFI to scope site survey requirements prior to the SRC.

• Review the existing radio frequency (RF) infrastructure to ensure WLAN coverage of identified requirements and examine each equipment installation location to determine the specific materials, equipment, and personnel required to perform the installation.

• Discuss base support coordination, including, but not limited to, Communications Squadron and Civil Engineering Squadron, and the offices listed below:

o CE: Electrical shop, 332 Approval process, Environmental Shop, and Drafting Shop.

o Base Communications Infrastructure.

o NCC personnel.

o Plans and Programs o Security Forces o Airfield Manager o Spectrum Manager o Base Safety Office o Munitions Safety for radiation near live ordinance o Personnel safety for radiation near humans o Information System Security Manager (ISSM)

• Discuss external agencies coordination.

• Request one escort from base infrastructure office to support removal of unused jumpers from FODPs while site survey is being completed.

• Discuss base requirements for an Airspace and Airfield Criteria Waiver should construction take place around the airfield.

• Post any Procurement Contracting Officer (PCO) approved changes to the ELT and to the contractor repository within three (3) business days.

• Present a detailed plan to perform a site survey and discuss the survey plan.

• The contractor shall meet the following SRC exit criteria in-order to begin the site survey:

o Base-approved Equipment List Tool.

o Prime contractor coordination with stakeholders (CE, SF, CS etc.).

o Prime contractor understanding of AF 103, AF 332 & AF 813 process.

o Obtain all required building…