N6449821C4000 P00006_FE_30 Sept 2025.pdf
PDF 366 KB Posted
- Attached to
- N6449821C4000 Scope Increase
- Solicitation number
- N6449821C4000P00006
About this file
This document is a contract modification for the Naval Surface Warfare Center Philadelphia Division's Integrated Surveillance Equipment Environment (ISEE) contract with Fiber Business Solutions Group Inc. The modification increases the contract ceiling by $746,265.10, raising the total contract value from $2,899,287.36 to $3,615,261.50. It adds funded Contract Line Item Numbers (CLINs) 0020 through 0025 and Option CLIN 0026, with funding of $715,974.14 obligated for work across multiple buildings.
The modification involves installing and integrating surveillance equipment across various buildings at the Navy Yard in Philadelphia, including Buildings 1000, 87, 77H, 77L, 29, 633, 4, and 662T. Key requirements include installing Power-over-Ethernet cameras, access control systems, balanced magnetic switches, panic buttons, and upgrading existing security infrastructure. The work includes creating a centralized command station, implementing networked motion detection, ensuring continuous power supply, and meeting specific technical requirements for image quality, encryption, and system performance. The period of performance runs from September 30, 2025, to May 5, 2026.
View the file
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
NAVAL SURFACE WARFARE CENTER PHILA
CODE 0232, KELLY NOLAN
267-990-6183, KELLY.M.NOLAN@NAVY.MIL
5001 SOUTH BROAD STREET
PHILADELPHIA PA 19112
SEE SCHEDULE
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this modification is to:
1. Additional ceiling and in-scope changes are hereby approved in the amount of $746,265.10.
2. Add funded CLINs 0020 through 0025 and Option CLIN 0026. As such, funding in the amount of $715,974.14 for CLINs 0020-0025 has been obligated via this modification.
3. Update the Performance Work Statement to add in scope w ork additions (3.12.9 through 3.12.15).
All other terms and conditions remain unchanged.
1. CONTRACT ID CODE PAGE OF PAGES
1 28
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code)
9B. DATED (SEE ITEM 11)
X N6449821C4000
10B. DATED (SEE ITEM 13)
X
9A. AMENDMENT OF SOLICITATION NO.
05-May-2021
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required) See Schedule
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
X D. OTHER (Specify type of modification and authority) Mutual Agreement of the Parties.
E. IMPORTANT: Contractor is not, X is required to sign this document and return 1 copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
30-Sep-2025
CODE
NAVAL SURFACE WARFARE CENTER PHILA
CODE 0243, KRISTEN CELLA
KRISTEN.M.CELLA.CIV@US.NAVY.MIL
5001 SOUTH BROAD STREET
PHILADELPHIA PA 19112
N64498 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE N64498
FIBER BUSINESS SOLUTIONS GROUP INC
G FORCE
ENNIO BRUNO
3019 W GERMANTOWN PIKE
NORRISTOWN PA 19403-1002
FACILITY CODE523Z5CODE
EMAIL:TEL:
Modification Control Number: cellakrm251560
Cynthia T. Gallo, President
09-30-2025 Cynthia T.
Gallo
Digitally signed by Cynthia T. Gallo Date: 2025.09.30 15:23:02 -04'00'
09/30/2025
P00006
N6449821C4000 (cellakrm251560)
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
The following items are applicable to this modification:
SUMMARY OF CHANGES
SUMMARY OF CHANGES
SECTION A - SOLICITATION/CONTRACT FORM
The total cost of this contract was increased by $715,974.14 from $2,899,287.36 to $3,615,261.50.
SECTION B - SUPPLIES OR SERVICES AND PRICES
CLIN 0020 is added as follows:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0020 1 Lot $171,780.72 $171,780.72 Building 1000
FFP
IAW PWS Section 3.12.9 FOB: Destination
PURCHASE REQUEST NUMBER: 1301293856
PSC CD: N063
NET AMT $171,780.72
ACRN AF
CIN: 130129385600001
$171,780.72
CLIN 0021 is added as follows:
0021 1 Lot $162,159.90 $162,159.90 Building 87
FFP
IAW PWS Section 3.12.10 FOB: Destination
NET AMT $162,159.90
$162,159.90
CLIN 0022 is added as follows:
0022 1 Lot $257,762.40 $257,762.40 Building 77H, 77L
FFP
IAW PWS Section 3.12.11 FOB: Destination
NET AMT $257,762.40
$257,762.40
CLIN 0023 is added as follows:
0023 1 Lot $105,435.00 $105,435.00 Building 29
FFP
IAW PWS Section 3.12.12 FOB: Destination
NET AMT $105,435.00
$105,435.00
CLIN 0024 is added as follows:
0024 1 Lot $16,792.88 $16,792.88 Building 633
FFP
IAW PWS Section 3.12.13 FOB: Destination
NET AMT $16,792.88
$16,792.88
CLIN 0025 is added as follows:
0025 1 Lot $2,043.24 $2,043.24 Building 4
FFP
IAW PWS Section 3.12.14 FOB: Destination
NET AMT $2,043.24
$2,043.24
CLIN 0026 is added as follows:
0026 1 Lot $30,290.96 $30,290.96 OPTION Building 662T
FFP
IAW PWS Section 3.12.15 FOB: Destination
NET AMT $30,290.96
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
The following have been modified:
PERFORMANCE WORK STATEMENT
Performance Work Statement (PWS) for Integrated Surveillance Equipment Environment (ISEE)
1.0 INTRODUCTION
1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 105, Security Office, which is responsible for providing security-related services and expertise to NSWCPD operations.
1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied
1.0.3 Government / Contractor Relationship
a). The services to be delivered under this Contract are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Contract between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.
b). The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.
c). Contractor personnel under this Contract shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or
DFARS Subpart 207.5.
d). Employee Relationship:
1) The services to be performed under this Contract do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government.
Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.
2) Rules, regulations, directives, and requirements that are issued by the U.S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.
e). Inapplicability of Employee Benefits: This Contract does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.
f). Notice. It is the Contractor's, as well as the Government's, responsibility to monitor Contract activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.
1) The Contractor shall notify the Contracting Officer in writing via letter or email within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the Contractor's estimated date when, absent a response, cost, schedule or performance will be impacted.
2) The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:
(i) Confirm the conduct is in violation and when necessary direct the mode of further performance,
(ii) Countermand any communication regarded as a violation,
(iii) Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or
(iv) In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.
1.1 BACKGROUND
NSWCPD consists of approximately 3000 personnel located within multiple buildings across the 1200-acre campus at The Navy Yard located in Philadelphia, Pennsylvania. There is a need for an Integrated Surveillance Equipment Environment (ISEE) to monitor activity within and surrounding the buildings that are part of the Command.
Each NSWCPD-building has a unique footprint and is utilized as office space, lab space, a test-site, storage or a combination thereof. Therefore, the wiring and configuration of each space varies from building to building.
Regardless of each building’s use, the ISEE is to enable each equipped building to:
a) Record images at the specified locations, and transmit the information back to the Control Room.
b) Support networked motion detection
c) Utilize Uninterruptable Power Supplies (UPS) to ensure continuous availability; the UPS shall ensure availability of at least 24 hours after disconnection from a power source.
The implementation of the ISEE System will occur in a phased approach. Generally, Phase I will encompass the creation of a Command-Station-Control-Room, and connection of one closed-loop subsystem/node of ISEE. The subsequent Phases will include the installation of additional nodes of ISEE across the NSWCPD campus that integrate into the ISEE.
1.2 SCOPE OF WORK
The Contractor shall support NSWCPD in the following areas:
a) CLIN 0001 - Command Station (Building 29), one closed-loop subsystem;
b) CLIN 0002 - Training Support
Option Tasks- CLIN 0003 - Complete Node 2 (Building 4, Building 1032, and the parking areas associated with each building)
a) CLIN 0004 - Complete Node 3 (“77 Complex” which consists of Buildings 77L, 87, 756, 670, 776, 779, and 771 as well as all the associated courtyards and parking areas in between and adjacent to each building)
b) CLIN 0005 - Complete Node 4 (Building 1000, Building 1055, and the parking areas associated with each building)
c) CLIN 0006 - Complete Node 5 (Building 542, its fenced area, and the parking areas associated with the building)
d) CLIN 0007 - Complete Node 6 (“633 Complex” which consists of Building 633 and the parking areas associated with each building)
e) CLIN 0008 - Maintenance Support for ISEE – Years 1-5
f) CLIN 0009 - Spare Parts
g) CLIN 0010 - Technical Data
2.0 APPLICABLE DOCUMENTS
2.1. Blueprints and existing wiring diagrams of the NSWCPD-buildings
2.2. National Electrical Code (NEC)
2.3. Technical Specifications for Construction and Management of Sensitive Compartment Information Facilities ICD 705 26 September 2015
2.4. UFC 4-020-01 DOD Security Engineering Facilities Planning Manual, Sep 08
2.5. UFC 4-021-02NF Unified Facilities Criteria Electronic Security Systems
2.6. UL 2050 Standard for National Industrial Security Systems
2.7. NFPA 70 National Electrical Code, latest edition.
2.8. National Electrical Safety Code, latest edition.
2.9. MIL-STD-100E, Engineering Drawing Practices
2.10. DoD 8570.01-M Information Assurance Workforce Improvement Program
2.11. DoD 8140.01 Cyberspace Workforce Management requirement
2.12. DoD Risk Management Framework regulation 8510.01, 12 March 2014
2.13. DoD Manual 5200.01 Volume 3 - DOD Information Security Programs
2.14. OPNAVINST 5100.23G, Navy Occupation Safety and Health Program Manual
2.15. OPNAVINST 5530.14E Navy Physical Security and Law Enforcement Program 23 Sept 2014
2.16. SECNAV M-5510.36B Department of Navy Information Security Program
2.17. SPAWARSYSCEN Shore Installation Process Handbook 5200.28
2.18. Applicable O&M Manuals per Applicable Manufacturer Equipment
2.19. Country and local codes
2.20. Fiber Backbone of Address, Warning, and Relay (AWARE) Announcement System
For access to 2.1, a proper chain-of-custody must be followed. To initiate the request, contact, Brian Valenti brian.valenti@navy.mil.
The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.
3.0. REQUIREMENTS
3.2 COMMAND STATION (CLIN 0001 - Building 29 and its parking lot) - Phase I consists of the development, installation, and establishment of the first Node of the ISEE; this consists of the creation of a Command-Station- Control Room to allow for a centrally-managed-view of all visual surveillance footage within the ISEE, and for the installation of networked equipment (networked equipment includes the utilization of pre-existing equipment, when appropriate). The completion of these tasks will establish the Command Station of the ISEE, capable of addressing any other installed Nodes. This Command Station is where the control and operation of all surveillance of NSWCPD-buildings occurs. To support the development of the Command Station, the Contractor shall meet or exceed the following requirements:
3.1.1 Command-Station-Control-Room – This Control Room shall monitor (as a supervised-system) and operate surveillance equipment in the manner in which the designated operator(s) choose(s). This Control Room shall act as the Command Station for all Nodes, current and future.
3.1.1.1 Customizable/Programmable –
3.1.1.1.1 Point-to-Multi-Points – The Command-Station-Control-Room shall possess the ability to not only access information within the building from which it is located, but also to any combination of buildings connected to the Fiber Backbone; latency shall be no longer than 1 second from Command Station to any combination of buildings connected to the Fiber Backbone. The Fiber Backbone refers to Applicable Document 2.20 above.
3.1.1.1.1.1 At a minimum, the System shall allow for at least six (6) (i.e. Nodes) Point-to-Multi-Point connections.
3.1.1.1.1.2 The System shall be expandable to allow for efficient connection of additional Points/Nodes to be included in this functionality; System shall allow for at least three (3) additional Points/Nodes as part of an expansion.
3.1.1.1.2 Building Notifications – Contractor shall develop the ISEE to deliver messages/signals from Nodes to the Command-Station-Control-Room in accordance with programmed prompts set by the operator of the Control Room (e.g. pop-up screens triggered by motion-detected activity, scheduled rotating displays at set intervals, etc.).
3.1.1.1.3 Recording – The System shall have the ability to record all the time for every connected input, but also be programmable to record only at the set intervals designated by the operator of the Control Room;
3.1.1.1.3.1 Motion-detected Activation - for areas set to record only during motion-detected-activated events, video footage shall be available and recorded/saved for at least a 10-second duration prior to the motion-detected-activated event.
3.1.1.2 Monitoring/supervised-system - Each Node shall utilize supervised loops / wiring to ensure the integrity of the surveillance system. The Command-Station-Control-Room shall prominently signal outages within the ISEE, and the notifications shall be sent immediately (real-time) after time of outage(s).
3.2.1.2.1 Domain Control – At minimum, the System shall allow for the following:
3.2.1.2.1.1 Active Directory Domain Services
3.2.1.2.1.2 BitLocker Drive Encryption Administration Utilities
3.2.1.2.1.3 IP Address Management (IPAM) Management Tools
3.2.1.2.1.4 Remote Access
3.2.1.2.1.5 Remote Desktop Services
3.2.1.2.1.6 Server Manager
3.2.1.2.1.7 Windows Server Update Services Tools
3.1.1.3 Graphical User Interface (GUI) – The GUI shall feature a programmable-selected-input of any of the visual inputs of ISEE. Additionally,
3.1.1.3.1 Contain a display setting to represent all the visual inputs of ISEE within a Node, as well as the connections to other Nodes around the NSWCPD campus.
3.1.1.3.2 Campus-view – contain a setting to view all external (i.e. outside buildings) surveillance, and be customizable regarding the number of simultaneous displays on monitor(s).
3.1.1.3.3 Rolling-displays – Be programmable to allow for customization of the sequence, timing, and duration of every input of ISEE for display within the Control Room.
3.1.1.3.4 Motion-Detected Activation - Subject to other tailored programming by an operator, allow for any motion-detected-activated event to automatically activate/trigger the next two closest Inputs to pop-up on the Command-Station-Control-Room’s display to show a broader field of view around the triggering event.
3.1.1.3.5 Hierarchy of Commands – The interface shall be intuitive to a reasonable person, and allow for the quickest possible operation.
3.1.1.3.6 Operation of Unit – Contractor shall support use of Touch Screen-functionality and/or Buttons.
3.1.1.4 Capacity - The Control Room shall utilize H.265+ (or better) compression technology, and allow for storage of footage for all connected ISEE inputs for 720 consecutive hours prior to any need for overwrite.
3.1.2 Command-Station-Node – first closed-loop subsystem of ISEE
3.2.2.1 Access-point Connections - The Contractor shall:
3.1.2.1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.1.2.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc.
are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.1.2.2 Connections/Communication (To-and-from the Command-Station-Control-Room) – Information shall be delivered via Power-Over-Ethernet connections.
3.1.2.2.1 Connectivity - The ISEE System shall be operational 24/7; UPS (to ensure availability of at least 24 hours after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.1.2.2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.1.2.2.3 Latency - latency shall be no longer than 1 second from any input to the Command- Station-Control-Room.
3.1.2.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.1.2.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended from all inputs to the Command-Station-Control-Room, and maintain continuous availability. Contractor shall deliver As-Built Design drawing package to document the layout in accordance with CDRL A005, a Certificate of Conformance to attest to its work in accordance with CDRL A006, and a Warranty Performance Report in accordance with CDRL A007 to identify warranted items/systems.
3.1.2.3 Inputs – Surveillance points that capture visual information to relay back to the Command-Station- Control-Room
3.1.2.3.1 Design Efficiency – Contractor shall limit the amount of unique types of equipment required to execute the requirements of this PWS; types of cameras, servers, monitors, wiring, brackets, etc. shall be kept to a minimum.
3.2.2.3.2 Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1.
3.1.2.3.3 Visual Signature/Size Limitations/Casing – The cameras that comprise the Node shall compliment the walls/structures they are mounted to, and be non-obtrusive. Field Equipment shall be suitable for the environment for which it is being installed (e.g. equipment located within office areas shall protect against unwarranted tampering, and industrial areas may utilize industrial-style weather-sealed equipment and be in-conduit).
3.1.2.3.4 Image Quality - Capture color images in no less than 5 megapixel resolution; for night-time surveillance, Input shall be able to capture decipherable footage for a distance of at least 100 feet.
3.1.2.3.5 Recording – be enabled to continuously capture footage to be stored for at least 720 consecutive hours
3.1.2.3.6 Be enabled with motion-detection that allows for adjustment of the sensitivity of activation
3.1.2.3.7 Synchronization – All Inputs shall be synchronized with the Main Server’s timing to ensure uniform reporting and timestamping of activities; synchronization shall occur daily at a time that causes the least disruption to the System.
3.1.2.3.8 Protection – All Inputs and their associated wiring shall be installed in conduit appropriate for the environment for which they are placed – Inputs and wiring installed within buildings shall be protected from tampering and hazards; Inputs and wiring outside of buildings shall be protected from tampering, hazards, and weather-elements.
3.1.2.4 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1,) to feature a programmable-selected-input of any of the visual inputs of ISEE as designated by the Control Room.
3.3 TRAINING SUPPORT (CLIN 0002)– The ISEE System shall include documentation on its design, components, operation, and maintenance. The Contractor shall provide the following:
3.3.1 Manual – Develop and deliver a technical manual that specifies the ISEE System’s overall design, components/subsystems, proper use and operation, and scheduled maintenance to keep the system performing at its intended levels; the manual shall also include video tutorials covering the aforementioned topics. The Manual shall be developed and delivered in accordance with CDRL B001.
3.3.2 Operation Training - The Contractor shall foster active student engagement through the use of both hands-on demonstrations and activities, all designed to improve students’ proficiency with using the ISEE System. This hands-on training shall be conducted and demonstrated on the fully-operational Command Station and/or Complete Node of the ISEE System.
3.3.2.1 This class shall provide thorough instruction in the following subject areas:
a) Explanation of the design of the ISEE System
b) Explanation and identification of the major components of the ISEE System (i.e. Command
Station, Complete Node with all the associated subcomponents)
c) Handling of documentation and Technical Manual(s)
d) Identifying and troubleshooting minor faults
e) Execution of preventive maintenance tasks
f) Hands-on operation training (utilizing the completed Command Station and/or Complete Node)
3.3.2.2 Contractor shall also address common recurring issues and good engineering practices within each area stated at 3.2.2.1.
3.3.2.3 Contractor shall make this course available for enrollment upon completion of the tasks stated within Sections 3.1; the exact start date will be coordinated with the Government POC after contract award.
3.3.2.4 Duration – it is anticipated that less than 8 hours is necessary to properly train students on the topics cited at Section 3.6.2.1. Proposed courses designed to be longer in duration shall cite the reasonable circumstances requiring an extended timeframe, and submit the plan to NSWCPD for consideration.
3.3.2.5 Capacity – Contractor shall plan to train approximately 50 NSWCPD-personnel on the topics cited at Section 3.2.2.1.
3.3.2.6 Training Materials – Contractor shall deliver all the course material in accordance with CDRL A008.
3.4 ADDITIONAL COMPLETE NODE FOR ISEE (CLIN 0003) (Node #2, which consists of Building 4, Building 1032, and the parking areas associated with each building) – This consists of the installation of Inputs for the building and parking areas, and connection of this complete subsystem to the ISEE to allow for the dissemination of surveillance information within the selected building back to the Command Station. To support the development of a Complete Node, the Contractor shall meet or exceed the following requirements:
3.4.1 Access-point Connections - The Contractor shall:
3.4.1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.4.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc. are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.4.2 Connections/Communication (within Node) – Information communicated within the Node shall be delivered to over POE connections.
3.4.2.1 Connectivity - The ISEE shall be operational 24/7; UPS (to ensure availability of at least 24 hours in standby mode, and at 24 hours of active usage after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.4.2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.4.2.3 Latency - latency shall be no longer than 1 second from receipt of signal from the Control Unit until the start of the delivery of the received message.
3.4.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.4.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended and maintain continuous availability. Contractor shall deliver an As-Built Design drawing package in accordance with CDRL A005, a Certificate of Conformance to attest to its work in accordance with CDRL A006, and a Warranty Performance Report in accordance with CDRL A007 to identify warranted items/systems.
3.4.3 Inputs – Surveillance points that capture visual information to relay back to the Control Room.
Contractor shall:
3.4.3.1 Coverage - Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.4.3.2 Consistency of Equipment – Utilize the same type of equipment used to satisfy the requirements of Section 3.1.2.3 so that the number of unique parts can be kept to a minimum to limit variation of usage, operation, and maintenance. Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
Visual Signature/Size Limitations – The cameras that comprise the Node shall compliment the walls/structures they are mounted to, and be non-obtrusive. Field Equipment shall be suitable for the environment for which it is being installed (e.g. equipment located within office areas shall protect against unwarranted tampering, and industrial areas may utilize industrial-style weather-sealed equipment).
3.4.3.3 Synchronization – All Inputs shall be synchronized with the Main Server’s timing to ensure uniform reporting and timestamping of activities.
3.4.3.4 Protection – All Inputs and their associated wiring shall be installed in conduit appropriate for the environment for which they are placed – Inputs and wiring installed within buildings shall be protected from tampering and hazards; Inputs and wiring outside of buildings shall be protected from tampering, hazards, and weather-elements.
3.4.4 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1, to feature a
3.5 ADDITIONAL COMPLETE NODE FOR ISEE (CLIN 0004) (Node #3, referred to as the “77 Complex” which consists of Buildings 77L, 87, 756, 670, 776, 779, and 771 as well as all the associated courtyards and parking areas in between and adjacent to each building) – This consists of the installation of Inputs for the building and parking areas, and connection of this complete subsystem to the ISEE to allow for the dissemination of surveillance information within the selected building back to the Command Station. To support the development of a Complete Node, the Contractor shall meet or exceed the following requirements:
3.5.1 Access-point Connections - The Contractor shall:
3.5.1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.5.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc. are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.5.2 Connections/Communication (within Node) – Information communicated within the Node shall be delivered to over POE connections.
3.5.2.1 Connectivity - The ISEE shall be operational 24/7; UPS (to ensure availability of at least 24 hours in standby mode, and at 24 hours of active usage after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.5 2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.5.2.3 Latency - latency shall be no longer than 1 second from receipt of signal from the Control Unit until the start of the delivery of the received message.
3.5.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.5.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended and maintain continuous availability. Contractor shall deliver an As-Built Design drawing package in accordance with
3.5.3 Inputs – Surveillance points that capture visual information to relay back to the Control Room.
Contractor shall:
3.5.3.1 Coverage - Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.5.3.2 Consistency of Equipment – Utilize the same type of equipment used to satisfy the requirements of Section 3.1.2.3 so that the number of unique parts can be kept to a minimum to limit variation of usage, operation, and maintenance. Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.5.3.3 Visual Signature/Size Limitations – The cameras that comprise the Node shall compliment the walls/structures they are mounted to, and be non-obtrusive. Field Equipment shall be suitable for the environment for which it is being installed (e.g. equipment located within office areas shall protect against unwarranted tampering, and industrial areas may utilize industrial-style weather-sealed equipment).
3.5.3.4 Synchronization – All Inputs shall be synchronized with the Main Server’s timing to ensure uniform reporting and timestamping of activities.
3.5.3.5 Protection – All Inputs and their associated wiring shall be installed in conduit appropriate for the environment for which they are placed – Inputs and wiring installed within buildings shall be protected from tampering and hazards; Inputs and wiring outside of buildings shall be protected from tampering,
3.5.4 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1, to feature a
3.6 ADDITIONAL COMPLETE NODE FOR ISEE (CLIN 0005) (Node #4, which consists of Building 1000, Building 1055, and the parking areas associated with each building) – This consists of the installation of Inputs for the building and parking areas, and connection of this complete subsystem to the ISEE to allow for the dissemination of surveillance information within the selected building back to the Command Station. To support the development of a Complete Node, the Contractor shall meet or exceed the following requirements:
3.6.1 Access-point Connections - The Contractor shall:
3.6 1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.6.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc. are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.6.2 Connections/Communication (within Node) – Information communicated within the Node shall be delivered to over POE connections.
3.6.2.1 Connectivity - The ISEE shall be operational 24/7; UPS (to ensure availability of at least 24 hours in standby mode, and at 24 hours of active usage after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.6.2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.6.2.3 Latency - latency shall be no longer than 1 second from receipt of signal from the Control Unit until the start of the delivery of the received message.
3.6.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.6.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended and maintain continuous availability. Contractor shall deliver an As-Built Design drawing in accordance with CDRL A005, a Certificate of Conformance to attest to its work in accordance with CDRL A006, and a Warranty Performance Report in accordance with CDRL A007 to identify warranted items/systems.
3.6.3 Inputs – Surveillance points that capture visual information to relay back to the Control Room.
Contractor shall:
3.6.3.1 Coverage - Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.6.3.2 Consistency of Equipment – Utilize the same type of equipment used to satisfy the requirements of Section 3.1.2.3 so that the number of unique parts can be kept to a minimum to limit variation of usage, operation, and maintenance. Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.6.3.3 Visual Signature/Size Limitations – The cameras that comprise the Node shall compliment the walls/structures they are mounted to, and be non-obtrusive. Field Equipment shall be suitable for the environment for which it is being installed (e.g. equipment located within office areas shall protect against unwarranted tampering, and industrial areas may utilize industrial-style weather-sealed equipment).
3.6.3.4 Synchronization – All Inputs shall be synchronized with the Main Server’s timing to ensure uniform reporting and timestamping of activities.
3.6.3.5 Protection – All Inputs and their associated wiring shall be installed in conduit appropriate for the environment for which they are placed – Inputs and wiring installed within buildings shall be protected from tampering and hazards; Inputs and wiring outside of buildings shall be protected from tampering,
3.6.4 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1, to feature a
3.7 ADDITIONAL COMPLETE NODE FOR ISEE (CLIN 0006) (Node #5, which consists of Building 542, its fenced area, and the parking areas associated with the building) – This consists of the installation of Inputs for the building and parking areas, and connection of this complete subsystem to the ISEE to allow for the dissemination of surveillance information within the selected building back to the Command Station. To support the development of a Complete Node, the Contractor shall meet or exceed the following requirements:
3.7.1 Access-point Connections - The Contractor shall:
3.7.1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.7.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc. are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.7.2 Connections/Communication (within Node) – Information communicated within the Node shall be delivered over POE connections.
3.7.2.1 Connectivity - The ISEE shall be operational 24/7; UPS (to ensure availability of at least 24 hours in standby mode, and at 24 hours of active usage after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.7.2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.7.2.3 Latency - latency shall be no longer than 1 second from receipt of signal from the Control Unit until the start of the delivery of the received message.
3.7.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.7.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended and maintain continuous availability. Contractor shall deliver an As-Built Design drawing package in accordance with CDRL A005, a Certificate of Conformance to attest to its work in accordance with CDRL A006, and a Warranty Performance Report in accordance with CDRL A007 to identify warranted items/systems.
3.7.3 Inputs – Surveillance points that capture visual information to relay back to the Control Room.
Contractor shall:
3.7.3.1 Coverage - Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.7.3.2 Consistency of Equipment – Utilize the same type of equipment used to satisfy the requirements of Section 3.1.2.3 so that the number of unique parts can be kept to a minimum to limit variation of usage, operation, and maintenance. Install Power-Over-Ethernet fixed and Pan-Tile-Zoom (PTZ) cameras at locations in accordance with Applicable Document 2.1
3.7.3.3 Visual Signature/Size Limitations – The cameras that comprise the Node shall compliment the walls/structures they are mounted to, and be non-obtrusive. Field Equipment shall be suitable for the environment for which it is being installed (e.g. equipment located within office areas shall protect against unwarranted tampering, and industrial areas may utilize industrial-style weather-sealed equipment).
3.7.3.4 Synchronization – All Inputs shall be synchronized with the Main Server’s timing to ensure uniform reporting and timestamping of activities.
3.7.3.5 Protection – All Inputs and their associated wiring shall be installed in conduit appropriate for the environment for which they are placed – Inputs and wiring installed within buildings shall be protected from tampering and hazards; Inputs and wiring outside of buildings shall be protected from tampering,
3.7.4 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1, to feature a
3.8 ADDITIONAL COMPLETE NODE FOR ISEE (CLIN 0007) (Node #6, referred to as the “633 Complex” which consists of Building 633 and the parking areas associated with each building) – This consists of the connection of this complete subsystem to the ISEE to allow for the dissemination of surveillance information within the selected building back to the Command Station. The Inputs for this Node will have already been installed and completed. To support the development of a Complete Node, the Contractor shall meet or exceed the following requirements:
3.8.1 Access-point Connections - The Contractor shall:
3.8.1.1 Connection to Fiber Backbone – Utilize the access-point(s) of the Fiber Backbone to enable point-to-multiple-point communication.
3.8.1.2 Approvals – Proposed work must be submitted to the Philadelphia Industrial Development Corporation (PIDC) and Navy Facilities Command (NAVFAC) for their review and approval prior to any work regarding access and use of the duct(s) in which cabling, fiber, wiring, etc. are housed; Contractor shall ensure all designs are compliant with PIDC’s rules and regulations, as well as the Navy requirements cited in Section 2.0; requests for approval from PIDC and NAVFAC shall be routed through an NSWCPD point-of-contact to be named by the Contracting Officer’s Representative (COR).
3.8.2 Connections/Communication (within Node) – Information communicated within the Node shall be delivered over POE connections.
3.8.2.1 Connectivity - The ISEE shall be operational 24/7; UPS (to ensure availability of at least 24 hours in standby mode, and at 24 hours of active usage after disconnection from a power source), in combination with other suitable tools, shall be utilized to ensure the continuous availability of the system.
3.8.2.2 Encryption – Information sent through ISEE shall be protected from unwanted intrusion, hacking, and jamming of signals. Federal Information Processing Standard (FIPS) compliant encryption shall be used to protect data transmissions lines outside of federal government control (e.g., under Philadelphia streets).
3.8.2.3 Latency - latency shall be no longer than 1 second from receipt of signal from the Control Unit until the start of the delivery of the received message.
3.8.2.4 Independence – Each Node shall be enabled to capture, record, and store information from Inputs within the Node locally for up to 720 consecutive hours; should transmission of information from a Node to the Command Station fail, this capability shall provide a node-level backup of information to be incorporated when the System is fully operational.
3.8.2.5 Testing - Contractor shall ensure all equipment and connections perform to the specifications within this PWS. Contractor shall perform tests to ensure information can be delivered as intended and maintain continuous availability. Contractor shall deliver an As-Built Design drawing package in accordance with
3.8.3 Displays/Monitors – Install displays at location(s) in accordance with Attachment 2.1, to feature a
3.9 MAINTENANCE SUPPORT FOR ISEE (CLINs 0008)– This support shall provide for the regular and routine maintenance to ensure the entire system performs as designed. Maintenance shall be performed at least semi-annually, with more frequent visits to be determined by Contractor. At minimum, Contractor shall:
3.9.1 Diagnostic Testing – analyze the System and its components to determine the current performance level against the baseline objectives and provide findings in accordance with CDRL A009:
3.9.2 Maintenance – service (and replace, if necessary) the components and parts of the System that underperform and are beyond their expected life.
3.9.3 Updates – notify the Contracting Officer Representative of available software/firmware updates that could enhance the System’s performance; if provided approval, proceed with installation and testing
3.9.4 Cleaning – ensure all Inputs are free from obstructions that their limit maximum visibility as designed
3.10 SPARE PARTS (CLIN 0009) – Contractor shall identify and deliver one (1) each of every part number utilized to execute the requirements of this PWS; however, for items with unit costs of $10,000 or more, a list shall be presented to the Contracting Officer Representative for review and decision prior to the execution of any purchase of these items.
3.11 SOFTWARE MODIFICATIONS AND UPGRADES FOR COMPLETE NODES OF ISEE (CLIN 0011)
– Contractor shall execute the following to enhance the security management features of the ISEE system:
3.11.1 Integrate Keystone Web software as part of the security management system; license must be obtained from an authorized seller.
3.11.2 Purchase, configure, install, and migrate new LENEL VAR server (latest version/model)
3.11.3 Reconfigure OnGuard software to:
3.11.3.1 Allow flexibility to adjust for changes to ISEE’s size and configurations
3.11.3.2 Create rules to address:
3.11.3.2.1 Badge type (capture the different types issued and in circulation [i.e.
TWIC/GSA, CAC, etc.])
3.11.3.2.2 Bulk user functions (for more efficient database management)
3.11.3.2.3 Inactive accounts (i.e. deleted IAW set parameters)
3.11.3.2.4 “Set up Visitor” configuration to allow for faster processing
3.11.3.3 Capture the count of the number of individuals within a building
3.11.4 Set up and integrate driver’s license scanners into ISEE’s security management system.
3.11.5 Enhance the Command-Station-Control-Room and Displays/Monitors’ functionality with the modifications and upgrades from this subsection.
3.11.6 Update all equipment firmware to the latest approved version for the specified hardware.
3.11.7 Update all equipment software to the latest approved…
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 .