N66001-16-R-0082 0001.pdf

1300572738

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

This ammendment provides responses to questions and resultant changes as noted in the Summary of Changes. Changes have been highlighted for reference.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 47

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

16C. DATE SIGNED

BY 18-Jul-2017

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 N66001-16-R-0082

X 9B. DATED (SEE ITEM 11)

22-Jun-2017

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 is extended, X 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

18-Jul-2017

CODE

SPAWAR SYSTEMS CENTER PACIFIC

JEREMY D. SHULL CODE 22410

JEREMY.SHULL@NAVY.MIL

53560 HULL ST

SAN DIEGO CA 92152-5001

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N66001-16-R-0082

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

Questions and Answers

1. On page 109 in Section L regarding Factor 2 Past performance, subparagraph (b) states “Part 15 of the Reference Information Sheet requires offerors to provide a summary description of contract work, not to exceed 1 additional single-sided pages in length, for each cited reference.” In the RFP Attachment 3 – Reference Information Sheet Part 15 states “Provide a summary description of contract work, not to exceed two (2) additional single-sided pages in length”. Should we assume two pages is correct considering all the PWS areas we must cover?

ANSWER: Two pages is correct. Section L is corrected to conform with RFP Attachment 3.

2. Section M Title – “Evaluation Factors for Award”, Page 113 Paragraph (a) reads “One or more awards may be reserved for small business if one or more small business prime contractors are found to represent the best value to the Government in terms of both technical capability and cost reasonableness.” Section L Title – “Type of Contract Clause” Page 95 reads “ The Government contemplates of a single award, indefinite-delivery, indefinite-quantity (IDIQ) contract(s) …” Please confirm that wording Section M referencing ‘One or more awards for Small Business’ is not applicable as it does not agree with the wording in Section L ‘The Government contemplates a single award.

ANSWER: Please see revised language in Section M, “Evaluation Factors for Award.”

The Government contemplates awarding to a single business, regardless of the business’s size standard.

3. In Section L, the Government states “Proposals shall be prepared on standard 8 1/2" by 11" formatted pages with 1" minimum margins.” We assume the Government will permit 11” by 17” formatted pages to accommodate large graphics and tables, such as an organizational structure as long as the Offeror counts them as two (2) pages. Is that correct?

ANSWER: No. Offerors are to conform to the page formatting referenced in Section L with the exception of forms provided by the Government.

4. Under [Section L] (e) (6) the instructions state only the Prime will complete Attachment 2 and include subcontractors. In the Attachment 2 instructions, it states that both the

Prime and subcontractor must complete and submit. Is the RFP or the Attachment correct?

ANSWER: Both the prime and subcontractors should complete the sheet. Section L has been revised to state the same.

5. CLINs 0001 – 0008 are all listed as 01-Feb-2021 to 31-Jan-2023. Should CLINs 0001 – 0008 are all listed as 01-Feb-2021 to 31-Jan-2023?

ANSWER: No. Please see revised Section F.

6. If subcontractors identified on the Small Business Participation Information Sheet (Attachment 5) must be included in the cost proposal (assuming this means only labor subcontractors can be accounted for), then would the Government consider changing the percentage of the total value of the acquisition to percentage of total labor?

ANSWER: No. Offerors shall calculate small business participation as a percentage of the total acquisition.

7. Reference Section L Factor 1 – Subfactor 1 (c), the expected LOE for the DoD CSWF certified workforce is unclear. Could the Government provide the required Level of Effort with DoD CSWF certifications so we can address the requirement?

ANSWER: The level of effort for the CSWF requirements is contained in the level of effort table in Section L.

8. Should Section M - Subfactor 2 be changed to read the same as Section L – Subfactor 2 which is: “(c) The Government will evaluate the offeror’s approach to Supply Chain Risk Management (SCRM). The Government will consider the offeror’s specifically identified practices currently in place to reduce supply chain risk, specifically: (1) The purpose and technical value of the subcontractors; and (2) The prime contractor’s management and oversight with regards to communication and accountability for all subcontractors and subcontractor personnel.

ANSWER: Please see revisions to Section M.

9. The subtotal hours for Annual Overtime hours are 12,322, while adding all the rows comes out to 12,329. This also causes a 7-hour difference in the overall total. Will the Government correct this difference?

ANSWER: Please see revisions to Section L.

10. Would the government exclude an offeror’s cover and title pages, Table of Contents and Acronym List from being counted against page limitations?

ANSWER: Yes.

11. The RFP specifies: “Proposals shall be prepared on standard 8 1/2" by 11" formatted pages with 1" minimum margins…The type used shall be no smaller than Times New Roman, 10-point.” However Attachment 3, Reference Information Sheet - which states that Offerors are not to change the spatial structure of this form, i.e. borders, block size, etc. - does not comply with margin and font size requirements. To make the attachment comply, the 1-page form becomes 2-pages. Would the Government allow offerors to populate and submit Attachment 3 as is, without having to manipulate the margins to fit 1 inches or changing the font size to 10?

ANSWER: Yes.

12. The contractor shall provide cybersecurity support for AT/FP systems through their lifecycle. The effort includes testing, mitigations, annual cybersecurity compliance, sustainment engineering support, and preparation and submission of C&A packages IN ACCORDANCE WITH the references in section 4.0 and DIACAP. Question: Per NAVADMIN 140/15 Section d. All A&A submission beginning 1 October 2016 will be under RMF. Does the government intend to update this section to support RMF rather than DIACAP?

ANSWER: Yes. Please see revised Section C.

13. The narrative discussion about Attachment 2 states “Subcontractors do not need to submit this attachment.” This statement conflicts with the instructions in the Excel version of Attachment 2, which states that subcontractors must complete the attachment. Are subcontractors required to complete Attachment 2?

ANSWER: See response to Question 4, above.

14. On sheet 2 of Attachment 2, the Government Labor Category Titles conflict with the labor categories provided in Section L-2.3. May offerors modify the labor category titles on Attachment 2 to match the labor category titles in Section L-2.3?

ANSWER: See also revised Attachment 2, where the labor categories have been corrected to match those in Section L of the RFP.

15. RFP Attachment 2 Column F will reflect the fringe benefit additive to the Direct Labor Hourly Rate. No other columns are provided for additional burdens such as Overhead, G&A, or Fee.

ANSWER: No. The other indirect costs will be included in the offeror’s cost proposal.

The Attachment 2 is in addition to the requirement for a cost proposal.

16. In table 2.3, the Annual Overtime Hours add up to 12,329, not 12,322 as shown in the table. Would the Government please clarify the number of overtime hours to propose?

ANSWER: See response to Question 9 above.

17. The accounting system questionnaire shown on page 106-107 seems excessive for very small companies that will be issued FFP/T&M type subcontracts. Would the Government consider removing this requirement for subcontractors who will be issued FFP/T&M type subcontracts. Would the Government consider removing this requirement for subcontractors who will receive less than 3% workshare?

ANSWER: Offerors with an approved accounting system should propose CPFF, and provide the information referenced in the question regardless of the workshare proposed.

Offerors without an approved accounting system should propose FFP or T&M, and do not need to provide the accounting system inforamtion.

18. In Section L-2.1(d)(2), page 101, Subcontractors are required to submit the same detailed level of cost information as the prime contractor. Would the Government consider removing the requirement for a Pricing Narrative for subcontractors who will be issued FFP/T&M type subcontracts? Would the Government consider removing the requirements for a Pricing Narrative for subcontractors who will receive less than 3% workshare?

ANSWER: Offerors with an approved accounting system should propose CPFF, and provide the information referenced in the question regardless of the workshare proposed.

Offerors without an approved accounting system should propose FFP or T&M, and do not need to provide the Pricing Narrative information..

19. Attachment 3 block 15 indicates each reference has a maximum of two (2) pages for a summary description. RFP pg. 110 Sect 2 (b) states offerors are to provide a summary description of contract work not to exceed one (1) additional single-sided pages in length for each cited reference. What is the maximum number of pages for the narrative summary description for each cited reference?

ANSWER: See response to Question 1 above.

20. Delivery/Task Order Procedures (SEP 2014)- Alternate II; section (e) indicates that Navy Commercial Access Control System (NCACS) will be used for facility access, but recent correspondence on other contracts has stated that NCACS credentials will no longer be accepted for base access effective 14 August 2017. Will this section be replaced with Defense Biometric Identification System (DBIDS) credential requirements?

ANSWER: The clause will be updated after award. However, this change has no impact to evaluation of offeror’s proposals.

21. Can the Government provide labor category descriptions (education, years’ experience etc) from section 2.3 on page 95 of the RFP. Or provide a current reference for this dictionary?

ANSWER: The Government does not have required or recommended personnel descriptions. Offerors must select the labor categories that are appropriate to meet the requirements described in the PWS. Offerors are also reminded of the Section L requirement to cross-walk the offeror’s internal labor category descriptions and nomenclature to the Government’s labor categories.

22. Can the Government clarify the DELIVERY/TASK ORDER PROCEDURES (SEP 2014) – ALTERNATE II on page 28 of the RFP? It is our understanding this will be a single award contract yet this section describes a Multiple Award Contract (MAC) Task Order bidding process.

ANSWER: Actually, the referenced clause is a generic clause that contains both MAC task order procedures AND single award task order procedures. Please note (b) of the above-referenced clause, which specifically addresses non-competitive ordering procedures: “It is anticipated that each order awarded to a single award contractor, or to a MAC contractor when a Contracting Officer-approved exception at FAR 16.505(b)(2)(i)(A) through (F) applies, or when making a Contracting Officer-approved award to a small business as outlined above, will be placed in accordance with the following procedures….”

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

For

Anti-Terrorism/Force Protection (AT/FP) Electronic Surveillance Systems (ESS)

1. SCOPE

1.1. The Space and Naval Warfare Systems Center Pacific (SSC PAC) Security Systems

Branch, Code 4118, has a requirement to provide life cycle sustainment, installation, integration, testing and procurement/acquisition support for Anti-Terrorism/Force Protection (AT/FP) Electronic Surveillance Systems (ESS) during their life cycle and to provide technical expertise to Naval Facilities Engineering Command (NAVFAC), Commander Naval Installation Command (CNIC), Navy Munitions Command (NMC), Naval Mine and Anti-Submarine Warfare Command (NMAWC), Strategic Weapons Facility Pacific (SWFPAC), United States Marine Corps, the Program Executive Offices (PEO), other Department of Defense (DOD) agencies, Department of Homeland Security (DHS), United States Coast Guard (USCG), Customs and Border Protection (CBP), and other Government activities as required. Specifically, Code 4118 performs the procurement, installation, integration, testing and life cycle sustainment of Naval AT/FP ESS at shore installations throughout the world. Systems/equipment and services are defined as equipment and/or systems that facilitate the detection, delay, deterrence, assessment, and response to terrorist events. Sustainment services include: preventive and corrective maintenance, interoperability, maintenance planning, supply/logistics support, testing and evaluation, reliability and maintainability, and configuration management.

1.2. AT/FP ESS systems provide the capability to receive/transmit orders, receive and process information into situational awareness displays, support command decision processes and communicate electronic data to multi-service, multi-agency nodes across the entire all-hazards/all-threats spectrum of Ashore and Afloat operations. These systems also provide all-hazard warnings to all personnel on board the installation, and others as appropriate. AT/FP ESS systems include the following:

The Regional Operations Center (ROC) and Emergency Operations Center (EOC) serves as the C4I point for information gathering, gain situational awareness, and exercise control over forces from early warning and detection of suspicious events through response and recovery.

The Regional Dispatch Center (RDC) command facility is the hub for all emergency communications between Navy citizens and the First Responders in a Navy Region.

The term RDC is intended to address the overarching RDC capability and all related subsystems within the RDC Family of Systems (FoS), to include, but not limited to, the Navy Emergency Response Management System (NERMS) and Enterprise NERMS (e-NERMS): Computer Aided Dispatch (CAD), Alarm Monitoring Automation System (AMAS), Records Management System (RMS), Mobile Data Computers (MDC), Navy 911, E-911, and ALI, Navy Emergency Management Addressing Project (NEMAP), Geographic Information System (GIS), and the Emergency Call Management System (ECMS).

Wide-Area Alert and Notification (WAAN) systems are utilized to update and disseminate information concerning a terrorist threat or danger, or if an incident has occurred. This includes procedures and techniques necessary to counter the threat and may include civil distribution systems, audio, signage or warning signals and e-mail via Navy Marine Corps Intranet (NMCI) or NGEN wide area network of computers.

Giant Voice (GV) is part of the Wide Area Alert and Notification (WAAN) suite of systems. GV is comprised of an Outdoor Voice/Alert function and a System Control function. The outdoor alert function is intended to provide initial alert and follow-on directions to personnel not located in a building. The System Control function allows authorized personnel to operate the system manually or autonomously. The outdoor component consists of the outside speaker(s) positioned on pole(s) and buildings across the installation. The Giant Voice system is installed as a base-wide system to provide a siren signal and pre-recorded and live voice messages. In order to create the right level of sound output, multiple poles and speakers will be positioned across the installation.

Indoor Voice (IV) is part of the individual building Mass Notification Systems (MNS) and is comprised of Indoor Voice, Interior Notification, and System Control functions. The Indoor Voice (IV) function is intended to provide real-time alert and follow-on directions to personnel inside and around buildings who may or may not have direct access to a telephone or computer. The System Control function allows authorized personnel to operate the system manually or autonomously. The Interior Notification function is intended to be provided by loud speakers, warning lights, and illuminated signs or displays. Speakers are provided at all locations in and around the building at entrances/exits and other outdoor areas (such as courtyards) commonly used by the building occupants.

Automated Telephone Notification System (ATNS) provides military installations with the ability to rapidly and effectively disseminate emergency alerting and notifications throughout the telephone and data network environments, including signals or messaging appropriate to force protection conditions (FPCONs), weather conditions, watches, warnings, evacuation routes, and other alerting information to meet Department of Defense (DoD) and federal warning requirements.

Computer Desktop Notification System (CDNS) provides Navy installations with the ability to rapidly and effectively disseminate emergency alerting and notification information throughout the data networks environment, including signals or messaging appropriate to FPCONs, information operations conditions (INFOCONs), watches, warnings, evacuation routes, and other alerting information to meet DoD and federal warning requirements.

Sensor Infrastructure, Integration, and Alarm Notification. Equipment Sensors and Alarm interfaces are part of the Navy Emergency Response Management System (NERMS) Alarm Monitoring and Automation System (AMAS) located at a Regional Dispatch Center (RDC). The RDC AMAS receives signals from and continuously polls all interfaced physical security and fire alarm system equipment sensors which result in the return of alarm signals. AMAS is divided into two systems, one local and one regional (LAMAS and RAMAS). Sensors and sensor interfaces/infrastructure are installed to provide alarm notification and alarm management to all command dispatch centers. This infrastructure integrates/interfaces all existing Fire Alarm, Access Control Systems (ACS), Intrusion Detection Systems (IDS), and Central Alarm Station Receiving/Monitoring Systems with LAMAS and/or RAMAS and then interfaces LAMAS with RAMAS.

o Access Control Systems (ACS) include screening, controlling, validating, and detecting authorized and unauthorized access at entry control points to installations, piers, harbors, ships, and incident sites from land. This includes physical restraints to prevent unauthorized access through perimeter security to installations, buildings, restricted areas, piers, harbors, family housing and incident sites from land.

Physical Security/Access Control (PS/AC). Physical security and access control which is comprised of the following: Automated Vehicle Gate (AVG), Automated Pedestrian Turnstile (APT), Enclaves, Electronic Security Systems, and Physical Security Information Management (PSIMS). PS/AC systems include: Physical Access Control System (PACS) software, either Lenel, AMAG, or another vendor's solution; License Plate Reader (LPR) systems S/W; iCX Chameleon for custom gate C2; various types of Video Management Systems (VMSs); as well as databases utilizing Oracle or MS SQL.

Security Surveillance Systems include the capability to detect and identify unauthorized movement of personnel, vehicles and material in or around installations, piers, harbors, ships, restricted areas, and incident sites

Sensor Management System (SMS) Telephony / Telecommunication infrastructure coordination, integration and sustainment of telephony interfaces, software applications, and hardware equipment utilized between local commercial telephony providers and county telephony agencies to the base BCO and the regional naval RDC/LDC end users.

Joint Perimeter Surveillance Command and Control System (JPSC2) Radar Sonar Surveillance Center (RSSC) and Communications Detachments

(COMMSDET) operating the Mobile Ashore Support Terminal (MAST IIIs) for Coastal Riverine Force

ELMR Backbone CONUS/OCONUS sustainment to include access of proprietary information to program, integrates, and configures ELMR components as required.

SharePoint based application system support PSNet enterprise connectivity

Assess Control Systems and Intrusion Detection Systems integration and sustainment Electronic Harbor Security Systems (EHSS) C4I installation and integration requirements.

Aruba Wireless Solutions (WIFI)

2. APPLICABLE DOCUMENTS

The following documents are for reference only, except where invoked for a specific section of the PWS, and are not all inclusive:

Reference Description Date

ANSI/ASME-Y-14.5M Dimensioning and Tolerancing for Engineering Drawings

ANSI/IEEE 315 Graphical Symbols for Electrical and Electronic Diagrams

ANSI/TIA-222-G-2005

Structural Standard for Antenna Supporting Structure and Antennas

COMNAVCYBERFOR

INST 5239.1

Information Assurance Workforce Improvement Program (IA

WIP)

COMUSFLTFORCOM

/COMPACFLTINST

6320.3A

Commander US Fleet Forces Command/Commander US Pacific Fleet Instruction, Medical Screening For US Govt Civilian Employees, Contractor Personnel, and Guests prior to embarking Fleet Units 7-May-13

DoD 5205.02-M DoD Manual – Operations Security (OPSEC) Program Manual 3-Nov-08

DoD 5220.22-M DoD Manual – National Industrial Security Program Operating Manual (NISPOM) 28-Feb-06

DoD 8570.01-M Information Assurance Workforce Improvement Program, 19 Dec 2005 with Change 3 24-Jan-12

DoDD 5205.02E DoD Directive – Operations Security (OPSEC) Program 20-Jun-12

DoDD 8140.01 Cyberspace Workforce Management 11-Aug-15

DoDI 5200.02 DoD Personnel Security Program (PSP) Reissues DoD Directive (DoDD) 5200.02

DoDI 5220.22 DoD Instruction – National Industrial Security Program 18-Mar-11

DoDI 6205.4 Department of Defense Instruction, Immunization of Other Than U.S. Forces (OTUSF) for Biological Warfare Defense 14-Apr-00

DoDI 8500.01 DoD Instruction – Cybersecurity 14 Mar 2014

DoDI 8510.01 DoD Instruction – Risk Management Framework (RMF) for DoD Information Technology (IT) 12 Mar 14 12-Mar-14

DoDM 5200.01 DoD Manual – Information Security Program Manual 24-Feb-12

FIPS-201

Personal Identity Verification of Federal Employees and Contractors

HSPD-12 Homeland Security Presidential Directive

MIL-E-17555H

Electronic/Electrical Equipment, Accessories and Repair Parts, Packaging/Packing.

MIL-HDBK-2036 Preparation of Electronic Equipment Specifications

MIL-HDBK-245D Preparation of Performance Work Statement

MIL-HDBK-419A

Grounding, Bonding, and Shielding for Electronic Equipment and Facilities

MIL-HDBK-454A General Guidelines for Electronic Equipment

MIL-HDBK-46855A

Human Engineering Guidelines for Military Systems, Equipment and Facilities

MIL-HDBK-61A Configuration Management Guidance

MIL-HDBK-781A

Handbook for Reliability Test Methods, Plans and Environments for Engineering, Development, Qualification and Production

MIL-HDBK-881A Work Breakdown Structures for Defense Materiel Items

MIL-M-85337A Technical Manuals, QA Program Requirements

MIL-P-24534A (Navy) Military Specification, Planned Maintenance System, Development of MRC, MIP, and Associated Documentation

MIL-PRF-29612B Training Data Products

MIL-STD-130M Identification and Marking of US Military Property

MIL-STD-1310G

Standard Practices for Shipboard Bonding, Grounding and Other Techniques for Electromagnetic Compatibility and Safety

MIL-STD-1472F Human Engineering

MIL-STD-2110(EC) Restoration, Overhaul, and Repair of Electronic Equipment.

MIL-STD-38784

Standard Practices for Manual, Technical, General Style and Format Requirements.

MIL-STD-740B

Airborne and Structure Borne Noise Measurements and Acceptance Criteria

National Security Decision Directive 298 (Series) National Operations Security Program (NSDD) 298

National Security Decision Directive 298 (Series) National Operations Security Program (NSDD) 298

NAVADMIN 107-12

Navy Information Assurance Workforce and Operating System/Computing Environment Certifications

NAVSEA S0300-BD-

PRO-010/020/030 ILS Procedures Manual for Systems/Equipment.

NAVSEA SL720-AA-

MAN-010

Fleet Modernization Program (FMP) Management and Operations Manual.

NAVSEAINST

4130.12A

Configuration Management Plan Content Guidance and Practical Applications

NAVSEAINST 5000.39

Acquisition and Management of Integrated Logistic Support for Ships, Systems and Equipment

Navy Telecommunications Directive (NTD 10-11) System Authorization Access Request (SAAR) - Navy

NENA 08-751 NENA i3 Technical Requirements Document, Issue 1 28-Sep-06

NFPA 1221

Standard for the Installation, Maintenance, and Use of Emergency Services Communications Systems 2010

OPNAVINST 3432.1

(Series) DON Operations Security 4-Nov-11

OPNAVINST 3432.1

(Series) DON Operations Sec

OPNAVINST 3440.17 Regional Operations Centers

OPNAVINST 4790.4.

Vol. I

Navy Maintenance and Material Management (3M), Planned Maintenance Subsystem (PMS).

OPNAVINST 5513.4E Classification Guide

OPNAVINST 5530.14E Navy Physical Security and Law Enforcement Program

OPNAVINST

F3300.53C (Series) Navy Antiterrorism Program

SECNAV 5239.2

Department of the Navy Information Assurance (IA) Workforce Management Manual

SECNAV M-5239.2

DON Cyberspace Information Technology and Cybersecurity Workforce Management and Qualification Manual Jun-16

SECNAV M-5510.30

Secretary of the Navy Manual – DoN Personnel Security Program

Jun-06

SECNAV Manual

5510.36 (Series) Department of Navy Information Security Program

SECNAVINST 4130.2 Configuration Management Program

SECNAVINST 4440.34

Secretary of the Navy Instruction – Implementation of Item Unique Identification within the DoN, 22 Dec 2009 22 Dec 2009

SECNAVINST 5239.19 Incident Response Mar-08

SECNAVINST

5239.20A DON Cyberspace IT and Cybersecurity 10-Feb-16

SECNAVINST

5239.3C DON Cybersecurity Policy 2 May 2016

SECNAVINST 5510.30 DON Regulation – Personnel Security Program 6-Oct-06

SPAWARINST 3432.1 SPAWAR Instruction – Operations Security (OPSEC) Policy 2-Feb-05

SPAWARINST 3432.1

(Series) Operations Security Policy

SPAWARINST

4440.12

Management of Operating Materials and Supplies (OM&S), Government Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory

SPAWARINST

5239.16

Information Assurance Workforce Improvement Program Training, Certification and Workforce Management (IA WIP)

SPAWARINST

5721.1B SPAWAR Section 508 Implementation Policy 17-Nov-09

UFC 4-010-1 DOD Minimum Antiterrorism Standards for buildings

UFC 4-022-1 Security Engineering: Entry Control Facilities

ASN RDA Memorandum, DON Policy on Digital Product / Technical Data 23-Oct-04

SPAWARSYSCEN PACIFIC: Shore Installation Process Handbook

ASN RDA Memorandums, Software Process Improvement Initiative Contract Language 17-Nov-06

DON CIO Memorandum, Acceptable Use of Department of the Navy Information Technology (IT) 12-Feb-16

APCO 25 (Project 25) Standards

3. REQUIREMENTS

The following paragraphs list all required support tasks that will be required throughout the contract life. The contractor shall provide necessary resources and knowledge to support the listed tasks. Specific objectives will be dependent on the basic contract and the TO written against the basic contract. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

3.1. PROJECT EXECUTION SUPPORT

The contractor shall provide Project Execution support, including but not limited to:

preparing agendas, presentations, and minutes for project meetings; managing the cost and schedule processes and outputs (e.g., gathering data to generate various reports and upload to the AT/FP Information Management (AIM) Portal, as required); preparing, and delivering training materials, guidance and instruction to project execution personnel; and the development and presentation of various reports. Specific project execution support tasks, deliverables, and performance assessment metrics will be provided at the task order level.

3.2. PROGRAM SUPPORT

3.2.1. The contractor shall review maintenance methodologies and procedures, investigate areas requiring improved or additional personnel maintenance training/techniques, and provide recommendations for minimum maintenance requirements. Recommend revisions to existing technical support documentation.

3.2.2. The contractor shall review security requirements at various facilities and provide recommendations to the Government. Once individual site requirements have been validated, the contractor shall develop a security system concept and evaluate any technical design plans and component integration at sites specified.

3.2.3. The contractor shall collect data, conduct engineering analyses and evaluate engineering parameters associated with long range planning for out-year programs to provide input for development, maintenance, and use of an advanced technology base.

3.2.4. The contractor shall prepare planning documents such as a Plan of Action and

Milestones (POA&M) for executing installations from initiation to completion.

3.3. INTEGRATED LOGISTIC SUPPORT (ILS) AND CONFIGURATION DATA

MANAGEMENT SUPPORT

3.3.1. The contractor shall support the sustainment of systems and equipment installed, including regionally installed equipment. This sustainment support includes, but is not limited to, developing ILS action item lists; developing ILS and Configuration Management Plan (CMP) input to the Program Management Plan (PMP); preparing ILS and sustainment updates to Project Execution documents (e.g., PWS template and appendices); prepare ILS inputs for briefings for PMR, QER, and road shows;

maintaining ILS Master POA&M; providing oversight for preventive maintenance plans (including milestones and schedules), and developing/ and recommending overall maintenance policies and procedures.

3.3.2. The contractor shall verify system/equipment configurations. The contractor shall correct differences between installed configuration and authorized baseline including approved modifications. The contractor shall record and report all unauthorized modifications.

3.3.3. Specific ILS and Configuration Data Management (CDM) support tasks, deliverables, and performance assessment metrics will be provided in individual task orders.

3.4. AT/FP INFORMATION MANAGEMENT (AIM) PORTAL SUPPORT

The contractor shall provide supporting the AIM Portal operating system; maintaining AIM database integrity; preparing AIM Working Group (AIMWG) meeting agenda, minutes, and action item lists; developing and maintaining AIM processes, producing AIM reports (including summary reports of AIM costs and performance) and analyzing AIM System for efficiency and effectiveness.

3.5. INFORMATION SYSTEMS SECURITY SUPPORT

3.5.1. The contractor shall provide cybersecurity support for for AT/FP systems through their lifecycle. The effort includes testing, mitigations, annual cybersecurity compliance, sustainment engineering support, and preparation and submission of C&A packages IN ACCORDANCE WITH the references in section 4.0 and Risk Management Framework (RMF). Enhancement can be viewed as the next generation of the system, when a new release is done on a system it will require a new cybersecurity package.

3.5.2. The contractor shall work with Government personnel to ensure compliance with all current Navy Information Technology (IT) & cybersecurity policies.

3.5.3. The contractor shall ensure that all integrated, installed, or operational application hosted on Navy networks are registered in the Department of the Navy (DON) Application and Database Management System (DADMS) and approved by the appropriate Functional Area Manager (FAM). The contractor shall ensure that all networks, servers, or associated devices procured and/or connected to a Navy network complete DADMS registration and receive FAM approval, as applicable.

The contractor shall ensure that all systems supported shall be registered within

DoD Information Technology Portfolio Repository (DITPR). The contractor shall ensure that all systems supported shall be registered in Enterprise Mission Assurance Support Service (eMASS). The contractor ensure that all systems supported shall be documented, collected, and uploaded for FRCB approval to the SPAWAR PEO Integrated Data Environment and Repository (SPIDER).

3.6. SYSTEM ENGINEERING SUPPORT

3.6.1. The contractor shall routinely evaluate installed systems, subsystems, projects, activities, and develop recommendations to reduce Total Ownership Costs (TOC).

As needed, the contractor shall develop draft engineering plans and specifications, perform risk identification/analysis/mitigation, and perform traceability. In addition, the contractor shall suggest an integration solution. This may include building a working model of a system or group of systems. Typical associated tasks include, but are not limited to: computer-aided design, design studies and analysis, high-level detailed specification preparation, configuration management, and document control.

3.6.2. The contractor will be an active participant in engineering and requirements management in support of AT/FP systems. The contractor shall provide systems engineering expertise toward programmatic and sustainment engineering efforts including the following, as required: Risk Assessment; Test and Evaluation;

Integrated Product Team (IPT) participation; and laboratory interactions.

3.6.3. The contractor shall review, verify, update, or revise technical documentation for specified electronic equipment/systems, such as engineering drawings, technical manuals, provisioning data, configuration data, and training plans and provide written recommendations or reports.

3.6.4. The contractor shall review/draft/revise test plans, repair procedures, equipment documentation, modifications to existing baseline, and adequacy of technical support documentation and test instrumentation to insure that proper quality assurance is maintained in accordance with the current prescribed standards.

3.6.5. The contractor shall develop, analyze, revise and/or recommends changes to test procedures including Pre Installation Test and Checkout (PITCO) and System Operations and Validation Testing (SOVT).

3.6.6. The contractor shall update interface control documents (ICDs) as required.

3.6.7. The contractor shall conduct initial system/equipment installations, upgrades and certifications.

3.6.8. The contractor shall install, groom, test, checkout, and evaluate new systems/equipment.

3.6.9. The contractor shall perform obsolescence program research to identify suitable replacement piece parts and/or provide recommendations to purchase the form, fit, and functional parts for continuing equipment operation to meet mission requirements.

3.6.10. The contractor shall collect and/or correlate system, subsystem, unit, or component level maintenance, reliability, maintainability, or operational performance data.

3.6.11. The contractor shall develop or revise maintenance, reliability, maintainability, or operational performance parameter data bases, conduct analysis on selected parameters, and provide parameter baselines, comparisons to specifications or predictions, platform deviations from predicted or average performance, and make recommendations for changes to test methods, procedures, or specifications.

3.6.12. The contractor shall perform system/equipment tests, grooms, checks, upgrades, inspections, and certifications including SOVT.

3.6.13. The contractor shall perform comprehensive repair of designated systems/equipment.

3.6.14. The contractor shall perform system/equipment de-installation and/or removal.

3.6.15. The contractor shall perform on site analysis of system fault symptoms, assess degree of operational impairment / mission degradation, recommend alternate operational modes, and conduct all necessary repairs.

3.7. SOFTWARE MANAGEMENT SUPPORT

3.7.1. The contractor shall identify and address risks, to identify resource requirements

(skill levels, facilities, computer resources) and schedules, to describe the metrics program, to define the contractor's software management organization and its interfaces, and to define use of automated tools.

3.7.2. The contractor shall employ well-defined written procedures for software metrics collection and analysis.

3.7.3. The contractor shall utilize software metrics, including product, productivity, quality, and management metrics, to assure the quality of all software and documentation produced.

3.7.4. The contractor shall prepare, develop, and maintain the following software support, operational, and change documentation: the technical preparation, impact evaluation/analysis, and planning necessary to implement or disapprove software change documentation.

3.7.5. The contractor shall provide technical support to the SSC Pacific Project Software Change Control Board for the evaluation and disposition of all proposed changes to the software and documentation produced electronically by e-mail; hard copies are only required if requested by the government. To ensure information compatibility, the contractor shall guarantee all deliverables (i.e., CDRLs), data, correspondence, and etc., are provided in a format approved by the receiving government representative.

4. GOVERNMENT FURNISHED PROPERTY/MATERIAL

As defined in FAR Part 45, Government-furnished property (GFP) is property in the possession of, or directly acquired by, the Government and subsequently furnished to the contractor for performance of a contract. GFP includes Government Furnished Material (GFM), Government Furnished Equipment (GFE), Special Tooling (ST) and Special Test Equipment (STE). Due to varying requirements for each task order, furnishing Government Property in accordance with DFARS PGI 245.103-70 will be determined at the task order level. The contractor shall utilize Government property in accordance with FAR clause 52.245-1 and 52.245-9. The contractor shall have the means to provide an effective and efficient stewardship of Government property.

In accordance with PGI 245.103-72, GFP items will be identified on Scheduled GFP (SGFP) and/or Requisitioned GFP (RGFP) forms which will be provided at the task order level.

4.1. GOVERNMENT PROPERTY ADMINISTRATOR

In accordance with FAR 42.201, the contract property administrator under this contract is designated as Defense Contract Management Agency (DCMA). The contractor shall work with the designated contract property administrator to ensure compliance with the contract’s property requirements.

4.2. PROPERTY TRANSFER BETWEEN GOVERNMENT AND CONTRACTOR

Contractors shall not take receipt or transfer custody of any government property without possessing proper contractual authority; i.e.; item specifically is identified as GFP at the basic contract or task order level. Per DoDI 4161.02, the government will utilize electronic transaction when transferring GFP to the contractor (specified by contract number) and upon return of the property to the government. The contractor shall use Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) (an application within WAWF) to receipt property transfer; when iRAPT is not available, the contractor may use with COR concurrence the Defense Logistics Management System (DLMS) standard logistics transaction set 527R to provide materiel receipt acknowledgement.

The contractor shall cite the applicable contract number for each item to properly track property shipments.

Note: In accordance with local management specifications, the contractor shall ensure transfer of property occurs with proper paperwork; e.g., Requisition and Invoice/Shipping Document (DD1149) or COMSEC Material Report (SF153).

4.3. GFP TAGGING AND ITEM UNIQUE IDENTIFICATION (IUID) REGISTRY

The contractor shall tag, label, or mark all serially managed GFP items not previously tag, labeled, or marked. The contractor shall ensure applicable Government Furnished Property (GFP) is identified in the DoD Item Unique Identification (IUID) Registry and its integral GFP Repository. The Contractor shall develop an IUID Marking Plan that details the Contractor’s strategy to execute marking requirements. The Contractor shall update the IUID Registry with the new marking information.

The Contractor shall establish, develop and implement property management plans and procedures that, at a minimum, address:

-Receipt of Government Property -Records of Government Property -Physical Inventory -Reports -Maintenance -Property Closeout

The Contractor shall also report the loss, damage, destruction or theft of Government property to the COR. This report shall include generating and submitting reports for Government Furnished Property (GFP) Status and Management, Item Unique Identification (IUID) Marking Activity, Validation and Verification, Physical Inventories, a plan for IUID Marking, and Technical Reports as required for incidents leading to loss, damage destruction or theft of GFP.

For all GFP items including laptops (required to be identified on the applicable contract/TO SGFP form) removed from a government facility, the contractor employee shall possess at all times a government signed copy of the DD1149 specifying contract and applicable TO number, company name, model number, and serial number of the computer. For GFP laptops assigned to contractor employees, in addition to the signed DD1149, a contractor-generated property pass with the employee’s name may be attached to validate possession in accordance with applicable company internal procedures.

4.4. GOVERNMENT PROPERTY TRANSFERRING ACCOUNTABILITY

Government property cannot be transferred between contracts or task orders unless approval is obtained from the Contracting Officer, proper identification/tracking is maintained, and modifications are issued to both affected contracts/task orders.

Contractor shall ensure they have all necessary documentation required for authorized transfer of property from one contract/task order to another. The contractor shall ensure transfer documentation specify the type, quantity and acquisition cost of each item being transferred. A modification must be performed on the exiting contract/TO or a new contract/TO awarded to authorize the items as GFP.

4.5. GOVERNMENT PROPERTY LOST OR DAMAGED ITEMS

Contractor shall promptly report to the COR and KO all lost and/or damaged government property.

4.6. Government Property Inventory Disposition

When disposition instructions for GFP are contained in the accountable contract or on the supporting shipping documents (DD Form 1149), the Contractor shall initiate and submit an excess inventory listing to the Procuring Contracting Officer (PCO), via the activity Property Administrator.

When disposition instructions are not stipulated in the contract or supporting shipping document (DD Form 1149), an excess inventory listing is required that identifies GFP and, under cost reimbursement contracts, CAP. The contractor shall submit the list to the COR and PCO, via the activity Property Administrator, at which time disposition instructions will be provided by the government.

When GFP and CAP are specific to a single task order, the contractor shall include a final inventory reporting list in the TO Closeout Report (CDRL number TBD at task order level). At the time of the Contractor’s regular annual inventory, the Contractor shall provide the PCO, via the assigned Property Administrator, a copy of the physical inventory listing. All contractor personnel shall be responsible for following the company’s internal inventory management procedures and correcting any problems noted by the government property administrator.

4.7. GOVERNMENT PROPERTY PERFORMANCE EVALUATION

Non-compliance with the contract’s Government Property terms and conditions will negatively affect the contractor’s annual Contractor Performance Assessment Reporting System (CPARS) rating.

4.8. GOVERNMENT FURNISHED INFORMATION (GFI)

GFI will be utilized on this contract. Unless otherwise specified, the contractor shall limit all GFI distribution and inventory reports to a need-to-know basis and ensure all GFI is returned at completion of the contract/task order. GFI and its estimated delivery date will be identified at task order level.

5. CYBER SECURITY

Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

5.1. CYBER IT AND CYBERSECURITY PERSONNEL

(i) The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01- M prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

(ii) The contractor shall be responsible for identifying, tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF) and Cyber IT workforce personnel. CSWF Report requirements are explained in a following paragraph. Although the minimum frequency of reporting is monthly, the task order can require additional updates at any time.

(iii) Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented below.

When a contractor requires logical access to a government IT system or resource (directly or indirectly), the required CAC will have a Public Key Infrastructure (PKI). A hardware solution and software (e.g., ActiveGold) is required to securely read the card via a personal computer. Pursuant to DoDM 1000.13-M-V1, CAC PKI certificates will be associated with an official government issued e-mail address (e.g. .mil, .gov, .edu). Prior to receipt of a CAC with PKI, contractor personnel shall complete the mandatory Cybersecurity Awareness training and submit a signed System Authorization Access Request Navy (SAAR-N) form to the contract’s specified COR. Note: In order for personnel to maintain a CAC with PKI, each contractor employee shall complete annual cybersecurity training. The following guidance for training and form submittal is provided; however, contractors shall seek latest guidance from their appointed company Security Officer and the SPAWAR/SSC Atlantic/SSC Pacific Information Assurance Management (IAM) office:

For annual DoD Cybersecurity/IA Awareness training, contractors shall use this site: https://twms.nmci.navy.mil/. For those contractors requiring initial training and do not have a CAC, contact the SPAWAR/SSC Atlantic/SSC Pacific IAM…