Attachment 1 - Draft PWS.docx

CSRCP HiPath Upgrade, Peterson Space Force Base

Performance Work Statement (PWS)

FOR

Unify HiPath to OpenScape Dispatch System Upgrade SBD 1 Colorado Springs Regional Command Post (CSRCP) Peterson Space Force Base, Colorado Springs, Colorado

1.0 Background

This PWS describes the hardware upgrade, software upgrade and the Unify OpenScape Command and Control (C2) dispatch system requirements for the CSRCP located at Peterson Space Force Base, Colorado Springs, Colorado.

2.0 Scope

This contract effort is to upgrade the Unify (Formerly Siemens) HiPath dispatch communications system at CSRCP to include the pre-existing network that connects the Giant Voice systems at Peterson SFB, Schriever SFB, and the United States Air Force Academy. This system will be installed on the premises of the primary command post on Peterson SFB, CO. The work set forth in this PWS consists of a site visit/survey, design, planning, installation, system set-up, testing, cutover, controller training, and applicable documentation of hardware and software components installed under this PWS. In addition, and as further described herein, this PWS includes a maintenance warranty for 1-year, beginning at system acceptance/cutover.

3.0 Objectives

The CSRCP will have direct lines to all operational organizations inclusive of Security Forces, Fire Department, Medical, and other essential base mission and mission support functions as part of the current Hi-Path System configuration. Each controller position must be able to communicate with all agencies involved in CSRCP operations.

4.0 Task Requirements

4.1. CSRCP, Bldg. TBD CP console. Contractor shall upgrade the existing HiPath 4000 communications server(s) and upgrade six (6) controller positions at the future primary location in the basement of building TBD.

The HiPath system will receive a software upgrade to the JITC Certified OpenScape Voice Local Session Controller (LSC) (Node A & B). The LSC-Node A will locate in building (TBD). LSC-Node B will be located in Bldg. TBD and both nodes will connect to each other via base LAN infrastructure and remain ‘active’ to support all positions. The existing voice recorders will receive upgrades to IP versions and connect to the OpenScape solution. Rack-installation locations will be determined during engineering survey.

4.1.1 In support of the upgrade described above, the contractor shall:

a) Coordinate with the 21st Communications Squadron telephone systems and Tech Control Facility to support relocating all existing PRI interface connections between the base Dial Central Office and HiPath to the OpenScape Voice LSC. (PRI relocation will be staggered during initial installation and testing so operations are not impacted) If PRI programming demands provisional changes from the current voice network/circuits; the contractor via the project PM will host a transport-provisioning meeting with the CS reps. All transport and PRI changes needed to accommodate the upgrade will be fully agreed upon as “able to provide” from the existing central office switch. The contractor is responsible for any proprietary issues that arise creating problems to establish the new service via the (LSC) gateway to the base central office, the contractor shall provide the SME-engineer POC to accommodate connection to today’s servicing transport/translations network.

b) Bldg. TBD, Primary Command Post controller area. Provide and install six (6) controller workstations each configured with; (1) touch-screen computer, (2) push-to-talk handsets, (1) dual-channel speaker. One UPS unit per position is included in this project. The contractor shall ensure proper ANSI/ANSI 568 cabling standards be employed to all servicing workstations back to the LSC as determined during engineering survey. This network will utilize the USAF/government LAN. Note it is possible to install the Unify network in its own turnkey enclave solution, if preferred – to be determined at engineering survey.

c) Install six (6) radio interfaces for Any-to-Any Voice Connectivity to connect primary Command Center radios for future capabilities. Specific channels/nets to be determined during engineering survey. Proper ANSI/ANSI 568 cabling standards will be employed to all servicing workstations back to the LSC as deemed. This connection will be via the USAF/government LAN.

d) Upgrade existing voice recorder to support recording (telephone and radio) for each controller position. Proper ANSI/ANSI 568 cabling standards will be employed to all servicing workstations back to the LSC as identified in the engineering survey.

e) Provide (1) administrative PC for (local) system management

f) End-Of-Life System Support and Upgrade. The Contract shall Engineer, Furnish, Install, Test, and Place into full service (EFIT&P) an upgrade solution to replace the existing End of Life/End of Service (EoL/EoS) system. The new dispatch system upgrade shall include hardware, software, licenses, controller console positions, system admin/manager workstation, admin multi-line phones, entrance phones, multi-party conferencing, voice recording, media gateways, interface equipment, and all other necessary equipment/wiring; and be capable of interfacing and integrating with the base VoIP Unified Capabilities (UC) Local Session Control (LSC), Secondary Crash Net (SCN), and radio networks (HF, VHF, UHF, LMR, and/or SATCOM) to provide complete services. All new dispatch system and equipment shall be the Joint Interoperability Test Command (JITC) certified Approval to Operate (ATO). The Contractor shall decommission and remove the existing dispatch system and its associated components/wiring upon completion of upgrade.

The Contractor shall coordinate with the base to verify all necessary information and changes upon the Contractor site survey and to identify and ensure all preparations required from the base responsibilities and allied support prior to implementation

4.2 Above system will support the following salient features

a) One-touch conferencing (perform “all calls” on radios and by phone)

b) Automatic Notification of incoming telephone or radio calls

c) Provide Programmable pre-set calling operations via ‘buttons” on touch-screens

d) Electronic directory (include hotlines to key agencies)

e) Administrative phones (2 included), (Multi-line capability)

f) Connect to existing base dial central office via existing PRI connections.

g) Installation into government provided furniture

h) A thorough transport/translation/configuration cutover strategy meeting will be performed and agreed upon prior to service activation. Segregated or NFAS/D channel service, dial plan, testing, and more will be thoroughly examined same. Future SIP services transport discussion is optional.

i) Warranty and contract service support included for 1 year

5.0 Government responsibilities:

5.1 1 In support of the expansion described above, the Government shall provide the following:

5.1.1 Physical plant infrastructure and applicable environmental requirements (i.e., power, space, air conditioning, etc.) prior to the Contractor’s commencement of on-site work;

5.1.2 Data network infrastructure.

5.1.3 Phone placement information, including marked floor plans identifying all phone types, locations, and extension numbers and cabling identification numbers.

5.1.4 Racks and associated equipment (unless identified on equipment list to be provided by Contractor), such as data racks, monitors for all applications servers.

5.1.5 Re-used equipment and cable, including any currently installed equipment to be reused except equipment outlined in 4.0 contractor task requirements.

5.2 Additionally, The Government is responsible for:

5.2.1 Participating in the project implementation review process and approving of all necessary documents prior to commencement of the product installation.

5.2.2 Completing the design workbook prior to the design workshop.

5.2.3 Providing a high speed, secure, remote access connection between Government’s network and Contractor’s support center to extent permitted by law and unless otherwise mutually agreed to by the parties

5.2.4 Providing network and telecommunications contractor coordination.

5.2.5 Ensuring that Contractor has all necessary, safe and prompt access to the premises and equipment (whether physical or virtual).

5.2.6 The performance of its network, including but not limited to any equipment provided by Government. Government agrees to promptly remedy deficiencies unless any connectivity is in direct violation of any DISA STIG compliance.

5.2.7 Providing suitable training facilities for end user training sessions.

5.2.8 Removing and disposing of any existing equipment, as applicable.

5.2.9 A CSRCP Project Manager or Quality Assurance Evaluator will be present during all formal Quality Assurance inspections, final testing, and acceptance of the project.

6.0 Security Requirements – Base/Site Access

6.1 The contractor and, as applicable, subcontractor shall not employ persons for work on this contract if such employee is identified as a potential threat to the health, safety, security, general wellbeing or operational mission of the installation and its population, nor shall the contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by Law Enforcement Agency Data System (LEADS) through the National Crime Information Center. LEADS checks will verify if a person is wanted by local, state, and federal agencies. All contractor and subcontractor personnel must consent to LEADS background checks. Contractor and subcontractor personnel who do not consent to an LEADS check will be denied access to the installation. Information required to conduct a LEADS check includes: full name, driver’s license number, and/or social security number, date of birth of the person entering the installation, and completion of a background check questionnaire. The contractor shall provide this information using Form 21, Contractors Consent for Background Check, and shall submit it in conjunction with the contractor’s request for either base or vehicle passes. Completion of a successful LEADS check does not invalidate the requirement for an escort when contractor or subcontractor personnel are working within controlled or restricted areas.

6.1.1 Contractors shall ensure their employees and those of their subcontracts have the proper credentials allowing them to work in the United States. Persons later found to be undocumented or illegal aliens will be remanded to the proper authorities. The contractor shall not be entitled to any compensation for delays or expenses associated with complying with the provisions of this clause. Furthermore, nothing in this clause shall excuse the contractor from proceeding with the contract as required.

6.1.2 To obtain unescorted access to the installation, all contractor’s credentials must be IAW the REAL ID Act of 2005. If a contractor does not have credentials that are compliant with the REAL ID Act, they must be escorted at all times. For more information, and to determine what credentials are and are not compliant, go to https://www.dhs.gov/real-id-public-faqs.

6.2 Badges: The contractor is required to provide identification badges for their employees. All contractor personnel shall wear these badges while on duty on the government site. Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. Size, color, style, etc. are to be mutually agreed to by contractor and government. The contractor’s identification badge will not be used as an entry requirement for installation entry or into any government designated controlled or restricted area. All DBIDS cards/passes will be turned in to the Visitors Control Center upon expiration of pass and/or completion of contract.

6.3. Contractor Registration of Vehicles on base: All contractor or contractor employees’ vehicles used for the performance of this contract shall comply with all local, state, and federal regulations. Additionally, any pass shall be surrendered to Security Forces upon demand to positively identify a person need to be on site. All delivery trucks must enter through the commercial Gate. All gates are available for passenger vehicles.

6.4. Access to Installation during Force Protection Conditions (FPCONs): Contractors will be assigned a mission essential designation IAW requirements contained in USAF Antiterrorism-Integrated Defense Plan 31-1 (AT-IDP). Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

6.5. Property Protection: Property protection for facility where the contractors’ primary work center is located will be the responsibility of the local facility manager and local Government Security Manager, or their duly authorized representative IAW AFI 31-101, Integrated Defense and command/local directives. The contractor shall safeguard all government-owned equipment and materials in his/her possession or use.

6.6. Safeguarding Classified or Unclassified Information: The contractor shall meet Air Force standards for storing, processing, and handling classified information and systems. Additionally, all resources (e.g. maps, publication/instructions, photos) provided by the government to assist the contractor in the performance of their contract will be surrendered upon termination of employment or the end of the contract performance period.

6.7. Contractors Working in Controlled or Restricted Areas: The unit requesting contract support will provide escort(s) for contractors at all times when within a controlled area. Contractors shall not escort other contractor employees within controlled or restricted areas. In addition, contractors shall fulfill, maintain, and comply with all security requirements IAW AT-IDP, and command/local directives.

6.8. Access to Government Facilities with Controlled or Restricted Areas: The contractor shall comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas on LVRCP, the government may direct the contractor to leave the controlled or restricted areas at any given time.

6.9. Contractors Responsibilities while Working within Controlled or Restricted Areas: Only contractor personnel with proper authority and qualifications shall enter a controlled or restricted area. Certain facilities require the issuance of an AF Form 1199. The government, at any time, may revoke the AF Form 1199. The procedures for the issuance of an AF Form 1199 are contained in AT-IDP. Contractors shall not escort other contractor employees within controlled or restricted areas. In addition, contractors shall fulfill, maintain, and comply with all security requirements contained in AT-IDP.

7.0 Place of Performance

Travel in and around the primary place of performance may be required throughout the period of performance.

Place of Performance Mailing Address:

CSRCP

775 Loring Ave. Ste 107 Peterson SFB, CO 80914

8.0 Period of Performance

Final testing and acceptance will take place no later than 60 days after the notice to proceed for installation is issued.

9.0 Hours of Work

This work shall be performed in government facilities at LVRCP. Work shall be performed typically 0800-1600, Monday through Friday, excluding Federal Holidays. Travel in and around the primary place of performance may be required throughout the period of performance (POP). Any work desired to be accomplished outside posted hours will require prior approval of the Contracting Officer & Site POC. The Contractor must submit a written request to the Contracting Officer no later than the preceding Wednesday of the current work week.

In the event that upgrades or changes to the system must be done during off peak or limited usage time (i.e. weekends), the Government reserves the right to request flexible work hours from contractor personnel. Upon a 24 hour advance, written notification from the Contracting Officer, the Government and contractor may establish a mutually agreed upon time to institute/incorporate the system change. Contractor personnel will substitute the noncore, weekend hours for an equal number of weekday hours. For example, if an upgrade is accomplished on a Saturday and takes 4 hours, contractor personnel may choose to take off 4 hours on the following Monday or Tuesday.

Contractor work requiring shutting down facility power will need to be coordinated with facility POCs in advance of requested power outage. Although not anticipated with this project, in cases where power outage requests may affect critical functions affecting the facility’s primary mission systems, power outage coordination requests are required twenty-one (21) days in advance due to critical information technology (IT) equipment within the building areas. It should be noted that the Contractor's performance may be interrupted from time to time because of high priority mission schedules or no-notice events. For each calendar day and/or portion of a calendar day that the contractor is removed/denied access from the job site, the contractor schedule will be adjusted by one calendar day.

10.0 Federal Holidays

No work is authorized on Federal Holidays. The following Federal holidays are normally observed by Government personnel: New Year’s Day, Martin Luther King, Jr’s Birthday, President’s Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving Day, Christmas Day, and any other day designated by Federal Statute, Executive Order, and/or Presidential Proclamation.

When the Government installation grants administrative leave to its employees (e.g. as a result of inclement weather, potentially hazardous condition, or other special circumstances), Contractor personnel working on-site may also be dismissed.

11.0 Site Project Managers (POCs): TBD

12.0 Clean Up

The Contractor is required to clean up daily and to maintain a safe working area at all times.

13.0 Travel and Expenses

The contractor shall provide all travel and expenses into the firm fixed price quote.