NAVSUPINST 4441.37A - NAVSEAINST 4441.12A - MARRC-RB (04 SEP 2020).pdf

DEPARTMENT OF THE NAVY

NAVAL SEA SYSTEMS COMMAND

WASHINGTON NA\'\' YARD DC 20376-0001

NAVAL SUPPL\' S\'STE:\IS COM:\IAND

MECHANICSBl1RG PA 17055-0791

NAVSEA INSTRUCTION 4441.12A

NAVSUP INSTRUCTION 4441.37A

From: Executive Director, Naval Sea Systems Command Vice Commander, Naval Supply Systems Command

NA VSEAINST 4441.12A

NAVSUPINST 4441.37A

SEA 06L/NA VSUP N4 l 2

SEA OOB/340

4 Sep 2020

Subj: MARITIME ALLOWANCE READINESS BASED SPARING, REPROVISIONING

AND CHANGE REVIEW BOARD

Ref: (a) OPNA VINST 4441.12D

(b) OPNAVINST 4442.SA

(c) NAVSUP P-488

Encl: (1) General Instructions Related to the MARRC-RB RBS System Checklist

(2) General Instructions Related to the MARRC-RB NON-RBS Major Reprovisioning

Systems Checklist

(3) General Instructions Related to the MARRC-RB Allowance Change

Request/Allowance Change Request-Fixed (ACR/ACR-F) Checklist

(4) General Instructions Related to the MARRC-RB Allowance Exception Request

Checklist

(5) General Instructions Related To Using Interim Navy Common Readiness Model

(NCRM) Tools

(6) Interim Navy Common Readiness Model (NCRM) Required Data Element

Parameters

(7) Interim Navy Common Readiness Model (NCRM) Required Simulation Data

Element Criteria

(8) Reliability Block Diagram Criteria

I. Purpose. To establish a joint Maritime Allowance Readiness Based Sparing (RBS), Reprovisioning, and Change-Review Board (MARRC-RB) to review and approve RBS optimizations and all major Naval Sea Systems Command (NAVSEA) reprovisioning efforts that result in changes to maritime allowances. This joint instruction establishes the allowance management oversight by Naval Supply Systems Command (NAVSUP) as required by Office of the Chief of Naval Operations (OPNAV) per references (a) and (b) as well as the associated funding and allowancing technical data by NA VSEA Logistics Director; Assistant Deputy Commander for Logistics Support (SEA 06L).

2. Cancellation. NAVSEAINST 4441.12 and NAVSUPINST 4441.37.

3. Scope and Applicability

NAVSEAINST 4441.12A

NAVSUPINST 4441.37A

4 Sep 2020

a. This instruction applies to proposed maritime allowances resulting from:

(1) RBS optimizations, (initial, re-optimizations, and back-fits);

(2) Allowance Change Requests/ Allowance Change Request-Fixed (ACRI ACR-F) as defined in reference ( c );

(3) Allowance exception requests; and

( 4) Major re-provisioning efforts. Major re-provisioning is defined as:

(a) An effort which will result in the increase range and depth of spare and repair part allowances of a platform (e.g., ship/shore activity Unit Identification Code), or of a major weapons system, by more than 30 percent; or

(b) An effort which will result in an Other Procurement Navy-8 (OPN-8). Weapons Procurement Navy (WPN-6) or Ship Construction Navy (SCN) buy-out of more than $250,000· or

(c) As directed by Director, Supply, Ordnance and Logistics Operations (OPNAV N41) or NA VSEA Program Executive Office (PEO).

b. Generally excluded are requirements detem1inations specifically governed by separate policy, such as TRIDENT Submarine (SSBN) Hull, Mechanical and Electrical (HME) and Strategic Weapons System (SWS) Coordinated Shipboard Allowance Lists (COSALs) nuclear reactor plant program material (Q COSAL) under the cognizance ofNAVSEA Nuclear Propulsion office (SEA 08), bulk petroleum, and controlled cryptographic material.

4. Policy

a. The MAR RC-RB will provide oversight and discipline of allowances arising from RBS, re-provisioning efforts, ACR/ACR-F, or allowance exception requests to ensure they are technically compliant, planned, budgeted/funded and valid per prevailing maritime allowance policy.

b. The MARCC-RB will identify potential policy issues that need to be reviewed and provide recommendations to the Allowance Working Group for consideration.

c. The MARRC-RB will be comprised of representatives from:

NA VSEAINST 4441.12A

NAVSUPINST 4441.37A

4 Sep 2020

(I) NAVSUP Deputy Director, N41B for Supply Chain Management (Co-chair)

(2) NA VSEA 06L Deputy Director Readiness and Logistics (Co-chair)

(3) NAVSUP Weapon Systems Support (WSS) Maritime Allowance and Outfitting Department (N43)

( 4) Naval Sea Logistics Center (NSLC) Life-Cycle Logistics Support Department Code

d. Resolution of specific issues may require expertise to address specific concerns and process changes. The MARRC-RB will engage and request participation as needed from:

(I) NA VSUP Business Systems Center (BSC)

(2) Commander, U.S. Fleet Forces Command (USFF) Fleet Supply (N4l)and Commander, U.S. Pacific Fleet (COMPACFLT) Fleet Supply (N4)

(3) In-Service Engineering Agent (ISEA)

(4) Hardware Systems Command (HSC) /Program Offices

(5) Program Executive Offices (PEO)

(6) NA VSUP WSS Program Manager (PM)

(7) OPNAV

5. Responsibilities. The activities designated as primary participants in the MARRC-RB will assign a representative to serve as a member on the review board. The NSLC Gatekeeper (GK) will coordinate the scheduling and create the agenda for the meeting. The agenda will include the system RBS optimizations, ACR requests, allowance exceptions, and proposed major re provisioning actions. Any member of the board or Program Offices, PEOs, and ISEAs may request an unscheduled/emergent meeting through the Review Board coordinator to address critical or urgent issues.

a. MARRC-RB will:

(1) Convene (monthly (second Tuesday of the month) or as required) meetings to review the pending RBS optimizations and major re-provisioning efforts.

(2) Per enclosures (I) through (8), deploy the checklists and procedures to facilitate the

NA VSUPINST 4441.3 7 A

4 Sep 2020 approval or denial of RBS (initial, re-optimizations, and back-fits), re-provisioning efforts, ACR, and allowance exception requests (see paragraph 8 for access to updatable checklists).

(3) Communicate with stakeholders regarding MARRC-RB decisions.

(4) For RBS systems, validate the cost effectiveness of the presented Operational Availability (Ao). In this regard, the MARRC-RB may make recommendations to adjust the modeled Ao target during the system review.

(a) The Program Office, in conjunction with the OPNAV Warfare Systems Resource Sponsor (OPNAV N9), must be afforded the oppo11unity to meet and discuss the recommendations of the MARRC-RB to adjust the modeled A0 target and repo11 their decision to the MARRC-RB.

(b) The HSC Program Office must coordinate the necessary action, with a system's OPNA V N9 Resource Sponsor, to obtain approval for a recommended deviation from any OPNAV Ao goal/value.

(5) Ensure all decisions and data files are provided to designated NAVSEA GK, NSLC, for processing.

(6) Any member can request an additional review if there are any issues with the Standard Allowance File Tool (SAFT) updates.

b. NA VSEA 06L will:

(1) Co-chair the MARRC-RB.

(2) Provide management and oversight for all actions associated with programming, coordinating, budgeting, justifying, defending, and executing requirements for OPN-8, WPN-6, and SCN outfitting spares requisitions.

(3) Ensure implementation of this policy and provide updates as needed.

c. NA VSUP will:

(1) Co-chair the MARRC-RB.

(2) Provide management and oversight for all actions associated with coordinating and executing Maritime allowance requirements.

(3) Provide oversight and guidance for NAVSUP WSS provisioning processes.

4 Sep 2020

(4) Ensure implementation of this policy and provide updates as needed.

d. NA VSUP WSS N43 will:

( 1) Refer all requests for allowance exception oven-ides to the NSLC GK for coordination and scheduling with the MARRC-RB.

(2) Monitor allowances to identify significant equipment/system specific allowance adds/increases and modifications to ensure validity.

(3) Report any suspected unauthorized/unapproved allowance Adds/Increases/Modifications to the NSLC GK for review by the MARRC-RB.

( 4) Provide allowancing process technical oversight to ensure any decision made by MARRC-RB is functionally possible within the scope of the allowancing process.

(5) Develop and maintain a database repository for the upload and controlled access of all RBS, ACRI ACR-F, allowance exception, and re-provisioning requests including cross reference identification numbers, aitifacts and details of the final MARRC-RB adjudication.

e. NSLC will:

( 1) Serve as the NA VSEA point of entry ("Gatekeeper") for all requests for allowance changes.

(2) Serve as the coordinator for the MARRC-RB including scheduling and developing the agenda.

(3) Provide updates to the database repository for all submitted RBS, ACR requests, allowance exception requests, and re-provisioning requests, regardless of disposition, to include details of final MARRC-RB adjudication as well as the following:

(a) Coordinate with NA VSUP WSS to ensure an identification number is assigned by type and date to facilitate access to entries in the repository.

(b) The details of the request including copy of the checklist, MARRC-RB disposition and for RBS systems the following data:

l. Model

2_. Reliability Block Diagram

J_.

1_.

Q.

z .

Boundary of model

Mission profile

Configuration profile

RBS curve with target A0

Part file

NAVSEAINST 4441.12A

NAVSUPINST 4441.37A

4 Sep 2020

.8_. Ao reference (e.g. Capability Development Document/Capability Development Plan)

(4) Verify funding is available for allowance modifications, (adds/increases), as a result of RBS or re-provisioning.

(5) Process RBS, ACR/ACR-Fs and allowance modifications based on the MARRC-RB decisions, including forwarding Standard Allowance File (SAF) updates to NAVSUP WSS N43.

6. Records Management

a. Records created as a result of this instruction. regardless of format or media, must be maintained and dispositioned according to the records disposition schedules found on the Directives and Records Management Division (DRMD) p01ial page:

https: //portal.secnav.nav,,.mi l/orgs/DUSNM/DONAA/DRM/SitePages/Home.aspx.

b. For questions concerning the management of records related to this instruction or the records disposition schedules, please contact your local Records Manager or the DRMD program office.

7. Review and Effective Date. Per OPNA VIN ST 5215.17 A, NA VSEA 06L and NA VSUP N4 will jointly review this instruction annually around the anniversary of its issuance date to ensure applicability, currency, and consistency with Federal, Department of Defense, Secretary of the Navy, and Navy policy and statutory authority using OPNA V 5215/40 Review of Instruction.

This instruction will be in effect for 10 years, unless revised or cancelled in the interim, and will be reissued by the 10-year anniversary date if it is still required, unless it meets one of the exceptions in OPNA VIN ST 5215.17 A, paragraph 9. Otherwise, if the instruction is no longer required, it will be processed for cancellation as soon as the need for cancellation is known following the guidance in OPNA V Manual 5215.1 of May 2016.

8. Forms. The following forms are available for download from the Naval Forms Online

NAVSUPINST 4441.37 A

4 Sep 2020

(NFOL) Web site at: https://navalforms.documentservices.dla.mil/web/public/home and the MARRC-RB Repository Web site at: https://my.navsup.navy.mil/apps/ops$rbs.home.

a. NA VSEA 4441/3 MARRC-RB RBS Systems Checklist

b. NAVSEA 4441/4 MARRC-RB Non-RBS Major Reprovisioning Systems Checklist

c. NAVSEA 4441/5 MARRC-RB ACR/ACR-F Checklist

d. NA VSEA 4441/6 MARRC-RB Allowance Exception Request Checklist

e. NA VSEA 4441/3 MARRC-RB Interim Navy Common Readiness Model (NCRM) Required OPUS Parameters

f. NAVSEA 4441/3 MARRC-RB Interim Navy Common Readiness Model (NCRM) OPUS 10 Suite SIMLOX Data Element Criteria

g. NAVSEA 4441/3 MARRC-RB Reliability Block Diagram Criteria

WENDELKEN• KUR O,grt,iy,,gned by'l',EtlOELKEtl KURT J 1026100441

T.J.1026100441

K. J. WENDELKEN

Vice Commander o,te 202oos 1s 12 57 21-o.ioo

Naval Supply Systems Command

Releasability and Distribution:

SMERCHANSKY JA Digitallysignedby

· SMERCHANSKY JAMES H.1230156

MES. H.12301563~4 t~ie: 2020.09.04 oa.41:39 -04·00·

J. H. SMERCHANSK Y

Executive Director Naval Sea Systems Command

This instruction is cleared for public release and is available electronically only via the Naval Logistics Library (NLL) Web site, https://nll.navsup.navy.mil/and via the NA VSEA Portal Web site, https://navsea.portal.navy.mil.

4 Sep 2020

GENERAL INSTRUCTIONS RELATED TO THE

MAARC-RB RBS SYSTEM CHECKLIST

I. The Maritime Allowance Readiness Based Sparing (RBS), Reprovisioning, and Change Review Board (MARRC-RB) System Checklist will be utilized for initial and follow-on optimization actions for RBS systems.

a. The checklist form must be signed by the co-chairpersons and must indicate the approval or disapproval of the system's RBS analysis.

b. The checklist will be published and distributed with the minutes of the meeting and filed in the MARRC-RB repository.

2. The Hardware Systems Command/Program Executive Office (HSC/PEO) Program Managers (PM) must schedule a MARRC-RB review of their completed RBS analyses via the NSLC "Gatekeeper" (GK) at the earliest opportunity, but no later than 1 month prior to the desired update of the Standard Allowance File Tool (SAFT).

a. In addition to the required MARRC-RB member attendees, a member of the RBS team performing the actual RBS analysis should also attend as required.

b. Verify that the checklist was assigned a unique "Identification Tracking Number" and creation date for subsequent reference and access in the central MARRC-RB repository.

3. The HSC PM or designated member of the RBS analysis team will fill out and provide sections I through III of the checklist to the MARRC-RB no later than 2 weeks prior to the scheduled date of the review. If a contractor has performed the RBS analysis/optimization, specify contractor name and POC(s). Although most of the entries are self-explanatory, the following specifics apply to Section I:

a. RBS Types can be either Initial Optimizations or Re-optimizations. Backfits can apply to either of these types. If additional clari Ii cation is required beyond type, use the remarks block accordingly.

b. For Re-optimizations, please provide the most "Current Actual Operational Availability (Ao)'' as well as the "Source" of this data and the "Reason" for the system' s re-optimization.

c. For all RBS types, provide:

(I) "Ao Threshold" (aka, Minimum Acceptable A0 ), the "A0 Target Objective" (e.g., the ultimate Ao value or target goal), and the Modeled A0 •

Enclosure (1)

4 Sep 2020

(2) Source and the document reference that authorizes/establishes the above Ao values.

4. Upon MARRC-RB approval, the SAFT will be loaded with the resultant overrides and will include activation dates.

5. The MARRC-RB will validate the following:

a. System A0 goal:

(1) Source of Ao goal ( e.g., Test and Evaluation Master Plan requirement, Capability Development Document /Capability Development Plan. Top Level Requirement, Weapon Spec, etc.)

(2) Accompanying documentation

(3) Reasonableness of Ao goal

( 4) Application of Multi-Tiered RBS

b. RBS model used:

(1) Navy approved (e.g., Interim Navy Common Readiness Model (NCRM) (OPUS Suite)), or,

(2) OPNAV approved alternative or OPNAV waiver letter for an unapproved model

c. Availability of Program Supp011 Data.

d. NA VSUP WSS Buy-In funding and material availability.

e. NAVSEA 06L4 Buy-Out funding.

f. The Ao value achieved by the system when zero spares are provided (this figure provides a baseline value for comparison with the target Ao RBS analysis result).

g. The A0 value achieved and associated cost savings by using Maintenance Assist Modules (MAMs) as spares.

h. The Ao value achieved when RBS sparing (referred to as Enhanced RBS) is designated to augment/supplement the existing range/depth of authorized spares.

1. Multi-Tiered RBS Ao (lesser of 5 percent below target Ao or knee of curve)

2 Enclosure ( 1)

4 Sep 2020 analysis including the cost savings (see reference (b), para 5.b and 7.a. (3) for fm1her detail and definition).

J. Source and reasonableness of reliability parameters.

(1) Mean Time Between Failures (MTBF)

(2) Mean Time To Repair (MTTR)

(3) Mean Requisition Response Time

3 Enclosure ( 1)

4 Sep 2020

GENERAL INSTRUCTIONS RELATED TO THE

MARRC-RB NON-RBS MAJOR REPROVISIONING SYSTEMS CHECKLIST

l. The Maritime Allowance Readiness Based Sparing (RBS), Reprovisioning, and Change- Review Board (MARRC-RB) Non-RBS Reprovisioning Systems Checklist will be utilized for major reprovisioning efforts as defined in the MARRC-RB instruction.

2. The NAVSUP Weapon Systems Support (WSS) Program Manager (PM) in coordination with the Hardware Systems Command (HSC) Program Office and In-Service Engineering Agent (ISEA) will provide the initial notification of a proposed reprovisioning effort to the Naval Sea Logistics Center (NSLC) Gatekeeper (GK) providing sufficient data to fill out all of Section I and portions of Section II of the MARRC-RB Non-RBS Major Reprovisioning Systems Checklist.

a. To facilitate the assessment and determine the return on investment (ROI), break out of spares data by new installs and backfits for existing installs is required.

(I) For New Installs the full range, depth and cost of spares must be provided.

(2) For reprovisioning backfit/applied to existing installs, both the range/depth/cost of Adds and Increases as well as Deletes and Decreases (to existing sparing) must be provided.

3. Verify the checklist was assigned a unique Identification Tracking Number and creation date for subsequent reference and access in the central MARRC-RB repository.

4. The NAVSUP WSS PM must be prepared to present a brief summary of the reprovisioning effort to include justification and funding requirements.

5. The MARRC-RB will utilize this checklist form to document the proceedings and results of the reprovisioning validation review as follows:

a. The checklist must be signed by the co-chairpersons and must indicate the approval or disapproval of the system's reprovisioning results.

b. The checklist form will be retained by the MARRC-RB coordinator and will be distributed with the minutes of the meeting and filed in the MARRC-RB repository.

Enclosure (2)

4 Sep 2020

GENERAL INSTRUCTIONS RELATED TO THE MARRC-RB

ALLOWANCE CHANGE REQUEST/ALLOWANCE CHANGE REQUEST

FIXED (ACR/ACR-F) CHECKLIST

1. The Maritime Allowance Readiness Based Sparing (RBS), Reprovisioning, and Change Review Board (MARRC-RB) will review and approve Allowance Change Requests/Allowance Change Request-Fixed (ACR/ACR-F). The objective is to ensure recommended ACR/ACR-F approvals are supported by a thorough technical review and data (e.g. , demand, maintenance, configuration, and criticality). Review criteria and thresholds for J\CR/ACR-F to be determined by the review board.

2. The MARRC-RB must utilize this AC R/ACR-F checklist to document the proceedings and record the final decisions.

a. For ACRs, the Naval Sea Logistics Center Gatekeeper will provide the data to complete Section I of the checklist. Since ACRs are consumable and primarily Defense Logistics Agency low cost items, Section II of the checklist is not required.

b. For ACR-Fs, the NAVSUP Weapon Systems Supp011 (WSS) Program Manager (PM) will provide sufficient data to complete Section I and, when the ACR-F is either an add or an increase, complete Section II.

Please note that the originally submitted ACR/ACR-F should include all the information that is required in Section I of this checklist and can be attached in lieu of filling out the checklist.

3. The MARRC-RB will ensure necessary funding and material are available to support all approved allowance changes generated by approved ACR/ACR-Fs.

4. The WSS PM will also load Planned Program Requirements for all approved ACR-F adds and increases as required.

Enclosure (3)

4 Sep 2020

GENERAL INSTRUCTIONS RELATED TO THE MARRC-RB

ALLOWANCE EXCEPTION REQUEST CHECKLIST

I. The Maritime Allowance Readiness Based Sparing (RBS), Reprovisioning, and Change Review Board (MARRC-RB) will review and approve/disapprove requests for overrides to manually adjust (Add/Increase or Delete/ Decrease) allowances originating from non-traditional sources (e.g., NAVSUP Weapon Systems Support (WSS) Program Managers (PMs), Hardware System Commands (HSCs) and In-Service Engineering Agents (ISEAs)). This excludes changes resulting from Fleet Allowance Change Requests/Allowance Change Request-Fixed (ACR/ACR- F), RBS optimizations and major re-provisioning efforts addressed in enclosures

(I) through (3) of the MARRC-RB instruction.

2. At a minimum, the NA VSUP WSS PM (in coordination with the HSC and/or ISEA as necessary) will provide the initial notification of a proposed allowance exception/modification request to the Naval Sea Logistics Center (NSLC) Gatekeeper (GK), providing sufficient data to fill out all of Section I and Section II (for Adds/Increases only) of this checklist.

3. The NSLC GK will monitor and collect requests for manual overrides for MARRC-RB review and disposition. Additionally, the repository will automatically assign each checklist a unique Identification Tracking Number and creation date (verified by the NSLC GK) for subsequent reference and access in the central MARRC-RB repository.

4. Following completion of an upgraded and expanded NA VSUP Web based ACR program, which will require the submission of all allowance changes/exceptions as well as pertinent review data, the submitting activity can attach the Web based form for MARRC-RB review and approval. The latter eliminates the need to fill out Section I of this checklist.

5. For multiple line-item entries against a single system Allowance Patts List, submission of an attachment to the check list listing the items is acceptable. However, it should be noted that submissions of this nature may be considered a re-provisioning and follow the Non-RBS Major Reprovisioning Systems Checklist, enclosure (2), of the MARRC-RB instruction guidelines.

6. The NA VSUP WSS PM must be prepared to present a brief summary of the request to include justification and material/funding requirements (for adds/increases only).

7. The MARRC-RB must utilize the checklist form to document the proceedings and results of the review as follows:

a. The checklist must be signed by the co-chairpersons and must indicate the approval or disapproval of the requested allowance modification.

Enclosure (4)

4 Sep 2020

b. The MARRC-RB will also ensure necessary funding and material are available to support all approved allowance changes generated by approved allowance exception requests.

c. The checklist form will be retained by the MARRC-RB coordinator and will be distributed with the minutes of the meeting and filed in the MARRC-RB repository.

2 Enclosure ( 4)

4 Sep 2020

GENERAL INSTRUCTIONS RELATED TO USING

INTERIM NA VY COMMON READINESS MODEL (NCRM) TOOLS

1. These instructions provides additional guidance and data standards used within the Interim NCRM Suite to MARRC-RB Co-Chairs, Hardware Systems Command (HSC), Program Executive Office (HSC/PEO) Program Managers (PM), Program Acquisition Resource Managers (PARM), Technical Support Activities (TSA), In-Service Engineering Activities (ISEA) and other NCRM Practitioners for initial/ updates to retail allowances, and for development ofrequired authoritative Maritime Reliability Block Diagrams (RBD).

2. This guidance applies to proposed Maritime allowances submitted to the MARRC-RB review/ approval process resulting from Interim NCRM Readiness Based Sparing (RBS) and SIMLOX derived allowance optimizations, such as initial, re-optimizations and back-fits.

3. As stated previously, generally excluded are requirements determinations specifically governed by separate policy, including TRIDENT Submarine (SSBN) Hull, Mechanical and Electrical (HM&E), Strategic Weapons System (SWS) Coordinated Shipboard Allowance Lists (COSALs), nuclear reactor plant program material (Q COSAL), bulk petroleum and controlled cryptographic material.

4. If the Interim NCRM is used for SSBN, HM&E, SWS COSAL, nuclear reactor plant program material, bulk petroleum and controlled cryptographic material, reference (a) and this MARRC-RB Instruction Supplement applies.

5. The OPNAV approved Maritime RBS model is transitioning to NCRM. The interim approved RBS model is the OPUS Suite. All Maritime system/ equipment programs, acquisition category (ACA T) and non-ACAT, should use the NCRM interim OPUS Suite RBS model and associated Maritime required RBDs for all new, altered or updated systems I equipment sparing.

6. RBS Model Result Presentation. The system I equipment Product Support Manager (PSM), or designated representative, attendance at the MARRC-RB is strongly recommended for presenting RBS candidates submitted to the MARRC-RB. If questions arise, and the PSM or representative is not in attendance, RBS candidates will be deferred until the next MARRC-RB.

Enclosure (5)

Table

ControlParametcrs

GlobalParameters

System

Item

I tcmStructurc

Station

StationStructurc

SystemDepk>) ment

SystcmRepair ltemReorder

NA VSEAINST 4441.12A

NAVSUPINST 4441.37A

4 Sep 2020

INTERIM NA VY COMMON READINESS MODEL (NCRM)

REQUIRED DAT A ELEMENT PARAMETERS

Required OPUS Parameters Column ID Description Input

STYPE Scenario type STEADY-ST A TE PTYPE Spares problem type INITIAL PRMOE Primary MoE A NPOINT Number of points 50 MINMOE MinimalMoE 0 MAXMOE Maximal MoE I SCLEN Scenario length 0 SCTIM Scenario Start Time 0 CURRN Currency name $

SID System Identifier Insert System Name 110 Item identifier NIIN* DESCR Description EQUIPMENT NOMEN* PRICt Unit price UNIT PRICE* FRT Failure rate ''=( IOOOOOO*BRF)/8760" 0

TYPE Type DU IID Subitem identifier NIIN* MID Motheritem or system identifier Insert System Name QTYPM Quantity per motheritem Integer Number, varies for each item* STID Station identifier "WHOLESALE"; "SHIP STOREROOM"; "SHIP" QTY Total quantity I TYPE Type DEPOT;OP MAXST Maximal Stock 0 for "Wholesale" and "Ship" STID Station identifier "SHIP";"SHIP STOREROOM" MSTID Mother station identifier "SHIP STOREROOM";"WHOLESALE" TFRMS Time from mother station 2.0; 360 TTOMS Time to mother station 2.0; 360 SID System identifier Insert System Name USTID Unit or station identifier "SHIP" QTYPS Quantity per unit or station I UTIL Utiliz.ation per calendar time 8760 SID System Identifier Insert System Name STID Station ldentif ier "SHIP" SUROT Subitem Replacement TAT (MTTR) 2 SURPF Subitcm Replacement Item Fraction I IID Item identifier NIIN* STID Station identifier "WHOLESALE" LEADT Lead time 0 MINRS Minimal reorder size MRU*

Enclosure ( 6)

Optional OPUS Parameters Table Column ID Description

RUD Redundancy Link Identifier SID System Identifier

Redundancy NRL Number of Redundanc" Links NRLRQ Number of Required links ACPA Active/Passive Option TS\\OV Time to switch over RLID Redundanq Link Identifier

RedundancyLink Ill) Item identifier QTYPL Quantity per link

NA VSEAINST 4441.12A

NAVSUPINST 4441.37 A

4 Sep 2020

Input Insert unique Identifier for Redundanc) Link

Insert S,stem Name lntergcr number of links

Integer number of links required

ACTIVE: PASSIVE

Delay time to switch to redundant link Insert unique Identifier for Redundancy Link

NIIN*

Quanitity of each item in a single redundancy link

* Note: For values of ITEM FRT (Failure Rate) and System Deployment UTIL (Utilization per Calendar Time) use actual system / equipment operational/ actual run-time; if the operational / actual run-time is not accurately known use the default value of 8,760.

2 Enclosure (6)

4 Sep 2020

INTERIM NA VY COMMON READINESS MODEL {NCRM)

REQUIRED SIMULATION DAT A ELEMENT CRITERIA

Required SIM LOX Parameters TABLE Column ID Opus Suite Description Input

NREPS Number of replications 100 SIMPE Simulation period From DRMP RSEED Random seed 123456789

Control /\I'll) Allocation Point Identifier Stock Allocation Point Identifier (from OPUS C/E curve)

RCINT Result collection interval 0.5 RCSTA Result collection start time 0 REI.OP Reliability option RBD; REDUNDANCY MTID Mission type identifier Mission Phase Identifier NOS Nominal numhcr of systems Quantity of Systems being analyzed

Mi,sionType MNOS Minimum numhcr of systems Quantity of Systems being analv.cd DURN Mission duration From DRMP MPAT Mission Pattern CONTINUOUS PRID Profile identifier Mission Profile Identifier SPRID Subprolilc identifier MTID from Mi,si<.mTypc

OperationProlile STIM Start time From DRMP ITYPE Initiation tvDe SCHEDULED IQTY Initiation quantitv I

Operations USTID Operational Mode Identifier "SHII'" PRID Profile identifier Mission Profil.: ldcntilicr POINT Point Identifier Stock Allocation Point Identifier ( from OPUS C/E curve) 110 Item identifier NII N

Stoc k/\llocation STII) Station identilkr "SI Ill' STOREROOM" STSIZ Stock size Quanititv of item, allowed ROSIZ Reorder svc MRU

Optional SIM LOX Parameters TABLE Column ID Opus Suite De sc ription Input

NBREQ Number of hkx:ks required NBOP Number of hkx:ks in operation

RI3DParallel TSWOY Time to switch over ONI.M Online maintained RBID Parallel block identifier SRBID Suh block identifier

RBl)l'arallelStructure OPMID Operational mode identifier <DEFAULT> QTYPB Quantity per hkx:k RBID Series hlock identilkr

RBDSerics RBID Series block identilkr SRBID Sub block identilkr

Rill )ScricsStructure Ol'MID Operational mode identifier <DEFAULT> QTYPB Quantity per hk,ck POINT Point identifier

OpcrationalModes OPMID Operational Mode Identifier MTID Mission Type ldcntilkr

MissionOpcrationalModes SID System Identifier Ol'MID Operati<.mal Mode Identifier MID Materiel Identifier

MaterialOpcraticmalModcs OPMID Operational mode identifier <DEFAULT> R131D Reliabilitv block identifier USERT Usage Rate <1.0>

Enclosure (7)

4 Sep 2020

RELIABILITY BLOCK DIAGRAM (RBD) CRITERIA

1. This enclosure describes criteria for developing Maritime standardized ship system RBDs.

a. RBDs are used primarily for input to Readiness Based Sparing (RBS) related simulation and analytic models to calculate system reliability and operational availability (Ao). These RBDs within RBS models are typically used to determine maintenance repair pa11s sparing to meet those reliability and Ao metrics at affordable cost or as an analysis metric showing a platform's operational availability over select time periods.

b. The RBD will be developed/designed in early acquisition and updated to 'As Delivered' configuration after Post Shakedown Availability/Delivery. Similar to Configuration records, engineering changes and alterations that change the equipment/system data update/revise the RBD. A record of the RBD will be saved along with justification for the RBD update for historical purposes.

c. RBD depicts system elements and system operation and denotes the operational modes and redundancy of the elements for the platform modeled. Systems I equipment modeled for each platform can include propulsion, electrical, auxiliary, steering, navigation, combat, exterior and interior communications, etc.

d. RDBs are typically a pictorial form of a system showing interdependencies among mission essential system elements (subsystem, equipment, etc.). A complete understanding of the system's mission is required to produce a valid RBD. In addition to the pictorial representation of a system, reliability engineers should provide the RBD in table format to assist practitioners in establishing data for simulations.

2. General Requirements

a. RBDs are linked to Design Reference Mission (ORM) which defines the percentage of time during a mission phase that the equipment I system is used during execution of the function performed. For example, a surface search radar may only use short pulse transmission to improve close target recognition during sea and anchor detail which is a smaller subset (percentage) of operational time than transit. The RBD would take into account the operating requirements for different mission phases. Each system should have a top-level RBD representing its configuration for each phases of the mission profile for the platform.

b. Across the Maritime Enterprise only ONE RBD is used for an equipment/ system to platform/ unit configuration. For example the RBD for an identical AN/SQQ-89 on a DDG51 Flight II Class destroyer will have a different RBD if the AN/SQQ-89 is installed on a DDG5I Flight I Class Destroyer. Further, if warranted, configurations may vary within a specific class of platform such that the RBD for an identical AN/SQQ-89 installation on the DDG5I would

Enclosure (8)

4 Sep 2020 require another RBD for the same AN/SQQ-89 installed on the DDG52.

c. Care must be given by those developing an RBD to ensure that operational success paths among all elements of the system are correctly described and proper boundaries identified for each instance of installation, i.e., different RBD per equipment / systems and platform if warranted.

d. Care must also be taken to ensure the RBDs for similar equipment / systems have identical boundaries to ensure consistent Ao metrics.

3. An RBD will include the following:

a. RBD number and descriptive title

b. Logic diagram or diagrams (blocks)

(1) Breakout of physically distinct equipment with identifiable Expanded Ship Work Breakdown Structure (ESWBS) or Functional Group Code.

(2) Engineering reliability and maintainability data, i.e .. Mean Time Between Failure (MTBF), Mean Time to Repair (MTTR), Duty Cycle, Total Available Downtime, etc.

(a) Note: Generation of readiness indices at the system level is complex and requires calculation of downtime and associated downtime indices with special attention to overlapping events and not simple counts of failure and downtime

(3) Correctly describe equipment / system functionality as series, parallel or in some cases extended parallel.

(4) Block assumptions include maintenance dependencies such as:

(a) Redundancy only

(b) Repair independent of non-failed operating blocks, etc.

(5) Block variables include:

(a) Time

(b) Cycles

( c) Events, etc. Phases matrices

2 Enclosure (8)

4 Sep 2020

1. DRM criteria typically is a day-by-day time-phased description of the operations, engagements and mission areas that the platform is expected to undergo while deployed for 120-days.

2_. DRMs are generated for ship class and approved by CNO

~. Recently platforms are re-directed and perform missions that exceed or change DRMs. which in turn may impact RBD validity.

3. Equipment Reference Profile is a series of duty cycles for each RBD Block by mission phases.

~. Multiple sets of duty cycles may be required to describe multi-mission systems.

(6) Reliability blocks typically utilizes three main formulas;

(a) Reliability;

1, Reliability(Mission Time) = e-A.t

2. A (lambda) = Failure rate = 1/MTBF

J t = mission time in cycles, hours, miles, etc.

1. e = natural logarithm = 2. 71828

(b) Reliability(System) = RI x R2 x R3 x R4 x .... RN

c. Reliability(Active Redundant Parallel System) = 1 - (1 - RI )(1 - R2)RB0s using mission free profiles (ORM not considered) are not generally valid for showing trends in material readiness, ( 1) NA VSEA Policy requires availability calculations based on ORM and an equipment reference profile.

d. All RBDs have approval and a prepared by activity and date associated with the official data.

e. Minimum RBD artifacts include (but not limited to):

3 Enclosure (8)

4 Sep 2020

( 1) Time meter assignments / runtime assumptions

(2) The parameters used to calculate the duty factors (Of / K factors)

(3) The ORM profile / DRM

( 4) Parts level

(a) Parts to block assignment-> outlining the critical and non-critical parts / Line- Replaceable Unit

(b) Part Cost (Turn in Cost or new unit replacement)

(c) Failure Mode Effects and Criticality Analysis / Level of Repair Analysis

( d) Depot I Intermediate level repair / Organizational level repair

( e) Failure rates

l. Engineering Estimates or Actuals or both

(f) Mean Supply Response Time / Mean Down Time, MTTR

l. NA VSUP policies or Actuals or both

(g) System boundaries based on (Configuration Data Managers Database-Record Index Number, ESWBS, Allowance Parts List End Item Code)

(h) Interoperability designs showing nodes and connections between systems.

4 Enclosure (8)