2. NOBLE Solution Approach and Requirements: This section outlines the Government s requirements for a NOBLE solution approach.

Transcription

1 Attachment 1 DRAFT Technical Supplement For Naval Operational Business Logistics Enterprise (NOBLE) Prototype(s) - Integrated Data Environment (IDE), Naval Operational Supply System (NOSS), Naval Aviation Maintenance System (NAMS), Naval Operational Maintenance Environment (NOME) 9 July Scope This Technical Supplement describes the Navy s high level requirements for the NOBLE Family of Systems consisting of NOSS, NAMS, and NOME as well as the IDE. 2. NOBLE Solution Approach and Requirements: This section outlines the Government s requirements for a NOBLE solution approach. 2.1 NOBLE Solution: The solution shall utilize the Navy s Agile Core Services (ACS) to the maximum extent possible (ACS Developers Guide attached) Solution(s) are desired to consist of COTS products to the maximum extent possible. Solution(s) should be capable of scaling to support over 1,000 ashore and afloat installations worldwide and over 150,000 users. The solution(s) may adhere to Human Systems Integration (HSI) guidelines provided as part of the Government s HSI guidance document. (SPAWAR HSI Guide attached) Solution(s) shall demonstrate the ability to be DoD cyber authorized (Authority to Operate) (ATO). Solution(s) shall be capable of providing single user sign-on entry utilizing Common Access Card (CAC) / Public Key Infrastructure (PKI). Solution(s) should provide the ability for Personal Identity Verification (PIV) credentials with role based applications embedded. Solution(s) should demonstrate ability to meet Payment Card Industry (PCI) compliance controls. The solution(s) shall demonstrate ability to integrate multiple platforms into a holistic environment, accessible via industry standard Application Program Interfaces (API). The solution(s) shall demonstrate Disconnected, Disrupted, Intermittent, and Limited (D-DIL) operations. 1

2 The solution(s) shall demonstrate distance support by providing application functionality via an Enterprise system to remotely provide reactive, proactive, and predictive logistics support to Naval Operational Forces, including performing local functions remotely via appropriate roles. The solution(s) shall demonstrate application functionality via an Enterprise system to remotely provide reactive, proactive, and predictive logistics support to Naval Operational Forces, including performing local functions remotely via appropriate roles. The solution(s) shall demonstrate the ability to use mobile computing devices (e.g. Smart Phone, tablets, mobile printers etc.) (interdependencies between NOSS, NAMS, NOME, and NOBLE at large). The solution(s) shall demonstrate a common look and feel to the system thus reducing the number of entry points to appropriately consolidated applications based on application operating environment requirements (ashore, afloat, expeditionary). The solution(s) should be able to connect to Navy classified and unclassified networks as well as receive and transmit classified/unclassified information. The solution(s) shall provide connected and disconnected training solutions providing the knowledge and skills for all Users and System Administrators to operate and maintain the system. The training solution(s) shall provide interactive Computer Based Training to support "Role Based" training (defined as the Role (clerk, supervisor, etc.) to the appropriate Community (i.e. Stores Clerk for Logistics Specialist (LS) rating). The Role Based training products shall provide at least 80% of the required training for the specific role, be integrated to allow for usage from any current Navy and USMC workstation, and will allow permission to the appropriate NOBLE system upon completion. The training completion process is expected to be provided by an 'Access Control' function. The connected training solution(s) shall include a training environment, with redundancy, that allows Internet access 24/7 and will also report to the NOBLE Access Control application the course completion metric for granting of Role Based permissions to the NOBLE system. Applicable role based training and access control in a disconnected environment shall be provided. A synchronizing/replication mechanism for access shall be enabled when reconnected to update an authoritative User database at the connected web based system. The solution(s) should have User and System Administrator guides deployed with disconnected users. 2

3 2.2 IDE Solution Approach and Requirements: The solution shall be able to support the data integration of multiple legacy platforms into a holistic data environment, accessible via API and can be hosted in a Government Certified Cloud. The solution shall provide a highly available and reliable commercial cloud Information Technology (IT) IDE. It will be capable of hosting and integrating applications, systems, and services planned to be transitioned into COTS technologies, and the migration of GOTS applications with no degradation of services. The solution shall demonstrate API usage for at least the following: Web services (i.e. Representational state transfer (REST)), Open Database Connectivity (ODBC), Java Database Connectivity (JDBC), Object Relational Mapping (i.e. HIBERNATE, Java Persistence Architecture (JPA)), and method calls. The solution shall be able to support a Government provided SecDevOps environment. The solution should be cloud, database, and data lake-agnostic. The solution shall support Online Transaction Processing (OLTP) operations with the business applications. The solution shall support information assurance requirements for Data at Rest (DAR), Data in Transit (DIT), and Data in Use (DIU). The solution should include business intelligence and analysis. The solution should adhere to best commercial practices for commercial cloud IT service development/deployment. The solution should provide a common, language-agnostic way of interacting with an application. The solution shall monitor performance and throughput of the data transactions and operations. 2.3 NOSS Solution Approach and Requirements: The solution shall be scalable to support over 150,000 users at 700 surface, submarine, expeditionary, aviation and shore support activities. The solution shall demonstrate supply chain planning using available resources, budget, historical data and analytics from enterprise to platform level. The solution shall demonstrate organizational hierarchy. The solution shall demonstrate the ability to manage multiple types of material by commodity type, user groups, allowance/load lists and financial ownership while applying different business rules. The solution shall demonstrate the ability to compute Moving Average Cost accounting and valuation on the basis of receipt by each asset and across all property types in compliance with DoN policy. The solution shall demonstrate the capability to manage useful life of an asset and account for and report depreciation in compliance with DoN policy. The solution shall demonstrate the capability to capture and maintain Unique Item Identifier (UII) or Item Unique Identifier (IUID) in compliance with DoD mandates. 3

4 The solution shall demonstrate material requests management to include sourcing, tracking, receipt, and transfers. The solution shall demonstrate warehouse management activities such as: configuration of storage; management of inventories that include hazardous material, ordnance, and subsistence; issues; and physical tracking of assets. The solution shall demonstrate the ability to interface with a disparate set of external systems for authoritative data, services, and reporting functions. The solution should demonstrate food service management consisting of subsistence inventory, financial management and menu preparations to include menus that go across international datelines. The solution should demonstrate Point of Sale (POS). The solution shall demonstrate ability to properly manage concentrations and location proximity of highly regulated materials (e.g. HAZMAT). The solution shall enable management of financial transactions in compliance with Financial Improvement and Audit Readiness (FIAR) requirements. 2.4 NAMS Solution Approach and Requirements: The solution shall be scalable to support over 2700 aircraft spread out over 338 ashore and afloat sites with 94,000 users. The solution shall demonstrate enterprise capability by maximizing automated machine to machine interfaces in a modular layer. The solution shall demonstrate the ability to consume parsed data from aircraft data downloads, then prefill a maintenance work order with any Built-in-Test (BIT)/discrepancy data. The solution shall demonstrate the ability to enable authorized maintenance personnel to document levels I/II/III (Organizational, Intermediate, Depot) scheduled and unscheduled maintenance against aircraft, engines and aviation related equipment assigned to the organization. The solution shall demonstrate the capability to redistribute existing aircraft to where they are needed, for example, transferring aircraft between squadrons. The solution shall demonstrate the ability to view, update or delete aircraft, engine, propulsion system, module and related component inventory from the authoritative source. The solution shall demonstrate the ability to electronically release aircraft safe for flight information, which requires the following: o Aircraft Weight & Balance (W&B) forms have been updated and verified o Valid daily/turnaround inspections are completed o Fuel samples have been taken and inspected o All downing discrepancies and flight safety Quality Assurance (QA) are signed off o Validate that engine/gearbox oil consumption is within limits of specified type-model-series. The solution shall provide the capability to dynamically schedule maintenance tasks using Conditioned Based Maintenance (CBM) and Reliability Centered 4

5 Maintenance (RCM) optimized periodicities for each task and offering the ability to group tasks into an event and schedule events for execution. 2.5 NOME Solution Approach and Requirements: The solution shall be scalable to support over 400 ashore and afloat sites. The solution shall provide a single, coherent, integrated means of supporting a common business process for preventive, corrective maintenance, and alteration management at the maintenance unit level aligned to OPNAVINST The solution shall demonstrate maintenance, repair, and overhaul, which consists of all actions, which have the objective of retaining or restoring an item in or to a state in which it can perform its required function or mission. The solution shall consolidate and display maintenance requirements (discovery)and provide visibility and management of maintenance requirements to allow safe and reliable operations during the service life of the equipment. The solution shall demonstrate consolidated work requirements, which include reviewing, documenting, updating and consolidating all work notifications. The solution shall facilitate scheduling maintenance based on calendar based (periodic) or event (situational) driven requirements. The solution shall provide for establishing maintenance periods. The solution shall demonstrate the ability to assign/un-assign work notifications to a work center. The solution shall demonstrate the ability to prepare work orders for maintenance, repair and overhaul, and include identifying materials needed, common and special tools, and personnel with a defined skill set. The solution shall demonstrate the ability to plan procedures for work, which includes determining methods for all planned maintenance, planned modifications, and unplanned maintenance and repairs. The solution shall demonstrate the ability to plan resources for work by identifying and requesting procurement of materials, components, parts, tools, equipment, labor skills and facilities necessary to perform maintenance. The solution shall manage maintenance execution and maintenance control by controlling which work orders are assigned resources and monitor execution of work orders. The solution shall support the execution and certification of work by allowing approval/verification of maintenance tasks and certifying the work was performed correctly, and is ready for return to service. The solution shall provide quality management by systematically implementing effective Quality Assurance processes per the Navy s Joint Fleet Maintenance Manual (JFMM) Volume 5. The solution shall provide the means of managing hazardous energy in compliance with 29 CFR Parts 1910 and 1915 as modified by S0400-AD-URM- 010/TUM (TAG-OUT USERS MANUAL). The solution shall provide off-hull reporting via the appropriate domain (unclassified and classified). 5

6 2.6 Intellectual Property Rights and Rights in Technical Data and Computer Software: The Government s technical data rights strategy has the goal to ensure qualified and sustainable NOBLE processes and protocol for meeting technical Data, processes, and procedures and product life-cycle data rights requirements. It is the Government s desire to receive unlimited rights in non-commercial technical data and computer software that is funded exclusively at Government expense and at least government purpose rights in all non-commercial technical data and computer software that is developed at least partially at private expense. Government purpose rights would be for all development and deliverables of technical data and computer software funded under the transaction agreement, for at least a fiveyear period. The five-year period, or such other period as may be negotiated, would commence upon execution of the Other Transaction Agreement that required development of the items, components, or processes or creation of the data. Upon expiration of the five-year or other negotiated period, the Government would receive unlimited rights in the technical data and computer software. Government purpose rights means the right to use, modify, reproduce, release, perform, display, or disclose technical data and computer software within the Government without restriction; and release or disclose technical data and computer software outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose technical data and computer software for United States government purposes. The Government s strategy for acquiring rights in intellectual property and technical data varies depending on whether technical data, computer software, or computer software documentation used, generated, or developed for NOBLE is commercial or noncommercial in nature. The solutions proposed for NOBLE are expected to be primarily commercial in nature. NOBLE technical data will be developed by the vendor and delivered during the development of the program. Fleet documents, (SAG, SUM) will also be delivered and a Technical Manual Identification Numbering System (TMINS) number from the Naval Sea Data Support Activity (NSDSA) will be assigned. Users will have the ability to download approved technical documentation in digital format from the Technical Data Management Information System (TDMIS) site or the SPAWAR Acquisition Integrated Logistics Online Repository (SAILOR) website. Technical documentation is changed or updated based on input from users, approved ECRs/ECPs, planned product improvement, and updates to software. A Technical Manual Deficiency Evaluation Report (TMDER) submitted via the TDMIS is the users method to recommend changes or revisions. 6

7 3. Program Management, Schedule and Sprints 3.1 Program Management The Vendor should accomplish all planning and execution of program management activities to ensure that the technical and programmatic requirements of this Agreement are accomplished in accordance with best commercial practices. A monthly technical report of accomplishments will be required to be submitted to the Government, with contents to be determined by the integrated product team. The Vendor should identify and document the prototype system in detail to support design evaluation and system lifecycle support in a configuration controlled baseline. At decision reviews, the baseline is considered to be locked, and after this point concurrence of the Government is required to make changes to the baseline. 3.2 Management Reviews Start of Work Meeting. The Vendor should host an initial meeting within 30 calendar days after award, in order to agree on key metrics and processes to be used during the project Integrated Product Team Meetings. The Vendor should establish and maintain regular communication with the Government team (both formal and informal) so that plan deviations are known, assessed, and resolved in a timely manner. 3.3 Projects Tasks and Milestones Table 1 lists the milestone tasks and notional schedule for completing each milestone for the NOBLE IDE. Table 1: IDE Milestones Milestones Duration Tasks I 30 days Host IDE in commercial cloud. II 30 days Host IDE in Digital Twin of ACS in cloud, Impact Level 4, Ingest Data Sets III 30 days Host IDE in Digital Twin of ACS in cloud, Impact Level 4, connect IDE to simulated external interfaces (not live) IV 30 days Configure IDE to meet Navy certification requirements V 60 days Interim Authority to Test (IATT) Table 2 lists the milestonce tasks and desired duration for completing each milestone for the NOSS application. Table 2: NOSS Milestones 7

8 Milestones Duration Tasks I 30 days Host solutions in commercial cloud and configure functional requirements. II 30 days Host NOSS in Digital Twin of ACS in cloud, Impact Level 4, Ingest Data Sets, Configure Navy Functional Requirements III 30 days Host NOSS in Digital Twin of ACS in cloud, Impact Level 4, connect NOSS to simulated external interfaces (not live) IV 30 days Configure NOSS to meet Navy certification requirements (Financial Improvement & Audit Readiness, Navy compliance) V 60 days Interim Authority to Test (IATT) Table 3 lists the milestone tasks and desired duration for completing each milestone for the NAMS application Table 3: NAMS Milestones Milestones Duration Tasks I 30 days Host solutions in commercial cloud and configure functional requirements. II 30 days Host NAMS in Digital Twin of ACS in cloud, Impact Level 4, Ingest Data, Configure Navy Functional Requirements III 30 days Host NAMS in Digital Twin of ACS in cloud, Impact Level 4, connect NAMS to simulated external interfaces (not live) IV 30 days Configure NAMS to meet Navy certification requirements (Financial Improvement & Audit Readiness, Navy compliance) V 60 days Interim Authority to Test (IATT) Table 4 lists the milestone tasks and desired duration for completing each milestone for the NOME application Table 4: NOME Milestones MIlestones Duration Tasks I 30 days Host solutions in commercial cloud and configure functional requirements. II 30 days Host NOME in Digital Twin of ACS in cloud, Impact Level 4, Ingest Data Sets, Impact Level 4, Configure Navy Functional Requirements III 30 days Host NOME in Digital Twin of ACS in cloud, Impact Level 4, connect NOME to simulated external interfaces (not live) IV 30 days Configure NOME to meet Navy certification requirements (Financial Improvement & Audit Readiness, Navy compliance) V 60 days Interim Authority to Test (IATT) 8

9 4.5 Prototype Durations: The Government s preference is to complete all prototypes within six months unless industry determines a longer duration is required to support completion of successful prototypes. 9