Draft_PWS_-_PD_AWS_STS_11_MAY_17_FBO.docx

Performance Work Statement For Systems Technical Support for Product Director, Army Watercraft Systems

Contract Number: W56HZV-16-R-0086

Department of the Army U.S. Army TACOM Life Cycle Management Command (LCMC) Army Contracting Command – Warren (ACC-WRN) Product Directorate Army Watercraft Systems (PdD AWS)

Section A: Solicitation / Contract Form 6

A.3.0 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEMS CODE……………………………………………….….6

A.4.0 EVAULATION OF PROPOSALS 6

Section C: Description / Specification / Statement of Work 10

Section E: Inspection and Acceptance 34

Section F: Deliveries or Performance 36

Section H: Special Contract Requirements 37

Section J: List of Attachments 52

Exhibit A: CONTRACT DATA REQUIREMENT LIST (CDRL) 40

ATTACHMENT 0001: CONFIGURATION MANAGMENT………………………………………………………………………..…48

ATTACHMENT 0002: TDP REQUIREMENTS………………………………………………………………………………………….…48

ATTACHMENT 0003: LABOR RATES BY ORDERING PERIOD ………………………………………………………..……….…48

ATTACHMENT 0004: FAILURE MODES EFFECTS AND CRITICALITY ANALYSIS……………………………………….…48

ATTACHMENT 0005: NON-DISCLOSURE AGREEMENT (NDA) ………………………………………………………………...48

ATTACHMENT 0006: DD Form 254 …………………………………………………………………………………………………….….48

Section A: Solicitation / Contract Form

A.1.0 BACKGROUND / DESCRIPTION OF ACTION.

A.1.1 Executive Overview & Objectives.

The Product Directorate (PdD) of Army Watercraft Systems (AWS) requires non-personal services to the current fleet of vessels consisting of Systems Technical Support (STS) within the Continental United States (CONUS) and Outside the Continental United States (OCONUS). The PdD AWS Performance Work Statement (PWS) requires the contractor to provide services on technical and programmatic issues. The contractor shall provide qualified personnel, equipment, supplies, facilities, transportation, tools, materials, and supervision necessary to perform the services as defined in this PWS, except for those items specified as Government-Furnished Property (GFP) and services.

A.1.2 Program Office Background.

PdD AWS serves as the Life Cycle Manager for AWS, primarily categorized as follows:

· Landing Craft: Logistics Support Vessel (LSV), Landing Craft Utility (LCU-2000), Landing Craft Mechanized (LCM-8) Mod I

· Ship-to-shore enablers: Modular Causeway System (MCS)

· Towing and terminal operations: Large Tug (LT-800), Small Tug (ST-900), and Barge Derrick (BD-115T)

· Watercraft operations support: LCM-8 Mod II

These systems and sub-systems require continued support including design and application of modifications to address deficiencies, address obsolescence issues, and improve capability; development and correction of technical data; and configuration management.

A.2.0 ACQUISITION APPROACH / STRUCTURE.

The U.S. Army Contracting Command – Warren (ACC-WRN) intends to award a Cost-Plus-Fixed-Fee (CPFF), Single Award, Indefinite Delivery Indefinite Quantity (IDIQ) contract. The contract performance period for the proposed IDIQ contract will consist of five ordering periods.

This contract will provide for the execution of Task Orders for the requirements within the general scope of the PWS. The hours awarded for each Task Order will be CPFF Term (Level of Effort (LOE)) or Completion based on individual requirements. Material and travel will be on a Cost, No Fee (CNF) basis only.

In accordance with (IAW) Federal Acquisition Regulation (FAR) 16.504(a)(4)(ii), the maximum quantity of services the Government will order against this contract is $10,000.

A.2.1 Contract Performance beyond Ordering Period Expiration.

Under this effort, there are five defined 12-month ordering periods. In the event that a Task Order is issued in the fifth Ordering Period, the Period of Performance (PoP) for that effort may continue beyond the expiration of the fifth Ordering Period. The PoP of the Task Orders may not continue more than 12 months from the expiration date of the fifth Ordering Period.

A.3.0 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEMS (NAICS) CODE.

The Government will use NAICS code 541330, Engineering Services, for this Request for Proposal (RFP) and the resulting contract as it encompasses the preponderance of the work expected under the contract.

A.4.0 EVALUATION OF PROPOSALS.

A.4.1 Section L of this RFP provides information and instructions for proposal preparation.

A.4.2 Section M of this RFP describes how the Government will evaluate proposals for award.

A.4.3 The Government will evaluate all offerors responding to the RFP using the criteria stated in Sections L and M.

Section B: Products or Services and Prices/Costs

B.1.0 LABOR RATES BY ORDERING PERIOD.

The rates identified by the contractor in Attachment 0003, represent the 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 awarded by modification on final day of the first Ordering Period, with performance primarily in the second Ordering Period, the first Ordering Period rates will apply).

B.1.1 Other Direct Costs (ODCs).

All anticipated ODCs associated with performance shall have an established price at time of Task Order award. The Contracting Officer will review and approve all proposed ODCs in excess of $10,000 prior to award.

B.1.2 Contract Pricing.

The contractor shall propose its proposed labor mix multiplied against the proposed labor rate(s) for the proposed categories and applicable ordering period. The contractor shall also provide its estimated travel costs IAW with the Joint Travel Regulations (JTR) and any incidental material costs applicable to the effort as CNF. 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 CPFF Task Order.

B.1.3 Job Categories Labor Categories (Attachment 0003) are definitions for the type of personnel required to perform the services covered in the PWS and resulting Task Orders. The Government reserves the right to add additional classifications for similar type work based on Army requirements.

B.2.0 ESTIMATED COST AND PAYMENT.

The Government will define each Task Order funded Contract Line Item Number (CLIN) as a Term (LOE) or a Completion effort. All terms in this Section B apply to both Term (LOE) CLINs and Completion CLINs.

B.2.1 Limitation of Cost.

FAR Clause 52.232-20, Limitation of Cost, applies to each CLIN separately.

B.2.1.1 The contractor shall provide the notification required by FAR Clause 52.232-20, whenever there is a reason to believe that the funds allotted to each CLIN are either insufficient or excessive for the performance of the work required.

B.2.1.2 Allowable cost shall be determined, and payment thereof shall be IAW FAR Clause 52.216-7, Allowable Cost and Payment. The Government does not authorize the contractor to perform work outside the period of performance of the CLIN established in each Task Order. Any work performed outside of the period of performance of the CLIN is at the contractors risk and the Government has no obligation to reimburse cost.

B.2.2 Fixed Fee.

The fixed fee together with the reimbursement of cost shall constitute full and complete consideration for the contractor services in connection with the work required and performed under this contract. The Government will pay the contractor the total fixed fee for the performance of work IAW FAR Clause 52.216-8, Fixed Fee as set forth in Section B.2.2.1 and B.2.2.2 below.

B.2.2.1 Term (LOE) CLIN(s) / Task Order(s).

The fixed fee ties directly to the LOE hour(s) expended. The fixed fee is payable based on satisfactory performance of the specified level of effort. For each request for payment, the contractor shall invoice fee as follows: Invoice Fee = Total CLIN Fixed Fee amount times the hours performed for the invoice period divided by total CLIN hours, subject to any applicable withholdings.

B.2.2.1.1 Pursuant to FAR Clause 52.232-20 (Limitation of Cost) and FAR 16.306(d) (Cost-Plus-Fixed-Fee Contracts), in the event the contractor cannot perform LOE hour(s) within the estimated cost set forth in the CLIN, the Government may increase the estimated cost of the hour(s) but will not increase the fixed fee for the hours.

B.2.2.2 Completion CLIN(s) / Task Order(s).

For each request for payment, the contractor shall invoice fee as follows: Invoice Fee = Total CLIN fixed fee amount times the costs for the invoice period divided by total CLIN estimated cost, subject to any applicable withholdings.

B.2.2.2.1 The fixed fee is based upon satisfactory completion of the scope within the period of performance. Pursuant to FAR Clause 52.232-20 (Limitation of Cost) and FAR 16.306(d) (Cost-Plus-Fixed-Fee Contracts), in the event the contractor cannot complete the scope within the estimated cost, the Government may require more effort without increase in fixed fee, provided the Government increases the estimated cost.

Section C: Description / Specification / Statement of Work

C.1.0 GENERAL INFORMATION.

This PWS applies to services required to deliver engineering and safety analysis, design support, technical support, configuration management, maintenance engineering, quality assurance, integrated logistics support, test asset installation, program management, new equipment training, milestone documentation, obsolescence management, business case analysis, and related support efforts for AWS. Requirements include analysis of failures in fielded vessels, research, engineering analyses, design, and installation of test assets for vessel performance issues, all with limited to no data. Specialized watercraft design support and naval architecture experience are required to execute this contract.

C.1.1 Specialized Watercraft Information.

The contractor shall comply with all applicable regulations and standards: including Department of Defense (DoD) regulations, Army Regulations (AR), United States Coast Guard (USCG) standards, Environmental Protection Agency (EPA) regulations, Safety of Life At Sea (SOLAS) requirements, Code of Federal Regulations (CFR) Title 46, American Bureau of Shipping (ABS) Rules, International Maritime Organization (IMO) requirements, and discharge standards.

C. 1.2 Task Orders.

All work under this contract shall be completed IAW the individual Task Orders issued by the Contracting Officer. The Contracting Officer will incorporate Task Orders into the contract by a bi-lateral modification. No work shall commence until the contractor has received a fully executed Task Order. Each Task Order will indicate if it is a Term (also referred to as LOE) or Completion, and will include the following information at a minimum:

(a) Task Order number and title

(b) Representative of task(s) in Section C

(c) Objective of the Task Order

(d) Identification of CPFF LOE or Completion Effort

(e) Number of hours authorized

(f) Detailed description of work to that the contractor shall perform

(g) Completion date(s)/ PoP

(h) Identification of applicable contract number, contractor's name and address

(i) Identification of deliverables as required by the Task Order (CDRL)

(j) Security Requirements

(k) Listing of Government-Furnished Material (GFM)/Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)/Government-Furnished Support (GFS)/GFP

(l) Contracting Officer’s signature

C.1.2.1 Term (LOE) Task Orders describe the work in general terms and obligate the contractor to devote a specified LOE for a stated time period. At its discretion, the Government may award additional hours to continue the effort. The Government will award term efforts as CPFF with the exception of Cost, No Fee (CNF) for material and travel.

C.1.2.2 Completion Task Orders describe work that states a definite goal or target and specified end product. Completion scope requires the contractor to complete and deliver the specified end product regardless of the number of hours awarded and/or performed. The Government will award Completion efforts as CPFF with the exception of CNF for material and travel.

C.1.3 Task Scope.

The Government will incorporate Task Orders that fall within the general PWS.

C.1.4 Schedule.

The contractor shall create and maintain a key events Integrated Master Plan (IMP) in addition to an Integrated Master Schedule (IMS) IAW CDRL A002 (Integrated Program Management Report (IPMR)) for each Task Order, to include development of an IMP and an IMS for various PdD AWS programs. The contractor shall use Microsoft Project to create and maintain the IMS and IMP. The IPMR shall include the applicable title and Task Order number. Schedules shall specify all necessary tasks to complete the work prescribed by the Task Order. Schedules shall differentiate between duration and milestone tasks. Schedules shall include a timeframe for each task including a start, finish, duration, and percent complete for any task in process. The IMS shall identify the critical path through completion of each Task Order. In addition, the schedule shall state responsible parties for each task as a resource-loaded schedule. The contractor shall update and publish each schedule IAW CDRL A002 (Integrated Program Management Report).

C.1.4.1 Schedule delays.

The contractor shall notify, within two (2) business days, the Contracting Officer's Representative (COR) and the Contracting Officer by email of any schedule slip. Within ten (10) business days of the email, the contractor shall detail the reasons for the schedule slip, proposed corrective action(s), and submit a revised schedule to the COR and Contracting Officer. The Government reserves the right to review and approve or disapprove any contractor proposed changes that affect contract and Task Order schedules. The contractor shall submit any necessary request for PoP extensions in advance of the completion date established in the Task Order. There will be no additional cost to the Government for PoP extensions for contractor delay(s).

C.1.5 Access to Data.

On request by the Contracting Officer or designated COR, the contractor shall provide access to records and data generated in the course of performing an individual Task Order. The Government shall have access, retention, and unlimited rights to all data (e.g. hard copy and computer files generated under the applicable Task Order and all underlying data and files).

C.1.6 Government Systems

The contractor shall use Government Systems to facilitate unclassified, secure internet-based information sharing between STS program participants. SharePoint will also serve as the primary means of submitting unclassified FOUO Contract Data Requirements List (CDRL) items, unless otherwise stated within a specific CDRL item. The contractor shall notify appropriate Government personnel, as specified on the applicable CDRL, via e-mail when it posts new or updated documents to a collaboration environment. The notification email shall include a hyperlink to the location of the posted content. The Government will provide details on specific Government Systems, requirements for access, and approach for use at the contract SOWM.

C.1.6.1 Government Sponsored Accounts

The Government will sponsor Army Knowledge Online (AKO), SharePoint, and any other required accounts. Personally Identifiable Information (PII) cannot be stored on SharePoint. The Government will provide these details at the SOWM. The Government can only sponsor accounts for U.S. Citizens. The contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these accounts no later than the SOWM. The contractor shall update this information throughout the life of the contract. All contractor and sub-contractor employees requiring access to these accounts must successfully complete the Department of Defense (DoD) Information Assurance (IA) awareness training; this must be accomplished before approval will be given to access these accounts. The DoD IA awareness training will be an annual requirement, thereafter. The Army Training Certification Tracking System (ATCTS), and required training, is located here: https://atc.us.army.mil/iastar/index.php.

C.1.6.2 Access to Government Systems

To access Government Systems, the contractor shall have or obtain an External Certification Authority (ECA) Certificate, or a DoD Common Access Card (CAC), for the appropriate personnel. Details on the ECA program and authorized ECA vendors can be found at: http://iase.disa.mil/pki/eca/. Request for access to any other Government systems shall go through the PCO. The contractor shall designate an IA Officer to work with PdD AWS and the Government IA Manager in order to obtain and implement usage of the CAC program in compliance with DoD Directive 8190.3 Smart Card Technology, and DoD 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) enabling.

C.1.7 Common Access Card (CAC) Automated Contractor Verification System

C.1.7.1 Common Access Card (CAC) Applications

The contractor shall appoint an Information Assurance Officer to process CAC applications for its employees and Subcontractor employees IAW Federal Acquisition Regulation (FAR) 52.204-9, Personal Identity Verification of contractor Personnel, DoD Directive 8190.3 Smart Card Technology and DoD Instruction 8520.2 PKI and PK Encryption.

C.1.7.2 Requests for Common Access Card (CAC)

The contractor shall submit requests for CACs via email to the COR.

C.1.7.3 Contractor Verification System (CVS)

The Government will establish a CVS application account for each CAC request and provide each contractor and subcontractor employee a User Identification (ID) and password via email.

C.1.7.4 Common Access Card (CAC) Access

The contractors and subcontractors employees shall access the CVS account and complete the CAC application within 7 days of notification of ID and password.

C.1.7.5 Common Access Card (CAC) Request Status

The Government will inform the contractors and subcontractors employee via email of the status of the CAC request. The status will be one of the following: (1) Approved; contractor shall proceed to nearest Real-Time Automated Personnel Identification System (RAPID) Defense Enrollment and Eligibility Reporting System (DEERS) location to obtain CAC. (2) Returned; additional information or correction to application required by contractor employee. (3) Rejected; Government in separate correspondence will provide reason(s) for rejection.

C.1.7.6 Common Access Card (CAC) Approved and Rejected Applications

The contractor shall maintain records of all approved and rejected CAC applications.

C.1.7.7 Common Access Card (CAC) Period of Performance

Issued CACs may be for a period of performance no longer than two years or the contract performance completion date (inclusive of all options), whichever is earlier. If a requirement for a CAC exists beyond two years, the contractor shall submit a new request.

C.1.7.8 Common Access Card (CAC) Return

The contractor shall return issued CACs to the DEERS office IAW FAR 52.204-9. The contactor shall notify the Government of all CACs returned to the DEERS Office.

C.2.0 MEETINGS.

C.2.1 Post Award Start of Work Meeting.

The contractor shall host a contract post award Start of Work Meeting (SOWM) at its facility, unless the parties agree to some other location, no later than 30 calendar days after contract award. The contractor shall at a minimum invite its leadership, PdD AWS representatives, the COR and the Contracting Officer. The contractor shall coordinate a mutually acceptable meeting date with the COR. The contractor shall prepare and submit a proposed agenda for the SOWM at least three business days before the scheduled meeting date, to include an outline of how it will accomplish all awarded tasks.

C.2.2 Task Order Kickoff Meeting.

The contractor shall host a Kickoff Meeting for each Task Order. The Kickoff Meeting shall include the contractor personnel assigned to the tasks prescribed by the Task Order and PdD AWS personnel overseeing the Task Order. The contractor shall hold Kickoff Meetings by phone within 15 days of award of a Task Order unless otherwise agreed to by PdD AWS. With the Government’s approval, the contractor may hold Kickoff Meetings in conjunction with other regularly scheduled PdD AWS meetings.

C.2.3 Meeting Minutes.

Following the SOWM and each Kickoff Meeting, the contractor shall provide meeting minutes within two business days IAW CDRL A003 (Record of Meeting Minutes).

C.2.4 Integrated Product Team (IPT) Meetings.

When directed by Task Order, the contractor shall participate in all planning/implementation meetings (consisting of IPT and working group meetings). The contractor shall host design review meetings as required by the Task Order.

C.2.5 Program Management Reviews (PMR).

The contractor shall schedule and conduct joint contractor and Government quarterly PMRs that include participation from senior-level program management, senior-level technical management and Subject Matter Experts (SME). PMRs shall focus on the full range of programmatic topics to include cost, schedule, performance, and risk. The contractor shall present program status at the PMRs based on its IMP, IMS, metrics, accomplishments, and risk management efforts. Risk management efforts shall follow the guidelines of the Risk Management Guide for DoD Acquisition (Sixth Edition, Version 1.0). The contractor shall provide status of all CDRL efforts. The contractor shall hold all PMRs either by telephone or at the contractor’s facility. The Government estimates that each PMR will not to exceed one business day. Following the PMR, the contractor shall submit meeting minutes IAW CDRL A003 (Record of Meeting Minutes).

C.3.0 ENGINEERING REQUIREMENTS.

The Government will assign services for the contractor to perform under this contract, by Task Order, and may include tasks from one or more sections of this PWS.

C.3.1 Analysis and Technical Investigation.

When required by Task Order, the contractor shall conduct a technical investigation. Technical investigations shall consist of one or more of the following:

i. analysis of failed components,

ii. investigation of field incidents,

iii. preparation of engineering calculations,

iv. fabrication of test asset hardware for trial installation and/or testing,

v. structural analysis (e.g., stress analysis, finite element analysis, dynamic modeling.) on parts, components, and assemblies,

vi. system/design trade-off studies,

vii. observations of Government and/or third party tests,

viii. attendance at technical meetings,

ix. field review of modified and/or failed parts or systems,

x. failure analysis,

xi. technology surveys,

xii. Manufacturing Readiness Level (MRL) analysis,

xiii. architecture evaluations,

xiv. cost modeling,

xv. engineering design review for life cycle cost reductions,

xvi. system requirement analysis,

xvii. development of Systems Engineering Plans (SEP), and/or

xviii. general technical assistance on engineering matters.

In the Task Order, the Government will either assign specific tasks for the contractor to perform in the course of a technical investigation or identify the required end product(s) or deliverable(s). The contractor shall identify and conduct any specific tasks necessary to complete and deliver the required end product(s) or deliverable(s). The contractor shall submit a technical report IAW C.3.3 and CDRL A004 (Technical Report) to document the results of a technical investigation, including identification of the purpose, methodology, results, and any other information required by the Task Order.

C.3.1.1 Regulatory Compliance.

As part of each technical investigation, the contractor shall evaluate the compliance of systems identified in applicable Task Orders with laws and regulations identified by the CFR, International Convention on SOLAS, ABS, IMO, and any other applicable regulations identified in the Task Order. The contractor shall identify compliance or non-compliance of investigated in the technical report IAW CDRL A004 (Technical Report).

C.3.2 Engineering Change Development and AWS Engineering Process.

When required by Task Order, the contractor shall develop engineering changes to be applied to PdD AWS vessels or related assets (e.g., other vessel equipment that is issued with the vessel but not permanently attached, such as a rescue boat). For all projects resulting in a change to the configuration of a PdD AWS vessel or related asset, 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 as defined in the subsequent paragraphs. Preliminary and Critical Design Reviews (C.3.2.1 and C.3.2.2) shall be completed for all engineering changes unless otherwise directed by Task Order. The rest of the process (C.3.2.3 thru C.3.2.6), when required, will be specified in the applicable Task Order.

C.3.2.1 Initial Design Work and Preliminary Design Review (PDR).

Following the Kickoff Meeting, the contractor shall develop design concept(s) to meet the requirements of the Task Order and shall present the concept(s) to the Government at PDR. The contractor shall present at least two potential design solutions at the PDR, with a recommendation of which design solution to select, unless otherwise directed by the Task Order. 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 the PDR, the contractor shall submit meeting minutes within two business days IAW CDRL A003 (Record of Meeting Minutes) and Paragraph C.2.3.

C.3.2.2 Detail Design Work and Critical Design Review (CDR).

Following approval of a design solution at the PDR, the contractor shall complete detailed design work on the selected design(s) and hold a CDR, IAW with the TO IMS, 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 within two business days IAW CDRL A003 (Record of Meeting Minutes) and Paragraph C.2.3.

C.3.2.3 Preliminary Engineering Change Proposal (PECP) and Configuration Control Board (CCB) Review.

When required by the Task Order, the contractor shall prepare a PECP and present it at the PdD AWS CCB. The contractor shall prepare and submit a PECP reflecting the outcome of the PDR. PECPs shall be prepared IAW CDRL A005, except submission of NOR and Technical Data Packages (TDPs) are not required with PECPs. PECPs do not satisfy the requirement for a formal ECP.

C.3.2.4 Test Asset(s) and Proof.

When required by the Task Order, following approval of the design at the CDR, the contractor shall build at least one test asset of the selected design, and install on the vessel(s). The test asset shall demonstrate functionality, validate the technical data package IAW Section C.4.3, and validate the modification instructions. Upon completion of the test asset installation and functionality demonstration, the contractor shall hold a Test Asset Review (TAR). At the TAR, the contractor shall present status to the Government, identify any needed configuration changes, present an updated TDP, and obtain approval for a second test asset installation, if required. The second test asset, if required, will serve as a “proof” incorporating any necessary changes identified during installation or use of the first test asset, and will serve as verification of the TDP and modification instructions. Any deviations from the TDP during the second test asset installation, or any subsequent test asset installation (if required), must be approved in advance by the COR with coordination of PdD AWS Engineering, IAW with C.4.10 and CDRL A006 (Request for Variance).

C.3.2.5 Production Readiness Review (PRR).

When required by the Task Order, the contractor shall hold a PRR to present status and outcomes of the test asset installation(s) 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 (Record of Meeting Minutes). Following successful completion of the PRR, the contractor shall prepare and submit an ECP IAW with C.4.10 and CDRL A005. The contractor shall furnish all drawings and models of the new design to the Government IAW with CDRL A007 (Technical Data Package) and Attachment 0002 (TDP Requirements).

C.3.3 Technical Report.

When required by Task Order, the contractor shall submit a technical report IAW CDRL A004 (Technical Report). Technical reports shall include the objective, background, technical problem, methodology, evaluation, analysis, assumptions, trade-offs studied, impacts to the vessel system, subsystems, vessel readiness, results of investigation, evaluation, findings and conclusions, recommendations, supporting rationale, documentation, risk assessment, and any other information required by the Task Order or deemed pertinent by the contractor. Documentation shall include cost estimates, calculations, sketches, schematics, and other visual depictions.

C.3.4 Temporary Modifications.

When required by Task Order, the contractor shall conduct trial installations and tests of items (e.g., modified or replaced systems, subsystems, or parts), and test or evaluate the functionality of the item under consideration. The contractor shall supply all tools and parts required for evaluation and shall restore the vessel to the original configuration at the conclusion of the test, unless otherwise specified in the Task Order.

C.3.5 Testing and Test Support.

When required by the Task Order, the contractor shall perform testing or provide support to the testing of existing, modified, or new vessel systems, subsystems, and components.

C.3.5.1 Testing.

When required by the Task Order, the contractor shall develop detailed test plans IAW CDRL A017 (Test Planning). Tests plan shall include the requirements tested, test procedures and processes, data collected during testing, method of data collection, and the required facilities and resources to execute the test plan. The contractor shall develop and maintain a test schedule as part of the project IMS IAW CDRL A002 (Integrated Program Management Report). The contractor shall provide all necessary testing support, including trained crew, maintenance personnel, and data collectors. If contractor conducts testing at a facility not owned or operated by the contractor, the contractor shall be fully responsible for coordination with the outside facilities. Throughout testing, the contractor shall provide test progress reports at a frequency determined by the Government IAW CDRL A002 (Integrated Program Management Report). At the completion or testing, the contractor shall develop a detailed Final Test Report IAW CDRL A034 (Test/Inspection Report).

C.3.5.1.1 Government Witness of Contractor Testing

The Government reserves the right to witness any or all testing conducted IAW C.3.5.1. The contractor shall ensure that Government personnel can witness the testing, whether conducted at their facility or another facility arranged by the contactor. The contractor shall be responsible for coordinating all requirements at the test facilities to ensure Government personnel have access to witness the testing. The contractor shall notify the Government of contractor testing dates and schedules no less than 15 calendar days for testing conducted at a CONUS location and no less than 45 days for testing conducted at an OCCONUS location. If the contractor fails to provide notification within the required timeframes, the contractor shall be responsible for repeating the test at no additional cost to the Government.

C.3.5.2 Test Support.

When required by Task Order, the contractor shall provide support to testing conducted by the Government or other directed testing entity both CONUS and OCONUS. The contractor shall provide test support personnel, to include Field Service Representatives (FSRs) and Technical Experts to provide technical, logistics and maintenance support for the vessels, subsystems, and components. The contractor shall provide logistics and maintenance support that includes, but is not limited to, special tools, diagnostic equipment, spare and repair parts, maintenance and parts documentation.

C.3.5.3 Test Deficiencies and Test Incident Reports.

When required by Task Order, the contractor shall be responsible to diagnose and respond to deficiencies and Test Incident Reports. In response to a test deficiencies and test incident reports, the contractor shall conduct an investigation, root cause analysis, and provide recommended corrective action(s). Upon Government approval, the contractor shall implement and verify all corrective and preventative actions. Corrective actions shall consist of interim corrective actions and that can implemented immediately to continue testing and final corrective and preventative actions that are part of the final design configuration. The contactor shall document all investigation, root cause analysis, and corrective and preventative actions and provide a final report to the Government IAW CDRL A035 (Failure Analysis and Corrective Action Report).

C.4.0 CONFIGURATION MANAGEMENT.

The contractor shall have a Configuration Management (CM) program implemented at contract award and shall comply with the requirements in Electronics Industry Alliance (EIA)-649-1, this contract, corresponding CDRLS, CM Attachment 0001 and applicable Task Orders.

C.4.1 Engineering Change Proposals (ECP).

When required by the Task Order, the contractor shall submit ECPs IAW CDRL A005.

C.4.2 Engineering Release Record (ERR).

When required by the Task Order, the contractor shall submit ERRs IAW CDRL A009 (Engineering Release Record).

C.4.3 Technical Data Package (TDP).

When required by the Task Order, the contractor shall deliver TDPs per requirements IAW the applicable Task Order, CDRL A007 (Technical Data Package), and Attachment 0002 (TDP Requirements).

C.4.4 Configuration Management Plan (CMP).

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

C.4.5 Configuration Identification (CI).

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

C.4.6 Interface Control Document (ICD).

When required by the Task Order, the contractor shall submit ICDs IAW CDRL A010 (Interface Control Document).

C.4.7 Configuration Control.

The contractor shall conduct Configuration Change Management (CCM) IAW Principles CCM-1 through CCM-9 of EIA-649-1.

C.4.8 Notices of Revision (NOR).

When required by the Task Order, the contractor shall submit NORs IAW CDRL A036.

C.4.9 Request for Variances (RFV).

When required by the Task Order, the contractor shall submit RFVs IAW CDRL A006 (Request for Variance).

C.4.10 Configuration Status Accounting (CSA).

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

C.4.11 Configuration Verification and Audit (CVA).

The contractor shall conduct CVA IAW Principles CVA-1 through CVA-3 of EIA-649-1.

C.4.12 Configuration Audit Plan (CAP).

When required by the Task Order, the contractor shall submit a CAP IAW CDRL A012 (Configuration Audit Plan).

C.4.13 Configuration Audit Summary Report (CASR).

When required by the Task Order, the contractor shall submit a CASR IAW CDRL A013 (Configuration Audit Summary Report).

C.4.14 Product Data Management (PDM) Link.

The contractor shall obtain access to Advance Center for Engineering (ACE)/Windchill for input of drawings, TDPs, ECPs, Notices of Revision (NORs), and RFVs unless otherwise instructed by Task Order. The ACE/Windchill access forms are available at the following website: https://ace2.tacom.army.mil/newuser/

C.5.0 INTEGRATED PRODUCT SUPPORT (IPS) LOGISTICS.

C.5.1 IPS Program.

When a Task Order requires an ECP, the IPS package shall include all logistics data specified below; which supports all generated ECPs. All IPS/Logistics Product Data (LPD) shall be prepared and delivered IAW designated CDRLs and guidance provided in AR 700-127, Society of Automotive Engineers (SAE) GEIA-STD-0007, SAE GEIA-HDBK-0007, MIL-HDBK-502, DoD Handbook for Acquisition Logistics, and MIL-PRF-49506. The contractor shall provide IPS management support that consists of:

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

b) Vessel System Technical Publications Development (Technical Manuals (TMs), MWOs, etc.)

c) LPD

The contractor shall designate LPD focal points to coordinate design interface activities with the engineering organization, during the design phase, supporting LPD tasks and subtasks that are required to develop and produce the required logistics products.

The contractor shall designate an IPS Manager to ensure achievement of program objectives within program cost and schedule. Additionally, the IPS Manager shall have the authority to manage, direct, and control the execution of all Product Support Elements (PSE) under contract. The contractor’s 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 development of logistics products IAW the IMS.

C.5.2 Data Validation.

The contractor shall validate all IPS data deliverables prior to submittal to the Government.

C.5.3 Dedicated Hardware.

The contractor shall ensure sufficient quantities of dedicated hardware and support items to accomplish all IPS development, reviews, validations, verifications, and logistics demonstrations (LDs) are available to support each event.

C.5.4 Existing Government Tools and Test, Measurement, Diagnostic Equipment (TMDE).

The contractor shall utilize existing Government tools and TMDE. The contractor shall notify the Government upon identification of any new special tools and TMDE. Introduction of new special tools and TMDE will require Government approval. Contractor recommendations for introducing new special tools and TMDE into the Government's maintenance and supply system shall require supporting justification identified by the contractor's supportability analysis. The Government will notify the contractor of the approval determination. If approved, the contractor shall proceed with development of related support requirements. If disapproved, the contractor shall provide alternative support methods using existing Government authorized tools and TMDE, at no additional cost to the Government.

C.5.5 IPS Management Control Log.

The contractor shall maintain an IPS Management Control Log IAW CDRL A014 (IPS Management Control Log), with supporting documentation for Government review, as required, that tracks all changes to the production configuration baseline and subsequent IPS/Logistics Management Information (LMI) impact, to consist of 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) Part Number (P/N), Commercial and Government Entity (CAGE) Code, and National Stock Number (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 C.5.6 Product Support Analysis (PSA) and Logistics Product Data (LPD) Objectives.

PSA provides a foundation for the IPS program by analyzing the system design and documenting source data to support the development and the delivery of the vessel's system product support packages; such as maintenance task lists, training support, technical publications, and initial provisioning package. Army policy requires the use of policy requiring use of the Logistics Product Data Store (LPDS). PowerLOG-J shall serve as the AWS IPS programs’ LPDS and be used to develop, evaluate, review, and integrate logistics data for materiel systems. LPD comprises the IPS records and related engineering and logistics data acquired or generated as a result of PSA conducted during any task under this contract. LPD enables the planning and execution of maintenance support strategies, including the identification of resources such as personnel, support equipment, facilities and transportation requirements, and initial provisioning package, cataloging, and item management. It also supports the management and tracking of design changes to the product baseline. The contractor shall follow good data management principals to ensure the proper identification, definition, preparation, control, archiving, and disposition of data required to execute this contract. GEIA-859, Data Management shall be used as guide.

C.5.6.1 Product Support Analysis (PSA) and Logistics Product Data (LPD) Tasks.

When required by Task Order, the contractor shall:

a) Perform a PSA to enable the development of LPD to support Operations and Maintenance planning and the deployment of AWS and Support Equipment.

b) Utilize the most current version of the PowerLOG-J database application to maintain and update LPD.

c) Make available to the Government LPD exported from the PowerLOG-J database.

d) Ensure LPD is available to develop, validate and deliver logistics support packages for AWS at the time of its scheduled use for testing, training, demonstrations, evaluations or fielding.

e) Analyze the data resulting from testing, manufacturing processes, quality assurance, LD, and any other evaluations of AWS.

f) Update LPD within the PowerLOG-J database to ensure LPD accurately reflects the results and findings of these activities IAW CDRL A018 (Logistics Product Data) C.5.7 Level of Repair Analysis (LORA).

When required by Task Order, the contractor shall develop a LORA using the latest version of the Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS). The contractor shall continue to conduct a LORA employing industry best practices and include all system-level repairs, all subsystem, assembly, subassembly level candidates, and kits for analysis. The contractor shall incorporate the Service Components maintenance philosophies, capabilities, and respective Military Occupational Specialty (MOS) skill set(s). All associated LORA LPD shall be input, maintained and updated in the PowerLOG-J application. The LORA Report shall include all COMPASS input and output data files to include COMPASS ACCESS database tables used in the assessment IAWCDRL A019(Level of Repair Analysis Report) C.5.8 Maintenance Management.

The contractor shall provide engineering and provisioning services to AWS in maintaining and upgrading existing AWS systems. The contractor shall be involved with detecting problems, isolating failures, providing courses of action, and implementing approved corrective procedures. The contractor shall perform technology upgrades into existing systems. This task shall include modifying and debugging hardware and software required to maintain operation of AWS systems.

The contractor maintenance concept shall include a description of the maintenance considerations, constraints, and plans for operational support of the AWS current system/equipment and those under development. This includes anticipated levels of repair, maintenance task analysis, general overall repair policies, organizational responsibilities for maintenance, anticipated availability of resources, use of contractor resources both CONUS and OCONUS, and ensure compliance with all applicable statutory and regulatory maintenance guidance.

C.5.8.1 Maintenance Task Analysis (MTA).

When required by Task Order, the contractor shall perform MTA on all AWS tasks IAW TA-STD-0017 Activity 12. MTA shall encompass all operator, maintainer, and support personnel tasks as identified by LORA, Reliability Centered Maintenance (RCM) Analysis, Failure Modes Effects and Critically Analysis (FMECA), Mission Task Analysis, and other similar analyses. The contractor shall update the MTA to reflect changes to the product baseline and the results and outcomes from testing, training, quality, manufacturing, Log Demo, and other AWS evaluations conducted throughout the contract. In performance of the MTA, the contractor shall provide the following LPD:

a) All LPD identified in TA-STD-0017 Activity 12 except activities 12.5 and 12.6.

b) Sequential narrative instructions and procedures for all tasks below depot level maintenance including maintenance source data for TMs and IETMs, shall be input into PowerLOG-J after TM and IETM validation and shall be updated in PowerLOG-J after successful TM and IETM verification and Government acceptance.

c) Support requirements for performing each task. These requirements shall include Military Occupational Specialty (MOS), skill levels, tools, support equipment, Automatic Test Equipment (ATE), Test Program Sets (TPS), and repair parts.

C.5.8.2 Reliability Centered Maintenance (RCM) Program.

The contractor's RCM Program shall…