3-CRA SOW FY-23_ver7 (04.28.23).pdf

Camera and Single Mode Fiber Design and Installation Statement of Work

Bureau of Prison Inside/Outside Plant Site Survey

1. BACKGROUND

The Bureau of Prisons (FBOP) is looking for a contractor to supply and install digital cameras (Attachment B). To include cameras, wiring, conduit, camera licenses. Along with the supply/install of Qognify recording and Video Management System (VMS) systems at specified locations. This contract will assist the Facilities throughout the Federal Bureau of Prisons (FBOP). Along with the supply and installation of Single Mode Fiber (SMF) at sites that are listed on attached (Attachment A). Site survey methodologies shall be consistent with industry standards and yield adequate details for documentation of general site layout, floor plans of the demarcation site (DMARC) as well as associated equipment rooms, 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. The contractor shall visit the site and conduct a survey at each specified location based on its mission, buildings, interior rooms, and outdoor area layout.

The contractor shall include a review of the preliminary list of included buildings. Site surveys will be coordinated with local Plans and Programs Offices BOP Contracting Officer's Representative/Contracting Officer's Technical Representative (COR/COTR) the Telecommunication Technician and local Computer Services Manager (CSM). The review will include any required dependencies or considerations that need to be observed in a future implementation.

2. GENERAL TERMS AND CONDITIONS

The government will award an Indefinite-Delivery requirements Firm-Fixed Price Contract.

Task/Delivery Order shall be issued to fund the Base and Option Period.

The government reserves the right to modify its priorities and rearrange the sequencing of the various agreed upon tasks.

The Contractor is not responsible for unforeseen changes or problems or changes in the government design needs and goals.

3. GENERAL REQUIREMENTS

3.1 PROJECT MANAGEMENT

3.1.1 The Contractor shall provide monthly status reports detailing the work accomplished and the work to be accomplished to the Contracting Officer (CO), the Project Manager and COR.

These reports shall be in writing and provided by no later than the 15th day of each month. Each report shall detail the status of the project and include, at a minimum, the current status of the requirement, and a detailed statement of all problems encountered or anticipated. The Contractor shall also forward a copy of all correspondence initiated by the Contractor to the Contracting Officer.

3.1.2 Additionally, the Contractor shall maintain frequent communications with the Project Manager and COR to conduct work in progress reviews. The work in progress reviews consist of monthly status meetings and workgroup meetings where knowledge transfer can occur.

3.1.3 Contractor will be responsible for contacting the COR and/or each site prior to the site surveys to get approval to take pictures during the survey. The decision is on each location for approval/denial of the use of cameras.

4. SPECIFIC REQUIREMENTS FOR CAMERA SUPPLY

4.1 The Contractor shall supply materials required to install IP Camera’s throughout the facilities from Fisheye, Fixed, IR, PTZ cameras, cabling, conduit, wiring, and switches. The Contractor will ship all equipment and materials to the sites when requested by the COR. This will be a firm fixed contract NTE the agreed upon amount. All cameras must be on the approved FITARA list and/or approved prior to purchase of equipment. Cameras will also be purchased with this contract and are required to have at least the minimum requirements listed below.

4.2 All Camera Horizontal drops will not exceed the 100m length and current horizontal camera drops can be utilized as long as the home end is at the current switch location. Camera system will not be taken down for long periods of time. Cameras will be replaced one at a time as not to take down all CCTV coverage in an area at a time and no camera will be down longer then needed.

4.3 Contractor will supply and install all materials to make horizontal drops and cameras operational (conduit, Cat6E cabling, patch panels and terminated ends).

4.4 Coordinate with National Network Communications (NNC) branch of the FBOP to coordinate switch port requirements for each switch location. No camera will be added to the BOPNet without prior approval from NNC and every Port will be programmed by FBOP staff.

4.5 Remaining contractor installed cameras not in the solicitation will be supplied by the government.

4.6 CAMERA GENERAL REQUIREMENTS

• ONVIF Compliant:

• 10/100BASE-TX, RJ45 Connector, CAT6 Cabling

• H.264/H.265

• Normal Network Supported Protocols

• Constant bit rate (CBR) constrained variable bit rate (CVBR) with configurable maximum value.

• 1280 x 960 (1 MP) minimum frame rate.

• 4K Max frame rate

• IPv4/IPv6 Compliant

• Support secure protocols for remote management such as HTTPS and SSHv2

• SNMPv3 compliant

• Support Power over Ethernet (PoE) IEEE 802.3at, IEEE 802.3af, UPOE, or UPOE+ depending on the model of camera.

4.7 PARTIAL LIST OF APPROVED FITARA EQUIPMENT:

• Avigilon H5 Series

• Axis P3225-LV

• Bosch Flexidome IP 7000 series

• Pelco Sarix pro 4 Series

• Vicon Alliance MX series

• OnCam 360 camera

• Qognify Recorder

• Qognify Decoder

4.8 QOGNIFY EQUIPMENT IS REQUIREMENT, below is a list of some of the used items.

All Equipment must be installed by a Certified and Authorized Qognify dealer.

• Nice Vision Decoder 5204 NV-NVD-5204

• QVMS Channel License QVM-A-INF-1C

• Management 236 server - AMS QFY-MNGT-20S-RP-S

• Enterprise SMA redundante lísense QVM-A-INF-1C-SMA-E1

• 12 bay 64TB, Ser 19 2U rackmount – Recorder QHW-CTY12-64T-8-S-R6

• 12 bay 80TB, Ser 19 2U rackmount – Recorder QHW-CTY12-80T-8-S-R6

4.9 ADDITIONAL EQUIPMENT MINIMUM REQUIREMENTS:

• 1 1/2” – 2” EMT Conduit, hangers, and boxes as a minimum

• Cat6E cabling

4.10 Uninterruptable power supplies (UPS) are not part of this solicitation.

4.11 No HVAC modifications are part of this solicitation.

4.12 Bennettsville Qognify System (CLIN #21):

Model Description Qty QVM-A-INFCP Core Server Package 1 QVM-A-INF-1C QVMS Channel License / Redundancy 223

QFY-MNGT-2OS-RP-

S2-MR

Management 236 server, Dual OS, Redundant Pwr, Ser19

QHW-CTY12-96T-12-

S2-R6

2U rackmount, 96TB, Dual Xeon Silver 4309Y Processor, Dual OS SSD, 32GB Mem, RAID6, Quad NIC, Windows Ser22, KB/Mouse, 5 yr NBD Onsite warranty

4.13 Alderson Qognify System (CLIN #22)

Model Description Qty QVM-A-INFCP Core Server Package 1 QVM-A-INF-1C QVMS Channel License / Redundancy 14

QFY-MNGT-2OS-RP-

S2-MR

Management 236 server, Dual OS, Redundant Pwr, Ser19

QHW-CTY12-64T-8-

S-R6

2U rackmount, 64TB, Dual Xeon Silver 4309Y Processor, Dual OS SSD, 32GB Mem, RAID6, Quad NIC, Windows Ser22, KB/Mouse, 5 yr NBD Onsite warranty

5. SPECIFIC REQUIREMENTS FOR FIBER DESIGN AND INSTALLATION

5.1 FIBER SITE SURVEYS

In performing site surveys at each BOP location, the contractor shall:

5.1.1 Review existing topology and verify all BOP provided data.

5.1.2 Capture a topology that identifies the number and location of Information Transfer Node (ITNs) and End Building Node (EBNs) and the connectivity.

5.1.3 Locate any know environmentally sensitive and hazardous material issues that could affect systems installation and operation, as identified by the BOP facilities department. Should the presence of asbestos-containing materials (ACM) or lead based paint (LBP) materials be confirmed, the implementation of hazardous material removal protocols should be initiated.

5.1.4 Locate all existing reusable network equipment, as identified by BOP facilities department.

5.1.5 Utilize Federal Bureau of Prisons (FBOP) materials ……approx. 70% FBOP Supplied - 30% Contractor Supplied. FBOP has 24-48-72 strand Fiber, some racks and LC cassettes may be provided along with larger conduit 3-4" rigid or PVC.

5.1.6 Capture digital images of a sample of existing equipment (manholes, hand holes, communication closets, EBN, ITNs) for use during the collaborative reviews.

5.1.7 Interview BOP Communications personnel that support the location for additional needs.

5.1.8 Participate in a pre-survey meeting with survey team prior to survey start.

5.1.9 Survey and design documentation reviews will be completed and government approval to proceed shall be obtained prior to material acquisition and installation.

5.1.10 Contractor will be responsible for inventorying and shipping of materials located at 6 FBOP sites around the country.

5.1.11 The contractor shall be responsible for providing logistics support to move materials from FBOP Warehouses to the appropriate work sites.

5.1.12 Cad drawings may be provided by location if available after the award of the contract.

They may be in DWG or PDF format but not all locations have useable drawings.

5.2 INSIDE SITE SURVEY (ISS)

A site survey of the inside cable plant will be completed at identified locations. At a minimum, the contractor shall accomplish the following:

5.2.1 Survey each building, each equipment room, and identify switch locations.

5.2.2 Identify locations requiring firestop material as it pertains to new fiber path design.

Document where existing firestop deficient risers or horizontal penetrations require government correction and new penetrations to be included in the scope of the ISP ITS installation.

5.3 OUTSIDE SITE SURVEY (OSS)

The contractor shall:

5.3.1 Survey communications between buildings, including all ways of data transfer (i.e., underground pathways and ducts, manholes, hand holes, wireless links).

5.3.2 As identified by BOP facilities, assess confirmed use of existing fiber optic cables to be reused in lieu of new installation, not to disturb existing available network infrastructure.

5.4 INSIDE/OUTSIDE PLANT DESIGN

After site surveys are completed, the contractor shall create detailed fiber design solutions based on existing site conditions that meet BOP requirements. All designs shall comply with the National Electrical Code (NEC) and BOP Fiber Specs document provided by BOP.

The contractor shall ensure completion of the following elements within the design phase:

• Concept plan

• Final labor estimate that will be required to perform the Information Technologies

Systems (ITS) installation.

• List of Materials (LOMs) appropriate for installation of each ITS subsystem

• Once validated design requirements are submitted, the contractor will not proceed to the installation phase until the BOP program office has provided written approval to proceed.

• Acceptance Test Plan

Those portions of the communications distribution system design included in work by others will be verified by a Professional Engineer (P.E.) or a BICSI Registered Communications Distribution Designer (RCDD) to ensure those elements are in conformance with applicable standards and codes. The designer and/or reviewer’s P.E. or BICSI RCDD stamp shall be affixed to the Installation Plan or cover sheet signifying the plan meets TIA/EIA Standards.

5.5 CONCEPT HIGH LEVEL DESIGN

The contractor shall create a high-level fiber design following the evaluation of existing site conditions, incorporating site specific needs as identified by the BOP facilities department. The concept plan drawing will be delivered in a CAD file converted to PDF and will include the following:

5.5.1 Single line diagram with 24-core fiber from feeder fiber hand-off (as directed by BOP facilities) to all identified switch locations.

5.5.2 Proposed routes and equipment rooms.

5.5.3 Assumptions and questions for client to clarify/confirm with on-site team.

5.5.4 Rough-order-of-magnitude (ROM) pricing estimate of site construction. Once concept plan reviews are completed, BOP COR/COTR and on-site BOP facilities’ approval is required to proceed with low-level design (LLD).

5.6 ISP LOW LEVEL DESIGN

For the locations identified in BOP ATTACHMENT A (subject to change), the contractor shall create an ISP ITS installation design by evaluating existing site conditions. The resultant design will address all criteria identified in the attachments or reasonably identified in referenced SOW documents.

NOTE: The BOP standard for premise wiring is established in BOP Fiber Specs document provided by BOP. It specifies that all buildings will be wired to the TIA/EIA standard for fiber optics.

5.6.1 All wiring and material comply with the NEC and BOP Fiber Specs document.

5.6.2 Fire Stop material will be used to restore walls to required fire rating on any new or reused pathway relevant to this design.

5.6.3 New or existing main telecommunication closets are connected to the existing entrance location with a SM count matching the OSP fiber optic cable feed terminated with LC connectors end-to-end.

5.6.4 Each fiber optic cable shall include the required single-mode fiber strands (24) to the switch plus any additional strands of spare fiber as required contractor is responsible for the termination, testing, and documentation of all 24 strands.

5.7 OSP LOW LEVEL DESIGN

For the locations identified in BOP ATTACHMENT A (subject to change), the contractor shall create an OSP ITS installation design. For all locations, the contractor shall provide all equipment, materials, labor, and services, which may be necessary to complete or to perfect all parts of the ITS installation design. Outside plant design shall be in accordance with the BOP Fiber Specs document. Where applicable, fiber optic cable provided as Government Furnished

Equipment (GFE) shall be used. The contractor shall develop a reuse plan for existing single mode fiber optic cabling. At a minimum, the contractors design documentation shall address:

5.7.1 Restoration of roads and grounds following excavation work.

5.7.2 Documentation of installed components and easy management of cable routing and Connections with map or index of wiring.

5.7.3 Dressed appearance and concealment of cables.

5.7.4 Easy access to installed cables.

5.7.5 Labeling of all cables at every duct exit/entrance and all termination components IAW national standards.

5.7.6 Installation of new telecommunication cables will not prevent use and maintenance of existing cabling and cross-connect systems.

5.7.7 Exclusive use of cables free of factory splices.

5.7.8 No use of mechanical splices or mechanical terminations.

5.7.9 When existing Entrance Facilities (EFs) are inadequate (size or location) to support a structured cabling design, contractor will include actions required to modify or relocate these functions to other spaces. Modifications will be classified as any actions to reconfigure an existing space. Creating new spaces is not considered a modification and will require a specific Form and BOP COR/COTR approval.

5.8 LIST OF MATERIALS (LOM)

The contractor shall deliver a List of Materials for each BOP location. The list of materials should include fiber optic cable, necessary pathway infrastructure, and fiber optic splice and termination panels that will need to be procured prior to the installation phase as well as labor costs for installation. The LOM shall be provided in excel format, each ITS component will be priced separately using a different tab with a summary tab that will provide aggregate total pricing for all components, the contractor will outline any dependencies between solution components. The contractor shall provide itemized costs for annual warranty options if applicable.

• Tab 1 – Summary Tab o Itemized costs for each solution component

• Tab 2 – OSP o Itemized list of materials required for installation of OSP

• Tab 3 – ISP o Itemized list of materials required for installation of ISP

5.9 FIBER INSTALLATION REQUIREMENTS

The contractor shall provide a detailed Installation Plan to accompany the low-level design. All identified exceptions to equipment manufacturer’s practices/standards (i.e., air conditioning installed, anti-static flooring, grounding, existing site facilities, power system, etc.) that could adversely affect warranty or service life shall be identified to the BOP COR/COTR. Contractor shall ensure no defacement occurs to the building structure(s) where work is being performed.

Contractor shall restore roads and grounds following excavation work. Contractor shall dispose of any unused cable and hardware unless the local POC requests and the COR/COTR concurs with the material being returned to the government. The installation schedule must be coordinated with each BOP site POC and identify specific timelines for each option of the installation as identified in the Installation Plan.

Complexity estimations fiber lengths:

Low Level 15-20,000 ft.

Med Level 32-36,000 ft.

High Level 55-66,000 ft.

At a minimum, the contractor shall:

5.9.1 Ensure that NEC, BICSI and/or EIA/TIA ITS Technician technical standards are being utilized during all work.

5.9.2 Ensure when planning cable routes, every attempt will be made to use a different space where hazardous materials are not present. It is not meant to be a wholesale remediation effort for a communication room or a conduit pathway. Areas deemed too large for ITS to handle will be identified to the site.

5.9.3 Ensure the installation of new cables does not prevent use and maintenance of existing cabling and cross-connect systems.

5.9.4 Coordinate with local BOP COR/COTR prior to any work that involves modification to existing structures.

5.9.5 Ensure all unused hardware and cable will be disposed of by the contractor.

5.9.6 Thoroughly test to ensure that installed cabling meets the TIA/EIA standards. Printed and electronic test results of all testing are required.

5.9.7 Provide all materials and consumable items (copper and fiber cable, connectors, termination equipment racks, tools, epoxy, polish pads, cable gel, tie wraps, etc.) for the installation as indicated in the LOM.

5.9.8 Ensure materials will be stored in a container at the installation staging site and protected from weather, moisture, extreme heat and cold, dirt, dust, and other contaminants that would damage the materials.

5.9.9 Ensure Product Material Safety Data Sheets (MSDS) documents will be included in the HWIPR documentation package for all applicable items used in the installation that relate to substances that will become part of the final product.

5.9.10 Ensure no defacement to the building structure shall be allowed.

5.9.11 Ensure a safe working environment for users and maintainers.

5.9.12 Ensure the use of wall mounted patch panels or rack mounted patch trays, to include.

accurate cable documentation.

5.9.13 Ensure a dressed appearance and concealment of cables.

5.9.14 Ensure easy access to installed cables.

5.9.15 Ensure minimal life cycle costs to maintain and rearrange the system to accommodate user moves and growth in communications services requirements.

5.9.16 Ensure those portions of the communications distribution system design included in work by others will be verified by a P.E. or a BICSI Registered Communications Distribution Designer (RCDD) to ensure those elements are in conformance with applicable standards and codes.

5.10 ISP Inside Plant installation will be contingent upon government review and approval of design plans. If approved, installation shall be in accordance with this SOW, required standards and regulations, the applicable Installation Plan, Low-Level Design (LLD), and LOM.

5.10.1 Install new SM Fiber runs between existing facilities to main Telecommunication Room (TR) and locations identified for new main TR locations (as specified in Installation Plan design and LOM).

5.10.2 Cable tray or another suitable pathway supports will be installed. A maximum 5-foot separation will be required if J-Hook type hanger supports are used (as specified in the Installation Plan design and LOM).

5.10.3 100% testing certifying the installed cabling meets the TIA/EIA standards will be completed. Printed and electronic test results of all testing are required.

5.10.4 The following are minimum requirements for single mode fiber and pathway requirements needed for the upcoming FSA project. It is our recommendation that where possible to utilizes existing infrastructure and pathways. If new pathways are required, then Innerduct should be used with larger conduit or at transition areas especially underground when at all possible.

1. All of the fiber optic cable shall conform to the following specifications as a minimum:

a. Fiber Type: Single-Mode

b. Core Diameter: 9 microns

c. Cladding Diameter: 125 microns

d. Proof Test: 100 kpsi (Minimum)

e. Maximum Attenuation @ 1310 nm: 0.5 dB/km @ 1550 nm: 0.5 dB/km

f. 10 Gigabit Ethernet Distance: @ 1300 nm: 10 km

g. Minimum Bend Radius During Installation: 20 X Cable O.D.

h. Long-Term:

Operating Temperature: 10 X Cable O.D. -40C to +70C

i. Storage Temperature: -40C to +70C

j. Shall be a listed indoor/outdoor cable.

2. All loose tube optical cables shall conform to the following specifications as a minimum:

a. Jacket: Indoor/Outdoor UV and moisture resistant polyethylene.

b. Jacket thickness: 1.4 mm (nominal)

c. Synthetic yarn: Torque balanced contra helical aramid yarn around the cable core.

d. Core: Dry with a water absorbent tape applied between the core and synthetic yarn.

e. Central strength member: Dielectric epoxy glass rod.

f. Buffer coating Polymer loose tubes with gel filling

g. Buffer diameter: 250 +/- 15 microns

h. Crush resistance: 250 N/cm min.

i. Minimum tensile strength: During Installation Long-Term 2,500N 850N

3. All tight buffered optical cables shall conform to the following specifications as a minimum:

a. Jacket: Indoor/Outdoor PVC jacket

b. Jacket thickness: Between 1.0 mm and 0.75mm at any point in the cable

c. Synthetic yarn: Individually tensioned and held helically around the cable core.

d. Central strength member: Dielectric epoxy glass rod.

e. Primary buffer coating: Color coded UV cured acrylate buffer.

f. Primary buffer diameter: 250 +/- 15 microns

g. Secondary buffer coating: Tight buffer high performance PVC.

h. Secondary buffer diameter: 900 microns

i. Crush Resistance: 1,800 N/cm

j. Minimum Tensile Strength:

Fiber Count During Installation Long Term 4 fiber or less 1150 N 350 N 5 to 6 fiber 1350 N 400 N 7 to 8 fiber 1550 N 475 N 10 to 15 fiber 1750 N 550 N 16 to 23 fiber 2050 N 650 N 24 to 47 fiber 2950 N 950 N 48 and greater 4150 N 1350 N

4. Interior Riser Cables:

a. The fiber optic cable shall be UL-listed riser-rated OFNR and shall meet NEC Article 770-179(B) for use in vertical runs in building riser shafts or from floor to floor.

5. Innerduct or Maxcell:

a. Innerduct shall be corrugated and have an outside diameter of less than 1.35 inches and an inside diameter of greater than 0.99 inches. Innerduct shall be non-metallic flexible raceway for use as an innerduct, Optic- Gard/PE Corrugated or approved equal.

Where transitioning from a vertical to a horizontal pull, from one size of conduit to another or within a vault or closet where the Fiber won’t be in conduit you should utilize Innerduct or Maxcell for ease of pull and protection of the fiber.

5.11 OSP Outside Plant installation will be contingent upon government review and approval of design plans. If approved, installation shall be in accordance with this SOW, the required regulations, the applicable Installation Plan, LLD and LOM.100% of installed cabling shall be tested and certified results must meet the TIA/EIA standards. Printed and electronic test results of all testing, including power metering and OTDR testing at 1310nm and 1550nm, are required.

5.12 FIBER TESTING Contractor will perform 100% testing for 1310 & 1550 unidirectional with launch cables, as well as power metering. Further testing (bi-directional – A to B-B to A) will be performed if failures or other issues are identified during initial testing using launch and receive cables. Industry standards will be based on TIA/EIA and IEC Fiber testing.

6. PROJECT COORDINATION

6.1 On this project, William “Russ” Wilkins is the Project Manager/Contracting Officer Representative (COR) The Local sites specified will be responsible for receiving all deliverables, inspecting, and accepting the services provided for this requirement in accordance with the terms and conditions of this purchase order. For acceptance of the services furnished for payment prior to forwarding the original invoice to the payment office and a copy to the Contracting Officer (CO) The contractor needs to supply the invoices to the COR for review of BOM sent to the sites.

6.2 The Project Manager and COR do not have the authority to alter the Contractor’s obligations under the purchase order, direct changes that fall within the changes clause, and/or modify any of the expressed terms, conditions, specifications, or costs of this task order modification to the current contract. If because of technical discussions, it is desirable to alter/change the contractual obligations or requirements, the Contracting Officer shall issue such changes via bilateral modifications.

7. SCHEDULE OF DELIVERABLES

Acceptance: Work shall be performed in a series of tasks issued through the Project Manager.

The satisfactory completion of each task and acceptance of each deliverable are subject to inspection by the Project Manager and the COR. The Project Manager and COR shall have ten

(10) working days for inspection following completion or delivery to the Project Manager and COR. If any item or service is found to be unsatisfactory the PM or COR will contact the Contractor.

Site Locations for Fiber Installation

SV=Service

Base Period Quantity Units Cost/Unit Total

CLIN 1 FCI Aliceville 1 SV 110700 Highway 14

P.O. Box 445

Aliceville, AL 35442 CLIN 2 FCI Danbury 1 SV

Route 37

Danbury, CT 06811 CLIN 3 FCC Hazelton 1 SV

1640 Sky View Drive

Bruceton Mills, WV 26525 CLIN 4 MCC Chicago 1 SV

71 West Van Buren St

Chicago, IL 60605 CLIN 5 FCI Tallahasse 1 SV

501 Capitol Circle, NE

Tallahassee, FL 32301 CLIN 6 FCI Waseca 1 SV

1000 University Drive, SW

Waseca, MN 56093 CLIN 7 FCI Marianna 1 SV

3625 FCI Road

Marianna, FL 32446 CLIN 8 FPC Alderson 1 SV

Glen Ray Rd P.O. Box A

Alderson, WV 24910

CLIN 9 FPC Bryan 1 SV 1100 Ursuline Ave

Bryan, TX 77803 CLIN 10 FDC Philadelphia 1 SV

700 Arch Street

Philadelphia, PA 19106 CLIN 11 Qognify Equipment 130 EA

Recorders

100=80TB

30=64TB

CLIN 12 Qognify Camera License 5,511 EA Camera/Redundant CLIN 13 IP – Fixed Camera 5,261 EA

CLIN 14 IP – PTZ Camera 250 EA

CLIN 15 2” conduit/box’s 10,000 EA

Materials only CLIN 16 Cat 6E cabling 2000 EA

1000’ boxes CLIN 17 FCI LA Tuna 1 SV 8500 Doniphan Rd.

Anthony, Tx 79821 CLIN 18 FCI Big Springs 1 SV

1900 SIMLER AVE – WAREHOUSE

Big Springs, TX 79720 CLIN 19 FCI Bastrop 1 SV

1341 HIGHWAY 95 NORTH

Bastrop, TX 78602 CLIN 20 FPC Pensacola 1 SV

110 RABY AVE

Pensacola, FL 32509 CLIN 21 Bennettsville System 1 EA

See SOW CLIN 22 FPC Alderson System 1 EA

See SOW CLIN 23 Contractor Installed 5511 EA

Option Period One (1)

CLIN 24 FCI Sandstone 1 SV 2300 County Road 29 Sandstone, MN 55072 CLIN 25 FCI Safford 1 SV

1529 West Highway 366 Safford, AZ 85546 CLIN 26 FPC Duluth 1 SV

6902 STEBNER ROAD

Duluth, Mn. 55814 CLIN 27 FPC Yankton 1 SV

1016 DOUGLAS AVENUE

Yankton, SD 57078 CLIN 28 MSFP Springfield 1 SV

1900 W. SUNSHINE ST.

Springfield, MO 65801 CLIN 29 FCI Morgantown 1 SV

446 GREENBAG ROAD

Morgantown, WV. 26501 CLIN 30 FCI Ashland 1 SV

ST. ROUTE 716

Ashland, KY 41105 CLIN 31 FCI McKean 1 SV

RT 59 & BIG SHANTY RD

Lewis Run, PA 16738 CLIN 32 FCI Edgefield 1 SV

501 GARY HILL ROAD

Edgefield, SC 29824 CLIN 33 Qognify Equipment 75 EA

Recorders

60 – 80TB

15 – 64 TB

CLIN 34 Qognify Camera License 7,537 EA Camera/Redundant CLIN 35 IP – Fixed Camera 6,641 EA

CLIN 36 IP – PTZ Camera 620 EA

CLIN 37 2” conduit/box’s 20,000 EA

Materials Only

CLIN 38 Cat 6E cabling 5,000 EA 1000 ft boxes CLIN 39 Contractor Install 13,091 EA

8. CONTRACTING AND ADMINISTRATIVE AUTHORITY

8.1 The Contracting Officer is the only person authorized to approve changes or modify any of the requirements under this modification to the current contract, and not withstanding any provision contained elsewhere in this modification to the current contract, the said authority remains solely with the Contracting Officer.

8.2 In the event the Contractor effects any such change at the direction of any person other than the Contracting Officer, the change shall be considered to have been made without authority and no adjustments shall be made in the modification to the current contract price, delivery schedule, terms or conditions to cover any increase in costs incurred as a result.

8.3 The Contractor shall submit requests for modifications to this modification to the current contract to the Contracting Officer, with a copy of the request to the Project Manager and COR.

8.4 Contractual problems, of any nature, that may arise during the performance of this modification to the current contract must be handled in conformance with specific public laws and regulations (e.g., Federal Acquisition Regulation).

8.5 Only the Contracting Officer is authorized to resolve such problems. Requests for information on matters related to this modification to the current contract action, such as explanations of terms and conditions or contractual interpretations, shall be submitted to the Contracting Officer.

9. CONSTRAINTS / NETWORK STANDARDS AND PROTOCOLS

Offerors must ensure compliance with section 508 of the rehabilitation act of 1973, 1998 amendments.

DEFINITIONS

Information System: A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. (Note:

Information systems also include specialized systems such as industrial/process controls systems, telephone switching and private branch exchange (PBX) systems, and environmental control systems.) Peripheral Device: Any auxiliary device that connects to and works with a computer or information system in some way. Examples of peripherals are image scanners, tape drives, microphones, loudspeakers, and webcams.

9.1 NETWORK STANDARDS AND APPROVED PROTOCOLS

All electronic and information (EIT) provided through this action via the resulting contract, task order, delivery order, or purchase order must meet the applicable accessibility standards at 36 CFR 1194. 36 CFR implements Section 508 of the Rehabilitation Act of 1973 as amended and is viewable at http:\\www.section508.gov. Applicable standards for this requirement include:

Information systems must meet the following network standards to be deployed on an administrative network:

• 36 CFR 1194.21 - Software Applications and Operating Systems

• 36 CFR 1194.22 - Web-based Intranet and Internet Information and Applications.

• 36 CFR 1194.31 - Function Performance Criteria

• 36 CFR 1194.41 - Information, Documentation and Support

Compliance with all Information Technology U.S. Regulations, Policies, and Guidance for the Department of Justice, Federal Bureau of Prisons, and Solicitation Requirements which include but not limited to:

• PS 1237.14 –Personal Computers and Network Standards

• PS 1237.15 –Information Resource Protection

• PS 1237.16 –Information Security

• DOJ Order 0903 –Information Technology Management

• DOJ Order 0904 –Cybersecurity Program

• Federal Information Security Modernization Act (FISMA) of 2014

• Federal Information Technology Acquisition Reform Act (FITARA)

• OMB Circular No. A-130 –Managing Information as a Strategic Resource

• NIST SP 800-53 –Security and Privacy Controls for Federal Information Systems and

Organizations.

• NIST FIPS 200 –Minimum Security Requirements for Federal Information and

Information Systems.

• NIST SP 800-171 - Protecting Controlled Unclassified Information in Nonfederal

• Information Systems and Organizations.

• Supports IPv4/v6 Dual Stack and provides full and equal functionality when utilizing

IPv6 as when using IPv4.

• Does not require or enable wireless of any type (Wi-Fi, Bluetooth, 3G/4G, etc.) unless an exception is granted by the CIO and is implemented per BOP and DOJ guidelines.

• All devices that make up the system must have a single network connection, only one

IPv4 address, one Globally Unique IPv6 address, and not be capable of routing.

• If internet accessible, can transmit traffic thru a proxy server to access the internet.

• Does not require direct inbound connections from the public internet.

• Does not allow out-of-band access (no modems, etc.).

• Does not require media converters.

• Does not directly connect to other IP networks.

• Does not use IPv4 Multicast.

• Cabling is IEEE Gigabit standard compliant.

• Power over Ethernet (POE) devices are IEEE 802.3af compliant.

• Cannot act (or is disabled from acting) as a DHCP server.

9.2 INSECURE PROTOCOLS

In accordance with current NIST standards, insecure protocols must be disabled and not planned for use. The information system must have the capability of disabling any insecure protocols including, but not limited to, the protocols listed below:

i. Telnet

ii. FTP

iii. SNMP v1/2

iv. HTTP

9.3 INFORMATION SYSTEM REQUIREMENTS

9.3.1 APPLICABILITY

All information systems deployed within the BOP, or on behalf of BOP to include contractor built and operated on-prem, private cloud systems, or government cloud, must be developed to include support for the standards detailed in this section to the greatest extent possible regardless of whether the system is connected to the BOP's administrative network (BOPNet). All systems will be evaluated prior to acquisition and/or deployment to determine that each system supports the technical standards contained in this section. Approval to connect to BOPNet will not be granted to any system that cannot support these standards unless a waiver has been granted by the CIO.

Additionally, all systems must acquire an Authority to Operate (ATO) prior to use, and an Authority to Test (ATT) prior to system testing. Testing will not leverage live data (must use data created for the sole purpose of verifying functional capability and contain neither BOP nor BOP user information). A pilot, if needed, will also be performed without the use of live data.

All the system environments, including development, test, quality assurance, integration, production, and any other environment related to the system, must reside within the authorization boundary.

9.4 OPERATING SYSTEMS AND APPLICATIONS

9.4.1 OPERATING SYSTEMS

All systems should be developed to use BOP standard workstations, laptops, and servers with versions of operating systems that are supported by the operating systems manufacturer/developer and will continue to be supported by the manufacturer/developer for at least three years after the BOP system goes live. Any systems that will rely on operating systems that are no longer supported or will be approaching their end-of-life or the end of extended support date, are prohibited from being installed unless a waiver is granted by the CIO.

All devices must have Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) Category I settings applied. Workstations and laptops with Windows operating systems must have DISA STIG settings applied for the versions of Windows currently in standard use in the BOP. Servers, workstations, laptops, and other devices running non-Windows operating systems must be approved for use by the CIO prior to acquisition and must be the latest supported versions by the vendor. If a DISA STIG exists for any non-Windows operating system, the operating system must be configured in accordance with that DISA STIG.

9.4.2 APPLICATIONS

All systems on an administrative network should be capable of using a BOP standard image for workstations. Systems should be developed to minimize the installation of new applications directly onto workstations. Systems that require a client application be installed on workstations are strongly discouraged.

Web-based applications should be installed on standard BOP servers running approved server operating systems and meet the following requirements:

i. Support TLS (non-deprecated version);

ii. Be browser-agnostic;

iii. Not require browser plug-ins, helper objects, specific ActiveX controls, or Java dependencies on the client.

All applications must be able to operate with the latest version of any supporting applications or services required to run that application (i.e., Java, Apache, IIS, etc.).

9.4.3 AUDITING/LOGGING

All operating systems and/or applications must be capable of auditing events and maintaining logs with sufficient information to be able to account for the actions of individual users and record system events and processes.

9.5 IDENTIFICATION, AUTHENTICATION, AND AUTHORIZATION

In order to reduce the amount of effort required to administer the information systems that are connected to any network and to comply with Homeland Security Presidential Directive 12 (HSPD-12), all new information systems should use a centralized directory for identification, authentication, and authorization to control, provision, and de-provision access to those systems.

To connect information systems to an administrative network, all information systems must be capable of supporting Lightweight Directory Access Protocol (LDAP v3 or successor).

Systems that cannot support either a BOP directory service or DOJ federated service and require the management of a separate credential store for identification, authentication, and authorization are prohibited.

Each system user must be uniquely identified. Access to information is controlled using a “Least Privilege” role- or assignment-based methodology that provides the user with only the information and access required to perform his/her duties and nothing more. Systems must be capable of tiered-role privileges that distinguish between users and administrators and their authorized functions.

9.6 ENCRYPTION

9.6.1 DATA AT REST

All information systems that store data must have the capability to encrypt the drives on which the data is stored using FIPS 140-2 compliant encryption. If the system cannot support encryption of system drives, it must be approved for use by the CIO prior to acquisition and use.

9.6.2 DATA IN MOTION

All information systems that transmit data over administrative networks must use protocols that encrypt data as it traverses the network. Information systems must support the most current version of secure protocols and encryption standards and must be capable of being configured to prevent the use of insecure protocols.

9.6.3 PUBLIC FACING WEBSITES

Any information system that hosts a publicly accessible website and web services must only provide service through a secure connection (HTTPS) and must use HTTP Strict Transport Security (HSTS) to ensure this connection.

9.7 ENDPOINT SECURITY AND MANAGEMENT AND VULNERABILITY

MANAGEMENT

All networked information systems should be capable of being managed through an approved endpoint security and management application and be fully operational while being scanned for security vulnerabilities without disruption of service. All networked systems should also be capable of being patched using a centrally managed patch management application.

Computer workstations, laptops, tablets, servers, and other computing devices using an operating system must employ anti-virus software protection. Anti-virus software and virus definition files must be updated with the most current versions and the anti-virus software must be configured to:

i. Begin protection when the devices are powered on;

ii. Scan daily;

iii. Check all files processed by the system in real time.

9.8 CLOUD SERVICES

Any system that will connect to or be hosted in a non-BOP cloud service must use cloud service providers (CSP) that have been independently evaluated by an authorized FedRAMP 3PAO and are FedRAMP-certified, and the CSP has provided the most current System Security Plan (SSP), Control Implementation Summary (CIS), Customer Responsibility Matrix (CRM), Security Assessment Report (SAR), and list of any open Plans of Actions and Milestones (POAMs) to the BOP CISO for consideration, and has received an ATO from the BOP Authorizing Official

(AO).

9.8.1 CLOUD APPLICATIONS – REQUIREMENTS FOR COTS AND CUSTOM

DEVELOPED

Contractors must develop or provide administration and user guides for applications, whether the application is custom developed for the BOP or is a Commercial Off the Shelf (COTS) product.

All applications must adhere to Section 508 accessibility standards.

9.8.2 CLOUD APPLICATIONS – CUSTOM DEVELOPED

The BOP owns any and all source code generated for applications custom developed for the BOP. The source code for any application custom developed for the BOP must be delivered to the BOP before the contract expires.

Contractors should use an Agile development strategy (or similar strategy) to enable rapid development with routine opportunities for stakeholders to review progress and provide feedback during the development process.

Applications should adhere to usability principles, plain language, and industry best practices.

Applications should interface with the BOP's IdP using SAML2.0 or OAuth 2.0 to appropriately authenticate users and protect sensitive resources.

Application data should be made available via webservices that are built using REST APIs, with endpoints appropriately protected.

Applications intended for deployment in the BOP’s cloud environment will either be hosted in AWS GovCloud West or AWS GovCloud East, depending on the FISMA classification of the information contained in the system.

Contractors shall identify exact cloud services and resources (i.e. Lambda, RDS types, EC2 instance types, etc.) that will be required to build the system, and use the AWS cost estimation tool to provide a breakdown of the anticipated system cost.

Contractors will make necessary changes to the application, configuration, or cloud infrastructure/services script (i.e. IaC) if required by the BOP cloud team.

Contractors will create CloudFormation scripts that will be used to build the Virtual Private Clouds (VPC) and infrastructure needed, and make necessary changes as identified by the BOP cloud team.

9.9 PERIPHERAL REQUIREMENTS LOCALLY ATTACHED PERIPHERALS

Peripherals that are locally attached to standard BOP workstations must:

i. Not be shared on the network.

ii. Not require software to operate that requires access to the internet or other network resources.

iii. Not require software to operate that requires older versions of software to operate such as

Java.

iv. Not broadcast wireless signals (i.e., Bluetooth, Wi-Fi, etc.).

v. Not require a change to the workstation local security policy to operate.

9.9.1 LOCALLY ATTACHED PRINTERS AND SCANNERS

Locally attached printers and scanners must have 64-bit drivers and cannot be shared to workstations other than the workstation to which it is directly connected.

9.9.2 NETWORKED-ATTACHED PERIPHERALS

Peripherals must connect directly to an administrative network should be part of a larger system or sub-system authorized to operate on that network. Each system or sub-system must provide controls to the peripherals attached to the network that comply with the system standards detailed above or provide mitigating controls for peripherals that cannot meet a system standard. The following sections detail the minimum additional standards for common peripherals attached to an administrative network:

9.9.3 MULTI-FUNCTION DEVICES AND NETWORKED PRINTERS

All multi-function devices (MFD) and networked printers must be capable of being configured in accordance with the Multifunction Device and Network Printers DISA STIG.

MFDs must be capable of supporting PIV authentication either directly or via a peripheral attachment/software but are not required to use PIV authentication at this time.

9.9.4 PRIVACY AND RECORDS MANAGEMENT

All systems must be evaluated prior to ATT or ATO for privacy and records management requirements. An Initial Privacy Assessment (IPA) must be completed and if BOP Privacy and Records Management Branch, and DOJ Office of Privacy and Civil Liberties (OPCL) determines that the system collects, processes, stores or disseminates personally identifiable information (PII), a Privacy Impact Assessment (PIA) must be done to evaluate the impact on the confidentiality, integrity, and availability of the data. If required, the Office of General Counsel (OGC) will prepare a System of Records Notice (SORN) to be published in the federal register prior to system’s use. All systems must complete a Records and Information Management Certification (RIMCert) evaluation regardless of PII status.

10. CONTRACTING AND ADMINISTRATIVE AUTHORITY

A. The Contracting Officer is the only person authorized to approve changes or modify any of the requirements under this modification to the current contract, and notwithstanding any provision contained elsewhere in this modification to the current contract, the said authority remains solely with the Contracting Officer. In the event the Contractor effects any such change at the direction of any person other than the Contracting Officer, the change shall be considered to have been made without authority and no adjustments shall be made in the modification to the current contract price, delivery schedule, terms or conditions to cover any increase in costs incurred as a result.

B. The Contractor shall submit requests for modifications to this modification to the current contract to the Contracting Officer, with a copy of the request to the Project Manager/COR.

C. Contractual problems, of any nature, that may arise during the performance of this modification to the current contract must be handled in conformance with specific public laws and regulations (e.g., Federal Acquisition Regulation). Only the Contracting Officer is authorized to resolve such problems. Requests for information on matters related to this modification to the current contract action, such as explanations of terms and conditions or contractual interpretations, shall be submitted to the Contracting Officer.

11. CONSTRAINTS

Compliance with section 508 of the rehabilitation act of 1973, 1998 amendments All electronic and information (EIT) provided through this action via the resulting contract, task order, delivery order, or purchase order must meet the applicable accessibility standards at 36 CFR 1194. 36 CFR implements Section 508 of the Rehabilitation Act of 1973 as amended and is viewable at http:\\www.section508.gov. Applicable standards for this requirement include:

• 36 CFR 1194.21 - Software Applications and Operating Systems

• 36 CFR 1194.22 - Web-based Intranet and Internet Information and Applications.

• 36 CFR 1194.31 - Function Performance Criteria

• 36 CFR 1194.41 - Information, Documentation and Support

Compliance with all Information Technology U.S. Regulations, Policies, and Guidance for the Department of Justice, Federal Bureau of Prisons, and Solicitation Requirements which include but not limited to:

• PS 1237.14 –Personal Computers and Network Standards

• PS 1237.15 –Information Resource Protection

• PS 1237.16 –Information Security

• DOJ Order 0903 –Information Technology Management

• DOJ Order 0904 –Cybersecurity Program

• Federal Information Security Modernization Act (FISMA) of 2014

• Federal Information Technology Acquisition Reform Act (FITARA)

• OMB Circular No. A-130 –Managing Information as a Strategic Resource.

• NIST SP 800-53 –Security and Privacy Controls for Federal Information Systems and Organizations.

• NIST FIPS 200 –Minimum Security Requirements for Federal Information and Information Systems.

• NIST SP 800-171 - Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

11.1.1 RELATED SERVICES

a. During the term of the contract the contractor shall be responsible for the retention of any specialists required for the completion of the work.

b. The contractor shall be responsible for the work done by any individuals or firms they retain.

11.1.2 STANDARD OF SERVICE

a. The contractor shall identify one primary contact person for the project within (2) calendar days after notification of contract award.

b. The contractor shall identify an alternate contact person(s) for the project within (2) calendar days after notification of contract award.

c. The contractor and his employees shall perform in a professional manner keeping noise and disturbances to a minimum.

d. The contractor shall be responsible for assuring all persons retained to work on this project comply with all policies and regulations while on the property where work is taking place.

e. The contractor shall be responsible for assuring all adjacent surfaces and vehicles are protected during all step of construction, including a thorough cleanup at the end of each work period.

f. If any other information is needed please contact the Bureau Project Manager/COR.

12. SPECIAL SECURITY AND CLEARANCE REQUIREMENTS:

The Contractor must abide by all FBOP security requirements including, “but not limited to” a 5-year Tier 1 clearance with HSPD-12 badge issued by the FBOP. All contractors and Subcontractors that will be on-site will be required to a background check.

NOTE: The BOP may permit other Government security clearances, to be substituted for the above background investigations, if determined by the BOP to be equal, current, and provided the contractor submits adequate documentation to support the BOP’s determination.

It is the responsibility of the contractor and the respective COR to ensure that all necessary forms and information is completed and submitted in a timely manner.

Refer to solicitation document, which includes FAR clause 52.204-9, “Personal Identity Verification of Contractor Personnel” and the DOJ clause “Notice of Contractor Personnel Security Requirements.” Both clauses refer to the Homeland Security Presidential Directive-12 and Federal Information Processing Standard Publication 201.

In addition to the aforementioned background investigations, the BOP’s security requirements include, but are not necessarily limited to the following:

1) National Crime Information Center (NCIC)

2) National Agency Check with Inquiries…