OPUS Suite Utilization in Maritime Readiness Based Sparing

UNCLASSIFIED

OPUS Suite Utilization in Maritime Readiness Based Sparing Presented to:

Systecon OPUS Conference Presented by:

Justin Hietsch: NAVSEALOGCEN Reliability Engineering Division POC: Riley Wingert riley.p.wingert.civ@us.navy.mil 16 April 2024 UNCLASSIFIED

Agenda

• Readiness Based Sparing (RBS)

– Policy and Objectives ACCESS LEVELS – Navy Common Readiness Model (NCRM) – RBS System Modeling – Modeling Data – Supply/Provisioning Data – NAVSEALOGCEN OPUS Suite Usage – MARRC-RB – Commonly Encountered Issues

2

RBS Policy and Objectives OPNAVINST 4442.5B

• Provide the range, depth, and location of spares:

‒ Support required readiness objectives at least cost ‒ Given the reliability and maintainability characteristics of a system/equipment

• “Operational Availability (Ao) is the primary measure of material readiness for weapon systems and equipment“ ‒ ‒ ‒ ‒

Historical and/or predicted failure information Many simulated deployments Repair time and logistics delay Models complex situations with multiple variables

OPNAVINST 3000.12 B

• Ao is defined as: UPTIME UPTIME + DOWNTIME

=

MTBF .

MTBF + MTTR + MLDT (Design-Driven)

(Support-Driven)

3

Navy Common Readiness Model (NCRM)

• A decision support capability to optimize resources ($) and readiness • A maintenance, supply, and manpower resource optimization model to dynamically meet mission readiness requirements • Will be developed and utilized by Chief of Naval Operations (OPNAV), System Commands (SYSCOMs), and the Fleet ‒ Establish early program performance requirements ‒ Analyze Ship/Submarine design for readiness during the Systems Engineering Process ‒ Establish readiness budgets for Systems/Ships/Strike Groups/Fleet

4

Navy Common Readiness Model (NCRM) cont.

• Model will reflect the requirements and detailed design (LRUs, redundancy, criticality, tie to mission, etc.) for all Systems, Ships, and Submarines • Planned to leverage COTS software, including OPUS Suite and Windchill Risk & Reliability

5

RBS System Modeling • Critical list of systems selected by community ‒ Redline systems ‒ New acquisition systems ‒ Troubled systems

• Prioritized by program

‒ System criticality ‒ Data availability and accuracy ‒ Readiness impacts

6

RBS Modeling Data • In Service Engineering Agent (ISEA) coordination for validation ‒ Design Reference Mission (DRM) ‒ Operational profile ‒ Reliability Block Diagram (RBD) ‒ System boundaries ‒ Provisioning data ‒ RBS candidates ‒ RBS results and part selection

The foundation for valid model results is proper Provisioning.

7

Supply/Provisioning Data • Part Data:

‒ Part number / National Stock Number ‒ Quantity per Assembly (QPA) ‒ Failure rate ‒ Part Military Essentiality Code (MEC) ‒ Unit price ‒ Additional part descriptors

• Configuration/LRU data mapped to RBD • Default Logistical Delay Times

8

NAVSEALOGCEN OPUS Suite Usage • Only use OPUS10 v2023 and SIMLOX v2023 • Typical Model Constraints used include:

‒ Scenario Type: Steady-State ‒ Spares Problem Type: Either Initial or Replenishment ‒ Aggregation Type: Hardware and Subsystem ‒ Task Type: Use only Replace ‒ Lead Time: No delay at depot upon ship requisition request

• Single variant modeling: one ship configuration used as baseline after reviewing available configuration data • 15 day default used for logistics delay time • 2 hour default used for part retrieval and MTTR • Mission profile can be dependent on ship class (e.g.

Littoral Combat Ships) or the system being modeled • Single maintenance level 9

MARRC-RB

NAVSEAINST 4441.12A/ NAVSUP 4441.37A

• MARRC-RB

‒ Maritime Allowance Readiness Based Sparing Reprovisioning and Change Review Board ‒ Joint NAVSEA/NAVSUP instruction ‒ Purpose to enforce the Maritime Allowance Policy ‒ Review all RBS packages, ACRs, and AERs • Reviews and approves all maritime RBS packages ‒ Packages can be submitted both internally and externally ‒ Can return packages to the modeler for correction

10

MARRC-RB cont.

• MARRC-RB Review and Approval Process

‒ Model is submitted via the MARRC-RB Repository ‒ Model is assigned a validator to review model for adherence to RBS policy and accuracy ‒ Validator reports back to submitter of any required changes or notifies MARRC-RB Gatekeeper model meets requirements ‒ Gatekeeper confirms funding requirements and submits RBS packages to MARRC-RB co-chairs ‒ Co-chairs ensure all instructions have been adhered to; Signing or sending back all reviewed packages ‒ Approved allowance overrides can be loaded to the SAF using unique ship/system/part information 11

Endurance Supply (ES) • OPNAVINST 4442.5B amendment (NAVADMIN 06/23) adds Es ‒ New readiness threshold ‒ ES measures the days a system remains fully operational without an off-ship requisition ‒ Target 85% confidence level that a system remains available for 90 days without replenishment ‒ ES can only be used for the systems listed in the amendment

12

In Review • RBS policy instruction overview • NCRM and data sourcing/input • OPUS usage and assumptions • Model results review via MARRC-RB • Policy and OPUS modeling work together to ensure accurate, reliable results

14

Questions?

15