PSM_SOW_12-23-2014_doc.docx

Product Support and Installation Statement of Work

1.0 SCOPE

Program Executive Office Integrated Warfare Systems Major Program Manager for Undersea Systems (PEO IWS 5) is responsible for ensuring life-cycle support of Undersea Warfare (USW) Systems and auxiliaries. This requirement concentrates on four inter-related areas of support; 1) logistics, 2) installation, 3) fleet support, and 4) life-cycle-sustainment. This includes Manpower & Personnel, Training and Training Support, Support Equipment, Technical Data, Packaging, handling, Storage & Transportation (PHS&T), Maintenance Planning and Management, Supply Support, Design Interface, Sustaining Engineering, Equipment Installation, SID review, ICD reviews, installation of Engineering Changes, staging of materials, outfitting, EC kit procurements, In-Service-Support, supportability metrics, New Construction Forward Fit support, Transducer Support SHIPMAIN Support, and Direct Fleet Support for both US and Foreign Military Sales (FMS) customers. Surface ship ASW capabilities cross all phases of acquisition.

Approximately 75% of the Surface Ship ASW capable ships are in the Operations and Support Phase, having stable software and hardware baselines utilized as fleet operational assets. Upgrade of these systems to AN/SQQ-89A(V)15 is currently in the production and deployment phase. Planned AN/SQQ-89 APB, LCS ASW and AN/SQQ-90 capabilities are in the technology development phase with future technology refresh for all systems undergoing material solution analysis.

When compared to AN/SQQ-89 and LCS ASW MS efforts, significant AN/SQQ-90 ASSE efforts are not expected to be accomplished within the scope of this contract. AN/SQQ-90 ASSE efforts will be focused on re-use of AN/SQQ-89 data to support AN/SQQ-90 functionality, and expansion of existing ASW infrastructure and processes to support the AN/SQQ-90 system.

1.1 Applicable Documents

The following documents provide guidance for format, content and process used to facilitate completion of efforts within this contract.

· PEO IWS 5 Surface Ship USW Combat Systems Integrated Logistics Support Plan (ILSP), IWS 5B-12-ILSP-011R2, including:

· Integrated Warfare Undersea Systems Maintenance Planning and Management Plan (MPMP) IWS 5-10-MPMP-081R2

· Integrated Warfare Undersea Systems Commercial Off The Shelf Item Management Plan (COTSMP) IWS 5-12-COTSMP-011R2

· Integrated Warfare Undersea Systems Supply Support Management Plan (SSMP) IWS 5B-10-SSMP-086R2

· Integrated Warfare Undersea Systems Technical Data Process Plan (TDPP) IWS 5B-10-TDPP-179R1

· Integrated Warfare Undersea Systems Manpower, Personnel and Training Management Plan (MPTMP) IWS 5-12-MPTMP-100

· Integrated Warfare Undersea Systems Consolidated Depot Management Plan (CDMP) IWS5-12-CDMP-118R2

· AN/SQQ-89(V) Unique Identification (UID) Plan, DTD 20 April 2006

· Surface Ship USW Combat System Configuration Management Plan, IWS 5-93-Q89-CMP-009R4

· Navy Training Systems Plan for AN/SQQ-89(V) Surface ASW Combat System N86-NTSP-S-30-8102K

· DOD-STD-2106- Department of Defense Design Criteria Development of Shipboard Industrial Test Procedures

· NAVSEA Standard Item 009.04 Quality Plan IAW NAVSEA Standard Item 009.04 (GFI)

· DoDI 3020.41, Contractor Personnel Authorized to Accompany the U.S. Armed Forces

· TS9090-310D / SL720-AA-MAN-020 – Technical specification: Alterations to ships accomplished by Alteration Installation Teams

2.0 REQUIREMENTS

The Major Program Manager Manager for Under Sea Warfare (USW) systems managed by the Program Executive Office Integrated Warfare Systems Major Program Manager for Undersea Systems (PEO IWS 5) is responsible for logistics, installation, fleet support, and life-cycle-supportability USW equipment, including:

· AN/SQQ-34 Aircraft Carrier Tactical Support Center (CV-TSC), Integrated Warfare Commander Cell (IWCC) and Sea Combat Commander’s Cell (SCC)

· Navy Signal Processors

· Advanced Development and Advanced System Technology Programs including the following Surface, Submarine and Air programs:

· Multi-Static Active ASW (MAASW)/Distant Thunder

· Active sonar transmission

· Advanced signal and data processing

· Active sonar classification, towed and hull arrays transducer technology (ie. Conformal Acoustic Velocity Sonar and Low Cost Conformal)

· Multi-static sonar, multi-sensor data fusion

· Advanced Capability Builds

· Advanced Processing Builds-Acoustic

· Advanced Processing Builds-Tactical

· Towed Arrays and Towed bodies

· Brag Grating sensors and vector sensors

· AN/SQQ-90 Tactical Sonar Suite

· LCS ASW Mission System

· AN/SQQ-89 Surface Ship Undersea Warfare Combat System (all variants, adjunct systems & sub systems)

· Ancillary systems as follows:

· AN/ARR-75 Sonobuoy Receiver

· AN/BQH-7 Bathythermograph Set

· AN/SQQ-56, 60 & 61 Expendable Bathythermographs

· AN/SQQ-89 On Board Trainer

· AN/SQR-18 Tactical Towed Array Sonar System

· AN/SQS-35(V) Variable Depth Active Sonar

· AN/SQS-56 Sonar

· AN/UQN-4 Fathometer

· AN/UYQ-21 Signal Data Processor Group

· AN/UYQ-100 / USW Decision Support System (USW DSS)

· AN/WQC-2/6 Acoustic Communications

· Computer Aided Dead Reckoning Tracer (CADRT)

· FF Integrated Shipboard Tactical System (FFISTS)

· MK 111, 114 & 116 Underwater Fire Control Group

· MK 309 Control Panel

· MK 34 AS W Switchboard

· MK 432 Test Sets

· OJ-452 Display console

· RD-420 Recorder/Reproducer

· Surface Vessel Torpedo Tubes & Launchers

2.1 Program Management

The contractor shall provide technical and business management for this contract. The contractor shall provide direction and control over all contract activities, contract administration, contract planning, schedule and financial management, subcontract management, and contract resource management under this effort. The contractor shall assign a specific point of contact within the contract program management area.

The contractor shall establish a Product Supportability program in accordance with the requirements of this Statement of Work (SOW). This plan shall be updated and submitted to the Government for approval.

The contractor may be required to purchase NMCI approved assets from the current approved vendor (HP). If required, all costs associated with the initial purchase and any monthly fees shall be direct charged to this task order. The contractor shall track these assets and ensure that the assets are directly linked to the NMCI network at least once every 30 days to obtain software patches and updates.

2.1.1 Security Management

Requests for CACs will only be accepted by the government when endorsed by the contractor Facility Security Officer (FSO). Assigned government personnel shall be provided badges for access to classified areas within the contractor managed spaces.

2.1.2 Work Breakdown Structure

The contractor shall establish and maintain a Work Breakdown Structure (WBS) for this contract (CDRL TBD). The WBS shall be broken down to the third discrete work package level. The WBS shall be consistent with product development and installation schedules agreed upon between the government and the contractor. The contractor shall track the labor hours and costs incurred for each TI using the WBS and shall provide the basis of invoices submitted for all work performed. The WBS numbers must be identified on the invoices so that charges are accurately and easily identified.

Upon government approval of the WBS, the Contractor shall accrue and report costs via a monthly report NLT the 10th calendar day of the following month for the efforts accomplished during the previous month. For work completed prior to the approval of the WBS, the Contractor shall attribute work/costs to date to the appropriate work package(s) and provide the results with the next subsequent submission. (CDRL TBD)

2.1.3 PSM Product Schedules

The contractor shall maintain PSM product development schedules and update the status of ongoing efforts on a monthly basis. The development schedules shall be delivered via iPDM and made available on Advanced Logistics Information and Configuration Environment (ALICE) located at https://ipdm.navy.mil. (CDRL TBD)

2.1.4 Meetings

The contractor shall attend, conduct and/or support meetings, seminars, and conferences related to USW system logistics and technical issues. The contractor shall provide equipment and services required to facilitate cost effective exchange of information between government agencies with varied locations on a 24 hour a day, 7 day a week basis. The contractor shall provide video conferencing services, host web-ex meetings, provide War Room and conference space for program, project and asset allocation reviews to facilitate up to 30 personnel.

The contractor shall provide the minutes of meetings conducted or attended along with action items no later than 15 business days after the meeting. The contractor shall provide follow-up on all assigned action items. Action items shall be maintained via the Action Item tracker on ALICE. Once approved by the government, summaries for meetings shall be posted on ALICE with electronic notification to meeting attendees. (CDRL TBD)

2.1.5 Kick-Off Meeting

The contractor shall host a 2-day kick-off meeting within 10 business days of contract award at the current performing facility. The Government shall review all required certificates, plans, processes and procedures required for the successful execution of this contract. The contractor shall exchange point of contact data for facility Defense Security Services (DSS) representative, Defense Contract Management Agency (DCMA) representative and specific technical RIs with the Contracting Officer and Contracting Officer’s Representative (COR). The contractor shall present all System Authorization Access Request SAAR forms and supporting documents required for access to https databases (IA, PII, training certificates etc) and coordinate database access requirements. The contractor shall submit the initial requests for common access cards (CACs). The contractor shall discuss any changes required to the DD254 and facility security policies. Deliver updates Monthly via CDRL TBD

2.1.6 Quarterly Program Reviews

The contractor shall conduct quarterly Contract Program Reviews at its facility to address the status of efforts, funds and any issues associated with this contract. Presentation materials and meeting minutes to be provided via CDRL TBD.

2.1.7 Installation Readiness Reviews (IRRs)

The contractor shall host/participate in a minimum of ten Installation Readiness Reviews (IRRs) per year. The Government anticipates that a maximum of 12 reviews a year may be required, and reserves the right to hold additional reviews if installation plans dictate. Presentation materials and meeting minutes to be provided via CDRL TBD

2.1.8 Integrated Logistics Support (ILS) Working Groups

The contractor shall host/participate in a minimum of six Integrated Logistics Support (ILS) Working Groups per year. The Government anticipates that a maximum of 12 reviews a year could be required, and reserves the right to hold additional reviews if plans dictate. Presentation materials and meeting minutes to be provided via CDRL TBD

2.1.9 Integrated Product Teams (IPT)

The contractor shall host/participate in a minimum of four ILS Integrated Product Teams (IPTs) per year. Presentation materials and meeting minutes to be provided via CDRL TBD

2.10 Supportability Integrated Product Team

The contractor shall prepare presentation material for and participate in program level Supportability Integrated Product Team (SIPT) meetings/presentations at a frequency of once per year. The SIPT function performs periodic assessments of the supportability of an acquisition program or project. Presentation materials and meeting minutes to be provided via CDRL TBD

2.11 On-Call Processes and Systems

The contractor shall establish “On-Call” processes and systems whereby contractor specified individuals can be contacted 24 hours a day, 7 days a week in performance of this contract. The contractor shall identify points of contact and alternates within their organization and provide contact information for functions arising after normal business hours. Points of contact shall possess sufficient authority to access contractor facilities, issue material, and coordinate emergent contractor personnel travel and similar emergent activities. Report activity monthly via CDRL TBD

2.1.12 Facilities

The contractor shall provide, equip and maintain an Integration and Logistics Center (ILC) within a twenty five-mile radius of the Norfolk Naval Base with interstate access to all modes of transportation (truck, rail, water, and air). The facility shall have a Secret security clearance and controlled access work area to include the proper storage of classified materials, and material handling equipment and procedures adequate to protect and preserve Government Furnished Property (GFP) from damage, to include Electrostatic Discharge (ESD). The facility shall identify and maintain physical locations and processes that ensure all environmental storage requirements (humidity and temperature control) are met with respect to items such as test equipment, circuit cards, and magnetic storage media. The facility shall provide for assembly and staging areas suitable for kitting, assembly, modification, engineering change installation, testing and troubleshooting and repair of GFP and Government Furnished Equipment (GFE). Hazardous material storage areas are required for the proper storage of material used in the course of supporting program events. The contractor shall adhere to all Defense Investigation Services Secret NISPOM and Information Assurance (IA) directives. The government will not be held responsible for any fines or legal action resulting from the contractor’s non-compliance of federal, state or local laws. The current facility supports 20,000 square feet of unclassified (warehouse, staging, repair) space and 10,000 square feet of space cleared for SECRET storage and processing. Total square feet required is 30,000. Industry is encouraged to bid any cost savings initiatives with regard to space utilization. This should be included in the transition plan.

For the facilities listed throughout this section, the Contractor shall prepare a maintenance program ensuring that all vendor-recommended maintenance or Navy PMS is performed. The contractor shall procure piece parts and consumables required to perform the daily operations of each facility and shall repair and upgrade Government Furnished Equipment (GFE) used within these facilities. If leased, the facility lease shall be transferrable to the following efforts within 60 days of award of the follow-on contract.

2.1.12.1 Logistics Support Facility (LSF)

Within the ILC, the contractor shall establish and maintain a Logistics Support Facility (LSF) capable of storing approximately 20,000 square feet of Government Property that will store approximately 432,547 parts. The facility shall be capable of supporting approximately 2.500 shipments per year and approximately 1,000 receipts per year of varying quantities. The current asset tracking database (Government On Line Database (GOLD)) will be replaced within the performance of this contract, The contractor shall utilize a non-proprietary DoDI 5000.64 compliant inventory system which is compatible with ERP. DoDI 5000.64 specifies the required data fields comprising a comprehensive property record as:

· Name of the asset, part number, model number, description

· Owner

· Unique Item Identifier (UII)

· National stock number (NSN)

· Acquisition cost or full cost value

· Location

· Status

· Estimated useful life

· General ledger classification

· Condition

· Posting references

· Date placed in service

2.1.12.1.1 ILS Development and Production Site (IDAPS)

Within the ILC the contractor shall ensure physical space (cleared to SECRET) for the development and production of ILS products, SIPRNet, and the conduct of USW training to uniformed personnel. The contractor shall maintain this site with the appropriate power, HVAC, and personnel to function as described in this SOW. The area must be cleared by DSS for SECRET processing, meet all local, federal, and DSS requirements and have visitor access control. The contractor shall maintain a log of hardware failures and report configuration changes, failures, upgrades etc accomplished.

2.1.12.1.2 Software & Firmware Reproduction Facility

Within the ILC shall reside an area capable of reproducing PEO IWS5 approved software and firmware changes for distribution to fleet systems in accordance with outfitting schedules, or in response to INCO or fleet failures. The area must be capable of generating and maintaining classified hardware, software, firmware, and documentation up to and including the level of SECRET. The contractor shall provide an area that meets the necessary space and equipment storage requirements in order to support the generation of and quality assurance for approximately 800 software and firmware total assets annually. The actual reproduction shall be performed by a government employee assigned by PEO IWS 5.

2.1.12.1.3 Commercial Off The Shelf (COTS) Testing, Repair and Evaluation area Within the LSF shall reside a COTS testing, repair and evaluation area. The contractor shall establish a clean environment for technicians to perform Micro Miniature repair of circuit boards and other LRUs. The contractor shall repair LRU items that are determined to be out of warranty by the original manufacturer.

2.1.12.1.4 Equipment Staging Area

Within the LSF, the contractor shall ensure space is available to install approved ECPs within GFP. In accordance with approved Engineering Change Proposal / Engineering change Order (ECP / ECO) Process, the contractor shall stamp the ECO accomplishment plate with the appropriate ECP or ECO number when post-installation testing has been completed.

2.1.12.1.5 Classified Storage

Within the ILC, the Contractor shall maintain a DISA approved storage area for classified material such as technical manuals, OGM, software tapes or disks. The contractor shall receive, store and track all classified material received and document each asset, at a minimum, by Part number, National Stock Number (NSN), manufacturer's part number, Commercial And Government Entity (CAGE) code, nomenclature or description, receiving document number and condition code.

The contractor shall have a working knowledge in Cold Fusion, JAVA, ASP, Extensible Markup Language (XML) and Oracle Internet products. The contractor shall support connectivity to the following: Failure Reporting Analysis and Corrective Action System (FRACAS), Technical Manual Identification Number (TMIN), Configuration Data Managers Database-Open Architecture (CDMD-OA), Defense Automated Message Execution System (DAMES), NAVSEA Crane Drawing Database, integrated Product Data Management System (iPDMS), Weapons System File (WSF), Haystack. The contractor shall assist with necessary installations and upgrades required to provide connectivity to the systems above. Status of all activities shall be provided within the monthly report CDRL TBD. Additional CSA requirements are addressed in section 2.2.10.1.

2.2.1.2 Integrated Product Data Management (iPDM) System Support The contractor shall provide programming and system design support for iPDM applications; specifically, CSA, COTS Cross Reference Database (CCRDB), ALICE, and Content Management tracker. iPDM applications are web-based and currently written in Oracle Developer 10 (i.e. Forms/Reports), Oracle PL/SQL, Cold Fusion, java script, and Active Server Pages (ASP) executing on a Windows 2000 server and Oracle environment. The contractor shall be responsible for maintaining existing application software, design documentation based on user requirements, forms/reports and upgrading applications due to software product upgrades. The contractor shall maintain the integration of iPDM with the AN/SQQ-89(V) MSH. The Contractor shall be proficient in Oracle Developer and PL/SQL, database design and analysis, diagramming tools, and Oracle database architecture. The contractor shall also have experience or training in Cold Fusion, JAVA, ASP, Extensible Markup Language (XML) and Oracle Internet products. List of actions accomplished monthly via CDRL TBD.

2.2.1.3 Enhanced Product Data Management (ePDM) System Support The contractor shall provide programming and system design support for ePDM applications; specifically, Content Management System (CMS) and electronic publishing applications such as .pdf, .xml. ePDM applications are web-based and currently written using Oracle Developer 10g PL/SQL , Cold Fusion, java, Java script, CSS style sheets, XML and XSLT on a Linux (CENTOS 5) and Oracle 10g environment. Active Server Pages (ASP) executing on a Windows 2000 server and Oracle environment. The contractor shall be responsible for maintaining existing application software, design documentation based on user requirements, forms/reports and upgrading applications due to software product upgrades. The contractor shall also support the migration of Oracle forms & reports to Oracle J developer, the integration of the above-mentioned applications with the Cold Fusion to alternate websites to be determined by the government. The contractor shall be proficient in Oracle J Developer 10g and PL/SQL, database design and analysis, diagramming tools, and Oracle database architecture. The contractor shall also have experience or training in Cold Fusion, JAVA, Extensible Markup Language (XML), XSLT and Linux and Oracle Internet products. List of actions accomplished monthly via CDRL TBD.

2.2.1.4 Data and Document Management

The contractor shall establish management process to maintain the configuration of data items and documents developed under this contract or provided as GFI within the iDAPS Content Management System (CMS). The process shall accommodate, at a minimum, four separate functions; data identification, data preparation, data maintenance, and data management. This process shall include identification procedures for data files and documents in an environment that is searchable and supports data mining and reutilization efforts and is available 12 hours a day 5 days a week in support of product development or maintenance. Data revision levels shall be identifiable in an effort to maintain consistency in reutilization efforts. The technical data manager will identify the specific files and documents to be managed and once placed under control shall not be altered except by procedures under this process.

2.2.2 Design Interface

The contractor shall interface with system design representatives and shall identify any Software or Hardware problem reports or other system changes that require resolution within the current or future ACB/TI. PEO IWS5B will provide ECPs, Deviations, Waivers or other Change Control Documents (CCD) that may have impact to products being prepared under this contract. The contractor shall evaluate the problem reports, ECP and other CCD impacting products and data previously delivered and being prepared under this contract and provide cost and schedule impacts from these changes for all areas cited in this contract to the Government. The contractor shall review Systems Performance Specification(s), System Design Specification(s), Hardware / Firmware / Software design documents, and other documents delivered by design activities for impacts to logistics products. The contractor shall submit comments to these documents to IWS5B Logistics and Installation Manager for review.

The contractor shall present obsolescence results from the COTS Working Group and forward them to the IWS5A System Engineering IPT lead for consideration in following Technology Insertion efforts. The contractor shall also provide this data to the In-service-Support leads designated by PEO IWS 5. Data to be provided quarterly within CDRL TBD

2.2.3 Reliability and Maintainability

The contractor shall provide reliability and maintainability support in accordance with the Maintenance Planning Management Plan and product Development schedule. The accomplishment of maintenance planning will involve the review of OEM CDRLS, performance of various analyses, and plans ensuring consistency between maintenance procedures, general/functional descriptions and other technical data, and training plans,. Additionally, the contractor shall author maintenance procedures (troubleshooting, corrective and preventive).Status provided monthly within CDRL TBD. The contractor shall review and staff maintenance plans, Reliability Centered Maintenance (RCM) data, Condition Based Maintenance Plus (CBM+), Level of Repair Analyses (LORA) and provide recommendations to the government for approval.

2.2.3.1 Reliability Maintainability and Availability (RM&A)

The contractor shall prepare, review and/or evaluate Failure Modes Effects and Criticality Analyses (FMECA), FRACAS or similar reliability documents or CDRLS. A summary shall be submitted to the government that identifies any resulting recommended maintenance actions to support the system reliability and maintainability thresholds established by the Program Office. The summaries shall include proposed solutions to RM&A drivers that are identified, new preventive maintenance actions, Intermediate/Depot level maintenance options, support equipment, spare parts, or consumables required. The summary shall be submitted to the logistics manager as the maintenance concept and should include rationale and recommendations for each item identified. CDRL TBD.

2.2.3.2 Reliability Centered Maintenance / Preventive Maintenance The contractor shall produce, or update Maintenance Requirement Summary Reports for each TI which identify all legacy and GFI preventive maintenance requirements that exist with a description of each requirement including hardware applicability. The contractor shall employ personnel possessing NAVSEA RCM level II certification regarding Navy maintenance procedure development and maintenance and demonstrate in depth knowledge of USW maintenance procedures, complete understanding / knowledge of the Navy's Planned Maintenance System (PMS) including development, verification and modification. The Contractor shall incorporate Technical Feed Back Reports (TFBR) changes and Failure Analysis Reports (FAR) USW systems. The contractor shall conduct a ship-specific Reliability Centered Maintenance (RCM) analysis utilizing decision tree logic to determine proposed scheduled maintenance actions from Maintenance Planning Summary Reports provided as GFI. Using vendor or OEM Mean Time Between Failure (MTBF) data, the contractor shall forecast potential failures prior to equipment degradation and to increase the system Operational Availability. The contractor shall update Maintenance Requirement Summary Reports via CDRL TBD to include the results of the RCM analyses.

The contractor shall prepare and maintain preventive maintenance procedures via the Content Managed System (CMS); maintain a Maintenance Index Page (MIP) and draft/update Maintenance Requirement Cards (MRC) to provide procedures and scheduling aids to accomplish the maintenance tasks for inclusion into the NAVY PMS system. MIP and MRC for existing PEO IWS5B equipment will be provided to the Contractor as GFI. MIP/MRCs shall be posted to ALICE and noted within the monthly report CDRL TBD.

The Contractor shall support validation/verification events for MIP and MRC products to ensure procedures are accurate and consistent with the system maintenance concept. A validation plan will be delivered to the government 20 business days prior to the validation event via CDRL TBD. At a minimum the validation plan will identify any unique requirements needed to support the event and the location where each MRC will be validated. The contractor shall resolve Technical Feedback Reports for PEO IWS5B system maintenance documentation by the government.

2.2.3.3 Maintenance and Repair Analysis

For equipment that is new to the fleet, the Contractor shall conduct repair analyses to identify maintenance requirements for system components and assemblies, and provide the Government via a Level Of Repair Analysis (LORA) with conclusions and recommendations for Source, Maintenance and Recoverability (SM&R) Coding assignments for each of the items and identify the most cost effective location for item repair (Organizational, Intermediate or Depot) or disposal. The contractor shall review existing SM&R and depot assignments for items used in new system baselines to ensure viability and conformance with the system Maintenance Concept. Discrepancies shall be reported to the government via a repair analysis summary report. Maintenance and Repair Analysis shall be delivered iaw CDRL TBD

2.2.3.4 Maintenance Plan

The contractor shall update system specific maintenance plans identifying all Organizational, Intermediate and Depot Level (O, I, & D) Lowest Replaceable Units for new equipment and all logistic resources required to support each level (O, I and D) of maintenance. Inputs for the Preliminary maintenance plan shall be based on vendor data and data generated from performing LORA and Task Skill Analysis. The maintenance plan shall be based on the Logistic Support Summaries and the applicable Maintenance Concept. The contractor shall update the maintenance plan to reflect all supportability related changes resulting from approved engineering design changes and deliver via CDRL TBD

2.2.3.5 Depot Support

The contractor shall provide organic and commercial support organizations who are seeking to achieve Depot level repair status for USW system components, with the technical data (drawings, schematics, test procedures) required to ensure successful repairs. The contractor shall conduct depot candidate certifications to ensure adherence with maintenance concept. Review current depot assignments in light of Diminished Manufacturing Sources (DMS) and obsolescence issues to mitigate system availability impacts. Provide status of efforts with recommendations as part of the quarterly review CDRL TBD.

2.2.3.6 Maintenance Data Authoring

The contractor shall draft and maintain technical documentation and illustration materials to adequately perform shipboard and intermediate level troubleshooting, corrective and preventative related maintenance tasks of superset systems. The data shall be developed in accordance with the established maintenance concept for the systems. Legacy data will be provided as GFI for the Contractor. Data shall be developed in accordance with Technical Data Management Plan (TDMP) and product schedules provided as GFI. Provide status of efforts with recommendations as part of the quarterly review CDRL TBD.

2.2.3.7 Maintenance Demonstration (MDEMO)

The contractor shall support conduct of the MDEMO events both in support of PM/FD/FL MDEMO, Original Equipment Manufacturer (OEM) MDEMO, or a Navy MDEMO. The contractor will interpret RM&A and LORA reports provided as GFI to assist in Performance Fault Monitoring (PFM) and Fault selection. The contractor shall ensure MDEMO events are included in the product development schedule and prepare a draft Navy MDEMO execution plan to facilitate Navy MDEMO events including faults to be inserted, method of insertion. The ILS Manager shall determine government and Navy roles and responsibilities to support MDEMO events. The contractor shall generate a report of the Navy MDEMO within 10 business days, detailing any findings or recommendations generated from the event and deliver via CDRL TBD

2.2.3.8 Maintenance Engineering

The contractor shall provide support for USW equipment Maintenance Engineering efforts. The contractor shall utilize reports and data being developed under the purview of PEO IWS5B by Universities, contractors and Navy Labs, and provided as GFE, within the Maintenance procedures. The contractor shall review FRACAS, Open Architecture Retrieval System (OARS) and similar data to determine equipment failure trends and provide recommendations to adjust maintenance policies or procedures to improve performance. The contractor shall implement Government-approved recommendations. The contractor shall establish an account on iPDM in order to post prepare and/or review ECPs submitted by program office representatives. The contractor shall state impacts to maintenance documentation and processes as part of the review and annotate efforts via monthly report CDRL TBD.

2.2.3.9 Planned Maintenance System (PMS) database

The contractor shall maintain the PMS database within ALICE. The PMS database shall include documents to support the Combat Systems, Command, Control, Communications, and Computer Readiness Assessment (C5RA) program, ILS certification, Integrated Maintenance Reviews (IMR) and Engineering Change kit assembly and submittal of documents to activities for inclusion into periodic fleet wide distribution programs. Support shall include the consolidation of known fleet issues, outstanding comments and review and update of the latest Force Revisions (FR) information on ALICE. Provide status of database updates via monthly report CDRL TBD.

2.2.4 Technical Data

The contractor shall deliver a validation completion report for each ACB/TI logistics package delivery (CDRL TBD).

2.2.4.1 Technical Data Authoring

The contractor shall prepare revisions or modifications to existing illustrations (line drawing or digital photos) used in legacy documentation, and for the preparation of new illustrations (line drawing or digital photos) for use in the System Technical Data. The contractor’s efforts shall be accomplished in accordance with the government approved Schedule, the USW systems Technical Data Management Plan (TDMP) and posted on ALICE or provided as GFI. The contractor shall utilize the government furnished ePDM system - for the management and maintenance of applicable legacy technical manuals. Utilizing the data and document management process, the contractor shall incorporate an approach to prepare data which can be reutilized in subsequent products to minimize efforts and maximize consistency of data being prepared. Document status via updated Schedule CDRL TBD.

2.2.4.2 Operator and operations Guidance Documentation

The contractor shall prepare or update General System Description and Consolidated Operations information that fully supports System Initialization, Software Load Procedures, Tactical Operations, and Functional Segment information and instructions necessary to support the operational aspects of the hardware and software baselines for all TI/ACB configurations. All prior data and documentation will be provided as GFI. The Operator Guidance Documentation shall, at a minimum:

· Describe System Software Load Procedures.

· Describe System Initialization Procedures including proper interface sequencing.

· Describe all control, indicator, and display formats available to support system, and equipment level operations.

· Describe all control, indicator, and display formats available to support system, and equipment level performance monitoring/fault detection/fault localization, reconfiguration and maintenance operations.

· Describe all operator-machine interface controls to support system, and equipment operations.

· Describe how to operate the system to meet mission tactical requirements (operator, supervisor and command).

· Describe how the system LAN operates and describe the LAN administration duties.

· Fault Detection, Fault Isolation, and Fault Localization, and remove and replace procedures.

· Maintenance instructions required to support system, functional segment, and equipment in terms of reconfiguration.

· Technical Data required to support System Resource Manager fault messages.

The contractor shall work with the DoD tactical development & doctrine group in exchanging information required to prepare employment guidance and Operations procedures. The contractor shall document all Capabilities and Limitations (Caps and Lims) of each TI/ACB. The capabilities shall show the capability of the system being installed compared to the system being removed. The limitations shall be based on the open SPRs/IRi listed in the software version description document. It is expected that these documents will require update for each TI/ACB. Deliver Caps/Lims document for each TI/ACB via CDRL TBD

2.2.4.3 Technical Data Validation/Verification Plan

The contractor shall update the baseline Validation and Verification (Val/Ver) Plan provided by the government addressing technical data being developed or modified for each TI/ACB or system baseline. Validation/Verification Plans shall include procedures for validation of data technically and functionally. The contractor shall conduct a functional and technical Val/Ver on the system Technical Data after it has been incorporated into the Supportability Functional Segment (SupFS) shell or at the Preliminary stage for non-SupFS capable systems. Upon completion of the Val/Ver, the Contractor shall prepare final TM, IETM, or SupFS content in accordance with the product development schedule. Update status via monthly report CDRL TBD, provide Val/Ver plan via CDRL TBD.

2.2.4.4 Software Version Description Document

The contractor shall post updated Software Version Description Documents (SVDDs) for USW systems in November of each business year, as required. These updates will include the most current list of open SPRs. All Pri 3 or higher SPRs shall include ‘workaround’ details showing the actions that can be taken at the organizational level to mitigate the impact of the SPR. These updates will be made available on the CSC Gateway upon approval by PEOIWS5 with a fleet message following the update. Update SVD provided via CDRL TBD.

2.2.5 Manpower & Personnel

The contractor shall review the configuration of the equipment for the new USW hardware and perform an analysis of the tasks required for active duty personnel to perform maintenance (preventive, corrective, troubleshooting), classify the tasks by the knowledge/skill area, and recommend personnel level when unique requirements are identified. Requirement for hazardous material and/or environmental impacts discovered while performing the task analysis shall be provided in the Manpower, Personnel and Training studies delivered as CDRL TBD.

The contractor shall perform Human Systems Integration (HSI) studies and deliver/revise plans delivered as CDRLTBD.

The contractor shall prepare Manpower, Personnel, and Training summaries that provide the necessary information to the Government who will establish classroom training, provide interim and initial training, and ensure manpower and personnel analysis requirements are met. The information contained within these reports shall identify the plan and schedule for establishing formal Navy Enlisted Code (NEC) awarding courses, providing interim training and initial training. Training summaries shall address the system's corrective and preventive maintenance tasks, operations tasks and Watch Condition supervisory tasks. Manpower estimates shall be provided for system operation, maintenance and supervisory tasks, and personnel skills required to perform the tasks shall be identified. Delivered as CDRL TBD.

The contractor shall perform manning level evaluations and studies. The contractor shall review the nature of the equipment and tasks being assigned and shall match the skill requirements to appropriate NAVY rated billet in accordance with the applicable Navy Training Systems Plan (NTSP) provided by as GFI.

The contractor shall procure and install Tactical Training Equipment (TTE) at FLEASWTRACENPAC and other NEC awarding training sites as directed in specific technical instruction documents. TTE shall support maintenance and or operations training documented in the NTSP and provide monthly status showing the course number, percentage complete and number of active duty personnel attending the course.

The contractor shall perform initial training for instructors and maintenance personnel in equipment familiarization support for troubleshooting, repair and scheduled maintenance requirements from ship delivery through sail away. During ship custody transfer, the Contractor shall provide familiarization and maintenance training to personnel in the proper maintenance USW systems to include proper alignments, diagnostics, intra- and intersystem checks, using applicable PMS cards, technical manuals, and other technical data. The contractor shall assist the logistics manager in updating the AN/SQQ-89 NTSP (at least) every even year to include all support activity requirements, new Course Identification Numbers (CINs), and updated pipeline diagrams. The contractor shall prepare, review and analyze logistics and training processes and procedures and make recommendations in terms of proposed changes that are consistent with the preparation of and maintenance of Interactive Course Ware (ICW), other training products and other logistics products. The contractor shall deliver recommendations in MS Word format.

The contractor shall conduct analysis and design activities based on MIL-PRF-29612B and MIL-HDBK- 29612B utilizing the Instructional Systems Development (ISD) model. Analysis and design products developed and delivered under this contract shall support the Advanced Distributed Learning (ADL) initiative's Sharable Content Object Reference Model (SCORM) for courseware development utilizing the Data Delivered Learning System (DDLS). In addition, all analysis and design requirements shall be assessed for Section 508 compliance as applicable. All training actions shall be prepared in accordance with the development Schedule provided as GFI. The contractor shall conduct Instructional Performance Requirements Analyses (IPRA) to identify training requirements supporting all categories of personnel including maintenance technicians, sensor operators, sonar supervisors, and fire control operators for both replacement and conversion training on systems. These analyses shall include the review and validation of the current training, identification of the target population, determination of training tasks, definition of learning objectives for the training tasks, and criticality and allocation of learning objectives that are appropriate for the delivery medium. IPRA data shall be incorporated into an Instructional Performance Requirements Report for courses applicable to the analyses.

The contractor shall conduct Instructional Media Analyses (IMA) to recommend to the government the most cost and training effective media for delivery of each learning objective and course of instruction identified. A media model shall be established to define the most appropriate use of the available technology to meet the specified learning objectives. A detailed media analysis shall be conducted to define the specific media requirements (e.g., screen captures, 3D animation, 2D stills, simulation, hands-on training, etc.) as well as the appropriate delivery method. The media shall be specific to meet the requirements of the training tasks, and the results shall be documented in an Instructional Media Requirements Report. IMA data shall be incorporated into an Instructional Media Analysis Report for courses applicable to the analyses.

The contractor shall conduct media design activities based on analyses results to identify overall courseware design strategies and requirements for each course of instruction. The Instructional Media Design Package (IMDP) shall include at a minimum, the mix of interactivity within a course; identification of where and how learning strategies are implemented; details for testing and evaluation of courseware effectiveness; and details of how files shall conform to SCORM metadata tagging criteria including a Sharable Content Object (SCO) schema. The contractor shall also include a prototype lesson to facilitate Government review and understanding of each of the courseware delivery media. Prototype lessons shall demonstrate all strategies identified in the IMDP and demonstrate interoperability within the specified Learning Management Systems (LMS) - DDLS. The media design results shall be documented in an Instructional Media Design Package (IMDP) for courses applicable to the analyses. Instructional Performance Requirements Report, Instructional Media Analysis Report, Instructional Media Design Package (IMDP), Instructional Aids and Instructional Media Packages delivered as CDRL TBD.

The contractor shall draft or maintain Training Conduct Support Documents (TCSD) for USW Acoustic Operator, System Maintenance, Sonar Supervisor, UWC Operator and other training. The training documents shall follow the course outlines and learning objectives as defined in their respective IPRA. The training documents for each course shall contain Lesson Plans, Trainee Guides, Tests, and Instructional Visual Aids. The Lesson Plans shall be developed using the government furnished Authoring Instructional Materials (AIM) Version 3.1 or current version software. The Trainee Guides shall be developed using best contractor format and contain the proper instruction sheets that will enhance the trainee's mastery of the knowledge and skills needed for the subject matter. The Tests may be developed in the contractor’s format and shall include title and lesson number; directions for taking the tests; test items; and answer sheets. The Instructional Aids may be developed in the contractor’s format and shall include slides, transparencies, or wall charts to support the proper conduct of training. The contractor shall prepare Instructional Media Packages (IMP) for PEO IWS5 USW systems Acoustic Operator, System Maintenance, Sonar Supervisor, UWC Operator, and other training. The IMP shall follow the strategies and requirements as defined in their respective IMDP. The IMP for each course shall contain the Computer Managed Instructional (CMI) audiovisual production treatments; lesson flows; Sharable Content Objects (SCO); and published lessons. The treatments shall be developed using best contractor format and contain lesson content; supporting digital media files names; and identify how the media will be used. The lesson flows depicting lesson sequencing and branching will be developed and stored in the government furnished SupFS Learning Management System (LMS). The lesson SCO will be authored using the government furnished SupFS Data Delivered Learning System (DDLS) and stored in the Content Managed System (CMS). The published lessons will be developed and stored in the LMS. The contractor shall draft a Validation and Verification (Val/Ver) Plan addressing each training requirement being developed or modified. Val/Ver Plans shall include procedures for validation of data technically and functionally. The contractor shall conduct a functional and technical Val/Ver on the USW system Training Data after it has been incorporated. Val/Ver Plan is due 3 months prior to event CDRL TBD.

2.2.6.2 Training Conduct

The contractor shall conduct training events for NAVSEA equipment and systems. Training shall consist of train-the-trainer and/or maintenance personnel training. The contractor shall submit a post training report identifying number and rates of personnel trained, location of training, and lessons learned no later than 10 business days after the training is complete. The contractor shall provide qualified personnel to conduct crew familiarization training during and at completion of each installation.

The contractor shall provide support to the FLEASWTRACEN in San Diego, CA. The contractor shall interface with fleet representatives in scheduling training for active duty personnel. The contractor shall modify course material based on fleet feedback. Additionally, the contractor shall relay all issues related to FLEASWTRACEN training equipment performance to the Logistics Manager and assist FLEASWTRACEN in ensuring equipment is maintained in working order.

The contractor shall provide support to the Combined Integrated Air and Missile Defense (IAMD) and Integrated Missile Defense (IAMD) Trainer (CIAT) through consult and training conduct. The contractor shall identify existing ACB technical data and Weapons and Tactics Instruction (WTI) course materials for reutilization within the CIAT course of instruction. The contractor shall perform maintenance of integrated and adjunct systems at other training sites as required.

The contractor shall support fleet training events including Initial Shipboard Familiarization (ISF), Fleet Synthetic Training (FST), Mobile Training Team (MTT), Advanced Warfare Training (AWT), WTI, ASW Qualification (ASWQ), ASW Evaluator (ASWE), team training events and others. The contractor shall provide up to eight full time personnel in the San Diego Area to conduct training with the experience noted in the Personnel Labor Category ‘Training Specialist, Mid’ or ‘Network Engineer’

2.2.7 Supply Support

The contractor shall provide supply support including provisioning, spares identification and management, allowance and equipage documentation preparation and maintenance, Navy supply system requirements support, outfitting material and documentation support, and similar supply support related requirements. All supply support actions will be accomplished in accordance with the product development schedule and status provided monthly via CDRL TBD.

The contractor shall review USW equipment provisioning and supply support data. The contractor shall monitor the Federal Logistics Information System (FLIS) and review data established by the Navy Supply System in response to the EDFP and PTD submitted by the Technical Support Activity (TSA).