PD_AWS_STS_PWS_RFI_Draft.docx

Performance Work Statement (PWS) For System Technical Support for Product Director, Army Watercraft Systems

Contract Number: TBD

Department of the Army U.S. Army TACOM Life Cycle Management Command (LCMC) Army Contracting Command – Warren Product Director, Army Watercraft Systems

TABLE OF CONTENTS

1.0 INTRODUCTION………………………………………………………………………………………………………… 3

2.0 GENERAL INFORMATION…………………………………………………………………………………………… 3

3.0 REQUIREMENTS – SPECIFIC TASKS……………………………………………………………………………… 5

4.0 ADDITIONAL CONSIDERATIONS………………………………………………………………………………… 10

5.0 DELIVERABLES…………………………………………………………………………………………………………… 13

6.0 APPLICABLE PUBLICATIONS...…………………………………………………………………………………… 14

7.0 ATTACHMENT AND TECHNICAL EXHIBIT LISTING……………………………………………………… 14

APPENDICES…………………………………………………………………………………………………………………… 14

PART 1

INTRODUCTION

1.1 Base Contract. The contractor shall adhere to all of the terms and conditions set forth in the base MA IDIQ contract. The terms and conditions in the base MA IDIQ are in full force and effect for this effort, in addition to those discussed in this Performance Work Statement (PWS). The contractor shall review sections C and H in particular for potential updates to topics that may be unique to this PWS, such as Organizational Conflicts of Interest (OCI); Inherently Government Functions; non-personal services; Contractor Manpower Reporting (CMR); and Quality Assurance Surveillance.

1.2 Executive Overview & Objectives: This non-personal service PWS establishes the requirements for contractor-provided services to the Product Director, Army Watercraft Systems (PD AWS). The scope of this PWS consists of System Technical Support to vessels under the purview of PD AWS. As a TACOM Strategic Services (TS3) task order, this effort is subject to Knowledge-Based Services multiple-award indefinite-delivery, indefinite-quantity (MA IDIQ) contract requirements. Knowledge-Based Services will require contractors to provide qualified personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform the services as defined in this PWS, except for those items specified as Government Furnished Property (GFP) and services, see Part 3 below to accomplish the services described in this PWS.

1.3 Program Office Background: PD AWS is responsible for several types of Amy Watercraft, including landing craft, tugs, barges, and a modular causeway system. These systems are out of production, and require continued support including design and application of modifications to address deficiencies or improve capabilities, technical data development and correction, and configuration management.

PART 2

GENERAL INFORMATION

2.1 General Information: This PWS applies to services required to deliver engineering analysis, design support, technical support, configuration management, quality assurance, ILS, maintenance, and related support efforts for AWS. Requirements include analysis of failures in fielded vessels, research, engineering analyses, and design and installation of hardware solutions for vessel performance issues. Specialized watercraft design and support experience is required to execute this contract. The Contractor shall be familiar with and experienced in complying with Safety of Life At Sea (SOLAS) requirements, Code of Federal Regulations Title 46 (CFR 46), American Bureau of Shipping (ABS) requirements, and general naval architecture practices.

2.2 Ordering / Task Orders / Performance Requirements: Under this effort all work shall be performed in accordance with individually issued, Cost-Plus Fixed Feed or Firm-Fixed-Price, performance-based Task Orders. Task Orders shall be added to contract via modification, issued by the Contracting Officer.

2.2.1 Minimum Order / Total Government Obligation: The guaranteed minimum value of this effort is $10,000. The Government is not obligated to issue additional effort in excess of this value.

2.2.2 Maximum Contract Value: The ceiling for the total effort under this Contract is $20M.

2.2.3 Task Order Scope: The Government may issue Technical Instructions for requirements which fall within the scope (see .3.1, 3.2, 3.3, 3.4, 3.5 below) or any combination of those areas.

2.2.4 Labor Rates by Ordering Period: The rates identified by the Contractor in Attachment XXXX, represent the ceiling rates for the applicable labor category and ordering period. The applicable rate for a given Task Order, is determined by the date of modification award, not by dates of performance (e.g. Task Order 0002 awarded via modification on final day of ordering period 1, with performance primarily in ordering period 2: Ordering period 1 ceilings apply). The Contractor may provide additional discounts on individual Task Orders.

2.2.5 Task Order Performance Beyond Ordering Period Expiration: Under this effort there are five defined 12-month ordering periods. In the even that a Task Order is issued in Ordering Period five (OP5), the Period of Performance for that Technical Instruction may continue beyond the expiration of OP5. The Period of Performance of Technical Instructions may not continue more than twelve month from the expiration date of OP5. As stated in 1.1.4 above, the applicable labor rate for a Task Order in performance across ordering periods, is determined by the date in which the modification is awarded.

2.2.6 Task Order Pricing: The Government, through the Contracting Officer, may issue Task Orders which detail the Government’s technical requirements, travel requirements, performance standards, and deliverables. Upon receipt of a Task Order, the Contractor shall provide its proposed labor mix multiplied against the applicable ceiling labor rate(s) for the applicable categories and ordering period (less any additional discounts). The Contractor shall also provide its estimated travel costs (in accordance with JTR) and any incidental material costs applicable to the effort. The Government will review the proposed labor mix, hours, travel, and material for reasonableness. Upon determination of a fair and reasonable price for the effort, the Contracting Officer will issue a performance-based firm-fixed-price Task Orders.

2.3 Contract Type: The contract type for this requirement is a combination of Cost-Plus Fixed Fee and Firm Fixed Price and Cost Reimbursement.

2.4 Commerciality: The contracting officer has determined that the services under this task order are Commercial. As such, the Commercial clauses are applicable to this Contract.

2.5 Period of Performance and Estimated Labor per Location:

The period of performance for this task order shall be for five 12 month Ordering Periods.

2.6 Place of Performance: The contractor shall perform the work under this task order at the Contractors facility and on vessels located within the continental United States, Hawaii, Kuwait, Japan and other locations worldwide. Several vessels are located at Joint Base Langley-Eustis in Newport News, VA, other vessels are located along the east and west coasts of the US, and in Hawaii, Japan and Kuwait.

2.7 Anticipated Travel: Any items added above what was estimated IAW Section H of this contract shall be approved by the PCO. The anticipated travel costs for each Ordering Period is $560,000.

2.8 Hours of Operations: Unless additional hours are coordinated in advance and approved in writing by the COR, the contractor is responsible for conducting business, no more than 10 work hours per day, 40 hours per work week, Monday through Friday, except Federal holidays or when any Government facility required for contract performance is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Lunch, rest periods and union time are not considered productive time and are not billable. If the hours required in a billing period cannot be fulfilled because of a Government-created circumstance, the contractor, COR and contracting officer will discuss an alternate billing arrangement on a case-by-case basis. The contractor must at all times maintain an adequate workforce for the performance of all tasks defined within this PWS. Upon mutual agreement of the COR and the contractor, contractor personnel may shift work hours from the Monday to Friday schedule to weekends. Any such shift will be hour for hour, meaning that any hour worked on the weekend would be offset by a corresponding reduction during the Monday through Friday period. There is no change to the labor rates for work performed during weekend periods.

2.9 Contracting Officer Representative (COR): The COR will monitor all technical aspects of the Task Order and assist in contract administration. The COR is authorized to perform the following functions:

The COR is not authorized to direct any changes to the contract. If the contractor believes an out of scope change has been directed, they are to notify the Contracting Officer in writing immediately and not proceed with this work until written authorization is received from the Contracting Officer.

2.10 Start of Work Meeting: At the discretion of the COR, the contractor shall host a Start of Work Meeting at contractor’s facility with contractor leadership, PD AWS representatives, the COR and Contracting, no later than 15 calendar days after task order award. The contractor shall outline how all tasks will be accomplished at each location and shall discuss any issues with regard to completing all assigned tasks.

2.11 Other Direct Costs (ODCs): To the extent possible, all anticipated ODCs associated with performance shall have an established task order price. Other Direct Costs must not be the primary purpose of the task order. All ODCs above $10k shall be approved by the contracting officer prior to expenditure.

PART 3

REQUIREMENTS – SPECIFIC TASKS

3.0 Scope of Work Sections. Tasks under this PWS will be assigned by Task Order (TO). Properly executed TOs will become part of this PWS. TOs may include tasks from multiple sections of this PWS.

3.0.1 Schedules. The contractor shall create a schedule (CDRL A002) for each open TO. Schedule may be in contractor format and shall have a title and TO number. Schedules shall specify all tasks necessary to complete the work prescribed by the TO. Schedules shall differentiate between tasks with durations and milestones. Schedules shall include a timeframe for each task including a start, finish, duration and will identify the task(s) actively being worked with percent completion. In addition, the schedule shall state responsible party/parties for each task. The contractor shall update and publish each schedule at IAW CDRL A002.

3.0.2 Kickoff Meeting. The contractor shall hold a Kickoff meeting for each Task Order. The kickoff meeting shall include the contractor personnel assigned to the tasks prescribed by the TO and PD AWS personnel overseeing the task order. Kickoff meetings shall be held by phone within 15 days of award of a TO unless otherwise agreed to by PD AWS. Kickoff meetings may be held in conjunction with other regularly scheduled PD AWS meetings. Following the Kickoff Meeting, the contractor shall submit meeting minutes IAW CDRL A003.

3.1 Science, Technology, Engineering, and Integration. Task Orders for engineering work will generally require a technical investigation, design of a modification to PD AWS vessels, or both. When instructed by a TO, the contractor shall perform the tasks identified below:

3.1.1 Technical Investigation. The contractor will be required to conduct technical investigations and evaluations of systems, components, and processes. Technical investigations may include analysis of failed components; investigation of field incidents; preparation of engineering calculations; fabrication of prototype hardware for trial installation and/or testing; structural analysis (stress analysis, finite element analysis, dynamic modeling, etc.) on parts, components and assemblies; system/design trade-off studies; observations of Government and/or third party tests; attendance at technical meetings; field review of modified and/or failed parts or systems; and general technical assistance on engineering matters. Specific tasks to be performed in the course of a technical investigation may be identified in the applicable TO. If specific tasks required to complete a technical investigation are not identified in the TO, the contractor shall identify and conduct the specific tasks required to deliver the end product(s) required by the TO. Technical reports shall be submitted in accordance with CDRL A004 to identify the results of investigations or evaluations with root cause(s) identified and with recommendations for future course(s) of action, such as changes to procedures, components, or systems, with supporting rationale and documentation. Documentation may include cost estimates, calculations, sketches, schematics, and other visual depictions.

3.1.1.1 Regulatory Compliance. As part of each technical investigation, the contractor shall evaluate the compliance of systems identified in applicable TOs with laws and regulations identified by the Code of Federal Regulations (CFR), International Convention on Safety of Life at Sea (SOLAS), American Bureau of Shipping (ABS), and any other applicable regulations. Compliance or non-compliance of investigated systems shall be identified in the technical report IAW CDRL A004

3.1.1.2 Temporary Modifications. As part of a technical investigation, the contractor may be required to temporarily modify a vessel system or subsystem. When required by a TO, the contractor shall conduct trial installations and tests of items (modified or replaced systems, subsystems, or parts), and test or evaluate the functionality of the item under consideration. The contractor shall supply the items for evaluation and shall restore the vessel to the original configuration at the conclusion of the test, unless otherwise specified in the TO.

3.1.2 Engineering Changes and AWS Engineering Process. The contractor will be required to develop and apply engineering changes to PD AWS vessels. For all projects resulting in a change to the configuration of a PD AWS vessel, including design of vessel modifications, integration of new parts, and additions of new tools, accessories, or equipment, the contractor shall follow the AWS engineering process below, unless otherwise instructed by the TO.

3.1.2.1 Preliminary and Critical Design Reviews. Following the kickoff meeting, the contractor shall develop design concept(s) to meet the requirements of the TO and shall present the concept(s) to the Government at a Preliminary Design Review (PDR). The contractor shall present at least 2 potential design solutions at the PDR, with a recommendation of which design solution to select, unless otherwise directed by the TO. At the PDR, the government will evaluate the design solutions and either select a design or require additional information or design solutions to be investigated. Following approval of a design solution at the PDR, the contractor shall complete detailed design work on the selected design(s) and subsequently hold a Critical Design Review (CDR) to present the completed design to the government. At the CDR, the government will evaluate the completed design and either approve the design or require changes or refinement to the design. Following the PDR and the CDR, the contractor shall submit meeting minutes IAW CDRL A003.

3.1.2.2 Preliminary ECP and CCB Review. The contractor may be required to prepare a preliminary Engineering Change Proposal (ECP) and present it at the PD AWS Configuration Control Board (CCB). If required by the TO, the contractor shall prepare and submit a preliminary ECP reflecting the outcome of the PDR. Preliminary ECPs shall be prepared IAW 3.2.3.1 and CDRL A005 except submission of Notices of Revision and Technical Data Packages not required with preliminary ECPs. Submission of a preliminary ECP does not satisfy the requirement for a formal ECP.

3.1.2.3 Prototype and Proof. When required by TO, following approval of the design at the CDR, the contractor shall build at least two prototypes of the selected design, both to be installed on fielded vessels. The first prototype shall serve to demonstrate functionality and validate the technical data package and modification instructions. Upon completion of the first prototype installation and functionality demonstration, the contractor shall hold a Prototype Review (PR) to present status to the government, identify any needed configuration changes, update the TDP as necessary, and obtain approval for the second prototype installation. The second prototype will serve as a “proof” or “LRIP,” incorporating any necessary changes identified during installation or use of the first prototype, and will serve as verification of the TDP and modification instructions. Any deviations from the TDP during the second prototype installation must be approved by PD AWS in advance, in accordance with 3.2.3.3 and CDRL A006 (Request for Variance).

3.1.2.4 Production Readiness Review. Following a successful proof installation, the contractor shall hold a Production Readiness Review (PRR) to present status and outcomes to the government and obtain approval to finalize the design and submit a formal ECP. Following the PRR, the contractor shall submit meeting minutes IAW CDRL A003. Following successful completion of the PRR, the contractor shall prepare and submit an ECP in accordance with 3.2.3.1 and CDRL A005 The contractor shall furnish all drawings and models of the new design to the government in accordance with CDRL A007.

3.1.2.5 Technical Report. Following the PRR, the contractor shall submit a technical report. Technical reports shall be submitted IAW CDRL A004 and shall thoroughly present/discuss the following: project objective; background information; technical problem; methodology of investigation, evaluation, or analysis; assumptions; trade-offs studied; impacts to the vessel system, subsystems, and vessel readiness; results of investigation, evaluation, or analysis; important findings and conclusions; recommendations for future courses of action; supporting rationale and documentation; risk assessment; and any other information the contractor deems pertinent to the project. Documentation may include cost estimates, calculations, sketches, schematics, and other visual depictions.

3.1.3 Vessel Modifications. In addition to prototype and proof installations identified in 3.1.2, the contractor may be required to complete modifications to vessels in accordance with an approved Technical Data Package (TDP). When instructed by a TO, the contractor shall complete modifications to vessels in accordance with the provided TDP, as identified in the TO. Any deviations from the approved TDP must be approved by PD AWS in advance, in accordance with 3.2.3.3 and CDRL A006. The contractor shall provide all equipment, hardware, labor, and supervision to complete the modification at the site identified in the TO.

3.2 Configuration Management. The contractor shall have a configuration management (CM) program implemented at contract award and shall comply with the requirements in EIA-649-1, this task order, corresponding CDRLS, CM Attachment 01, and applicable TOs. The contractor shall conduct the following CM tasks:

3.2.1 Configuration Management Plan. The contractor shall conduct Configuration Management, Data Management, and Planning in accordance with Principles CMP-1 through CMP-5 of EIA-649-1. The contractor shall submit a CM Plan (CMP) in accordance with CDRL A008.

3.2.2 Configuration Identification. The contractor shall conduct Configuration Identification in accordance with Principles CI-1 through CI-13 of EIA-649-1 and shall adhere to the Product and Enterprise Identifier requirements in CM Attachment 01.

3.2.2.1 The contractor shall submit Engineering Release Record(s) in accordance with CDRL A009.

3.2.2.2 The contractor shall submit Interface Control Documents (ICDs) in accordance with CDRL A010.

3.2.3 Configuration Control. The contractor shall conduct Configuration Change Management (Configuration Control) in accordance with Principles CCM-1 through CCM-9 of EIA-649-1.

3.2.3.1 The contractor shall submit Engineering Change Proposals (ECPs) in accordance with CDRL A005.

3.2.3.2 The contractor shall submit Notices of Revision (NORs) in accordance with CDRL A005.

3.2.3.3 The contractor shall submit Requests for Variances (RFVs) in accordance with CDRL A006.

3.2.4 Configuration Status Accounting. The contractor shall conduct Configuration Status Accounting in accordance with Principles CSA-1 through CSA-3 of EIA-649-1. The contractor shall submit Configuration Status Accounting Information (CSAI) in accordance with CDRL A011.

3.2.5 Configuration Verification and Audit. The contractor shall conduct Configuration Verification and Audit in accordance with Principles CVA-1 through CVA-3 of EIA-649-1.

3.2.5.1 The contractor shall submit a Configuration Audit Plan in accordance with CDRL A012.

3.2.5.2 The contractor shall submit a Configuration Audit Summary Report (CASR) in accordance with CDRL A013.

3.2.6 Technical Data Package (TDP). The Contractor shall deliver TDP per requirements in Task Order (TO), in accordance with CDRL A007, and in accordance with Attachment 02 (TDP Requirements).

3.3 Logistics. The Contractor shall plan, manage, and execute the logistics requirements described herein. Integrated Product Support (IPS) program objectives are to analyze the support requirements and to develop and deliver a logistics support package including parts, provisioning data, technical data, training, and technical support for Contractor-generated ECPs for AWS and all support items. The IPS package shall include all the logistics data specified below, which supports all generated ECPs. All IPS/Logistics Management Information (LMI) shall be prepared and delivered IAW designated CDRLs and IAW guidance provided in MIL-HDBK-502, Department of Defense Handbook for Acquisition Logistics, and MIL-PRF-49506. The Contractor shall provide IPS management support that includes:

a. End Item(s) Configuration Management Control/IPS Functional Interface

e. Vessel System Technical Publications Development (MWO)

f. The contractor shall deliver all word processing files, i.e. MS Word for Windows.

3.3.1 IPS Management Responsibilities. The Contractor shall identify an IPS Manager who will be the primary Point of Contact (POC) for the Contractor development of logistics products. The Contractors IPS manager shall:

a. Be responsible for managing Contractor efforts to meet logistics planning requirements.

b. Serve as the lead for the Contractor for IPS IPT Reviews

c. Participate in milestone planning and ensure logistics products are developed based on the jointly developed schedules.

3.3.2 IPS Management Control Log. The Contractor shall maintain an IPS Management Control Log IAW CDRL A014, with supporting documentation for Government review, as required, that tracks all changes to the production configuration baseline and subsequent IPS/LMI impact, to include the following:

a. ECP Control Number (system, subsystem, component, part)

b. Provisioning Change (Required/Not Required), by affected system, sub-system, assembly, subassembly, component Part

c. Number (P/N), Contractor and Government Entity Code (CAGEC), and NSN, if available via screening

d. Operation/Maintenance Instructions Change (Required/Not Required), short description of change.

e. Operation/Maintenance Training Material Change (Required/Not Required), short description of change.

f. Technical Publication Change (Required/Not Required), short description of change.

g. Illustrations

3.3.3 Modification Work Order. When instructed by TO, the Contractor shall prepare a Modification Work Orders (MWO) from each ECP IAW MIL-PRF-63002L(TM), AR 750-10 as well as CDRL A015. The contractor shall create fully scripted or abbreviated MWOs as directed by the TO.

3.4 Quality Assurance (QA)

3.4.1 Quality Program / System. The Contractor shall develop, implement, and maintain a quality system for all supplies and services to be provided under this contract. The quality system shall, as a minimum, meet the requirements of ANSI/ISO/ASQ ISO9001-2015 or an industry recognized equivalent standard. The Contractors quality system shall address all contract requirements, to include management, design, fabrication, processing, production, shipping, storage, site installation, software, hardware and testing at all facilities and work activities impacted by the work performed. The quality system shall follow the guidelines within ISO 9001:2015 or equivalent QS/TS guidance documents. The quality system shall achieve (i) defect prevention, (ii) process control, and (iii) record keeping, providing adequate quality controls throughout all areas of contract performance. All documentation shall be available for Government review throughout the contract period.

3.4.2 Directed Quality Efforts. When directed by TO, the contractor shall perform supplemental quality efforts such as trend analysis and support to the Government during quality symposiums and strategic planning events (CDRL A016); and development of test plans and Test and Evaluation Master Plans (TEMPs) (CDRL A017).

3.5 Security Requirements

3.5.1 Controlled Unclassified Information (CUI). CUI is unclassified information requiring application of access, distribution controls, and protective measures which meets the standards for safeguarding and dissemination controls pursuant to statute, and government-wide policies under Executive Order (EO) 13556. The types of information considered CUI for the program are technical data and information marked Unclassified//For Official Use Only (U//FOUO) by the U.S. Government. Examples of technical data consist of research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation. The Contractor shall adhere to the below guidelines for handling U//FOUO information accompanied by DoDM 5200.01-V4, “DoD Information Security Program: Controlled Unclassified Information (CUI)”, Army Regulation (AR) 25-55, “The Department of the Army Freedom of Information Act Program”, AR 25-2, “Information Assurance” and AR 25-1, “Army Information Technology”.

3.5.1.1 Definition of U//FOUO Information. Information that has not been given a security classification pursuant to the criteria of an EO, but which may be withheld from the public for one or more of the reasons cited in Freedom of Information Act (FOIA) Exemptions 2 through 9, shall be considered as being U//FOUO.

3.5.1.2 Identification of Markings. The U//FOUO marking is assigned to information at the time of its creation in a DoD User Agency. It is not authorized as a substitute for a security classification marking but is used on official government information that may be withheld from the public as listed above. An unclassified document containing U//FOUO information shall be marked “UNCLASSIFIED//FOR OFFICIAL USE ONLY” or “U//FOUO” in bold letters at the bottom on the outside of the front cover, on each page containing U//FOUO information, and on the outside of the back cover IAW DoDM 5200.01-V4.

3.5.1.3 Dissemination and Transmission of U//FOUO Information. No person may have access to information designated as U//FOUO unless that person has been determined to have a valid need for such access in connection with the accomplishment of a lawful and authorized Government purpose. Until U//FOUO status is terminated, the U//FOUO information may be disseminated within DoD Components and between officials of DoD Components and DoD contractors to conduct official business for the Department of Defense, provided that dissemination is consistent with any further controls imposed by a distribution statement. Recipients shall be made aware of the status of such information, and transmission shall be by means that preclude unauthorized public disclosure. Transmittal documents shall call attention to the presence of U//FOUO attachments. Removal of the U//FOUO marking is only accomplished by the originator or other competent authority IAW DoDM 5200.01-V4.

3.5.1.4 Transporting U//FOUO Information. Records containing U//FOUO information shall be transported in a manner that precludes disclosure of the contents. When not commingled with classified information, U//FOUO information may be sent via first-class mail or parcel post. Bulky shipments, such as distributions of U//FOUO directives or testing materials, that otherwise qualify under postal regulations may be sent by fourth-class mail. When material marked U//FOUO is removed from storage, the Contractor shall attach DA Label 87 (For Official Use Only Cover Sheet).

3.5.1.5 Electronically Transmitted Messages. The Contractor shall not transmit U//FOUO information electronically over the Internet unless it is encrypted by Federal Information Processing Standard (FIPS) 140-2 standard. All messages shall be transmitted in accordance with (IAW) Army Regulation (AR) 25-1. Documents containing U//FOUO shall not be posted on websites available to the public.

3.5.1.6 Telephone Usage. U//FOUO information may be discussed over the telephone lines with DoD Components and between officials of DoD Components and DoD contractors to conduct official business for the Department of Defense.

3.5.1.7 Storage of U//FOUO Information During Duty Hours. Records and or data determined to be U//FOUO shall be placed in an out-of-sight location if the work area is accessible to persons who do not have a need for access to this information.

3.5.1.8 Storage of U//FOUO Information During Non-Duty Hours. At the close of business, U//FOUO records shall be stored so as to preclude unauthorized access. Filing such material with other unclassified records in unlocked files or desks is adequate when U.S. Government or government-contractor internal building security is provided during non-duty hours. When such internal security control is not exercised, locked buildings or rooms normally provide adequate after-hours protection. If such protection is not considered adequate, U//FOUO material shall be stored in locked receptacles such as file cabinets, desks, or bookcases.

3.5.1.9 Termination. The originator or other competent authority, e.g., initial denial and appellate authorities, shall terminate U//FOUO markings or status when circumstances indicate that the information no longer requires protection from public disclosure.

3.5.1.10 Disposal. Documents containing U//FOUO shall be destroyed by shredding. When a mechanical automatic shredder is not available, non-record copies of U//FOUO materials may be destroyed by tearing each copy into pieces to preclude reconstructing, and placing them in regular trash containers. CD-ROM/DVD copies of U//FOUO documents shall be destroyed by breaking the CD media into pieces or placing into a mechanical shredder that can accommodate destruction of CDs.

3.5.1.11 Unauthorized Disclosure. The Contractor shall ensure there is no unauthorized disclosures of U//FOUO information. If an unauthorized disclosure does occur, the respective DoD Component that originated the U//FOUO information shall be informed of its unauthorized disclosure. The unauthorized disclosure of U//FOUO information protected by the Privacy Act may result in criminal sanctions.

3.5.1.12 Distribution Statements. Marking of Technical Data shall be IAW the corresponding distribution statement provided in the Security Classification Guide. If the contents of the technical document require more than one distribution statement, the Contractor shall apply the most restrictive statement. This does not preclude additional mandated markings that may be contractually required. The Contractor shall contact the Program Security Manager, Project Manager-Transportation Systems (PM-TS) or G2 TACOM LCMC, AMSTA-CSS, 6501 E. 11 Mile Road, MS 105, Warren, MI 48397-5000, to request distribution statements.

3.5.2 Operations Security (OPSEC).

3.5.2.1 If the Contractor generates unclassified OPSEC sensitive information, this information will be protected at the same level as U//FOUO information. The Contractor shall develop an OPSEC program, in accordance with DoDM 5205.02-M and AR 530-1, with specific features based on command or unit approved OPSEC requirements.

3.5.2.2 Because of antiterrorism and or force protection, operations security, and counterintelligence concerns, the Contractor shall not release any diagrams, maps, floor plans, schematics, or digital pictures of Government installations and Contractor facilities to outside organizations or companies without the approval of the G2 TACOM LCMC communicated by the COR. All information proposed for public release that may consist of videos, pictures, articles, brochures, websites or other information that may be considered OPSEC sensitive shall undergo a Program Executive Office Combat Support and Combat Service Support (PEO CS&CSS) OPSEC Review using the most current and approved PEO CS&CSS STA Form 7114. The Contractor shall contact the Program Security Manager, PM-TS to obtain a copy of the aforementioned form.

3.5.2.3 Examples of information that would be considered OPSEC sensitive consist of: Equipment capabilities, limitations, and vulnerabilities; Detailed mission statements; Operation schedules; Readiness and vulnerability assessments; Test locations and dates; Inventory charts and reports; Detailed budget data; Photographs of components; Detailed organizational charts (with phones and e-mail listings); Technical and scientific data; Unclassified technical data with military applications; Critical maintenance information; Information extracted from a DOD Intranet web site; Lessons learned that could reveal sensitive military operations, exercises, or vulnerabilities; Logistics support (munitions, weapons, movement); Specific real time support to current or on-going military operations; Delivery schedules; and Manufacturing methods.

3.5.2.4 OPSEC review requests should be sent via US mail or encrypted e-mail to:

Program Security Manager, PM-TS 6501 E. 11 Mile Rd Warren, MI 48397

3.5.3 Security Classification Guide (SCG).

3.5.3.1 Unclassified information will be protected in accordance with the applicable Army Watercraft Systems Interim SCG, dated 23 February 2015, as well as the OPSEC Plan, respective DOD and Army Regulations, and additional guidance provided above.

3.5.4 Training.

3.5.4.1 All Contractor personnel performing services in the execution of this task order shall complete the following training IAW respective security clauses as referenced in this contract: iWATCH; Antiterrorism Level I; and OPSEC training. The Government reserves the right to request completion notification from the Contractor.

PART 4

ADDITIONAL CONSIDERATIONS

4.1 Monthly Status Report: The contractor shall deliver a Monthly Status Report (MSR) in accordance with CDRL A001. This report shall: 1) summarize accomplishments of the previous month; 2) discuss major issues and concerns; 3) discuss new support needs; 4) summarize the current financial billing profile, including any projected shortfalls or under-runs; and 5) detail the monthly labor charges for all direct labor, including contractor personnel, consultants, and subcontractor personnel, with cumulative totals for all charges against the task order. The report will close out the last day of the contractor’s monthly accounting period and be submitted no later than ten calendar days after close of the contractor’s monthly accounting period. (CDRL A001).

4.2 Integration of Effort: The contractor shall be solely responsible for the management of its employees, consultants, and subcontractors’ employees, and the execution and integration of all work performed.

4.2.1 Day-To-Day Supervision: The contractor shall be responsible for day-to-day supervision of contractor personnel, consultants, and subcontractors’ personnel regardless of location.

4.2.2 Chargeable Work. In order for charges to be invoiced, deliverable services must have been performed in direct support of a requirement. There may be occasions when contractor personnel are invited to participate in Government morale and recreational activities, such as holiday parties, golf outings, sports days, and other various events. The Government does not have an employer/employee relationship with contractor employees and therefore is not authorized to grant administrative leave or expend Government resources to compensate contractor employees for hours expended on activities not within scope of the task order. Under these circumstances, contractor employees must comply with individual company policy that is in accordance with that company’s compensation system. Submission of an invoice for payment of non-billable charges is not authorized and constitutes a false claim, which may lead to criminal sanctions, fines, suspension, and debarment.

4.3 Identification: Contractor personnel, consultants, and subcontractor personnel must identify themselves as contractors during meetings, telephone conversations, in electronic messages, and all other correspondence related to this task order.

4.4 Non-Disclosure Agreements: The contractor is responsible for providing executed Non-Disclosure Agreements (NDAs) (Attachment 06) for personnel supporting PD AWS under this task order to protect all proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this task order.

4.5 Off-Duty Employment: Contractor personnel, consultants, and subcontractor personnel shall neither employ nor establish a compensatory arrangement with any person who is an employee of the United States Government, either civilian or military, without verifying that the employee has complied with the Joint Ethics Regulation (DoD 5500.7-R) and any appropriate department regulation pertaining to off-duty employment for Government personnel.

4.6 Restrictions/Prohibited Activities: Contractor personnel, consultants, and subcontractor personnel are expressly prohibited from performing the following tasks in accordance with the FAR, its supplements, and other applicable laws and regulations:

-Preparing any statement of requirements, objectives, or needs for advisory and assistance services -Evaluating the qualifications of any potential source or proposal for an order or contract for advisory and assistance services -Formulating evaluation criteria, acquisition plans, solicitations, or strategies for the acquisition of advisory and assistance services -Preparing documentation for other orders or contracts for advisory and assistance services

4.7 Disclosure of Information: There shall be no disclosure or publication of information developed under this task order unless prior written approval has been obtained from the PCO. In order to comply with DFARS 252.204-7000, Disclosure of Information, copies of the information to be released are required at least forty-five days prior to the scheduled release date. The locations as to where these copies should be sent to can be found at DFARS 525.204-7000.

4.8 Government Incentives/Remedies: The Contractor shall perform in accordance with the requirements specified within this Performance Work Statement. This section is in addition to any of the rights provided by FAR clause 52.246-4, Inspection of Services, and any other rights and remedies the Government has under statute or common law.

4.8.1 Incentives: The COR performing surveillance will document high quality performance and ensure this record of performance becomes a part of the Contractor Performance Assessment Report (CPAR) for this order IAW Section H of the MA IDIQ.

4.8.2 Remedies: If the Contractor does not perform in accordance with the PWS requirements stated herein, the following may result as applicable:

(1) a CPAR rating applicable to the level of work performed;

(2) loss of contract financing;

(3) withholding of payments until the Government can determine the ramifications of the below-standard performance;

(4) withhold exercise of remaining options; and/or

(5) contractor correction at no additional cost to the Government.

4.9 Accident Reporting and Responsibilities:

4.9.1 Accident investigation and reporting to higher command levels will remain with the U.S. Army at the host installation

4.9.2 The contractor shall report within one hour of an accident to the COR all available facts relating to each instance of damage to Government property and material or injury to task order personnel.

4.9.3 The contractor shall immediately secure the accident area and wreckage until released by the accident investigation authority from the host installation. The COR will prepare the notification of release of equipment impacted by the accident or wreckage.

4.9.4 If the Government conducts an investigation of the accident, the contractor shall cooperate fully with the Government personnel until the investigation is completed.

PART 5

DELIVERABLES

PART 6

APPLICABLE PUBLICATIONS

6.1 Joint Ethics Regulation, DoD 5500.7-R

6.2 Joint Federal Travel Regulation

6.3 EIA-649-1

6.4 MIL-HDBK-502, Department of Defense for Acquisition Logistics

6.5 MIL-PRF-49506

6.6 MIL-PRF-63002L(TM)

PART 7

ATTACHMENT AND TECHNICAL EXHIBIT LISTING

7.1 Attachments:

7.2 Technical Exhibits:

A – Performance Requirements Summary

TECHNICAL EXHIBIT A

PERFORMANCE REQUIREMENT SUMMARY

The contractor services requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of services for each requirement. These thresholds are critical to mission success.

Contractor’s Monthly Status Report

(CDRL A001)

Technical Instruction Schedule

(CDRL A002)

Meeting Minutes

(CDRL A003)

Technical Reports

(CDRL A004)

Engineering Change Proposal and Notice of Revision

(CDRL A005)

Request for Variance

(CDRL A006)

Technical Data Package

(CDRL A007)

Configuration Management Plan

(CDRL A008)

Engineering Release Record

(CDRL A009)

Interface Control Document

(CDRL A010)

Configuration Status Accounting Information

(CDRL A011)

Configuration Audit Plan

(CDRL A012)

Configuration Audit Summary Report

(CDRL A013)

IPS Management Control Log

(CDRL A014)

Modification Work Order Development

(CDRL A015)

Non-Disclosure Agreements

Trend Analysis

(CDRL A016)

Test Planning

(CDRL A017)

image1.png