PWS_SAP_23Apr18_final.docx
DOCX document 74 KB Posted
- Attached to
- NOTICE OF INTENT TO SOLE SOURCE AWARD TO CDS2
- Solicitation number
- N65236-18-Q-0136
View the file
Other files
On GovTribe
Work with this file
- 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: MOBILE COMMUNICATIONS VEHICLE (MCV) FULL RATE PRODUCTION (FRP) ENGINEERING AND INTEGRATION
1.0 PURPOSE
Provide programmatic and technical support services for the White House Communications Agency (WHCA) Mobile Communications Vehicle (MCV) project. For the purpose of this PWS, the term “platform integration” refers to incorporation of Government furnished post milestone C (full-rate production) and/or Commercial Off-The-Shelf (COTS) systems, typically the integration of communication systems (including all components) into a commercial vehicle.
1.1 SCOPE
Work under this task order shall include design, integration, troubleshooting and basic operation of combinations of the following communications systems and associated antennas into a commercial platform:
· Commercial (Wideband) SATCOM
· Narrowband (Military) SATCOM
· Cellular Voice and Data Systems
· Wireless Data Networks
· Military and Public Safety Line of Site Radio Systems
· Computer systems (Thick Client)
· Networking systems
· Power and grounding systems
· Peripheral devices (connectors, cabling, terminators, coupling, keyboard/video/mouse switches, etc.)
· Video Surveillance Systems
2.0 PLACE(S) OF PERFORMANCE
2.1 GOVERNMENT FACILITIES
No Government facilities (i.e., office space or lab space) are provided on this task order. Work shall be performed at the contractor facility and/or temporarily at locations specified under travel.
2.2 CONTRACTOR FACILITIES
A significant portion of work issued under this task order requires close liaison with the Government. The contractor shall be prepared to establish a local facility within a ten (10)-mile radius of Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic). Close proximity allows for proper task order administration duties. The contractor’s facility is not necessary for the exclusive use of this task order and can be utilized on a shared basis. For task orders with Government Property, the contractor’s facility shall include physical security to protect Government assets as identified in Para10.0. The contractor shall meet all facility location and size upon award. Facility space shall include an integration bay and staging area for materials and equipment.
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 do 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 PROGRAM MANAGEMENT
| 3.1.1 | Coordinate and prioritize the performance of work on this task order within established cost and schedule parameters. |
| 3.1.2 | Assign, monitor, and assist with daily integration tasks. |
| 3.1.3 | Track/update inventory report weekly and report any shortage to the Government as soon as possible to ensure the Government can replenish any required item in a timely manner. The updated inventory report shall be included with the weekly Task Order Status Report (TOSR) (CDRL A001). |
3.2 TECHNICAL SUPPORT
3.2.1 MCV Integration and Testing Support
[NOTE: Full vehicle integration completion for the last two MCVs (CDRL ND-1) will be accomplished in accordance with the Government’s schedule.]
| 3.2.1.1 | Maintain the contractor facility for integration efforts. |
| 3.2.1.2 | Complete the integration of all remaining MCVs with communications, network, and power equipment as per the MCV Technical Data Package (TDP) and associated design changes, as required. All required tools are available for contractor use and located at the work location. Any shortfalls that are identified will be resolved through a Government procurement action. Integration efforts shall include the following: |
· Install racks and brackets.
· Install vehicle platform power distribution system per design
· Install antennas on roof of each vehicle.
· Install network equipment within each vehicle.
· Install video surveillance equipment within each vehicle
· Install communications equipment within each vehicle.
· Perform power and data connectivity tests on integrated components through the installation process.
· Fabricate, test, and integrate all required cables to include CAT5e, complex payload system DC and AC power system cables, RF (Heliax/LMR/RG), audio system cables, security surveillance system cables, and vehicular low voltage DC cables (CDRL ND-2).
· Note discrepancies discovered during integration to assist the Government updating design changes/drawing package.
· Diagnose cable (physical layer) faults and repair cable faults (coaxial, CAT-5e, etc.).
4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS
The services provided on contract are not IT related.
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 TOSR (CDRL A001) and submit it weekly. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor reports. The TOSR shall include the following:
(a) Weekly TOSR – the contractor shall develop and submit a weekly status report which is e-mailed to the COR no later than close of business (COB) every Friday. The first report is required on the first Friday following the first full week after the task order award date. The contractor shall ensure the weekly report includes a Plan of Action and Milestones (POA&M) that depicts major tasks and events from start to completion of the PWS. The schedule shall be maintained in a Microsoft Project 2010 compatible format. At a minimum, the contractor shall include in the weekly report the following items and data:
| 1. | Percentage of work completed |
| 2. | Percentage of funds expended |
| 3. | Updates to the POA&M and narratives to explain any variances |
| 4. | If applicable, notification when obligated costs have exceeded 75% of the amount authorized |
5.3.1.2 Contract/Task Order Closeout Report
The contractor shall develop a contract/task order closeout report (CDRL A002) and submit it no later than 15 days before the task order completion date. The prime contractor 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 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 A003) 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 (Attachment #1). 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 A004) submitted 10 days after task order award and CPARS Draft Approval Document (CDAD) Report (CDRL A005) 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 |
| Task Order Status Report (TOSR) |
| 3.1.3; 5.3.1.1; 10.3.5.1 |
| WEEKLY |
| COB every Friday |
| Unclassified |
| A002 |
| Contract/Task Order Closeout Report |
| 5.3.1.2; 10.3.8 |
| 1TIME |
| NLT 15 days before completion date |
| Unclassified |
| A003 |
| Invoice Support Documentation |
| 5.3.1.3 |
| ASREQ |
| Within 24 hrs from request |
| Unclassified |
| A004 |
| 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 |
| Unclassified |
| A005 |
| Contractor CPARS Draft Approval Document (CDAD) Report |
| 5.4 |
| MTHLY |
| 30 DATO and monthly on the 10th |
| Unclassified |
6.2 NON-DATA DELIVERABLES
The following table lists all required non-data deliverables:
| # |
| Deliverable Title |
| PWS Reference Para |
| Frequency |
| Date Due |
| ND-1 |
| Fully Integrated MCV (Qty 2) |
| 3.2.1 |
| 1TIME |
| In accordance with the SPAWAR delivery schedule |
| ND-2 |
| Fabricated Cables |
| 3.2.1.2 |
| As Required |
| In accordance with the SPAWAR delivery schedule |
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 |
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
All Quality Control and Quality Assurance functions to include auditing and inspections will be performed by the Government.
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 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.2.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.2.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.2.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.3 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 utilized on this task order. Any applicable document (PWS Para 16.0) not available online, the Government will provide document as GFI listed in the table below. The contractor shall inventory all GFI by tracking distribution and location and provide a GFI inventory to the Government. The contractor shall use the GFI provided to support this task order only – use of GFI document(s) to support other projects beyond this task order is not allowed. Unless otherwise specified, all GFI will be provided by the Government by the estimated delivery date listed in the table below, and the contractor shall return all GFI to the Government at completion of the task order. If a contractor requires additional GFI other than what is listed, the contractor shall submit a request to the COR within 30 days after task order award.
| Item # |
| Description |
| GFI Estimated Delivery Date |
| 1 |
| MCV Technical Data Package |
Per the Project Schedule
| 2 |
| MCV Management Documents |
Per the Project Schedule
| 3 |
| Vendor Equipment Manuals |
Upon Receipt From Vendor
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.
Government property includes GFP, but does not include intellectual property and software. The contractor shall have established property management procedures and an appropriate property management point of contact who shall work with the assigned Government Property Administrator to ensure their property management system is acceptable.
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).
Utilizing GFP on this task order is authorized in accordance with DFARS requirements. The contractor shall meet applicable FAR requirements for the use and charges of GFP. The contractor shall have the means to provide an effective and efficient stewardship of Government property. NOTE: The contractor shall only receive items listed in the Consolidated GFP form and shall only take possession of items not in excess of the maximum promised quantity identified in the GFP form. If additional items or increased quantities are required, a modification to the task order is needed which includes a revised GFP form being uploaded to Electronic Document Access (EDA) system. The following types of GFP are applicable on this task order:
10.1.1 Government-Furnished Equipment
GFE is Property, Plant and Equipment (PP&E) provided to the contractor. It consists of tangible items that are functionally complete for their intended purpose, durable, non-expendable, and needed for the performance of a contract. It is not intended for sale and does not ordinarily lose its identity or become a component part of another article when put into use. It does not include material, real property, special test equipment or special tooling. GFE will be provided to the contractor as identified on the Consolidated GFP form, Attachment #2.
10.1.2 Government-Furnished Material
GFM is Operating Material and Supplies (OM&S) provided to the contractor. It may be consumed or expended during the performance of a contract, component parts of a higher level assembly, or items that lose their individual identity through incorporation into an end-item. It does not include equipment, special tooling, special test equipment, or real property. GFM will be provided to the contractor as identified on the Consolidated GFP form, Attachment #2.
10.2 CONTRACTOR-ACQUIRED PROPERTY (CAP)
As defined in FAR Part 45, CAP is property acquired, fabricated, or otherwise provided by the contractor for performing a contract and to which the Government has title but has not yet performed receipt and acceptance. CAP consists of Contractor-acquired equipment (CAE), Contractor-acquired material (CAM), ST, and STE.
CAP is not anticipated on this task order.
10.3 GOVERNMENT PROPERTY MANAGEMENT
10.3.1 Contractor Property Management System
Pursuant to FAR clause 52.245-1 and DFARS clause 252.245-7003, the contractor shall establish and maintain an acceptable property management system that is subject to review and approval by the Contracting Officer and task order Government Property Administrator. The contractor’s property management system shall adhere to the applicable prescribed requirements in FAR clause 52.245-1 and include the required data elements in DFARS clause 252.211-7007. The contractor shall ensure GFP in the possession of a subcontractor shall also be reported using the required data elements cited in DFARS clause 252.211-7007.
10.3.2 Government Property Administrator
As allowed by FAR Subpart 42.201, the contract property administrator under this contract is, unless otherwise designated, the Defense Contract Management Agency (DCMA). The contractor shall work with the Contracting Officer appointed PA to ensure compliance with the contract’s property requirements in accordance with DoDI 4161.02 and the Guidebook for Contract Property Administration. For contractors without an approved property management system, the contractor shall contact the appointed PA within 30 days of contract award, and provide a copy of their property management procedures with the names of appropriate points of contact.
10.3.3 GFP Transfer between Government and Contractor
Contractors shall not take receipt or transfer custody of any GFP without possessing proper contractual authority; i.e.; GFP items must be specified on a Consolidated GFP form which is tied to one specific contract or task order. The contractor shall perform GFP reporting as required by DFARS clause 252.211-7007. The primary and preferred means of reporting is via electronic transfer transaction in Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT), an application within WAWF, which will automatically transmit the GFP custody information to the GFP Repository within the Item Unique Identification (IUID) Registry. For non-serially managed GFP items, the contractor shall only report the initial receipt. For serially-managed GFP items, the contractor shall report all subsequent transactions affecting GFP custody. In order to perform electronic transaction reporting in iRAPT, the contractor shall register for iRAPT access and obtain the Contractor Property Shipper and Contractor Property Receiver roles.
Note: As a backup process to the electronic tracking, SPAWARSYSCEN Atlantic property management specifies use of Requisition and Invoice/Shipping Document (DD1149) and/or COMSEC Material Report (SF153) to validate actual transfer of property physically occurred. The contractor shall ensure all received and returned items are documented with proper paperwork.
10.3.4 GFP Tagging, Labeling and Marking
The contractor shall tag, label, or mark all serially managed GFP items not previously tagged, labeled, or marked. This does not refer specifically to an IUID tag, label or mark.
10.3.5 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.3.5.1 The contractor shall ensure all GFP 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 weekly TOSR (CDRL A001).
10.3.5.2 For all GFP items including laptops (identified on the Consolidated GFP 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 task order 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.
10.3.6 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. If CAP is required to be utilized on a contract or task order other than the one that funded its acquisition, it must be delivered to the Government. Once received and accepted by the Government, it can be provided as GFP on the same or another contract.
10.3.7 Government Property Lost or Damaged Items
Contractor shall promptly report to the COR and Contracting Officer all lost and/or damaged Government property. The requirements and procedures for reporting lost Government Property are specified in DFARS clause 252.245-7002.
10.3.8 Government Property Inventory Disposition
When disposition instructions for GFP are contained in the accountable task order or on the supporting shipping documents (DD Form 1149), the Contractor shall initiate and submit an excess inventory listing to the Contracting Officer, via the activity Property Administrator.
Pursuant to DFARS clause 252.245-7004, when disposition instructions are not stipulated in the task order or supporting shipping document (DD Form 1149), an excess inventory listing is required that identifies GFP. 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. Note: If any Government property is slated for demilitarization, mutilation, or destruction by the contractor, the event shall be witnessed and verified by the COR or the designated Government personnel.
The contractor shall include a final inventory reporting list in the Contract/Task Order Closeout Report (CDRL A002). 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.
10.3.9 Government Property Performance Evaluation
Non-compliance with Government Property terms and conditions will negatively affect the contractor’s annual CPARS rating.
10.4 TRANSPORTATION OF EQUIPMENT/MATERIAL
No transportation of equipment/material is required by the contractor on this task order.
11.0 TRAVEL
No travel requirements are anticipated under this task order.
12.0 SAFETY ISSUES
12.1 OCCUPATIONAL SAFETY AND HEALTH REQUIREMENTS
The contractor shall be responsible for ensuring the safety of all company employees, other working personnel, and Government property. The contractor is solely responsible for compliance with the Occupational Safety and Health Act (OSHA) (Public Law 91-596) and the resulting applicable standards, OSHA Standard 29 CFR 1910 (general), 1915 (shipboard/submarine) and 1926 (shore), and for the protection, safety and health of their employees and any subcontractors assigned to the task orders. Without Government assistance, the contractor shall make certain that all safety requirements are met, safety equipment is provided, and safety procedures are documented as part of their quality management system. If performing within Government facilities, contractor shall immediately report any accidents involving Government or contractor personnel injuries or property/equipment damage to the Contracting Officer and COR. Additionally, the contractor is responsible for securing the scene and impounding evidence/wreckage until released by the COR or on-site Government representative.
13.0 SUBCONTRACTING REQUIREMENTS
13.1 APPROVED SUBCONTRACTORS
Subcontracting requirements are in accordance with the basic contract. If the prime contractor is planning to utilize subcontractor(s) on this task order, the applicable subcontractors shall be specified at task order award. Per FAR clause 52.244-2, if a subcontractor (includes tier 1, tier 2, tier 3, etc.) is proposed by a prime and is not approved on the basic contract, formal justification is required and subject to Government approval.
14.0 ACCEPTANCE PLAN
Inspection and acceptance is performed by the COR on all services, data, and non-data deliverables in accordance with the QASP, Attachment #1.
15.0 OTHER CONDITIONS/REQUIREMENTS
15.1 NON-DISCLOSURE AGREEMENT (NDA) REQUIREMENTS
All Contractors and subcontractors shall sign Non-Disclosure Agreements (NDAs) (Attachment #3), essentially stating that none of the information released on this effort will include anything affiliated with the Project Sponsor. This NDA will cover all information releases including in-house company literature/brochures/etc. The contractor shall work through the government COR and associated government Public Affairs Officer (PAO), as required, prior to any company press releases.
Project related technical data shall not be stored on contractor servers. Technical data shall be stored in Government designated repositories.
16.0 APPLICABLE DOCUMENTS (AND DEFINITIONS)
The contractor shall ensure all work accomplished utilizes the latest, relevant industry practices and standards when applicable unless otherwise indicated by text. In accordance with Defense Acquisition Policy, maximum utilization of non-Government standards will be made wherever practical.
16.1 REQUIRED DOCUMENTS
The contractor shall utilize the following mandatory documents in support of this task order. The documents referenced in this section list the minimum version dates; however, the contractor shall meet requirements for any referenced document including subsequent updates applicable at time the task order request for proposal is posted.
| Document Number |
| Title |
| a. |
| DoDD 5205.02E |
| DoD Directive – Operations Security (OPSEC) Program dtd 20 Jun 12 |
| b. |
| DoD 5205.02-M |
| DoD Manual – Operations Security (OPSEC) Program Manual dtd 3 Nov 08 |
| c. |
| DoD 5220.22-M |
| DoD Manual – National Industrial Security Program Operating Manual (NISPOM) dtd 28 Feb 06 |
| d. |
| DoDI 5220.22 |
| DoD Instruction – National Industrial Security Program (NISP) dtd 18 Mar 11 |
| e. |
| SECNAV M-5510.30 |
| Secretary of the Navy Manual – DoN Personnel Security Program dtd Jun 2006 |
| f. |
| SECNAV M-5510.36 |
| Secretary of the Navy Manual – DoN Information Security Program dtd Jun 2006 |
| g. |
| SPAWARINST 3432.1 |
| Space and Naval Warfare Instruction – Operations Security (OPSEC) Policy dtd 2 Feb 05 |
| h. |
| SPAWARINST 4440.12A |
| Space and Naval Warfare Instruction – Management of Operating Materials and Supplies (OM&S), Government Furnished Property (GFP), and Inventory |
| i. |
| SPAWARSYSCENLANTINST 3070.1B |
| Space and Naval Warfare Systems Center Atlantic Instruction – Operations Security Policy dtd 20 Jan 17 |
| j. |
| Navy Telecommunications Directive (NTD 10-11) |
| System Authorization Access Request (SAAR) - Navy |
| k. |
| Privacy Act of 1974 |
| United States federal law, Pub.L. 93–579, 88 Stat. 1896, dtd December 31, 1974, 5 U.S.C. § 552a |
16.2 GUIDANCE DOCUMENTS
The contractor shall utilize the following guidance documents in support of this task order. The documents referenced in this section list the minimum version dates; however, the document’s effective date of issue is the task order’s request for proposal issue date.
| Document Number |
| Title |
| a. |
| MIL-HDBK-61A |
| Configuration Management |
| b. |
| MIL-STD-130N |
| DoD Standard Practice – Identification Marking of US Military Property |
| c. |
| DoDI 4161.02 |
| DoD Instruction – Accountability and Management of Government Contract Property dtd 27 Apr 12 |
| d. |
| NAVSEA TS9090-310F |
| NAVSEA Technical Specification 9090-310 dtd 12 Feb 15 (and subsequent revisions) |
| e. |
| ISO 9001 (ANSI/ASQ Q9001) |
| International Organization for Standardization (American National Standard Institute/American Society for Quality) – Quality Management Systems, Requirements |
| f. |
| ISO/IEC 12207 |
| International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – Software Life Cycle Processes |
| g. |
| ISO/IEC/IEEE 15288 |
| International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – System Life Cycle Processes |
| h. |
| ASTM Std E-2135-06 |
| American Section of the International Association for Testing Materials, Standard |
| i. |
| IEEE Std 12207-2008 |
| Institute of Electrical and Electronics Engineers – Systems and Software Engineering, Software Life Cycle Processes |
| j. |
| FIPS PUB 201-2 |
| Federal Information Processing Standards Publication 201-2 – Personal Identity Verification (PIV) of Federal Employees and Contractors, August 2013 |
| k. |
| Form I-9, OMB No. 115-0136 |
| US Department of Justice, Immigration and Naturalization Services, Form I-9, OMB No. 115-0136 – Employment Eligibility Verification |
| l. |
| N/A |
| SPAWARSYSCEN Atlantic Contractor Check-in portal – https://wiki.spawar.navy.mil/confluence/display/SSCACOG/Contractor+Checkin |
| m. |
| N/A |
| COMSPAWARSYSCOM Code 80330 mandatory training webpage – https://wiki.spawar.navy.mil/confluence/display/HQ/Employee+Mandatory+Training |
16.3 SOURCE OF DOCUMENTS
The contractor shall obtain all applicable documents necessary for performance on this task order. Many documents are available from online sources. Specifications and commercial/industrial documents may be obtained from the following sources:
Copies of Federal Specifications may be obtained from General Services Administration Offices in Washington, DC, Seattle, San Francisco, Denver, Kansas City, MO., Chicago, Atlanta, New York, Boston, Dallas and Los Angeles.
Copies of military specifications may be obtained from the Commanding Officer, Naval Supply Depot, 3801 Tabor Avenue, Philadelphia, PA 19120-5099. Application for copies of other Military Documents should be addressed to Commanding Officer, Naval Publications and Forms Center, 5801 Tabor Ave., Philadelphia, PA 19120-5099.
All other commercial and industrial documents can be obtained through the respective organization’s website.
LIST OF EXHIBITS & ATTACHMENTS
Exhibit A -- CDRLs - DD FORM 1423 Attachment #1 – Quality Assurance Surveillance Plan (QASP) Attachment #2 -- Consolidated GFP form Attachment #3 -- Non-Disclosure Agreement (NDA) form
[Ver dtd 31 Aug 17] 1 of 14
File details come from the government source that posted it.