Attachment 1_Draft CMDS PWS.docx

Logistics (LOG) IT Capability Modernization, Deployment, and Support (CMDS) Performance Work Statement (PWS)

Scope:

Background

Logistics IT Portfolio Overview Program Executive Office (PEO) Manpower, Logistics, and Business Solutions (MLB) manages the Logistics (LOG) Information Technology (IT) portfolio which is composed of 300+ afloat and ashore IT systems/applications with 150,000+ users across all Naval Systems Commands (SYSCOMs) and Naval Operational Forces (NOF) to include ships, carriers, submarines, USN/USMC aviation squadrons, and Naval Expeditionary Forces. The United States Coast Guard (USCG) is a joint user of LOG IT capabilities and will be considered as a part of the program requirements. LOG IT enables essential business operations, including the following capability pillars:

1. Naval Maintenance, Repair, and Overhaul (N-MRO)

· Plan, predict, schedule, and execute maintenance at the Organizational, Intermediate, and Depot levels

2. Naval Supply Chain Management (N-SCM) / (Naval Operational Supply System (NOSS))

· Plan, procure, receive, store, distribute, dispose and manage material, goods and services across all commodities and communities

3. Naval Product Lifecycle Management (N-PLM)

· Manage weapon system technical data required for life cycle support (configuration, Bill of Material, 3D models, readiness models, drawings, maintenance procedures)

· Provide workforce automation, optimization, and process standardization for program lifecycle management; integrate acquisition with the warfighter

4. Integration & Infrastructure (I&I)

· Facilitates data exchange and integration between modernized, legacy, and external IT systems

· Enables synchronization of enterprise and edge instances of all portfolio components

· Includes Logistics Information Network Connector (LINC) which provides a common platform hosting environment for LOG IT systems and applications

5. Logistics Integrated Data Environment (L-IDE)

· Aligning readiness data systems to support the other 4 pillars, enable analytics, and supports broader data efforts

N-MRO, N-SCM, N-PLM, L-IDE, and I&I capability pillars are currently undergoing modernization and limited deployment through Other Transaction Authority (OTA) orders and other means. LOG IT is also working closely with PEO MLB's technical team to align capability pillars to the Department of Navy (DON) initiatives.

Logistics IT Integration and Support Overview

Logistics IT Integration and Support (LIIS) is a series of acquisitions to provide efficient shared services to the LOG IT portfolio. LIIS consists of two acquisitions to accomplish the following goals:

· Acquisition #1 LOG IT Portfolio Integration (PI) – Performs Portfolio and System of Systems (SoS) level tasks:

· Goal #1: Portfolio Management – Portfolio management and integration of common capabilities, data, and support services. Improve service performance and reduce operational costs through reduction/elimination/automation of duplicative services, capabilities, and data sets.

· Goal #2: Integrated Platform and Develops Pipeline – Implementation of an agile development process and an adaptable architecture for continuous modernization, integration, migration; and accelerate speed to fleet of logistics capabilities.

· Acquisition #2 [This PWS]: LOG IT Capability Modernization, Deployment, and Support (CMDS) – Perform program/system level tasks:

· Goal #3: Continuous CMDS – continuous CMDS of the N-MRO, N-SCM, N-PLM, L-IDE, and I&I capability solutions as part of or within the integrated platform and Develops pipeline.

This CMDS PWS is for Acquisition #2 only. This LOG IT CMDS PWS describes the continuous capability modernization, deployment, and support tasks for the LOG IT systems undergoing modernization.

Service Requirements and Lot Overview

CMDS service requirements are organized into three Lots:

· LOT 1: Capability Modernization (2.1.1)

· Design (2.1.1.1)

· Development (2.1.1.2)

· Technical Manuals (2.1.1.3)

· Integration (2.1.1.4)

· Market Research & Prototyping/Piloting (2.1.1.5)

· Capability Solution Delivery (2.1.1.6)

· LOT 2: Operations Support Planning and Sustainment (2.1.2)

· Supportability Plan (2.1.2.1)

· Manpower, and Personnel, and Analysis (2.1.2.2)

· Training Support Services (2.1.2.3)

· IT Service Management Processes (2.1.2.4)

· Service Level Management (2.1.2.5)

· Release and Deployment Management (2.1.2.6)

· Service Desk Request Fulfillment (2.1.2.7)

· Implementation (2.1.2.8)

· Deployment (2.1.2.9)

· Sustainment (2.1.2.10)

· LOT 3: Afloat Installation (2.1.3)

· Design, Integration, Configuration or Installation of Hardware and Software (2.1.3.1)

· Applicable Documents for Afloat Installation Services (2.1.3.2)

· Platform Preparation Requirements (2.1.3.3)

· Afloat Design Documentation (2.1.3.4)

· System Operational Verification Test Development (2.1.3.5)

· Electromagnetic Environmental Effects (2.1.3.6)

· Contractor Furnished Material (2.1.3.7)

· Installation Tasks (2.1.3.8)

· Removal (2.1.3.9)

· Submarine Safety Program (SUBSAFE) Work (2.1.3.10)

· System Operational Verification Test Support (2.1.3.11)

· System Operational Verification Test (Performance (2.1.3.12)

· Afloat Installation Logistic Support Documentation (2.1.3.13)

· Technical Assistance (2.1.3.14)

· Fault Isolation and Repair (2.1.3.15)

· Formal Corrective Action Responses and Root Cause Analysis (2.1.3.16)

· Safety (2.1.3.17)

· Clean-up (2.1.3.18)

System Scope

Scope for the LOG IT CMDS PWS is for LOG IT systems to be modernized and those LOG IT systems requiring afloat installation. Targeted systems/programs for each task lot include, but not limited to the following:

LOT 1 and LOT 2:

· N-MRO modernization, including the following systems:

· N-MRO

· Enterprise Remote Monitoring (eRM)

· Maintenance Engineering Ground Station for Aviation (MEGA)

· N-SCM modernization, including the following systems:

· Naval Operational Supply Solution (NOSS)

· N-PLM modernization, including the following systems:

· Aviation Product Lifecycle management (AvPLM)

· Model Based Product Support (MBPS)

· L-IDE modernization, including the following logistics data sub-domains:

· Aviation – DECKPLATE

· Maritime

· Model Based Product Support (MBPS)

· Ship Maintenance Data Improvement Initiative (SMDII)

· Navy Maritime Maintenance Enterprise Solution (NMMES) – Data capability only

· Supply – NOSS TBD

· I&I modernization, including the following systems:

· Joint Delivery Management System (JDMS)

· Joint Technical Data Integration (JTDI)

· Enterprise Service Bus (ESB)

· LINC

LOT 3: Include those listed above for Lots 1 and 2, as well as the following major LOG IT Systems afloat:

· Naval Tactical Command Support System (NTCSS)

· Maintenance Figures of Merit (MFOM)

Requirements

Work must meet the specifications in Section 3.

Logistics IT Capability Modernization, Deployment, and Support Service Requirements

The Government requires technical services for the modernization, deployment, and support of Logistics IT capability solutions.

[LOT 1] Capability Modernization

The Contractor shall:

· Configure, develop, and integrate new or modified software/hardware capabilities;

· Conform to appropriate LOG IT program standards;

· Develop data migration and cutover strategies and scripts to support the installation teams; and

· Provide schedules, architectures, Technical Data Packages to the Government.

Design The Contractor shall design a solution based on modern Commercial-off-the-shelf (COTS) technologies to minimize customization, to maximize reuse, and to leverage commercial cloud services, which:

· Incorporates retained applications as part of the overall solution;

· Incorporates DoD and commercial common standards, common architectures, and common parts into a comprehensive product or service;

· Designs for integration and synchronization of future products and services with existing product and service solutions; and

· Reuses and reconfigures existing applications as needed to support the optimal future state design.

Design Documentation The Contractor shall:

· Develop, update, and deliver a System/Subsystem Design Description (SSDD) (CDRL TBD) with associated architecture, network, system/design diagrams, and Database Design Descriptions (DBDDs) (CDRL TBD) that addresses the relationship and integration of COTS software with the overall capability;

· Develop, update, and deliver an Interface Control Document (ICD) using Data Item (DI)-SESS-81876 (CDRL TBD); and

· Develop, update, and deliver an Interface Design Description (IDD) (CDRL TBD) and Interface Control Agreement (ICA) (CDRL TBD) for each system interface in accordance with the Interface Control Document (ICD).

· Develop, update, and deliver test documentation including Test Scripts, Test Plans, Test/Use Cases (CDRL TBD).

Fit/Gap Analysis The Contractor shall:

· Conduct a fit/gap analysis that compares, identifies, and resolves the as-is business processes and the capability requirements and technologies;

· Analyze the out-of-the-box capability of Government Off The Shelf (GOTS) and Commercial Off The Shelf (COTS) applications, employ configuration of the software, and document the fit of requirements to the to-be operations for functional business owner use; and

· Propose to-be business processes based on COTS capabilities with configuration, as needed, but without customization to resolve the identified gaps.

Development The Contractor shall:

· Describe its software configuration and development approach, within the Software Development Plan (SDP) (CDRL TBD), aligned to Government’s standard processes as required.

· Design, deliver and maintain the LOG IT capability for continuous integration and continuous delivery (CI/CD) across the LOG IT portfolio.

· Deliver software components and interfaces using proven software development or software configuration/integration methodology; and

· Perform development activities, including but not limited to:

· Environment, database, reports, and interface development;

· COTS and GOTS software configuration, application migration, and integration;

· Components, interfaces, and data migration and exchanges to meet functional and system requirements;

· Testing of teaming partner, subcontractor, and other contractor provided products and services;

· Technology refresh and software update efforts;

· Standardization of processes and procedures by which the design is transitioned into a deliverable product or service;

· Software customization, if determined necessary by the Government; and

· Automated Test Scripts.

Technical Manuals The Contractor shall:

· Provide COTS manuals (e.g., technical manuals, user manuals, operator manuals, and maintenance manuals), supplemental data for COTS manuals, and COTS manuals that are tailored for LOG IT configurations and hardware configurations (i.e., Mobile Training Suites (MTSs)) (CDRL TBD – Software Center Operator Manual), which include the following:

· All information required for the operation and support of LOG IT systems, including the applications, network, interfaces, and training suite;

· All information required for the installation, operation, and maintenance of the hosting environment, any noteworthy warnings or cautions, and configuration details; and

· Cybersecurity portions of LOG IT systems for technical reference, including all required security precautions, handling instructions, and any unique restrictions or precautions necessary to maintain cybersecurity.

· The Contractor shall provide technical data directly associated with LOG IT that provides instructions for the installation, operation, maintenance, training, and support. The Vendor shall develop technical publications, User Logistics Support Summary (ULSS), System Administration Guide (SAG), Maintenance Index Page (MIP)/Maintenance Requirements Card (MRC), Quick Reference Guide (QRG) and Application or System User Manual (AUM/SUM) for each of the platforms LOG IT systems are installed on. Technical manual(s) will incorporate cybersecurity portions of LOG IT systems for technical reference, including required security precautions and handling instructions; and identify unique restrictions or precautions necessary to maintain product cybersecurity. (CDRL TBD)

· The Contractor shall implement an incremental development approach, using sprints to develop the Technical Publications and shall include incremental reviews. The Contractor shall conduct Validation/Verification events with Government reviewers at the agreed upon development milestones and adjudicate Government comments in accordance with TMMP (E0005-AC-HBK-010/TMMP).

Integration The Government requires the migration and integration of COTS and GOTS software components and external facing applications and capabilities to include LINC and Small Form Factor (SFF) with host facilities, platforms and networks. The application migration effort involves a series of tasks to ensure successful delivery of the specific capabilities provided by these tools.

The Contractor shall:

· Integrate software components and external interfacing applications and capabilities;

· Ensure that all internal and external integration is performed to satisfy all functional, performance, and system requirements; and

· Ensure that products are compatible and interoperable with all prior versions.

Application Migration and Integration The Contractor integration activities shall include the following:

· Identify and prioritize appropriate systems/applications to execute migration and integration tasks;

· Determine technology requirements for any systems/applications to be migrated/rationalized;

· Analyze, determine, and define interface, system/application dependencies between systems and functional areas relative to the delivery of each mission task area, and functional capabilities;

· Define, collect, and deploy test data;

· Perform data management and data migration;

· Development and implement deployment plans;

· Development and execute installation procedures;

· Perform system and database administration;

· Implement applications and systems;

· Manage and maintain databases;

· Execute test;

· Deploy/Migrate/integrate to Production and failover environments;

· Manage and maintain network connections;

· Develop interface; and

· Develop and propose an application migration and integration approach that aligns and executes to the prioritized release schedule and deliver a report with the results and recommendations (CDRL TBD – Technical Report Study/Services).

System Data Management The Contractor shall:

· Deliver and execute a Contractor’s Data Management Plan (CDMP) (CDRL TBD) that addresses the following:

· Transactional structured data, metadata, the hierarchical relationship to other data, data protection requirements, and the data life cycle which includes initial entry, validation, update, and deletion as well as the required permissions to complete those actions and the acceptable and unacceptable usage of the data;

· A strategy for data tagging and implementation of that strategy to facilitate proper protection of sensitive data

· Establish, operate, and maintain data management capabilities (processes, procedures, and tools) to create, receive, validate, maintain, catalog, store, update, back-up, restore, and retrieve data in accordance with the CDMP; and

· Establish, operate, and sustain a data environment to include:

· Maintaining existing taxonomy and metadata standards;

· Providing access and SME support to the Government for audits on the integrity of the data environment; and

· Processing requests for user access to the data environment and providing system administration and support of data management tools by assigning rights based on roles and responsibilities.

Data Migration The Contractor shall:

· Deliver and execute a Data Conversion and Migration Plan (DCMP) (CDRL TBD), addressing the following:

· Life cycle responsibilities for organizing, planning, reviewing, analyzing, and supporting data requirements;

· High-level data requirements, existing data sources available with these requirements, and identification of a strategy for populating required data in the LOG IT portfolio;

· Development and delivery of a system data architecture that addresses a data repository to serve as the source of legacy data for conversion and staging that will feed into the future efforts of data repository and data analytics development;

· Develop and deliver field level data mapping artifacts, to include translation rules and logic; and

· Conduct data migration of existing systems and applications into the LOG IT enterprise.

Data Conversion The Contractor shall:

· Develop and implement data conversion strategies that incorporate either automated or manual conversion that require data to be populated into LOG IT databases according to its data validation requirements (CDRL TBD – DCMP);

· The DCMP shall include a data-cleansing plan that specifies how the Government and the Contractor team will collaborate with data owners to resolve data quality issues prior to conversion. Data conversion covers extracting master and transactional data from existing systems, analyzing, transforming, preparing and finally loading it into the LOG IT system.

· In the development and execution of a DCMP and validate the plan using data migration solutions validating the data conversion and data load routines in a Pre-Production environment for clients to perform quality assurance of their migrated data.

· Plan and execute Pre-Production Data Conversions and quality assurance checks, Cutover Practice, and Go-Live data loads. Provide error correction activities with the deploying customer and resources in an error identification and resolution tracking tool. Provide Lessons Learned report following the completion of each Pre-Production Data Conversion, Cutover Practice, and Go-Live data load.

Market Research & Prototyping/Piloting The Government requires the market research, prototyping, and piloting of COTS and GOTS software products to assess their capabilities to satisfy LOG IT requirements.

The Contractor shall:

· Perform market research by assessing market conditions;

· Provide analysis of software for use in LOG IT;

· Develop and deliver prototypes and pilots to determine the feasibility of using a particular system, service or software product as a solution to a functional or system requirement (CDRL TBD – Computer Software (CS) Product End Items);

· Perform an analysis of the requirements, establish a prototype capability, evaluate the prototype’s performance at satisfying the requirements, and produce a report with the results and recommendations (CDRL TBD – Technical Report Study/Services); and

· Generate user access and evaluation of the capability.

Capability Solution Delivery The Contractor shall deliver the capability solution, inclusive of applicable software and hardware, to meet task order requirements. (CDRL TBD – Computer Software Product End Items). This includes, but not limited to, he following tasks:

· Producing new software code;

· Configuring and Modifying existing software;

· Providing Hardware solution;

· Reusing or migrating existing software;

· Configuring and implementing COTS software;

· Integrating software and hardware components;

· Establishing databases;

· Developing a deployment cutover plan and schedule for each installation, to cover, data conversion and technical validation, backward compatibility, financial validation, inventory / material validation, legacy ramp-down, go-live, and legacy period end close;

· Supporting working group sessions with user community activities regarding functionality and deployment activities, responding to questions regarding the transition for a range of arenas;

· Conducting demonstrations of functionality to provide user community activities deployment teams with an in-depth understanding of business processes;

· Providing resources with solution knowledge for Deployment On-Site Support, for a duration until the end of the installation;

· Reviewing and comment on user community activity integration, transition plan and timelines;

· Supporting deployment sites to plan, schedule, and execute implementation tasks;

· Providing functional expertise to meetings, demos, and working groups;

· Identifying, compiling, and formatting enterprise and site-specific information for configuration activities;

· Providing a site test plan for each of the deployment sites describing the installation activities including testing and acceptance criteria;

· Providing the site test plan within 60 days of the first site installation with the Government providing concurrence 30 days after submittal. The installation effort includes:

· Site data load;

· Data Load validation;

· User provisioning; and

· Running smoke test in the PaaS.

· Providing User and Sys Admin familiarization training utilizing SUM, QRGs, SAGs System Administration Guide (SAG), Maintenance Index Page (MIP)/Maintenance Requirements Card (MRC), Quick Reference Guide (QRG) and Application or System User Manual (AUM/SUM) to the Navy Installation team responsible for over the shoulder support and Service Desk team., prior to Limited Deployment (LD) no later than (NLT) 60 days prior to first installation for each platform type;

· Conducting Security Technical Implementation Guide (STIG) testing and provide test results to the Government; and

· Providing post-production on-site support (OSS) to end-users.

[LOT 2] Operations Support Planning and Sustainment The Contractor shall:

· Establish an Integrated Logistics Support (ILS) program as specified by DoDI 5000.02, Operation of the Defense Acquisition System; DoDI 5000.75, Business Systems Requirements and Acquisition; and SECNAVINST 5000.2G, DON Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System, to ensure that supportability design criteria and characteristics are considered and incorporated into the system as described in the System Requirements Specification (SRS) (Attachment TBD);

· Establish and update a detailed ILS project schedule as part of the IMS (CDRL TBD – IPMR). ILS status updates shall be included in the Monthly Contract Status Report (CDRL TBD) to the COR. The Contractor’s ILS activities shall further develop and deliver the ILS related products and data detailed in the sections below; and

· Ensure the ILS efforts and products address site specific or unique requirements or constraints at each site (i.e., union and U.S. Forces Japan), to produce required training, organizational change management, and implementation materials for various audiences.

Supportability Plan The Contractor shall develop, deliver, and maintain a Product Support Business Case Analysis (CDRL TBD), Product Support Strategy (CDRL TBD), and document findings in the Capability Support Plan (CSP) (CDRL TBD), in accordance with the Government CSP format, and address the product support elements tailored for LOG IT.

Manpower, and Personnel and Training Support The Contractor shall provide Manpower, Personnel, and Training (MPT) support to the Government. This support entails the full life cycle of the program from the Front End Analysis (FEA) to developing the Navy Training System Plan (NTSP), producing training products required for initial and follow-on training / formal schoolhouse curriculum.

Ready Relevant Learning The Contractor shall assist in the alignment of LOG IT training efforts to the Ready Relevant Learning (RRL) process in accordance with RRL Process Manual - SAILOR 2025 (S2025) RRL.

Deliverables include:

a) RRL Documents (CDRL TBD)

· Rating Domain Analysis (RDA)

· Media and Fidelity Analysis (MFA)

· Training Effectiveness Evaluation Plan (TEEP)

· Total Lifecycle Cost Estimate (TLCE)

· Program Objective Memorandum (POM) Issue Paper.

· Training Installation and Transfer Agreement (TITA) Instructional Systems Design The Contractor shall provide curriculum development services to meet training requirements for LOG IT programs. ISDs shall adhere to Naval Education and Training Plan, Analysis, Design, Develop, Implement, and Evaluate + Maintenance (PADDIE+M) model for curriculum development. Deliverables include:

a) Training Data Products (CDRL TBD)

· Training Project Plans (TPP)

· Job Duty Task Analysis (JDTA)

· Instructional Performance Requirements Document (IPRD)

· Storyboards

b) Training Course Control Document (TCCD) with Annexes (CDRL TBD)

a. Course Training Task List (CTTL)

b. Learning Objectives (LOs)

c. Curriculum Outline of Instruction (COI)

d. Course Master Schedule (CMS)

e. Testing Plan

c) Instructional Media Design Package (IMDP) (CDRL TBD). NAVEDTA 136 lists minimum requirements for the IMDP. In addition, the IMDP shall include how the contractor will address the requirement for training to be compatible with mobile devices. Government approval is required of the IMDP to authorize curriculum development.

d) Interactive courseware (ICW) developed shall be Sharable Content Object Reference Model (SCORM) compliant. Adhere to Government requirements for Learning Management System (LMS) content hosting, tracking training metrics such as course registrations, course completions, assessments, and feedback. Provide all media source files to the Government when requested and prior to contract end (CDRL TBD: Instructional Media Package)

e) Testing and Evaluation. The contractor shall update, revise, and develop test questions, test banks, progress checks and test administrator guides (Test Package, CDRL TBD).

f) Finished Courseware. The contractor shall provide two copies of all deliverables in Section 2.1.2.2.1 Instructional System Design (ISD) on disc or other approved transfer media deemed by the Government Navy Training System Plans and Training Transfer Agreements The Contractor shall develop and maintain the Navy Training Systems Plans (NTSP) and Training Transfer Agreements (TTA) (CDRL TBD: NTSP), in accordance with OPNAVINST 1500.76 series, Naval Training Systems Requirements, Acquisition, and Management. The NTSP is required to be loaded in the NAVWAR Human Analysis & Requirements Planning System (HARPS) workflow for approval if the MPT analysis determines existing formal Navy schoolhouse courses or learning objectives will be impacted by the implementation of a LOG IT system.

Manpower, Personnel, and Training Advisory Board The Contractor shall:

· Organize and conduct MPT Advisory Boards in accordance with current version of OPNAVINST 1500.76;

· Develop the necessary materials to facilitate meetings in order to demonstrate progress in completing the MPT analysis and NTSP;

· Provide meeting minutes;

· Conduct a manpower and personnel analysis using a Front-End Analysis (FEA) in accordance with Chief of Naval Operations Instruction (OPNAVINST) 1500.76D, Naval Training Systems Requirements, Acquisition, and Management. The manpower and personnel analysis shall include assessment of the existing workforce at each maintenance activity including military, civilian, and contractor personnel operating, maintaining, and supporting the existing system(s) to establish the “As Is” user population and baseline the “To Be” target audience requirements. By population type, list the quality (skills and experience level) and quantity of manpower required;

· Document and deliver the results of the manpower and analysis in the Training Requirements Analysis Report (TRAR) (CDRL TBD), which addresses:

· As required by the Government, and deliver Navy Training Systems (NTSP) (CDRL TBD), which identifies training requirements by billet(s), in accordance with OPNAVINST 1500.76D, Naval Training Systems Requirements, Acquisition, and Management. The NTSP is required to be loaded in the NAVWAR Human Analysis & Requirements Planning System (HARPS) workflow for approval if the MPT analysis determines existing formal Navy schoolhouse courses or learning objectives will be impacted by the implementation of a LOG IT system.

Training Support Services The Contractor shall:

· Provide training products, performance support products, and training event support to include instruction/facilitation. Conduct classroom and virtual training sessions. Training products shall be compatible with mobile devices;

· Provide training beyond generic COTS product capabilities, to include system interface familiarity, system configuration options, workflows, user roles, and navigational properties all within the context of the associated business processes;

· Coordinate with the Government to customize training, implement iterative design, Subject Matter Expert (SME) review, training package approval, course pilot and test, and demonstration of instructor and trainee readiness;

· Training support package materials may consist of (at a minimum) Lesson Plans, Instructor Guides, Trainee Guides, Visual Media (such as MS Power Point, video) (CDRL TBD: Training Conduct Support Package);

· Adhere to Government requirements for Learning Management System (LMS) content hosting, tracking training metrics such as course registrations, course completions, assessments, and feedback;

· Provide management oversight on the development of system training developed by other vendors for LOG IT programs. This oversight includes monitoring training development is within program cost, schedule, and performance;

· Evaluate and validate training materials and training instruction/facilitation services;

· Manage the Technical Training Equipment (TTE) and Training Devices by analyzing, validating, cost estimating, and updating TTE and Training Devices, TTE/TD classroom work scope, TTE/TD work package, and TTE/TD installation schedule, including modification or rehabilitation of existing facilities used to accomplish training objectives;

· Provide shipboard training support as it relates to LOG IT programs and systems. The training can be Instructor Led Training (ILT), train-the-trainer (TTT), or on-the-job training (OJT). The training can be in person or virtual (e.g. Microsoft Teams, NetMeeting, or similar);

· Coordinate with the LOG IT USMC liaison SMEs, develop draft source documentation relative to United States Marine Corps (USMC) ALTIS Administration training and provide System Training for USMC ALTIS SMEs in support of their build of sustainment training curriculum. Material and training to include the management, administration, and maintenance of LOG IT systems and services and shall at a minimum support the installation, maintenance, and documentation of the application software, and operating systems. Additionally, the material will support the maintenance and troubleshooting of complex application and server issues; and

· Develop Curriculum for AZ Course (Intermediate & Organizational Levels). Course material shall include application data base oversight and supervise maintenance administration functions to include; maintenance of database integrity on assigned database management servers, collect and organize data, monitor and ensure accuracy of maintenance data, and support network systems administration functions for detachments and up line reporting. The Course material will include performance standards, integrity, troubleshooting, and security of a database.

Training Implementation Planning

The Contractor shall develop and deliver a Training Implementation Plan (CDRL TBD), that provides training planning data and training course control data. It is the long-range training program resource requirements for personnel and equipment, and their implementation. It must address manpower requirements and the constraints of the maintenance activity installation sites for concurrent training classes.

Training Program Management The contractor shall provide training program management to ensure all tasks are performed efficiently, accurately, on time, and in compliance with all requirements and maintain the training inputs to the ILS project schedule as part of the IMS. A Training Management Plan shall be developed and maintained that details the roles and responsibilities, and methods the contractor plans to utilize to address all training requirements for each LOG IT program.

Organizational Change Management The Contractor shall:

· Plan and coordinate all aspects of communication activities;

· Train and educate on Organizational Change Management (OCM) in the areas of implementation, trends, techniques, and case studies; and

· Engage in a proactive communication plan to establish and enhance the customer experience, using principles and techniques of change communications as directed by the Government.

· The Contractor shall develop, deliver, and maintain an OCM Plan (CDRL TBD), in accordance with the Government’s OCM Plan.

Human Systems Integration / Customer Experience Support The contractor shall:

· Organize and maintain the Human System Integration (his) plan (CDRL TBD), ensuring technical accuracy;

· Organize and maintain the HSI plan in compliance with DoD, DON, and SPAWAR HSI standards;

· Perform Heuristic Assessments, User Assessments, and Design Thinking Focus Groups with programs and user communities;

· Document findings and monitor findings and track their resolution;

· Document the results (CDRL TBD: Technical Report – Study/Services).

· Align to PEO MLB’s Customer Experience Support guidance and best practices

Facility Assessments

The Contractor shall conduct facility site assessments and deliver Facility Assessment Reports (CDRL TBD) that include:

· Requirements for establishing on-premises facilities required for the delivery of LOG IT capabilities and services; and

· Requirements for establishing local deployment business offices to accommodate the Contractor’s deployment On-Site Support (OSS).

Information Technology Service Management (ITSM) Processes The Contractor shall:

· Ensure Artificial Intelligence Operations (AIOps) and Machine Learning (ML) methods are analyzed and incorporated into operations to the maximum extent possible;

· Automate processes to the maximum extent possible; and

· Develop and execute plans for ITSM processes such as: Availability Management, Capacity and Demand Management, Access Management and Asset Management.

Service Level Management The Contractor shall:

· Document service levels in formal Service Level Agreements (SLAs) (CDRL TBD);

· Perform end-to-end Service Level Management for LOG IT systems, including all CIs, such as hosting environments, cloud environments procured by the Contractor or provided to the Contractor by the Government, software applications, and hardware.;

· Maintain SLAs and monitor and report on compliance in the SLA Compliance Report (CDRL TBD); and

· Provide a balanced set of Key Performance Indicators (KPIs) (e.g., availability, speed of service execution, accuracy of execution, legal/regulatory compliance, financials/costs, user satisfaction) for a program dashboard and quad charts.

Release and Deployment Management The Contractor shall:

· Plan for patches and cybersecurity management releases;

· Document software/system releases resulting from sustainment activities in release notes and in appropriate system documentation;

· Develop and submit for Government approval change communications, including expected service impacts, for all scheduled maintenance or change events, no later than 10 business days in advance of the event;

· Develop and execute a Release and Deployment Management Process Guide (CDRL TBD); and

· Deliver and install new software versions, provide a Software Version Document (SVD) (CDRL TBD) with each release, and update all technical baseline documents.

Service Desk Request Fulfillment Service Desk request fulfillment is the responsibility for managing the life cycle of all Service Requests (SRs) from the users. The Contractor shall maintain production operations staff to perform event, incident and problem/issue management for all environments and products. The help desk will support incident and problem management for the entire system, which includes all software applications and the hosting environment. The help desk will be available 24 hours a day, 7 days a week, and 365 days a year to support all related LINC, SFF, N-MRO, N-SCM, N-PLM and CBM+ capabilities. Additionally, the help desk will be accessible via telephone, e-mail, and chat. LOG IT will execute request fulfillment in collaboration with the Navy Enterprise Service Desk (NESD) Program.

The Contractor shall:

· Work with NESD on Tier 1 help desk support and ensure seamless integration with Tier 2 and 3 help desk support services;

· Provide Tier 2 and Tier 3 Help Desk Support;

· Conduct an analysis to determine the most efficient help desk model;

· Develop and execute a Request Fulfillment Plan (CDRL TBD);

· Include autonomous processes to improve the customer experience (e.g., request submittal and ticket routing);

· Provide embedded context-sensitive online help capability;

· Establish embedded Service Request Management (SRM)/Customer Relationship Management (CRM) tool integrated with the NESD ticketing system as part of the KB (CDRL TBD)

· Escalate Service Requests (SRs) as required to software vendors, CSP(s), or both; and

· Provide monthly Help Desk Metrics Report (CDRL TBD).

Implementation Implementation for LOG IT services will align and prepare both users and data in the system for adoption with limited business impact, while effectively enabling the solution.

Role Assessment The Contractor shall:

· Assess the functions performed with the current processes and align to roles in new LOG IT systems and services;

· Develop an Identity and Access Management (IDAM) Process (CDRL TBD) aligned to Government policies and processes, to include personnel data collection, account creation and maintenance, access levels, role conflicts, and role mapping efforts;

· Create and maintain a record of base system roles aligned to job functions, and of derived roles, including a matrix that cross references independent job function and access authorization levels; and

· Develop tailored briefing materials related to UM that provide communications to the end users and the deployment sites.

Role Mapping The Contractor shall:

· Recommend access/role assignments based on regulatory requirements, information sensitivity, confidentiality, and other technical factors;

· Provide an analysis of the role mapping to ensure there is adequate coverage for all functionality and that any conflicts of interest in role mapping are addressed;

· Conduct role mapping workshops with end user community representatives and additional personnel at the maintenance activities (deployment sites), as agreed to by the Government, in order to establish end user mapping and role assignment based on the role mapping strategy;

· Provide reports summarizing the status and counts of role mapping efforts in accordance with the Access Management Report (CDRL TBD);

· Collect and maintain records for conflicts of interest within roles and role mapping efforts and provide recommended courses of action to mitigate the conflicts; and

· Provide automated account requests and role responsibility assignment capabilities.

Training Implementation The Contractor shall:

· Design, develop, and deliver training and performance support products in accordance with training analysis (CDRL TBD - Instructional Performance Requirements Document), IMS (CDRL TBD), and Training Implementation Plan (CDRL TBD);

· Implement training at user locations;

· Ensure training and performance support products achieve the learning outcomes identified in the training analysis;

· Develop, deliver and maintain Online Embedded Training, Instructor Led Training and Formal Schoolhouse Training

· Deliver instructional media source files and render final training and performance support products to the Government prior to release (CDRL TBD – Instructional Media Package; Training Conduct Support Document – Pre-Deployment/Sustainment Training Support Package).

Training and performance support products in support of system implementation and sustainment shall consist of a blended solution to include but not be limited to the modalities listed in this PWS.

Training Equipment The Contractor shall provide the training equipment required to support training delivery in accordance with the Training Implementation Plan (CDRL TBD). Training equipment should complement the blended training solution.

Deployment The Contractor shall develop and implement a Deployment Cutover Plan and Schedule (CDRL TBD).

Deployment Support The Contractor shall:

· Conduct working group sessions with end users regarding LOG IT services and deployment activities and respond to questions regarding the transition for a range of arenas (i.e., business processes, mock data loads, and cutover activities);

· Conduct demonstrations of functionality to provide deployment teams with an in-depth understanding of the business processes;

· Provide resources with solution knowledge for deployment on-site support (OSS), with OSS personnel both traveling and hired locally based on cost and duration of cutover;

· Conduct communications necessary to work collaboratively with LOG IT deployment teams and deployment sites to plan, schedule, and execute implementation tasks;

· Provide functional expertise during meetings, demonstrations, and working groups related to implementation; and

· Provide functional expertise input to external audits and compliance assessments (such as Government Accountability Office (GAO) and DON).

Cutover The Contractor shall:

· Develop a Deployment Cutover Plan and Schedule (CDRL TBD), taking into account the master schedule for each release; and

· Plan and execute cutover activities, ensuring a successful transition from legacy systems to LOG IT systems and services while minimizing impacts to business operations.

Sustainment The Contractor shall maintain and sustain to include the following activities:

· Maintenance of software and licenses;

· Security and IA activities;

· CM activities including updates to training and technical manuals;

· System and database administration functions;

· System enhancements and upgrades;

· Software changes and maintenance; and

· Resolution of defects.

Application/ Software Maintenance The Contractor shall perform application sustainment, which includes processes, procedures, material, and information required to support, maintain, and operate the LOG IT software applications. The Contractor shall modify LOG IT systems and services application software to correct faults, enhance or change existing functionality, improve performance or other attributes, or adapt to changing hardware environments and security requirements.

Hardware Maintenance

The Contractor shall perform hardware sustainment, which includes processes, procedures, material, and information required to support, maintain, and operate the LOG IT hardware systems. The Contractor shall modify LOG IT systems to correct faults, enhance or change existing functionality, improve performance or other attributes, or adapt to changing physical and security requirements.

Software Changes The Contractor shall:

· Perform the integration and testing of new software functionality (including additional modules of existing COTS software); and

· Submit recommended software and cloud infrastructure changes that enhance or change business processes to the Government.

System Enhancements The Contractor shall perform software systems engineering that is a change to the system, when approved by the Government through the Government configuration management process. These changes are considered beyond the maintenance break/fix changes associated with regular sustainment and maintenance activities. These types of software systems engineering activities are changes in response to Engineering Change Proposals (ECPs).

Sustainment Software Changes The Contractor shall perform sustainment software changes as part of sustainment and maintenance. These services include software modifications other than break/fix updates that are related to business process and policy changes as well as modularity and open systems architecture improvements.

System Monitoring The Contractor shall:

· Perform daily, weekly, and monthly monitoring of the program production schedules, interfaces, outputs, and operations. This may include correcting customer data input errors, transferring data, updating reports and distribution requirements, re-running lost reports, and providing authorized system access;

· Coordinate with CSP(s) to access and use monitoring tools; and

· Deliver a Daily Operations Status Report.

Functionality Support The Contractor shall maintain transactional functionality and the reporting capabilities of all functionality within designated system boundary. This includes reports from LOG IT transactional and analytics environments.

Database Maintenance The Contractor shall:

· Perform database administration, which includes maintaining the logical and physical data models for databases, implementing physical databases, maintaining reference tables and metadata, and providing support to all environments;

· Perform database backups to include restoration; and

· Perform, at a minimum, quarterly validation of these capabilities in a Database Back-Up Report (CDRL TBD).

System Administration Support The Contractor shall provide systems administration support for all environments, to include:

· Maintenance of server operating systems;

· Maintenance of web server active directory and Public Key Infrastructure (PKI) certificates for encrypted Security Socket Layer (SSL) communications;

· Coordination with appropriate external services/programs (e.g. CANES, NMCI, NIS/ICAM);

· Integration of software patching;

· Interpretation of server operational characteristics, identification of problems, identification of possible solutions, and implementation of a solution in a timely manner in accordance with the ECP;

· Restoration of older versions of operating systems if technical issues arise that prevent the use of software upgrades;

· Analysis of the interdependencies of multiple software products, and administration of solutions for their implementation; and

· Installation of current and future releases of the operating system and associated products.

[LOT 3] Afloat Installation Design, Integration, Configuration or Installation of Hardware and Software The Contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The Contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/DON/Navy cyber directives and does not violate the terms and conditions of the accreditation/authorization issued by the appropriate Accreditation/Authorization official. Contractors that access Navy IT are also required to follow the provisions contained in DON CIO Memorandum: Acceptable Use of Department of the Navy Information Technology (IT) dtd 12 Feb 16. Use of blacklisted software is specifically prohibited and only software that is registered in DON Application and Database Management System (DADMS) and is Functional Area Manager (FAM) approved can be used as documented in Section 3.12.2.1. Procurement and installation of software governed by DON Enterprise License Agreements (ELAs) – Microsoft, Oracle, Cisco, Axway, Symantec, ActivIdentity, VMware, Red Hat, NetApp, and EMC shall be in accordance with DON CIO Policy and DON ELAs awarded.

Applicable Documents for Afloat Installation Services The Contractor shall perform all afloat platform installation services in accordance with the requirements contained in the current version of the NAVSEA Navy Modernization Process Management and Operations Manual (NMP-MOM) (also known as the “One Book”), NAVSEA 9090-310 (Series), Afloat Installation Process Handbook (AIPH). All installation documentation, including Memorandums of Agreement, Ship Installation Documents (SIDs), and System Operational Verification Test (SOVT) documents, delivered under this contract shall meet the technical and formatting requirements for these documents contained in the NMP-MOM and in this document.

Platform Preparation Requirements The Contractor shall provide installation specifications that describe in detail the work that must be performed in order to conduct an installation. These specifications shall include the standards, test plan, and inspection requirements by licensed professional engineers operating in their field of expertise. (CDRL TBD)

Afloat Design Documentation The Contractor shall provide afloat installation design documentation that meets the applicable requirements of the IRD Standard and the afloat standards listed in Table 1 as required by Task Order. This Installation Design Documentation includes, but is not limited to:

a. Draft Memorandums of Agreement (MOAs) (CDRL TBD)

b. Installation Requirements Drawings (IRDs) (CDRL TBD)

c. Ship Change Documents (SCDs) (CDRL TBD)

d. Ship Installation Drawings (SIDs) (CDRL TBD)

e. Alteration Completion Reports (CDRL TBD)

f. Liaison Action Records (LARs) (CDRL TBD)

g. On-the-Job Training (OJT) Materials (CDRL TBD)

System Operational Verification Test (SOVT) Development The Contractor shall develop and provide afloat platform specific SOVT Plans. (CDRL TBD)

Electromagnetic Environmental Effects The Contractor shall conduct and provide Electromagnetic Environmental Effects (E3) surveys utilizing Technical Reports (CDRL TBD) as required by Task Order. When preparing planning documentation for the installation of radio frequency transmitters under this contract, the contractors shall include any requirement for an E3 study or related documentation in accordance with OPNAVINST 2400.20F, and as specified in individual Task Orders.

Contractor Furnished Material The Contractor shall furnish all installation material identified as contractor furnished material and provide an Installation Bill of Materials (IBOM) (CDRL TBD) to include any long lead material and estimated delivery dates where required by the Task Order.

Installation material (not to include incidental material; e.g.