FA8771-16-R0023_Attachment_1_-_Performance_Work_Statement.pdf

PERFORMANCE WORK STATEMENT

AIR FORCE SYSTEMS NETWORKING (AFSN)

(17 May 2016)

1.0 OBJECTIVES: The AFSN Technical and Project Management Support Tasks encompass design analysis, testing (proof-of-concept, design verification/validation), implementation and installation, site acceptance testing and project closeout for network efforts at all network levels (i.e., base, intermediate (Network Operations and Security Center (NOSC)/Integrated Network Operations and Security Center (INOSC), etc.), and/or AFNET (the Air Force Enterprise Network). The Contractor will support AFSN efforts, as prioritized by either AFLCMC/HNI (C3I Infrastructure Division) or, under the auspices of the Memorandum of Agreement (MOA) between AFLCMC/HNI and AFLCMC/HIZ, 24th Air Force (to include its subordinate organizations). Details relative to these objectives can be found in paragraph 5.1.6 and the Service Summary table contained therein. PWS Paragraphs 4.1 and 4.2 outline the tasks required for satisfactory performance.

a) Complete enterprise network architectural analysis, to include Analysis of Alternatives

(AoA), for feasibility, thoroughness, security, reliability and provide recommended action to AFSN IAW CDRL A013, Network Systems Recommendation Report and the Base Information Transport Infrastructure (BITI) Quality Assurance (QA) Analysis Report, found in the CDRL table in paragraph 5.1.7 of this document.

b) Complete network/component removal, installation, configuration, testing and integration, troubleshooting and corrective actions associated with classified and unclassified networks to meet AFSN project implementation/installation schedules as required.

c) Provide Tier III network systems support for problem resolution as required.

d) Complete project management tasks for identifying, tracking, and coordinating implementation activities, with all project stakeholders (i.e., AFLCMC/HNI and their subordinate entities, base-level project management and operational personnel, 26 NOS (as required), and the INOSCs) within the specific AFSN timelines pertaining to each project/task.

e) Complete circuit actions (i.e., order, change, discontinue, upgrade, downgrade, track and manage the status of Air Force long haul communications circuits).

f) Complete Internet Protocol (IP) Address management actions to effectively plan, manage, assign, allocate and redistribute Air Force IP (IPV4 and IPV6) address space.

g) Complete AFSN Integration Facility testing and deployment of current and future (to include AoA efforts) information technology requirements.

FA8771-16-R0023 Attachment 1

h) Complete database systems administration, configuration management support to maintain, track and update the AFSN database and server.

NOTE: For those Contractor technical personnel (either individually, or as a team) performing duties outlined in paragraphs 4.1.2, 4.2.1, 4.2.6, 4.2.7, and 4.2.9 must be able to lift, move, or otherwise handle, heavy IT equipment/components (approximately 100lbs).

2.0 PLACE AND WORK HOURS:

2.1 Place of Performance.

The Government will provide property incidental to the place of performance (e.g. office space, desks, chairs, telephones, computers, and fax machines) at the AFSN facilities (offices and Integration Facility) at Maxwell AFB-Gunter Annex, AL. The Contractor will travel for work to Active Duty Air Force, Air Force Reserve (AFRC), Air National Guard (ANG), and/or DoD sites within the Continental United States (CONUS) and Outside the Continental United States (OCONUS).

2.2 Travel.

The travel noted in paragraph 2.1 above could be extensive and often includes weekend departures and/or returns to facilitate Monday morning starts to ensure timely completion of work. Additionally, Contractor personnel may travel with AFSN personnel, or on behalf of AFSN, to vendor conferences, working group meetings, technical interchange meetings, Configuration Control Board (CCB) meetings, and other information or technical meetings as required and tasked by the AFSN Contracting Officer Representative (COR). Daily Status Reports (DSR) will be required verbally or electronically during periods of travel. In addition, the Contractor will provide trip reports (CDRL A017) in-accordance-with the CDRL table found in paragraph 5.1.7 of this PWS.

The Contractor shall coordinate specific travel arrangements with the individual

Contracting Officer’s Representative (COR) to obtain advance, written approval for the travel about to be conducted. The Contractor’s request for travel shall be in writing and contain the dates, locations and estimated prices of the travel in accordance with the basic contract clause H047. Travel exceeding the previously negotiated cost ceiling requires written CO approval.

Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

2.3 Work Hours: The contractor shall attend all meetings scheduled by the Government. The AFSN office is typically open between between 6:00 AM and 5:00 PM (CST), Monday through Friday other than Holidays, and Base Closures. Work hours during travel will vary greatly depending on site availability, mission need, and approved Authorized Service Interruption (ASI) schedules. ASIs are routinely scheduled during non-duty hours to limit the impact of network changes system users.

3.0 DESCRIPTION OF SERVICES:

3.1 Scope of Work

The Contractor will provide enterprise level, intermediate level, and base level networking, analysis, design, proof of concept and component testing, site surveys, implementation, installation, site acceptance and IT project management support to the AFSN office. This support facilitates the development, adaptation and deployment, and sustainment of the Air Force (AF) Infrastructure. For the purposes of the PWS, and subsequent Contractor support, the Government defines the Air Force network as ranging from the base, post, camp, station Base Area Network (BAN) level, through the Wide Area Network (WAN) levels to the overarching Air Force Information Network level. Support provided under the contract will also include the Joint Regional Security Stack (JRSS) and Air Force portions of the Joint Information Environment (JIE). Examples of the range of the AFSN mission to support the various network levels include support for the implementation of the Base Information Transport Infrastructure (BITI) effort, which encompasses the recapitalization of the BAN and the JRSS which is at the enterprise level. The level of effort, and skill sets required, can vary from the very simple removing and replacing a component to exhaustive technical and project planning of a large, and highly complex, network implementation.

The Contractor’s efforts will directly support the AFSN mission to provide design, development, technical and programmatic support for the installation, sustainment and modernization of Air Force classified and unclassified data communications requirements, both wired and wireless networks. Lifecycle implementation projects could encompass complete system upgrades, or removal, and replacement of, some system components that become, or will soon become, End-of-Life (EoL) and/or End-of-Support (EoS). Operational Support efforts could include network system upgrades to support near term operational requirements or replacement of network equipment (routers, switches, media converters, Service Delivery Points (SDP), etc.).

4.0 Performance Requirements.

The tasks shown in paragraph 4.1 facilitate the AFSN Operational Support Functions mission.

Operational Support Functions include those tasks required to sustain the current “operational” Air Force Information Network (AFIN).

The tasks shown in paragraph 4.2 facilitate accomplishment of the AFSN Lifecycle Implementation Functions mission. Lifecycle Implementation Support includes projects to upgrade the current AFIN architecture or replace End-of-Life (EoL) or End-of-Support (EoS) components.

4.1 Specific Technical and Project Management Support Tasks (Operational Support Functions) (FFP CLIN):

4.1.1 Network Systems Technical Support: The Contractor shall provide network systems technical support to AFSN to include the following:

a) Design, engineer, implement, integrate, configure, and verify network solutions for highly complex requirements within the Air Force Information Network and AF portion of DoD Information Networks.

b) Provide Tier III network systems support to resolve operational problems for the C3I Infrastructure Division and the 26th NOS. Contractor personnel providing Tier III support will respond to “Non-Emergency” problems within 24 hours of notification and within one (1) hour of notification for “Emergency” problems.

c) Meet DoD 8570.1 certification requirements detailed in paragraph 5.1.8 of this PWS.

d) Develop detailed, comprehensive Implementation Plans (IPlan) (CDRL A016) that capture the full range of technical implementation activities from initial tasking to concept development, solution engineering, implementation, and project closeout.

e) Conduct thorough reviews and analysis of customer enterprise network, LAN/WAN, voice, data and image requirements for clarity and full understanding of the customer’s need.

f) Evaluate customer proposed technical solutions for feasibility, thoroughness, security, reliability and maintainability, timeliness to implement, and price effectiveness.

g) Provide recommendation to AFSN on customer’s proposed technical solution, or recommend an alternate technical solution to AFSN that meets AF and DoD architecture requirements for customer approval.

h) In the absence of a customer provided technical solution, develop/design a technical solution to satisfy customer requirements in an efficient, price effective manner and by need date.

i) Develop technical solution recommendations for large scale network requirements and document findings in a Network Systems Recommendation Report (CDRL A013)

j) Ensure Contractor developed technical solutions meet the customer’s feasibility, thoroughness, security, reliability and maintainability requirement(s).

k) Implement and integrate Government procured multi-vendor upgrades into the AF Network environment including routers/switches (i.e., Cisco, Juniper, HP, Foundry, etc.), firewalls (i.e., Sidewinder, Palo Alto, Source Fire, etc.) and servers.

4.1.2 Network Systems Implementation Support: The Contractor must be able to provide network systems implementation support at four (4), separate geographical locations (CONUS and OCONUS), simultaneously. The network systems implementation support the Contractor shall provide to AFSN includes the following:

a) Survey, install, configure, test and integrate wired, and wireless, network and cryptographic equipment into the AF Information Network. The Contractor shall provide the same level of support for base-level, and/or intermediate-level, network implementations. Note that installation work often requires an Authorized Service Interruption (ASI), typically scheduled outside of normal duty hours such as over weekends or at night.

b) Meet DoD 8570.1 certification requirements detailed in paragraph 5.1.8 of this PWS.

c) Provide in-briefs and out-briefs to base personnel as required for onsite visits.

d) Inventory and transport all required components, and materials, from the base storage facility to the base installation location(s). These equipment/components could include equipment chassis, internal blades/cards, Uninterrupted Power Supplies (UPS), and extended battery module(s), routers, switches, media converters, etc.

e) For equipment being removed and replaced, complete the systematic shutdown of the equipment, disconnect all cables (fiber and/or copper), and remove the equipment, remove specific blades/modules from equipment (as required for form, fit and function replacement projects), and remove the equipment from their respective rack(s).

f) Build, install, ground, and anchor equipment racks, if required, as part of the installation.

g) Install new equipment and properly secure new equipment in specified rack/equipment rack/cabinet, power on and configure equipment as required.

h) If required, install new blades/cards, or the blades/cards taken from removed equipment/components, into new equipment/components and place new equipment/components in their respective rack(s).

i) As required, employ DISA Security Technical Implementation Guides (STIG).

j) Install and connect UPS and extended battery module(s), in their respective rack(s) (as required).

k) Troubleshoot and resolve network issues that may arise.

l) Ensure pristine cable management and properly secure and label appropriate cable connections.

m) Perform site acceptance testing and complete the AFTO Form 747 for coordination and signature.

n) The Contractor will ensure the installation site is left in a clean and orderly fashion.

o) If equipment was removed, the Contractor shall turn it over to the base POC for local disposition unless it has been designated to be returned to AFSN. If the equipment is designated to be returned to AFSN, the Contractor will coordinate the Information Technology Equipment Custodian (ITEC) account transfer and shipment with the base POC. Additionally, the Contractor shall coordinate with the base POC for disposition of waste and any hazardous materials.

p) Provide trip reports and site drawings for all work performed. Upon completion of each installation, update engineering (As-Built) drawings (CDRL A020) depicting the actual installation. Deliver updated As-Built drawings (electronically) to the AFSN Project Manager for the base where the work was performed.

q) During installations, the Contractor shall provide daily status updates to the Government.

4.1.3 Integration Facility Support Services: The Contractor shall provide Integration Facility support to AFSN to include the following:

a) Conduct integration testing to support the insertion of Information Technologies Systems into the AF Information Network (AFIN).

c) Build detailed test plans, configure corresponding testing environment, and author test reports.

d) Prepare concise work statements, test data, and efficient procedures.

e) Apply attack and exploitation techniques and general security knowledge in the application of cryptography, network/systems security, authentication, and authorization in the design, development, testing to meet network security requirements.

f) Devise and perform appropriate tests to evaluate, debug and check equipment.

g) Develop and recommend technical solutions to perform all procedures necessary to ensure the security of enterprise networks and transactions across the AFIN. This task will culminate in the Contractor delivering a Network Systems Recommendation Report

(CDRL A013).

h) Conduct tests in compliance with AF/DoD suspense dates (to include Time Compliance

Network Orders (TCNO) and Information Assurance Vulnerability Alerts and Bulletins (IAVA and IAVB), etc.), track and document results through simulated and/or connected network systems.

i) Perform network traffic analysis, network design and analysis, and configuration of dynamic routing protocols.

j) Provide the configuration management and documentation of the technical baseline (hardware/software) of the AFSN Integration Facility.

k) Develop information technology/network solutions for operational requirements which will include accessing and maintaining configuration control of base architecture drawings and Internet Protocol addressing schemes.

l) As required, provide support for surveying, installing, configuring, testing and integrating network and cryptographic equipment in the AFIN.

4.1.4 Project Support: The Contractor shall provide IT Project Management support to AFSN to include the following:

a) Review customer requirements for clarity and communicate with customer to resolve any ambiguities in the requirement prior to entering into the AFSN database.

b) Enter new requirements/projects into the AFSN database.

c) Update project information and documentation in the AFSN database in timely manner.

d) Send requirement to the AFSN COR, through the AFSN database, for validation when technical/engineering support is required.

e) Establish new project folders, and maintain existing project folders, to ensure all relative documentation is accurate and complete.

f) Analyze implementation strategies to identify potential issues/risks to the proposed schedule and develop/recommend a viable plan to mitigate those issues/risks.

g) Identify, track and coordinate installation activities with project stakeholders.

h) Plan, schedule, control, execute and close entire projects, or segments of a project, to ensure delivered solutions meets customer/project requirements and is well documented.

i) Coordinate all AFSN directed implementation/installation activities with all appropriate stakeholders.

j) Assist sites in scheduling and processing Authorized Service Interruption (ASI) request packages as required.

k) Present implementation/installation efforts, IP Management Address and Circuit Action requests to the AFSN Peer Review (PR), either through attendance at the weekly peer review meeting or out-of-cycle via e-mail as appropriate, for approval.

l) Provide weekly timeline/schedule status, either through attendance at the weekly

Program Performance Review (PPR) meetings, or via verbal and/or e-mail responses to Government inquires.

m) Update project/task status in the AFSN database daily.

n) Have a minimum of one year (3 year preferred) project management, or personnel/resource management experience.

4.1.5 Circuit Actions: The Contractor shall provide circuit actions support to AFSN to include the following:

a) Review customer Requests for Service (RFS) to order, change, discontinue, upgrade, or downgrade a circuit (or circuits).

b) Monitor/provide quality control and guidance for RFS submitted to Air Force Space Command (AFSPC).

c) Communicate with customer to clarify any ambiguities in the RFS.

d) Enter RFS into the DISA web site.

e) Identify and coordinate shipment of components to facilitate completion of requested circuit action.

f) Coordinate the return shipment of components being removed from circuits discontinued (if required).

g) Track and manage the status of communications circuits daily.

h) Maintain and update the communications circuit configuration management database reflecting the current and projected long haul communications for Air Force sites.

i) Brief status of circuit action requests/requirements at AFSN weekly Peer Reviews (PR) and/or Project Performance Reviews (PPR).

j) Provide technical expert support, on circuits/circuit actions, to aforementioned meetings and other meetings (i.e., Technical Interchange Meetings (TIM), Integrated Product Team (IPT), etc.) as requested by the Government.

4.1.6 Internet Protocol (IP) Address Management: The Contractor shall provide IP address management support to AFSN to include the following:

a) Effectively plan, manage, administer assignment of, allocate and redistribute Air Force

Internet Protocol (IPv4 and IPv6) address space consistent with DoD addressing scheme.

b) Coordinate all Air Force IP block changes and/or assignments with the DoD Network Information Center (NIC).

c) Revalidate Air Force IP allocations every 3 years or sooner as required by DoD policy.

d) Assign, verify, and validate individual base and user IP addresses and ranges of addresses.

e) Respond to requests from DoD organizations to identify/locate Air Force IP address block owners.

f) Participate in Air Force and DoD meetings and working groups regarding IP addressing and policy.

g) Provide technical guidance on IPv6 protocols and potential transition mechanisms to support Air Force migration activities.

h) Develop and execute test plans in a laboratory environment to support integration of IPv6 technologies and protocols into the AF Information Network.

4.1.7 Basic Database Management: The Contractor shall provide barebones sustainment database management support to AFSN. This database tracks all AFSN Program Office customer network architecture requirements. The Contractor shall:

a) Provide a database manager to maintain the AFSN automated database (i.e., apply patches, MTOs, etc.) which is currently based on the Metastorm E-Work application.

b) Coordinate database privileges with the AFSN COR Personnel.

c) Take necessary actions to ensure AFSN data is preserved during operating system and backend Microsoft SQL Server upgrades.

d) Explore price effective and process improvement alternatives to enhance, or replace Metastorm E-Works.

4.1.8 Upgrade Metastorm E-Work Application: The Contractor shall upgrade AFSN’s current OPENTEXT/Metastorm E-Work (Version 7.6) Business Process Management (BPM) tool to the latest OPENTEXT/Metastorm E-Work BPM tool. This BPM database tracks all AFSN Program Office customer network architecture requirements. The Contractor shall:

a) Update AFSN database which is currently based on the Metastorm E-Work BPM version 7.6.

b) Copy data from Metastorm E-Work BPM 7.6 database to the new database.

c) Map processes from old version 7.6 to new version

d) Generate Entity Relationship Diagrams (ERDs) for new version.

e) Create new or revise queries and auxiliary databases in support of the new version for AFSN requirements.

f) Maintain a timeline of action items within the database and report status weekly. The

Contractor shall coordinate database privileges with the AFSN COR Personnel.

g) Take necessary actions to ensure AFSN data is preserved during Metastorm E-Work application upgrade.

h) Protect the integrity of the data and prevent the loss of data during the conversion.

4.2 Specific Technical and Project Management Support Tasks (Lifecycle Implementation Functions):

4.2.1 Base Network Implementation Support: Relative to Base Network Implementation Support and equipment/component removal/installations, the Contractor is responsible for the following:

NOTE: Base network implementation support is projected at 5 site surveys/5 installs per year with an average switch count per install of 80.

a) Meet DoD 8570.1 certification requirements detailed in paragraph 5.1.8 of this PWS.

b) Site Survey. The Contractor shall:

1. Physically Survey Communications Equipment Location (CELs) indicated on the Government-Provided Building List for each base.

2. Provide a Network Discovery Checklist (CDRL A012) that identifies network discovery activities that were completed during the site survey. Discovery activities include but are not limited to: network topology (physical and logical), network physical inventory, IP scope, device configuration, and power and HVAC load/capacity assessments.

3. Perform a network discovery using a Government provided automated tool such as Whats Up Gold—WUG and/or Airwave Management System to determine the baseline BAN at the base.

4. Update the Government-Provided Building Lists (CDRL A008) and complete the Equipment List Tool (CDRL A004) with verified information obtained during physical site survey and network discovery.

5. Survey and test spare fiber strands available for possible use in setting up a Critical BAN in parallel with the Baseline BAN for testing prior to cutover during the installation and cutover process. Testing of fiber must be accomplished utilizing a Government furnished Optical Time-Domain

Reflectometer (OTDR).

6. Upon site survey completion, and completion of all required Telecommunications System Implementation Plan (TSIP) updates, submit the TSIP to the Government for review. (CDRL A002)

7. Prepare and maintain an Integrated Master Schedule (IMS) (CDRL A003), as required, that reflects all tasks required to complete the project including Government dependencies. The IMS shall be in a Microsoft Project-compatible format. (CDRL A003) A separate schedule for each base is required.

8. Include in the IMS all contract deliverables, project meetings, milestones, reviews, inspections, base configuration timelines, Authorized Service Interruption (ASI) dates, status of applicable Air Force (AF) Forms, all required permits, quality assurance inspections and unique tasks and events requested by the Government.

9. Provide program oversight and management as necessary to track, manage, and report on the schedule and performance status of this project.

10. Create an IMS where all tasks (non-summary) have a predecessor and successor that will create a critical path.

c) Implementation. Contractor shall:

1. Develop detailed, comprehensive TSIPs (CDRL A002) that capture the full range of technical implementation activities from initial tasking to concept development, solution engineering, integration, implementation, verification, and project closeout.

2. As required develop detailed and comprehensive Qualification Test Plans (QTPs) (CDRL A005).

3. Ensure the TSIPs include physical site surveys, network design, and equipment mounting (to include associated patch/jumper cables, electrical power service and grounding) for the critical nodes. The Contractor shall ensure that the integration plan does not degrade existing network capabilities and services.

4. Submit all required draft AF Form 332s and send to the respective base POC for approvals.

5. This project does not include replacing inter-building or intra-building fiber optic and copper cables. However, replacing copper and fiber distribution patch panel cables may be required for equipment connectivity.

6. Implement and integrate Government procured multi-vendor upgrades into BAN environments (i.e., Cisco, Juniper, HP and Foundry, etc.), firewalls (i.e., Sidewinder, Palo Alto, and Source Fire, etc.)

NOTE: AFIN Installation support work often requires a corresponding approved Authorized Service Interruption (ASI), which is typically scheduled outside of normal duty hours such as weekends and at night.

7. Ensure the seamless interface and interoperation of the critical nodes with the noncritical nodes as part of this project. This project will upgrade the critical nodes, or subcomponents nearing End-of-Life/End-of-Support (EoL/EoS) bringing the Critical BAN into compliance with the Government provided Technical Requirements Document (TRD).

8. Build a mockup of Contractor’s technical solution, at a Government approved facility, to demonstrate it can be readily integrated into the existing site network environment, executable within the project schedule, and logistically supportable post installation. NOTE: This validation and verification could take place at a laboratory at Hanscom AFB, MA, a vendor laboratory, or the AFSN Integration Facility at Maxwell AFB-Gunter Annex, AL. The Mockup will be tested utilizing the QTP (CDRL A005) with Government furnished network analysis test equipment.

9. Provide detailed network (router, switch, and firewall) configuration files that depict the changes to the BAN baseline in a Network Configuration Submittal (CDRL A006) document to the Government prior to installation.

10. Provide a System Subsystem Design Document (CDRL A009) that details the contractor’s technical solution. Proposed technical solutions must comply with the DoD Unified Capabilities Approved Products List (UC-APL) at the time of Critical Integration Review (CIR) and Systems Acceptance by the base.

11. Maintain compliance with customer Government Technical Requirements Document (TRD).

12. Troubleshoot and resolve network issues that may arise during implementation.

d) Installation. The Contractor shall:

1. Inventory and transport all required components, and materials, from the base storage facility to the base installation location(s). These equipment/components could include equipment chassis, internal blades/cards, Uninterrupted Power Supplies (UPS), and extended battery module(s), routers, switches, media converters, etc.

2. Provide in-briefs and/or out-briefs to base personnel as required for onsite visits.

3. When practical, implement the technical solution in parallel to existing infrastructure.

4. During installations, the Contractor shall provide daily status updates to the Government.

5. If required by the TSIP, build, install, ground and anchor equipment racks, shelves, backer boards, etc.

6. Ensure all Contractor installed equipment is compliant with DISA Security Technical Implementation Guides (STIG), and that all procedures listed under the Qualification Test Plan (QTP) (CDRL A005) are fully tested and documented utilizing Government furnished network analysis test equipment.

7. Install and connect UPS and extended battery module(s), in their respective rack(s) (as required).

8. Ensure pristine cable management and properly secure and label appropriate cable connections.

9. Power on and configure new equipment IAW Government approved TSIP.

10. Ensure the installation site is left in a clean and orderly fashion.

11. If equipment was removed, the Contractor shall turn it over to the base POC for local disposition unless it has been designated to be returned to AFSN. If the equipment is designated to be returned to AFSN, the Contractor will coordinate the Information Technology Equipment Custodian (ITEC) account transfer and shipment with the base POC. Additionally, the Contractor shall coordinate with the base POC for disposition of waste and any hazardous materials.

12. Provide trip reports and site drawings for all work performed. Upon completion of each installation, update engineering drawings depicting the actual installation. Deliver updated As-Built drawings (electronically) (CDRL A020), TSIP (CDRL A002), Inventory Checklist/Record/Asset Management Form, (CDRL A007) and the Equipment List Tool (CDRL A004) to the Government.

13. Coordinate with the base POC for disposition of waste and any hazardous materials.

e) System Acceptance. Contractor shall:

1. Maintain a Quality Assurance (QA) Program.

2. Provide a QA inspection schedule for installation activities upon request.

3. Make available all QA inspection records when requested by the Government at any time during the performance of the contract.

4. Support Government network engineer visits to the base once all installation and cutover activities are complete, for wired and wireless installations, to conduct Audit/Inspection activities. Once Audit/Inspections are complete, the Contractor is responsible for any corrective actions identified by the Government engineer.

5. Support, test, and execute Critical BAN verification and validation activities as defined in the QTP. (CDRL A005)

6. Perform site acceptance testing and complete the AFTO Form 747 for coordination and signature.

7. For both wired and wireless installation projects, assist Government efforts to coordinate with base NCC personnel to obtain approval to use an automated discovery and configuration audit tool such as WhatsUp Gold from Ipswitch, Inc. on the operational BAN. This project shall include supporting the Government during discussions, negotiations, and briefings with appropriate base personnel for a suitable maintenance time slot and permission to make administrative changes to BAN switch configuration files during this audit and inspection period.

f) On-Site Support. After the base Government designee signs the AFTO FM 747 accepting the system, the Contractor shall:

1. Designate one installation team member who participated in the base Critical BAN cutover and test to remain on-site to provide network engineering support for 30 days. Eight (8) hours per day, five (5) days per week (Monday through Friday). The AFSN COR could direct a lesser period of time if warranted.

2. Provide network engineering support via telephone Saturday and Sunday for eight (8) hours per day.

3. Respond to base requests for support in resolving issues regarding the Critical

BAN.

g) Configuration Management (CM). Contractor shall:

1. Include documentation for IT Services, hardware, software, and baseline configurations.

2. Immediately notify the Government of any changes which affect the Contractor's established CM process.

3. Develop, implement and maintain CM processes, tools and infrastructure support across all aspects of the contract in order to facilitate attainment of program objectives.

4. Identify, collect, verify and store data in a Configuration Management System as identified by the Government. Periodic CM reviews may be conducted by the Government.

5. Conduct and maintain internal change management processes. The Contractor's change management process shall include specific, approved processes for identification of changes which may prompt the need for engineering change proposals or deviations from designs and architectures presented to or reviewed by the Government.

6. Designate a CM representative to serve as a primary point of contact to the Government for all CM matters.

7. As required define and maintain a CM program to provide Unique Identification (UID) control, status accounting and audit disciplines. The Inventory Checklist/Record/Asset Management Form (CDRL A007) will be provided to the AFSN COR in-accordance-with (IAW) paragraph 5.1.9 of this

PWS.

8. The CM principles contained in MIL-HDBK-61 may be used for guidance.

4.2.2 Audit Support. Provide compliance audits to assist AFSN in verifying implementations completed by outside BITI PMO integration contractors, ensuring that implementation meets industry best practices, and DISA STIGs. May be required to travel on a limited basis. The Contractor shall:

NOTE: Audit team will remediate audit scans for BITI bases. The historical number of bases per year is approximately 45.

1. Review the implementation documentation for highly complex network solutions against DISA STIGs, BITI TRD, and industry best practices and provide an Audit Analysis Report (CDRL A021) of any discrepancies.

2. Support multivendor upgrades into the AF Network environment including routers/switches (i.e., Cisco, Juniper, HP, Foundry, etc.)

3. Provide analysis, and troubleshooting support for network discovery outputs obtained by a Government provided automated tool such as WhatsUp Gold— WUG and/or Airwave Management System to determine the baseline BAN at the base.

4. Provide network discovery tool maintenance on Government provided hosting equipment by applying vendor release patches, and operating system security patches. Produce monthly release IAW CM plan.

5. Create Regular Expressions (REGEX) audit scripts as required in support of network discovery scanning

6. Test all REGEX scripts in a Government provided integration facility against Original Equipment Manufacturer (OEM) equipment.

7. Remediate audit script errors resulting from scans conducted using Government provided automated network discovery tools such as WUG.

8. Provide pre-verification analysis, and obtain site specific sample configurations at least 1 week prior to audit for each device model at the BITI PMO integration Contractor’s immersion lab utilizing network scanning tools such as WUG. Provide findings utilizing Audit Analysis Report (CDRL A021).

9. Provide feedback to the BITI PMO integration Contractor and the Government on any nuances of the network under test/evaluation. Provide the Government and BITI PMO integration Contractor an Audit Analysis Report (CDRL A021) that needs to be remediated with respect to scan outputs provided by network discovery. The Audit Analysis report shall be accomplished during BITI PMO integration Contractor immersion lab scanning, prior to cutover, and post cut over of newly deployed OEM equipment. Recommendation reports shall include STIG deficiencies, configuration inconsistencies, audit script errors, and site specific rationale for deviations from best practices, and STIG deficiencies. Audit scans/remediation will be a repetitive process between the integration Contractor and audit team for the integration Contractor’s immersion lab, and Pre/Post install scans until Audit Analysis Report (CDRL A021) findings are at an acceptable level for Government approval.

10. Coordinate with the BITI PMO integration Contractor, base communication squadron, and AFLCMC/HNI PMO on issues that must be remediated to meet industry standards.

11. Ensure compliance with BITI TRD, and DISA STIG prior to installation of

OEM equipment as provided in Audit Analysis Report (CDRL A021).

12. Track STIG evolution and assess impacts to audit compliance scripts.

13. Store all network discovery outputs to a Government provided secure location. All outputs must be saved in Government agreed upon format based off of BITI PMO Contractor immersion lab scans, pre cutover scans, and post cutover scans.

4.2.3 Trusted Agent Support. The Contractor shall assist AFSN in reviewing the technical portion of project implementations accomplished by outside BITI PMO integration vendors contracted by the Government. The contactor shall:

NOTE: Trusted Agent support is estimated at 20 sites (simultaneously) (4 sites per FTE).

Meetings will be deconflicted to ensure no more than 5 occur simultaneously.

a) Review the implementation documentation for highly complex network solutions against DISA STIGs, BITI TRD, and industry best practices and provide an Audit Analysis Report (CDRL A021) of any discrepancies.

c) Project kickoff meeting. The Contractor Shall:

1. Participate in a Site Survey & Integration Planning (SS&IP) phase kickoff meeting at customer provided location after contract award on a date established by the Government.

2. Provide read-ahead versions of agenda items and meeting materials electronically prior to the scheduled meeting.

3. Conduct a review of the TRD with the BITI PMO integration Contractor and notify the Government of any areas of concern with respect to the requirements.

4. Review all Government Furnished Information (GFI) prior to the kickoff meeting and have questions ready for discussion.

5. Produce meeting minutes for kick off meeting and submit to Government

(CDRL A014)

d) Survey Requirements Confirmation. Contractor Shall:

1. Review the Government-Provided Building Lists to scope site survey requirements prior to the Survey Requirements Confirmation (SRC) and present a basic plan for the site survey.

2. Review Baseline BAN information provided as GFI prior to the SRC.

3. Discuss base support coordination with the Communications Squadron, Civil Engineering Squadron, external agencies, and other stakeholders as appropriate.

4. Demonstrate to the Government an understanding of site survey requirements.

5. Present a methodology for replacing existing Baseline BAN nodes with new BAN nodes while minimizing network downtime and interruption of services to end-users.

6. Present and discuss the site survey plan.

7. Assure technical data captured during site survey is adequate to support proper technical solution.

e) Vendor Integration Confirmation. The Contractor shall:

1. Confirm technical solution meets Government standards (i.e., project Technical Requirements Document (TRD)).

2. Conduct a review of the TRD with the BITI PMO integration Contractor, and document any areas of concern with respect to the requirements and provide to the Government.

3. Validate that proposed technical solutions (to include utilization, placement and configuration, of network components) are readily integrated into the existing site network environment, executable within the project schedule and logistically supportable post installation. NOTE: This validation and verification can take place at a laboratory at Hanscom AFB, MA, a vendor laboratory, or the AFSN Integration Facility at Maxwell AFB-Gunter Annex, AL.

4. Perform compliance audits at a laboratory at Hanscom AFB, MA, a vendor laboratory, or the AFSN Integration Facility at Maxwell AFB-Gunter Annex, AL and on the installed network at the base immediately prior to Cutover and Government Witness Test (GWT).

5. Perform onsite audits of the installations to identify, troubleshoot and resolve any issues prior to installation completion and site acceptance testing. NOTE:

Depending on the size and complexity of the installation(s), these audits could begin within a week prior to installation completion and site acceptance testing.

6. Government Witness System Verification - Contractor shall witness, on behalf of the Government, the System Acceptance Test (SAT) and make recommendations to the Government as to “pass” or “fail”. If “fail”, the Contractor in collaboration with the integrator shall identify and describe remediation efforts to attain successful installation.

7. Verify (audit) the operation of the upgraded network after installation and cut-overs are completed.

8. Contractor may also be responsible for providing Government assistance during Audit/Inspection activities, for both wired and wireless installations, which includes validating audit results performed by other vendor company personnel.

9. Receive and evaluate findings in the audit report and explain what the errors actually mean to the Communications Squadron POC and BITI PMO integration Contractor engineers so that corrections/adjustments can be made to the BAN components.

10. As required, verify implementation of DISA Applications Security Technical Implementation Guides (STIG).

11. Ensure the AFTO Form 747 is properly filled out, coordinated and signed.

12. Review all project completion documentation (i.e., As-Built Drawings, Trip Reports, After Action Reports, etc.). Ensure CDRLs are properly completed and delivered to the Government IAW the CDRL table found in paragraph

5.1.7 of this PWS.

13. Contractor shall be responsible for technical review and validation of CDRLs A002 Telecommunications System Installation Plan (TSIP), A005 Qualification Test Plan (QTP), A009 System/Subsystem Design Document (S/SDD), A015 Test Report, and the A022 BITI QA Analysis Report. As required the results of these technical reviews will be documented in the Network Systems Recommendation report (CDRL A013) and delivered to the Government.

14. The Contractor shall support and execute BAN verification and validation activities as defined in the Qualification Test Plan (QTP) Template (CDRL A005).

4.2.4 Trusted Agent Project Support (In support of 4.2.3): The Contractor shall provide IT project management support to assist AFSN in reviewing the IT project management portion of base network implementations accomplished by outside integration vendors which are contracted by the BITI PMO. The Contractor shall:

NOTE: Trusted agent project support is estimated at 16 sites (simultaneously) (4 sites per FTE). Meetings will be deconflicted to ensure no more than 4 occur simultaneously.

a) Review customer requirements for clarity and communicate with customer to resolve any ambiguities in the requirement prior to entering into the AFSN database.

b) Enter new requirements/projects into the AFSN database.

c) Update project information and documentation in the AFSN database.

d) Send requirement to the AFSN COR, through the AFSN database, to obtain technical/engineering support.

e) Establish new project folders, and maintain existing project folders, to ensure all relative documentation is accurate and complete.

f) Analyze implementation strategies to identify potential issues/risks to the proposed schedule and develop/recommend a viable plan to mitigate those issues/risks.

g) Identify, track, coordinate and facilitate installation activities with project stakeholders to ensure project implementation schedules are not adversely affected and the quality of work performed is acceptable.

h) Plan, schedule, control, execute and close entire projects, or segments of a project, to ensure delivered solution meets customer/project requirements and is well documented.

i) Coordinate all AFSN directed implementation/installation activities with all appropriate stakeholders.

j) Assist sites in scheduling and processing Authorized Service Interruption (ASI) request packages as required.

k) Provide weekly timeline/schedule status, either through attendance at the weekly Program Performance Review (PPR) meetings, or via verbal and/or e-mail responses to Government inquires.

l) Update project/task status in the AFSN database daily.

m) Have a minimum of one year (3 year preferred) project management, or personnel/resource management experience.

n) Integrate Product Team (IPT) Support. The Contractor shall:

1. Provide technical support to the Government established IPT membership and provide input to the Government IPT chairperson relative to IPT scheduling.

2. Conduct a weekly IPT meeting for each base for the duration of the project to discuss project progress and issues.

3. Allow for IPT meetings to be held during 0600 to 1800 EST for OCONUS bases to account for time differences.

4. Include the BITI PMO integration Contractor, the base, the PMO, and other stakeholder organizations identified by the Government.

5. Support Technical Interchange Meetings (TIM) to address price, schedule, or performance issues. Prepare and deliver minutes for the TIMs. (CDRL A014)

6. Keep a current copy of the BITI PMO integration contractors Integrated Master Schedule (IMS) that reflects all tasks required to complete the project including Government dependencies.

7. Provide program oversight and management as necessary to track, manage, and report on the schedule and performance status of this project.

4.2.5 Minor Electrical Support. The Contractor shall provide minor electrical services from a licensed electrician on an as needed basis to power equipment installed under this PWS. The

a) Provide a master electrician licensed for the area where the base is located. Personnel must comply with the National Electrical Codes, laws, and regulations for the base/area.

b) Physically survey CELs indicated on the Government-Provided Building List for each base requiring electrical power upgrades.

c) Provide detailed electrical drawings indicating building and room numbers, breaker panels, power terminations, receptacle types, wire gauge, conduit path(s), etc.

d) Identify all site specific electrical components required for new circuit (breakers, wiring, plugs, conduit, electrical boxes, mounting brackets, etc.)

e) Provide a detailed price estimate to include labor and materials required to complete the power upgrade. Price estimate must include a per CEL breakdown.

f) Submit proposed solution to the Government for Contracting Officer (CO) approval.

g) Once approved by the CO, purchase required list of materials to complete power upgrade. Complete the installation and integration of new electrical circuits, from breaker to plug, to meet the codes, laws, and regulations for the base/area.

4.2.6 Lifecycle Implementation Support. The Contractor shall provide lifecycle network implementation support to:

a) Design, engineer, implement, integrate, and verify network solutions for highly complex requirements within the Air Force Information Network and AF portion of DoD Information Networks.

b) Meet DoD 8570.1 certification requirements detailed in paragraph 5.1.10 of this PWS.

c) Conduct detailed analysis of AF Information Networks and provide recommendations in a Network Systems Recommendation Reports (CDRL A013) to optimize or improve network efficiency and performance. If approved by the Government for implementation, execute optimization recommendations.

d) Identify, track, report, and mitigate potential implementation risks

e) Develop detailed, comprehensive IPlans (CDRL A016) that capture the full range of technical implementation activities from initial tasking to concept development, solution engineering, implementation, and project closeout.

f) Implement and integrate Government procured multi-vendor upgrades into the AF Network environment including routers/switches (i.e., Cisco, Juniper, HP, Foundry, etc.), firewalls (i.e., Sidewinder, Palo Alto, Source Fire, etc.) and servers.

g) Survey, install, configure, test and integrate network and cryptographic equipment into the AF Information Network or the AF portion of the DoD Information Network.

h) Build, install, ground, and anchor equipment racks if required as part of the installation.

i) Install new equipment and properly secure new equipment in specified rack/equipment rack/cabinet, power on and configure equipment as required.

j) Troubleshoot and resolve network issues that may arise during implementation.

k) As required, employ DISA Security Technical Implementation Guides (STIG).

l) Develop detailed site survey reports, Project Support Agreements (PSAs), test readiness review minutes/reports, test artifacts, and AFTO Form 747s.

m) Support Technical Interchange Meetings (TIM) as directed by the Government to address price, schedule, or performance issues. Prepare and deliver minutes (CDRL A0014) for the TIMs.

n) Prepare and maintain an Integrated Master Schedule (IMS) (CDRL A003) that reflects all tasks required to complete the project including Government dependencies. The IMS shall be in a Microsoft Project-compatible format. A separate schedule for each effort is required. Include in the IMS all contract deliverables, project meetings, milestones, reviews, inspections, base configuration timelines, Authorized Service Interruption (ASI) scheduling windows, status of applicable Air Force (AF) Forms, all required permits, and quality assurance inspections to provide a work plan within the specified period of performance (PoP).

o) Provide technical expertise to address Urgent Operational Needs (UON) and other short notice or emergency type requirements

p) Conduct/attend weekly IPT meetings for each effort for the duration of the project to discuss project progress and issues.

q) Provide trip reports (CDRL A0017) and site drawings for all work performed. Upon completion of each survey provide a site survey report (A011) and upon completion of each installation, update engineering (As-Built) drawings (CDRL A020) depicting the actual installation. Deliver updated as-built drawings (electronically) to the Government.

r) Provide project management support to compose, coordinate, and publish all PSAs, coordinate with applicable stakeholders relative to status of allied support efforts, coordinate all technical and programmatic documentation with the affected organizations and advise AFSN of…