ITESS_FY19_Performance_Work_Statement_(PWS)_REVISED.docx

Performance Work Statement Information Technology Engineering Support Services (ITESS)

1. Objectives

The objective of this contract is to obtain Information Technology (IT) Engineering Support Services that will assist the Military Sealift Command’s (MSC) Command, Control, Communications, and Computer Systems (C4S) Division (N6) in providing and sustaining Department of Defense (DoD) and Department of the Navy (DoN) compliant technical C4S solutions for MSC through execution of the performance requirements defined in section 4.0, which will satisfy emerging requirements, enhance and develop IT capabilities in support of the MSC’s mission and assist in the development of governance to ensure IT capabilities align to MSC N6’s strategic Business Support Plan, MSC N6’s technical architecture road maps, Department of Defense (DoD), and Department of Navy (DoN) mandates. The solutions primarily satisfy emergent cyber security mandates, CTOs, and technical refreshes for end of life hardware and software.

2. Scope

The Contractor shall provide IT Systems Engineering Support Services necessary to maintain, upgrade, test, develop and install new IT capabilities for MSC worldwide. All systems should be developed in accordance with the Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and assessed using the applicable checklist and benchmarks available at http://iase.disa.mil/. Compliance with and variations of these requirements shall be documented in the appropriate form as described in Task Area 8, Information Assurance (IA) Support.

The Contractor shall adhere and apply processes that are equivalent to those articulated by Capability Maturity Model Integration (CMMI) for Development, Version 1.3 (CMMI-DEV, V1.3) capability level 3. The Contractor shall also provide disciplined systems engineering and project management practices in accordance with DoD 5000.02 and shall be in compliance with all DoD and Department of the Navy (DoN) mandates and instructions, and consistent with the work requirements identified within the following Performance Work Statement (PWS).

Unless otherwise indicated, copies of the specifications, standards, and handbooks referenced in this PWS are available upon request from the Document Automation and Production Service (www.defense.gov/pubs/), 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094. MSC unique documents are available from the Military Sealift Command Head Quarters (MSCHQ), Military Sealift Command 471 East Co Street, Bldg. SP 64, Norfolk, VA 23511-2419.

In the event of a conflict between the text of this document and the references cited herein, refer to the text of this document as it takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

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

· Task Area 1 – Contract Management

· Task Area 2 – Project Management Support Services

· Task Area 3 – Systems Engineering (SE) Support Services

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

· Task Area 5 – MSC C4S Engineering Lab (MCEL) Support Services

· Task Area 6 – IT Service Management (ITSM) Support Services

· Task Area 7 – Enterprise Architecture (EA) Support Services

· Task Area 8 – Information Assurance (IA) Support Services The Contractor will be responsible for the purchase of small, consumable parts and equipment. These items include cables, CD spindle, laminating supplies, drop clothes, ear plugs and other minor items in order 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), in the role as single DoD manager for sea transportation, operates a worldwide command and a Government-owned fleet of approximately 116 ships that provides 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 ships operating with the Fleet Oiler (PM1), Special Mission (PM2), Prepositioning (PM3), Service Support (PM4), Sealift (PM5), Fleet Ordnance and Dry Cargo (PM6), Afloat Staging and Command Support (PM7), and Expeditionary Fast Transport (PM8). Each PM is responsible to COMSC for the operation, maintenance, and administrative management 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 supporting sponsor mission requirements. The technical services provided though the ITESS contract provides support all MSC PM Organizations and all ship classes 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 command, and support units located in various locations as 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.

3.1 Current Operating Environment

The MSC current operating environment Afloat includes Government owned and operated ships, Government owned and Contractor operated ships, and Contractor owned and operated ships. Additionally, MSC employs an Ashore infrastructure to support Afloat operations.

3.1.1 Ashore Environment

MSC’s IT environment operates using the following ashore networks including: Navy Marine Corps Internet (NMCI) Continental United States (CONUS), Overseas Navy Enterprise Network (ONE-NET), Outside the Continental United States (OCONUS), MSC Data Centers Continental United States (CONUS) and Afloat Network Operations Center (ANOC) and Back-Up Network Operations Center (BNOC) (CONUS) for the continued operations of IT networks and systems support.

MSC’s ashore desktop operating environment is currently various Microsoft Windows environments.

MSC’s current ashore server operating environment includes Windows, UNIX and LINUX environments at the Navy's Enterprise Data Center (NEDC), ANOC, and BNOC. Desktop applications include both standard off-the-shelf software products such as the Microsoft Office Suite and other common Windows software. In addition, MSC has a wide variety of Commercial-Off-The-Shelf (COTS), Government-Off-The-Shelf (GOTS), and legacy applications on user desktops including Standard Shipboard Automated Maintenance Management (SAMM), Shipboard Configuration and Logistics Information (ShipCLIP), Human Resource Management System (HRMS/Department Head Afloat Management System DHAMS) and Financial Medical System (FMS), Budget Preparation System (BPS), Logistics and Engineering System (LES)

3.1.2 Afloat Environment

The network infrastructure deployed on MSC ships includes a combination of MSC designed and developed systems as well as Navy Program of Record (POR) systems.

3.1.2.1 Shipboard Management Information System

Unclassified (SMIS-UNCLASS) Network, Attachment J-001, consists of workstations, primary and backup domain controllers, a database server, a switch, router, Dynamic Host Configuration Protocol (DHCP) and, accelerator, encryptor/decryptor, and link to the ANOC via satellite transport services. The MSC Shipboard SMIS-UNCLAS environment currently operates using Microsoft operating systems and Internet Explorer. The workstations utilize various Government-off-the-shelf (GOTS), Commercial-off-the-shelf (COTS), and Shipboard Management Information System (SMIS) applications and software. Depending on the hull type of an MSC ship, the number of on board workstations can range from 15 to 120. This system is currently deployed on 68 MSC ships. MSC is currently in the process of providing a network upgrade to the deployed system and has numerous In-Service Engineering Activity (ISEA) And Software Support Activity (SSA) activities ongoing including upgrading End of Life (EoL) hardware and workstation operating systems. The SMIS-UNCLAS hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.2 Shipboard Management Information System

Classified AFLOAT Classified GOSUP(V)2 (ACG(V)2) Attachment J-002, includes a single Server running Microsoft Exchange and thin-client workstations running Windows. Exchange servers and client desktops runs in a virtualized server environment. Data for Active Directory, DNS, and Exchange is replicated among local and remote domain controllers. This system is currently deployed on 34 MSC ships. MSC is presently executing a Non-Recurring Engineering (NRE) project to upgrade and replace EoL hardware and software, which includes upgrades to servers, routers, storage and workstations, and server and workstation operating systems. Low-Rate Initial Production (LRIP) and deployment scheduled FY18Q4. The SMIS-CLASS network hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.3 Shipboard Management Information System (SMIS)

SMIS Unclassified Mini (SMIS-UNCLASS-Mini), Attachment J-0013, Standalone workgroup with reach back to the Afloat Network Operations Center (ANOC). The system includes a desktop-laptop workstation environment. This system is currently deployed on 21 MSC ships. MSC has recently completed the Low Rate Initial Production (LRIP) phase of the system upgrade. Fleet deployment is in progress. The SMIS-UNCLAS-Mini hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.4 Shipboard Management Information System

SMIS Classified Mini (SMIS-CLASS-Mini), Attachment J-0014, Stand-alone workgroup with reach back to the ANOC. The system includes a desktop-laptop workstation environment and is currently deployed on 56 MSC ships. MSC has recently completed the LRIP phase of the system upgrade and MSC fleet deployment is in progress. The SMIS-CLASS-Mini hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.5 Shipboard Management Information System

Unclassified Workgroup (SMIS-UNCLAS-WG), Is a standalone unclassified network deployed on MSC Ocean Surveillance Ships. This system is currently deployed on 6 MSC ships. The SMIS-UNCLASS-WG hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.6 Integrated Shipboard Network System (ISNS) / Common PC Operating System Environment (COMPOSE)

ISNS/COMPOSE is a Navy POR supported system that provides a common network infrastructure across multiple security domains and supports cross-domain and coalition operations. COMPOSE combines commercial-off-the-shelf (COTS) and government-off-the-shelf (GOTS) products to deliver directory services, e-mail, Web acceleration, office automation applications, collaboration tools and antivirus software for the Integrated Shipboard Network System (ISNS), Combined Enterprise Regional Information Exchange System (CENTRIXS).

3.1.2.7 Standalone and Single PC Solutions

MSC deploys a number of standalone and single PC solutions:

PC to PC Transfer System (PPTS) - Provides 71 MSC ships with the capability to receive and transmit classified and unclassified data with the MSC Afloat Network Operations Center (ANOC) and the DoD Information Network (DoDIN). Architecture includes a Commercial-Off-The-Shelf (COTS) workstation and a secure telephone (STE).

Navigation Aids (NAVAIDS) - Designed to provide navigation planning applications used by navigators to do celestial, chart planning, tides and waypoint marking. The NAVAIDS are loaded on a single, standalone workstation not connected to the network. The NAVAIDS are updated via CDs due to the size of the updates. The collection of NAVAIDS provides tidal predictions, celestial navigation, 3-D harbor visualizations, navigational routing, and electronic charting display capabilities.

The hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

3.1.2.8 Integrated Navy Program of Record (POR) Systems

The integration and test for various Navy POR systems is required to interface with the MSC SMIS Networks. Engineering Support Services for the Afloat environments include the following effort:

Naval Modular Automated Communications System (NAVMACS) - A ship-to-ship or ship/shore/ship message processing system. NAVMACS processes and records all incoming and outgoing message traffic and serves as an automated shipboard terminal for the Common User Digital Information Exchange System (CUDIXS). The NAVMACS system architecture provides an RS-232 serial output capability which interfaces with MSC ACG(V)2.

Assured Command and Control (AC2) Modem integration efforts – The AC2 effort is required to integrate an additional modem onto MSC’s Next Generation Wideband (NGW) connected networks for network monitoring in a reduced operating status.

These hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of each system’s life cycle.

3.1.2.9 Pilot Systems

Engineering Support Services for the Afloat environments also includes system or software rapid prototyping efforts such as:

Visual Information (VI) Pilot-VI- Related to tactical level operations is required to be forwarded in a timely and accurate manner through the operational chain of command to help achieve operational objectives, support the combatant commanders' communication strategies and potentially counter propaganda. The ability to collect, process and disseminate VI is essential to achieve timely, factual information for operational decision-making, intelligence analysis and public information. me operations centers within 60 minutes of a reportable event.

Own Force Monitoring – Monitors the ship’s RF emissions and reports compliance with the emissions control (EMCON) condition currently in effect.

The hardware and software technical refresh efforts will actively be supported through MSC N6 In-Service Engineering throughout the duration of the life cycle.

4. Performance Requirements

4.1 Task Area – 1 Contract Management

The Contractor shall provide all necessary personnel, administrative, financial, and managerial resources necessary for the performance of this task. The Contractor shall designate a single point of contact (POC) as the Contract Manager (CM) who is responsible for fielding and responding to Government identified issues, concerns, or problems on this task order. The CM shall have the authority to direct the Contractor’s organization and make decisions for the Contractor’s organization in response to the Government identified issues, concerns, or problems. The CM shall be readily available to field and respond to the Government’s inquiries. The CM shall also be the designated POC to alert the Government to potential contractual/technical issues. Although Government staff may coordinate with other Contractor staff, the CM shall serve as the single Contractor POC responsible for resolving all issues, concerns, and problems. The CM position description and requirements are defined in section 12.1.

The Contractor shall provide a draft Contract Management Plan (CMP) in accordance with CDRL A103 to the MSC Contracting Officer’s Representative (COR), Michele Gordon (757) 443-0873 Michele.Gordon@Navy.mil, at the Kick-Off Meeting. Effective Contract Management will ensure that all contractor support assigned to this task are coordinating and leveraging processes already in place or being developed. This effort will include the overall management of Contractor resources assigned to the resultant contract as well as reporting to and direct interaction with the COR and the Alternate Contracting Officer’s Representative (ACOR), Earl Munrath (757) 443-3127 Earl.Munrath@Navy.mil. Contract Management support shall include 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.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 five (5) business days of contract 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 (as defined in section 12) and key MSC personnel. At the kick-off meeting, the Contractor shall present its Transition Plan for overall contract management of the awarded task order in accordance with Contract Data Requirements List (CDRL) A101. The Contractor shall develop and, after Government approval, distribute meeting minutes and action items within five (5) business days after the kick-off meeting in accordance with CDRL A102.

4.1.2 Contract Management Plan

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

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

h. delivery procedures

i. tests

j. certifications

k. packaging

l. shipping

m. other Data Item Description (DID) DI-MGMT-80004A may be used and tailored with the Government’s concurrence.

4.1.3 Contract Management Reviews

The Contractor shall prepare and submit a Contract Management Review (CMR) agenda to the COR five (5) business days prior to the CMR meeting in accordance with CDRL A104. The Contractor shall also prepare minutes for the CMR within five (5) business days after the meeting in accordance with CDRL A105. The Contractor shall prepare the actual CMR to be delivered the day of the review in accordance with CDRL A104. The CMR shall address current status to include current task order technical management and execution in comparison with task order planned activities, mitigation plans for under-performing areas, and all other risks, issues and concerns that may occur. The CMR shall summarize the previous three (3) months project execution and agreement with the Contract Management Plan. The CMR will define the work planned and projected for the subsequent three (3) months. The first review will be conducted one month following award. Subsequent reviews will be conducted at monthly intervals. The CMR will occur 30 days from contract award, reoccurring monthly as determined by the COR and Contractor PM.

4.1.4 RESERVED

4.1.5 Performance Cost Reporting

The Contractor shall prepare and submit a report concurrently with each invoice presented for payment in accordance with CDRL A108. The report shall include a status for every deliverable for the specific task order (to include base contract deliverables if applicable). The Contractor shall create and the Government approve a status report template prior to the first submission.

4.1.6 Information Assurance

The Contractor shall comply with the latest MSC Information Assurance Policy. Current policy is detailed in MSC Instruction (COMSCINST 5239.3 series, Attachment J-004). Compliance with this directive is mandatory during the execution of design, development, and implementation and maintenance tasks within the following PWS.

The Contractor shall comply with the DoD Information Assurance Workforce Improvement Program (DoD 8570.01-M Attachment J-005). The Contractor shall use only certified personnel for all task(s) performed under this task order where certification is a requirement in accordance with DoD 8570.01-M.

4.1.7 Quality Assurance

The Contractor shall have at contract award, and shall maintain, an existing quality management system per the International Organization of Standards ISO 9001:2000 or above which is standard for all work performed at the Contractor’s facilities and onsite in support of this effort. The Government reserves the right to require the Contractor to present its current ISO 9001 certificate of compliance at any time. The Contractor shall, in addition, support all MSC ISO 9001assessments by adhering to N6 processes for work performed under this effort.

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 in accordance with CDRL A109. 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 the Government’s concurrence.

4.1.8 Configuration Management

The artifacts used to engineer the systems and networks developed and sustained under this contract will need to produced, updated and maintained to accurately reflect the Technical Data Packages for all deployed instances. The Contractor shall implement a Configuration Management (CM) system which complies with the following requirements:

a. Establishes initial hardware and software baseline of requirements. This baseline shall include hardware drawings and software programs and code which represent the delivered end items.

b. Perform CM reviews during formal technical program reviews at the Contractor and subcontractor facilities that verify the high level system requirements have been incorporated and implemented into the evolving detail baseline.

c. A change control system for identifying, evaluating, dispositioning, and implementing proposed hardware and software changes to the established baseline.

d. A system that provides for periodic audits, including subcontractors, to ensure the overall requirements and objectives of the program are being accomplished and satisfied.

The Contractor shall provide a Configuration Management Plan documenting all CM areas included in the above section (4.1.8) of this PWS and shall do so in accordance with CDRL A110. MIL-HDBK-61 may be used for guidance when doing so. Data Item Description (DID) DI-SESS-81875 may be used, tailored with the Government’s concurrence.

4.1.9 Communications

The Contractor will develop and organize the communications strategy necessary to keep key stakeholders, and project team leads informed as projects move through each of the life cycle phases (i.e. Requirements Definition, Design, Implementation, Test & Evaluation, Deployment) of the engineering processes and shall provide technical support by assisting MSC in drafting plans, Standard Operating Procedures (SOPs) and other guidance documents as pertain to this PWS.

4.1.10 Staffing

The Contractor is required to provide resources with required project management, systems engineering and IT Service Management competencies in accordance with the MSC Service Delivery Overarching Framework (Attachment J-006) and Enterprise Project Management Handbook (Attachment J-007).

4.1.11 Phase-In / Phase-Out Plans

Phase-In Plan: No later than five (5) business days after the contract kick-off meeting, the Contractor shall develop, with Government input, a plan of action to ensure the smooth transition of services from the predecessor Contractor to the new Contractor with no degradation of services in accordance with CDRL A112.

Phase-Out Plan: No later than 120 calendar days prior to the end of the contract, the Contractor shall develop, with input from the Government, a plan of action to facilitate the transition of services to the incoming Contractor with no degradation of services in accordance with CDRL A113.

4.1.12 Contract Management Deliverables

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

4.2 Task Area 2 – Project Management Support Services

The Contractor shall provide support for Project Management and Technical Management Processes through engineering and technical projects supporting the N61 Program Management Office in accordance with DoD Instruction (DoDI) 5000.02, DoN mandates, Cybersecurity (Information Assurance) policies, standards, instructions and directions. Project Management support services ensure the engineering, logistics and maintenance and support planning and execution for MSC IT systems, operators and sustainers to resolve availability and supportability issues, to assist in gathering logistics and system data, and in training especially during introduction of new or newly modified systems. Additionally, this task will be used to ensure management and control of activities, review of the scheduled milestones and the Technical Data Package (TDP) baseline. A technical data package (TDP) is a collection of artifacts for supporting an acquisition, production, engineering, and logistics support (e.g. Specification, Architecture Drawings, Test Procedures, Engineering Data for Provisioning, Training, and Technical Manuals). The description defines the required design configuration or performance requirements, and procedures required to ensure adequacy of item performance. It consists of applicable technical data such as SOPs, models, drawings, associated lists, specifications, standards, performance requirements, QAP, software documentation and packaging details.

4.2.1 Project Management Reviews

The Contractor shall prepare and submit a Project Management Review (PMR) agenda to the COR and ACOR within five (5) business days prior to the PMR meeting in accordance with CDRL A201. The Contractor shall also prepare minutes within five (5) business days after the meeting in accordance with CDRL A202. The Contractor shall prepare a Project Status Report (PSR) to be delivered the day of the review in accordance with CDRL A203. The PMR shall address current project status to the Government including performance, performance metrics, mitigation plans for under-performing areas and risks, issues and concerns. The PMR shall summarize the previous month’s performance and overall consistency with the project plan. The first review will be conducted one month following each project kick-off. Subsequent reviews will be conducted at monthly intervals.

4.2.2 Travel

The Contractor shall be required to support various IT Engineering Support Services, including ship site surveys to support requirements elicitation in upgrading existing systems and validation configurations for system installation during Low-Rate Initial Production (LRIP) deployment activities. Additionally the Contractor will be required to travel in support of the Type Desk audit activities.

4.2.2.1 Travel Request

In response to COR or ACOR requested travel the Contractor shall develop and deliver a trip request 10 business days prior to any travel in accordance with CDRL A216. The travel request shall include detailed travel information as well as specific details for the purpose, requirements, associated costs, objectives, purpose, summary of activities, and the name of individuals traveling.

4.2.2.2 Trip Report

The Contractor shall develop and deliver a trip report within five (5) business days after the conclusion of all travel in support of project efforts while containing detailed travel information and accomplishments in accordance with CDRL A217. It shall contain sufficient detail of the travel information including:

· Dates

· Purpose

· Location

· Dates at Site

· Personnel Contacted

· Summary

· Chronology of Events

· Observations

· Deliverables Left

· Training Provided

· System & Software Performance & metrics

· Action Items

· Conclusion

· Recommendations

4.2.7 Project Management Deliverables

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

4.3 Task Area 3 – Systems Engineering (SE) Support Services

The Contractor shall provide technical and engineering support services to ensure the development, integration, deployment and sustainment of systems to provide solutions for emergent requirements, modifications to existing systems and equipment, and the correction of systems or equipment deficiencies. The systems engineering process framework is a collection of technical management processes and technical processes applied through the systems development and acquisition lifecycle. The technical management processes are technical planning, configuration management, Interface management, technical data management, requirement management, risk management, technical assessment, and decision analysis. The technical processes are stakeholder requirements definition, requirements analysis, architecture design, implementation, integration, verification, validation and transition. The Contractor shall provide systems and software engineering support services compliant with all DoD and DoN policy and guidance as defined by the DON CIO (http://www.doncio.navy.mil/Policy.aspx) and Office of the Deputy Secretary of Defense (https://www.acq.osd.mil/se/pg/guidance.html). The Contractor shall be given additional technical direction or clarification to accomplish work via individual task orders (TOs).

4.3.1 Engineering Studies and Analysis Services

The Contractor shall perform engineering studies and analysis for requirements definition, operations concept definition, systems engineering decisions, trade studies, analysis of alternatives (AoA), and system definition in support of efforts in the formulation, implementation, sustainment and/or operations phases. Tasks cover a broad range of mission and system domain areas.

4.3.2 Requirements Engineering Support Services

The Contractor shall provide requirements engineering support services to ensure the correct and accurate development of new capabilities and modifications to existing systems and equipment, and correction of deficiencies in existing systems and equipment. Such efforts shall include examining existing requirements for establishing baselines for new systems and equipment, while defining how best to meet these requirements as well as evaluating existing systems and equipment for possible improvement. The Contractor shall conduct technical studies and evaluations to determine the cost and feasibility of implementing systems engineering concepts. Successful completion of the requirements engineering and definition phase shall be determined by a completed Systems Engineering Technical Review (SETR) demonstrating the system is mature and ready to move to the next phase of the lifecycle. All Requests for Action (RFAs) produced during the SETR will be closed prior to moving to the next phase of the life cycle. The Naval Systems Engineering Technical Review Handbook – Version 1.0 (Attachment J-15) may be used for guidance in preparing and conducting the SETR.

4.3.3 Design Engineering Support Services

The Contractor shall conduct system, subsystem and component design engineering on specific systems architecture and conduct system design engineering on new or existing systems undergoing improvement modifications with current and future system performance considered. Successful completion of the design phase shall be determined by a completed Systems Engineering Technical Review (SETR) demonstrating the system is mature and ready to move to the next phase of the lifecycle. All Requests for Action (RFAs) produced during the SETR will be closed prior to moving to the next phase of the life cycle. The Naval Systems Engineering Technical Review Handbook – Version 1.0 (Attachment J-15) may be used for guidance in preparing and conducting the SETR.

4.3.4 Implementation and Integration Support Services

The Contractor shall provide implementation and integration services to establish total systems and software capable of providing user requirements. Successful completion of the Implementation and Integration phase shall be determined by a completed Systems Engineering Technical Review (SETR) demonstrating the system is mature and ready to move to the next phase of the lifecycle. All Requests for Action (RFAs) produced during the SETR will be closed prior to moving to the next phase of the life cycle. The Naval Systems Engineering Technical Review Handbook – Version 1.0 (Attachment J-15) may be used for guidance in preparing and conducting the SETR.

4.3.5 Test and Evaluation Support Services

The Contractor shall provide systems Developmental Test (DT) and Operational Test (OT) support services to verify & validate systems and software meet user requirements. Successful completion of this effort shall be determined by a completed Systems Engineering Technical Review (SETR) demonstrating the system is mature and ready to move to the next phase of the lifecycle. All RFAs produced during the SETR will be adjudicated and remediated IAW the Naval Systems Engineering Technical Review Handbook, section 8.0 Request For Action/Request For Information Process, Attachment J-15.

4.3.11 Systems Engineering (SE) Deliverables

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, a System Engineering Management Plan (SEMP) that addresses a contractors overall systems engineering management approach and shall be used as a foundation for technical, resource, production, test and evaluation, and management planning for all Systems Engineering support activities in accordance with CDRL A209. The Contractor shall provide a draft SEMP at contract kick off and an updated SEMP within 30 calendar days after the kick-off meeting. Specific deliverables required to meet specific engineering requirements shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

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

The Contractor shall provide In-Service Engineering Activity (ISEA) support for existing and/or newly developed systems and equipment. ISEA activities are delegated functions by, and in support of the engineering program manager for the overall engineering, test, maintenance, technical analysis and logistics requirements incident to specific operational equipment. ISEAs are typically utilized by a government organization providing field changes after initial system fielding have occurred. This effort includes, but is not limited to performance analyses, problem identification and solution development for MSC systems. Continuous ISEA activities shall be performed primarily for the SMIS Systems and associated with hardware tech refresh efforts associated with life cycle maintenance and support. Additionally, as a function of ISEA the Contractor shall provide a Software Support Activity (SSA) to ensure integration of software used by MSC Systems is compliant with emergent Cyber Security requirements. Contractor shall provide a Software Support Activity (SSA) to ensure MSC Systems are compliant with emergent Cyber Security requirements as changes are made to workstation and server software configurations. The SSA will provide support to integrate and test new and updated software into the SMIS Networks, which includes support for commercial and non-commercial software, Microsoft Windows 10 (or current) Secure Host Baseline (SHB) and Microsoft Server 2016 (or current) Deployment schedules.

4.4.2 In-Service Engineering Activity (ISEA) Deliverables

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, an In-Service Plan and Procedures that shall be used as a foundation for technical, resource, production and management planning for all ISEA support in accordance with CDRL A401. The Contractor shall provide the ISEA Plan & Procedures 30 calendar days following contract award. Specific deliverables required to meet emergent requirements shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

4.5 Task Area 5 – MSC C4S Engineering Lab (MCEL) Support Services

The Contractor shall provide technical services to ensure the MCEL is maintained in accordance with all current Navy mandates. The Contractor must ensure the lab is continuously capable of providing C4 network development and software integration and validation environment for the MSC Shipboard Management Information Systems (SMIS) Afloat classified and unclassified environments. The MSC C4 Engineering Lab (MCEL) fills a critical role for the C4 program, providing a facility to support the design, development, testing, and troubleshooting of C4 capabilities, ensuring MSC Afloat IT systems are developed to a rigorous systems engineering standard prior to their use in the MSC fleet. The purpose of the lab is to provide C4 network development and software integration and validation for the MSC Shipboard Management Information Systems (SMIS) Afloat classified and unclassified environments.

The Contractor shall ensure the MCEL is maintained in accordance with all current Navy mandates. The Contractor must provide the Government a MCEL Management Plan in accordance with CDRL A501. The MCEL Management Plan must include the detail of the following vital MCEL activities.

4.5.1 MCEL Support Deliverables

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, a MCEL Management Plan and MCEL Operational Procedures that shall be used as a foundation for technical, resource, production and management planning for all ISEA support in accordance with CDRL A501 and A502. The Contractor shall provide a MCEL Plan & Procedures draft 30 days following contract award with a final copy due 60 days following contract award. Update as required to reflect modifications to MCEL configuration Specific deliverables required to meet emergent requirements shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

4.6 Information Technology Service Management (ITSM) Support Services

The Contractor shall provide IT Service Management Support Service to provide support for Service Validation and Test (SV&T) and Service Asset and Configuration Management (SACM) Support Services and Change Management. The Contractor shall provide SV&T services to support testing new and updates software. The MCEL currently supports on average 60 Service Validation and Testing activities annually; the duration of each SV&T activity is on the average 5 business days. The SV&T function shall include support for OT&E testing in support of LRIP activities. The Contractor shall create Service Validation and Testing (SV&T) Support Plan describing the test scripts to be performed in the Validation Testing for each new or revised MSC C4 system.

4.6.1 Service Validation and Testing (SV&T) Support Plan

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, a Service Validation and Testing (SV&T) Support Plan that shall be used as a foundation for technical, resource, and management planning for all SV&T support in accordance with CDRL A601. The Contractor shall provide the SV&T Support Plan within 30 calendar days after the kick-off meeting. Specific deliverables required to meet emergent requirements shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

4.7 Task Area 7 – Enterprise Architecture (EA) Support Services

4.7.1 Enterprise Architecture Content Development

The Contractor shall be familiar with and perform the functions involved in Enterprise Architecture (EA). MSC defines these functions as: EA Development, EA Maintenance, EA Change Management, and EA Repository Maintenance. In accordance with the Clinger-Cohen Act, the Office of Management and Budget (OMB) EA Assessment Framework 3.1 and the policies of the Government Accountability Office (GAO) EA Management Maturity Framework version 2.0, Section 2. The Office of Management and Budget (OMB) Enterprise Architecture Assessment Framework (EAAF) version 3.1 identifies the measurement areas and criteria by which agencies are expected to use the EA to drive performance improvements.

4.7.2 Enterprise Architecture Deliverables

The Contractor shall develop, deliver, and maintain throughout the contract period of performance, an EA Change Management Plan that shall be used as a foundation for all configuration, change and data management planning and execution for all EA support in accordance with CDRL A708. The Contractor shall and provide an EA Change Management Plan within 30 calendar days after contract award with annual updates. Specific deliverables required to meet emergent EA Project requirements shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

4.8 Task Area 8 – Information Assurance (IA) Support

4.8.1 Requirements for Contractor Provision of Security Plan, IA Controls

The Contractor shall establish an IA Program to implement and sustain appropriate IA management, operation, and technical controls and processes required to safeguard DoD non-public information resident on or transiting the Contractor’s unclassified information systems from unauthorized access and disclosure. Protection measures applied must be commensurate with the risks (i.e., consequences and their probability) of loss, misuse, unauthorized access, or modification of information. The Contractor shall submit for Government approval (Authorization to Operate) an overarching security plan that describes their strategy for implementation of IA and Industrial Security requirements throughout the life of the contract in accordance with CDRL A801. The security plan shall address the security controls described in (DoDI) 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) and should be tailored in scope and depth appropriate to the effort and the specific unclassified DoD information. Draft of overarching security plan described in CDRL A801 a draft plan shall be delivered to the government within 30 days of contract award, the final due 90 days following contract award. The final Security Plan shall be delivered before the Government data is stored, transmitted, or received on the Contractor systems.

4.8.2 Continuous Monitoring Strategy

As part of the RMF Security Authorization process the Contractor shall, in conjunction with the program office and Security Control Assessor, develop a system-level strategy for the continuous monitoring of the effectiveness of security controls employed within or inherited by the system, and monitoring of any proposed or actual changes to the system and its environment of operation in accordance with CDRL A812. The strategy must include the plan for annual assessments of a subset of implemented security controls, and the level of independence required of the assessor (e.g., ISSM or SCA). The system-level continuous monitoring strategy must conform to all applicable published DoD enterprise-level or DoD Component-level continuous monitoring strategies (e.g., DoD’s ISCM Strategy) to ensure the complete set of planned, required, and deployed security controls within an information system or inherited by the system continue to be effective over time in light of the inevitable changes that occur.

4.8.3 Information Assurance Support Service Deliverables

Specific deliverables required to meet emergent IA requirements or requirements related to individual engineering efforts shall be provided via individual task orders. All deliverables shall be provided electronically, in a Microsoft (MS) Office commercially available product format unless otherwise defined.

Task

5. Place of Performance

Tasks will be performed primarily at the Contractor site and on site at Naval Station Norfolk. The Contractor shall participate in meetings at Naval Station Norfolk; therefore, travel to and from the Contractor site will be required on an as needed basis. The Contractor shall be expected to keep abreast of current activities and meetings to ensure that appropriate personnel are on site as needed.

Furthermore, all tasks may require travel to other MSC, Navy, and USTRANSCOM or DOD installations to include but not limited to:

· MSC and U.S. Navy vessels worldwide

· MSC ANOC, San Diego, CA

· MSC MDRS, Pensacola, FL

· MSC, San Diego, CA

· MSC, Yokohama, Japan

· MSC, Naples, Italy

· USTRANSCOM Headquarters, Scott AFB, IL

· Navy Data Centers

6. Contract Phase In / Phase Out Period

6.1 Task Order Phase-In Period

Following award, there will be up to a 30 day phase-in period. The purpose of the phase-in period is to ensure a smooth transition of services. Immediately following award, the Contractor shall commence review of all tasks to be performed under this contract. Prior to the contract kick-off meeting, the Contractor shall develop, with Government input, a plan of action to ensure the smooth transition of services. At the end of the phase-in period, the Contractor shall be responsible for full performance in accordance with the terms of the contract.

6.2 Task Order Phase-Out Period

There will be a task order phase-out period commencing 30 days prior to end of the task order. The purpose of the phase-out period is to ensure a smooth transition of services from the predecessor Contractor to the new Contractor. The Contractor shall provide the services necessary to ensure a successful transition of services from it to the awardee under a subsequent contract for the same or similar requirement. No later than 120 days prior to the end of the task order, the Contractor shall develop, with input from the Government, a plan of action to facilitate the transition of services to the incoming Contractor with no degradation in services.

7. Deliverables

All deliverables will be prepared using Microsoft Office and Adobe compatible products. If non-compatible software is used, the Contractor must obtain COR written approval.

All deliverables, unless specified by the COR or the Contracting Officer, shall be delivered by posting to the existing N6 Collaboration Site. Access to the N6 Collaboration Site will be provided by the Government, as required.

All deliverables shall comply with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) and the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology (EIT) Accessibility Standards (36 CFR part 1194). Exception to this must be approved in writing by the COR or Contracting Officer.

8. Security

8.1 Security Classification

The Contractor shall comply with security requirements in accordance with Department of Defense Instruction 5220.22M (National Industrial Security Program Operating Manual).

All work under the task order is UNCLASSIFIED – BUSINESS SENSITIVE unless otherwise stipulated.