N3220518R1015_Amendment_0002.docx

N3220518R1015

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 17-Jul-2018 04:30 PM to 24-Jul-2018 02:30 PM.

TABLE OF CONTENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

to:

Exhibit/Attachment Table of Contents

The following have been modified:

STATEMENT OF WORK

Performance Work Statement Military Sealift Command (MSC) N6 Afloat Operations Support

1. General The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

2. 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, and the operation and sustainment of the MSC Network Operations Centers (MNOCs).

3. Background The Commander, Military Sealift Command (COMSC), in the role as single Department of Defense (DOD) manager for sea transportation, operates a worldwide command and a Government-owned fleet of approximately 116 ships, which provide 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), Afloat Staging and Command Support (PM7) 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: http://www.msc.navy.mil/inventory/inventory.asp?var=hull. The fleet inventory and operating status change as required to support sponsor mission requirements.

Additionally, MSC has an extensive, global shore support organization that is 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 greater detail below. MSC’s operating model differs substantially from that practiced by the Navy’s Combatant Fleet. MSC ships are minimally manned, 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 Fleet. To balance the need for high operational availability with minimal crew manning, most troubleshooting, repair, sustainment, and maintenance tasks are provided by MSC shore personnel and the contractor workforce.

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

· Consolidated Afloat Networks and Enterprise Services (CANES)

· Common PC Operating Environment (COMPOSE)

· Automated Digital Network System (ADNS)

· Next Generation Wideband (NGW)

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

· Afloat Release 1 (AR1)

· Afloat Release 2 (AR2)

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

· Afloat Classified Global Operating System Upgrade (GOSUP) (ACG- V1)

· Afloat Classified Global Operating System Version 2 (ACG-V2)

· PC to PC Transfer System (PPTS)

· Combined Enterprise Regional Information Exchange System (CENTRIX)

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

· Assured Compliance Assessment Solution (ACAS)

· Maintenance Figure of Merit (MFOM)

· Department Head Afloat Management System (DHAMS)

· Host Based Security System (HBSS)

· Ship’s Security Alert System (SSAS)

· Global Maritime Distress and Safety System (GMDSS)

· Commercial Broadband Satellite Program (CBSP)

· Public Branch Exchange (PBX)

· MSC Network Operations Centers (MNOCs)

4. 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 (MNOCs), and Training.

5. 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 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, as well as 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.

The contractor shall provide a draft Program Management Plan (PMP) to the MSC Contracting Officer’s Representative (COR) at the Kick-Off Meeting. 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 as well as 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.

5.1 Contract Kick-Off Meeting

The contractor, after coordination with the Government, will schedule and coordinate a contract kick-off meeting to be held within 5 business days of task order award. The contractor, with the assistance of the Government, will develop an agenda for the meeting. The contractor will ensure that all identified participants are notified of the meeting in advance. At a minimum, kick-off attendees shall include key contractor personnel and key MSC personnel. At the kick-off meeting, the contractor shall present its Transition Plan for overall program management of the awarded task order. The contractor shall develop and, after Government approval, distribute meeting minutes and action items within 5 business days after the kick-off meeting.

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

5.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 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 in comparison with 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 3 months. The first review will be conducted three-months after award. Subsequent reviews will be conducted at three-month intervals.

5.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, schedule, cost and hours by labor category for each reporting period. Metrics shall be reported for both monthly and aggregate/cumulative totals.

5.5 Performance Cost Reporting

The contractor shall prepare and submit a report concurrently with each invoice presented for payment. The contractor shall report expenses that can be invoiced under the contract. The report shall include labor expended for the period and cumulatively broken out to identify labor categories, labor rate, project ID and project phase and personnel utilized. Contractors must provide a cost summary sheet providing a breakout of monthly costs per effort and cumulative costs as they relate to the estimated amounts. The contractor shall use the report format found as defined in the Performance Cost Report. DI-MGMT-81466A, Cost Performance Report and/or DI-FNCL-80912, Performance and Cost Report may be used and tailored with Government concurrence.

5.6 Information Assurance / Cybersecurity

The contractor shall comply with the latest MSC Information Assurance/Cybersecurity Policy. Current policy is detailed in MSC Instruction COMSCINST 5239.3. Compliance with this directive is mandatory during the execution of this PWS.

The contractor shall ensure all staff comply with the certification requirements identified in Department of Defense (DoD) Directive 8570.01-M, Cyberspace Workforce Management and SECNAVINST 5239.20A DON Cyber IT and CSWF Management and Qualification. The contractor shall prepare a cybersecurity workforce (CSWF) report semi-annually that describes the current CSWF level for each contract team member, certification status, and number of hours of training completed for the calendar year. The report shall be updated and delivered upon staff replacement as well.

5.7 Quality Assurance

The contractor shall have at contract award, and shall maintain, a quality management system for all work performed at the contractor’s facilities in support of 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.

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

5.9 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 an annual basis:

· 203 CONUS trips with a total of 2989 travel days

· 135 OCONUS trips with a total of 2028 travel days

5.9.1 Contractor Request and Approval of Travel: Any travel under this contract must be either 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), prior to incurring any travel expense. The contractor shall submit the written request to the COR three weeks in advance, when possible. 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 written notice of such approval or disapproval to the contractor.

5.9.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 set forth in the DOD Joint Travel Regulations located at https://secureapp2.hqda.pentagon.mil/perdiem/. Actual cost does not include handling charges, general and administrative cost, overhead, profit or any other indirect cost. Typically, for an employee "permanently" stationed oversee, 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 expects total funding expended for reimbursable travel to reach 85 percent of the total funds available on the reimbursable travel CLIN, the Contractor shall notify the Contracting Officer and the COR and any other Government official identified by the Contracting Officer. The notice shall state the estimated amount of 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 in excess of the funded amount stated on an order’s reimbursable travel CLIN.

The Contractor is not obligated to continue performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel in excess of 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 an 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.

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.

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

5.9.4 Travel Audits: 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 e shall be produced along with any other supporting documentation.

5.10 Program Management Deliverables

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

5.1

5.1

5.2

5.4

5.7

5.8

14.1

14.2

6. 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 the collection, dissemination, and analysis of data and information from authoritative sources of data. 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 either within MSC facilities or in 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 generation, storage, and management of artifacts required to execute the work identified in this PWS. The plan should address issues such as file management, discoverability, access, collaboration, and solution or solutions used for the storage, access, and retention of artifacts.

· Use the command’s trouble ticket system (currently BMC Remedy) 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.

· 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 the development of 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 supporting; 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. 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. Goal of the Deployment Lessons Learned report is 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 important 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 N6 CASREP will be sent. The contractor shall:

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

· Provide a daily N6 CASREP report. Weekend and Federal Holidays will be included in the next business day’s report. The format of the report 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.

6.2 Knowledge Management Deliverables

6.0

6.1

7. 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 in accordance with applicable MSC instruction and shall 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.

· Engage or provide Tier III support as required to resolve complex system problems and outages.

· 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 in accordance with applicable references.

7.1 Incident Response and Problem Management

The contractor shall support incident response and problem management efforts, which includes, but is not limited to, implementation of necessary corrective actions and/or interim workarounds, identifying and documenting 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. MSC’s Trouble Ticket System shall be used for Incident Reporting. To best support this effort the contractor shall:

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

· Managing Configuration Control which 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 the resolution of issues/trouble tickets/network CASREPs within the prescribed time thresholds and Service Levels (SLs) established by MSC.

· Provide weekly activity reports to include tracking of trouble calls, outages, user problems, and resolutions, travel dates with associated costs and routine operational maintenance. The format of the report 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 format of the report 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 with regards to incidents.

· Provide SMEs to attend ad hoc meetings at the discretion of the Government PM or designee via the COR’s concurrence. 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

OR

A problem has made an important application function / system unusable or unavailable and no workaround exists.

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 shore infrastructure. In addition the contractor shall:

· Perform all troubleshooting in accordance with SPAWAR 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 and access groups as well as 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 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 that resides in the shipboard network environment in accordance with current cybersecurity policies.

· Review results of monthly network security scans to determine if corrective actions are required. Perform installation of software patches and service packs 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 and will be performed in accordance with 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. Technicians performing at this level are expected to collect the necessary data from both 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 provide appropriate support, which includes hand-off and receipt of documentation 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.3D Policy and Procedures for Handling, Distribution, and Control of Communications Security Material in the Military Sealift Command using Electronic Key Management System (EKMS)

· COMSCINSTR 3540.7 Engineering Operations and Maintenance Manual (EOMM)

· COMSCINST 4400.3 Use, Issue, and Control of Property Pass (NAVSUP FORM 155)

· COMSCINST 4400.4 Custody Control of Personal Property and Equipment

· COMSCINST 4470.1 Transportation of Supplies to Afloat Prepositioning Force (APF) Ships

· COMSCINST 4650.2 Passengers, Including Noncombatant Operation Evacuees, Onboard Military Sealift Command Controlled Ships

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

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

· 4700.16 MSC General Technical Requirements

· 4700.2 Alteration Management for MSC Ships

· COMSCINST 4750.2 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.2 Commander, Military Sealift Command, Information Technology (IT) Governance Instruction

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

· COMSCINST 5239.3 Military Sealift Command Information Assurance (IA) Policy

· COMSCINST 5239.4 Military Sealift Command Secret Media Transfer

· COMSCINSTR 5522.2 Policy for Prohibited Items and Use of Personal Electronic Devices (PEDs)

· COMSCINST 9944.1 Radio Communication System Demonstration test Package

· COMSCINST 9670.1 Allowance of Electronics Equipment for MSC Ships

· COMSCINSTR 9670.10 Installation and Maintenance of Navy Electronics in Certain MSC Ships

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

7.5 Maintenance and Sustainment Deliverables

8. 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 installation of a minor maintenance update that is beyond the capability of ship’s force and which would require touch labor to perform. The MSC IT Program Office Engineering section has overall responsibility for the ISEA function but may require support from the contractor.

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 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. Modernization Modernization involves the introduction of a new system or an upgrade to 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 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 the development and maintenance of five to seven year, class-specific, modernization plans for MSC ship, which will detail the schedule for modernization, technical refresh and system grooms.

· Assist in the development of TRANSALTS for modernization efforts.

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

· Coordinate with MSC N6 Systems Engineering efforts to support 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 observer in first low-rate initial production (LRIP) events run by MSC N6 Systems Engineering, assist MSC N6 Systems Engineering with the second LRIP event, and conduct the third LRIP event independently as preparation for shipboard deployment phase.

· Establish processes and provide the facility needed to produce systems needed 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

9.0

9.0

9.0

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

10.1 Equipment/Asset Inventory

The contractor shall perform and record results of C4 system physical inventories on MSC ships as directed by the Government. Inventories are to be performed and recorded using MSC systems and procedures identified in the MSC CDMP, COMSC Instruction 4790.3C. Inventories will include Financial Improvement Audit Readiness (FIAR) validation as required to support equipment valuation. An initial inventory reconciliation will be conducted within 90 days of contract award using sampling methodology. The initial inventory sample shall be between 5-10%. An annual inventory report will be produced each subsequent contract year.

10.2 Equipment/Asset Validation

The contractor shall perform and record the results of physical ship C4 system/equipment validations. Validations are to be performed and recorded using MSC systems and procedures identified in the MSC CDMP.

10.3 Equipment On-load or Off-load

During physical on-loads and off-loads of C4 system equipment, performed by 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 form, fit, and function of replacement C4 systems and equipment.

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

· 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, commercial and international specifications of C4 equipment.

· Provide recommendations for equipment standardization options to maximize equipment performance and reliability based on what is already 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 in accordance with 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 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 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 ship.

· As required, update configuration and logistics data/records in accordance with 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 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, as well as 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 perform analysis on 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.4

11. 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, and telephony services and the provision of Tier II help desk services to MSC afloat users. The MNOC West is located in San Diego, CA and currently serves as the primary servicing NOC for MSC ships operating globally. The MNOC East is located in Pensacola, FL and serves as the backup servicing NOC in the event of primary NOC failure. Upon completion of ongoing shipboard and NOC configuration changes, which are expected to complete in third quarter of fiscal year 2017 (Q3FY17), the MNOC West will serve as the primary serving NOC for MSC ships operating in the Pacific and Southwest Asian theaters and as a backup servicing NOC for MSC ships in the Atlantic and European theaters. MNOC East will then serve as the primary servicing NOC for MSC ships in the Atlantic and European theaters and as a backup servicing NOC for MSC ships operating in the Pacific and Southwest Asian theaters.

The MNOCs are the focal point for network troubleshooting, updating, router and domain name management, and coordination with affiliated networks, which include Navy program of record systems and services provided from the Navy’s Fleet NOCs (FLTNOCs). The MNOCs are the shore termination sites for MSC’s NGW (Inmarsat) satellite communications system and provide persistent reachback support to enable swift identification and resolution of afloat IT and communications systems issues. Functions the MNOCs currently perform include:

· Maintain and manage communications guard for MSC fleet

· Provide C2OIX-N/C2OIX-S Naval messaging services for guarded commands

· Provide classified email and messaging services for 80+ Lotus notes clients

· Provide 7/24/365 network operations and administrative support to MSC fleet

· Provide secure routing and remote access services (RRAS) to units with STE and remote dial up access.

· Provide Help Desk Tier II support to MSC units

· Provide connectivity and Tier II support for MSC’s mobile communications capability

Systems and Services currently provided by the MNOCs include but are not limited to the following:

· Non-secure Internet Protocol Router Network (NIPRNET)

· Secure Internet Protocol Router Network (SIPRNET)

· Telecommunications

· Official Information Exchange (OIX)

· Private Branch Exchange (PBX)

· Intrusion Detection System (IDS)

· Shipboard Management Information System (SMIS)

· PC-to-PC Transfer System (PPTS)

· Next Generation Wideband (NGW) Inmarsat Satellite Communications System

· Enterprise Network Operations Center (ENOC) Firewall Capability

· McAfee Host Based Security System (HBSS)

· Assured Compliance Assessment Solution (ACAS)

· Network Management and Monitoring

· Network Backup and Restore

· Microsoft Server

· Office Products

· Microsoft Exchange

· Active Directory

· Offsite Storage

· Unity Sync

· Enhanced Mitigation Experience Toolkit (EMET)

· Local Registration Authority (LRA) Services

During the period of performance for this contract, MNOC functionality is expected to transfer to the FLTNOCs. Given this, the scope of this task will shift from the day-to-day operations and sustainment of the MNOCs to support for the transition of functions to the FLTNOCs and shutdown of the two MNOC facilities.