3 PWS.doc

DOC document 89 KB Posted

Attached to
LSD-46 HYDRA SYSTEM-ENGINEER AND LOGISTIC SUPPORT- INTENDED SOLE SOURCE Federal contract opportunity
Solicitation number
N65236-18-Q-7303
Issued by
Department of the Navy Information Warfare Systems Command

View the file

Other files for this federal contract opportunity

Other files attached to LSD-46 HYDRA SYSTEM-ENGINEER AND LOGISTIC SUPPORT- INTENDED SOLE SOURCE, newest first.
File Type Posted
3 CDRL A004.pdf PDF
3 CDRL A002.pdf PDF
3 CDRL A001.pdf PDF
3 CDRL A005.pdf PDF
3 CDRL A003.pdf PDF
3 CDRL T001.pdf PDF
3 CDRL A007.pdf PDF
3 CDRL T002.pdf PDF
3 CDRL A006.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based task order will be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein will be referred to as Performance Work Statement (PWS):

SHORT TITLE: HYDRA ENGINEERING SUPPORT

1.0 PURPOSE

To provide engineering and logistics Support of the Hierarchical, Yet Dynamically Reprogrammable Architecture (HYDRA) Wireless Communications System.

1.1 SCOPE

This PWS covers systems engineering, technical, and logistics support services to the Interior Communication group’s HYDRA Program for Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic). This support encompasses OEM engineering analysis and recommendations for technical logistical and life cycle support for the AN/SRC-55 HYDRA communications system. Services will immediately commence once the system is installed and in light-off status.

1.2 BACKGROUND

The AN/SRC-55 Land Mobile Radio (LMR) System is an Ultra High Frequency (UHF) Land Mobile Trunking Radio System that is based upon the Harris Enhanced Digital Access Communication System (EDACS). It is designed to operate in the UHF frequency band (380-400 MHz) using COTS technology. The system is designed for interior communications within the ship or on the flight deck. The system includes low power radios in addition to the critical helmet circuitry that makes the intelligibility of the system in the high noise flight deck environment superior to any other system. HYDRA is designated as 'Vital' Communications and is typically integrated into the ship's IVN, CAAS, and SATCC systems. HYDRA is a program of record that is managed by NAVSEA05H. Space and Naval Warfare System Center Atlantic (SPAWARSYSCENT Atlantic is responsible for the procurement, fielding and sustainment of this system.

LSD 46 is expected to complete installation of their new HYDRA system which was designed to adhere to the APCO P25 standard. This particular configuration is unique to most HYDRA configurations currently fielded in the fleet as it contains new equipment racks and software. As a result, there is a need to take the time to understand how the new equipment and configuration functions to better serve the ship’s technical support needs.

2.0 PLACE(S) OF PERFORMANCE

The contractor shall provide support at the following location:

a. Naval Station Norfolk, Norfolk, VA

b. BAE Shipyard Norfolk, VA

2.1 GOVERNMENT FACILITIES

Government facilities (i.e., office space or lab space) are provided to those labor categories that would otherwise adversely affect the work performance if they were not available on Government site. Contractor personnel with supplied Government facilities shall be located at St. Julien’s Creek ANNEX SPAWARSYSCEN Atlantic in Portsmouth, VA.

2.2 CONTRACTOR FACILITIES

The contractor can have its facility location anywhere as long as the location does not present a hardship to complete work required on task. The contractor shall have real-time communication between the contractor personnel supporting the efforts and government personnel available at time of award.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list all required non-personal services tasks that will be required throughout the task order. The contractor shall provide necessary resources with knowledge and experience as cited in the personal qualification clause to support the listed tasks. Contractors shall perform requirements in accordance with Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS) which does not include performance of inherently Governmental functions. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

3.1 TECHNICAL SUPPORT

In accordance with the requirements of this contract PWS, the contractor shall develop and submit documentation (see CDRL under Para 6.1) as required for contract administration.

3.1.1 On-site Technical Assist

The Contractor shall provide support for the Testing and Verify power, energize equipment, verify all required channel alignments, perform Operational checks of all functionality of system. Verify operation of all remote fixed equipment (Fixed Standard/Fixed Command/Talk-Group Select Boxes/Battery Chargers and perform coverage checks of the new HYDRA trainer equipment installed at Naval Station Norfolk, Norfolk, VA. Major tasking under this order includes Systems Engineering Support. The contractor shall report findings, analysis results and corrective action taken associated with technical assistance provided. The contractor shall submit a Trip Report (CDRL A008).

3.1.2 On-site Technical Assist

The Contractor shall provide support for the Testing and Verify power, energize equipment, verify all required channel alignments, perform Operational checks of all functionality of system. Verify operation of all remote fixed equipment (Fixed Standard/Fixed Command/Talk-Group Select Boxes/Battery Chargers and perform coverage checks of the new P25 HYDRA equipment installed on the USS Tortuga (LSD 46) located in BAE Shipyard, Norfolk, VA. Major tasking under this order includes Systems Engineering Support. The contractor shall report findings, analysis results and corrective action taken associated with technical assistance provided. The contractor shall submit a Trip Report (CDRL A008).

3.2 ENGINEERING AND TECHNICAL DRAWING SUPPORT

3.2.1 System Interconnect drawings

The contractor shall provide system interconnect drawings to support the development of Installation Control Documents (ICDs). The requirements of the contractor in performing this task shall include but are not limited to the following, (CDRL T001)

1. Frequency Specific equipment part numbers

1. Pinout information for anything that may have changed from previous designs

1. Changes to drawings/specifications based on ship design changes

3.2.1.1 Parametric data for assembly drawings

The contractor shall provide an update to drawings containing parametric data related to design changes. The requirements of the contractor in performing this task shall include but are not limited to the following, (CDRL T002)

a. Weights

b. Center of Gravity

c. Dimensions

d. Power consumption

e. BTU

3.3 NSN PROVISIONING, DISPOSITION AND OBSOLESCENCE

3.3.1 The contractor shall provide an update to drawings containing parametric data related to design changes. The requirements of the contractor in performing this task shall include but are not limited to the following, (CDRL T003)

a. Track and maintain an obsolescence spreadsheet

b. NSN provisioning and disposition support

c. Assign and provide part numbers for future ship planning documentation

d. Support of shock extension reviews post-submittal

4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

4.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

The contractor shall be responsible for the following:

4.1.1 Ensure that no production systems are operational on any research, development, test and evaluation (RDT&E) network.

4.1.2 Follow DoDI 8510.01 when deploying, integrating, and implementing IT capabilities.

4.1.3 Migrate all Navy Ashore production systems to the Navy, Marine Corps Intranet (NMCI) environment where available.

4.1.4 Work with Government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).

4.1.5 Follow SECNAVINST 5239.3B & DoDI 8510.01 prior to integration and implementation of IT solutions or systems.

4.1.6 Register any contractor-owned or contractor-maintained IT systems utilized on task order in the Department of Defense IT Portfolio Registry (DITPR)-DON.

4.1.7 Ensure all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B.

4.1.8 Only perform work specified within the limitations of the basic contract and task order.

4.2 ACQUISITION OF COMMERCIAL SOFTWARE PRODUCTS, HARDWARE, AND RELATED SERVICES

Contractors recommending or purchasing commercial software products, hardware, and related services supporting Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

4.2.1 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA), contractors that are authorized to use Government supply sources per FAR Subpart 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program as prescribed in DFARS Subpart 208.74 and Government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. The contractor shall purchase the following software and/or software licenses:

4.2.2 DoN Application and Database Management System (DADMS)

The contractor shall ensure that no Functional Area Manager (FAM) disapproved applications are integrated, installed or operational on Navy networks. The contractor shall ensure that all databases that use database management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting Navy applications and systems be registered in DoN Application and Database Management System (DADMS) and are FAM approved. All integrated, installed, or operational applications hosted on Navy networks must also be registered in DADMS and approved by the FAM. No operational systems or applications will be integrated, installed, or operational on the RDT&E network.

4.2.3 Cybersecurity/Computer Security Requirements

The contractor shall ensure that all products recommended and/or procured that impact cybersecurity or Information Assurance (IA) shall be selected from the National Information Assurance Partnership (NIAP) Validated Products List. The contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level (EAL) for the network involved, and are utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for government review at any time.

5.0 TASK ORDER ADMINISTRATION

Administration of the work being performed is required; it provides the Government a means for task order management and monitoring. Regardless of the level of support, the ultimate objective of the contractor is ensuring the Government’s requirements are met, delivered on schedule, and performed within budget.

5.1 CONTRACTING OFFICER REPRESENTATIVE (COR) DESIGNATION

The COR for this task order is identified in task order clause 5252.201-9201.

5.2 CONTRACTOR LIAISON

The contractor shall assign a technical single point of contact, also known as the Program Manager (PM) who shall work closely with the Government Contracting Officer and COR. The contractor PM, located in the contractor’s facility, shall ultimately be responsible for ensuring that the contractor’s performance meets all Government contracting requirements within cost and schedule. PM shall have the requisite authority for full control over all company resources necessary for task order performance and be available to support emergent situations. The PM shall ultimately be responsible for the following: personnel management; management of Government material and assets; and personnel and facility security. In support of open communication, the contractor shall initiate periodic meetings with the COR.

5.3 CONTRACTOR MONITORING AND MAINTENANCE

The contractor shall have processes established in order to provide all necessary resources and documentation during various times throughout the day including business and non-business hours in order to facilitate a timely task order response or modification in particular during urgent requirements.

5.3.1 Task order Administration & Documentation

Various types of administration documents are required throughout the life of the task order. At a minimum, the contractor shall provide the following documentation:

5.3.1.1 Task Order Status Report (TOSR)

The contractor shall develop a Task Order Status Reports (CDRL A001) and submit it monthly, weekly, and/or as cited in the requirements of each task order. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports. The TOSR include the following variations of reports:

5.3.1.2 Task Order Closeout Report

The contractor shall develop a task order closeout report (CDRL A002) and submit it no later than 15 days before the task order completion date. The Prime shall be responsible for collecting, integrating, and reporting all subcontracting information. See applicable DD Form 1423 for additional reporting details and distribution instructions.

5.3.1.3 Enterprise-wide Contractor Manpower Reporting Application Pursuant to NMCARS 5237.102-90, the contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this task order for the DoD via a secure data collection website – Enterprise-wide Contractor Manpower Reporting Application (eCMRA). The Product/Service Codes (PSC) for contracted services excluded from reporting are as follows:

(1) W, Lease/Rental of Equipment;
(2) X, Lease/Rental of Facilities;
(3) Y, Construction of Structures and Facilities;
(4) S, Utilities ONLY;
(5) V, Freight and Shipping ONLY.

The contractor shall completely fill-in all required data fields using the following web address: https:// doncmra.nmci.navy.mil/. Reporting inputs consists of labor hours executed during the task order period of performance within each Government fiscal year (FY) which runs from October 1 through September 30. While inputs may be reported any time during the FY, the contractor shall report all data no later than October 31 of each calendar year. Contractors may direct questions to the help desk at http://www.ecrma.mil/.

5.3.1.4 WAWF Invoicing Notification and Support Documentation Pursuant to DFARS clause 252.232-7003 and 252.232-7006, the contractor shall submit payment requests and receiving reports using DoD Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) application (part of the Wide Area Work Flow (WAWF) e-Business Suite) which is a secure Government web-based system for electronic invoicing, receipt, and acceptance. The contractor shall provide e-mail notification to the COR when payment requests are submitted to the iRAPT/WAWF and the contractor shall include cost back–up documentation (e.g., delivery receipts, time sheets, & material/travel costs, etc.) to the invoice in iRAPT/WAWF. When requested by the COR, the contractor shall directly provide a soft copy of the invoice and any supporting invoice documentation (CDRL A004) directly to the COR within 24 hours of request to assist in validating the invoiced amount against the products/services provided during the billing cycle.

5.4 CONTRACTOR PERFORMANCE MANAGEMENT

Contractor performance standards and requirements are outlined in the task order QASP. The ability of a contractor to perform to the outlined standards and requirement will be captured in the Contractor Performance Assessment Reporting System (CPARS). In support of tracking contractor performance, the contractor shall provide the following documents: Cost and Schedule Milestone Plan (CDRL A007) submitted 10 days after task order award and CPARS Draft Approval Document (CDAD) Report (CDRL A009) submitted monthly.

6.0 DOCUMENTATION AND DELIVERABLES

6.1 CONTRACT DATA REQUIREMENTS LIST (CDRL)

The following listing identifies the data item deliverables required under this task order and the applicable section of the PWS for which they are required. Section J includes the DD Form 1423s that itemize each Contract Data Requirements List (CDRL) required under the basic contract. The contractor shall establish a practical and cost-effective system for developing and tracking the required CDRLs generated under each task. The contractor shall not develop any CDRL classified TOP SECRET with SCI.

6.1.1 Administrative CDRL

The following table lists all required administrative data deliverables, CDRLs, applicable to this task:

CDRL #
Deliverable Title
PWS Reference Para
Frequency
Date Due
Security

Classification (up to S/TS or unclassified)

A001

Contract Status Report

5.3.1.1
MTHLY
30 Days after contract award and monthly on the 10th
UNCLAS
A002
Contract Closeout Report
5.3.1.2
1TIME
NLT 15 days before completion date
UNCLAS

A004

Invoice Support Documentation

5.3.1.4
ASREQ
Within 24 hrs from request
UNCLAS
A005
Quality Documentation
7.1
ASREQ
Within 24 hrs from request
UNCLAS
A006
Cost and Milestones Schedule Plan
5.4
One time with revisions (ONE/R)
NLT 10 DATO; revision NLT 7 days after receipt of Govt review
UNCLAS

A007

Contractor CPARS Draft Approval Document (CDAD) Report

5.4
MTHLY
30 after contract award and monthly on the 10th
UNCLAS

6.1.2 Technical CDRL

The following table lists all required technical data deliverables, (CDRLs), applicable to this task order:

CDRL #
Deliverable Title
PWS

Ref Para

Frequency
Date Due
Security

Classification (up to S/TS or unclassified)

T001
System Interconnect Drawings
3.2.1
ASREQ
Within 24 hours from request
UCLAS
CDRL #
Deliverable Title
PWS

Ref Para

Frequency
Date Due
Security

Classification (up to S/TS or unclassified)

T002
Parametric Data
3.2.1.1
ASREQ
Within 24 hours from request
UCLAS
T003
NSN Provisioning, Disposition and obsolescence
3.3.1
MTHLY
30 Days after contract award and monthly on the 10th
UCLAS

6.2 NON-DATA DELIVERABLES

The following table lists all required non-data deliverables:

6.3 ELECTRONIC FORMAT

At a minimum, the contractor shall provide deliverables 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. The contractor shall provide all data in an editable format compatible with SPAWARSYSCEN Atlantic corporate standard software configuration as specified below. Contractor shall conform to SPAWARSYSCEN Atlantic corporate standards within 30 days of task order award. The initial or future upgrades costs of the listed computer programs are not chargeable as a direct cost to the Government.

Deliverable
Software to be used
a.
Word Processing
Microsoft Word
b.
Technical Publishing
PageMaker/Interleaf/SGML/ MSPublisher
c.
Spreadsheet/Graphics
Microsoft Excel
d.
Presentations
Microsoft PowerPoint
e.
2-D Drawings/ Graphics/Schematics (new data products)
Vector (CGM/SVG)
f.
2-D Drawings/ Graphics/Schematics (existing data products)
Raster (CALS Type I, TIFF/BMP, JPEG, PNG)
g.
Scheduling
Microsoft Project
h.
Computer Aid Design (CAD) Drawings
AutoCAD/Visio
i.
Geographic Information System (GIS)
ArcInfo/ArcView

6.4 INFORMATION SYSTEM

6.4.1 Electronic Communication

The contractor shall have broadband Internet connectivity and an industry standard email system for communication with the Government. The contractor shall be capable of Public Key Infrastructure (PKI) client side authentication to DOD private web servers. Unless otherwise specified, all key personnel on task shall be accessible by e-mail through individual accounts during all hours.

6.4.2 Information Security

Pursuant to DoDM 5200.01, the contractor shall provide adequate security for all unclassified DoD information passing through non-DoD information system including all subcontractor information systems utilized on task. The contractor shall disseminate unclassified DoD information within the scope of assigned duties and with a clear expectation that confidentiality is preserved. Examples of such information include the following: non-public information provided to the contractor, information developed during the course of the task order, and privileged task order information (e.g., program schedules and task order-related tracking).

6.4.2.1 Safeguards

The contractor shall protect Government information and shall provide compliance documentation validating they are meeting this requirement in accordance with DFARS clause 252.204-7012. The contractor and all subcontractors shall abide by the following safeguards:

(a) Do not process DoD information on public computers (e.g., those available for use by the general public in kiosks or hotel business centers) or computers that do not have access control.

(b) Protect information by at least one physical or electronic barrier (e.g., locked container or room, login and password) when not under direct individual control.

(c) Sanitize media (e.g., overwrite) before external release or disposal.

(d) Encrypt all information that has been identified as controlled unclassified information (CUI) when it is stored on mobile computing devices such as laptops and personal digital assistants, or removable storage media such as portable hard drives and digital optical disks, using DoD Authorized Data-at-Rest encryption technology. NOTE: Thumb drives are not authorized for DoD work, storage, or transfer. Use GSA Awarded DAR solutions (GSA # 10359) complying with ASD-NII/DOD-CIO Memorandum, “Encryption of Sensitive Unclassified Data-at-Rest on Mobile Computing Devices and Removable Storage.” The contractor shall ensure all solutions meet FIPS 140-2 compliance requirements.

(e) Limit information transfer to subcontractors or teaming partners with a need to know and a commitment to at least the same level of protection.

(f) Transmit e-mail, text messages, and similar communications using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and Transport Layer Security (TLS). Encrypt organizational wireless connections and use encrypted wireless connection where available when traveling. If encrypted wireless is not available, encrypt application files (e.g., spreadsheet and word processing files), using at least application-provided password protection level encryption.

(g) Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

(h) Do not post DoD information to Web site pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to Web site pages that control access by user identification or password, user certificates, or other technical means and provide protection via use of TLS or other equivalent technologies. Access control may be provided by the intranet (vice the Web site itself or the application it hosts).

(i) Provide protection against computer network intrusions and data exfiltration, minimally including the following:

1. Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

2. Monitoring and control of inbound and outbound network traffic as appropriate (e.g., at the external boundary, sub-networks, individual hosts) including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services.

3. Prompt application of security-relevant software patches, service packs, and hot fixes.

(j) As applicable, comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, critical program information (CPI), personally identifiable information, export controlled).

(k) Report loss or unauthorized disclosure of information in accordance with contract, task order, or agreement requirements and mechanisms.

6.4.2.2 Compliance

Pursuant to DoDM 5200.01, the contractor shall include in their quality processes procedures that are compliant with information security requirements.

7.0 QUALITY

7.1 QUALITY SYSTEM

Upon task order award, the prime contractor shall have and maintain a quality system that meets contract and task order requirements and program objectives while ensuring customer satisfaction and defect-free products/process. The contractor shall have an adequately documented quality system which contains processes, procedures, planning, and all other documentation and data necessary to provide an efficient and effective quality system, which includes an internal auditing system. Thirty (30) days after task order award, the contractor shall be able to provide, as requested by the Government, a copy of the contractor’s Quality Assurance Plan (QAP) and any other quality related documents (CDRL A006). The contractor shall make their quality system available to the Government for review at both a program and worksite services level during predetermined visits. Existing quality documents that meet the requirements of this task order may continue to be used. If any quality documentation is disapproved or requires revisions, the contractor shall correct the problem(s) and submit revised documentation NLT 2 weeks after initial disapproval notification. The contractor shall also require all subcontractors to possess a quality assurance and control program commensurate with the services and supplies to be provided as determined by the prime’s internal audit system. The Government reserves the right to disapprove the contractor’s and/or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet contractual requirements at either the program or worksite services level. The Government reserves the right to participate in the process improvement elements of the contractor’s quality assurance plan or quality system, and development of quality related documents. At a minimum, the contractor shall ensure their quality system meets the following key criteria:

· Establish documented, capable, and repeatable processes

· Track issues and associated changes needed

· Monitor and control critical process, product, and service variations

· Establish mechanisms for feedback of field product and service performance

· Implement and effective root-cause analysis and corrective action system

· Establish methods and procedures and create data used for continuous process improvement

7.2 MANAGE QUALITY COMPLIANCE

7.2.1 General

The contractor shall have quality processes or a Quality Management System (QMS) processes in place that coincide with the Government’s Manage Quality processes which address Quality Control, Quality Assurance, Software Quality, and/or project Quality System tasks. The contractor shall use best industry practices including, when applicable, ISO/IEC 15288 for System life cycle processes and ISO/IEC 12207 for Software life cycle processes. As applicable, the contractor shall also support and/or participate in Acquisition Milestones, Phases, and Decision Points, which are standard elements of the Defense Acquisition System and support DoDD 5000.01 and DoDI 5000.02. The contractor shall provide technical program and project management support that will mitigate the risks to successful program execution including employment and objective evidence of Lean Six Sigma, Risk Management, and System Engineering methodologies; and System and Software Engineering best practices. As part of a team, the contractor shall support projects at SPAWARSYSCEN Atlantic that are currently, or in the process of, being assessed under a Capability Maturity Model Integration (CMMI) program. The contractor shall be required to utilize the processes and procedures already established for the project and deliver products that are compliant with the aforementioned processes and procedures that is commensurate with the CMMI level the government project is at or working towards. Contractor is not required to have a formal CMMI appraisal; however, possession is desired.

7.2.2 Navy Shipboard/Submarine work

The contractor shall ensure the quality of all services provided under this task order shall be compliant to ISO 9001 in the relevant profession, trade or field of endeavor. Upon task order award, the Prime contractor shall have in place, an existing Government approved QMS by the NAVSEA Quality Programs and Certification Office (04RP office) for shipboard and submarine work pursuant to NAVSEA Technical Specification 9090-310 and/or applicable NAVSEA Standard Items. The documented QMS will be used to ensure that the end product of and services associated with each task conforms to contract and task order requirements whether produced by the Contractor or provided by approved subcontractors or vendors. The QMS will provide for control over all phases of the various types of tasks, from initial manning and material ordering to completion of final tasking, before offering to the Government for acceptance as specified in this task order PWS. The contractor shall ensure all services are rendered accordingly to the documented QMS, and personnel are directly supervised by individuals qualified in the relevant profession or trade.

7.3 QUALITY ASSURANCE

The contractor shall perform all quality assurance process audits necessary in the performance of the various tasks as assigned and identified in the contractor‘s Quality Assurance Plan (QAP) or by the respective WBS, POA&M, or quality system/QMS documentation in support of continuous improvement. The contractor shall deliver related QAP and any associated procedural documents upon request. The Government reserves the right to perform any additional audits deemed necessary to assure that the contractor processes, products, and related services, documents, and material meet the prescribed requirements and to reject any or all processes or related products, services, documents, and material in a category when noncompliance is established.

7.4 QUALITY CONTROL

The contractor shall perform all quality control inspections necessary in the performance of the various tasks as assigned and identified in the contractor QAP or by the respective WBS, POA&M, or quality system/QMS documentation. The contractor shall submit the following related quality objective evidence (CDRL A006) upon request:

· Detailed incoming receipt inspection records

· First article inspection records

· Certificates of Conformance

· Detailed sampling inspection records based upon MIL-STD-1916 (Verification Level III)

· Quality Measurement and Analysis metrics/data The Government reserves the right to perform any inspections or pull samples as deemed necessary to assure that the contractor provided services, documents, material, and related evidence meet the prescribed requirements and to reject any or all services, documents, and material in a category when nonconformance is established.

8.0 SECURITY

8.1 ORGANIZATION

8.1.1 Security Classification

All work performed under this task order is “unclassified.” A facility security clearance (FCL) is not required; therefore, DoD Contract Security Classification Specification, DD Form 254, does not exist. Pursuant to DoDM 5200.01 – Volume 4, Controlled Unclassified Information (CUI), the contractor shall safeguard any sensitive Government information.

8.2 PERSONNEL

The contractor shall conform to the security provisions of DoDI 5220.22/DoD 5220.22-M – National Industrial Security Program Operating Manual (NISPOM), SECNAV M-5510.30, DoD 8570.01-M, and the Privacy Act of 1974. Prior to any labor hours being charged on this task order, the contractor shall ensure all personnel (including administrative and subcontractor personnel) have obtained and can maintain favorable background investigations at the appropriate level(s) for access required for the task order, and if applicable, are certified/credentialed for the CSWF. A favorable background determination is determined by either a Tier 1 (T1) investigation, Tier 3 (T3) investigation, or Tier 5 (T5) investigation and favorable Federal Bureau of Investigation (FBI) fingerprint checks. Investigations are not necessarily required for personnel performing unclassified work who do not require access to Government installations/facilities, Government IT systems and IT resources, or SPAWARSYSCEN Atlantic information. Cost to meet these security requirements is not directly chargeable to task order.

NOTE: If a final determination is made that an individual does not meet or cannot maintain the minimum security requirements, the contractor shall permanently remove the individual from SPAWARSYSCEN Atlantic facilities, projects, and/or programs. If an individual who has been submitted for a fitness determination or security clearance is "denied," receives an "Interim Declination," or unfavorable fingerprint, the contractor shall remove the individual from SPAWARSYSCEN Atlantic facilities, projects, and/or programs until such time as the investigation is fully adjudicated or the individual is resubmitted and is approved. All contractor and subcontractor personnel removed from facilities, projects, and/or programs shall cease charging labor hours directly or indirectly on task orders.

8.2.2 Access Control of Contractor Personnel

8.2.2.1 Physical Access to Government Facilities and Installations Contractor personnel shall physically access Government facilities and installations for purposes of site visitation, supervisory and quality evaluation, work performed within Government spaces (either temporary or permanent), or meeting attendance. Individuals supporting these efforts shall comply with the latest security regulations applicable to the Government facility/installation.

(a) The majority of Government facilities require contractor personnel to have an approved visit request on file at the facility/installation security office prior to access. For admission to SPAWARSYSCEN Atlantic facilities/installations, the contractor shall forward a visit request to Joint Personnel Adjudication System (JPAS) /SMO 652366, or submit request on company or agency letterhead by fax to (843)218-4045 or mail to Space and Naval Warfare Systems Center Atlantic, P.O. Box 190022, North Charleston, SC 29419-9022, Attn: Security Office. For visitation to all other Government locations, the contractor shall forward visit request documentation directly to the on-site facility/installation security office.

(b) Depending on the facility/installation regulations, contractor personnel shall present a proper form of identification(s) and vehicle proof of insurance or vehicle rental agreement. NOTE: SPAWARSYSCEN Atlantic facilities located on Joint Base Charleston require a Common Access Card (CAC) each time physical installation access is required. Contractor shall contact SPAWARSYSCEN Atlantic Security Office directly for latest policy.

(c) All contractor persons engaged in work while on Government property shall be subject to inspection of their vehicles at any time by the Government, and shall report any known or suspected security violations to the Security Department at that location.

8.2.2.2 Identification and Disclosure Requirements

Contractor and subcontractor employees shall take all means necessary to not represent themselves as Government employees. All contractor personnel shall follow the identification and Government facility disclosure requirement as specified in contract clause 5252.237-9602, Contractor Identification.

8.2.2.3 Government Badge Requirements

Some contract personnel shall require a Government issued picture badge in accordance with contract clause 5252.204-9202, Contractor Picture Badge. While on Government installations/facilities, contractors shall abide by each site’s security badge requirements. Various Government installations are continually updating their security requirements to meet Homeland Security Presidential Directive (HSPD-12) identification standards. Contractors are responsible for obtaining and complying with the latest security identification requirements for their personnel. Contractors shall submit valid paper work (e.g., site visit request, request for picture badge, and/or SF-86 for CAC) to the applicable Government security office via the COR. The contractor FSO shall track all personnel holding local Government badges at the task order level.

8.2.2.4 Common Access Card (CAC) Requirements

Some Government facilities/installations (e.g., Joint Base Charleston) require contractor personnel to have a CAC for physical access to the facilities or installations. Contractors supporting work that requires access to any DoD IT/network also requires a CAC. Granting of logical and physical access privileges remains a local policy and business operation function of the local facility. The contractor is responsible for obtaining the latest facility/installation and IT CAC requirements from the applicable local Security Office. When a CAC is required to perform work, contractor personnel shall be able to meet all of the following security requirements prior to work being performed:

(a)Pursuant to DoDM 1000.13-V1, issuance of a CAC is based on the following four criteria:
1.eligibility for a CAC – to be eligible for a CAC, Contractor personnel’s access requirement shall meet one of the following three criteria: (a) individual requires access to multiple DoD facilities or access to multiple non-DoD federally controlled facilities on behalf of the SPAWARSYSCEN Atlantic on a recurring bases for a period of 6 months or more, (b) individual requires both access to a DoD facility and access to DoD network on site or remotely, or (c) individual requires remote access to DoD networks that use only the CAC logon for user identification.
2.verification of DoD affiliation from an authoritative data source – CAC eligible personnel must be registered in the Defense Enrollment Eligibility Reporting Systems (DEERS) through either an authoritative personnel data feed from the appropriate Service or Agency or Trusted Associated Sponsorship System (TASS).
3.completion of background vetting requirements according to FIPS PUB 201-2 and DoD 5200.2-R – at a minimum, the completion of FBI fingerprint check with favorable results and submission of a T1 investigation to the Office of Personnel Management (OPM), or a DoD-determined equivalent investigation. NOTE: Contractor personnel requiring logical access shall obtain and maintain a favorable T3 investigation. Contractor personnel shall contact the SPAWARSYSCEN Atlantic Security Office to obtain the latest CAC requirements and procedures.
4.verification of a claimed identity – all contractor personnel shall present two forms of identification in its original form to verify a claimed identity. The identity source documents must come from the list of acceptable documents included in Form I-9, OMB No. 115-0136, Employment Eligibility Verification. Consistent with applicable law, at least one document from the Form I-9 list must be a valid (unexpired) State or Federal Government-issued picture identification (ID). The identity documents will be inspected for authenticity, scanned, and stored in the DEERS.
(b)When a contractor requires logical access to a Government IT system or resource (directly or indirectly), the required CAC will have a 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-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 task order 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 SPAWARSYSCEN Atlantic Information Systems Security Management (ISSM) office:
1.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 SPAWARSYSCEN Atlantic ISSM office at phone number (843)218-6152 or e-mail questions to ssc_lant_iam_office.fcm@navy.mil for additional instructions. Training can be taken at the IAM office or online at http://iase.disa.mil/index2.html.
2.For SAAR-N form, the contractor shall use OPNAV 5239/14 (Rev 9/2011). Contractors can obtain a form from the SPAWARSYSCEN Atlantic ISSM office at or from the website: https://navalforms.documentservices.dla.mil/. Digitally signed forms will be routed to the ISSM office via encrypted e-mail to ssclant_it_secmtg@navy.mil.

8.2.2.5 Contractor Check-in and Check-out Procedures

All SPAWARSYSCEN Atlantic contractor personnel requiring or possessing a Government badge and/or CAC for facility and/or IT access shall have a SPAWARSYSCEN Atlantic Government sponsor and be in compliance with the most current version of Contractor Check-in and Check-out Instruction and Forms as posted on the Command Operating Guide (COG) website. Throughout task order performance, the contractor shall provide necessary employee information and documentation for employees hired, transferred, and/or terminated in support of this task order within the required timeframe as cited in the Check-in and Check-out instructions. The contractor (FSO, if applicable) shall ensure all contractor employees whose services are no longer required on this task order return all applicable Government documents/badges to the appropriate Government representative. NOTE: If the contractor does not have access to the SPAWARSYSCEN Atlantic COG website, the contractor shall get all necessary instruction and forms from the COR.

8.2.2.6 Accessing Navy Enterprise Resources Planning (ERP) System Contractor personnel shall not access the Navy Enterprise Resource Planning (Navy ERP) system. Prior to accessing any Navy ERP System, contractor personnel shall contact the COR or Contracting Officer to obtain the applicable NMCI Assistant Customer Technical Representative (ACTR) who can assign each personnel with an NMCI account. ACTRs can be found on the NMCI Homeport website at: https://nmcicustomerreporting/CTR_Lookup/index.asp. After an NMCI account has been established, the contractor shall submit a request for Navy ERP access and specify the role required via the COR to the Competency Role Mapping POC. The COR will validate the need for access, ensure all prerequisites are completed, and with the assistance of the Role Mapping POC, identify the Computer Based Training requirements needed to perform the role assigned. Items to have been completed prior to requesting a role for Navy ERP include: SAAR-N, annual cybersecurity training certificate, and Questionnaire for Public Trust Positions. For directions on completing the Questionnaire for Public Trust Positions, the contractor is instructed to consult with its company’s Security Officer. In order to maintain access to required systems, the contractor shall ensure completion of annual cybersecurity training, monitor expiration of requisite background investigations, and initiate re-investigations as applicable.

8.2.3 Security Training

Applicable for unclassified and classified contracts, contractor personnel (including subcontractors) shall complete all required mandatory Government training in accordance with COMSPAWARSYSCOM Code 80330 mandatory training webpage: https://wiki.spawar.navy.mil/confluence/display/HQ/Employee+Mandatory+Training. Contractors without access to the SPAWAR webpage shall coordinate with the COR concerning mandatory training as listed on the training webpage.

8.3 OPERATIONS SECURITY (OPSEC) REQUIREMENTS

Security programs are oriented towards protection of classified information and material. Operations Security (OPSEC) is an operations function which involves the protection of any critical information – focusing on unclassified information that may be susceptible to adversary exploitation. Pursuant to DoDD 5205.02E and SPAWARINST 3432.1, SPAWARSYSCEN Atlantic’s OPSEC program implements requirements in DoD 5205.02-M – OPSEC Program Manual and SPAWARSYSCENLANTINST 3070.1B. Note: OPSEC requirements are applicable when task order personnel have access to either classified information or unclassified Critical Program Information (CPI)/sensitive information.

8.3.1 Local and Internal OPSEC Requirement

Contractor personnel, including subcontractors if applicable, shall adhere to the OPSEC program policies and practices as cited in the SPAWARINST 3432.1 and existing local site OPSEC procedures. The contractor shall development their own internal OPSEC program specific to the task order and based on SPAWARSYSCEN Atlantic OPSEC requirements. At a minimum, the contractor’s program shall identify the current SPAWARSYSCEN Atlantic site OPSEC Officer/Coordinator.

8.3.2 OPSEC Training

Contractor shall track and ensure applicable personnel receive initial and annual OPSEC awareness training in accordance with requirements outline in the Security Training, Para 8.2.3. OPSEC training requirements are applicable for personnel during their entire term supporting this SPAWARSYSCEN Atlantic task order.

8.3.3 SPAWARSYSCEN Atlantic OPSEC Program

Contractor shall participate in SPAWARSYSCEN Atlantic OPSEC program briefings and working meetings, and the contractor shall complete any required OPSEC survey or data call within the timeframe specified.

8.4 EFFECTIVE USE OF CONTROLS

The contractor shall screen all electronic deliverables or electronically provided information for malicious code using DoD approved anti-virus software prior to delivery to the Government. The contractor shall utilize appropriate controls (firewalls, password protection, encryption, digital certificates, etc.) at all times to protect task order related information processed, stored or transmitted on the contractor’s and Government’s computers/servers to ensure confidentiality, integrity, availability, authentication and non-repudiation. The contractor shall ensure provisions are in place that will safeguard all aspects of information operations pertaining to this task order in compliance with all applicable PWS references. In compliance with Para 6.4.2.1, the contractor shall ensure Data-at-Rest is required on all portable electronic devices including storage of all types. Encryption/digital signing of communications is required for authentication and non-repudiation. The contractor shall follow minimum standard in SECNAV M-5510-36 for classifying, safeguarding, transmitting, and destroying classified information.

9.0 GOVERNMENT FURNISHED INFORMATION (GFI)

Government Furnished Information (GFI) is Government owned intellectual property provided to contractors for performance on a task order. For the purposes of this task order, GFI includes manuals, technical specifications, maps, building designs, schedules, drawings, test data, etc. Depending on information contained in a document, the contractor shall comply with additional controls (e.g., completion of a Non-Disclosure Agreements, etc.) for access and distribution.

GFI is not anticipated on this task order.

10.0 GOVERNMENT PROPERTY

As defined in FAR Part 45, Government property is property owned or leased by the Government which includes Government-furnished property (GFP) and Contractor-acquired property (CAP). Government property is material, equipment, special tooling, special test equipment, and real property.

GFP will not be provided and CAP is not anticipated on this task order.

10.1 GOVERNMENT-FURNISHED PROPERTY (GFP)

As defined in FAR Part 45, 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 spares and property furnished for repair, maintenance, overhaul, or modification. GFP includes Government-furnished equipment (GFE), Government-furnished material (GFM), Special Tooling (ST) and Special Test Equipment (STE).

GFP will not be provided on this task order.

10.1.1 Government Property Records

Pursuant to FAR clause 52.245-1, contractors and any subcontractors if applicable shall be responsible for establishing and maintaining records of Government Property in their possession – this includes GFP and CAP. The contractor shall ensure GFP and CAP records contain, at a minimum, the data elements as described in FAR clause 52.245-1 and GFP records also contain the data elements specified in the DFARS clause 252.211-7007.

10.1.1.1 The contractor shall ensure all GFP and CAP identified in the Contractor’s Property Management System are designated appropriately as material, equipment, ST and/or STE. The contractor shall work with the COR and designated contract Property Administrator to maintain adequate GFP records. The contractor shall forward the GFP inventory to SPAWARSYSCEN Atlantic functional mailbox for review, tracking, and centralization which is required as part of the monthly TOSR (CDRL A002).

10.1.2 Government Property Transferring Accountability

GFP 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 and/or task orders. Unlike GFP, CAP cannot be transferred.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.