Bldg 200 Vindicator Device Installation - PWS dated 06 Sep 24.pdf

Performance Work Statement Bldg. 200 Vindicator System 509th OSS Whiteman AFB

06 September 2024

1. SCOPE/General Description Installation/testing of six cameras at main entry/exit points on the exterior and interior of building 200. Which will offload video feed to CCTV system located in M205 building 38.

Recording will be tested to ensure proper capture of video traffic to existing CCTV system DVR recorder.

Installation of V5 motion detector components:

• Site Commander (qty. 2)

• Single Alarm Contact Either Closed or Open Loop, With Tamper Circuit, Closed Loop

(qty. 13)

• Request to Exit (qty. 4)

• RDR, RPK40-H, PIVCLASS, SE E, LF STD, HF STD/SIO/SEOS/FIPS/C (qty. 14)

• U.L. Listed Multi-Output Power Supply/Charger with Enclosure- 24VDC @ 10 amp, 115VAC input, AC, and b (qty. 6)

• 18-8C STR BC FRPVC FRPVC JKT WHT CMP/FPLP 75C 1000' REEL (qty. 2000)

• 18/4c SOL LOWCAP CM/CL3/FPL 500' 87180450C (qty. 5000)

• WIRE BOXES RESISTERS (qty. 8)

• DS9370 Motion Detector, Ceiling Mount, High Perf TriTech PIR/Microwave, 70 ft 360 coverage (qty. 65)

• Power Supply / Charger- 12VDC @ 10 Amp Board with zero voltage drop on battery switchover. UL Recogn (qty. 6)

• ALTNX PWR DIST UNT CNVRTS 1-8 (qty. 12)

• Demo Wire and Cable (qty.1)

• CAT 6 Network Cable (qty. 1600 Feet)

• Illustra Pro Gen4 4MP MiniDome, 2.7-13.5mm, Indoor/Outdoor, IP67, IK10, TDN w/IR

(Camera Total 6)

Installed with support cabling within main secure work area of building 200, programmed and configured to offload message traffic from current bldg. 200 V5 to building 38 vindicator servers. All installed request to exit devices directly communicate with the Bldg. 200 V5 and offload to building 38 vindicator system. System programming includes alert response and proxy programming from building 38.

During this project all Type I HSS devices will be replaced with Type II HSS devices at current Type I installed locations.

Installation of site commanders at the following locations:

- Rm. 124 first floor of building 200

- Inside secure work area facing out, attached to the left wall near override switch

Following installation both will communicate with 200 basement V5 and Bldg. 38.

2. Non-Personal Services The government shall neither supervise contractor employees nor control the method by which they perform the required tasks. Contractor personnel will be escorted into the required areas to complete the work. The contractor will coordinate any requirements with security personnel in Bldg. 200, 509 OSS security section.

3. Requirements Proposed Tasks for Camera installation Provide installation of the CCTV cameras at the locations designated in the contract and provide the ability to monitor each camera around the facility while communicating with the CCTV system to record events within building 38.

Installation of the V5 in Rm 5 to communicate with existing vindicator infrastructure ensuring message traffic is evenly distributed preventing future system lockups. With any programming that will be required to allow the V5 to communicate with the existing system and peripherals.

4. Security and Safety Contractor shall wear appropriate security badges, line badges, identification and/or name tag as required by the security procedures of the squadron where performance takes place. Contractor personnel shall meet established unescorted installation entry requirements pursuant to AFI 31- 101 before base identification will be issued. Contractors shall submit requests for installation identification to 509 OSS security personnel. Personnel not meeting the minimal standards will not be issued an installation pass and will not be allowed access to the installation. The contractor will provide employee information for an entry authorization listing to gain entry onto the base strictly for the time-period of the work to be accomplished. The information that needs to be provided will be Full Name, Social Security Number, Date of Birth, Driver’s License Number, State, .and citizenship.

5. Period of Performance Contractor shall perform installation on the system during regular working hours (0730-1600) only on weekdays excluding Federal Holidays or Whiteman AFB down days without prior coordination. If events like weather or Air Force exercises prevent compliance with that timeline personnel in Bldg. 200 will be contacted as soon as possible. All work will be conducted in Bldg.

200 and Bldg. 38, 509 OSS. Date and time will be set up between the contractor and security personnel in Bldgs. 38 and 200.

6. Operational Security Purpose: The following information provides Operations Security (OPSEC) guidance to Government Contractors and subcontractors awarded Government contracts at Whiteman AFB.

Government Contractors are provided this guidance to ensure compliance and protection of critical information that may be a threat to national security. All OPSEC briefs and updates will be conducted by 509 OSS security personnel after arrival at 509 OSS and before performing necessary duties.

Definition: OPSEC is a methodical process to identify Critical Information (CI), identify threats to that CI and the related vulnerabilities and risks of exploitation to that CI, and identify, develop, and implement countermeasures to protect that CI. CI is specific facts about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively to guarantee failure or unacceptable consequences for friendly mission accomplishment. CI includes those facts, which individually, or in the aggregate, reveal sensitive details about US Government, i.e., Whiteman AFB or the contractor’s security or operations related to the support or performance of the Statement of Work (SOW)/Performance Work Statement (PWS), and thus require a level of protection from adversarial collection or exploitation not normally afforded to unclassified information. OPSEC supplements but does not replace traditional security practices such as Physical Security and Information Security. OPSEC is essential to ensure the initial and continued success of our mission, operations, systems, and procedures.

OPSEC Applicability: The 509 OSS OPSEC Program Manager has determined that additional safeguards are essential for this contract and imposes OPSEC as a requirement in the responsibilities of this contract. During this contract, in addition to those restrictions, instructions and guidelines defined in the contract Statement of Work and/or other references provided the contractor will adhere to the following minimum requirements in support of the 509 OSS OPSEC Program. Introduction of personnel electronic devices into government spaces, laptops, tablet PCs, cellular phones, cameras, recording devices, and data recording/storage devices is STRICTLY controlled and forbidden in some areas of Whiteman AFB. Photography and recording are not allowed except for official use and by permit only. (Unless otherwise stipulated in the contract). Contractor personnel shall not discuss government operations in public or over unprotected or unencrypted communications. Official business controlled unclassified information may only be transmitted as directed in the SOW/PWS. The Contractor shall not post to company websites, publications, newsletters, or other media any images, data or information that reveal sensitive government operations, personnel, equipment, and/or classified or controlled unclassified information, refer to paragraph (d) below. When in doubt, company press releases related to this contract should be coordinated through the 509th Contracting Office. Because observation of events, operations, physical changes, etc. may reveal National Security information, specific restrictions are needed to preclude unintentional release of this information to unauthorized parties. (Unauthorized disclosure and transfer of National Security Information is punishable under 18 USC § 793.) Therefore, contractor personnel shall not disclose to unauthorized third parties, post to unofficial sites (including Social Networking sites) any images, data, or information, or observed events that reveal sensitive government operations, personnel, or equipment. Government issued badges, identification shall be removed and/or concealed from plain sight when off station and shall not be left in vehicles or unprotected.

Badges and passes may not be duplicated or copied or loaned to others. Lost or stolen identification badges, vehicle passes etc. will be immediately reported to the 509th Security Forces LE Desk at (660) 687-3700. Practice OPSEC and implement countermeasures to protect CI and other sensitive unclassified information and execution of military operations performed or supported by the contractor in support of the mission. Protection of CI will include the adherence to and execution of countermeasures which has been provided by the 509 OSS. It is strongly recommended the contractor mark and protect related internal production schedules, deliverables, inventories, and shortages and identified vulnerabilities related to production of government material. Internal company markings e.g., Business Sensitive, etc., are appropriate for identifying the aforementioned as sensitive information. Specific Government-provided information, drawings etc., will be protected in accordance with guidance in applicable paragraphs of the SOW. Destroy (burn, shred, etc.) critical and/or sensitive unclassified information no longer needed to prevent the inadvertent disclosure and/or reconstruction of this material. Critical information identified by 509 OSS will be marked and handled appropriately as FOR OFFICIAL USE ONLY (FOUO). Government CI includes but is not limited to known or probable vulnerabilities to any U.S. system and their direct support systems, details of information about military operations, unit, vessel, aircraft movements/arrivals, missions, and exercises, etc.