MSC Afloat Operations PWS.docx

PERFORMANCE WORK STATEMENT

Afloat Operations Performance Work Statement (PWS)

1. Objectives The objective of this contract is to obtain Command, Control, Communications, and Computers (C4) Afloat Operations and Sustainment support. The Contractor shall provide technical support services for the various C4 capabilities aboard the MSC fleet of ships, the operation and sustainment of the MSC Network Operations Centers (MNOCs), Mobile Expeditionary Communication Kits (MECK) and future C4 capabilities hosted at the Navy Fleet Network Operation Centers (FLTNOCs).

2. Scope This requirement encompasses all activities to provide C4 support for MSC’s afloat environment and, ultimately, MSC’s mission. The tasks include but are not limited to, Knowledge Management, Cybersecurity, Maintenance and Sustainment, Modernization, Equipment/Asset Management, MSC Network Operations Centers (MNOC), Mobile Expeditionary Communication Kits (MECK), and Training unless a specific exemption is obtained.

The Task Areas below are identified within the following PWS and detailed herein to identify specific areas for performance under this requirement.

· Task Area 1 – Program Management

· Task Area 2 – Knowledge Management

· Task Area 3 – Maintenance and Sustainment

· Task Area 4 – In-Service Engineering Activity (ISEA) Support

· Task Area 5 – Support Services Modernization

· Task Area 6 – Equipment/Asset Management for Maintenance, Sustainment and Modernization

· Task Area 7 – MSC Network Operations Centers (MNOCs)

· Task Area 8 – Mobile Expeditionary Communication Kit (MECK) Support

· Task Area 9 – Training

· Task Area 10 – Place of Performance

· Task Area 11 – Contract Phase in/Phase-out

· Task Area 12 – Deliverables

· Task Area 13 – Security

· Task Area 14 – Common Access Cards (CAC)

· Task Area 15 – Additional Contractor Required Training

· Task Area 16 – Government Furnished Equipment/Government Furnished Items (GFE/GFI)

· Task Area 17 – Personnel Requirements

· Task Area 18 – Performance Standards

The Contractor will be responsible for purchasing small, consumable parts and equipment. These items include cables, CD spindles, laminating supplies, drop clothes, earplugs, and other minor items to complete the full scope of work. These items should be included in the fully burdened rates under the contract.

3. Background The Commander, Military Sealift Command (COMSC), as the single Department of Defense (DoD) manager for sea transportation, operates a worldwide command and a Government-owned fleet of approximately 116 ships, providing strategic and operational sealift to meet national defense objectives. In executing this mission, COMSC has implemented a Program Management (PM) organization responsible for all life cycle matters pertaining to its ships. These PMs are Fleet Oiler (PM1), Special Mission (PM2), Strategic Sealift (PM3), Service Support (PM4), Ready Reserve (PM5), Fleet Ordnance and Dry Cargo (PM6), and Expeditionary Fast Transport (PM8). Each Program Manager is responsible to COMSC for the operation, maintenance, and administrative management required to provide mission-ready ships worldwide to the Command Sponsors. An inventory of the vessels by Hull Number is available at the following Internet address: https://flankspeed.sharepoint-mil.us/sites/USFF-MSC-int/dashboards/SitePages/ShipDirectory.aspx. The fleet inventory and operating status change as required to support sponsor mission requirements.

Additionally, MSC has an extensive, global shore support organization focused on ensuring MSC’s fleet is operated and maintained in response to Fleet and Joint commander requirements. This shore infrastructure includes a headquarters element in Norfolk, VA, area commands, and support units located in various locations and discussed in detail below. MSC’s operating model differs substantially from that practiced by the Navy’s Combatant Fleet.

MSC ships are minimally crewed, with shipboard personnel focused primarily on operations. MSC ships maintain higher levels of operational availability than fleet units and operate in and out of ports not typically frequented by the DOD fleet. To balance the need for high operational availability with minimal crew staffing, MSC shore personnel and the contractor workforce provide most troubleshooting, repair, sustainment, and maintenance tasks.

MSC C4 Systems supported shall include, but are not limited to:

· Consolidated Afloat Networks and Enterprise Services (CANES)

· Network Management System (NMS)

· Common PC Operating Environment (COMPOSE)

· Automated Digital Network System (ADNS)

· Naval Modular Automated Communications System (NAVMACS)

· Next Generation Wideband (NGW)

· Shipboard Management Information System – Unclassified (SMIS-U)

· Shipboard Management Information System – Classified (SMIS-C)

· Mobile Expeditionary Communications Kit (MECK)

· Combined Enterprise Regional Information Exchange System (CENTRIXS)

· Global Command and Control System – Maritime (GCCS-M)

· Assured Compliance Assessment Solution (ACAS)

· Maintenance Figure of Merit (MFOM)

· Endpoint Security System (ESS)

· Ship’s Security Alert System (SSAS)

· Commercial Broadband Satellite Program (CBSP)

· MSC Network Operations Centers (MNOCs)

· Visual Information (VI) Kits

· Afloat Technical Assistance Center (ATAC)

· MNOC Telephony Services (Granite)

4. Performance Requirements

4.1 Task Area – 1 Program Management

4.1.1 Program Management

The contractor shall provide all necessary personnel, administrative, financial, and managerial resources necessary for the performance of this activity. The contractor shall designate a single point of contact (POC) as the Program Manager (PM) for use in communicating issues, concerns, or problems on this Performance Work Statement (PWS). The PM shall have the authority to commit to the contractor’s organization and make decisions for the contractor’s organization in response to Government issues, concerns, or problems. The PM shall be readily available to respond to questions, concerns, and comments and be proactive in alerting the Government to potential contractual/technical issues. Although Government staff may coordinate with other contractor staff, the PM shall serve as the single contractor representative responsible for resolving all issues, concerns, and problems.

At the Kick-Off Meeting, the contractor shall provide a draft Program Management Plan (PMP) to the MSC Contracting Officer’s Representative (COR). Effective Program Management will ensure that all contractor support resources assigned to this task are coordinated and leveraging existing processes. This effort will include the overall management of contractor resources assigned to this task order and reporting to and direct interaction with the COR. Program Management support includes the full range of project planning, resource management, risk assessment and mitigation, quality management, change control, and management of project deliverables consistent with industry best practices.

4.1.2 Program Management Plan

The contractor shall develop, deliver, and maintain, throughout the contract period of performance, a Program Management Plan that shall be used as a foundation for technical, resource, production, and management planning. The Contractor shall develop and deliver a preliminary Program Management Plan at the kick-off meeting and an updated Program Management Plan within 30 calendar days after the kick-off meeting. The Program Management Plan shall include the following summary information as well as any additional information deemed relevant by the Contractor:

· Identification of Key Contract Management Team Members, Authorities and Limitations

· Key Contract Vulnerabilities or Performance Risk Areas

· Inspection and Acceptance Process

· Key Performance Metrics

· Contract Transition Planning

· Deliverables

· Reporting Requirements

· Contract Change Control Process

· Fee Administration and Invoice Review

· Communication Process

· Quality Assurance Plan

4.1.3 Program Management Reviews

The contractor shall prepare and submit a Program Management Review (PMR) agenda to the COR 5 business days prior to the PMR meeting and prepare minutes within five (5) business days after the meeting. The Contractor shall disseminate the review to the COR and other stakeholders designated by the COR at least one business day prior to the date of the review meeting. The PMR shall address current task order performance compared to task order performance metrics, mitigation plans for under-performing areas, and other issues and concerns. The PMR shall summarize the previous three months' performance. The PMR will define the work projected for the subsequent three (3) months. The first review will be conducted three months after the Task Order award. Subsequent reviews will be conducted at three-month intervals.

4.1.4 Performance Measurement

The contractor shall monitor performance standards and report monthly via Monthly Program Status Reports. Monthly Program Status reports shall address all labor areas and include performance metrics for resources, risks, deliverables, accuracy, quality, schedule, cost, and hours by labor category for each reporting period. Metrics shall be reported for both monthly and aggregate/cumulative totals.

4.2 Information Assurance / Cybersecurity

The contractor's responsibilities under this contract encompass various critical areas of information assurance and cybersecurity, including the following:

· Operational Support: Ensure day-to-day IT operations and user support to maintain system efficiency. Timely and effectively respond to security incidents to minimize potential damage and facilitate rapid recovery.

· Education and Protection: Develop and implement comprehensive training programs to educate personnel and stakeholders on security best practices and compliance requirements. Implement robust measures to safeguard sensitive data and adhere to data protection and privacy regulations.

· Information Security Assurance: Implement comprehensive security measures to protect all facets of organizational information, covering data, systems, and processes. Enforce security protocols and controls specific to information systems, preserving access integrity.

· Communication Security: Safeguard the confidentiality and integrity of internal communications, ensuring secure transmission and storage of sensitive data.

· Proactive Cybersecurity: Maintain a proactive cybersecurity stance, continuously monitoring for threats, vulnerabilities and applying mitigation strategies.

· Risk Management and Compliance: Support the full Risk Management Framework (RMF) process, from risk assessment to authorization and continuous monitoring activities, ensuring compliance with DoD and relevant regulations. Regularly assess and audit activities and systems for adherence to regulatory and organizational standards.

· Business Continuity and Vendor Oversight: Develop and implement strategies for uninterrupted operations during disruptions. - Oversee third-party vendors or suppliers for security and performance, if applicable.

· Governance and Policy Framework: Establish and enforce security policies and governance frameworks, guiding all security-related activities.

· Security Integration in SDLC: Prioritize the early integration of security requirements within the system development life cycle (SDLC), aligning with DoD, USCYBERCOM, and other relevant authorities.

· Use automated tools (e.g., SCAP, ACAS, STIG Viewer, SCC, Tenable, Nessus, eMASS) to apply and monitor cybersecurity compliance.

· Timely Compliance and Reporting: Emphasize prompt compliance with security notifications (IAVMs, CVEs, SRGs, STIGs) and conduct regular security scans, reviews, and assessments. - Address vulnerabilities in non-compliant systems through patching or documented approval of mitigation plans. Generate reports via command’s trouble ticket system (currently Helix) for non-operational ACAS scanners and invalid assets.

· Classification Control and Authorization: Ensure information systems adhere to authorized classification levels. - Maintain valid RMF ATOs, operate authorized systems, and register NIPRNet and SIPRNet systems through eMASS.

· Information Security Compliance: Ensure compliance with federal, departmental, and agency policies and guidelines regarding Controlled Unclassified Information (CUI) and personally identifiable information (PII).

· Privileged Account Management: Thoroughly complete and sign all DD Form 2875 entries for privileged account requests, ensuring adherence to DoD training, certification prerequisites, non-disclosure agreements, and access level justification. - Maintain quarterly reporting of privileged user accounts in line with USCYBERCOM Taskord 14-0185 Insider Threat Mitigation.

· Cybersecurity Workforce Compliance: Ensure staff strictly comply with certification requirements outlined in DoD Manual 8140.03 Cyberspace Workforce Qualification and Management Program and SECNAVINST 5239.20A. Prepare and continuously update a semi-annual cybersecurity workforce (CSWF) report on team members' current CSWF levels, certification statuses, and annual training hours, providing updates upon staff replacements. These responsibilities underscore the contract's focus on integrating security, maintaining compliance, and preserving data integrity while aligning with stringent DoD and relevant regulations.

4.3 Quality Assurance

The contractor shall have at contract award and maintain a quality management system for all work supporting this contract. The contractor shall provide a quality assurance plan and approach for task order management, task order deliverables, and business process improvement to enhance the current and future processes. The quality assurance plan shall be provided at the contract kick-off meeting. DID DI-QCIC-81794, Quality Assurance Program Plan (QAPP) may be used and tailored with Government concurrence.

4.4 Data Control

The Contractor shall implement a Data Management (DM) process for identification, acquisition, control, maintenance, status accounting, and timely delivery of data items. All data associated with the performance of this contract shall be considered Government owned and shall be made available to the Government upon request. The Contractor shall transfer data and information to the Government electronically to the maximum extent possible to facilitate more rapid communications between Government and Contractor organizations.

4.5 Travel

While performing work in accordance with this PWS, the contractor shall be required to travel within the continental United States (CONUS) and outside the continental United States (OCONUS). The contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. Historically, the contractor can anticipate the following on a 12-month basis:

4.5.1 Contractor Request and Approval of Travel

Any travel under this contract must be directed by the Contracting Officer’s Representative (COR) or specifically requested in writing by the contractor and approved by the Contracting Officer’s Representative (COR) before incurring any travel expense. When possible, the contractor shall submit the written request to the COR three weeks in advance. The travel request shall include, as a minimum, the following:

1. Contract number

2. Date, time, and place of proposed travel

3. Purpose of travel and how it relates to the contract

4. Contractor’s estimated cost of travel with a breakdown of the estimated costs of transportation, lodging, meals, and incidentals; and

5. Name(s) of individual(s) traveling.

The COR will review and approve/disapprove (as appropriate) all travel requests submitted, giving the contractor written notice of such approval or disapproval.

4.5.2 Travel Reimbursement

The Contractor will be reimbursed for the reasonable actual cost of transportation, lodging, meals, and incidental expenses. However, actual costs shall be considered reasonable, allowable, and reimbursable only to the extent that they do not exceed on a daily basis the maximum per diem rate in effect at the time of travel as outlined in the DOD Joint Travel Regulations located at https://secureapp2.hqda.pentagon.mil/perdiem/. Actual cost does not include handling charges, general and administrative costs, overhead, profit, or any other indirect cost. Typically, for an employee "permanently" stationed overseas, rather than pay per diem, the employee would be granted a cost of living allowance (COLA) to make up for the difference. Reference: https://aoprals.state.gov/Web920/cola.asp, which includes the different COLA rates. This COLA would be billable under a travel CLIN.

The contractor shall use the allowable Government personnel rates for transportation and lodging. Reimbursement for airfare shall not exceed the lowest customary standard, coach, or equivalent airfare offered during normal business hours. The Contractor will not be reimbursed for travel expenses unless audited records for transportation contain evidence, such as original receipts, substantiating actual expenses incurred for travel. In no event will reimbursement exceed the published rates of common carriers. Expenses for lodging, meals, and incidental expenses shall be reimbursed to the Contractor, provided that the overnight stay was documented as necessary.

Each order that requires travel will include a not-to-exceed funding limitation for travel costs. When the Contractor projects funding for travel to reach 70 percent of the total funds available on the reimbursable travel CLIN, the Contractor shall notify the Contracting Officer, the COR, and any other Government official identified by the Contracting Officer. The notice shall state the estimated additional funds required to continue performance for the period specified in the order. The Contractor shall not exceed or incur costs that exceed the amount of funding stated on an order’s reimbursable travel CLIN.

The Government is not obligated to reimburse the Contractor for otherwise reimbursable travel above the funded amount stated on an order’s reimbursable travel CLIN.

The Contractor is not obligated to continue the performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel above the funded amount stated on an order’s reimbursable travel CLIN unless the Contracting Officer notifies the Contractor in writing that the funded amount stated under that reimbursable travel CLIN has been increased. In the event notification is made orally, such notification shall be followed up in writing within two working days.

No notice, communication, or representation from any person other than the Contracting Officer shall affect the Government’s obligation to reimburse the Contractor.

Changes to the contract or order shall not be considered an authorization to exceed the funded amount stated on a reimbursable travel CLIN unless the change contains a statement expressly increasing the funded amount of the reimbursable travel CLIN by a sufficient amount to cover the change.

A Travel Summary Report shall be created for each instance of travel to locations as an MSC N6 representative. It shall contain sufficient detail of the travel information and costs incurred.

A trip Report shall be created upon the return for each instance of travel to locations as an MSC N6 representative. It shall include the dates, purpose, location, summary of actions, action items, and recommendations for future work.

4.5.3 Multiple Vessel Visits at the Same Site

A Contractor visiting multiple vessels at the same site shall only be entitled to travel reimbursement for a single occurrence of travel to and from the site. Per diem shall be provided if visiting the multiple vessels takes more than one (1) day.

4.5.4 Travel Audits

The Contractor shall maintain receipts for all travel expenses greater than $75 throughout the life of the contract. At least two (2) random audits will be conducted by the COR within a 12-month period. All receipts shall be produced along with any other supporting documentation.

5.0 Program Management Deliverables

All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format.

6.0 Task Area 2 – Knowledge Management

Knowledge management is the process of capturing, distributing, and effectively using internal and external data and information resources to produce insights about the MSC afloat enterprise that drive effective planning and decision-making. It requires a structured and disciplined approach to collecting, disseminating, and analyzing data and information from authoritative data sources. For example, MSC uses trend analysis from N6 Casualty Reports (CASREPs) to drive decisions about procurement of spare parts, requirements for technical refreshes, and systemic problems requiring programmatic action. Performance of Knowledge Management functions requires regular and routine access to classified and unclassified government IT systems within MSC facilities or a secure contract service provider facility. To support this area, the contractor shall:

· Develop and implement a Knowledge Management Plan that will document the vendor’s approach for generating, storing, and managing artifacts required to execute the work identified in this PWS. The plan should address issues such as file management, discoverability, access, collaboration, and solutions used for storing, accessing, and retaining artifacts.

· Use the command’s trouble ticket system (currently Helix) to document actions taken to resolve issues and conduct trend analysis of the trouble ticket system to determine systemic issues with MSC C4 capabilities.

· Analyze N6 CASREP data and conduct trend analysis to determine systemic issues with MSC C4 capabilities.

· Review unclassified and classified data from MSC N6 CASREPS and compare the reported equipment and parts data with the data in MSC Configuration Data Management Plan (CDMP), COMSC Instruction 4790.3C, systems. The Contractor will correct the MSC CDMP data as required, provide N6 CASREP quality results to the government, and trend the results on a ship, class, and program basis.

· Respond to data calls, as required, on MSC C4 capabilities to address higher headquarters information requirements or to address MSC N6 C4 capability analysis requirements and inform resource issue papers.

· Capture, analyze, and disseminate lessons learned from system, equipment, and network deployment activities that are used to drive continuous process improvement.

· Assist MSC N6 with developing Safety Management System (SMS) and Quality Management System (QMS) procedures.

· Develop, produce, and maintain all standard operating procedures (SOPs) and other reference material in an authoritative library managed under a disciplined change control process.

· Develop and maintain a government-approved Ship C4 Readiness Reports. The Ship C4 Readiness reports shall be tailored to specific PMs and Area Commands and include all ships assigned to the PM and Area Command. This report will include ship-specific information, exercise, mission or operation support, and C4 readiness of the ship based on Networks, Communications, Navigation, and Command and Control capability readiness. N6 CASREPs and Trouble Tickets will be evaluated when determining readiness.

Readiness will be indicated in clear color-coded identification (i.e., Red, Yellow, and Green), where red indicates non-mission capable capability, yellow indicates degraded capability, and green indicates full operational capability. Amplifying information will be included in the report for all degraded conditions.

· Produce a lesson-learned report for all class-wide or multi-class deployment activities. The plan must document variances and the causes for the variances between the original cost, schedule, performance, and risk projections made during the deployment planning phase and the final cost, schedule, performance, and risk at the conclusion of the deployment. The Deployment Lessons Learned report aims to identify factors generating variance between the deployment plan and execution of the deployment to inform the development and implementation of mitigations that can reduce variances and lead to more effective deployment planning.

6.1 N6 CASREP Reporting

N6 CASREP has been designed to support the Chief of Naval Operations (CNO) and fleet commanders in the management of assigned forces. The IT/Electronics CASREP also alerts the Naval Safety Center for Incidents; the provided information is crucial for mishap prevention. The effective utilization and support of Navy units and organizations require an up-to-date, accurate operational status for each unit. An essential part of operational status is equipment casualty information. The reporting of casualties results in operational commanders and support personnel being advised of the status of significant equipment malfunctions, which may result in the degradation of a unit’s readiness. If systems cannot be restored within 48 hours of submission, a CASREP will be released. The contractor shall:

· Conduct a daily identification and review of MSC N6 CASREPs.

· Provide a daily UNCLASSIFIED N6 CASREP report. Weekend and Federal Holidays will be included in the next business day’s report. The report format will be developed and mutually agreed upon between the Government and the contractor.

· Maintain a SECRET level database of Initial, Update, Corrected, and Canceled N6 CASREPs. The SECRET database will include all historical N6 CASREPs for five years.

6.2 Knowledge Management Deliverables

7.0 Task Area 3 – Maintenance and Sustainment

The Contractor shall provide the maintenance and sustainment support of MSC systems identified throughout this contract. Maintenance and sustainment activities shall be performed per applicable MSC instruction and maintain government-approved C4 system baselines. In order to maintain and sustain MSC equipment, the contractor shall perform the following functions, including but not limited to:

· Provide network incident response and problem management.

· Provide Tier II support for shipboard networks and MNOCs.

· Review and provide input to Government-developed Configuration Change Requests (CRQ) and Transportation Alterations (TRANSALT), COMSCINST 4700.2.

· Review and provide input to system configuration utilizing REMEDY for software and Corrective Maintenance and Logistics System (CMLS) for hardware.

· Review and provide input to software load procedures.

· Review and provide input to production and installation drawings, schedules, and documentation IAW COMSCINST 4700 series instructions.

· Provide input to version configuration required for proper system operation, production testing, and configuration management.

· Perform maintenance and sustainment functions per applicable references.

· Track certificate expirations and upgrade certificates before expiration on all POR and Non-POR systems.

7.1 Incident Response and Problem Management

The contractor shall support incident response and problem management efforts, which include, but are not limited to, implementation of necessary corrective actions and/or interim workarounds, identifying and documenting the root cause of system problems, restoration of system functionality using the known good baseline, as well as updating appropriate knowledge bases and providing lessons learned. The Navy Enterprise Service Desk’s Trouble Ticket System, Helix, shall be used for Incident Reporting. To best support this effort, the contractor shall:

· Support incident response activities that include, but are not limited to, problem identification, recording, classifying, diagnosing, creating metrics, resolving, and reporting.

· Managing Configuration Control includes providing correction of configuration items to resolve or remove errors, faults, or inconsistencies in conjunction with the overall management of known configuration while they remain unresolved and until they are eliminated by the successful implementation of changes made under the change control process.

· Be responsible for resolving issues/trouble tickets/network CASREPs within the prescribed time thresholds and Service Levels (SLs) established by MSC.

· Provide weekly activity reports to track trouble calls, outages, user problems, resolutions, travel dates with associated costs, and routine operational maintenance. Provide weekly technician assignment reports. The report format will be developed and mutually agreed upon between the Government and the contractor.

· Provide a monthly activity report to include accomplishments, issues, metrics, and recommendations for process improvement. The report format will be developed and mutually agreed upon between the Government and the contractor.

· Design and implement solutions for the analysis and visualization of data to support MSC’s decision-making process regarding incidents.

· Provide SMEs for contracted systems to attend ad hoc meetings at the discretion of the Government PM or designee via the COR’s concurrence. The contractor role in ad hoc meetings is to provide fleet support experience, technical recommendations, or support process clarification. The contractor will not be required to host meetings or generate meeting minutes. The contractor shall be ready to prepare and provide any further artifacts as a result of any ad hoc meeting.

7.1.1 Incident Response Prioritization

workaround exists.

OR

A problem has made a vital application function/system unusable or unavailable, and no workaround exists.

performance, but the functionality still performs as specified in the user documentation.

7.1.2 Incident Response and Resolution Time

7.2 Tier II Support

For the purposes of this contract, Tier II support is defined as technicians that have a pre-determined skill set (e.g., network engineering, systems administration, etc.) and the capability to use advanced diagnostic tools and analytical processes to conduct independent assessments needed to sustain, troubleshoot, and repair C4 capabilities. The contractor shall provide Tier II support to the MSC fleet in analyzing, troubleshooting, repairing, testing, and making recommendations related to the shipboard network environment and associated MNOC/FLTNOC shore infrastructure. In addition, the contractor shall:

· Perform all troubleshooting per NAVWAR Program of Record (POR) approved documentation such as the Hardware Configuration Document (HCD), Load Plan, etc., derived from SAILOR 2.0, CM Pro and other authoritative sources.

· Troubleshoot, diagnose and resolve outages and other problems with network components and subsystems, including, but not limited to, routers, switches, servers, workstations, thin clients, printers, copiers, and multi-functional devices.

· Work in coordination with other network efforts in MSC to improve the network performance.

· Maintain and troubleshoot all approved connections to the operational shipboard networks.

· Maintain and troubleshoot all Commercial Off-the-Shelf (COTS) software on the network.

· Respond to all validated network/subsystem Global Service Desk (GSD) trouble tickets and network CASREPs. The contractor shall capture support efforts using Remedy and other applicable CDMP systems.

· Associate any Remedy incident numbers with the appropriate N6 CASREPs by annotating the associated N6 CASREP in the incident.

· Provide Active Directory services to allow administrators to assign policies, deploy software, and apply critical updates to the shipboard network infrastructure.

· Set up and maintain Active Directory accounts, access groups, folders, and file-sharing capabilities.

· Provide Operating System (OS) services and administration to include enterprise system management, server and data storage administration, security boundary administration, file services, print services, Internet Protocol (IP) services, management storage services, Windows systems administration, and user account management.

· Provide Windows administration, which includes but is not limited to:

· Central authentication and authorization services

· Analyze data stored on the Windows system and make recommendations relating to the performance and efficiency of that data storage.

· Maintain all networking security standards (e.g., Cryptographic Logon/Public Key Infrastructure) to the network and subsystem equipment in the shipboard network environment per current cybersecurity policies.

· Review results of weekly Assured Compliance Assessment Solution (ACAS) scans that apply to their IS components to determine if remediation actions are required. Information Systems (IS) vulnerabilities will be addressed. Critical vulnerabilities must be remediated within 15 calendar days of initial detection, and High vulnerabilities must be remediated within 30 calendar days of initial detection. The local ISSM will determine the mitigation of non-remediated vulnerabilities or removal of the affected system from the network.

· Contractors will verify compliance with all STIGs that apply to their IS components semi-annually. Compliance with new STIGs will occur no later than ten (10) business days after STIG release, generating a POA&M on fixes and dates proposed for compliance on “Open” items.

· Install software patches and service packs that apply to their IS components required to maintain cybersecurity compliance and adherence to the government-approved system baseline.

· Assist the fleet with reporting possible incidents to MSC’s Information Systems Security Manager (ISSM) and cybersecurity team. Support includes providing all required incident documentation, which will be performed per established MSC cybersecurity incident policies.

7.3 Tier III Support

MSC defines Tier III support as technicians with specialized skills over and above those of Tier II technicians. The type of support provided involves the skills necessary to address and resolve complex issues. Assist in the engineering and development of IT/IS solutions. Technicians at this level are expected to collect the necessary data from Tier I and Tier II technicians while working toward resolution.

The contractor shall:

· Access appropriate Tier III support as directed by MSC.

· Work diligently with the MSC entity or commercial vendor that performs Tier III tasks and provides appropriate support, including hand-off and documentation receipt through resolution.

7.4 Maintenance and Sustainment References

Maintenance and Sustainment support will adhere to applicable MSC Directives, Instructions, and Memorandums to include, but not limited to:

· COMSCINST 2280.1 Public Key Enablement of Secret Internet Protocol Router Network

· COMSCINST 2280.3E Policy and Procedures for Handling, Distribution, and Control of Communications Security Material in the Military Sealift Command using Communications Security (COMSEC)

· COMSCINST 3540.7 Engineering Operations and Maintenance Manual (EOMM)

· COMSCINST 4700.1 Military Sealift Command's Technical Authority, Maintenance Philosophy, and Maintenance and Repair Management System (MRMS)

· COMSCINST 4700. 15E Overhaul, Repair, and Maintenance of MSC Vessels in Foreign Shipyards

· COMSCINST 4700.16 MSC General Technical Requirements

· COMSCINST 4700.2H Alteration Management for MSC Ships

· COMSCINST 4750.2D Preservation Instructions for MSC Ships

· COMSCINST 4790.3 Equipment Configuration Data Management and Logistic Support for Ships of the Military Sealift Command

· COMSCINST 4800.1 Regulatory Standards and Documentation for MSC Ships

· COMSCINST 5230.2A Commander, Military Sealift Command, Information Technology (IT) Governance Instruction

· COMSCINST 5230.8 Military Sealift Command Information Technology Asset Management (ITAM)

· COMSCINST 5230.10 Integration Process for the COMSC Command Control Communications and Computer Systems (C4S) Enterprise

· COMSCINST 5239.3E Military Sealift Command Information Cyber Security Policy

· COMSCINST 5239.4B Military Sealift Command Secret Media Transfer Policy

· COMSCINST 5522.2A Portable Electronic Devices in MSC Spaces (PEDs)

7.5 Maintenance and Sustainment Deliverables

8.0 Task Area 4 – In-Service Engineering Activity (ISEA) Support ISEA are delegated functions by and in support of the program manager for the overall engineering, test, maintenance, technical analysis, and logistics requirements incident to the specific MSC systems identified in section

3.0. An example of such an activity would be installing a minor maintenance update that is beyond the ship’s force’s capability and would require touch labor to perform. The MSC IT Program Office Engineering section is responsible for the ISEA function but may require support from the contractor or other system commands.

To support MSC’s ISEA efforts, the contractor shall:

· Identify problems to the IT Program Office that may require ISEA to resolve.

· Participate in engineering-led operational and failure analyses to assess problems and develop solutions.

· Support on-site engineering investigations to evaluate the performance of systems/equipment.

· Assist in the development of TRANSALTS for ISEA efforts.

· Assist in maintaining applicable documentation in the MSC Configuration Management Database (CMDB).

· Deploy solutions developed through ISEA to the MSC Fleet.

9.0 Task Area 5 – Support Services Modernization

Modernization involves introducing a new system or upgrading an existing system that delivers new or enhanced functionality. Throughout the life of this contract, MSC may direct significant system-wide or fleet-wide modernization activities that require the deployment of hardware and software by the Contractor. An example of such an activity would be a technical refresh of network servers and routers across the MSC fleet.

To support MSC’s modernization efforts, the contractor shall:

· Assist in developing and maintaining class-specific modernization plans for MSC ships, detailing the schedule for modernization, technical refresh, and system grooms.

· Assist in the development of TRANSALTS for modernization efforts.

· Assist with developing processes and tools to increase the efficiency and effectiveness of modernization planning.

· Coordinate with MSC N6 Systems Engineering efforts to support the transition from the design, development, and testing phases of system development into the deployment phase.

· Participate in system reviews (Critical Design Review, Test Readiness Review, Deployment Readiness Review, etc.) and other systems development milestone activities.

· Conduct or participate in, as required, Pre-Installation and Test Check-Out (PITCO) and Systems Operational Verification Tests (SOVTs).

· Participate as an observer in the first low-rate initial production (LRIP) events run by MSC N6 Systems Engineering, assist MSC N6 Systems Engineering with the second and third LRIP event, and conduct the fourth, fifth, and sixth LRIP event independently as preparation for shipboard deployment phase. STRATAS LRIP team should be the same as LRIPS one through six.

· Establish processes and provide the facility needed to produce systems for class-wide deployment of modernized systems.

· Develop detailed deployment plans in a work breakdown structure (WBS) that show the time-phased steps for deployment activities such as survey, procurement, production, training, shipping and logistics, de-installation, installation, and disposal.

9.1 Modernization Deliverables

Maintenance Plans

10.0 Task Area 6 – Equipment/Asset Management for Maintenance, Sustainment and Modernization The contractor shall use commercial best practices to provide C4 equipment support services listed below to support MSC ship operations and to assist in maintaining fleet readiness and performing modernization activities.

10.1 Equipment Validation/Asset Inventory

The contractor shall perform and record the results of physical ship C4 system/equipment validations. Validations will be performed and recorded using MSC systems and procedures identified in the MSC CDMP to inform and populate command, service, and joint Baseline Configuration Control Program (BCCP) plans or similar documents/databases. Provide inventory/equipment forecasting based on the installation or repair demands.

10.2 CMLS and ShipClip Data Entry

The contractor shall use MSC’s Approved Property System of Record (APSR) to manage the life cycle of MSC C4I assets afloat and ashore from installation to disposal. MSC’s APSR is Corrective Maintenance and Logistics System (CMLS), Shipboard Configuration Information Program (ShipClip). All afloat configuration changes performed by the contractor or other activity (NIWC, NAVWAR, etc.) (adds, changes, and deletes) shall be processed using the feedback function in CMLS/ShipClip. The N6 Type Desk shall coordinate CMLS/ShipClip training with the contractor.

All assets shipped to an MSC warehouse, not ordered in CMLS/ShipClip, shall have a Not from Due document created to allow the warehouse personnel to receive the material. Shipping requests shall be processed in CMLS.

10.3 Equipment On-load or Off-load

During physical on-loads and off-loads of C4 system equipment performed by the Ship’s force and/or MSC Logistics personnel, the Contractor shall ensure MSC inventories and system configurations are updated and recorded using MSC systems and procedures identified in the MSC CDMP.

10.4 Overhaul, Alteration, and Voyage Repair Support

The contractor shall:

· Assist the Government with research and technical analysis to determine the form, fit, and function of replacement C4 systems and equipment.

· Review the replacement systems and equipment specifications for the impact of configuration and life cycle support.

· Identify current system and equipment configuration and suitable replacement systems/equipment.

· Identify initial outfitting spares.

· Research and identify applicable Military Specifications (MILSPECS), technical drawings, American Bureau of Shipping (ABS) / Coast Guard standards, and commercial and international specifications of C4 equipment.

· Provide recommendations for equipment standardization options to maximize equipment performance and reliability based on what is installed onboard the target ship or ship class.

· Identify Allowance Parts Lists (APL) / Allowance Equipage Lists (AEL) associated with the system/equipment.

· Identify and submit TRANSALTs for adding and deleting systems/equipment per COMSC Instruction 4700.2H.

10.5 Attend Repair/Alteration Planning Meetings

The contractor shall attend, participate in, and record minutes from Repair and Alteration Planning meetings to obtain logistics planning information and maintenance schedule changes.

10.6 Process Technical Manual, Drawing, and other Technical Documentation Information The contractor shall process the technical manual and drawing information and update the MSC CDMP database as dictated by availability and new ships coming into the MSC inventory. Technical manual and drawing information in MSC CDMP-identified systems is updated from the Virtual Technical Library, MSC library data, Technical Manual Indices, and Drawing Indices in response to feedback and availability changes. The Contractor shall also review and upload other technical document data from various sources as provided by the Government.

10.7 Conduct Technical Manual, Chart, and Drawing Analysis

The contractor shall:

· Compare the ship’s Technical Manual and Drawing Indices with MSC CDMP systems and databases, the MSC Virtual Technical Library, and other references to identify any omissions or errors.

· Produce and install new Technical Manuals and/or drawing indices aboard the ship.

· As required, update configuration and logistics data/records per the MSC CDMP.

· Provide data for requisitions and Technical Manual deficiencies.

10.8 Monitor Government Issued Equipment

At the direction of the Government, the contractor shall monitor, record, and report to the Government representative all C4 equipment issued from MSC warehouses to support shipboard installation or repair work items. The record of equipment issued shall be recorded and maintained using MSC systems and procedures identified in the MSC CDMP. NOTE: At no time will equipment be issued to a ship without the concurrence of a TPOC and the approval of the COR.

10.9 Ship Activation/Deactivation Support

The contractor shall support MSC ship activation/deactivation activities as directed by the Government. For ship activations, activities may include, but not be limited to:

· Verify that C4 is configured in accordance with approved baselines.

· Verify and validate C4 equipment inventory using MSC systems and procedures identified in the MSC CDMP.

· Reconcile shipboard C4 equipment inventory and spares using MSC systems and procedures identified in the MSC CDMP.

Ship deactivations shall include but are not limited to:

· C4 equipment offload, transportation of equipment, appropriate pack up of offloaded equipment, and an inventory of the offloaded equipment.

· Ship configuration data resident in MSC configuration management systems shall be removed and archived in accordance with the MSC CDMP.

10.10 Coordinate Disposition of Residual Government Equipment The Contractor shall:

· Prepare a list of residual Government C4 equipment that remains after completion of an overhaul, deactivation, availability, or voyage repair,

· Prepare equipment for warehousing and/or long-term storage and potential reuse,

· Provide this consolidated list to the Government for disposition instructions,

· Coordinate the disposition and, if applicable, dispose of the residual equipment in accordance with the FAR Part 45 and forward all associated documentation to the Government.

10.11 Identify Planned Program Requirements

The Contractor shall analyze C4 equipment, identify recommended shore-based spares requirements, and recommend upgrades and/or replacements for supportability through a ship or equipment life cycle.

10.12 Equipment/Asset Management Deliverables

10.1/ 10.8

Office products

11.0 Task Area 7 – MSC Network Operations Centers (MNOCs)

11.1 MSC Network Operations Centers (MNOCs)

MSC operates, sustains, and maintains two network operations centers (MSC NOCs or MNOCs) that provide support for MSC afloat operations through administration and management of the afloat IT infrastructure, commercial satellite connectivity, security, network management, and telephony services and the provision of Tier II Helpdesk services to MSC afloat users and MSC HQ Staff. MNOC East is in Pensacola, FL, the primary NOC service for MSC ships operating globally.