DI-SESS-82362

Contractor Reliability, Availability, Maintainability and Testability (RAM-T) Program Plan

This plan describes the Contractor's Reliability, Availability, Maintainability and Testability (RAM-T) Program Plan and management process to ensure the system meets all reliability requirements.

Approval DateJanuary 19, 2022

AMSC Number10277

Preparing ActivityMDA

Project NumberSESS-2021-035

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This plan describes the Contractor's Reliability, Availability, Maintainability and Testability (RAM-T) Program Plan and management process to ensure the system meets all reliability requirements. This plan documents the engineering activities and technical approach for each contracted RAM-T task including allocations, predictions, models, criticality analysis, built-in test, demonstrations, stress screening, reliability growth, stockpile reliability and failure reporting and corrective action system maintained through design, development, production, and sustainment. The principal uses of the plan are to provide a basic tool to manage the RAM-T program, ensure contractual compliance to the specified RAM-T requirements, and to insure that RAM-T is integrated into system engineering and throughout the system lifecycle to reduce operations and sustainment cost.

This Data Item Description (DID) contains the format, content, and intended use information for the data product that is generated by the specific task described in the contract.

Preparation Instructions

1FormatThe RAM-T Program Plan shall be documented in a digital format using the latest Microsoft Word document format.

2ContentThe RAM-T Program Plan shall identify and describe the activities planned by the Contractor for implementation of the RAM-T program, and shall include:

aScope / Objective.

bApplicable Documents, Standards, and Other References.

cProgram description of RAM-T contractual activitiesThe Program description of RAM-T contractual activities, the planned timing, duration, and responsible organization for each R&M and Testability activity, RAM-T requirement definition, ground rules, and process. Provide an Organizational chart that provides visibility into the resources, management and organizational structure of those responsible and accountable for the conduct of Reliability, Maintainability and BIT.

dThe approach to perform the requisite managementThe approach to perform the requisite management, design, monitoring, testing, and verification efforts for RAM-T and BIT tasks (e.g. models, allocations, predictions, fault trees, critical items lists, stress analysis, etc.), including those of the subcontractors, and methods comparing status and results to plan. Provide an integrated program schedule with all R&M and Testability test and demonstration activities aligned to major Program milestones. The schedule should include the duration of the FRACAS program and indication of Contractor or Government testing and demonstrations.

eReliability growth planning in order to meetReliability growth planning in order to meet the quantitative requirement(s) including methods, data sources, planned growth rate, factors, test resources, growth model curve(s), etc. and showing how the tasks are integrated into the program's master schedule.

fExplicitly include Mission Requirements Traceability Matrix showingExplicitly include Mission Requirements Traceability Matrix showing what mission function and non-function requirement requires software capability to support vulnerability assessments and Risk Management Framework (RMF) Assessments. Relate loss of software capability to mission capability degraded or lost.

gThe Design guidelines to be usedThe Design guidelines (e.g. Mission Profile, Failure Definitions, Sneak Circuit, Worst Case, De-Rating, Thermal Stress Analysis, Mechanical Stress Analysis, Finite Element Analysis, etc.) to be used for the reliability, maintainability and BIT tasks.

hList Government Furnished Information and Equipment necessaryList Government Furnished Information and Equipment necessary to support RAM-T design, development, and test activities and identify the use of RAM-T data sources (e.g., service maintenance data collection systems).

iDescription of the intended use of theDescription of the intended use of the Government-Industry Data Exchange Program (GIDEP) to promote and facilitate the sharing of RAM-T information.

jDescription of tests and demonstrations planned forDescription of tests and demonstrations planned for reliability, maintainability and BIT (e.g. Highly Accelerated Life Testing (HALT), Accelerated tests, Reliability Confidence Testing, BIT demonstrations, Maintainability demonstrations).

kInterrelationships of reliability, maintainability, and BIT tasksInterrelationships of reliability, maintainability, and BIT tasks, including how the resulting data will be integrated with system safety, human factors, and other system oriented tasks (e.g., design and life cycle cost analyses, level of repair analyses, availability analyses, trade-off studies, etc.).

lThe appendices listed below shall appearThe appendices listed below shall appear in the RAM-T Program plan, and should detail ground rules and assumptions, processes, models, etc., and shall use the referenced guidance:

3Software Reliability Program PlanPlan shall include:

aScope / Objective.

bApplicable Documents, Standards, and Other References.

cIdentify the roles and responsibilities associated withIdentify the roles and responsibilities associated with development of reliable software including the role of software developers, system engineers, testability engineers, and R&M engineers.

dSchedules, progress reporting, deliverables, resources of theSchedules, progress reporting, deliverables, resources of the software reliability engineering effort.

eThe plan for the design forThe plan for the design for software reliability achievement in accordance with contract requirements.

fThe plan for meeting software reliability allocationThe plan for meeting software reliability allocation requirements including the technical approach, software FEMA, model, schedule, deliverables, and integration with the system requirements baseline.

gThe plan for verification of software reliabilityThe plan for verification of software reliability including metrics, randomized level testing and system level simulation.

hThe plan for verification, validation, and accreditationThe plan for verification, validation, and accreditation for models and simulations.

4Reliability Assessment PlanPlan shall include:

aScope / Objective.

bApplicable Documents, Standards, and Other References.

cRequirements definition, ground rules, processes including modelRequirements definition, ground rules, processes including model description and verification methods to meet the quantitative requirements.

dPlans for development of a probabilistic reliabilityPlans for development of a probabilistic reliability model (e.g. National Aeronautics and Space Administration (NASA) Probabilistic Risk Assessment (PRA) model) utilizing event sequence diagrams utilizing event sequence diagrams (ESDs), fault trees, test data, failure distributions, etc., to be used for system and component Reliability assessments, projections, and growth analysis.

eAnalysis factors such as dormancy failure modesAnalysis factors such as dormancy failure modes and rates, aging, pre-launch residual failures, etc.

fPlans for a model that calculatesPlans for a model that calculates Reliability, Availability, and Maintainability from operational system operating times and corrective and preventative maintenance downtimes.

5Stockpile Reliability Program PlanPlan shall include:

aScope/ Objective.

bApplicable Documents, Standards, and Other References.

cGround rules, roles and responsibilities, process, lifeGround rules, roles and responsibilities, process, life cycle alignment, schedule, test planning, method of data collection and trending.

dOverall plan for demonstrating service and reliabilityOverall plan for demonstrating service and reliability through life cycle, to include:

1Initial service life assessment reports on expectedInitial service life assessment reports on expected component service life based on FMECA and other information available to developers;

2Identification of limited life itemsIdentification of limited life items;

3Strategy for demonstrating assessed service lifeStrategy for demonstrating assessed service life, including service life extension for ordnance and one-shots;

4Identification of initial hardware and quantityIdentification of initial hardware and quantity requirements (lot requirements for one-shots) for service life validation of limited life items;

5Activities and schedules for periodic inspectionActivities and schedules for periodic inspection, surveillance and testing of each limited life item.

eMethod of reporting including analysis resultsMethod of reporting including analysis results, data delivery, limited life items identification, performance parameters measuring degradation, and system operating life compliance.

References

—

Figures

Figure Table 1. RAM-T Appendices / Guidance

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer