Atch 1 Performance Work Statement 19Jul23.pdf

McEntire Joint National Guard Base 169th Fighter Wing

A I R N A T I O N A L G U A R D

Installation Notification and Warning System (INWS)

Performance Work Statement (PWS)

19 July 2023

Table of Contents 1 Scope

1.1 Background

1.2 Tasks

1.3 Period of Performance

1.4 Place of Performance

1.5 Operating Hours

1.6 Recognized Holidays/Base Closures

1.7 Quality Assurance

1.8 Prohibited – Utilization of Personal Electronic Devices

2 General Contractor Requirements

2.1 Air Force Privacy Act

2.2 Air Force Messaging

2.3 Security Requirements

2.4 CAC Requirements

2.5 Training Requirements

2.6 Identification of Contract Employees

2.7 Combating Trafficking in Persons

2.8 Data Rights

2.9 Organizational Conflicts of Interest

2.10 Contract Administration

2.11 Non-Disclosure Agreement

2.12 Cyber Security and Systems Security

3 Specific Contract Requirements

3.1 Post Award meetings and Reports

3.2 Initial/One Time Project Deliverables

3.3 Recurring Deliverables

3.4 Qualifications of Suppliers and Contractors

3.5 Site survey Requirements

3.6 Design Requirements

3.7 System Requirements and Components

3.8 Installation Requirements

4 Contract Deliverables

4.1 Contract Data Requirements Listing (CDRL)

5 Definitions and Acronyms

5.1 Definitions

5.2 Acronyms

Attachment 1 General References, Standards, Codes and Guidance

Attachment 2 Performance Requirements Summary

Attachment 3 Data Item Descriptions

1. Scope The Air National Guard is located at more than 180 locations, varying in size, airman population, and mission. The Installation Notification and Warning System (INWS) is a combination of notification methods using audible/visual signals, verbal messages, and electronic communications and must provide all elements of a robust mass notification system including interfaces. The INWS project includes design, installation, configuration, and integration of a Wide-Area Mass Notification System (aka Giant voice) and Indoor Mass Notification Systems (to include visible and audible devices) for identified facilities. The system shall be integrated with associated Network Centric Alerting System (NCAS), automated telephone (robo) calls, Simple Message Service (SMS) text alerts, simultaneous LMR and Giant Voice activation. The system shall interface to the base Public Address (PA) system and provide alert precedence override from both the MNS Control station (overrides PA head-end equipment), and from the individual building MNS Autonomous Control Unit (ACU) (for single building override). The vendor shall provide any additional hardware, software, and material not already on hand; and all expertise and training; for the entire integration of the systems described above.

1.1 Background

1.1.1. Following the tragic shootings at Ft. Hood, the DOD reviewed its protection policies. The findings of that review;

Secretary of Defense Memorandum: Protecting the Force, Ft. Hood Follow on Review August 18, 2010; points out the deficiencies and gaps in the security environment and gives final recommendations from the follow-on review. The Independent Review found that many DOD installations lack mass notification capabilities. The purpose of the mass notification warning system is to provide warning and response direction for all personnel within 10 minutes of incident notification and verification. Ultimately, a robust mass notification system is needed at all DOD locations. More recent active shooter events across the country, have emphasized the need for a robust INWS capability that informs all military personnel when a threat is present in their geographic locality.

1.1.2. This effort will encompass implementation of mass notification in compliance with the DOD antiterrorism requirements as specified in Unified Facility Criteria (UFC) 4-010-01. This effort will implement UFC design standards and recommendations for mass notification systems as provided in National Fire Protection Association (NFPA) Standard 72 (including Annex E) and UFC 4-021-01 Design and O&M: Mass Notification Systems, Change 1. The ultimate goal is to achieve an integrated level of coordination of DOD mass notification capabilities with national systems as required by Executive Order 13407, Air Force Instruction 10-2501 states that every Air Force installation must have a rapid and effective system to disseminate emergency information quickly.

1.1.3 Buildings that have been recently renovated or constructed may have combined Fire Alarm/Mass Notification systems that includes all appropriate strobes, ACUs, LOCs, etc. In the event a building is already UFC compliant, the building will be integrated with the base INWS as part of this project.

1.2 Tasks

1.2.1. Fulfillment of tasks defined within this initiative must provide all professional and technical personnel as well as materials to perform various planning, site survey, design, construction, technical documentation, quality control, and certification efforts necessary to comply with this Performance Work Statement.

1.2.2. The programmatic approach for this initiative establishes the following hierarchical sequence for primary tasks as depicted in the Work Breakdown Structure in Figure 1.

• Site Survey

• Project Support Agreement Development

• Design Verification and Update

• Design Approval

• Equipment Inventory and Procurement

• Verification of Installation of Existing Equipment

• Installation of New Equipment and Integration

• Acceptance Testing

• Certification (IA/Security )

• Training

1.2.3. Communication methods to be addressed in subtasks include:

• Giant Voice

• Central Control Station(s)

• Individual Building Mass Notification System (including speakers, strobes, ACUs and LOCs)(PA speakers will not be utilized for this effort)

• Integration with Network Centric Alert System (NCAS) (computer tones/windows popup)

• Integration with Automated Calling/SMS Text Messaging services

• Integration with APCO P25 compliant LMR GV announcement

• Integration with and interfaces to PA

Implement INWS at Selected Locations

Survey Site § Certified BICSI/NICET

Designers § Building Comm Rooms § Building Utility Rooms § Building Fire Alarm

System § Interior Audio

Speakers § Interior Fire Alarm/

MNS Strobe Lights § Exterior HPSA/GV

Loud Speaker Locations § Electronic Signage

Fundamental Design to Reach Target

Architecture

PSA & Attachments § Vendor Installation

Access § On Site Storage Rqmt § Site Plan Markup (Base

Layout drawing and/or GeoBase Aerial GIP) § Space Reservations

(FPI Reservation, Rack Elevation, Wall Backboard, Pathways, Cables, etc.)

§ Construction Support

(Comm Room, Grounding/Electrical Service, Interior/ Exterior Cable Paths, Exterior Speaker Support Structures, Lightning Protection, etc.)

§ NPDES

§ AF Forms 332, 103 and

§ DD Forms 1494

Identify INWS As-Is Conditions

Detailed Design to Reach Target Architecture

Install INWS Systems

INWS Design § Central Control Station

Design § Local Operating

Console Placement § Building Speakers &

Stobe Placement § INWS Fire Alarm

Building Integration § Exterior HP Speaker

Arrays (HPSA) Placement § System Health

Monitoring (audible & silent) § Existing Systems

Interface (Fire Alarm, Electronic Signage, LMR, CATV, etc.)

§ INWS System

Integration Design (Electronic Signage, LMR Broadcast, CATV, etc.)

INWS Install Plan § Project Schedule § Comm Mgt Plan § Risk Mgt Plan § IA Scty / RMF Plan § QC Plan § Accept/Test Plan

§ LOM

§ User/Maintainer

Training Plan

INWS Site Work § Central Control Install/

Modification § Building System Install § Fire Alarm Integration § HPSA Install § Electronic Signage/

CATV Integration § LMR Channel

Integration

Figure 1: INWS Government Work Breakdown Structure (GWBS)

1.2.4. A site visit may be conducted and is highly recommended. All interested vendors will be afforded the opportunity to survey the physical site and examine existing infrastructure with a government representatives available to answer questions. Vendors will be expected to develop a proposal submission with associated bid costs (including key personnel qualifications, costs for installation, training plan, training equipment and training materials, warranty and certification tasks) for government technical review and comparative best value determination and vendor selection.

1.3 Period of Performance

The period of performance will be 12 months from date of award.

1.4 Place of Performance

Place of performance McEntire Joint National Guard Base. The government will provide Adobe formatted drawings. The vendor will be responsible for delivering all as-built drawings in both autocad and Adobe .pdf format.

1.5 Operating Hours

The contractor shall provide services during the base’s normal duty hours to the maximum extent possible, except on recognized US holidays or when the Government facility/installation is closed due to local or national emergencies, administrative closings, or similar Government-directed facility/installation closings. System downtime for installation/integration of INWS systems will be coordinated with local unit personnel to minimize impact to mission operations.

1.6 Recognized Holidays/Base Closures

The following are recognized US holidays. The contractor shall not perform services on these days:

New Year’s Day: January 1st Martin Luther King, Jr.’s Birthday President’s Day Memorial Day Independence Day: July 4th Labor Day Columbus Day Veteran’s Day: November 11th Thanksgiving Day Christmas Day

1.6.1 Additional federal holidays or time off declared by the President of the United States or Government employees may be given “59 minutes” early release. In these events, the Contractor personnel shall seek appropriate guidance on duty location from his/her Contractor supervisor. The contractor shall at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS when the Government facility/installation is not closed for the above reasons. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the work force are essential.

1.6.2 Telework. Telework is not authorized

1.6.3 Unscheduled Gate / Base Closures. Unscheduled gate closures by the Security Forces may occur at any time causing all personnel entering or exiting a closed installation to experience a delay. This cannot be predicted or prevented.

Contractors are not compensated for unexpected closures or delays. Vehicles operated by contractor personnel are subject to search pursuant to applicable regulations. Any moving violation of any applicable motor vehicle regulation may result in the termination of the contractor employee’s installation driving privileges.

1.6.4 Contractor shall not report to work on those days the Government or installation is closed due to inclement weather, national emergencies, or other events requiring installation closure. During periods of closure, the Contractor shall work with the Government to determine payment terms; any payments will be subject to CO approval. For official AF or base-level Family Days, or holidays granted by Executive Order, the Government is not liable for the Contractor’s costs incurred for work at the locale affected by the shutdown. In all cases (including normal workdays), when Government personnel are not available in the building/location of work to oversee Contractor activities, Contractor personnel shall leave the premises but are allowed to work at the local Contractor’s office. Costs incurred for work will not be reimbursed.

1.6.5 Performance of Services during Crisis or Emergency Conditions. In the event of a crisis, services on this contract have been determined as non-essential and do not require continued support during the crisis.

1.7 Quality Assurance

The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). 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 acceptable quality levels.

1.8 Prohibited - Utilization of Personal Electronic Devices

At NO time shall the contractor utilize a personal computer or any other personal electronic device to transmit or store Government information of any type such as; Soldiers PII/Medical Information, medical board reviews/results, drill schedules etc. Prior to utilizing a personal device the contractor shall coordinate with the SCARNG Directorate of Information Office to ensure DoD established security measures can be met. If a PII breach results from the contractor’s unauthorized utilization of a personal electronic device, the contractor shall bear all notification costs, call-center support costs, and credit monitoring service costs for all individuals whose PII has been compromised.

2. General Contractor Requirements

2.1 Air Force Privacy Act Program.

Contractor personnel may be exposed to data subject to the Privacy Act of 1974. The Contractor shall ensure all its personnel assigned to perform work under this PWS take appropriate action to prevent disclosure of this information and follow the guidance provided in AFI 33-332, Air Force Privacy and Civil Liberties Program, 12 January 2015.

2.2 Air Force Messaging

The contractor shall adhere to Air Force Manual (AFMAN) 33-152, User Responsibilities and Guidance for Information Systems, 1 June 2012

• Chapter 2, Information Systems and End User Devices (entire section)

• Section 6.2, Air Force Messaging, (entire section)

• Section 6.4, Electronic Message Format, (entire section)

2.3 Security Requirements

The contractor and all associated subcontractors’ employees shall comply with all applicable installation, facility, and area commander installation and facility access and local security policies and procedures, which may be obtained from the Contracting Officer’s Representative (COR). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the local installation’s Security Forces, Director of Emergency Services or local Security Office. The contractor shall ensure compliance with all personal identity verification requirements as directed by DoD, HAF and/or local policy. Should the Force Protection Condition (FPCON) change, the Government may require changes in contractor security matters or processes.

2.3.1 General Security. The contractor shall:

a. Comply with the Computer Security Act of 1987 and all DoD and Air Force requirements for access to Sensitive, but Unclassified Information and classified systems.

b. Comply with all administrative and security requirements to obtain a Common Access Card (CAC).

c. Obtain Non-secure Internet Protocol Routing Network (NIPRNet), if required by the COR.

d. Return of ALL badges (controlled/restricted area, local access, building, etc.) to include CAC (if necessary) and any other government property upon contract completion or when contract personnel no longer requires access to the installation (e.g. quits or the contract is terminated).

e. Coordinate with the site POC or sponsoring organization on all security issues and to gain access to the base and all areas necessary to execute this project.

f. Comply with established security procedures for entering an installation and its facilities, including special security procedures for entry to restricted or controlled areas. The government reserves the right to refuse entry to any individual at any work location. Any areas where work must be done or systems checked that are located within a secure environment, the site POC will ensure those areas are sanitized of any or potential classified information and contract personnel are escorted at all times.

g. Protect DoD information technology resources (e.g. installations, personnel, equipment, electronic media, documents, etc.) from damage, loss, theft or unauthorized physical access. The contractor shall ensure physical security is in accordance with DoDD 5200.28.

h. The contractor’s employees shall become familiar with and obey the regulations of the installation; including fire, traffic, safety and security regulations while on the installation. All contractor employees shall carry proper identification with them at all times.

2.3.2 COMSEC / IT Security. All communications with DoD organizations are subject to communications security (COMSEC) review. All telephone communications networks are continually subject to intercept by unfriendly intelligence organizations. DoD has authorized the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations. Therefore, the contractor is advised that any time contractor place or receive a call they are subject to COMSEC procedures. The contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with DoD information. The contractor shall abide by all Government regulations concerning the authorized use of the Government's computer network, including the restriction against using the network to recruit Government personnel or advertise job openings.

2.3.3 Use of Government Information Systems. Use of Government Information Systems (IS) and access to Government networks is a revocable privilege, not a right. Users are the foundation of the DoD strategy and their actions affect the most vulnerable portion of the Air Force’s and Air National Guard’s Enterprise Information (EI). Contractor employees shall have a favorable background investigation or hold a security clearance and access approvals commensurate with the level of information processed or available on the system. Contractor employees shall:

a. Comply with the command's Acceptable Use Policy (AUP) for Government owned IS and sign an AUP prior to or upon account activation.

b. Complete initial and/or annual Information Assurance (IA) training IAW AFPD 33-2.

c. Mark and safeguard files, output products, and storage media per classification level and disseminate them only to individuals authorized to receive them with a valid need to know.

d. Protect IS and IS peripherals located in their respective areas in accordance with physical security and data protection requirements.

e. Practice safe network and Internet operating principles and take no actions that threaten the integrity of the system or network.

2.3.4 Protection of Personally Identifiable Information (PII). The contractor shall protect all Personally Identifiable Information (PII) encountered in the performance of services in accordance with DFARS 224.103 and DoDD 5400.11, Department of Defense Privacy Program, and DoD 5400.11-R. If a PII breach results from the contractor’s violation of the aforementioned policies, the contractor shall bear all notification costs, call-center support costs, and credit monitoring service costs for all individuals who’s PII has been compromised.

2.3.5 Physical Security. Areas controlled by contractor employees shall comply with base Operations Plans/Instructions for Force Protection Conditions (FPCON) procedures, Random Anti-Terrorism Measures (RAMs) and local search/identification requirements. The contractor shall safeguard all government property including controlled forms provided for contractor use. At the close of each work period, Government facilities, equipment and materials shall be secured.

2.3.6 OPSEC Requirements/Plan. Non-Applicable. In accordance with AFI 10-701, Operations Security, the requirements of this PWS do not involve the contractor having potential access to critical information. Therefore, no OPSEC requirements/plan is required. However, OPSEC training will be required.

2.3.7 Visitor Group Security Agreement (VGSA). Not applicable

2.3.8 Classified Information. Not applicable.

2.3.9 Increased Force Protection Conditions (FPCONS). There could be impact on contractor performance during increased FPCON due to periods of increased threat. During FPCONs Charlie and Delta, services may be discontinued / postponed due to higher threat. Services will resume when FPCON level is reduced to level Bravo or lower.

2.3.10 Random Antiterrorism Measures Program (RAMP). Contractor personnel working on an installation are subject to participation in the installation RAMP Program (e.g. vehicles searches, wearing of ID badges, etc).

2.3.11 Personnel Security . The contractor shall provide properly cleared personnel for entry into all controlled areas included in the INWS project. The contractor is responsible for providing security briefings, and ensuring its employees comply with all Government and corporate security regulations.

2.3.11.1 The vendor shall submit the following forms (if required): Department of Defense (DD) Form 2875 for access to eMASS and DD Form 254 for Department of Defense Contract Security Classification Specification and Visitor Group Security Agreement for access.

2.3.11.2 Contractor personnel are required to wear or prominently display installation identification badges or contractor furnished contractor identification badges while visiting or performing work on any DoD installation. The vendor shall ensure employees comply with the safekeeping, wearing, and visibility of a contractor provided name badge with picture, as well as any government issued badges.

2.3.11.3 To meet the requirements of this PWS, the contractor shall obtain necessary badges or documents required for entry to restricted or controlled areas.

2.3.11.4 As necessary, the contractor shall coordinate with the base POC to obtain and return temporary badges and vehicle registrations.

2.3.11.5 All contractor personnel shall comply with established security procedures for entering an installation and its facilities, including special security procedures for entry to restricted or controlled areas.

2.3.11.6 For all contractor and subcontractor personnel, the prime contractor shall provide the full name, Title, E-Mail address, phone number and fax number of the Company Official who may be contacted to certify security clearance information.

2.3.11.7 All contractor personnel having access to information systems for the purpose of installation or configuration will have at least a Secret clearance before doing any work under this PWS.

2.3.11.7.1 The contractor shall provide the necessary security clearance information to the site POC no later than two weeks prior to installation commencement for contractor personnel being granted access to any work locations

2.3.11.8 The contractor will comply with DOD Standard 22 – Level 1 AT Awareness training and associated tasking IAW AFI 10-245, Antiterrorism.

2.3.11.9 The Contractor shall ensure the return of all badges, and any other Government property, upon task completion, or when personnel depart a task.

2.3.11.10 The Government reserves the right to refuse entry to any individual at any work location.

2.4 CAC Requirements.

The Common Access Card (CAC) is the Department of Defense’s (DoD) Federal Personal Identity Verification (PIV) credential. The issuance of a CAC will be based on four criteria; (a) eligibility for a CAC and (b) verification of DoD affiliation from an authoritative data source IAW DoDM 1000.13, V1, DoD Identification (ID) Cards: ID Card Life Cycle, January 2014; (c) completion of background vetting requirements according to the Federal Information Processing Standards Publication 201-2, Personal Identity Verification (PIV) of Federal Employees and Contractors, August 2013, and DoD 5200.2-R, Department of Defense Personnel Security Program, January 1987; and (d) verification of a claimed identity. CAC eligible personnel must be registered in the Defense Enrollment Eligibility Reporting System (DEERS) through either an authoritative personnel data feed from the appropriate Service or Agency or Trusted Associate Sponsorship System (TASS).

2.4.1 HSPD-12 Background Investigation Requirements. The contractor will ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel assigned to work on the Government site and/or requiring access to a DoD network. In accordance with DoDI 5200.46, DoD Investigative and Adjudicative Guidance for Issuing the Common Access Card (CAC), September 2014, a favorably adjudicated National Agency Check with Inquiries (NACI) or equivalent in accordance with revised Federal Investigative Standards is the minimum investigation required for a final credentialing determination for a CAC. The contractor shall make all reasonable efforts to ensure that contractor employees meet CAC eligibility standards upon assignment to the contract and shall be held responsible for delays, failure to meet performance requirements or decreases in efficiency in accordance with the applicable inspection clause.

2.4.2 Trusted Associate Sponsorship System (TASS). The contractor is responsible for processing applications for Common Access Cards (CAC) for every contractor employee who deploys with the military force OR who has need to access any government computer network in accordance with FAR 52.204-9, "Personal Identity Verification of Contractor Personnel."

2.4.3 CAC Requests. The contractor is responsible for managing requests for new or renewal CAC cards in sufficient time to ensure that all contractor employees have them when needed to perform work under this contract. The norm is at least ten calendar days advance notice to the Trusted Agent (TA), unless there are extenuating circumstances approved by the Contracting Officer's Representative (COR) or Contracting Officer.

2.4.3.1 It is recommend that a "Corporate Facility Security Officer" (FSO) be designated to serve as your firm's single point of contact for Background Investigation (BI), and other CAC and security related matters. If a FSO is not established, each contractor employee requiring a CAC will be required to process their own applications.

2.4.3.2 CAC applications shall be processed through the COR.

2.4.3.3 The government will establish a process for CAC applications and will manage the applications through the COR.

2.4.3.4 The FSO or contractor employee will submit completed applications to the COR and will follow up to ensure that the TA is processing the request. A CAC cannot be issued without evidence that the FSO has initiated a National Agency Check with Written Inquires (NACI) or a personnel security investigation (PSI) equal to or greater in scope than a NACI.

2.4.3.5 The government will inform the contractor's applicant, via email, of one of the following:

a. Approved.* Upon approval, the information is transferred to the Defense Enrollment Eligibility Reporting System (DEERS) database and an email notification is sent to the contractor with instructions on obtaining their CAC. The contractor proceeds to a Real-Time Automated Personnel Identification System (RAPIDS) station (RAPIDS Site Locator: http://www.dmdc.osd.mil/rsl/).

b. Rejected.* The Government, in separate correspondence, will provide reason(s) for rejection.

c. Returned. Additional information or correction to the application required by the contractor employee.

2.4.3.6 The contractor shall maintain records of all approved and rejected applications.

2.4.3.7 At the RAPIDS station, the RAPIDS Verification Officer will verify the contractor by SSN and two forms of identification. Identity source Documents must come from the list of acceptable documents included in Form I-9, OMB No. 115-0136, "Employment Eligibility Verification." Consistent with applicable law, at least one document from the Form I-9 list shall be a valid (unexpired) State or Federal Government-issued picture identification (ID). The Identity documents will be inspected for authenticity and scanned and stored in the DEERS upon issuance of an ID. The photo ID requirement cannot be waived, consistent with applicable statutory requirements. The Verification Officer will capture primary and alternate fingerprints, picture, and updates to DEERS and will then issue a CAC.

2.4.3.8 Issued CACs shall be issued for the period of performance (current contract year), not the contract end date (inclusive of any options). CACs are validated by the acceptance and issuance of the new Option Year.

2.4.3.9 The contractor shall return issued CAC's to the TA, COR or DEERS office upon departure or dismissal of each contractor employee. Obtain a receipt for each card and provide to the TA/COR if returned to a DEERS office.

2.5 Training Requirements

2.5.1 AF MyLearning. All contractor employees and associated sub-contractor employees assigned to work on a government site and/or requiring access to a DoD network will be required to register with MyLearning at commencement of services in order to complete the necessary training required of them initially and annually for the duration of the contract (i.e., DoD CyberAwareness Challenge).

2.5.1.1 Antiterrorism (AT) Level 1 Awareness Training. All contractor employees, to include subcontractor employees, requiring access to Government Installations, Facilities and Controlled Access areas shall complete AT Level I awareness training within 10 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall attend training sponsored by the COR and provided by the government.

2.5.1.2 Information Assurance (IA) / Information Technology (IT) Training and/or Certification. All contractor employees and associated sub-contractor employees shall complete the DoD CyberAwareness Challenge before issuance of network access and annually thereafter. All contractor employees performing services involving IA/IT functions shall comply with DoD and Air Force training requirements in DoDD 8570.01, DoD 8570.01-M and AFPD 33-2 within 30 days of the start of contract performance. In accordance with DoD 8570.01-M , DFARS 252.239.7001 and AFM 33-282, contractor employees performing services supporting IA/IT functions shall be appropriately certified upon contract award.

The baseline certification as stipulated in DoD 8570.01-M shall be completed upon contract award.

2.5.2 OPSEC Training. In accordance with AFI 10-701, Operations Security, OPSEC PMs/SMO/SMNCOs/Coordinators for the Communications Squadron/Flight will provide OPSEC brief to contract employees upon arrival prior to commencement of work. General organizational orientations may need to be supplemented by duty-related orientations in the work center targeted toward specific critical information and vulnerabilities associated with the work.

2.5.3 iWATCH Training (See Something, Say Something). The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees' commencing performance, with the results reported to the COR no later than 30 calendar days after contract award.

2.6 Identification of Contractor Employees.

All contractor personnel attending meetings, answering Government telephones and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression that they are Government employees. The contractor shall ensure that all documents or reports produced by contractor personnel are suitably marked as contractor products or that contractor participation is appropriately disclosed.

The contractor’s status as a “contractor” shall be predominantly displayed in all correspondence types (to include signature blocks on e-mail) and dealings with Government or non-Government entities/ Contractor personnel shall wear identification badges distinguishing themselves as such. The badges shall have the company name, employee name and the word “contractor” displayed. The contractor shall retrieve all identification media (including vehicle passes) from their employees who depart employment for any reason. All identification media (i.e., badges and vehicles passes) shall be returned to the KO within 14 calendar days of an employee’s departure.

2.7 Combating Trafficking in Persons.

The United States Government has adopted a zero tolerance policy regarding trafficking in persons. Contractors and contractor employees shall not engage in severe forms of trafficking in persons during the period of performance of the contract; procure commercial sex acts during the period of performance of the contract; or use forced labor in the performance of the contract. The Contractor shall notify its employees of the United States Government’s zero tolerance policy, the actions that will be taken against employees for violations of this policy. Such actions may include, but are not limited to, removal from the contract, reduction in benefits, or termination of employment. The Contractor shall take appropriate action, up to and including termination, against employees or subcontractors that violate the US Government policy as described at FAR 22.17.

2.8 Data Rights.

The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the KO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

2.9 Organizational Conflicts of Interest (OCI).

The contractor and subcontractor personnel performing services under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCIs, as defined in FAR Subpart 9.5. The contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may affect other remedies as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2.10 Contract Administration

2.10.1 Contract Manager (CM). The contractor shall designate a CM who shall ensure performance under this contract.

The name of this person, and an alternate who shall act for the contractor when the CM is absent, shall be designated in writing to the KO. The CM or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The CM shall work through the COR, (or the KO if a COR is not assigned), to resolve issues, receive technical instructions, and ensure adequate performance of services. The CM shall ensure that contractor employees do not perform any services outside the scope of the contract without an official modification issued by the KO. The CM shall ensure contractor employees understand that services performed outside the scope of the contract are performed wholly at the expense of the contractor.

2.10.2 Post Award Conference / Periodic Progress Meetings. The contractor agrees to attend any post award conference convened by the KO in accordance with Federal Acquisition Regulations Subpart 42.5. The KO, Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contactor’s performance. At these meetings, the Contacting Officer will apprise the contractor of how the Government views the contractor’s performance and the contractor shall apprise the Government of problems, if any, being experienced. The contractor shall resolve outstanding issues raised by the Government. Contractor attendance at these meetings shall be at no additional cost to the Government.

2.10.3 Contractor Manpower Reporting Application (CMRA) The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the National Guard Bureau via a secure data collection site.

2.10.3.1 eCMRA reporting not applicable.

2.10.4 Contractor Travel and Mobilization. Contractor travel and mobilization will be included in their proposal and will be part of the firm fixed price contract.

2.11 Non-Disclosure Agreement

Non-Disclosure: Contractor personnel will be exposed to information covered under the Privacy Act of 1974, and will comply with all applicable safeguarding and handling requirements associated with Privacy Act information. During the performance of this tasking, Contractor personnel may be required to access or come into contact with proprietary Government information, including financial account records or source selection information. Contractor personnel will sign a non-disclosure agreement if this situation occurs and will not use such information for any purpose other than the performance of this order.

2.12 Cyber Security and Systems Security

2.12.1 In accordance with DoD 5200.1-R and AFI 31-401, the contractor will comply with AFI 33-200, Cybersecurity Program Management; AFI 33-210, Air Force Certification and Accreditation Program (AFCAP),; AFMAN 33-282, Computer Security (COMPUSEC); AFMAN 33-285, Cybersecurity Workforce Improvement Program; AFSSI 7702, Emission Security (EMSEC); AFI 10-701, Operations Security (OPSEC); and all applicable AFKAGs, AFIs and AFSSIs for Communications Security (COMSEC).

2.12.2 AFMAN 33-285, Figure 3.1, page 28, provides the following mandatory contract language:

DFARS Mandatory Contract Language. 252.239-7001 Information Assurance Contractor Training and Certification. As prescribed in 239.7103(b), use the following clause: Certification and Accreditation (C&A) and Risk Management Framework: (NIST SPs) in accordance with the governing guidance of SP 800-37 Guide for Applying the Risk

Management Framework to Federal Information Systems, DoD 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), DoD 8500.01 Cybersecurity, Security Categorization and Control Selection for National Security Systems (CNSSI No. 1253), & AFI 33-210 Air Force Certification and Accreditation (C&A) Program (AFCAP).

The contractor shall also provide all required documentation for the C&A package, which includes but not limited to:

System Security Plan (SSP), Testing, Scans (ACAS), STIG's, Configuration Management Plan, Disaster Recovery Plan, Hardware/Software lists, and Topology.

3. Specific Contract Requirements

3.1 Post Award Meetings/Reports. The vendor will participate in the following post award meetings:

3.1.1 Kick-Off Meeting. The contractor shall host a kick-off meeting with Base POC’s within 15 calendar days of contract award, at a location of the Contracting Officer’s choosing to meet key personnel and discuss pertinent issues. The kick-off meeting shall cover the following topics:

• Introductions

• Communications Management

• Sub-contractor Management

• Business Partner Arrangements

• Contract Issues or Concerns

• Deliverables

• Project/Installation Approach

• Projected Master Project Schedule

• Site Surveys

• Design

• Payment Milestones/Procedures

• Questions

3.1.1.2 Contractor shall provide meeting minutes to the Base project manager within 3 calendar days after kick-off meeting.

3.1.2 Monthly Project Management Review (PMR). The contractor shall coordinate/host a monthly PMR NLT the 15th of each month, or at any date agreed upon with the COR, with dial in capability to support at least 20 remote attendees.

3.1.2.1 Contractor shall provide Monthly PMR Minutes within 3 calendar days of the PMR.

3.1.3 Bi-Weekly Project Status Meeting. The contractor shall coordinate/host a Bi-Weekly Project Meeting with dial in capability to support at least 20 remote attendees.

3.1.3.1 Contractor shall provide Bi-Weekly Project Meeting Minutes.

3.1.4 The contractor shall provide a Bi-Weekly Activity Report (WAR) NLT 1600 on the day prior to the Bi-Weekly Project Status Meeting.

3.2 Project Deliverables

3.2.1 Risk Management Plan

3.2.2 Communications Management Plan

3.2.3 Installation Plan

3.2.4 Acceptance Test Plan

3.2.5 Master Project Schedule

3.2.6 Training Plan

3.2.8 Site Survey

3.2.9 Project Support Agreements

3.2.10 Design Documentation

3.2.11 Quality Control Plan

3.2.12 Installation As-Built Documentation

3.2.12.1 Within (20) business days of completion of installation at a location, the contractor shall update the existing Installation Plan and provide updated System Installation Records (CSIR) as well as a signed AFTO Form 747.

Requirements for the Installation Phase will be considered met upon delivery and acceptance of applicable CSIR, As-Built drawings, and warranties.

3.2.13 System Acceptance/Commissioning Documentation

3.3 Project Recurring Deliverables

3.3.1 Project Management Review Report

3.3.3 Bi-weekly Activity Report

3.3.4 Bi-Weekly Project Status Meeting minutes

3.4 Qualifications of Suppliers and Contractors

System Designers, Integrators and Contractors Special Qualifications. The contractor shall use system designers, integrators and contractors that are able to demonstrate a full knowledge and understanding of systems used for mass notification. Vendors will use industry certified and factory-trained personnel to perform system design, integration, installation, testing, training, and maintenance.

3.4.1 Certified Personnel. The contractor shall use qualified personel IAW this PWS and UFC 4-021-01, Design and O&M: Mass Notification Systems, dated 9 April 2008 Change 1, January 2010.

3.4.2 Designer Qualifications.

3.4.2.1 Communications-Electronics Infrastructure. Active BICSI Registered Communications Distribution Design (RCDD) credentialed persons will be treated as fully qualified in the communications-electronics engineering discipline.

Contractor will provide the full name and RCDD Credential registration number to the government in order to verify BICSI credentials. Verification will be accomplished using BICSI certification query at https://www.bicsi.org/forms/Verify/CredentialHolder. All designs will include the BICSI RCDD certifiers stamp and BICSI RCDD credential registration number.

3.4.2.2 Wide Area Mass Notification System. The wide area MNS shall be designed under the supervision of a registered professional engineer with a minimum of 4 years’ current work experience in fire protection, electrical, and communication-electronics engineering areas specific to wide area MNS. Shall possess a minimum of 4 years’ current work experience specific to wide area MNS communications-electronics. Alternately, the wide area MNS may be designed by an engineering technologist that possesses a minimum of 10 years’ documented current work experience specific to wide area MNS communications-electronics. The individual’s name, signature, and professional engineer number or NICET certification number (when applicable) shall be included on all final design documents.

Note: The MNS designer should have demonstrated expertise in audio system design, sound pressure and intelligibility measurement and evaluation, radio communications systems, audible and visual notification appliances, and central control station designs.

3.4.2.2.1 Speaker Array Supporting Structure. The speaker array supporting structure shall be designed by a registered professional structural engineer to resist all environmental loads, including site-specific wind and seismic forces. The individual’s name, signature, and professional engineer number or NICET certification number (when applicable) shall be included on all final design documents. Verification will be accomplished using NICET certification query at https://candidate.nicet.org/Certification/CertificationDirectorySearch.aspx .

3.4.2.3 Individual Building Mass Notification System. The individual building MNS shall be designed under the supervision of a registered professional engineer with a minimum of 4 years of current work experience in fire protection, electrical, and communication-electronics engineering areas specific to individual building MNS. Alternately, the individual building MNS may be designed by an engineering technologist verified by NICET as certified at Level IV in low voltage electronic-communications systems or at Level IV in fire alarm systems, plus this engineering echnologist shall possess a minimum of 4 years current work experience specific to individual building MNS communications-electronics. Alternately, the individual building MNS may be designed by an engineering technologist that possesses a minimum of 10 years of documented current work experience specific to individual building MNS communications-electronics. The individual’s name, signature, and professional engineer number or NICET certification number (when applicable) shall be included on all final design documents.

3.4.3 Installer Qualifications.

3.4.3.1 Communications-Electronics Infrastructure. BICSI Installer Level 1 credentialed personnel will be considered as fully qualified installers for purposes of this effort. On site supervision of installer work by a BICSI Installer Level 2 or BICSI Technician work leader will be acceptable in lieu of Installer Level 1 workers.

3.4.3.2 Wide Area Mass Notification System. Use system integrators and contractors that can demonstrate a full knowledge and understanding of systems used for mass notification, and that have factory-trained personnel to perform system installation, testing, training, and maintenance.

3.4.3.3 Individual Building Mass Notification System. Use system integrators and contractors that can demonstrate a full knowledge and understanding of systems used for mass notification, and that have factory-trained personnel to perform system installation, testing, training, and maintenance.

3.4.3.4The contractor shall use manufacturer-certified technicians to accomplish all contracted infrastructure installation and set-up work. This shall include installation, programming, and testing phases of the upgrade/install.

3.4.3.5 BICSI Installer Level 1 credentialed personnel will be considered as fully qualified installers for purposes of this effort.

3.4.3.6 On site supervision of installer work by a BICSI Installer Level 2 or BICSI Technician work leader will be acceptable in lieu of Installer Level 1 workers.

3.4.3.7 MNS Component Products and Manufacturers Qualifications. Only accept products from manufacturers that can meet the design criteria of this UFC and can demonstrate 5 years of experience in producing products similar to those required for mass notification. Utilize products of current manufacture with replacement parts and components available for a minimum of 10 years.

3.4.4 INFORMATION ASSURANCE CONTRACTOR TRAINING AND CERTIFICATION (JAN 2008) (a) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program.

3.4.4.1 The Contractor shall meet the applicable information assurance certification requirements, including:

3.4.4.1.1 DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M

3.4.4.1.2 Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

3.4.4.1.3 Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

3.4.4.1.4 Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

3.5 Site Survey Requirements

Site survey methodologies shall be consistent with applicable industry standards and regulations to yield necessary details for documentation of general site layout, floor plans of all affected buildings, proposed component installation locations with configurations, and relevant site preparation issues. Site surveys will be used to collect information necessary to accomplish design, engineering, and installation planning.

3.5.1 General Site Survey Requirements. The contractor shall perform site surveys at each location, to include:

• Obtain General Site Layout, along with any drawings and floor plans

• Obtain any Telecom Equipment Room drawings including Equipment Rack Floor Position Indicators (FPI), rack elevations (to identify existing equipment and available space) and wall boards used to mount communications or alarm equipment

• Take pictures of all work areas for later reference (may need local authorization)

• Obtain any required distances for conduit, cable, etc.

• Obtain a complete list of areas requiring intrinsic devices.

• Obtain/create drawings of all proposed component installation locations

• Assess any site preparation issues/concerns; obtain contacts and base address information

• Obtain a complete list of all buildings along with identified use and occupancy rates

• Determine if space, power, HVAC, UPS, etc.