19_SAMM_Support_Sample_Task_Order_1.docx

Attachment 19 N32205-18-R-1000

PERFORMANCE WORK STATEMENT

SAMM System Support

Contract: XXXXX-XX-X-XXXX Task Order Number: SAMPLE 1

TPOC: X Type: Firm Fixed Price Period of Performance: Upon award for 1 year

1. SCOPE OF WORK:

1.1. Maintain the Engineering Maintenance Management Systems (SAMM, PENG, VTL, SEAS, OAS, FAS, VAS, Logbook, Ships Log, iDEXTER, eConsole, Ship Inspection, OCI Web Tracker, SMS, RASP). The Contractor shall provide non-personal engineering, technical, and system implementation and improvement services in the performance of investigative and design efforts relating to material readiness, preventive and predictive maintenance, and condition monitoring programs. Maintain the existing MSC SAMM, PENG, Work Package and Life Cycle planning (LCP) system installed onboard MSC vessels and used in support of MSC vessels by ashore personnel. Support includes responding to help calls, collecting system modification suggestions, training users, repairing and replacing data collectors, SAMM software requirements and design analysis, software testing, system deployment, management and maintaining shipboard and shore side SAMM systems. The contractor shall maintain data and configuration to interface with MSC/NAVY's other business systems to include CMLS ashore, RMAIS, NAVY PMS, and SHIPCLIP afloat. The Contractor shall provide support for the engineering maintenance management systems SAMM Preventive Maintenance compliance reporting, and analysis training of MSC personnel on the engineering management systems. The contractor shall provide the required support at field offices, MSC Norfolk, MSC Area Commands, on MSC vessels, and at the contractor’s facility. The contractor shall support and maintain American Bureau of Shipping (ABS) submittal and approval fees, ABS planned maintenance and condition monitoring requirements to comply with ABS standards. The contractor shall support and maintain the system related hardware including repair and calibration. The Contractor shall provide the MSC Engineering Directorate (N7) administrative support, data management support, and technical support for the engineering library including the MSC Safety Management System (SMS) and the MSC Virtual Technical Library system (VTL). The Contractor shall provide technical management, administrative, technical services, and troubleshooting of equipment in connection with test and inspections onboard MSC ships. Obtain test documentation, provide test equipment/data collectors and research/retrieve applicable technical documentation

1.2. Vessel Support: This task is estimated but not limited to support the following MSC Operated Ships

2. SPECIFIC TASKS:

2.1. Specific Task Management Support.

2.1.1. The requirements of this section are applicable to the management of all specific tasks.

2.1.2. Maintenance Systems Support. The Contractor shall provide Specific Task Management Support for the MSC Engineering Maintenance Management Systems. The Contractor shall perform the following:

2.1.2.1. Oversight and in depth analysis of the technical, schedule, and resources.

2.1.2.2. Collect, analyze, and document metrics to measure performance and identify areas requiring greater oversight or improvements in processes.

2.1.2.3. Attend meetings and conferences as requested by the COR.

2.1.2.4. Prepare and present system and application related briefings.

2.1.3. Project Management Plan (PMP): For all projects the Contractor shall provide a PMP. (i.e. SAMM Development for USNS Big Horn). The PMP should include all milestones, timeframes, resources (people), dependencies, deployment, communication matrix and Quality Assurance Plan (QAP). The QAP shall consist of procedures, metrics and remedial actions. The milestones in the PMP will be summarized in a baseline Gantt chart. All schedule changes shall be measured against the baseline Gantt chart. CDRL 1423-21 Project Management Plan (PMP)

2.1.3.1. The Contractor shall submit a PMP within ten (10) working days of initiation of a project.

2.1.3.2. The Government will review the PMP and provide comments within five (5) working days.

2.1.3.3. The Contractor shall incorporate/address the Governments comments and submit the final PMP within five (5) working days.

2.1.4. Quality Assurance Plan:

2.1.4.1. The Contractor shall submit a preliminary Quality Assurance Plan (QAP) for all specific tasks that describes the processes which will be in place to ensure the final product is free of errors. The QAP shall describe how the Contractor will ensure that the work performed will meet the requirements of the task(s). The QAP must address how the Contractor intends to implement quality control, quality assurance, and continuous process improvement. The QAP shall include as a minimum: Quality Metrics, Quality Checklist(s) and, Process Improvement Plan; Quality Baseline. The Contractor shall retain documentation generated as a result of the QAP to facilitate audits by the COR.

2.1.5. Process Management Plan: The process document shall include identification of the process lead, all additional roles, the detailed process activities to include quality assurance and sustainment. (i.e. helpdesk support process).

2.1.6. Weekly Conference Calls. The Contractor shall schedule Weekly Meetings with the COR. The COR can elect to conduct meetings in person or electronically and the frequency. The meeting shall include subcontractors as needed, discuss work conducted since the last meeting and expected work to be conducted in the next reporting period, and any areas of concern. The Contractor shall provide meeting minutes as defined in CDRL 1423-11 Meeting Minutes.

2.1.7. Trip Reports. The Contractor shall provide Trip Reports for all travel (shipcheck, installation, and training, etc). The Trip Reports shall be in the format as defined in CDRL 1423-19 Trip Report.

2.1.8. Monthly Report. The Contractor shall provide a Monthly Report that outlines the progress for each of the Specific Tasks. CDRL 1423-15 Monthly Report

2.1.9. Invoice Reporting. Reports shall be created to submit with the invoice packages and include: ODC details, Option Allocations for invoicing, SF 1035, Sub-Contractor Financial reports. CDRL 1423-33 Invoice Report

2.1.10. Monthly Management Meeting. The Contractor shall schedule Monthly Meetings with the COR in person to discuss the Monthly Report. At minimum, Program Manager(s) and Assistant Program Manager(s) shall attend these meetings. Contractor shall provide meeting minutes as defined in CDRL 1423-11 Meeting Minutes.

2.1.11. Action Item Tracking. The Contractor shall maintain a consolidated list of actions items, with the exception of help calls or feedback, and shall enter all action items into the SAMM Task Manager and record the task identification number in the action items tracking list. When an action item is the responsibility of the government, the Contractor shall submit a task request via the SAMM Task Manager module. CDRL 1423-35 Action Item Report

2.2. Helpdesk Support:

2.2.1. The Contractor shall coordinate with the MSC helpdesk to receive, triage, track and document progress of all help calls within the MSC helpdesk software in support of the MSC Engineering systems both ashore and shipboard. The Contractor shall indicate which help calls required a ship visit and which calls did not require a ship visit.

2.2.2. The Contractor shall provide on-call helpdesk support to assess the urgency of help calls that are received after normal business hours. The Contractor shall provide immediate direction to the submitter for all cases where the problem affects day to day operations and as directed by the COR.

2.2.3. The Contractor shall triage each help call and respond to the submitter within twenty-four (24) hours with an initial plan to correct the help call.

2.2.4. The Contractor shall track to conclusion all helpdesk calls. Conclusion shall occur within 30 calendar days of receipt, and shall include confirmation that the problem defined in the help call was corrected, with the exception to help calls containing recommendations for software updates.

2.2.5. The Contractor shall provide a status report each week for all open help calls. The Contractor shall provide an explanation for all help calls open for more than 29 days, the plan for resolution, an estimated date of closure, and how it will be addressed as part of their quality assurance process. CDRL 1423-37 Help Call Weekly Report

2.2.6. The Contractor shall review all assigned help calls to determine if the requirement or issue reported requires updating of the SAMM software to resolve. The Contractor shall investigate record and track to completion all software change request reported via the MSC Global Service Desk in the Software Update Tracker. CDRL 1423-12 Software Update Tracker Report

2.2.7. Approximately 1219 help calls are received each year.

2.3. Training Support:

2.3.1. Training Materials, Documentation and SAMM Learning Management System Support

2.3.1.1. The Contractor shall host and maintain an online course registration and attendee record management solution. The Contractor shall maintain a log of all training events to include at minimum the date of the training, the instructor name, the course contents, the students registered, the students in attendance, and student contact information. Training events for each month shall be incorporated into a monthly training report provided to the COR. CDRL 1423-18 Training Documentation

2.3.1.2. The Contractor shall develop and maintain materials to conduct training, to include training simulation equipment, quick reference guides, help manuals, instructor training guides, lesson plans, syllabi, handouts, student assessments and student course reviews. CDRL 1423-18 Training Documentation

2.3.1.3. For each software update and as directed by the COR, the Contractor shall create training material and/or update existing training material for all MSC Maintenance Management Systems as required in CDRL 1423-18 Training Documentation.

2.3.1.4. The Contractor shall create and maintain interactive training content for deployment via the SAMM training module for all SAMM Modules. All interactive training shall be SCORM compliant.

2.3.1.5. The Contractor shall provide web hosted collaboration and training services to ensure efficient use of resources to train shipboard and shore side personnel located remotely as directed by the COR.

2.3.2. Contractor Hosted Classroom Training.

2.3.2.1. The Contractor shall maintain a training facility to host training sessions and training hardware for up to 40 attendees. Each training attendee shall be provided a training workstation during training classes.

2.3.2.2. For estimating purposes, the Contractor shall plan on providing 500 total classroom training hours per year for the below training classes in the Norfolk, VA area:

2.3.2.2.1. Afloat SAMM Training for Senior Engineers

2.3.2.2.2. Afloat SAMM Training for Junior Engineers

2.3.2.2.3. Shore side SAMM & PENG Training

2.3.2.2.4. Afloat SAMM Training for Deck Officers

2.3.2.2.5. Engineering Division Training

2.3.2.3. The Contractor shall provide updated CMEO training materials within 30 calendar days of MSC’s acceptance of a SAMM software update.

2.3.3. On-site Training at Government Facilities

2.3.3.1. The Contractor shall provide training support, including training materials and hardware, for training at MSC office locations around the world. For estimating purposes, the Contractor shall plan on providing classroom style training classes each year on site at MSC facilities around the world. Reference Table 2. Estimated Travel Table.

2.3.3.2. The content of the training will be within the scope of the training synopsis. The specifics of the training class will be directed by COR. (See Attachment 07)

2.3.4. On-site Training at MSC Contractor Facilities

2.3.4.1. The Contractor shall provide training materials and hardware to support up to 15 students per training session hosted at the facilities of another MSC contractor. Close to 50% of MSC's government owned vessels are contractor operated. The contract operator's shore side staff requires training and MSC sometimes deems it more cost effective to request the trainers to travel to provide training at another contractor's facility. For estimating purposes, the Contractor shall plan on providing training sessions at the other MSC contractor’s facilities when directed by the COR. Reference Table 2. Estimated Travel Table.

2.3.4.2. The content of the training will be within the scope of the training synopsis. The specific training requirements for each session shall be as directed by the COR.

2.3.5. On-site Training at Repair Facilities in support of MSC Ship Availabilities

2.3.5.1. The Contractor shall provide materials to support the training of MSC ship availability management personnel after the installation of the SAMM and PENG Software at the ship repair facility. For estimating purposes, the Contractor shall plan on providing web based training support for approximately 75 availabilities each year.

2.3.5.2. The content of the training will be within the scope of the training synopsis. The specific training requirements for each session shall be as directed by the COR.

2.3.6. Shipboard crew training

2.3.6.1. As part of each ship visit, the Contractor personnel shall be prepared to provide training and materials to shipboard personnel in all aspects of the SAMM system.

2.4. SAMM System Feedback Support:

2.4.1. Data Management. The Contractor shall manage the Shipboard Automated Maintenance Management System (SAMM) data which is installed onboard MSC vessels and ashore installations used in support of MSC vessels by ashore personnel. This data management will be performed in accordance with the latest version of Attachment 06. The data management shall consist of the following:

2.4.1.1. Performing initial SAMM feedback request reviews to determine the course of action. The Contractor shall submit all software or hardware issues as a help call to the MSC Global Service Desk.

2.4.1.2. Conducting research for SAMM feedback using MSC policy and Reliability Centered Maintenance principles to formulate a feedback proposal. The Contractor shall provide a feedback proposal to the COR within 30 calendar days of the feedback origination date for MSC approval.

2.4.1.3. Submitting feedback proposals to MSC for approval. CDRL 1423- 22 SAMM Feedback Proposal. Any changes that cannot be executed via SAMM (i.e. SQL scripts) must have an approved feedback defining the method of execution. As part of the feedback proposal, the Contractor shall incorporate any new or updated technical documents in to SAMM and as directed by the COR.

2.4.1.4. Notifying ships of upcoming MSC approved maintenance changes prior to implementation.

2.4.1.5. Implementing MSC approved maintenance changes using the SAMM system.

2.4.1.6. Feedback Turnaround Time. An estimated 7484 Feedbacks will be entered per year based on historical data. The Contractor is expected to close out/implement, all feedback items within sixty (60) days from the feedback system date as recorded in the SAMM database. CDRL 1423- 38 SAMM Feedback Weekly Report.

2.4.2. Periodic Data Maintenance Requirements:

2.4.2.1. Hierarchical Structure Code (HSC) Review. The Contractor shall provide engineering support for the reconciliation of the HSC every six months and as directed by the COR. The Contractor shall provide services for HSC review and alignment to Configuration & Logistics Information Program (CLIP). The equipment HSC’s in SAMM and CLIP must be linked in order for SAMM to pull in Allowance Part List (APL) information for the equipment manufacturer and model. The Contractor shall submit a feedback to recommend any configuration and/or maintenance changes. CDRL1423-29 SAMM Feedback Submittal

2.4.2.2. NAVY Planned Maintenance System (PMS) Maintenance Requirement Card (MRC) Updates. The Contractor will perform an update to the Navy PMS MRC maintenance embedded in SAMM every six months and as directed by the COR. Access to the online Navy PMS system can be gained by contacting the COR. The Contractor shall submit a feedback to recommend any configuration and/or maintenance changes. CDRL1423-29 SAMM Feedback Submittal

2.4.2.3. Configuration Management. The Contractor shall review configuration change reports from MSC or the MSC Logistics Contractor to identify new or modified equipment by make, model and APL every six months and as directed by the COR. The Contractor shall confirm each entry for correctness and determine the extent of the impact across the ship's class and across the fleet and make corrections to each applicable vessel. The Contractor shall submit a feedback to recommend any configuration and/or maintenance changes. CDRL1423-29 SAMM Feedback Submittal

2.4.2.4. Equipment Technical Manual Review. In conjunction with the requirements of section 3.10, the Contractor shall provide engineering support for the reconciliation of SAMM equipment to the latest Technical Manuals every six months and as directed by the COR. The Contractor shall submit a feedback to recommend any configuration and/or maintenance changes. CDRL1423-29 SAMM Feedback Submittal

2.4.2.5. Review of Equipment relationships to Engineering, Logistics and Operations data elements. The Contractor shall identify areas where data elements require updating and submit a SAMM feedback proposal to correct data relationships every six months and as directed by COR. (i.e. SAMM Equipment to Logbook gauge relationships) CDRL1423-29 SAMM Feedback Submittal

2.5. Engineering Ashore Support:

2.5.1. Port Engineering and Work Package Development Support.

2.5.1.1. The Contractor shall furnish the hardware necessary for the temporary use of the PENG software during ship availabilities.

2.5.1.2. Upon receipt of the ship Availability schedule from the government the Contractor shall open a help call with the MSC Global Service Desk 30 calendar days prior to the start of the availability to initiate the availability support activities.

2.5.1.3. The Contractor shall provide availability planning support for the SAMM program for all MSC offices worldwide. This support requires the entry of work package data, updating of user rights, addition of new users, port engineer training and the updating/management of reference data elements. The Contractor shall install the SAMM software onto the data collection hardware and configure it appropriately for the Port Engineers to use at each ship availability. The Contractor shall deliver the data collection hardware to the port engineer. The delivery of the data collection hardware and training shall be provided no later than seven (7) working days prior to the start of the availability. Reference Table 1. Data Collection Hardware Table. CDRL 1423- 39 Port Engineer Availability Support Monthly Report.

2.5.1.4. During the execution of the availability, the Contractor shall provide on-site or remote support, to include data maintenance, training or troubleshooting. Reference Table 2. Estimated Travel Table.

2.5.1.5. The Contractor shall provide post availability support to include retrieving the data collector, providing support for categorizing, and documenting the completion of maintenance.

2.5.1.6. The Contractor shall provide data maintenance support for Life Cycle Plan (LCP) definition and management at all MSC offices worldwide. This support requires updating and management of reference data elements, voyage repair requests, transportation alterations, and planned maintenance requiring industrial assistance. Reference Table 2. Estimated Travel Table.

2.5.1.7. The Contractor shall provide support for planned maintenance requiring industrial assistance maintenance parts definition for all MSC vessels. This support requires the entry and updating of parts information associated to SAMM maintenance actions.

2.5.2. Monthly Life Cycle Management Effectiveness Review.

2.5.2.1. The Contractor shall review each vessel’s Availability module usage for the prior month. The Contractor shall ensure the Availabilities module usage, as determined by the quality of the data compared to the latest Maintenance, Repair and Training (MRT) schedule from the government, is accurate and complete. The Contractor shall report and correct data deficiencies as directed by the COR. CDRL 1423-4 Data Review and Analysis Report

2.5.2.2. The Contractor shall review the PENG module usage for availabilities completed during the prior month. The Contractor shall ensure the PENG module usage, as determined by the quality of the data, is sufficient to ensure proper maintenance and repair documentation and analysis. The Contractor shall report and correct data deficiencies as directed by the COR. CDRL 1423-4 Data Review and Analysis Report

2.5.2.3. The Contractor shall review the Availabilities module data for the prior month, for items that should have been related to Standard Work Items, VRR, PMIA, or T-Alt records. The Contractor shall report and correct data deficiencies as directed by the COR. CDRL 1423-4 Data Review and Analysis Report

2.5.2.4. Review the Library items module data for the prior month to identify library items where the item execution history shows the actual cost was much higher than awarded cost. The Contractor shall analyze the work item data to determine the cause of the cost difference. The Contractor shall report and provide recommendations for improvements. CDRL 1423-4 Data Review and Analysis Report

2.5.2.5. The Contractor shall perform a detailed analysis of the SAMM Ashore M&R data to include each module (see attachment 02 SAMM System Description) for the prior month and deliver a report highlighting any issues in an executive summary. The contractor’s analysis should ensure that the SAMM Ashore M&R data is of sufficient quality for proper planning, budgeting and analysis. The Contractor shall report and correct data deficiencies as directed by the COR. CDRL 1423-4 Data Review and Analysis Report

2.5.2.6. The Contractor shall review the Ashore M&R data relationships to determine other data correlations that can be used to improve MSC’s Ashore M&R processes.

2.5.2.7. The database SQL queries used to create monthly Life Cycle Management Effectiveness Review reports shall be posted to the MSC Virtual Tech Library along with the monthly reports.

2.5.3. Compliance and Sustainment Reporting and Review.

2.5.3.1. By the end of each month, the Contractor shall perform a detailed analysis of the SAMM maintenance, condition monitoring, and repair system effectiveness for the prior month and deliver a report highlighting any issues in an executive summary. CDRL 1423-4 Data Review and Analysis Report

2.5.3.1.1. Review Condition Monitoring System Compliance and actions taken or not taken in response to Condition Monitoring Recommendation recorded in machinery history and repair records. Ensure for every recommendation that the recommendations validity has been verified and that the actions taken based on the recommendations have been recorded properly into the SAMM machinery history records. Report instances where condition monitoring compliance or overall condition monitoring effectiveness could be improved. Report instances where the condition monitoring has been effective. CDRL 1423-49 Compliance and Completion Report

2.5.3.1.2. Review shipboard planned maintenance compliance and effectiveness. If maintenance was deferred for reason of data collector error or feedback entered, ensure that the ship’s crew actually entered the help call or the feedback necessary for the change to happen. If maintenance is repeatedly deferred, investigate reasons for repetitive deferrals and propose possible solutions to make maintenance more effective. Use RCM principals defined in the Reliability Centered Maintenance Handbook (Attachment 09). The Contractor shall submit Feedback for maintenance improvements via SAMM. CDRL 1423-49 Compliance and Completion Report and CDRL 1423-29 Feedback Submittal

2.5.3.1.3. The Contractor shall conduct a machinery reliability analysis of PM compliance, existing maintenance plans, and machinery repair records and provide maintenance optimization recommendations. The Contractor shall ensure that all SAMM repair records are associated to the proper equipment. The Contractor shall use RCM principals defined in the Reliability Centered Maintenance Handbook (Attachment 09). The Contractor shall submit feedback for maintenance improvements via SAMM. CDRL 1423-29 Feedback Submittal and CDRL 1423-50 VRR Usage Report

2.5.3.1.4. Review the number and quality of Feedback entered into the SAMM system by each ship’s crew and report vessels that have not submitted feedback in the last three months. Based on review of the quality of Feedback items submitted, the Contractor shall suggest ways to improve Feedback process efficiency.

2.5.3.1.5. Review official CASREP historical data. Upon receipt of CASREP data from the government, the Contractor shall ensure for every CASREP a VRR has been properly entered into SAMM with the CASREPID and C-Rating. The Contractor shall correct SAMM VRR data as directed by the COR. The Contractor shall provide a report containing all discrepancies found.

2.5.3.1.6. The Contractor shall calculate the Materiel Readiness Quotient for MSC vessels, maintain the model and assess its accuracy using various statistical analysis methods, and provide recommendations for improving the model’s ability to reflect the current and future materiel condition of MSC vessels, as part of a continuous improvement process.

2.5.3.1.7. The database SQL queries used to create monthly PM Compliance and Analysis reports shall be posted to the MSC Virtual Tech Library along with the monthly reports.

2.5.4. Operational Ashore Systems Support.

2.5.4.1. American Bureau of Shipping (ABS) – MSC voluntarily enrolls all ABS classed vessels into the ABS Surveys Based on Preventative Maintenance Techniques for Planned Maintenance (PM) and Condition Monitoring (CM) in accordance with ABS Rules Part 7, Appendix 14 and all future versions. (Attachment 08). The Contractor shall provide the following support:

2.5.4.1.1. For estimation purposes, the Contractor shall plan that fourteen (14) vessels per year will be enrolled into ABS’s program for surveys based on PM and CM. CDRL 1423-2 ABS Initial CM Survey Package and CDRL 1423-3 ABS Initial PM Survey Package.

2.5.4.1.2. The Contractor shall define and maintain vibration data points, test conditions and parameters using an ABS Recognized Condition Monitoring Company.

2.5.4.1.3. The Contractor shall maintain the data exchange between ABS and SAMM to include equipment nomenclature and other data elements.

2.5.4.1.4. The Contractor shall provide a Condition Monitoring (CM) report to all MSC vessels annually. The report shall be provided to the vessel 30 days prior to the start date of the vessel’s Annual Machinery Survey as found in ABS’s Safenet software system. CDRL 1423-1 ABS Annual CM Report CDRL 1423-40 ABS CM submittal report. The government will provide the Contractor access to ABS’s Safenet software for MSC vessels.

2.5.5. Engineering Management Support Data Reporting. The Contractor shall create reports to assist with analysis of all SAMM data. As directed by the COR, the Contractor shall incorporate analysis reports into the SAMM Reports module. The Contractor shall make recommendations for data collection improvements for efficiency and accuracy of metric definition. CDRL 1423-4 Data Review and Analysis Report

2.5.5.1. The Contractor shall assist with defining SQL queries necessary for exporting data, metric definition, and metric visualization. The Contractor shall assist with transitioning this data into MSC’s Enterprise Data Warehouse (EDW) and Oracle Business Intelligence tools with the applicable MSC support contractor(s).

2.5.6. Data Acquisition Systems. The Contractor will support new and existing interfaces for eConsole, iDEXTER, or other sensor data acquisition systems and output to SAMM. The Contractor will provide technical information, analysis support and general assistance to aid in the installation, updating, training and troubleshooting of data acquisition systems. The Contractor will provide machinery plant diagnostic support and analysis of the sensor data in SAMM. Reference Table 2. Estimated Travel Table.

2.5.7. Energy Management Support. The Contractor will provide on-site support at shore side operational offices for the SAMM Energy Conservation dashboard and RASP system. The Contractor will respond to help calls, collect system modification suggestions, train users, and assist with data entry. The Contractor shall provide support for data collected in the electronic log keeping system, including Navy Energy Usage Reporting System data. The Contractor will provide data analysis support to assist MSC Operations and Marine Transportation Specialists with scheduling an energy efficient route for vessels. The Contractor will provide technical information and assistance to aid in the successful testing of system modifications, software installation, troubleshooting and/or updating of the RASP system. This work requires personnel with a Secret Clearance. Reference Table 2. Estimated Travel Table.

2.5.8. Ship Inspection Program Support. The Contractor shall provide support for the (SMART, OCI, Vessel Self-Assessment (VSA), and Port Engineer Vessel Inspection (PEVI)) inspection programs including database extraction, inspection team software support, and data collection hardware. The Contractor shall provide the hardware necessary for the temporary use of the Ship Inspection software during ship inspections (SMART, OCI, Vessel Self-Assessment (VSA), and Port Engineer Vessel Inspection (PEVI)). The Contractor will support the transfer of inspection deficiency records into SAMM. The Contractor shall assist with generation of a monthly report containing status of all inspection deficiencies recorded in SAMM. Reference Table 1. Data Collection Hardware Table.

2.5.9. RITEMOV Support

2.5.9.1. The Contractor shall support the conversion of test plan memo documents as SAMM maintenance actions.

2.5.9.1.1. Each individual data element of the test memo needs to be associated with the corresponding SAMM equipment(s) that it pertains to. For example, if a test memo has 4 engines worth of data in the word document, then this test memo needs to be split up so that the data for each engine is stored against each engine individually.

2.5.9.1.2. The test memo segment assigned to equipment shall represent a Task Code in SAMM and shall be written such that it can be executed alone or together with other inspection related Task Codes. One or more Task Codes in SAMM will map to the test plan memo that exists in the MS Word and MS Excel Files.

2.5.9.1.3. Each Task Code in SAMM shall be part of the SAMM maintenance plan associated to the equipment in the Master Maintenance Library.

2.5.9.1.4. The individual data elements of the executed Task Code/Test Memo need to be stored individually with data input entry and alarm limits defined in the database for each parameter.

2.5.9.1.5. The Contractor shall associate one or more Task Code/Test Memos to a test plan group. Test plan groups shall be associated to execution types.

2.5.9.1.6. The Contractor shall associate the execution type(s) (i.e. SMART, OCI, Vessel Self-Assessment (VSA), Port Engineer Vessel Inspection (PEVI), Periodic Safety Test Procedure (PSTP), ABS Inspection, Coast Guard Inspection) to each Task Code/Test Memo segment that is converted into SAMM.

2.5.9.1.7. The data sheet for engine performance analysis shall be associated to the SAMM combustion analysis data collection maintenance action (MCODE 0660).

2.5.9.1.8. The Contractor shall review the maintenance plans for each equipment including shipboard maintenance, industrial maintenance, regulatory body requirements, SMART, OCI, VSA, and PEVI to ensure like inspection/maintenance requirements utilize the same procedure. The Contractor shall make recommendations and implement data changes as directed by the COR.

2.5.9.1.9. The Contractor shall submit a SAMM Feedback for the implementation of all test plans and Task Code/Test Memos. CDRL 1423- 29 SAMM Feedback Submittal

2.5.9.1.10. The Contractor shall deliver all SQL database queries to the COR that they used to input data into SAMM. CDRL 1423-4 Data Review and Analysis Report

2.5.9.2. The Contractor shall provide support for the distribution of test plans to the vessels via ESTA six months prior to each SMART inspection, at the start of each VSA, and as directed by the COR.

2.5.9.3. The Contractor shall provide training and support to assist with the transition of business processes related to inspection items.

2.6. Data Collection Hardware and Software Support.

2.6.1. Upon award, the government will provide the latest Government Furnished Equipment Document (Attachment 25).

2.6.2. The Contractor shall provide for calibration, repair, and maintenance of all hardware. The Contractor shall ensure that all data collectors supplied to MSC vessels are replaced and returned for calibration prior to the re-calibration due date. The calibrated unit shall be sent to the ship to arrive at the ship no earlier than 45 days and no later than 15 days prior to the calibration expiration date of the unit being replaced. CDRL 1423- 20 Hardware and Software Maintenance and Calibration Log

2.6.3. The Contractor shall provide support and technical assistance to include replacing, installation, updates, testing, and troubleshooting for all hardware and SAMM System software. All hardware replacements shall be compatible with SAMM and provide equal or better performance in the areas reliability and maintainability than the current hardware. No hardware shall be replaced without the technical approval of the COR.

2.6.4. The Contractor shall maintain a Hardware and Software Maintenance History Log for all hardware and software. CDRL 1423- 20 Hardware and Software Maintenance and Calibration Log

2.6.5. The Contractor shall provide a maintenance pool of hardware and software to quickly respond to hardware or software issues. The below table is provided for estimation purposes and includes the hardware that the Contractor may be required to provide for the sustainment of the maintenance pool during one (1) year of support. For a six month bidding period, the Contractor should approximate half of the yearly requirements stated below.

2.6.6. The Contractor shall maintain an awareness of supplier plans for supporting the MSC data collection hardware and when appropriate perform a sustainability review. The technical approach to the review shall be approved by the COR. The results and recommendations of the review shall be presented to the COR.

Table 1. Data Collection Hardware Table.

2.7. Condition Monitoring Support:

2.7.1. The Contractor shall develop, sustain, and analyze the condition based monitoring technologies integrated into the SAMM System. Condition based monitoring technologies currently integrated into SAMM include Oil Analysis, Vibration Analysis, Diesel Engine Combustion Analysis, Water Chemistry Analysis (SEAS-WCA), and Fuel Oil Analysis (SEAS-FAS). All analyst comments and recommendations shall be saved in SAMM.

2.7.2. Fuel and Lube Oil Analysis. The Contractor shall work with the ships and the ashore analysis team to ensure that data such as Sample Point Identification (SPID) numbers and equipment nomenclature are correctly identified to the machinery to be sampled by the shipboard engineering crews. The Contractor shall monitor data transfer from the lab to the ashore database and from the ashore database to the ships, identify issues and correct problems. An Oil Data Analysis Report shall be submitted monthly. CDRL 1423-5 Data Validation Report – CM Oil Analysis Furthermore, the Contractor shall:

2.7.2.1. Update and deliver electronic equipment registration files to the current oil analysis lab.

2.7.2.2. The Contactor shall review data transfer daily between the lab and the ashore database to identify issues and correct problems. The daily review may identify issues in the file transfer or file processing.

2.7.2.3. Work with contracted oil analysis labs to troubleshoot sample delivery, tracking and analysis.

2.7.2.4. Review all oil sample testing, test slate completion, laboratory sample analysis, ferrographic report ordering and content. Upon receipt of a ferrography analysis report, the Contractor shall associate the report with the test result in SAMM. CDRL 1423-34 Ferrography Report

2.7.2.5. Analyze all oil test results from the laboratory reports for the purpose of determining oil replacement or corrective maintenance. Prepare analyst recommendations to vessels and supporting commands within two business days of receiving the oil test results from the laboratory. The messages are released by MSC officials. CDRL 1423-41 Oil Analyst Results summary Report.

2.7.2.6. Review oil analysis test slates to identify where test slates can be combined. Review oil analysis data results across the fleet to identify where equipment groupings can be established to facilitate creation of test variable alarms. Propose changes to test variable alarm limits to improve analysis.

2.7.2.7. Provide support for the data maintenance, oil analysis, message preparation, reporting and secure file transfer for the Shipboard Engineering Analysis System - Oil Analysis System (SEAS –OAS).

2.7.2.8. Evaluate SEAS-OAS and propose software upgrades required to improve its efficiency.

2.7.2.9. Provide support for the oil analysis expert system maintenance to reduce man-hour requirements for oil analysis.

2.7.2.10. Review results of shipboard lube oil testing conducted by Ship’s Force to ensure compliance with MSC shipboard lube oil testing requirements.

2.7.2.11. For estimation purposes, assume approximately 900 fuel oil samples require analysis per year based on historical data.

2.7.2.12. For estimation purposes, assume approximately 38,000 lube oil samples require analysis per year based on historical data.

2.7.2.13. The below chart displays the approximate number of lube oil samples received per year by repair priority based on historical data.

2.7.3. Vibration Analysis. The Contractor shall use the MSC Ashore SEAS/Vibration Analysis Software (VAS) tools to allow the analysis of vibration monitoring data and to accurately predict machinery failures. Using an ABS Recognized Condition Monitoring Company, the Contractor shall review recommendations made by the shipboard Equipment Automated Diagnostic System (EADS) and provide recommendations on the condition of the machine or the accuracy of the data collected. A Vibration Data Analysis Status Report shall be submitted monthly. CDRL 1423-7 Data Validation Report – CM Vibration Analysis Furthermore, the Contractor shall:

2.7.3.1. During a review of the shipboard vibration data, if it is determined the shipboard EADS did not provide an analysis of the data then the Contractor shall run the shore side EADS to perform manual review. The Contractor shall also troubleshoot as to why the shipboard EADS is no longer providing analysis.

2.7.3.2. Conduct a manual review and validation of all important and mandatory shipboard EADS fault severities and communicate results of the review. Provide the manual analysis review results to the affected ship’s Chief Engineer, Master, Port Engineer, Program Manager, Life Cycle Manager, and the COR within three (3) business days. CDRL 1423-43 EADS Fault Severity Report.

2.7.3.3. Conduct a manual review and validation of all desirable and noteworthy shipboard EADS fault severities and communicate results of the review. Also review those results where the shipboard EADS recommendation states “a manual review of spectra warranted.” Provide the manual analysis review results to the affected ship’s Chief Engineer, Master, Port Engineer, Program Manager, Life Cycle Manager, and the COR within three (10) business days. CDRL 1423-43 EADS Fault Severity Report.

2.7.3.4. Requests from MSC shipboard personnel that require additional analysis shall be forwarded to the COR for concurrence prior to beginning the analysis. After concurrence with the COR the Contractor shall review the requested EADS test results and vibration spectra within five (5) business days. The Contractor shall communicate the results of the review to the affected ship’s Chief Engineer, Master, Port Engineer, the Program Manager, Life Cycle Manager, and the COR.

2.7.3.5. The Contractor shall maintain the data relationships for the System Average Data, Machinery IDs (MIDs), Vibration Test Analysis Guide (VTAG), and appropriate maintenance actions.

2.7.3.6. The Contractor shall evaluate SEAS-VAS EADS and propose software upgrades required to improve its efficiency.

2.7.3.7. For estimation purposes, assume 35,000 vibrations samples are collected per year based on historical data.

2.7.3.8. The below chart portrays the approximate number of Vibration samples where manual analysis was performed per year by repair priority based on historical data:

2.7.4. Diesel Engine Combustion Analysis. The Contractor shall conduct an analysis of the parameter readings and combustion data taken by the crew and provide recommendations on the condition of the diesel engine system or the accuracy of the data collected. Provide the manual analysis review results to the affected ship’s Chief Engineer, Master, Port Engineer, Program Manager, Life Cycle Manager, and the COR within three (3) business days. For estimation purposes, assume that 850 readings will be taken for analysis per year based on historical data. A Diesel Engine Analysis Status Report shall be submitted monthly. CDRL 1423-6 Data Validation Report – CM Other; CDRL 1423-44 Diesel Engine Combustion Analysis Summary Report

2.7.5. Water Chemistry Analysis Support. The Contractor shall review the water chemistry parameters monthly to determine the applicability of the assigned log parameters to ensure that they match the chemical product in use. The Contractor shall update the data collection parameters in Logbook as necessary. A Water Chemistry Analysis Status Report shall be submitted monthly. CDRL 1423-6 Data Validation Report – CM Other

2.7.6. Monthly Review of condition monitoring systems effectiveness. The Contractor shall ensure the condition monitoring systems usage, as determined by the quality of the data, is sufficient to ensure proper collection, analysis, recommendation, maintenance and repair documentation for all condition monitoring technologies. Contractor should propose changes to existing processes or propose use of alternate technologies to more cost effectively assess the condition of the machinery. CDRL 1423-4 Data Review and Analysis Report

2.8. SAMM Software Requirements Analysis Support:

2.8.1. The Contractor shall provide support for documenting, analyzing and tracking of all software change requests. The Contractor shall review and determine the software change required within five (5) days of receiving the request. CDRL 1423-12 Software Update Tracker Report.

2.8.2. Software Requirement Stories (SRS) and Design Specification (DS) Support (CDRL 1423-17 Software Requirements Documentation).

2.8.2.1. When directed by the COR, the Contractor shall provide support for the development and maintenance of the SRS and DS as follows:

2.8.2.1.1. Define the Function of the Systems

2.8.2.1.2. Define the Performance Specification

2.8.2.1.3. Define the User Interface

2.8.2.1.4. Define the External Interfaces

2.8.2.1.5. Define Test Plan components

2.8.3. Software Test Plan. The Contractor shall provide software test plan development support for each SAMM system release and based on the Software Requirements Stories (SRS) and Design Specification (DS). CDRL 1423-17 Software Requirements Documentation

2.8.3.1. The Contractor shall maintain an overall system regression test plan. Testing shall be executed and results documented for each release of SAMM.

2.8.3.2. The Contractor shall set up a SAMM test environment to support troubleshooting, staff training, and creation of training documentation for each release of SAMM.

2.8.4. Data Support. The Contractor shall define and validate test data to be used during software testing. CDRL 1423-17 Software Requirements Documentation

2.8.5. The PMP for this specific task, SAMM Software Requirements Analysis Support, shall include milestones for monthly delivery of updated SRSs. CDRL 1423-21 Project Management Plan (PMP)

2.9. Engineering Afloat Support:

2.9.1. The Contractor shall visit MSC ships to provide upgrades of the installed SAMM system software. The Contractor shall coordinate with the MSC COR for the ships targeted for upgrade. Reference Table 2. Estimated Travel Table.

2.9.2. The below travel table is applicable to specific tasks 3.1 through 3.10 and provided for estimation purposes for one (1) year of support. The Contractor shall submit all travel requests to the COR for approval in accordance with the contract terms for required travel. All travel requests shall include supporting justification which defines the help call, reason for support, or issues to be resolved. The Contractor shall be responsible for submitting all necessary security visit requests to the appropriate government authority. Contractor travel will be reimbursable and shall be in accordance with DOD Joint Travel Regulations where the contract terms are silent or are not applicable. The Contractor shall only estimate travel listed in the below table for specific tasks 3.1 through 3.10.

Table 2. Estimated Travel Table. The Contractor shall be capable of traveling to all areas where MSC vessels are required to operate. The table below is provided for estimating purposes only.

iDEXTER/eConsole Support

SAMM Upgrade Support Visit

SAMM in-service visit

SAMM training support visit

SAMM Vibration monitoring support visit

Monthly Meeting Support

VTL Scanning Support

Local Travel

2.9.3. The Contractor shall provide ship support personnel sufficiently trained and capable of supporting all aspects of the SAMM support requirements listed below. Regardless of the primary purpose the Contractor may be required to support any of the items listed below during a ship visit. The Contractor shall visit MSC ships to provide the following:

2.9.3.1. Software Installation,…