N3943019R2128.pdf

SEE ADDENDUM

(No Collect Calls)

N3943019R2128 17-Sep-2019

b. TELEPHONE NUMBER

805-982-3872

8. OFFER DUE DATE/LOCAL TIME

04:00 PM 17 Oct 2019

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

N394309. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

WILLIAM J. HEPLER

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

1 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ACQR5626176

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

NAVFAC EXWC

CODE ACQ / NAVAL BASE VENTURA COUNTY

1100 23RD AVE BLDG 1100

PORT HUENEME CA 93043-4301

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE N39430 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

NAVFAC EXWC

TROY CULLISON

CODE ATFP

1000 23RD AVE

PORT HUENEME CA 93043-4301

TEL: 805-982-2372 FAX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$11,000,000

NAICS:

811213

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF90

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

N3943019R2128

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Project Base Year

FFP

ELMR Sustainment FOB: Destination

PURCHASE REQUEST NUMBER: ACQR5626176

PSC CD: J058

NET AMT

0002 12 Project OPTION Option Year 1

FFP

ELMR Sustainment FOB: Destination

0003 12 Project OPTION Option Year 2

FFP

ELMR Sustainment FOB: Destination

0004 6 Project OPTION Extension of Services

FFP

ELMR Sustainment FOB: Destination

ADDENDA TO 52.212-1

The Government intends to award a contract to Motorolla Solutions Inc. after determining the firm is responsible, has a record of satisfactory past performance and that the price is fair and reasonable.

Motorolla is requested to submit a response to the performance work statement (PWS) that addresses their understanding and solution to the requirements. No information regarding past performance need be submitted.

The Contracting Officer has determined that this proposal will require the submission of other than certified cost or pricing data. To the extent the offeror is able to provide pricing data, such as prior sales data, that demonstrates that the same or similar items have been previously sold in the commercial market place for similar quantities, then no further information needs be provided. For areas where the offeror is unable to demonstrate that the same or similar items have been previously sold in the commercial market place for similar quantities, the information requested below should be used to supplement the price proposal. If Data Other than Certified Cost or Pricing Data is refused, we will implement the procedures found at PGI 215.404-1(a)(i)(A) to attempt to resolve.

Direct labor:

Provide a schedule breakdown of total proposed direct labor dollars detailing proposed labor hours by labor categories (skill) multiplied by the proposed direct labor base wage rates. The narrative should include:

1) The basis of estimate for the quantity of labor hours proposed.

2) Identify the rationale for the labor mix and experience of direct labor positions.

3) The basis of estimate for the proposed labor rates.

a. Identify if rates are actual individual or blended rates.

b. Identify the date the actual individual rates are effective, if applicable.

c. Provide the listing of rates that are used to calculate a blended rate, if applicable.

d. Identify source of rates (Payroll records, FPRA, etc.)

4) If escalation is used for out-year labor rates, provide the basis of estimate for escalation.

Material:

Provide a consolidated priced bill of material detailing proposed material types, kinds, quantities, proposed unit prices. The schedule narrative and/or notes should include:

1) The basis of estimate for the proposed quantity of materials, including any allowance for scrap or variation.

2) Provide the source of the pricing.

a. If based on adequate competition, provide substantiating quotes and analysis.

b. If sole source, provide rationale and price analysis with in-house estimates, historical data, etc. Provide copy of supplier certified cost or pricing data, if required to be obtained (FAR 15.404-3 (c)(1))

c. If based on historical data, provide substantiating data and the basis of estimate for any escalation applied.

Equipment:

1) Provide basis of estimate for quantity and duration of equipment.

2) Identify if equipment is leased, purchased, or from inventory.

a. Provide lease v. purchase analysis for equipment purchased or leased.

b. If used from inventory, provide basis for usage charge.

c. Provide competitive quotes and analysis for lease or purchase.

d. If sole source, provide rationale and price analysis with in-house estimates, historical data, etc.

Travel:

Provide a schedule of total proposed travel costs which details trip to and from location, number of travel days, daily cost of lodging, meals, airfare, rental vehicles, and incidentals, as applicable. The schedule narrative should include:

1) Provide basis of estimate for quantity and costs.

a. Provide substantiating records for costs such as airfare, rental vehicles, lodging and per diem.

SubContracts:

Provide a schedule of total proposed subcontract costs which breaks out the subcontracted cost by subcontractor.

The schedule narrative and/or notes should include:

1) Provide an explanation of the scope of work the subcontractor(s) will perform.

2) Provide the source of the pricing.

a. If based on adequate competition, provide substantiating quotes and analysis.

b. If sole source, provide rationale and price analysis with in-house estimates, historical data, etc. Provide copy of subcontractor certified cost or pricing data, if required to be obtained (FAR 15.404-3 (c)(1))

c. If based on historical data, provide substantiating data and the basis of estimate for any escalation applied.

SPECIAL CONTRACT REQUIREMENTS

1. ECMRA Reporting: The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the NAVFAC EXWC via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address:

https://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.ecmra.mil.

2. Insurance: The following types of insurance are required in accordance with the clause entitled “52.228-5 -- Insurance -- Work on a Government Installation” (FAR 52.228-5, incorporated by reference) and shall be maintained in the minimum amount shown:

(a) Workers’ compensation and employer’s liability. Contractor shall comply with applicable Federal and State workers’ compensation and occupational disease statutes. If occupational diseases are not compensable under those statutes, they shall be covered under the employer’s liability section of the insurance policy, except when contract operations are so commingled with a contractor’s commercial operations that it would not be practical to require this coverage. Employer’s liability coverage of at least $100,000 shall be maintained, except in States with exclusive or monopolistic funds that do not permit workers’ compensation to be written by private carriers.

(b) General liability.

(1) Contractor shall maintain bodily injury liability insurance coverage written on the comprehensive form of policy of at least $500,000 per occurrence.

(c) Automobile liability. Contractor shall maintain automobile liability insurance written on the comprehensive form of policy. The policy shall provide for bodily injury and property damage liability covering the operation of all automobiles used in connection with performing the contract. Policies covering automobiles operated in the United States shall provide coverage of at least $200,000 per person and $500,000 per occurrence for bodily injury and $20,000 per occurrence for property damage. The amount of liability coverage on other policies shall be commensurate with any legal requirements of the locality and sufficient to meet normal and customary claims.

PERFORMANCE WORK STATEMENT

1.0 SCOPE

The AT/FP Ashore Enterprise Land Mobile Radio (ELMR) Sustainment Contract covers full system support during the Sustainment Phase of Enterprise Land Mobile Radio project to include all system related hardware, associated firmware, and software associated under Appendix C “Lists of Systems” plus Post-Award installation of new AT/FP ELMR Systems/equipment and required software. This contract Performance Work Statement (PWS) details services to be provided by the Contractor to include corrective and preventive maintenance of the systems/equipment, and the response and resolution of Service Calls. The scope of this AT/FP Ashore ELMR Sustainment Contract is to provide centrally-managed sustainment of the Navy’s ELMR System/hardware and software identified in this PWS and supporting documents. Navy Regions included in this Contract include all Continental United States (CONUS) Regions (except Naval District Washington (NDW)) and the Outside Continental United States ( OCONUS) Regions of Navy Region Europe, Africa Central (EURAFCENT), Commander Navy Region Japan (CNRJ), and Joint Region Marianas (JRM).

The intent of this AT/FP Ashore ELMR Sustainment Contract is to effectively procure the equivalent of a full maintenance warranty for the AT/FP Ashore ELMR System with associated equipment and software, including all of the hardware, firmware, and cabling or other signal/data transmission sub-systems necessary for the system to function as intended during operations. Sustainment is defined as all work and costs associated with maintaining and repairing systems, associated software and material as required to enable the System to perform as specified.

This PWS does not include warranty or sustainment services for the Navy information transport network known as the Public Safety Network (PS-Net) that is used by the ELMR System for data connectivity.

This AT/FP Ashore ELMR Sustainment PWS describes the requirements to provide the support needed to carry out the day-to-day sustainment and maintenance of AT/FP Ashore ELMR System hardware, associated software and related services which are summarized as follows:

• Sustainment of existing AT/FP Ashore ELMR equipment to include associated hardware and software management; Microwave systems as identified in this PWS, and Uninterruptible Power Supply (UPS) units as identified in this PWS.

o Corrective and Preventive Maintenance as required to maintain the Operational Availability (Ao) requirements identified in this contract.

• Service Call Management to provide end-to-end sustainment support to include:

o Response and Resolution of Service Calls o Preventive and Corrective Maintenance o Asset and Configuration Management as required to maintain specified Operational Availability o Contract Support and Data Requirements as required

• The Contractor shall provide a person to be positioned at the following Zone Core locations for a total of 40 hours per week at each facility. Roles and Responsibilities for the ELMR Sustainment Contractor representative providing support at the Zone Core are set forth in paragraph 4.4.6 Zone Core Technical Support.

o Zone 2 (Norfolk, VA) o Zone 3 Primary (Yokosuka, Japan) o Zone 3 Backup (Finegayan, Guam) o Zone 5 (San Diego, CA) o Zone 6 (Sigonella, Italy) o Zone 7 (Manama, Bahrain)

• Managing software licenses and renewals and maintaining software up to date. Support includes the installation of the software and any appropriate Cybersecurity approvals that the update may require. This includes updates to DADMS, NITEP, and the software list within the ELMR ATO in eMASS. For Contractor system software, the contractor will provide software updates for current versions supported through the Security Update Service (SUS) and consistent with company release policies. The contractor will maintain software licenses and renewals during the course of the contract as well as any cost associated with software licenses known to Motorola at the time of the initial award of a contract.

• Implementation of Cybersecurity policy across the Enterprise. Generally, the contract’s performance and compliance with the various technical requirements specified in this contract are based upon the versions/revision levels referenced in this contract. Due to the fluid nature of Cybersecurity and the need to maintain the security posture of DON networks, there is the potential for changes in equipment, software, processes or security requirements due to Cyber threats that were not known at award. The contractor shall be informed of these changes and the Navy will provide these new requirements to the contractor.

Performance/compliance to subsequent versions/revision levels not part of the obsolescence management in paragraph 4. 6 and or changes not specifically detailed in this PWS are considered out of scope of the contract and would be subject to a change order to adjust the price and/ or schedule of the contract. This includes required changes in equipment, software, processes, cybersecurity/Information Assurance, security requirements and any other change not specifically detailed in this PWS on the date of execution. In these cases, the contractor shall provide a proposal and schedule when work may begin. In cases that involve changes and would require requirements to be provided, the Navy shall provide written and approved requirements to the contractor at least 90 days prior to the contractor providing a proposal and schedule for work.

o The contractor will not be responsible for accreditation or Information Assurance related tasks on the microwave system referred to in this PWS.

• Technical refresh of software and equipment required to maintain the required Ao and to maintain Cybersecurity Assessment and Authorization (A&A).

1.1 Order of Precedence

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations, including contract clauses, unless a specific exemption has been obtained in writing.

1.2 Objective

The intent is to have the Contractor conduct both preventive and corrective maintenance as required to meet the system Ao of 0.9995 (excluding planned maintenance as per paragraph 4.2.3 Preventive Maintenance Down-time) as required by the National Fire Protection Association (NFPA) 1221 “Standard for the Installation, Maintenance and Use of Emergency Services Communications Systems”. Further, the Contractor shall maintain the designated time periods listed in Table 2 “Technical Support Response and Resolution Time”. The effort will require advance preparation by the Contractor to include, but not limited to, positioning of technician personnel and housing spare parts at locally-accessible storage facilities.

1.3 System Description

The ELMR system is a digital trunked land mobile radio (LMR) system fielded to coordinate the deployment and actions of the first responder community. It is recognized that effective emergency communications is a key element in reducing the loss of life and property in any crisis or incident. The ELMR network allows a coordinated response between Navy emergency services and other federal, state and local agencies involved in public safety.

Additionally, ELMR will provide interoperability within and between the service components.

The ELMR system is the Navy’s solution to the Deputy Secretary of Defense Land Mobile Radio Policy memorandum dated 01 August 2001. The Policy directed the following:

• Compliance with the National Telecommunications and Information Administration (NTIA) mandate to transition to narrowband operations (12.5 KHz) on VHF 162-174 MHz by 1 January 2005, VHF 138 -

150.8 MHz, and UHF 406.1-420 MHz by 1 January 2008,

• Conformance with the TIA-102 Project 25 (P25) standards,

• Incorporation of an interoperability solution with other federal, state, and local first responders during times of national, state, or local emergencies without violating current rules and regulations concerning the national spectrum management policy.

The Navy ELMR network is a multi-zone trunked repeater system that is compliant with the TIA-102 Project 25 (P25) standard. The P25 standard is a set of protocols established to support interoperability between Public Safety radios from different radio manufacturers. In the ELMR system network, the zone core is the central source of network services and control. High availability of the network is achieved with multiple Master Site Zone Core switching centers to provide centralized system management and redundant call processing capability, redundant data controllers, security management, authentication, and network management along with dual network transport equipment. ELMR system equipment for all locations within the Continental United States (CONUS) are serviced by two (2) Master Site Zone Cores operating with Dynamic Site Resilience (DSR). Site Resilience provides for mutual site backup capabilities between two zone cores, assuming voice call routing and other system duties upon the failure of its assigned partner Zone Core. In this manner, each ELMR system equipment site has a primary Zone Core with a secondary Zone Core always ready to immediately assume traffic routing as a measure of redundancy for a failure at the primary. Radio users will notice little or no effect of the switch between primary and secondary other than a drop of a radio call that was in progress which may then be immediately re-initiated. Establishing links from each remote site (i.e., repeater, dispatch, network management, etc.) to both zone cores increases network resiliency and retains continuity of operations if a remote site loses connectivity with its primary core.

The two Master Zone Cores that provide service to the CONUS ELMR system equipment are located in the Service Delivery Point (SDP) West in San Diego, California and the SDP East located in Norfolk, Virginia. The two Master Site Zone Cores that provide Site Resilient primary and secondary service to ELMR system equipment in Navy Region Europe, Africa Central (Navy Region EURAFCENT) are located in the Operations Control Center Sigonella at Naval Air Station (NAS) Sigonella Italy and in the ELMR shelter in Manama Bahrain at Naval Support Activity (NSA) Bahrain. The Master Site Zone Core that provides service to Commander, Navy Region Japan (CNRJ) and Joint Region Marianas Guam ELMR sites is located in the Commander Fleet Activity Yokosuka building in Yokosuka, Japan. The Site Resilient secondary site is located in NAVCOMTELSTA Guam in Finegayan, Guam.

This Contract Performance Work Statement (PWS) is intended to address the sustainment requirements of the ELMR system infrastructure items and not the ELMR subscriber items, such as portable radios, vehicle radios, or fixed base station radios that connect to the ELMR system solely using wireless, push-to-talk transmissions.

Appendix C “List of Systems” establishes the contractual requirements for systems to be supported under the terms and conditions of this PWS. The Contractor shall sustain listed systems at the locations identified in the Appendix C. Actual system subcomponents may differ from one location to another; however, the Contractor shall be responsible for sustaining the system and all subcomponents, associated firmware and software thereunder.

Subcomponent Detail, such as Microwave sites and Uninterruptible Power Supply (UPS) units currently being sustained under this contract, is provided in Appendix M.

NOTE: The systems and equipment in Joint Region Mariannas (JRM) are currently under enhanced warranty as “Best Effort” under a separate contract. Best Effort is defined later in this contract. The Best Effort contract support ends 18 July 2020. This ELMR contract provides for onsite personnel from contract award to 18 July 2020, thus increasing the JRM support from Best Effort to full support as defined in this contract. This ELMR contract will continue to provide full support of JRM systems and equipment starting on 19 July 2020.

2.0 REFERENCES

All reference documents are intended to be used for guidance only, unless compliance is required within the body of this PWS. Guidance documents may be used as an aid in identifying applicable topics to be addressed consistent with meeting the objectives of the NAVFAC AT/FP program. The Contractor shall propose alternatives, as required, to the specifications and standards cited herein if they would enhance system performance or cost effectiveness. Unless otherwise specified, the issues of Government documents are those listed in the current version of the Department of Defense (DoD) Information Technology (IT) Standards Registry (DISR) on the date of this specification. The issues of Industry standards are those in effect on the date of this specification.

The references identified below apply to this PWS. Changes to listed references and/or standards shall be evaluated by the contractor, and in instances where the contractor determines changes result in an increased cost or effort, the contractor shall submit an Engineering Change Proposal in accordance with this PWS.

2.1 Department of Defense

NUMBER DATE TITLE

CNICINST 2300.1 Draft v1.0 Enterprise Land Mobile Radio Account Management

COMSPAWAR M-3090.2C-M 07/10/2017 Fleet Readiness Certification Board (FRCB) Handbook

DDCIO (N) 08/04/2017 Risk Management Framework Process Guide v2.0

DFARS 252.211-7003 Rev 05/28/2014 Item Unique Identification and Valuation

DISR 05-1.0 04/25/2005 Department of Defense Information Technology Standards

Registry

DoD 5200.08-R 04/09/2007 DoD Physical Security Program

DoD 5200.28-STD DoD Trusted Computer System Evaluation Criteria

DoD A/E/C CAD STD R5.0 U.S. National CAC Standard (NCS)

DoD DAG 09/15/2012 Department of Defense Guide to Uniquely Identifying Items, Assuring Valuation, Accountability and Control of Government Property, Version 2.5

Defense Acquisition Guidebook (DAG) (Available on-line at https://dag.dau.mil/Pages/Default.aspx)

DoDD 5000.1 05/12/2003 Operation of the Defense Acquisition System

DoDD 5200.1 12/13/1996 DoD Information Security Program

DoDD 5200.28 03/21/1988 Security Requirements for Automated Information Systems

DoDD 8100.2 04/14/2004 Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid

(GIG)

DoDD 8140.01 07/31/2017 Cyberspace Workforce Management, with Change 1

DoDD C-5200.5 04/21/1990 Communications Security

(COMSEC)

DoDI 5200.08 12/10/2005 Security of DoD Installations and Resources

DoDI 5215.2 Computer Security Technical Vulnerability Reporting Program

(CSTVRP)

DoDI 7730.47 Defense Incident-Based Reporting

DoDI 8500.01 03/14/2014 Cybersecurity

DoDI 8510.01 07/28/2017 Risk Management Framework (RMF) for DoD Information

Technology

DoDI 8520.02 04/24/2011 Public Key Infrastructure (PKI) and Public Key (PK) Enabling

DoDI 8520.03 05/13/2011 Identity Authentication for Information Systems

DoDM 5200.01 Vol 1-4 02/24/2012 DoD Information Security Program

(DTM) 08-006 11/26/2008 DoD Implementation of Homeland Security Presidential Directive

-12

(HSPD-12)

ELMR CONOPS v2.05 02/24/2014 Commander Navy Installations Command (CNIC) Concept of

Operations for the U.S. Navy Enterprise Land Mobile Radio

(ELMR)

EM 385-1-1 08/11/2011 Army Corps of Engineers Safety Manual

MIL-HDBK-235/1B 12/22/2000 Electromagnetic (Radiated) Environment Considerations for

Design & Procurement of Electrical & Electronic Equipment, Subsystems & Systems

MIL-HDBK-338B 10/01/1998 Electronic Reliability Design

MIL-HDBK-1013/1A Design Guidance for Physical Security Facilities

MIL-HDBK-2036 11/01/1999 Electronic Equipment Specifications, Preparation of

MIL-STD-130N, with Change 1 11/16/2012 Department of Defense Standard Practice Identification Marking of U.S.

Military Property

MIL-STD-461E 08/20/1999 Requirements for the Control of Electromagnetic Interference

Characteristics of Subsystems and Equipment

MIL-STD-464A 12/19/2002 Electromagnetic Environmental Effects Requirements for

Systems

MIL-STD-810G 08/10/2007 Test Standard for Environmental Engineering

MIL-STD-882D 02/10/2000 System Safety

MIL-STD-961E 08/01/2003 DoD Defense and Program-Unique Specifications Format and

Content

NAVNETWARCOMINST 12271.1 10/17/2006 Policy and Procedures for the Fleet Readiness Certification Board

(FRCB)

Process

OPNAV 3440.17 07/22/2005 Navy Installation Emergency Management Program Manual

OPNAVINST 2400.20F 07/19/2007 Electromagnetic Environmental Effects (E3) and Spectrum

Supportability Policy and Procedures

OPNAVINST 3000.12A 09/02/2003 Operational Availability Handbook

OPNAVINST 3440.17A 08/01/2014 Navy Installation Emergency Management Program

OPNAVINST 5530.14C Navy Physical Security

SECNAV-M 5239.1 11/2005 DoN Information Assurance Program

SECNAV-M 5239.2 06/2016 Cyberspace Information Technology and Cybersecurity

Workforce

Management and Qualification Manual

SECNAVINST 5510.36A 10/06/2006 DoN Information Security Program

SIPH v4.0 10/12/2014 SPAWAR Shore Installation Process Handbook version 4.0

2.1.1 Unified Facilities Guide Standards – http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc

UFGS-26 00 00.00 20 07/2006 Basic Electrical Materials and Methods

2.1.2 Unified Facilities Criteria – http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc

UFC 3-501-01 10/06/2015 Electrical Engineering 2

UFC 3-520-01 02/03/2010 Interior Electrical Systems, with Change 2

UFC-3-580-01N 06/22/2007 Telecommunications Building Cabling Systems Planning and

Design

UFC 4-020-01N 09/11/2008 DoD Security Engineering Facilities Planning Manual

UFC 3-580-10 04/12/2005 NMCI Standard Construction Practices, with Changes 1-3

FC 1-300-09N 06/14/2018 Design Procedures, with Change 4

2.1.3 Industry Standards

NFPA 1221 2016 Standard for the Installation, Maintenance, and Use of Emergency

Services Communications Systems

TIA 102 Series Project 25 System Standards

Note: For locations outside of the United States, the Contractor shall comply with equivalent standards from the Host Nation as required. Examples standards that apply are European Union Standards (CE), Japanese Architectural Standard Specifications (JASS), and Japanese Industrial Standards (JIS).

3.0 GENERAL REQUIREMENTS

The Navy’s sole overarching requirement for this contract is that its ELMR system remain in an operational and committable state to perform the function that it was designed, installed, and tested to do in order that it may be utilized to its fullest capacity at those critical moments in which it is needed to support the Navy’s mission.

This overarching requirement involves many aspects of planning, preparation, management and execution which are described in the following paragraphs.

3.1 Management of Operational Availability

Based on the statement of requirement expressed above, the most meaningful parameter for discussing the effectiveness of the sustainment effort is called Operational Availability (Ao). This parameter relates the percentage of time that the system remains in an “operational and committable state” (i.e. “up-time”) to the amount of time that it is not (i.e. “down-time”). The same figure can also be used to predict the probability that the system is in an “operational and committable state” at any future moment, including those critical moments in which it is needed.

Refer to OPNAVINST 3000.12A, “Operational Availability Handbook, A Practical Guide for Military Systems, Sub-Systems and Equipment”, for a further explanation of Ao and also DED A043 Trend Analysis Reports for calculation methods by the NAVFAC AT/FP Ashore program.

The Contractor shall strive to maximize the Ao of the ELMR System to the maximum extent practicable with a minimum threshold requirement of 99.95% (excluding planned maintenance as per paragraph 4.2 System Maintenance). This figure requires the ELMR System to remain free of Critical Priority fault conditions, as described in paragraph 4.3.1 Priority Level Assignments for System Fault Conditions, for 99.95% of the time. That calculates to a maximum amount of 4 hours and 23 minutes of down-time over the course of one calendar year.

The Contractor shall plan and implement a Supportability Strategy as described in paragraph 4.1 Supportability Strategy and DED A020 “Supportability Strategy” to facilitate this level of Operational Availability. Planning documents shall demonstrate how critical faults can be prevented and, should they occur, can be detected, responded to, diagnosed, and corrected in a manner that supports an Ao of 99.95%.

This will require the following:

• 24/7 monitoring capability,

• Positioning of replacement parts, qualified personnel, test equipment, etc. required to quickly diagnose and affect repairs,

• Robust and disciplined approach to periodic inspections, functionality tests, and preventive maintenance,

• An analysis of critical points of failure and strategies for either monitoring/quick repair or redundancy/backup measures that prevent a failure or maintenance down-time from creating a critical system outage,

• Disciplined approach to receiving, assignment, tracking, and closure of Service Calls using the U.S. Navy’s

Help Desk and AT/FP Ashore Remedy information system,

• Analysis of fault histories and fault trends to proactively predict and mitigate repetitive issues,

• Disciplined approach to configuration management and documentation to include adherence to and participation in the ELMR Engineering Review Board process, and

• Methodology to track the evolution of technology, identify issues within the ELMR System associated with technology obsolescence, and develop solutions that avoid down-time and maximize the longevity of the ELMR System.

3.1.1 Calculation of Ao

System Operational Availability (Ao) is defined by the equation:

Ao = Up-time / (Up-time + Down-time)N39430-16-C-1812

It should be noted that “up-time” and “down-time” are, by definition, two mutually exclusive states and that, taken together, they represent the total amount of time. Therefore, the equation may also be expressed as follows:

Ao = Up-time / Total Time

Therefore, the calculation of Ao requires a determination of when the system is in an “Up” state, and therefore available for use, and when it is in a “Down” state, existing in a degraded capacity such to render it “unavailable” if needed. For the purposes of planning and management of Ao, the failures which would constitute “down-time” of the ELMR System shall be those classified as a Critical Priority as specified by the Priority Level definitions found in paragraph 4.3.1 Priority Level Assignments for System Fault Conditions.

NAVFAC AT/FP Ashore generates a tri-annual report that calculates Ao for each installation, which aggregates to a Regional Ao, which finally aggregates to a Family of System (ELMR) Ao. This underlying data associated with this report is provided monthly to the Contractor for review and comments. It is the Contractor’s responsibility to review this monthly report and to inform NAVFAC AT/FP of any discrepancies they identify within 10 calendar days of receipt of report. This report utilizes the tickets within the NAVFAC AT/FP Ashore Remedy system and is considered the standard by which Ao calculations will be derived.

3.1.2 Applicability of Ao in Contractor Execution

While Ao is the most accurate statement of the U.S. Navy requirement, there are often complications which prevent the use of Ao as an accurate metric for measurement of Contractor performance. While a 99.95% Ao threshold requirement permits a maximum of 4 hours and 23 minutes of down-time within one calendar year (excluding planned maintenance as per paragraph 4.2.3 Preventive Maintenance Down-time), there is rarely a definitive record of the exact moments that the systems enters a “down” state and is then restored to an “up” state. There may also be confusion as to the classification of a particular outage event as meeting the criteria of “down-time”.

For these reasons, Ao cannot be the sole determining factor of Contractor performance in the execution of this PWS.

It will be used only as an “order-of-magnitude” guideline to identify gross infractions of contractual requirements.

The paragraphs that follow in Section 4.0 will outline other measurement criteria such as Response Time and Resolution Time which are more practical for managing the day-to-day sustainment operations under this PWS.

In spite of these practical limitations, the Contractor shall continue to plan and implement strategies using the maximization of Ao as the overarching strategic objective.

4.0 SPECIFIC REQUIREMENTS

This section details sustainment task requirements for the Contractor in execution of this PWS.

4.1 Supportability Strategy

The Contractor shall develop and implement a comprehensive, cost-effective Supportability Strategy for the ELMR System to ensure that the systems/equipment described herein meet the mandated mission performance thresholds for Operational Availability. The Supportability Strategy shall include the periodic maintenance, repair, replacement, and overhaul of existing systems, hardware, software, and firmware associated with Appendix C “List of System Equipment” and shall be prepared in accordance with DED A020 “Supportability Strategy”.

The Supportability Strategy shall include the Contractor’s approach to:

• Centrally monitoring the health and status of the ELMR System during real-time operations,

• Logistically locate replacement parts at forward supply points,

• Position qualified personnel, test equipment, etc. needed to quickly diagnose and affect repairs,

• Plan, perform, and document periodic inspections, and preventive maintenance,

• Identify critical system operations and implement strategies to prevent potential failures or administrative down-time from creating a critical system outage,

• Analyze fault histories and fault trends to proactively predict and mitigate repetitive issues,

• Track the evolution of technology, predict issues that will result from technology obsolescence, and develop solutions that extend the viability of ELMR System into the foreseeable future, and

• Identify the Service Level Agreement or other business relationship to be established and maintained with

Original Equipment Manufacturers (OEM) to allow continued support of the ELMR System, whether it be using materials and training programs available commercially off-the-shelf, a Certified Service Provider arrangement, through sub-contract arrangement, or other business relationship.

4.2 System Maintenance

The Contractor shall perform Corrective and Preventive Maintenance on the ELMR System as detailed below.

4.2.1 Inspection and Preventive Maintenance

The Contractor shall periodically visit each system installation site for the performance of a Preventive Maintenance Inspection (PMI). PMI shall include a full and complete test of the ELMR system capability at that location that is sufficient to exercise all individual components and communication paths with the intent to discover any latent faults.

The Contractor shall perform preventive maintenance adhering to manufacturer’s guidelines, as documented in a PMI checklist. Should the ELMR capability include additional functionality that was customized for the Navy requirement, the Contractor shall develop new, additional steps for the testing, inspection, and preventive maintenance of that customized functionality; and incorporate the same into existing PMI checklists.

The PMI checklists shall be completed during the PMI to document all tests and measurements performed, components evaluated and results of those observations, and the maintenance actions taken at each site visited by the Contractor. The Contractor shall upload a signed copy of the completed PM checklist to the applicable PM Service Call in the AT/FP Ashore Remedy System.

Following completion of a PMI, the Contractor shall produce a PMI report. The PMI report shall include the following:

• The Preventive Maintenance Remedy ticket numbers for the PMs completed,

• The Corrective Maintenance Remedy ticket numbers if any for corrective maintenance that was required to correct any deficiencies,

• An initial statement that the entire ELMR capability at that location has been tested and maintenance service provided,

• Data sheets with PMI test results and detail of all actions taken to correct discovered deficiencies, and

• A listing of equipment, date, and place of database backups whenever performed in conjunction with a PMI event.

The statement shall be signed by a Contractor Representative and also by a local Navy customer representative.

PMI reports shall be provided to the NAVFAC AT/FP Ashore Program Sustainment Director within five (5) working days of PMI completion via upload to the AT/FP Ashore Information Module (AIM).

A PMI shall occur within a period not to exceed one year from the previous inspection. Beyond these minimum requirements, PMIs shall be performed more frequently as required to conform to manufacturer guidelines and the Contractor’s approved CDRL A017 “Maintenance Plan” submission in accordance with this PWS and DED A017 “Maintenance Plan”. Regardless of the actual periodicity specified (semi-annually, quarterly, or monthly) the intention of periodicity is to space the maintenance as evenly as possible over the designated period. As an example, “quarterly” PMs shall consist of four (4) PMIs, evenly distributed over a one-year period, i.e., every three-months, AND shall be completed within the month specified in the approved A017 Maintenance Plan CDRL submission.

Preventive Maintenance requirements are summarized as follows:

• The Contractor shall prepare a Preventive Maintenance Plan and Schedule for the ELMR system. The Plan shall be based upon the equipment manufacturer’s maintenance recommendations and standard industry practices and shall be prepared and submitted in accordance with DED A017, Maintenance Plan. The contractor shall upload and actively manage approved baseline Plan of Actions and Milestones (POA&M) on a monthly basis in the AT/FP Information Module (AIM).

• All Preventive Maintenance Schedules shall be identified in CDRL A002 “Program Schedule and Progress Report” submission by the Contractor in accordance with DED A002 “Program Schedule and Progress Report” and as described in paragraph 4.3.1 “Inspection and Preventive Maintenance”. The approved CDRL A002 “Program Schedule and Progress Report” submission shall be used to plan and track preventive maintenance activities for the duration of the period of performance in accordance with this PWS and DED A002 “Program Schedule and Progress Report”. The contractor shall synchronize any POA&M updates with the baseline schedules in AIM on a monthly basis.

• Preventive Maintenance shall be coordinated with NAVFAC AT/FP Ashore Program Facilities Engineering

Command Liaison (Liaison) and local N6. Preventive Maintenance activities shall be requested no less than thirty (30) days prior to the performance of the maintenance action.

• The Contractor shall provide all test equipment, tools, support equipment and supplies required to perform

Preventive Maintenance. Test equipment shall be calibrated according to manufacturer recommended standard and interval. The Contractor shall maintain calibration records for potential audit by the U.S.

Government.

• The Contractor shall notify the designated Navy Help Desk activity at least thirty (30) days in advance of a

Preventive Maintenance Inspection in order to have a “Routine” priority Service Call created and assigned back to the Contractor. This Service Call shall be used by the Contractor to document work performed during the maintenance activity in the AT/FP Ashore Remedy System. The Contractor shall update the Work Log and resolve the Service Call within the scheduled calendar month as determined by the Contractor’s approved A017 and A002 Maintenance schedule submissions.

• If a defect is found during PMI that requires a replacement part, the Contractor shall direct Navy 311 Helpdesk to create a new Corrective Maintenance Service Call within the AT/FP Ashore Remedy System, complete a CDRL A033 “Asset Data Template,” and upload that form into the Remedy Work Log when resolving the Service Call.

• Upon resolution of the PMI, the Contractor shall upload a signed copy of the completed PM checklist to the applicable PM Service Call in the AT/FP Ashore Remedy System.

The Contractor shall refer to Appendix B “Contractor User Guide for the AT/FP Ashore Remedy System and AT/FP Information Module (AIM) Portal” for specific instructions for updating Work Log entries and uploading attachments/reports.

4.2.1.1 ELMR Account Management

Contractor personnel will be assigned user and administrative accounts on the ELMR System following the guidelines listed below. Contractor personnel shall comply with Appendix E “CNIC Policy and Procedures Enterprise Land Mobile Radio (ELMR) Account Management SOP” on all accounts.

• Contractor technicians that access the ELMR System will be assigned an individual account whenever possible and shall not use system default accounts.

• All accounts shall require a CAC, PIV or Alt Token for access with the following exceptions: identity authentication under non-standard conditions or during contingency operations as described in DoDI 8520.03;

accounts on devices where PKI/PKE cannot be implemented.

• All contractor technicians shall sign a Privileged User Account form for all System Administration accounts and Regular User Accounts and shall file a System Access Authorization Request - Navy (SAAR-N) form for all accounts on the ELMR System to include dispatch consoles. No generic logons are permitted on the system.

• The Contractor will manage the KMF Admin account and will setup accounts for the Government to use when performing KMF functions. User Accounts are to be entered into folders by Region. The Navy will be responsible for providing to Contractor in writing the appropriate account names that are associated with a specific region.

• The Unified Network Configurator (UNC) Admin account will be managed by the Contractor. The Contractor shall create Government UNC accounts as required and approved. Creation of Government UNC accounts shall be approved by the ELMR Engineering Review Board.

The Contractor shall establish and perform routine procedures to help identify Contractor user accounts that have remained inactive for more than thirty (30) days. Such records shall be identified to the Regional N6 and local Installation N6 departments, and the site’s NAVFAC Facilities Engineering Command Team Liaison for appropriate action.

4.2.2 Operational Data Management

For those ELMR System equipment that store and retrieve data to provide their functionality, the Contractor shall provide regular maintenance, backup, and restoration services. The requirements described herein form part of the base Performance Work Statement and are applicable to planning and execution of sustainment for all ELMR System equipment.

The Contractor shall establish and perform routine procedures to help identify database records that are outdated, corrupted, duplicated, incomplete, or may otherwise affect system performance. Such records shall be identified to the Regional N6 and local Installation N6 departments, and the site’s NAVFAC Facilities Engineering Command Team Liaison for appropriate action.

The Contractor shall perform periodic backups of stored data and shall store the most recent three sets of backup data in a geographically separate location, normally at the Contractor’s service shop. Database backups shall be performed on a regular schedule not to exceed one week intervals. The Contractor shall include the equipment, date, and place of database backups with PMI reports whenever performed in conjunction with a PMI event.

Otherwise, the information shall be reported separately to the NAVFAC AT/FP Ashore Program Sustainment Director.

When a system fault results in the loss of data, the Contractor shall restore the database using the most recent backup data available.

The Contractor is not responsible to maintain or off-line backup stored operational data that is not related to the functionality of the system. Examples include audio recordings of 9-1-1 telephone and radio traffic. However, functionality of the system to have primary and backup storage for 9-1-1 telephone and radio traffic shall be sustained.

4.2.3 Preventive Maintenance Down-time

Should maintenance activities require down-time of minor-level system functionality, the Contractor shall note the impact and duration of this planned down-time in the Contractor’s CDRL A017 Maintenance Plan submission in accordance with this PWS and DED A017 “Maintenance Plan” for Navy review and approval. Should the requirement for maintenance down-time meet the criteria for Ao “down-time” established in paragraph 3.1.1 Calculation of Ao, the Contractor shall request authorization for such down-time from the Base via the NAVFAC AT/FP Ashore Program Facilities Engineering Command Liaison (Liaison). In other words, should a maintenance down-time request create the need for the submittal of a Critical Priority ticket (a System Down ticket) the Contractor shall request authorization for such down-time from the Base via the NAVFAC AT/FP Ashore Program

Liaison. The Contractor must be granted permission to bring the system down. This request shall include (a) the impact of the planned down-time, (b) the reasons why it is required, (c) a proposed method using backup resources or a temporary alternative capability to mitigate the impact of the down-time, and (d) a proposed date and time of the down-time. Any system down-time associated with planned maintenance that has an approved waiver in place or is otherwise approved by the Government will not be included in Ao calculations and will, therefore, have no negative impact on Contractor performance.

Any maintenance down-time shall be planned within the scheduled maintenance window. Maintenance windows are established as follows:

• Regular Maintenance: Monday through Friday from 2100 to 0500, with pre-notification to the local N6.

• Extended Maintenance: The Contractor shall coordinate schedules with the NAVFAC AT/FP Ashore Program

Liaison and the local Installation N6.

4.3 Corrective Maintenance

Whenever it is learned that the system suffers from a deficiency that degrades its intended functionality, the Contractor shall perform diagnostics and repair services to restore system…