030ADV24R0008 - Attachment J-2 - Task Order SOW FINAL.pdf
PDF 368 KB Posted
- Solicitation number
- 030ADV24R0008
- Issued by
-
Library of Congress
About this file
This document is a Statement of Work (SOW) for the Integrated Electronic Security System (IESS) and Physical Security Network (PSN) Operations and Maintenance Task Order under Solicitation 030ADV24R0008 issued by the Library of Congress (Library).
The SOW requires the contractor to provide all services and technical expertise to maintain an uninterrupted and fully functional IESS and PSN, including preventative maintenance, emergency repair, installation, and inventory services. Key requirements include monitoring hardware and software obsolescence, replacing end-of-life components, providing a preventative maintenance plan, supporting unscheduled and emergency corrective maintenance, and delivering various reports. The contractor must also procure and install specified IT hardware, replace 300 analog cameras with IP cameras, and provide a transition plan. The period of performance is from September 2024 to September 2025. This is an unrestricted solicitation with no set-asides.
View the file
Other files
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
030ADV24R0008 Page 1 of 13 Attachment J-2 - IESS TO SOW 04/15/2024
030ADV24R0008 – Attachment J-2 Statement of Work (SOW) Integrated Electronic Security System (IESS) & Physical Security Network (PSN) Operations and Maintenance Task Order
C.1. OVERVIEW / BACKGROUND:
The Library of Congress (Library) Security and Emergency Preparedness Directorate (SEPD) operates the Physical Security Network (PSN) supporting the Library’s Integrated Electronic Security System (IESS).
The IESS consists of the Primary Intrusion Detection System (PIDS) and the Security Video Management System (SVMS). Functionally, PIDS provides alarm monitoring and processing, ID badge making, and card reader control to spaces and consists of card readers, intrusion sensors, alarm panels and proprietary software defined in the IDIQ contract. SVMS provides video monitoring, recording and retrieval. Both these systems depend on the Physical Security Network (PSN). The PSN includes data servers, storage, data network devices, computer workstations and related software. Operation of the PSN is governed and overseen by Library’s Chief Information Officer (CIO).
The Library requires operations and maintenance (O&M) support of the IESS and PSN.
C.2. SCOPE
The contractor shall provide all required services and technical expertise to secure an uninterrupted and fully functional IESS & PSN. The contractor must provide real-time availability, visibility, timely incident resolution, and risk mitigation of the IESS & PSN to the Library. This involves integration with software outlined in the IESS IDIQ contract TBD and the configuration, support, maintenance and integration of the PSN equipment information system equipment (data servers, storage, data switches, and workstations).
C.3. REQUIREMENTS
The contractor shall provide preventative maintenance, emergency repair, installation, and inventory services to maintain a fully functional IESS & PSN, including the purchase of materials and parts in accordance with the IESS IDIQ contract. Refer to Attachment J-4 – IESS System Components for a listing of applicable items. Specifically, the contractor shall provide services and technical expertise as outlined in the following sections.
3.1. CLIN 0001 Physical Security Network (PSN) Operations & Maintenance
3.1.1. The contractor shall provide preventative maintenance, emergency repair, installation, and inventory services to maintain a fully functional Integrated Electronic Security System (IESS), including the purchase of materials and parts.
3.1.2. The contractor shall monitor planned obsolescence of the IESS hardware and software components as part of uninterrupted preventative maintenance and lifecycle replacement activities. Specifically, the contractor must exercise the technical expertise and business judgement to recommend an acceptable and modern alternative to provide the same or better functionality.
3.1.3. The contractor shall prioritize the replacement of components that may be impacted by end-of-life products where the manufacturer is no longer offering technical support for those products. Outdated and unmaintainable solutions place the Library at risk of equipment and programmatic failure. The contractor must avoid failure of a fully-operational and uninterrupted IESS at no additional cost to the Library.
030ADV24R0008 Page 2 of 13
3.1.4. The contractor shall ensure all replacement parts are of the same or equivalent make and model as the component requiring replacement. If a product is beyond the manufacturer’s support time frame, the contractor shall recommend a suitable replacement and receive written approval from the COR prior to installing the replacement.
3.1.5. The contractor shall provide hardware, licenses, and peripherals as outlined in C.3.2.
3.1.6. The contractor shall specify an estimated date, noting that it is an estimated end-of-support date. This information must be provided in writing to the COR at the time of award. Updates to the end-of-support date(s) must be provided.
3.1.7. The contractor must notify the COR immediately upon discovery and significantly in advance of any potential obsolescence or end of life to IESS hardware and software components. The contractor is responsible for reporting to the COR when it is anticipated that hardware or software is approaching its average replacement cycle.
3.1.8. The contractor may be required to provide unscheduled or emergency installation services and shall comply with Library IT processes and ticketing procedures to schedule installation services and to obtain necessary approvals to perform required tasks.
3.1.9. The contractor must provide, implement, and maintain a Preventative Maintenance (PM) Plan. The
PM is based on the task, frequency, or corrective action. The PM must include all IT systems and software associated with the IESS. At a minimum, the plan shall include the following:
3.1.9.1. A schedule for all IT infrastructure components to include but not limited to Servers, Workstations, Network devices etc. in the Library, which addresses installation of patches and/or fixes for all computers and field panels at all locations.
3.1.9.2. Technical roadmap for execution of the preventative maintenance plan.
3.1.9.3. Faults and failures found during PM shall be documented and reported to the COR, to include corrective actions taken/to be taken. Degradation from baseline should be reported to the COR.
3.1.9.4. Annual power outages testing (shutdown and recovery) by the AOC at the Library (three tests of generator-systems and one test of the Uninterruptible Power Supply (UPS)).
3.1.9.5. Contractor shall perform configuration audits to ensure equipment is located in accordance with diagrams and functioning properly. A configuration audit is an inventory of hardware, software, drawings and technical documentation and is a function of configuration management. Configuration audits shall be performed in parallel with preventative maintenance. The contractor shall review and validate technical drawings as part of the configuration audit. If a discrepancy is found in the audit, the contractor shall redline drawings to indicate the actual configuration of the system.
3.1.9.6. As part of a continuous and uninterrupted IESS, the contractor must resolve incidents on a timely basis. “Timely” is defined by the level of priority to address any obstacles to IT systems that may prevent the Library from conducting normal operations. To better facilitate the timeliness of issue resolution, activities tracked and resolved must be consistent or earlier than the standard IESS SLAs.
3.1.9.7. For other unique scenarios where emergency access is limited or restricted, the contractor must notify and consult with the COR for specific technical direction within 15 minutes of being notified of the incident.
3.1.10. The contractor shall provide a plan that addresses the following:
3.1.10.1. Migration plan and support the PSN IT infrastructure from the Jefferson and other non-datacenter locations into the Technical Operations Center (TOC).
030ADV24R0008 Page 3 of 13
3.1.10.2. A plan to re-design critical PSN devices to address open IT security vulnerabilities. The plan must outline newly identified and existing vulnerabilities with recommended resolution.
3.1.10.3. A plan outlining the schedule of quarterly patching reviews, user account maintenance, software updates, firmware, and life cycle analysis, security and auditing.
3.1.11. Contractor shall support added items as they are installed under CLIN 0004.
3.1.12. The contractor shall perform preventative maintenance quarterly and when required by ITSG in accordance Information Technology Security Directive 5.410.1 (Attachment J-5_ITSG_SD_5-410- 1.pdf)
3.1.13. The contractor shall comply with the Library Hardening guides that are furnished after contract award.
3.1.14. The contractor shall provide continuous monitoring support of the Video Management System (VMS) and Primary Intrusion Detection System (PIDS) Application Systems, this includes conducting root cause analysis to identify if any servers, storage, network devices, or workstations need service.
3.1.15. The contractor shall ensure support for all new or upgraded hardware and software shall be included as part of IESS Routine and Preventative Maintenance Services/Management of Third Party Support.
3.1.16. As the certified service provider of the Library’s continuous and hardware support agreements, the contractor must actively monitor software releases from the software manufacturers that provide applications in support of the IESS. When a new release is made available by the respective manufacturers, the contractor shall immediately notify the Library. Third Party support tasks may include but are not limited to:
3.1.16.1. Maintain and make available all appropriate service/support agreements/licenses for software and hardware support.
3.1.16.2. Make available fixes, patches, and updates for identified software.
3.1.16.3. Test updates in an environment to simulate issues that may arise in production.
3.1.16.4. Coordinate with manufacturers and support on-site certification visits, if required.
3.1.17. The contractor shall provide a report identifying backup meta data for the system and participate in annual Disaster Recovery exercises conducted by OCIO team.
3.1.18. The contractor shall deliver reports, with detail documentation for discussion and analysis delivered in formats defined in C.11 or other format if approved by COR. Due date for reports shall be as designated in SOW C.5.
030ADV24R0008 Page 4 of 13
3.1.18.1. Monthly reports with a cover page calling out action items and overdue deliverables.
Monthly report shall document all tasks completed, projects in process, projects on hold, actions required from Library/Contractor, blockers, and general status.
3.1.18.2. Weekly reports with a front section calling out action items and blockers. Weekly report shall document tasks completed and active tasks with accomplishments and next steps planned for the week.
3.1.18.3. All written deliverables must be of a professional quality; free of grammatical and spelling errors; accurate in presentation, technical content, and adherence to accepted elements of style; clear & concise; and consistent with the requirements of the contract.
3.2. CLIN 0002 Install IT Hardware
3.2.1. The contractor shall procure, test, and install the following equipment in the table below. Install services will be provided and invoiced following successful testing, the contractor shall update baseline configuration documents accordingly. Refer to the table below for IT infrastructure components that need to be procured & installed. The contractor shall submit a test report indicating results of testing in their own format.
Item No Description Quantity
1 1100W AC 80+ platinum config 1 secondary power supply 14 2 9300 DNA Advantage, 48-Port, 5 Year SW Term License 14 3 Catalyst 9300 8 x 10GE Network Module 14 4 Catalyst 9300 48-port UPOE, Network Advantage 14 5 CON-SNT-C93004UA SNTC-8XNBD Catalyst 9300 48-port UPOE, Network
Advantage Service Agreement 14
6 HPE DL38X Gen 10 5 year Maintenance package 26
3.3. CLIN 0003 IESS Operations and Maintenance
3.3.1. The contractor must describe preventative maintenance tasks for each system component and software application. The contractor is required to evaluate event data from the service location to identify potential issues that have not been reported for repair.
3.3.2. The contractor will use service tickets to schedule preventative maintenance tickets repetitively. A ticketing process must be used to track resolution to resolve incidents actively and regularly upon discovery of potential failures. The contractor must resolve any identified preventative maintenance incidence in accordance with section C.3.3.3 and report written failure reduction findings to include details of preventative action frequencies, scheduled dates, and testing procedures to the COR.
3.3.3. Security Equipment Maintenance Cadence
3.3.3.1. Library Collections
The Library’s Collections are tiered by risk and the required maintenance schedule will reflect this. The required preventative maintenance activity for each collection level is listed below.
Collections Level PM Frequency Definition Platinum Quarterly The Library’s most priceless items
030ADV24R0008 Page 5 of 13
Gold Semi-Annually (2x per year)
Rare items having prohibitive replacement cost, high market value, and significant cultural, historical, and/or artifactual importance.
Silver Annually (1x per year)
Items that require special handling and including those at particularly high risk, such as computer software, popular labels in print, videos, and compact discs.
Bronze Biennial (1x every 2 years)
Bronze collections include those items served without special restrictions in the Library’s reading rooms and materials that may be loaned without stringent restrictions.
Copper N/A Copper collections are those the Library does not intend to retain but holds while deciding, for example, which may be used for its exchange and gift programs.
3.3.3.2. All Other Areas
For non-collection areas, the contractor shall perform scheduled maintenance on the system based on the following:
Non-Collection Risk Category
PM Frequency Definition
Critical Quarterly (4x per year= 1x every 3 months)
• System-wide Outages and Interruptions to IESS to include access to forensic data related to high value collections, monitoring of all Capitol Hill perimeter entrances and doors, electronic key boxes, duress switches, etc.
• Services impacting emergency responses and monitoring by the USCP such as inspections, physical security, technical countermeasures, and widely attended public events on the Capitol Hill complex
• Activities impacting the Financial Services Directorate such as the Disbursing Office
• Activities impacting the Human Capital Directorate such as the Library of Congress Credit Union and Little Scholars Childcare Center
• Capitol Hill Perimeter and Lobby Cameras
• Activities impacting the Library’s IT infrastructure such as IT security breaches High Quarterly • General Physical Access by Members of the Library Staff, Members of Congress and Congressional Staff impacting Continuity of Operations
• Activities impacting the Library’s Space Utilization Planning and Design (SUPD) and AOC architectural, safety, electrical, and engineering components
• Activities impacting the Library’s IT infrastructure such as the critical technical operations center, data centers, switch rooms, etc.
• Activities impacting the Library’s ability to host events such as the use of the freight elevator by caterers.
• Perimeter and Lobby Cameras for Library Annexes such as NLS, Culpeper, etc.
Moderate Semi-Annually
• General Physical Access by Readers and the General Public
• Postal Operations Center
• Receiving Office
• Cash Room for Food Service Contractor
Low Annually • Childcare Center
• Retail Sales and Storage
030ADV24R0008 Page 6 of 13
• Record Storage Areas as identified by National Archives and Records Administration (NARA)
• Other items not covered by the priority matrix above
3.3.3.3. Daily Performance Checks
In addition to the PM activity specified above, the contractor shall perform daily functional performance checks.
The intent of these checks is to verify the video management system and the PIDS system components are operating as designed. Examples of the level of detail intended for these checks are listed below:
• All servers supporting VMS and PIDS are operating within recommended limits for available memory resources.
• All cameras are sending video streams and being recorded.
• All security panels have data connectivity to the server and operating in accordance with the manufacturer’s specifications.
The contractor shall develop a method to identify system and connected device (edge) failures, whether intermittent or catastrophic. Additionally, these checks should be used to evaluate overall performance deficiencies and anomalies. Failures or performance concerns should be immediately reported as a trouble, and resolved within the constraints of the Incident Resolution Requirements.
3.3.4. Emergency (unscheduled) repair times
Priority Collection Level
Acknowledge Response Time
Resolution Time
P1 Platinum 15 minutes Immediate, NTE 2 hours P2 Gold 15 minutes Same business day, NLT 2 hours P3 Gold 15 minutes Same business day, NLT 4 hours P4 Silver/Bronze 1 hour NLT 2 business days
3.3.5. Door Hardware
The contractor will be required to support new and existing installations on doorways equipped with door hardware maintained by the building owner, (AOC). The contractor shall support the equipment monitoring the device signal starting at the output terminals of the alarm sensor or door controller to include a full functional test of the complete alarm circuit. Examples of these type installations include, but are not limited to, the following:
• Automatic Door Openers
• Delayed Egress Devices (e.g. maglock or delayed panic egress bar)
• Storefront Style Doors with Electrified Vertical Rods
• Electrified Strikes and Lock Sets Inside Building Perimeter
• Motorized Overhead Doors
• Secure Storage Facility Locking Hardware
030ADV24R0008 Page 7 of 13
3.3.6. Unscheduled and Emergency Support
3.3.6.1. Acceptance and Response
The contractor shall provide a means to receive requests for service or repair from the following: (1) Library staff and contractors, (2) United States Capitol Police (USCP), (3) House of Representatives and Senate staff or members of Congress, (4) Architect of the Capitol (AOC). The response to these requests shall be in accordance with SOW 3.3.4., Emergency (Unscheduled) Repair Times. This service shall be available 24x7x365 days a year.
Service will include account management support such that devices and/or systems malfunction will be addressed per the restoration table.
3.3.7. Baseline Configurations and Build Books
The contractor shall provide and maintain the Baseline Configuration documentation and Build Books for the IESS system. The contractor must document the step-by-step procedures in the build book for a qualified system administrator to install and configure the system. The build book must include extensive details of each installation and configuration and thoroughly document the steps necessary to sequentially build, configure, and install a system compliant with Library policy.
For the software service agreements, the contractor must manage the software title and patch level and all other critical system settings required to rebuild the system. Separate books are required for each major system and subsystem. This includes the Library’s PIDS (currently Software House C-Cure 9000 Support Agreements, Security Video Management System (currently Intellicene Symphia Support Agreements), and all the related storage or failover components.
The Baseline Configuration shall include information critical to configuring the Physical Security Network servers, data switches and mass storage devices.
Preventative Maintenance by Location
Location Description of Preventative Maintenance Tasks Frequency Maintenance Rounds for field devices/computers
Verification of communications to all equipment, including servers: LM G01C (ACC), LJ G39 (PCC Equip. Room), LJC71C-CURE System, LJC71 Intellicene System, Key Systems Electronic Key boxes, Lecterns
Daily
Culpeper, Ft. Meade, Taylor Street, Cabin Branch, Childcare Center
Network PM: Servers (Culpeper only), C-CURE Workstation, Cisco 1801 router
Annually
Childcare Center, Retail Sales and Storage, and Record Storage Areas
CCTV, access control devices, beam photoelectric detectors and Istars
Annual (Silver)
Capitol Hill Complex Network Maintenance
C-CURE/Intellicene servers, domain controller, workstations, Cisco IPS-4215, network router/switches.
Jefferson only: WSUS, Whats Up, RSA, NTP clock
Semi- Annually
Lecterns Maintenance UPS, HDR-P Quarterly Police Shelters Camera, access control devices, UPS, RMP/SMP/ RM4 cans, duress, shock sensors, peripheral electronic equip, workstations, pump boxes
Quarterly
Rare Book Area, Vaults, Server Maintenance
CCTV, access control devices, beam photoelectric detectors, temp/water sensor, duress, shock sensors, peripheral equip
Quarterly
030ADV24R0008 Page 8 of 13
Location Description of Preventative Maintenance Tasks Frequency Electronic Key Boxes, Lobby Cameras
Devices Key boxes, cameras Quarterly (Platinum)
Entrances/Exits/Garages, General Collection Stacks and General Office areas
CCTV, access control devices, security lock box, shock sensors, armored door cord, peripheral electronic equip
Bi-Annually (Bronze)
Security Rooms
(LCC/ACC)
CCTV, access control devices, beam photoelectric detectors, security lock box, temp/water sensor, duress, peripheral electronic equip, workstation
Quarterly
Perimeter Cameras/Photoelectric Sensors, Duress Circuits, Postal Operations Center, Receiving Office, Cash Room for Food Service Contractor, Disbursing Office
Camera, perimeter sensor, card reader, tampers, beam photoelectric detectors, duress circuits, pump boxes
Semi- Annually (Gold)
Security Closets Door contacts, tampers, UPS, iSTAR, power supply, temp/water sensor, RMP/SMP/ RM4 cans, peripheral electronic equipment
Annually
3.3.8. Maintain “As-Built”/Engineering Drawing Set
Contractor shall maintain the set of engineering drawings which document the signal flow between system components, physical location of all devices, and riser diagram of security panels. The background Computer Aided Design information for the base buildings shall be updated at least once per year to align the space plans with the Library’s most recent library of CAD files. The contractor shall update the drawings continuously and publish in PDF and native (AutoCAD 2019 version) once per year.
3.4. CLIN 0004 Replace 300 Analog Cameras
The contractor shall procure IP cameras and replace analog technology cameras with “IP” cameras identified in the table below.
Camera Locations”. Installation shall be prioritized as follows:
1. Capitol Hill complex (Madison, Jefferson & Adams buildings) Cameras
2. Priority sequential order (“1” before “2” and “2” before “3”).
The contractor shall validate locations of camera and BOM requirements noted in table below. The contractor shall assume the following applies for installation purposes:
- Cameras shall be installed in a drop ceiling, no higher than 10 feet.
- Camera locations are within 300ft of existing data switches
- The contractor shall comply with the LOC IT Security Directive requirements (See attachment J-5, Directive 5-410.1)
Item No Description Quantity 1 Bosch, Fixed Dome 2MP HDR 3-9mm IR IP66 300 2 Bosch, Drop ceiling support mounting plate for flexi dome IP fixed dome camera 200 3 Bosch, Fixed Camera Wall mounting pendant 50 4 Bosch, Fixed camera will mounting plate 75 5 PAIGE DATE, Plemum gamechanger cables (1000' roll) 100 6 BRADY, Brady labels MC-500-595WT bk 12 7 OCC, 12 Channel Plenum rated fire optic cable 4000 8 CORNING, SC to SC connectors 25/Box 5 9 INTELLICENE, 373.20Symphia VMS 7.7 single (1) Camera License software for
ENTERPRISE package 300
10 Platinum Tools, Pass Through ezEX-RJ45 (50 Pack) 15
030ADV24R0008 Page 9 of 13
The contractor shall develop a Project Installation Program of Actions and Milestones (POAM) for this task order, including data reports, which can be modified as necessary. However, any modifications or updates to the POAM require acceptance by the COR. Prior to the award, the contractor shall submit the POAM to the COR, ensuring that the project can be executed according to the reasonable schedule of actions.
C.4. CONTRACT PERFORMANCE
4.1. Contractor Personnel Roster
To provide badges and verify the suitability of contract staff, the contractor shall provide to the Library’s COR a roster of personnel, with resumes, who will be performing services. The COR will review the qualifications of proposed staff before approval and issuance of badges. If the contractor's staff does not meet the qualifications to provide the services described in the task order, the contractor shall provide the resume of another staff.
4.2. Issue Tracking System
To meet the minimum IESS maintenance, upgrade, and enhancement tracking system prioritization and incident response requirements, the contractor must provide a web-based incident and resolution tracking/work order system or equivalent method for tracking preventative maintenance and repair activities. Access by the Library Administrators must be initiated from Library networks over a secure VPN connection.
The contractor must provide access to the incident and resolution tracking system for the COR and designated Library staff to review data, initiate and check the status of corrective and preventative repairs, and generate reports.
The contractor must provide ongoing end-user support to use the ticketing system.
C.5. SCHEDULE OF EVENTS/DELIVERABLES
Event /
Deliverable #
SOW
Reference Description of Event/Deliverable Due Date
1 N/A Kick-Off Meeting Within 5 business days after award
2 3.1.25 Provide support to Information Technology Contingency Plans (ITCP)
Five (5) business days after receipt of the Library’s comments to the Draft ITCP
3 3.4 Project Installation Program of Actions and Milestones
Within 5 business from the start of the period of performance
4 3.2.1 Installation Test Report Within 10 days after successful completion
Within 10 days after successful completion
5 3.3.8 “As-Built” Drawings Within 30 days after successful testing
Within 30 days after successful testing
6 3.1.12.3.2 Inventory Updates within 30 days after successful testing
Within 30 days after successful testing
7 3.1.24 QASP Thirty (30) days after contract award
030ADV24R0008 Page 10 of 13
Event / Deliverable #
SOW
Reference Description of Event/Deliverable Due Date
8 C.4.1 Key Contractor Personnel Roster Within 30 business days of award
9 3.1.7 Plan for replacement of End of life equipment Within 120 Business days after award
10 3.1.16 Plan for updates to address security issues identified by LOC ISSO
Within 120 Business days after award
11 3.1 & 3.3.6 Evidence of Unscheduled and Emergency Corrective Maintenance and reporting
Weekly
12 3.1.25.1 Monthly reports Due on the first Monday of the month by noon
13 3.1.25.2 Weekly reports Due on Monday by noon except for the first Monday of the month (Monthly report is a superset of the weekly report)
14 C.15 Transition Plan Due with Proposal
15 3.1.12.3.2 Software and Hardware Inventory Report (.xls and .pdf) the 5th of each month of January, April, July, October
16 3.1.25 Report Backup metadata of System Data the 5th of each month of January, April, July, October
17 3.1.26 Project Status and Performance Report Monthly 18 3.1.26 Project Review Report & Meetings Weekly 19 3.3.2 Recommendation and Findings Report Annually
C.6. OTHER REQUIREMENTS
6.1. Coordination with System Administrator
The Government’s Applications Administrator (the System Business Owner, SEPD Protective Services Division Chief) will provide any necessary programming of the C-Cure system as suggested by the contractor in support of this effort. The contractor shall coordinate any necessary changes at least two weeks prior to installation.
6.2. Coordination with Custodial Division Personnel and USCP
The contractor shall work with the COR to schedule access to non-public/non-SEPD-controlled areas. This coordination will be made with a COR-designated Library space owner and the USCP Library Division Police Supervisor to minimize disruption of Library operations or security controls. Note that for security panels protecting building perimeter access areas, this coordination shall require the contractor to provide notification four (4) weeks prior to the activity.
030ADV24R0008 Page 11 of 13
C.7. PROJECT SCHEDULE/INSTALLATION SCHEDULE
Any work affecting the normal operation of the Library shall be performed outside of normal business hours.
Normal business hours for this task order are defined as 8:00 AM to 8:00 PM Monday through Friday, excluding Federal Holidays and unscheduled times, which prevent normal business. All other work shall be completed during 6 a.m. to 6 p.m. Monday – Friday, excluding Federal Holidays. Any access required outside this time frame, should it become necessary, shall be coordinated by the COR.
C.8. PLACE OF PERFORMANCE
Refer to the IDIQ locations of performance.
C.9. HOURS OF OPERATION
Hours of operation are specified in the IDIQ
C.10. GOVERNMENT FURNISHED PROPERTY
The Library will provide access to systems, facilities, and information as required for the contractor to fulfill the requirements of this contract.
C.11. DOCUMENTATION
The contractor shall develop all deliverables in native file format of Autodesk Brand AutoCAD version 2018 or later, Adobe Acrobat and Microsoft Office Word/Excel/Project version 2019 or later.
C.12. TRAVEL
The Library will not separately reimburse contractor travel expenses incurred in performance of this contract.
C.13. INTELLECTUAL PROPERTY RIGHTS
The Library shall have unlimited rights in and rights to use, modify, or reproduce any deliverables provided under this contract in accordance with FAR Clause 52.227-14, Rights in Data. These rights include, but are not limited to, the right to use, disclose and reproduce applicable contractor work product (e.g., documentation, software code, processes and procedures, best practices). The Library has the right to share contractor work product with other contractors for future solicitation and/or contract purposes.
C.14. STAFFING AND KEY PERSONNEL
The following personnel have been identified as Key Personnel in the performance of this contract:
030ADV24R0008 Page 12 of 13
Labor Category Minimum Qualifications 0BProject Manager – Key 1BResponsible for coordinating overall team/project activities, maintaining project documentation, tracking deliverables and financial information
2B- US Citizenship 3B- BA/BS degree or 4 years of project management experience with electronic security system operational support on systems of similar size and complexity
4BTechnology Specialist – Key 5B(Qty 2)
6B- US Citizenship 7B- Software House C-Cure 9000 advanced certification at integrator level 8B- Intellicene Video Management System VMS training certifications for installers 9B- 10 years supporting an enterprise level integrated security system of comparable size and complexity 10B- 5 years experience supporting High Availability Software - Configuration of applications, which provide high availability and fault tolerance. Examples: AAM/Replistore/Marathon, ARCServ.
11B- 5 years experience with Virtualization (VM Ware environment) -includes the configuration of VSphere and the management of ESX Host servers, virtual machines, virtual networking.
12BSupervisory Technician - Key 13B- US Citizenship 14B- 4-year Apprentice Program in Electronics or Communications OR an Associate degree in Electronics, Communications, or Graduate of Military Class A and/or B school in Electronics or Communications 15B- Software House C-Cure 9000 advanced certification at integrator level 16B- Intellicene Video Management System VMS training certifications for installers
Before replacing any individual designated as Key Personnel by the Government, the Contractor shall notify the Contracting Officer no less than 15 business days in advance, submit written justification for replacement, and provide the name and qualifications of any proposed substitute(s). All proposed substitutes shall possess qualifications equal to or superior to those of the Key person being replaced, unless otherwise approved by the Contracting Officer. The contractor shall not replace Key Contractor personnel without approval from the Contracting Officer.
030ADV24R0008 Page 13 of 13
C.15. TRANSITION
The Library will require a transition period to occur at the beginning and end of the IESS maintenance support contract from the incumbent contractor to the newly awarded contractor. Based on funds availability, the Library plans to provide four weeks overlap between contractors to review open issues, provide any outstanding documentation, and to go over procedures to include reporting formats and any applicable SOPs or training guides.
The incumbent contractor will provide support until the new contractor has access to Library systems and has conducted an initial meeting with Library personnel to review outstanding issues. After that point, the newly awarded contractor will perform required IESS maintenance support and the incumbent contractor will perform contract closeout activities under their respective contract, including returning any government furnished property and information to the Library. The project manager for the incumbent contractor shall be available for questions until the end of its period of performance.
The contractor shall submit a transition plan with its initial proposal and the COR will provide feedback to the contractor upon contract award. Any comments or questions regarding the transition plan shall be resolved between the parties within 10 days after award, after which the contractor shall adhere to the agreed upon transition schedule.
PERIOD OF PERFORMANCE:
CLIN Description PoP 0001 PSN Operations & Maintenance 09/15/2024 – 09/14/2025 0002 Install IT Hardware 09/28/2024 – 09/27/2025 0003 IESS Operations and Maintenance 09/15/2024 – 09/14/2025 0004 Replace 300 Analog Cameras 09/28/2024 – 09/27/2025
ATTACHMENTS
Identifier
Title
Date
Number of Pages
J-4 IESS System Components Workbook 03/08/2024
1 Excel Workbook w/ 9 embedded worksheets
J-5 ITS 5-410.1 03/29/2019 145 pages
| C.1. OVERVIEW / BACKGROUND: |
| The Library of Congress (Library) Security and Emergency Preparedness Directorate (SEPD) operates the Physical Security Network (PSN) supporting the Library’s Integrated Electronic Security System (IESS). |
| The IESS consists of the Primary Intrusion Detection System (PIDS) and the Security Video Management System (SVMS). Functionally, PIDS provides alarm monitoring and processing, ID badge making, and card reader control to spaces and consists of card r... |
| The Library requires operations and maintenance (O&M) support of the IESS and PSN. |
| - Software House C-Cure 9000 advanced certification at integrator level |
| C.2. SCOPE |
| The contractor shall provide all required services and technical expertise to secure an uninterrupted and fully functional IESS & PSN. The contractor must provide real-time availability, visibility, timely incident resolution, and risk mitigation of ... |
| C.3. REQUIREMENTS |
| The contractor shall provide preventative maintenance, emergency repair, installation, and inventory services to maintain a fully functional IESS & PSN, including the purchase of materials and parts in accordance with the IESS IDIQ contract. Refer to... |
| 3.1. CLIN 0001 Physical Security Network (PSN) Operations & Maintenance |
| 3.1.1. The contractor shall provide preventative maintenance, emergency repair, installation, and inventory services to maintain a fully functional Integrated Electronic Security System (IESS), including the purchase of materials and parts. |
| 3.1.2. The contractor shall monitor planned obsolescence of the IESS hardware and software components as part of uninterrupted preventative maintenance and lifecycle replacement activities. Specifically, the contractor must exercise the technical exp... |
| 3.1.3. The contractor shall prioritize the replacement of components that may be impacted by end-of-life products where the manufacturer is no longer offering technical support for those products. Outdated and unmaintainable solutions place the Libra... |
| - US Citizenship |
| Project Manager – Key |
| - BA/BS degree or 4 years of project management experience with electronic security system operational support on systems of similar size and complexity |
| - Intellicene Video Management System VMS training certifications for installers |
| - 4-year Apprentice Program in Electronics or Communications OR an Associate degree in Electronics, Communications, or Graduate of Military Class A and/or B school in Electronics or Communications |
| - US Citizenship |
| Supervisory Technician - Key |
| - 5 years experience with Virtualization (VM Ware environment) - includes the configuration of VSphere and the management of ESX Host servers, virtual machines, virtual networking. |
| - 5 years experience supporting High Availability Software - Configuration of applications, which provide high availability and fault tolerance. Examples: AAM/Replistore/Marathon, ARCServ. |
| - 10 years supporting an enterprise level integrated security system of comparable size and complexity |
| - Intellicene Video Management System VMS training certifications for installers |
| - Software House C-Cure 9000 advanced certification at integrator level |
| (Qty 2) |
| Technology Specialist – Key |
| - US Citizenship |
| Responsible for coordinating overall team/project activities, maintaining project documentation, tracking deliverables and financial information |
| 3.1.4. The contractor shall ensure all replacement parts are of the same or equivalent make and model as the component requiring replacement. If a product is beyond the manufacturer’s support time frame, the contractor shall recommend a suitable repl... |
| 3.1.5. The contractor shall provide hardware, licenses, and peripherals as outlined in C.3.2. |
| 3.1.6. The contractor shall specify an estimated date, noting that it is an estimated end-of-support date. This information must be provided in writing to the COR at the time of award. Updates to the end-of-support date(s) must be provided. |
| 3.1.7. The contractor must notify the COR immediately upon discovery and significantly in advance of any potential obsolescence or end of life to IESS hardware and software components. The contractor is responsible for reporting to the COR when it is... |
| 3.1.8. The contractor may be required to provide unscheduled or emergency installation services and shall comply with Library IT processes and ticketing procedures to schedule installation services and to obtain necessary approvals to perform required... |
| 3.1.9. The contractor must provide, implement, and maintain a Preventative Maintenance (PM) Plan. The PM is based on the task, frequency, or corrective action. The PM must include all IT systems and software associated with the IESS. At a minimum, th... |
| 3.1.9.1. A schedule for all IT infrastructure components to include but not limited to Servers, Workstations, Network devices etc. in the Library, which addresses installation of patches and/or fixes for all computers and field panels at all locations. |
| 3.1.9.2. Technical roadmap for execution of the preventative maintenance plan. |
| 3.1.9.3. Faults and failures found during PM shall be documented and reported to the COR, to include corrective actions taken/to be taken. Degradation from baseline should be reported to the COR. |
| 3.1.9.4. Annual power outages testing (shutdown and recovery) by the AOC at the Library (three tests of generator-systems and one test of the Uninterruptible Power Supply (UPS)). |
| 3.1.9.5. Contractor shall perform configuration audits to ensure equipment is located in accordance with diagrams and functioning properly. A configuration audit is an inventory of hardware, software, drawings and technical documentation and is a func... |
| 3.1.9.6. As part of a continuous and uninterrupted IESS, the contractor must resolve incidents on a timely basis. “Timely” is defined by the level of priority to address any obstacles to IT systems that may prevent the Library from conducting normal o... |
| 3.1.9.7. For other unique scenarios where emergency access is limited or restricted, the contractor must notify and consult with the COR for specific technical direction within 15 minutes of being notified of the incident. |
| 3.1.10. The contractor shall provide a plan that addresses the following: |
| 3.1.10.1. Migration plan and support the PSN IT infrastructure from the Jefferson and other non-datacenter locations into the Technical Operations Center (TOC). |
| 3.1.10.2. A plan to re-design critical PSN devices to address open IT security vulnerabilities. The plan must outline newly identified and existing vulnerabilities with recommended resolution. |
| 3.1.10.3. A plan outlining the schedule of quarterly patching reviews, user account maintenance, software updates, firmware, and life cycle analysis, security and auditing. |
| 3.1.11. Contractor shall support added items as they are installed under CLIN 0004. |
| 3.1.12. The contractor shall perform preventative maintenance quarterly and when required by ITSG in accordance Information Technology Security Directive 5.410.1 (Attachment J-5_ITSG_SD_5-410-1.pdf) |
| 3.1.13. The contractor shall comply with the Library Hardening guides that are furnished after contract award. |
| 3.1.14. The contractor shall provide continuous monitoring support of the Video Management System (VMS) and Primary Intrusion Detection System (PIDS) Application Systems, this includes conducting root cause analysis to identify if any servers, storage... |
| 3.1.15. The contractor shall ensure support for all new or upgraded hardware and software shall be included as part of IESS Routine and Preventative Maintenance Services/Management of Third Party Support. |
| 3.1.16. As the certified service provider of the Library’s continuous and hardware support agreements, the contractor must actively monitor software releases from the software manufacturers that provide applications in support of the IESS. When a new ... |
| 3.1.16.1. Maintain and make available all appropriate service/support agreements/licenses for software and hardware support. |
| 3.1.16.2. Make available fixes, patches, and updates for identified software. |
| 3.1.16.3. Test updates in an environment to simulate issues that may arise in production. |
| 3.1.16.4. Coordinate with manufacturers and support on-site certification visits, if required. |
| 3.1.17. The contractor shall provide a report identifying backup meta data for the system and participate in annual Disaster Recovery exercises conducted by OCIO team. |
| 3.1.18. The contractor shall deliver reports, with detail documentation for discussion and analysis delivered in formats defined in C.11 or other format if approved by COR. Due date for reports shall be as designated in SOW C.5. |
| 3.1.18.1. Monthly reports with a cover page calling out action items and overdue deliverables. Monthly report shall document all tasks completed, projects in process, projects on hold, actions required from Library/Contractor, blockers, and general st... |
| 3.1.18.2. Weekly reports with a front section calling out action items and blockers. Weekly report shall document tasks completed and active tasks with accomplishments and next steps planned for the week. |
| 3.1.18.3. All written deliverables must be of a professional quality; free of grammatical and spelling errors; accurate in presentation, technical content, and adherence to accepted elements of style; clear & concise; and consistent with the requireme... |
| 3.2. CLIN 0002 Install IT Hardware |
| 3.2.1. The contractor shall procure, test, and install the following equipment in the table below. Install services will be provided and invoiced following successful testing, the contractor shall update baseline configuration documents accordingly. R... |
| 3.3. CLIN 0003 IESS Operations and Maintenance |
| 3.3.1. The contractor must describe preventative maintenance tasks for each system component and software application. The contractor is required to evaluate event data from the service location to identify potential issues that have not been reporte... |
| 3.3.2. The contractor will use service tickets to schedule preventative maintenance tickets repetitively. A ticketing process must be used to track resolution to resolve incidents actively and regularly upon discovery of potential failures. The cont... |
| 3.3.3. Security Equipment Maintenance Cadence |
| 3.3.3.1. Library Collections |
| The Library’s Collections are tiered by risk and the required maintenance schedule will reflect this. The required preventative maintenance activity for each collection level is listed below. |
| 3.3.3.2. All Other Areas |
| For non-collection areas, the contractor shall perform scheduled maintenance on the system based on the following: |
| 3.3.3.3. Daily Performance Checks |
| In addition to the PM activity specified above, the contractor shall perform daily functional performance checks. The intent of these checks is to verify the video management system and the PIDS system components are operating as designed. Examples ... |
| All servers supporting VMS and PIDS are operating within recommended limits for available memory resources. |
| All cameras are sending video streams and being recorded. |
| All security panels have data connectivity to the server and operating in accordance with the manufacturer’s specifications. |
| The contractor shall develop a method to identify system and connected device (edge) failures, whether intermittent or catastrophic. Additionally, these checks should be used to evaluate overall performance deficiencies and anomalies. Failures or p... |
| 3.3.4. Emergency (unscheduled) repair times |
| 3.3.5. Door Hardware |
| The contractor will be required to support new and existing installations on doorways equipped with door hardware maintained by the building owner, (AOC). The contractor shall support the equipment monitoring the device signal starting at the output... |
| Automatic Door Openers |
| Delayed Egress Devices (e.g. maglock or delayed panic egress bar) |
| Storefront Style Doors with Electrified Vertical Rods |
| Electrified Strikes and Lock Sets Inside Building Perimeter |
| Motorized Overhead Doors |
| Secure Storage Facility Locking Hardware |
| 3.3.6. Unscheduled and Emergency Support |
| 3.3.6.1. Acceptance and Response |
| The contractor shall provide a means to receive requests for service or repair from the following: (1) Library staff and contractors, (2) United States Capitol Police (USCP), (3) House of Representatives and Senate staff or members of Congress, (4) Ar... |
| Service will include account management support such that devices and/or systems malfunction will be addressed per the restoration table. |
| 3.3.7. Baseline Configurations and Build Books |
| The contractor shall provide and maintain the Baseline Configuration documentation and Build Books for the IESS system. The contractor must document the step-by-step procedures in the build book for a qualified system administrator to install and conf... |
| For the software service agreements, the contractor must manage the software title and patch level and all other critical system settings required to rebuild the system. Separate books are required for each major system and subsystem. This includes ... |
| The Baseline Configuration shall include information critical to configuring the Physical Security Network servers, data switches and mass storage devices. |
| Preventative Maintenance by Location |
| 3.3.8. Maintain “As-Built”/Engineering Drawing Set |
| Contractor shall maintain the set of engineering drawings which document the signal flow between system components, physical location of all devices, and riser diagram of security panels. The background Computer Aided Design information for the base b... |
| 3.4. CLIN 0004 Replace 300 Analog Cameras |
| The contractor shall procure IP cameras and replace analog technology cameras with “IP” cameras identified in the table below. |
| Camera Locations”. Installation shall be prioritized as follows: |
| 1. Capitol Hill complex (Madison, Jefferson & Adams buildings) Cameras |
| 2. Priority sequential order (“1” before “2” and “2” before “3”). |
| The contractor shall validate locations of camera and BOM requirements noted in table below. The contractor shall assume the following applies for installation purposes: |
| The contractor shall develop a Project Installation Program of Actions and Milestones (POAM) for this task order, including data reports, which can be modified as necessary. However, any modifications or updates to the POAM require acceptance by the C... |
| C.4. CONTRACT PERFORMANCE |
| 4.1. Contractor Personnel Roster |
| To provide badges and verify the suitability of contract staff, the contractor shall provide to the Library’s COR a roster of personnel, with resumes, who will be performing services. The COR will review the qualifications of proposed staff before app... |
| 4.2. Issue Tracking System |
| To meet the minimum IESS maintenance, upgrade, and enhancement tracking system prioritization and incident response requirements, the contractor must provide a web-based incident and resolution tracking/work order system or equivalent method for track... |
| The contractor must provide access to the incident and resolution tracking system for the COR and designated Library staff to review data, initiate and check the status of corrective and preventative repairs, and generate reports. The contractor must ... |
| C.5. SCHEDULE OF EVENTS/DELIVERABLES |
| C.6. OTHER REQUIREMENTS |
| 6.1. Coordination with System Administrator |
| The Government’s Applications Administrator (the System Business Owner, SEPD Protective Services Division Chief) will provide any necessary programming of the C-Cure system as suggested by the contractor in support of this effort. The contractor shal... |
| 6.2. Coordination with Custodial Division Personnel and USCP |
| The contractor shall work with the COR to schedule access to non-public/non-SEPD-controlled areas. This coordination will be made with a COR-designated Library space owner and the USCP Library Division Police Supervisor to minimize disruption of Libra... |
| C.7. PROJECT SCHEDULE/INSTALLATION SCHEDULE |
| Any work affecting the normal operation of the Library shall be performed outside of normal business hours. Normal business hours for this task order are defined as 8:00 AM to 8:00 PM Monday through Friday, excluding Federal Holidays and unscheduled t... |
| C.8. PLACE OF PERFORMANCE |
| Refer to the IDIQ locations of performance. |
| C.9. HOURS OF OPERATION |
| Hours of operation are specified in the IDIQ |
| C.10. GOVERNMENT FURNISHED PROPERTY |
| The Library will provide access to systems, facilities, and information as required for the contractor to fulfill the requirements of this contract. |
| C.11. DOCUMENTATION |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .