W9124A23R0021-0001.pdf

W9124A23R0021

ACC-APG

RHONDA GILL

BLDG 61801 RM 2637

PN: 520-538-6362 FAX: 520-538-6400

FORT HUACHUCA AZ 85613

0011905563

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 Amendment 01 is to:

1. Answ er Questions Received

2. Update the Performance Work Statement (PWS)

3. Extend the due date from 11 August 2023 to 22 August 2023 and update change questions due date of 17 August 2023.

4. All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 27

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 09-Aug-2023

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) X W9124A23R0021

X 9B. DATED (SEE ITEM 11)

26-Jul-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X 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)

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:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return 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

09-Aug-2023

CODE

ACC-APG

BLDG 61801 RM 2633

FORT HUACHUCA AZ 85613

W9124A 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE W9124A

FACILITY CODECODE

EMAIL:TEL:

FOR OFFICIAL USE ONLY

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been modified:

INSTRUCTIONS TO OFFERORS

INSTRUCTIONS TO OFFEROR-COMMERCIAL ITEMS.

OFFEROR IS REQUIRED TO READ ALL INSTRUCTIONS AND COMPLY WITH THE

INSTRUCTIONS.

1. Please fill in (write/type) On the First Page of the Government 1449 Solicitation, Blocks 17a, 30a, 30b, 30c.

2. Fill in ALL Pricing and All Applicable TAXES on ALL Line Items (CLINs). Please TOTAL ALL CLINs, IN YOUR QUOTE to show an overall FINAL Price and include ALL shipping charges as FOB Destination. When submitting your quote in response to this Request for Quote, the offeror shall provide their best pricing, including all discounts. Attachment(s) to the SF 1449 please ensure your cost on the attachment matches your entry, if applicable

3. Include the delivery lead-time; if lead-time differs from solicitation, notate delivery lead time on the quote.

4. Provide the following information with your offer:

e. POC Name: __________________________________

f. POC Phone Number: _________________

g. POC E-Mail: ___________________________

5. The Government will award a Firm Fixed-Price contract resulting from this solicitation on a lowest-priced technically acceptable basis (considering the following two factors:

technical, and price.) All offerors shall be considered in terms of price, lowest to highest, and then the apparent lowest-priced offeror will be evaluated for acceptability under the technical and price factors. If the lowest-price offeror is evaluated as unacceptable, the acceptability of the next lowest-price offeror will be evaluated, continuing this process as necessary. The offer shall meet all terms and conditions of the solicitation and shall detail the offered solution in their quote or attach a data specification sheet.

6. Complete the Following Clauses (located below in the Contract Clauses).

a. FAR clause 52.212-3 “Offeror Representations and Certifications” Commercial Items. Section B of this clause still needs to be completed in its entirety and returned to the contracting office with your quote.

b. FAR Clause 52.204-26 “Covered Telecommunications Equipment or Services- Representation. Section B of this clause still needs to be completed in its entirety and returned to the contracting office with your quote.”

c. FAR Clause 52.204-24 “Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment Section B of this clause still needs to be completed in its entirety and returned to the contracting office with your quote.”

7. Quote/Proposal shall be received electronically via e-mail to Tuesday Friday 22 August 2023.

8. Questions about the solicitation are to be directed to rhonda.k.gill.civ@army.mil before the due date of 17 August 2023 at 09:00 AM local AZ time.

Additional Information

1. Vendor invoicing shall not be submitted prior to proof of delivery that items have been received.

2. The CLINs in this schedule are being competed as BRAND NAME OR EQUAL and must be entered with the made, model, and description of equivalent if so quoted-In accordance with the Federal Acquisition Regulation (FAR) 52.211-6.

3. Per DFARS 252.232-7003 Electronic Submission of Payment Requests, the vendor shall submit combination payment requests (invoice and receiving report) using Wide Area Work Flow (WAWF). Receipt and Acceptance (WAWF-RA) or other methods authorized by the Contracting Officer. Failure to comply could result in delayed payment.

4. Please provide a detailed breakdown or narrative of what is being provided to meet the requirement. Do not copy and paste the line item information from the RFQ to your bid as this could classify a bid unsuccessful in the technical evaluation process. We require detailed descriptive information on all bids.

5. Support Renewals – NO THIRD PARTIES WILL BE ACCEPTED.

6. ONLY THE CONTRACTING OFFICER (KO) CAN MAKE CHANGES TO THE

CONTRACT/DELIVERY ORDER/PURCHASE ORDER.

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 11-Aug-2023 09:00 AM to 22-Aug-2023 09:00 AM.

The following have been added by full text:

QUESTIONS & ANSWERS

Questions for RFP W9124A23R0021

1. Section 1.3 (Page 3) refers to Ft. Huachuca sharing the Cochise County Spillman CAD system. If the new, independent Emergency Call Taking System will need to interface with a shared CAD system, how will data be provided to the Spillman CAD system separate from the Cochise County system? NG911

Data provided by interface to Spillman will still be shared

2. Section 4 (Pages 10, 13) refers to Attachment 1, Site Survey document that provides information on number of channels and circuits. Can you provide the referenced Site Survey document?

No Site Survey – remove from PWS

3. Section 4.1 (Page 9) – The RFP states that the contractor will be responsible for providing on premise wiring and networking elements. Does the Government already have CAT 6 wiring at the CDC, Building 31044 that connects to Host Server A – Building 31044? Also, does the Government already have CAT 6 wiring for the mobile Call Taker Computers at Building 51028 (Fire Station 1)?

CAT5E wiring is installed

4. Section 4.2 (Page 10) states that the proposed solution must support Text to 911. Please identify whether the SMS will be delivered over dedicated circuits from a Text Control Center (TCC) or via some other mechanism.

Dedicated circuits from a Text Control Center (TCC)

5. Section 4.2 (Page 10) - The government to provide diverse fiber paths where applicable to provide redundant connectivity between facilities. The system shall provide flexibility and expansion capability to provide an increase in the number of consoles at each location to support additional technicians, administrators, helpdesk supervisors and calls.

a. Are the Fiber connections MMF or SMF? Dark or Light?

Unknown

b. Is the Fiber handoff going to be Ethernet or a straight Fiber connection?

Straight fiber

6. Section 4.2 (Page 10) – Please provide details on the size, weight, and number of components that make up the existing system that require disposal.

Approximately 1,000 lbs. Size varies from handhelds devices to server and monitors.

7. Section 4.3 (Page 10) – Please detail the number of base switches that require connectivity to the proposed

NG9-1-1 solution.

None

8. Section 4.3.a (Page 11). The requirement indicates that the private ALI database system shall be installed on the Air Force premises. Which Air Force premise should the private ALI database system be installed?

Disregard Air Force - It will be installed in the comms room of Bldg 31044

9. Section 4.3.b/c – Please specify the number of CAMA circuits to be supported by the offerer’s proposed solution.

One – need to check

10. Section 4.3.3.1.1 (Page 13). May the offerer propose equivalent workstations with Intel CPU and

Motherboards instead of AMD?

YES

11. Section 4.3.3.1.7 (Page 13). Does the Government prefer handsets rather than headsets, or both?

Both

12. Section 4.3.6 (Page 17). May the offerer provide references from Army bases as well as Air Force bases as stated?

References from Army and Air Force can be sent

13. Section 4.4.2 (Page 17). Is the additional NG911 Workstation/Console requested in addition to the third mobile workstation requested?

YES

14. Section 4.6 (Page 18). Is the single System Management solution requested intended to operate on the 3

Call Taker workstations or the Additional NG911 Workstation/Console or a new workstation to be included in the quote?

All three terminals

Item Number RFP Document /RFP Section/ Page Lumen Question / Comment

1 n/a – general question Will the customer entertain supplemental terms and conditions with Lumen's response for the purposes of post -award negotiations?

Answer: No there will be no supplemental terms.

2 p. 1, item/box 10 The RFP calls for “100% set aside for small business”. Can you explain in more detail what is expected and/or the qualification limitations associated with the “set aside”?

Answer: This Request for Quote is being set aside in accordance with FAR 19.502-2

3 p. 1, item/box 10 Lumen currently has several relationships with small businesses that fill many requirements outlined in this RFP as well as others we've responded to. Lumen intentions is to bid with a small business that fulfills all requirements outlined in this RFP. Our question is does this did strategy fulfill the requirements of the

RFP?

Answers: In order to quote on this requirement offerors need to be a small business concern

4 p. 3, item 6 The Reference FAR clauses do not appear to have a “Section B” – please indicate which sections need to be completed.

Answer: The Section B of 52.212-3 begins on page 32 at (b)(1) Annual Representations and Certifications

5 p. 3, item 6 Similarly, there are clauses that appear to require responses within clauses in pgs. 24-61, but are not listed in item 6 – do they NOT require responses with proposal submission?

Answer: Yes, complete the clauses in pages 24-61

6 p. 4, Additional Information, item 5 Please explain what is meant by “NO THIRD PARTIES WILL BE ACCEPTED” - does this apply to the entire RFP, or is this specific to “Support Renewals”?

Answer: This applies to Support Renewals

7 p.10, Section 4.3, 4th bullet on page;

p. 13, Section 4.3.3.1.2

Both Sections of the RFP refer to an Attachment 1, the Site Survey Document that does not appear to be included. Can you forward Attachment 1 or where may we obtain it?

No Site Survey – remove from PWS

8 p.10 of 61, Section 4.3, paragraph 3 The government to provide diverse fiber paths where applicable to provide redundant connectivity between facilities. The system shall provide flexibility and expansion capability to provide an increase in the number of consoles at each location to support additional technicians, administrators, helpdesk supervisors and calls.

Describe the Demarc from the Fiber drop to the connection point for Omni911. Is the Fiber connection MMF or SMF? Dark or Light?

Unknown

Is the Fiber handoff going to be Ethernet or a straight Fiber connection?

FIBER

9 p. 11 of 61, Section 4.3, 1st non-bullet paragraph

The system shall support calls from on base PBX/VSS (DSN) wire-line extensions, PSTN (commercial) wire-line (housing, on-base contractors, vendors, etc.), and commercial wireless sources. Call routing for all PSTN 911 calls shall be based on the associated Emergency Service Number, automatically delivering the call to the designated on-base PSAP.

How many T1-PRIs will be utilized by the solution (4.3.8 mentions single T1-PRI)? One

How many CAMA Trunks will be utilized by the solution (2 trunk circuits mentioned in section 4.3.5)? Two

How many FXO analog lines will be utilized by the solution? Two

How many SIP Trunks will be utilized by the solution? Two 10 p. 13 of 61: Table May the vendor select an Intel CPU / Motherboard option regarding the

Workstation configuration? Yes 11 p. 14 of 61, Section 4.3.3.1.7:

Handsets Are the vendors limited to Handsets vs Headsets? Both

12 p. 21 of 61, Section 6.7 Equipment Removal

Please define the approximate weight of the Equipment to be re-packaged. Approximately 1000 lbs.

Does the original packaging for the current solution exist? No If so, may the vendor utilize those packaging items? N/A

13 p. 22 of 61, Section 10.

GOVERNMENT MULTI FUNTION

TEAM/ POC’S

There is no requirement in this section – what is expected here?

These will be provided upon contract award.

General

Did the government intend to allow full and open unrestricted competition in order to provide the best value to the government?

Answer: This is being competed as a Small Business Set-Aside

General

Is the successful contractor responsible for walking in and taking over the current solution until it can transition to the newly awarded solution?

Answer: No

The following have been modified:

PERFORMANCE WORK STATEMENT

Performance Work Statement for

Next Generation 911 (NG911) Public Safety Answer Point (PSAP) Installation at

Fort Huachuca, AZ June 4, 2022

242 Christy Ave

Fort Huachuca, Arizona 85613

March 3, 2021 i

Table of Contents Section Title Page

1. Purpose .......................................................................................................................... Error! Bookmark not defined.

1.1 Scope Erro r! Bookmark not defined.

1.2 Objective Erro r! Bookmark not defined.

1.3 Background Erro r! Bookmark not defined.

2. Program Requirements ....................................................................................................... Error! Bookmark not defined.

2.1 Program

Requirements Erro r! Bookmark not defined.

2.2 Place of

Performance Erro r! Bookmark not defined.

2.3 Performance

Period Erro r! Bookmark not defined.

2.4 Joint Interoperability Test Center Approved Product

List Erro r! Bookmark not defined.

2.5 Certification and Accreditation

(C&A) Erro r! Bookmark not defined.

2.6 Schedule Erro r! Bookmark not defined.

2.7 Spares Erro r! Bookmark not defined.

3. Project Execution ................................................................................................................. Error! Bookmark not defined.

3.1 Site

Coordination Erro r! Bookmark not defined.

3.2 Multi-Function Team (MFT)

Coordination Erro r! Bookmark not defined.

3.3 Project In-

Brief Erro r! Bookmark not defined.

3.4 Provisioning Project

Owner Erro r! Bookmark not defined.

ii

3.5 Government

Delays Erro r! Bookmark not defined.

3.6 Routine Working

Hours Erro r! Bookmark not defined.

3.7 Contractor

Supervision Erro r! Bookmark not defined.

3.8 Personnel Training and

Certifications Erro r! Bookmark not defined.

3.9 Security

Clearance Erro r! Bookmark not defined.

3.10 Safety Erro r! Bookmark not defined.

3.11 Implementation Erro r! Bookmark not defined.

3.12 Conformance to

Standards Erro r! Bookmark not defined.

3.13 System Installation Plan (SIP) / Project Support Agreement (PSA) Erro r! Bookmark not defined.

3.14 System Turn

Over Erro r! Bookmark not defined.

3.15 Associate Contractor

Agreements Erro r! Bookmark not defined.

3.16 Performance of Services During

Crisis Erro r! Bookmark not defined.

4. Technical Requirements ...................................................................................................... Error! Bookmark not defined.

4.1 Baseline Erro r! Bookmark not defined.

4.2 Baseline

Requirement Erro r! Bookmark not defined.

4.3 Optional CLINs/Requirements 15

4.4 Total Cost of

Ownership Erro r! Bookmark not defined.

iii

4.5 Single System Management

Solution Erro r! Bookmark not defined.

5. Testing Requirements .................................................................................................... ….Error! Bookmark not defined.

5.1 General Testing

Requirements Erro r! Bookmark not defined.

6. Logistics Support ................................................................................................................. Error! Bookmark not defined.

6.1 Warranty Erro r! Bookmark not defined.

6.2 Software

Patching Erro r! Bookmark not defined.

6.3 Remote

Access Erro r! Bookmark not defined.

6.4 Packaging, Handling, Storage, and

Transportation. Erro r! Bookmark not defined.

6.5 Training Erro r! Bookmark not defined.

6.6 Commercial Off-the-

Shelf Erro r! Bookmark not defined.

6.7 Equipment

Removal Erro r! Bookmark not defined.

7. Support Requirements ......................................................................................................... Error! Bookmark not defined.

7.1 Support Requirements (Base

Requirements) Erro r! Bookmark not defined.

8. Contractor Manpower Reporting ......................................................................................... Error! Bookmark not defined.

9. Service Summary ................................................................................................................ Error! Bookmark not defined.

9.1 Methods of

Surveillance Erro r! Bookmark not defined.

9.2 Spillman Flex

Maintenance Erro r! Bookmark not defined.21

10. Program Managers / Contracting Office Representative

1. PURPOSE

1.1 Scope

This Performance Work Statement (PWS) provides for the purchase and installation of three dispatcher consoles utilizing the current DoD Version of Next Generation 911 (NG911) PSAP Emergency Call Taking System with the capability to transfer data to the existing Spillman Computer Aided Dispatch system, which is used by Fort Huachuca via an extension from the Cochise County system. The purchase shall include three NG911 Workstations (IWS), which one may be a mobile NG911 Workstation Emergency Dispatch Positions and stand-alone Automatic Location Identification (ALI) databases. The purchase shall include one year maintenance and warranty and any and all required equipment, software, work, and test to ensure the successful delivery and operation of the NG911 PSAP system. The system shall support calls from on base PBX wire-line extensions (TDM and VoIP), commercial wire-line (housing, on-base contractors, vendors, etc.), and commercial wireless sources equivalent to the State of Arizona NG911 capabilities and functionalities. Call routing for call from commercial (non-government) sources shall be based on the associated existing Emergency Service Number, automatically delivering the NG911 call to the newly designated on-base PSAP. The system shall provide the direct delivery of NG911 calls to a Department of Defense (DoD) staffed PSAP without the need for intermediate call answering by the local civilian PSAP.

Modifications to this PWS will be as authorized by Contracting Officer. Authorized modifications shall be integrated into the project by the Contractor. Change Orders must be approved by The Contracting Officer prior to implementing any changes or additions.

1.2 Objective

The objective of this PWS is to document the requirements to Engineer, Furnish, Install, and Test (EFI&T) an NG911 Emergency System.

1.3 Background

Fort Huachuca currently utilizes a Vesta Enhanced E-911 Version 4 system as a part of the Cochise County Vesta system. This system is out of date and in order to separate from the county system, shall be upgraded to a current DoD Version of NG911 Emergency Call Taking System with the capability to transfer data to the existing Spillman Computer Aided Dispatch system, which is used by Fort Huachuca via an extension from the Cochise County system.

2. PROGRAM REQUIREMENTS

2.1 Program Requirements

This is a turn-key installation wherein the Contractor shall EFI&T and upgrade from the current Vesta Enhanced 911 Ver. 4 to the current DoD version of NG911 solution meeting the State of Arizona NG911 requirements at the site identified in paragraph 2.2. The Contractor shall engineer, furnish, install, test and make operational newly installed equipment to OEM, industry and/or Army specifications with the appropriate vendor pass through licenses.

The Contractor shall provide all hardware, software, licensing, and training required for the use of all systems and equipment installed under this PWS. The overall objective is to upgrade the NG911 infrastructure at Fort Huachuca.

Contractor shall clearly identify expected government labor, government furnished property (GFP) and support required to implement a fully functional solution. This paragraph is applicable to the solution(s) proposed under paragraph 4.

2.2 Place of Performance

The place of performance shall be at Fort Huachuca.

2.3 Performance Period

The Government desires delivery of all work to be accomplished within 180 days of contract award.

If the Contractor is unable to meet the desired delivery schedule, it may, without prejudicing evaluation of its offer, propose a delivery schedule. However, the Contractor’s proposed delivery schedule must not extend the delivery period beyond 365 days of contract award. Any request or justification for change shall be made to the Contracting Officer in writing and must be approved by the Contracting Officer.

2.4 Joint Interoperability Test Center Approved Product List

The Contractor’s solution(s) shall be on the JITC-certified Approved Product List (APL) https://disa.mil/Mission- Support/Testing/DoDIN-APL. The systems shall meet interoperability requirements of the JITC to ensure interface with commercial and military interface standards. Operating Systems and applications shall be configured in accordance with Security Technical Implementation Guides (STIGs) https://iase.disa.mil/stigs . Windows operating systems (OS) shall be Server 2012 R2 and Windos 11. Contractor shall provide a copy of all Interoperability (IO) and Information Assurance (IA) certifications and approval letter as an attachment to the proposal. The IA certification must the Server 2012 and Window 10 operating systems. A recent review of the E9-1-1 Customer Premise Equipment (CPE) solutions on the JITC APL indicated that there are no solutions that meet the criteria below. OEMs that do not currently have products on the APL meeting the stated OS and other requirements herein must demonstrate a plan to achieve listing on the APL prior to contract award date. Plan must include a current application tracking number from the DISA APLITS test center and scheduled test dates and shall be submitted in response to this PWS.

2.5 Certification and Accreditation (C&A)

The Contractor shall assist the base in implementing the Information Assurance (IA) compliance for system C&A.

To support the Risk Management Framework (RMF) process, the contractor shall provide and develop any necessary system documentation, settings, self-assessments and specifications required to support the successful accreditation of the Government RMF package. This shall include information in support of Government input into the Enterprise Mission Assurance Support Service (eMASS).

2.6 Schedule

Contractor shall provide a Government approved final schedule within 14 working days prior to on-site work.

3. PROJECT EXECUTION

3.1 Site Coordination

The Contractor shall coordinate with the identified site POCs, Government Multi Function Team (MFT) a minimum of 10 business days prior to arrival on site.

3.2 Multi-Function Team (MFT) Coordination

The MFT members will be identified prior to contract award. The MFT is composed of stakeholders in the acquisition and is responsible for the acquisition throughout the life of the requirement. The goals of the MFT are to manage this contract and to provide an avenue to collectively work together to create a strong working relationship between the using agency, contracting and the contractor and provide the highest level of contract performance and customer service. Prior to any on-site work, the Contractor shall provide the MFT a project coordination call to review all planned efforts and data collection requirements in support of project implementation.

3.3 Project In-Brief

The Contractor shall conduct a project in-brief with MFT. Contractor shall support and respond to questions regarding issues pertaining to this PWS.

3.4 Provisioning Project Owner

The Contractor shall identify by name a Provisioning Project Owner (PPO), who shall be the prime contractor’s employee, responsible as the single point of contact from award to site acceptance with regard to system implementation. The PPO must remain on site as necessary to assure performance of project. The Contractor shall also assign a system engineer to work for the PPO. The system engineer shall support architectural diagrams, system interface specifications, technical planning, test plans, test procedures, and logistics sustainability. The Contractor shall submit the first Monthly Status Report NLT forty (40) calendar days after contract award and subsequently every month thereafter until all tasks have been completed IAW this PWS and government final acceptance has been completed.

3.5 Government Delays

In the event that a Government-caused delay requires the Contractor to incur schedule delays or additional costs, the Contractor must document and submit these changes to the Contracting Officer for their review and consideration prior to any change in schedule.

3.6 Routine Working Hours

Routine work efforts shall be performed during normal installation operating hours (Mon-Fri 0730-1630) with exception to the cutover to upgraded system. Cutovers and any other service-affecting actions must be pre-approved by the Government and scheduled during maintenance windows (Approved Service Interruption – ASI).

3.7 Contractor Supervision

The Contractor shall be responsible for supervision of all contract personnel and performance of all Contractor-related functions.

3.8 Personnel Training and Certifications

All personnel identified to support this requirement must be trained and/or certified on the systems involved in this effort. Personnel identified to support this requirement must be able to provide training certification upon Government request.

3.9 Security Clearance

All contracted personnel shall comply with established security procedures for entering an installation and its facilities, including special security procedures for entry to restricted or controlled areas. The Contractor shall obtain necessary badges or documents required for entry to restricted or controlled areas, if applicable, to meet the requirements of this PWS. The Contractor shall coordinate with the site POC to obtain and return temporary badges and vehicle registrations. Contractors working under this PWS, as a minimum, shall have a favorable National Agency Check. However, if the proposed solution requires a need for access to Government system(s) requiring a higher security level, the Contractor shall ensure personnel have the proper security requirements at no additional cost to the Government.

3.10 Safety

No personnel presenting potential threats to the health, safety, security, general wellbeing, or operational mission of the installation and its population shall be employed by the Contractor during the execution of this PWS.

3.11 Implementation

The Contractor shall have ultimate responsibility for the successful deployment and cutover to the new infrastructure. Any work deemed non-compliant shall immediately be re-worked at the Contractor’s expense. This task shall include all necessary work required to connect to the existing infrastructure providing a fully functional network solution.

The Contractor shall plan and manage daily operations and activities associated with providing this requirement to ensure necessary processes and activities are performed to provide an effective and acceptable system. The Contractor will employ effective management tools and methods to assure control of cost, schedule and performance.

The Contractor shall conduct, support, or participate in program management and technical reviews, meetings, and conferences, as required, to ensure effective and efficient PWS execution.

The Contractor shall ensure protection of government property to prevent damage during the period of time the property is under the control or in possession of the Contractor. The Contractor shall ensure that any damages incurred during the execution of this PWS shall be repaired at the Contractor’s expense.

3.12 Conformance to Standards

All equipment and system solutions shall conform to the applicable industry standards and mil specs as identified in the following table. Also, if any standards aren't identified below but are applicable contractor shall conform to those as well.

TABLE 3.13.1 INDUSTRY STANDARDS ORGANIZATIONS

1. Federal Information Processing Standards (FIPS).

United States Department of Commerce National Technical Information Service 5285 Port Royal Road Springfield, VA 22161 http://www.itl.nist.gov/fipspubs/

2. Military Standards, Specifications, and Regulations (MIL-STDs, DoD-STDs).

Standardization Document Order Desk Bldg. 4, Sec. D, 700 Robbins Ave. Philadelphia, PA 19111-5094

3. National Computer Security Center (NCSC) Documents.

Office of Standards and Products National Computer Security Center Fort Meade, MD 20755-http://www.radium.ncsc.mil/

4. National Institute for Standards and Technology (NIST) (formerly National Bureau of Standards, NBS) Documents.

National Institute for Standards and Technology US Department of Commerce Washington, DC 20234 http://www.nist.gov/

5. Code of Federal Regulations (CFRs).

Superintendent of Documents US Government Printing Office Washington, DC 20402 http://www.access.gpo.gov/nara/cfr/

6. American National Standards Institute (ANSI) Documents.

American National Standards Institute 11 West 42nd Street New York NY 10036 http://www.ansi.org/

7. Electronic Industries Association (EIA) Standards.

Electronic Industries Association (Alliance) 2001 Pennsylvania Avenue NW Washington DC 20006

(202) 457-4942 http://www.eia.org/

8. Institute of Electrical and Electronics Engineers (IEEE) Standards.

Institute of Electrical and Electronics Engineers 445 Hoes Lane PO Box 1331 Piscataway NJ 08855-1331 http://www.ieee.org/

9. International Standards Organization (ISO) Documents.

American National Standards Institute 1430 Broadway New York, NY 10018 http://www.iso.ch/iso/en/ISOOnline.openerpage

10. Data Interchange Standards Community (E- Business) Data Interchange Standards Community 333 John Carlyle Street Suite 600

Alexandria, VA 22314 http://www.disa.org/

11. International Committee for Information Technology Standards INCITS Secretariat c/o Information Technology Industry Council 1250 Eye Street NW Suite 200 Washington D.C. 20005 http://www.ncits.org/

12. International Telecommunications Union

ITU

Place des Nations CH-1211 Geneva 20 Switzerland http://www.itu.int/home/

13Unified Facilities Criteria (UFC) UFC-3-580-01 22 June 2007 Telecommunications Building Cabling System Planning, Design and Estimating

Whole Building Design Guide http://www.wbdg.org/references/docs_refs.php

14. Telecommunications Industry Association (TIA) 1320 N. Courthouse Rd., Suite 200 Arlington, VA 22201 http://www.tiaonline.org

3.13 System Installation Plan (SIP) / Project Support Agreement (PSA) A System Installation Plan (SIP) / Project Support Agreement (PSA) is required for this PWS no later than thirty

(30) days prior to project installation. The SIP/PSA shall be approved by Fort Huachuca prior to the start of any onsite work. The system must be installed with little or no disruption to existing services. Any disruption of service must be coordinated with the Fort Huachuca.

3.14 System Turn Over

The Contractor shall assist the Government in completing the AFTO Form 747, Communications and Information Systems Acceptance Certificate. Configuration Management information shall be provided to Government MFT and each site awarded as part of this PWS as PDF files. The Contractor shall provide as-built documentation including, but not limited to:

a) Bayface layout drawings and diagrams of the chassis/shelf/cabinet identifying installed cards, modules, equipment, etc.

b) The as-built documentation shall also include cable and power drawings/specifications, floor plans, and engineering specifications generated in support of the installation of the system.

c) The documentation shall include drawings that depict the overall installed system configuration and network topology.

d) Documentation shall also include an equipment listing with serial/model numbers and manufacturer specifications.

e) The Contractor shall provide an inventory of any newly installed equipment and software, identification of test results, site-specific “as-built” engineering drawings, and a summary of any open items.

f) Completed test results.

All upgrade and reconfigured equipment and material (i.e., cabinets, racks, termination blocks, patching, cables, etc.) shall be permanently identified through stenciling or tags. Hand written tags are not permitted. Red-lined drawings are unacceptable. All network are considered both sensitive and proprietary.

3.15 Associate Contractor Agreements

When applicable, the Contractor shall enter into Associate Contractor Agreements (ACA) with the following Contractors. The agreement is to purchase, license and enable the NG911 module to create the NENA file required for populating the ALI database.

The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the NG911 System, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

Associate contractors are listed in (3.15.1) below.

ACAs shall include the following general information:

Identify the associate contractors and their relationships.

Identify the program involved and the relevant Government contracts of the associate contractors.

Describe the associate contractor interfaces by general subject matter.

Specify the categories of information to be exchanged or support to be provided.

Include the expiration date (or event) of the ACA.

Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

The Contractor shall have fourteen (14) days to provide a copy of the agreement to the Contracting Officer if requested.

The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

3.15.1 The following associate contractors with whom agreements may be required:

3.15.1.1 Unique Communications

3.16 Performance of Services During Crisis

Performance of Services During Crisis Declared by the National Command Authority or Overseas Combatant Commander. Services covered by this task are determined to be non-mission essential for performance during crises according to DoDI 3020.37. However, in the event of a crisis, or a significant emergency is declared, the Contracting Officer will contact the Contractor to notify them of the situation and any possible changes to responsibilities. Upon notification, the Contractor shall perform special event services due to contingencies, natural disasters, including facility operation on an extended basis up to 24 hours per day, etc, as required. In the event of verbal notification, written confirmation of such notification will be provided within 5 calendar days. If addition costs are incurred under this paragraph the Contractor shall have up to 30 calendar days to request equitable contract price adjustment.

4. TECHNICAL REQUIREMENTS

4.1 Baseline

Unless otherwise specified in the following paragraphs, the base shall receive baseline requirements for an NG911 system as described in Section 4.2. The Government reserves the right to award all, some or none of the line items listed.

The contractor shall be responsible for providing all premise wiring and networking elements to facilitate the requirements that support the system connectivity from the demarcation or the fiber patch panel.

4.2 Fort Huachuca

The Contractor shall provide an NG911 solution with the minimum requirements as outlined. The contractor shall provide software licenses, hardware components, cabinets, cabling to facilitate a central equipment system with required UPS system, LD VoIP Card, System Server Applications, GPS Netclock capability, router and other require/related equipment/software to install a functional NG911 system. The contractor shall provide PSAP and accessories to support three positions (two at consolidated dispatch center and one at fire station 1), and required monitors licenses, mapping software, wireless headsets and other required/related equipment/software/licenses to install three dispatch positions. The contractor shall install the additional capabilities of Text to 911, digital recording and immediate playback, ANI/ALI capabilities, and other State of Arizona NG911 required capabilities.

System components subject to wear or beyond their projected life cycle (i.e. servers, PCs, displays, keyboards, Ethernet switches, etc.) shall be replaced to effectively refresh the system and provide with the full operational capabilities.

The proposal shall include the decommissioning and removal of the existing E911 system and associated equipment/wiring where applicable. Any equipment removal and/or disposal shall be coordinated with a designated official at the host base and disposition thereof shall be in accordance with the host base instructions.

4.3 Baseline Requirement

The minimum requirement is to equip the PSAP with 2 Intelligent Call Taker Workstations/NG911 operator consoles. The system shall include all hardware, software, installation, and training services. Location of system assets are as follows:

Host Server A - Bldg 31044 Call Taker Positions o 2 Consoles at Building 31044, Consolidated Dispatch Center o 1 Console or Mobile Call Taker Computers at Building 51028 (Fire Station 1)

The system shall provide full host core redundancy including but not limited to servers, switches, gateways etc. with automatic failover eliminating single points of failure in the call path. The host cores shall be installed in a geo-diverse configuration.

The government to provide diverse fiber paths where applicable to provide redundant connectivity between facilities. The system shall provide flexibility and expansion capability to provide an increase in the number of consoles at each location to support additional technicians, administrators, helpdesk supervisors and calls. The system shall provide, at a minimum, the following features:

Computerized Telephony Integration (CTI) for IWS Provide the ability to support the base’s migration from legacy TDM platforms to VoIP, regardless of VSS manufacture and without requiring NG911 system replacement or major modifications. The proposed solution shall interconnect to each of the base’s voice switches simultaneously and independently as defined, without dependency on a single voice switch to be the 9-1-1 call aggregator.

Integrated Telecommunication Device for the Deaf (TDD/TTY) capability at each call taker position without need for additional hardware such as phone couplers.

The system shall include a Digital Logging Recorder (DLR) that archives recordings to internal hard disk drive and the ability to transfer recordings to Digital Versatile Disc (DVD) or other portable, digital electronically recorded media and include features to capture of Date/Time, Automatic Number Identification (ANI) / Automatic Location Information (ALI) data associated with each incoming call recorded. All communications at the call taker console level shall be recorded. See Siet Survey Data document for noumber of discreet channel to be recorded.

Redundant instances of a private, on premise ALI database for all on-base VSS devices. This solution shall accept automatic location data updates from the CAIRS TMS ALISON module.

The system shall provide a management information and reports application shall provide reporting metrics that describe the health of the system. Additionally system shall also track and report call center metrics to include average call volume, duration to answer, lost calls, as well as calls divided by 911 trunk and agent designation.

The system shall have an Environmental Systems Research Institute (ESRI) Geographic Information System (GIS) based map application. The system shall provide a means of distributing and synchronizing map data updates across all system CPUs (server and position) from a dedicated administrator workstation.

The system shall provide a Network Time Protocol (NTP) server to synchronize the time on all system CPUs (servers, workstations, logger/archiver, etc.). The NTP server shall derive system time from the Global Positioning Satellite (GPS) system. This system shall include a GPS receiver and GPS antenna with associated cabling. Signal amplifiers may be used when required. A surge protection device shall be installed to protect the NetClock receiver and connected devices from lightning damage.

The system shall support calls from on base PBX/VSS (DSN) wire-line extensions, PSTN (commercial) wire-line (housing, on-base contractors, vendors, etc.), and commercial wireless sources. Call routing for all PSTN 911 calls shall be based on the associated Emergency Service Number, automatically delivering the call to the designated on-base PSAP.

All NG911 call data shall display on the operator workstations including the calling party’s Automatic Number Identification (ANI) and the location of the caller (ALI). Call data shall be displayed textually and plotted to the map. Based on the call source ANI, the Automatic Location Information (ALI) shall be derived from a current data directory provided as follows:

a. DSN PBX/VSS Call Source: This system shall provide a private ALI database system

(hardware and software) to store phone set location information associated with the appropriate PBX extension number. This private ALI database system shall be installed on the Air Force premises. Note: The source for this ALI data shall be provided by the Government in the form of a compatible extract file format.

b. PSTN (Commercial) Wire-Line Call Source (CONUS): The system shall provide an interface to NG911 trunk circuits (aka CAMA) provided by the local commercial telephone Local Exchange Carrier (LEC) to deliver NG911 caller voice and ANI data from PSTN commercial wire-line (traditional POTS or VoIP) telephone numbers. The system shall include the capability to interface via ALI modems to query for) ALI from the database provided by the LEC, based on ANI data delivered with the call via the NG911 (CAMA) trunks with ability to support both RFAI and NENA i3 standards with minor reconfiguration requirements.

c. PSTN (Commercial) Wireless Call Source (CONUS): The Contractor shall provide, as part of this system, the provision to interface to NG911 trunk circuits (aka CAMA) provided by the local commercial telephone LEC and deliver caller voice and ANI data for processing NG911 calls from commercially provided wireless carriers. The system shall include the capability to interface to ALI modems, to query ALI from the database provided by the LEC, based on ANI data delivered with the call via the NG911 (CAMA) trunks with ability to support both RFAI and NENA i3 standards with minor reconfiguration requirements. The system shall be capable of supporting Phase I and Phase II compliant wireless calls and location data.

Note: NG911 trunks and ALI circuits for commercial wire-line and wireless calls to be provided by the Government. Contractor shall provide all equipment, materials and associated services in the form of installation, setup, test, commissioning and end user training to connect to the Government-furnished CAMA and ALI circuits.

Except where indicated, the Contractor shall be required to provide all services, equipment, and associated materials in the form of installation, setup, test, commissioning, and end user training for the new system. The Contractor shall provide all labor, parts, tools, supervision, and skill/expertise necessary to meet the requirements defined in this

PWS.

4.3.1 System Requirements

The NG911 system shall meet the following minimum performance and physical requirements.

4.3.1.1 Performance

The following performance requirements shall be met.

4.3.1.1.1 Voice Switching System Interoperability

The system shall be interoperable with and directly interconnect to Fort Huachuca Host Voice Switching Systems (VSS) that performs the base level voice communications and unified capabilities. At a minimum the system shall directly interface with Multi-Function Soft Switches (MFSS), WAN Soft Switches (WANSS), Multi-Function Switches (MFS), Local Session Controllers (LSC), End Offices (EOs), and PBXs without use of phone set interface/emulation or the addition of a PBX or LSC. It is acceptable for the proposed system to offer soft-phone application that is integrated with the system.

4.3.2 Physical Characteristics

The system shall meet all of the following requirements:

4.3.2.1 Dimensions

The core backroom/server equipment shall be 19–inch rack mountable to the maximum extent possible. The equipment shall adhere to best commercial practices when not rack mountable.

4.3.2.2 Sever Uninterruptible Power Supply (UPS)

A new UPS shall be provided.

4.3.3 System Capabilities

The system capabilities shall meet the following functional requirements:

4.3.3.1 Call Taker Workstation

The call taker workstation shall utilize Computerized Telephony Integration (CTI) to present NG911 calls with ANI and ALI to the screen. Each call taker position shall provide:

4.3.3.1.1 PSAP Equipment Compatibility

Call taker positions shall be NENA2-compliant Intelligent Workstations (IWS). IWS shall be compatible with the NENA-compliant PSAP core backroom system servers and is a current production product from the same manufacturer.

The minimum requirements for the workstations shall meet the following specifications:

Call Taker Workstation Minimum Specification (or equivalents) Chip Set AMD® A78 FCH Chipset

CPU

AMD PRO A10-9700E 3.0G 2M Quad Core 35W APU with AMD Radeon R7 HD Graphics

Expansion Bays 1 x 2.5” internal storage drive bay

Expansion Slots

(1) internal M.2 connector for optional wireless NIC

(1) internal M.2 connector for optional SSD drive

Hard Drive 500 GB SATA 5400rpm 8gb HDD Keyboard USB Standard Keyboard Mouse USB optical 2-Button scrolling mouse carbon

NIC

Broadcom NetXtreme Gigabit Ethernet Plus – DASH compliant NIC (integrated)

Ports USB 3.0 x 4 (2 rear, 2 front); USB 2.0 x 2 (rear), 1 x VGA, 2 x DP, 1 x RJ45, 3.5mm headphone output and microphone jacks (front)

Power Supply 65W DM External Power Adapter

RAM 4GB (1X4GB) DDR4-2133 SODIMM RAM

Software Microsoft Windos 11 Pro 64-bit OS US Software EliteDesk 705 Country Kit US Video AMD Radeon HD Graphics (integrated on processor)

2nd Display Port 2nd Display Port (Required selection if the Desktop Mini HDMI port or Desktop Mini Serial Port card is not selected. May not be combined with the HDMI or Serial Port cards)

Warranty 3 year parts/labor, 9-5, NBD

Weight/Dimensions Chassis (W x H x D) 6.9 x 1.3 x 7.0 in Standard weight - 2.9lb; Shipping weight 9lb

4.3.3.1.2…