Draft_PWS_-_PD_AWS_STS.docx

Performance Work Statement (PWS) 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 Product Director, Army Watercraft Systems

C.1.0 INTRODUCTION

C. 1.1 Executive Overview & Objectives.

This non-personal service Performance Work Statement (PWS) establishes the requirements for contractor-provided services to the Product Director (PdD), Army Watercraft Systems (AWS). The scope of this PWS consists of Systems Technical Support (STS) to vessels under PdD AWS. The contractor shall advise PdD AWS on technical and programmatic issues. Contractor is required to provide qualified personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, 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 C.3 below to accomplish the services described in this PWS.

C.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 require continued support including design and application of modifications to address deficiencies, obsolescence issues and improving capabilities, development and correction of technical data, and configuration management.

C.2.0 GENERAL INFORMATION

C. 2.1 General Task Information.

This PWS applies to services required to deliver engineering and safety analysis, design support, technical support, configuration management, maintenance engineering (e.g., maintenance task analysis, maintenance procedure development, failure mode-effects and criticality analysis, level of repair analysis, maintenance allocation charts, two-level maintenance), quality assurance, integrated logistics support (e.g., technical publications, provisioning, supply support), maintenance and alterations installation, program management, new equipment training, milestone documentation, obsolescence management, performance based logistics, business case analysis, 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 support and naval architecture experience are required to execute this contract.

C.2.1.1 Specialized Watercraft Information.

The contractor shall be familiar with and experienced in complying with applicable regulations and standards such as: Department of Defense (DoD), 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) (e.g., ABS-SVR and ABS-HSC Naval Rules) requirements, International Maritime Organization (IMO) requirements, discharge standards, general naval architecture practices, maintenance and marine engineering, and technical drawing standards.

C.2.2 Ordering / Technical Instructions / Performance Requirements.

Under this effort, all work shall be performed in accordance with (IAW) individually performance-based Technical Instructions (TI) issued by the Contracting Officer (CO). The CO will add TIs to the contract via modification. No work shall commence until the contractor has received a fully executed TI. Each TI shall include the following information at a minimum:

(a) TI number (and TI revision number, if applicable) and title.

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

(c) Objective of the work directive (and TI revision, if applicable).

(d) Maximum number of hours authorized.

(e) Detailed description of work to be performed.

(f) Required completion date(s)/Period of performance.

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

(h) Identification of deliverables (reports, software, data, drawings and/or prototype hardware) to be delivered to PdD AWS.

(i) Security Requirements.

(j) Listing of Government-Furnished Material (GFM)/Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)/Government-Furnished Support (GFS)/GFP provided for the TI.

(k) CO’s signature.

C.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.

C.2.2.2 Maximum Contract Value.

The ceiling for the total effort under this contract is $29M.

C.2.2.3 Task Scope.

The Government may issue TIs that fall within the scope (see C.3.1 below).

C.2.2.4 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 TI is determined by the date of modification award, not by dates of performance (e.g. Technical Instruction 0002 awarded via modification on final day of Ordering Period One, with performance primarily in Ordering Period Two: ordering Period One rates will apply).

C.2.2.5 Contract Performance beyond Ordering Period Expiration:

Under this effort, there are five defined 12-month ordering periods. In the event that a TI is issued in Ordering Period Five, the Period of Performance (PoP) for that TI may continue beyond the expiration of Ordering Period Five. The PoP of the TIs may not continue more than twelve months from the expiration date of Ordering Period Five. As stated in C.2.2.4 above, the applicable labor rate for a TI in performance across ordering periods is determined by the modification award date.

C.2.2.6 Contract Type.

The contract type for this requirement will be either Firm Fixed Price (FFP), Firm Fixed Price Level of Effort (FFP LOE), or Cost-Plus-Fixed-Fee (CPFF) based on the individual requirements of each technical instruction. Material and travel will be on a Cost, No Fee basis only.

C.2.2.7 Contract Pricing.

The Contracting Officer (CO) may issue TIs that detail the Government’s technical requirements, travel requirements, performance standards, and required deliverables. Upon receipt of a T I, the contractor shall provide its proposed labor mix multiplied against the applicable labor rate(s) for the applicable categories and 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. 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 CO will issue a performance-based Firm-Fixed-Price (FFP) or FFP Level of Effort (FFP LOE)T Is modification.

C.2.2.8 Schedule.

The contractor shall notify the Contracting Officer's Representative (COR) and the CO immediately by telephone if the dates that the work must be performed or data to be delivered will not be met. The contractor shall follow-up the telephone call with a letter/email to the COR and CO within 10 business days, detailing the reasons why the requirements will not be met and proposed corrective actions.

C.2.2.9 Work Priority.

The Government has the unilateral right to increase, decrease, or prioritize the work to be performed hereunder by the issuance of T Is signed by the CO. It is understood and agreed that such adjustments will be made within the general scope of work and level of effort of the contract and with equitable adjustment.

C.2.3 Commerciality.

The contracting officer has determined that the services under this task order are Non-Commercial.

C.2.4 Period of Performance and Estimated Labor per Ordering Period:

The period of performance of the contract is 60 months.

C.2.5 Place of Performance.

The contractor shall perform the work under this task order at the contractor’s facility and/or onsite where vessels are located within the continental United States, Hawaii, Kuwait, Japan and other CONUS and OCONUS locations as directed in the technical instructions. 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. The contractor shall provide onsite support within PdD AWS located in Warren, MI as required under specific technical instructions.

C.2.6 Hours of Operations.

All overtime requests must be coordinated in advance and approved in writing by the COR. The contractor shall conduct business, no more than, 40 hours per workweek per employee based on a seven (7) day workweek (Sunday through Saturday), 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 CO will discuss an alternate billing arrangement on a case-by-case basis. The contractor shall maintain an adequate workforce for the performance of all tasks defined within this PWS and individual TIs.

C.2.7 Start of Work Meeting.

The contractor shall host a Start of Work Meeting at the U.S. Army TACOM LCMC facility in Warren, Michigan with contractor leadership, PdD AWS representatives, the COR and the Contracting Officer, no later than 15 calendar days after contract award. The contractor shall outline how all tasks are to be accomplished in the first TI. The contractor shall discuss any issues with regard to completing all assigned tasks.

C.2.7.1 TI Kickoff Meeting.

The contractor shall hold a Kickoff Meeting for each TI. The Kickoff Meeting shall include the contractor personnel assigned to the tasks prescribed by the TI and PdD AWS personnel overseeing the TI. Kickoff Meetings shall be held by phone within 15 days of award of a TI unless otherwise agreed to by PdD AWS. Kickoff Meetings may be held in conjunction with other regularly scheduled PdD AWS meetings.

C.2.7.2 Meeting Minutes.

Following the Start of Work Meeting and each Kickoff Meeting, the contractor shall submit meeting minutes within two business days IAW CDRL A003.

C.2.8 Other Direct Costs (ODCs).

All anticipated ODCs associated with performance shall have an established price at time of award of the TI. All proposed ODCs in excess of $10,000 shall be reviewed and approved by the CO prior to contractor expenditure.

C.2.9 Access to Data On request by the CO or designated COR, the Contractor agrees to provide access to records and data generated in the course of performing an individual TI. The Government shall have access, retention, and unlimited rights to all data (e.g. hard copy and computer files generated under the applicable TI and all underlying data and files) as well as reports, assessments, software programs, technical reports, and analyses.

C.2.10 Integrated Product Team (IPT) The contractor shall be a participant in all planning/implementing meetings such as IPTs and working groups. The contractor shall host design review meetings as required by the TI. Design review meeting dates shall be determined after award of the TI.

C.3.0 REQUIREMENTS – SPECIFIC TASKS

C.3.1 Scope of Work.

Tasks to be performed under this PWS will be assigned by TI. Properly executed TIs will become part of this PWS. TIs may include tasks from multiple sections of this PWS.

C.3.2 Work Areas.

The contractor shall implement a System Engineering approach for analyzing, developing, and enhancing PdD AWS’s ongoing program. The areas that shall be the focus of the contractor’s efforts are identified below (C.3.2.1 – C.3.2.13). The contractor shall supply the required resources to perform the following system engineering tasks related to the PdD AWS programs. The contractor shall investigate, analyze, and consider cost variables and affordability issues and conduct cost/technical trade off analysis as required for each work area as directed by TIs. The contractor may receive TIs requiring multiple work areas to be supported.

C.3.2.1 Engineering and Safety Analyses.

The contractor shall perform engineering analyses, design, and testing services to include but not limited to failure analysis, technology surveys, trade studies and trade-off analyses, Manufacturing Readiness Level (MRL) analysis, architecture evaluations, cost modeling, engineering design review for life cycle cost reductions, and product change analysis of components and end items. The contractor shall provide component and system testing, design analysis, design layout and simulation, proof and prototype build, and delivery of recommended design changes to the government. The contractor shall develop domain models and use cases to analyze systems for safety as well as function. Safety analysis may include qualitative and quantitative methods (finding causal dependencies between a hazard on system level and failures of individual components, probabilities, rates and/or severity of consequences).

C.3.2.2 System Requirements Analysis.

The contractor shall perform a system requirements analysis for either new systems or new applications of an existing system. The analysis shall include functional, performance, and environmental requirements. The contractor shall consider the system users’ requirements and growth capability. The contractor shall prepare Systems Engineering Plans (SEP) for AWS, as required. The SEP will capture the required steps to manage the system during the life of the system.

C.3.2.3 System Design.

The contractor shall generate a design based on the systems functional and performance requirements. The contractor shall be capable of allocating functions to hardware and software through engineering synthesis. The contractor shall investigate existing and future technologies as part of the system engineering process. The contractor shall use concurrent engineering practices that may include human factors engineering, packaging engineering, and software engineering in the generation of a design that will meet all the system requirements.

C.3.2.4 Engineering Changes and AWS Engineering Process.

The contractor shall be required to develop and apply engineering changes to PdD AWS vessels. For all projects resulting in a change to the configuration of a PdD 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 to be provided at the Start of Work Meeting, unless otherwise instructed by the TI.

C.3.2.4.1 Engineering Change Proposals.

The contractor shall submit Engineering Change Proposals (ECPs) IAW CDRL A005.

C.3.2.4.2 Engineering Release Record.

The contractor shall submit Engineering Release Record(s) IAW CDRL A009.

C.3.2.4.3. Preliminary and Critical Design Reviews.

Following the Kickoff Meeting, the contractor shall develop design concept(s) to meet the requirements of the TI and shall present the concept(s) to the Government at a Preliminary Design Review (PDR). The contractor shall present a PDR completion timeline to the government (which may be unique to individual TIs). Once approved by the Government, 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 TI. 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 within two business days IAW CDRL A003.

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

The contractor may be required to 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 Notices of Revision (NOR) and Technical Data Packages (TDPs) not required with PECPs. PECPs do not satisfy the requirement for a formal ECP.

C.3.2.6 Maintenance Concept and Engineering.

The maintenance concept is critical in system design and its planned support for AWS. 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, general overall repair policies (such as "repair or replace" criteria), organizational responsibilities for maintenance, anticipated availability of resources, use of contractor resources both CONUS and OCONUS, and establish the contractor is in compliance with all applicable statutory and regulatory maintenance guidance.

The contractor shall provide support for the following: expert repair and maintenance of Army Watercraft, Failure Mode, Effects, and Critically Analysis (FMECA) requiring a bottom-up, inductive analytical method to be performed at either the functional or piece-part level, which will be summarized in a Failure Mode Effects Summary. The contractor shall conduct a Level of Repair Analysis (LORA) to determine item replacement, repair, or disposal based on cost considerations and operational readiness requirements. The contractor shall support maintenance allocation charts displaying operator or crew, unit maintenance, direct support maintenance, general support maintenance, or depot maintenance. The allocation chart shall contain the necessary grouping such as assembly group, maintenance function, maintenance level, required tools and equipment, and remarks. Two-Level Maintenance includes sustainment and field maintenance.

C.3.2.7 Systems Engineering.

The contractor shall perform systems engineering to design, develop, integrate, test, and sustain C4ISR capabilities for Army Watercraft, including both tactical communications and commercial navigation systems. The contractor shall identify and analyze requirements to integrate systems to the Global Information Grid and meet Net Ready-Key Performance Parameters. The contractor shall generate and update Information Support Plans (ISPs) and shall coordinate with various Government agencies to get required products/information incorporated into the ISP and facilitate the ISP approval process.

C.3.2.8 Information Assurance and Cybersecurity.

The contractor shall manage the lifecycle cybersecurity risk to DOD IT IAW DODI 8510.01 and Risk Management Framework (RMF) documentation. The contractor shall coordinate and facilitate obtaining Army Interoperability Certification for necessary systems. The contractor shall conduct data modeling of wireless networks to include throughput, bandwidth, frequency, and range.

C.3.2.9 System Integration.

The contractor shall perform hardware/software integration, subsystem and system integration. The contractor shall assure that all hardware components, software modules, and subsystems within the system are communicating and performing in accordance with the system requirements and design.

C.3.2.10 Prototype and Proof.

When required by TI, 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 demonstrate functionality, validate the technical data package, and validate the modification instructions. Upon completion of the first prototype installation and functionality demonstration, the contractor shall hold a Prototype Review (PR). The PR shall present status to the government, identify any needed configuration changes, update the TDP, and obtain approval for the second prototype installation. The second prototype will serve as a “proof” or “Low Rate Initial Production (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 PdD AWS engineering in advance, IAW with 3.2.15.6 and CDRL A006 (Request for Variance).

C.3.2.11 Production Readiness Review (PPR).

Following a successful proof installation, the contractor shall hold a PPR to present status and outcomes of the proof installation to the government and obtain approval to finalize the design and submit a formal ECP. Following the PPR, the contractor shall submit meeting minutes IAW CDRL A003. Following successful completion of the PPR, the contractor shall prepare and submit an ECP IAW with 3.2.15.5 and CDRL A005. The contractor shall furnish all drawings and models of the new design to the government IAW with CDRL A007.

C.3.2.12 Vessel Modifications.

In addition to prototype and proof installations identified in 3.2.10 the contractor may be required to complete modifications to vessels IAW with an approved TDP. When instructed by a TI, the contractor shall complete modifications to vessels IAW with the provided TDP. Any deviations from the approved TDP must be approved by PdD AWS Engineering in advance and be IAW Section 3.2.15.6 and CDRL A006. The contractor shall provide all equipment, hardware, labor, and supervision to complete the modification at the site identified in the TI.

C.3.2.13 Technical Data Package (TDP).

The contractor shall deliver TDPs per requirements IAW the applicable TI, CDRL A007, and Attachment 0002 (TDP Requirements).

C.3.2.14 Modification Work Order.

When instructed by TI, the contractor shall prepare Modification Work Orders (MWOs) from each ECP IAW MIL-PRF-63002L(TM), AR 750-10, and CDRL A015. The contractor shall create fully scripted MWOs as directed by the TI.

C.3.2.15 Configuration Management (CM).

The contractor shall have a CM program implemented at contract award and shall comply with the requirements in EIA-649-1, this contract, corresponding CDRLS, CM Attachment 0001 and applicable TIs.

C.3.2.15.1 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.

C.3.2.15.2 Configuration Identification.

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.3.2.15.3 Interface Control Documents.

The contractor shall submit Interface Control Documents (ICDs) IAW CDRL A010.

C.3.2.15.4 Configuration Control.

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

C.3.2.15.5 Notices of Revision (NOR) The contractor shall submit NORs IAW CDRL A005.

C.3.2.15.6 Request for Variances The contractor shall submit Requests for Variances (RFVs) IAW CDRL A006.

C.3.2.15.7 Configuration Status Accounting.

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.

C.3.2.15.8 Configuration Verification and Audit.

The contractor shall conduct Configuration Verification and Audit IAW Principles CVA-1 through CVA-3 of EIA-649-1.

C.3.2.15.9 Configuration Audit Plan The contractor shall submit a Configuration Audit Plan IAW CDRL A012.

C.3.2.15.10 Audit Summary Report The contractor shall submit a Configuration Audit Summary Report (CASR) IAW CDRL A013.

C.3.2.16 Testing:

The contractor shall perform testing of AWS’ vessel systems as required in the TI. The contractor shall develop test plans, test description, software test code, and test reports. The testing effort shall include software from the Computer Software Unit level and hardware from the module to Line Replaceable Unit (LRU) level. System level testing shall flow from individual LRUs up to final system configuration. The contractor shall participate in field and contractor facility tests by preparing test plans, preparing test procedures, performing system operation, system troubleshooting, data acquisition, data reduction and analysis, and preparing test reports. The contractor shall provide staffing and logistical activities for tests as identified in test plans and as directed by the TI.

C.3.2.17 Integrated Logistics Support (ILS).

The contractor shall conduct ILS involving managing an integrated and iterative process for developing materiel and a support strategy that optimizes functional support, leverages existing resources, and guides the system engineering process to quantify and lower life cycle cost and decrease the logistics footprint, making the AWS system easier to support IAW Army Regulation (AR) 700-127.

C.3.2.17.1 Logistics.

The contractor shall plan, manage, and execute the logistics requirements described herein. Integrated Product Support (IPS) programs analyze the support requirements, develop and deliver logistics support packages including parts, provisioning data, technical data, training, and technical support for contractor-generated ECPs for AWS and additional support items required in the TI. The IPS package shall include all logistics data specified below, which supports all generated ECPs. All IPS/Logistics Management Information (LMI) shall be prepared and delivered IAW designated CDRLs and guidance provided in MIL-HDBK-502, DoD 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

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

c The contractor shall deliver all word processing files, i.e. Microsoft Word for Windows.

C.3.2.17.2 Maintenance and Obsolescence 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, and 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.

C.3.2.17.3 New Equipment Training (NET).

The contractor shall provide training and transfer of knowledge to the Army end user to achieve operational capability in the shortest time practical. The contractor shall be responsible for conducting NET training in both CONUS and OCONUS locations. The contractor shall be responsible for providing certified instructors, preparing and maintaining training plans, working with AWS to develop training schedules and coordinating the NET training team to training sights to deliver training.

C.3.2.17.4 Technical Publications.

The contractor shall develop Technical Publications inclusive of updates and changes to TMs resulting from, but not limited to technical support, alterations, or installations.

C.3.2.18 Program Management.

The contractor shall attend a monthly PdD AWS Integrated Product Team meeting. The contractor shall perform Independent Verification and Validation (IV&V) tasks to include evaluating design processes and document reviews. The contractor shall conduct technical investigations, prepare and present technical papers/subsystems/systems, and attend technical information exchange meetings. The contractor shall provide administrative services to include meeting coordination by scheduling, contacting meeting attendees and reserving facilities, resource tracking and progress status by project, availability, and schedule, travel coordination including making reservations and preparing necessary travel documents, purchase requisitioning and locating sources of items to be purchased, management by maintaining and tracking the list of automatic data processing inventory, facility maintenance coordination including making required maintenance requests and monitoring corrective maintenance actions, forms preparation, document preparation, arranging field test sites, and presentation material preparation to PdD AWS.

C.3.2.18.1 Business Case Analysis (BCA).

The contractor shall develop a BCA that will provide more than one course of action to optimize total system availability yet minimize cost and the existing logistic footprint. The BCA shall contain a structured methodology within both organic and contractor’s logistical support inclusive of existing processes, resources, and feasible courses of action.

C.3.2.18.2 Schedules.

The contractor shall create and maintain an Integrated Master Schedule (IMS) (IAW CDRL A002) for each TI, to include developing an IMS for various PdD AWS programs. The contractor shall use computer software, which is compatible with the hardware/software utilized by PdD AWS (Microsoft Project). The schedule shall have a title and TI number. Schedules shall specify all necessary tasks to complete the work prescribed by the TI. 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 should be able to calculate a critical path through each TI. The contractor shall submit a critical path analysis report that includes tasks within 10 working days of the critical float value to the Government indicated milestone that includes a float analysis and variance report with a narrative explanation of the root cause and corrective action or mitigation plan to recover the lost schedule. 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.

C.3.2.18.3 IPS Management Responsibilities.

The contractor shall identify an IPS Manager who will be the primary Point of Contact (POC) for 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.

C.3.2.18.4 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. 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.3.2.18.5 Materiel Release Services.

The contractor shall prepare materiel release packages in accordance with ARs and local policy, coordinate the timely receipt of documentation, and present status briefings.

C.3.2.19 Quality Assurance.

Contractor shall provide oversight and ensure compliance maintaining both internal and external audit programs along with their corresponding correction/preventative action programs. Contractor shall also be responsible for Managers' Internal Control Program, Balance Scorecard, and other regulatory agency inspections.

C.3.2.19.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 meet the requirements of American National Standards Institute/ International Organization for Standardization /American Society for Quality ISO 9001-2015 (ANSI/ISO/ASQ/ISO 9001-2015) or an industry recognized equivalent standard. The contractor’s quality system shall address all contract requirements and work activities impacted by the work performed such as management, design, fabrication, processing, production, shipping, storage, site installation, software, hardware, and testing at all facilities. The quality system shall follow the guidelines within ISO 9001-2015 or equivalent Quality Standard/Technical Standard (QS/TS) guidance documents. The quality system shall achieve defect prevention, process control, and record keeping. The contractor shall provide adequate quality controls throughout all areas of contract performance. All documentation shall be available for Government review throughout the contract period.

C.3.2.19.2 Directed Quality Efforts.

When directed by a TI, the contractor shall perform supplemental quality efforts, such as trend analysis, support the Government during quality symposiums and strategic planning events (CDRL A016), and develop test plans and Test and Evaluation Master Plans (TEMPs) (CDRL A017).

C.3.2.20 Technical Support.

The contractor shall provide support for quality assurance reviews, conduct pre-installation ship checks to verify the accuracy of installation drawings, identify interferences, and identify discrepancies between installation drawings and actual vessel configuration, including verification of the material requirements contained in the drawing. Develop ECPs where applicable. Develop database design models and provide networking and engineering support for new and existing hardware/software/system requirements, develop data structures to assist with the management of related systems and components including hardware, software, and system interfaces, develop/maintain data structures to assist with the management of technical data and system network information, and testing/troubleshooting hardware/software/network systems.

C.3.2.20.1 Technical Investigation.

Tis for engineering work may require a technical investigation, design of a modification to PdD AWS vessels, or both. When instructed by a TI, the contractor shall perform the tasks contained within the TI. The contractor shall 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 will be identified in the applicable TI. If specific tasks requiring the completion of technical investigations are not identified in the TI, the contractor shall identify and conduct the specific tasks required to deliver the end product(s) required by the TI. Technical reports shall be submitted IAW 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 shall include cost estimates, calculations, sketches, schematics, and other visual depictions.

C.3.2.20.2 Technical Report.

Following the PPR, the contractor shall submit a technical report. Technical reports shall be submitted IAW CDRL A004 and shall thoroughly 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 shall include cost estimates, calculations, sketches, schematics, and other visual depictions.

C.3.2.20.3 Regulatory Compliance.

As part of each technical investigation, the contractor shall evaluate the compliance of systems identified in applicable TIs with laws and regulations identified by the CFR, International Convention on SOLAS, ABS, IMO, and any other applicable regulations that will be identified in the TI. Compliance or non-compliance of investigated systems shall be identified in the technical report IAW CDRL A004.

C.3.2.20.4 Temporary Modifications.

As part of a technical investigation, the contractor shall be required to temporarily modify a vessel system or subsystem. 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 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 TI.

C.3.3 Security Requirements:

The Contractor shall adhere to all security requirements listed below along with those identified in the DD 254 and Continuation Sheets, attachment zzzz.

C.3.3.1 Cyber Security.

The contractor shall develop and implement a Cybersecurity Strategy that addresses the contractors software development, software assurance, hardware validation, supply chain risk management, testing (architecture and configuration), vulnerability management, patch management, release management and configuration management efforts for the PdD AWS STS contract. This strategy will be used to validate the systems cybersecurity posture throughout contract period of performance. The contractor shall provide a copy of their Cybersecurity Strategy, IAW CDRL XXXX, which will be incorporated into the program’s Cybersecurity Strategy. The contractor shall execute the Cybersecurity Strategy which includes: analyzing system security requirements derived from the requirements of this contract; designing a system and the security architecture; developing detailed system security design; developing security test strategy; and developing a report that outlines the system risk for the proposed architecture in accordance with System Security Design and Risk Assessment, CDRL XXXX.

This information shall be available to the Government and discussed at IPT meetings and technical reviews. The contractor shall support IA/cyber assessment and authorization of the system by providing the Cybersecurity Artifact Package in accordance with CDRL XXXX. This information shall be available to the Government and discussed at IPT meetings and technical reviews.

C.3.3.1.1 Data Protection The contractor shall establish appropriate administrative, technical, and physical safeguards to protect all Government data, to ensure the confidentiality, integrity, and availability of Government data in accordance with DoD Instruction (DoDI) 8582.01 Security of Unclassified DoD Information on non-DoD Information Systems. The contractor shall encrypt all unclassified data (including CUI and For Official Use Only (FOUO)) stored electronically using Federal Information Processing Standard (FIPS) 140-2 validated encryption, IAW DoDI 8582.01.

C.3.3.1.2 Policies The contractor shall comply with the Army and DoD IA/Cybersecurity policies to include Army Regulation (AR) 25-2, IA, associated Best Business Practices (BBP), Security Technical Implementation Guides, DoD policy to include DoDI 8500.01 Cybersecurity, DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), National Institute of Standards and Technology (NIST) standards, including FIPS publications, Chairman of the Joint Chiefs of Staff Manual (CJCSM) 6510.01IA, Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01E Interoperability and Supportability of Information Technology and National Security Systems, DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), Federal Information Security Management Act (FISMA), and AR 380-5 Department of The Army (DA) Information Security Program. The contractor shall provide the IA documentation needed for assessment and authorization as outlined in DoDI 8510.01 and conform to IA controls outlined in NIST SP 800-53 Rev 4, Recommended Security Controls for Federal Information Systems and Organizations. The contractor shall conform to DoDI 8551.1, Ports, Protocols and Services (PPS) Management (PPSM). In addition as part of the Cybersecurity Artifact Package, CDRL XXXX, the contractor shall list all PPS being used in the PdD AWS STS contract, system software and associate those PPS to the modules and functions where they are used.

C.3.3.1.3 Cybersecurity Workforce.

IAW cybersecurity directives, the Government requires cybersecurity support for all tasks identified. The contractor shall designate at least one individual as subject matter expert for Cybersecurity for the PdD AWS STS contract. This person will be the single point of contact for all Cybersecurity issues at the contractor’s facility. The contractor shall have an individual designated as the contractor's System Security Engineer who will support development of the Program Protection in Section C.4 and work with the Systems Engineer for the PdD AWS STS contract in addressing all Cybersecurity issues relative to all issued TI’s.

To achieve Cybersecurity assessment and authorization, the contractor cybersecurity support must comply with training requirements and certifications mandated by DoD Directive (DoDD) 8570.01-M IA Workforce Improvement Program for Information Assurance Technical (IAT) Level III, identifying all personnel assigned with cybersecurity roles and functions and ensuring certification and background checks are completed. This information shall be made available to the Government upon request. Current DoD Approved 8570 Baseline Certifications can be found at http://iase.disa.mil/iawip/Pages/iabaseline.aspx.

C.3.3.1.4 Annual Cybersecurity Review For the life of the contract, the contractor shall provide access to Command, Control, Communications, Computers Intelligence, Surveillance, and Reconnaissance (C4ISR) and Cybersecurity Subject Matter Experts (SME), vessel and documentation for all vessel and equipment (Contractor Furnished Equipment (CFE) and GFE) configurations for joint Government and contractor annual security reviews. The reviews shall occur annually from the date of baseline cybersecurity and software scan and annual security review. The Government estimates the contractor will need to provide sufficient SMEs for five business days per planned activity.

C.3.3.2 Operations Security (OPSEC).

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, IAW DoDM 5205.02-M and AR 530-1, and in accordance with the stipulations listed in the attachment zzzz.

C.3.3.3 Controlled Unclassified Information (CUI).

Controlled Unclassified Information shall be protected IAW the applicable AWS Interim SCG, dated 23 February 2015, as well as the OPSEC Plan, respective DoD and Army Regulations, and additional guidance provided in attachment zzzz.

C.3.3.4 Communications Security (COMSEC) The contractor shall adhere to COMSEC guidelines and DoD and Army Regulations further identified in the attachment zzzz.

C.3.4 Program Protection.

The contractor shall comply with the security requirements imparted by the DD Form 254 (Attachment 0004), the NISPOM DoD, 5220.22-M), and AR 70-77.

C.3.4.1 Program Protection Working Group and Critical Program Information Assessment (CPIA).

For the life of the contract, the contractor shall host a Program Protection Working Group (PPWG) not less than annually. The first PPWG shall be held as part of the Contract SOWM. Each PPWG will be chaired by the Government Systems Engineer and co-chaired by the contractor's System Security Engineer. The co-chair shall develop the agenda and action items (Reference CDRL A001, Conference Agenda and CDRL A002, Report, Record of Meeting Minutes). The agenda will include a CPIA that will identify Critical Program Information (CPI) or Critical Technology (CT) (defined by DoDI 5200.39, 16 July 2008 Including Change 1 28 Dec 2010, CPI Protection within the DoD). Each PPWG will be a one day planned activity.

C.4.0 ADDITIONAL CONSIDERATIONS

C.4.1 Monthly Status Report.

The contractor shall deliver a Monthly Status Report (MSR) IAW CDRL A001. This report shall summarize accomplishments of the previous month, discuss major issues and concerns, discuss new support needs, summarize the current financial billing profile, including any projected shortfalls or under-runs, and 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 shall close out the last day of the contractor’s monthly accounting period and be submitted no later than 10 calendar days after close of the contractor’s monthly accounting period.

C.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.

C.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.

C.4.2.2 Chargeable Work.

In order for charges to be invoiced, deliverable services shall be 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 shall comply with individual company policy that is IAW 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.

C.4.3 Identification.

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

C.4.4 Non-Disclosure Agreements.

The contractor is responsible for providing executed Non-Disclosure Agreements (NDAs) (Attachment XX) for personnel supporting PdD 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.

C.4.5 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 CO. In order to comply with Defense Federal Acquisition Regulation Supplement (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 shall be sent to can be found at DFARS 525.204-7000.

C.4.6 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.

C.4.7 Restrictions/Prohibited Activities:

Contractor personnel, consultants, and subcontractor personnel are expressly prohibited from performing the following tasks IAW with the Federal Acquisition Regulation (FAR), its supplements, and other applicable laws and regulations:

·…