MADE Module Guides > Import Configuration
Import Configuration User Guide — Introduction and Data Field Reference
Version: 3.9.1
1 Introduction
MADE includes various import configurations designed to map external tool properties with MADE. Each configuration is tailored to import specific information into the software and guide MADE into understanding which columns of the Excel file belong to fields within the MADE project. The source file shall be in .xlsx format. Each import configuration is mapped to a specific source file. Therefore, if the source file changes, the configuration must be updated, or a new configuration should be created.
This document is a guide for users to create configurations for the MADE Import capability. For configurations to be effective, the fields in the Excel files need to correspond with MADE. Below is a list of the data fields that can be populated in MADE for model items, FMEA, reliability and maintenance.
1.1 Model Item / Reliability Data Fields
| MADE Property | Definition | Location in MADE |
|---|---|---|
| Parent Item Number | A field which captures information from the Item Number field in the Properties viewer for an Item with children Items. | Properties, Advanced Properties |
| Item Number | A field which captures information from the Item Number field in the Properties viewer. | Properties, Advanced Properties |
| Item Name | The listed identifier or name of the item defined in the system model. | Properties, Advanced Properties |
| Delay Time (hrs) | That element of down time during which no maintenance is being accomplished on the item because of either supply or administrative delay. | Properties, Criticality & Reliability Editor |
| Distribution Type | A reliability function type which describes the probability at which an item will fail. | Properties, Criticality & Reliability Editor |
| Duration of operation | The operating time of the item. | Properties, Criticality & Reliability Editor |
| Exponential - MTTF | The average time an item will function or perform within its specified limits under stated conditions before it fails. Although MTTF is used for non-repairable items (i.e. run-to-failure then replaced), it is assignable for all MADE items regardless of whether they are repairable or non-repairable. | Properties, Criticality & Reliability Editor |
| Exponential - Part Failure Rate | The number of times an item may be expected to fail. It is expressed in failures per 10^6 hour. | Properties, Criticality & Reliability Editor |
| Is Critical | A designation which defines an item as critical. | Properties |
| LCN | The Logistics Control Number (LCN) structure represents a top-down physical or functional breakdown of hardware and software for use within Logistics Support Analysis (LSA). | Properties, Advanced Properties |
| MTTR | The mean time to repair represents the average time required to repair a failed item. | Properties, Maintenance Actions |
| Physical Description | Alphanumeric field to describe the physical characteristics of an item. | Properties, Advanced Properties |
| Safety Item? | A designation which defines an item as a safety item. | Properties |
| Spares on Hand | Number of replacement spares available for the system, component or part. | Properties, Criticality & Reliability Editor |
| Turn Around Time (hrs) | The period of time required to prepare a system prior to resuming scheduled operations. Turn Around Time represents the time taken to perform maintenance or repair tasks before the system is brought back on-line. | Properties, Criticality & Reliability Editor |
| Weibull - Characteristic Life | For a Weibull distribution, this corresponds to a time value when 63.2% of a batch of items have failed. This value is used in conjunction with duration to change the slope of the Weibull curve, i.e. a higher characteristic life lowers the probability of failure for a given duration of operation. | Properties, Criticality & Reliability Editor |
| Weibull - Slope | The slope of the line in the probability plot. It determines which family of Weibull distributions provide the best fit for the reliability data provided. As one of the defining parameters for a Weibull distribution, it indicates which class of failure is present (infant mortality, random failures, wear out failures). | Properties, Criticality & Reliability Editor |
1.2 Maintenance Data Fields
| MADE Property | Definition | Location in MADE |
|---|---|---|
| Parent Item Number | A field which captures the item number for which maintenance data needs to be imported into the software. | Properties, Advanced Properties |
| Name | The listed identifier or name of the maintenance action defined in the Maintenance Action page. | Maintenance Actions |
| Maintenance Action ID | An identification number for a Maintenance Action. | Maintenance Actions |
| Active? | A designation for Maintenance Action to define whether the Maintenance Action is active and being performed on an item. | Maintenance Actions |
| Description | An entry field allowing the user to give a detailed narrative of the maintenance action. | Maintenance Actions |
| Inspection Interval (hrs) | The regular time interval for maintenance to be conducted, especially for scheduled Maintenance Actions. | Maintenance Actions |
| Location | Location of where maintenance is conducted. This is selected from a drop-down list with the following options: Field, Local Depot, and Remote Depot. | Maintenance Actions |
| Maintenance Interval (hrs) | The regular time interval for maintenance to be conducted, especially for scheduled maintenance actions. | Maintenance Actions |
| Maintenance Type | A combination of the Maintenance Type (e.g. Breakdown, Scheduled) and Sub-Type (e.g. Repair, Replace) used to define the maintenance action. | Maintenance Actions |
| Task ID | An alphanumeric value assigned by the user to a maintenance action task from the Advanced Properties editor. | Maintenance Actions |
| Activity Type | A type of activity which is conducted, either maintenance or inspection. This is only applicable if a Maintenance Action has a Condition-based Maintenance Type. | Maintenance Actions |
| Downtime? | A 'Yes / No' selection stating whether a maintenance task will or will not consider downtime in hours. | Maintenance Actions |
| Duration (hrs) | A numerical value of the length of time for a set of maintenance or inspection tasks. | Maintenance Actions |
| Personnel ID | An identification number for personnel who are performing the Maintenance Actions. | Maintenance Actions |
| Personnel - Quantity | A total number of personnel who are performing the Maintenance Action. | Maintenance Actions |
| Rate | The cost per person per hour attributed to Personnel conducting maintenance or Inspection tasks. | Maintenance Actions |
| Item ID | An alphanumeric value assigned by the user to a spare/item. | Maintenance Actions |
| Items - Quantity | A total number of spares/items for a maintenance action. | Maintenance Actions |
| Unit Cost | The cost of a single spare/item for a maintenance action. | Maintenance Actions |
1.3 FMECA Data Fields
| MADE Property | Definition | Location in MADE |
|---|---|---|
| Parent Item Number | A field that captures information from the Item Number field in the Properties viewer for an Item with children Items. | Properties, Advanced Properties |
| Item Number | A field that captures information from the Item Number field in the Properties viewer. | Properties, Advanced Properties |
| Function | A function is a specific action or a set of actions that a system, subsystem, or component is designed to perform. | Functions editor (Item > Functions) |
| Failure Mode | A failure mode is the specific manner or way in which a failure occurs in a system, subsystem, or component. It describes how the failure manifests itself. | Failure Diagram (Item > Failure Diagram) |
| Failure Cause | A failure cause is the underlying reason or root cause that leads to a failure mode. | Model-based RCM |
| Local Effects | Local effects refer to the immediate consequences of a failure mode on the component or subsystem where the failure occurs. It describes how the failure impacts the specific part of the system. | Model-based RCM |
| Next Effects | Next effects describe the consequences of a failure mode on the next higher level of the system hierarchy. This includes the impact on other connected subsystems or components. | Model-based RCM |
| End Effects | End effects are the ultimate consequences of a failure mode on the entire system. It describes the overall impact on the system's functionality and mission objectives. | Model-based RCM |
| Detection Methods | Detection methods are the techniques and tools used to identify the occurrence of a failure mode. | Control Measures (Item > Failure Diagram > Failure Mode) |
| Compensating Provisions | Compensating provisions are design features, redundancies, or procedural actions that mitigate the effects of a failure mode. They aim to minimize the impact or prevent the failure from occurring. | Control Measures (Item > Failure Diagram > Failure Mode) |
| Prevention Controls | Prevention controls are measures implemented to avoid the occurrence of failure modes. | Control Measures (Item > Failure Diagram > Failure Mode) |
| Substantiation Actions | Substantiation actions are activities performed to verify that the system meets the required reliability and safety standards. | Control Measures (Item > Failure Diagram > Failure Mode) |
| MIL-STD-1629A – Failure Effect Probability | Failure effect probability is the likelihood that a specific failure effect will occur. This is often expressed as a percentage or a probability value. | Failure Diagram (Item > Failure Diagram > Failure Mode > Properties) |
| MIL-STD-1629A – Failure Mode Ratio | Failure mode ratio is the proportion of a particular failure mode in relation to all possible failure modes of a component or system. | Failure Diagram (Item > Failure Diagram > Failure Mode > Properties) |
| MIL-STD-1629A – Failure Rate | Refers to failure mode failure rate. It is expressed in failures per 10^6 hour. | Model-based RCM |
| MIL-STD-1629A – Probability of Occurrence | Probability of occurrence is the likelihood that a specific failure mode will happen during a given period. | Model-based RCM |
| MIL-STD-1629A – Severity Classification | Severity classification is the categorization of failure effects based on the extent of their impact on the system. | Model-based RCM |
| MIL-STD-1629A – Operating Time | The operating time is the duration of operation of the item per mission. | Model-based RCM |
| MIL-STD-1629A – Failure Mode Criticality Number | Failure Mode Criticality Number (Cm) is calculated as Cm = β·α·λ·t where: β = Conditional probability of mission loss; α = Failure mode ratio; λ = Part failure rate; t = Duration of applicable mission phase, usually expressed in hours or number of operating cycles. | Model-based RCM |
| MIL-STD-1629A – Item Criticality Number | Item Criticality Number (Cr) is calculated as Cr = Σ(m=1 to j) Cm, where j = Last failure mode in the item under the criticality classification. | Model-based RCM |
| MIL-STD-882E - Probability | A measure of the likelihood that a specific hazard will occur during the lifecycle of a system, expressed in qualitative or quantitative terms. | Model-based RCM |
| MIL-STD-882E – Probability Level | A predefined qualitative or quantitative scale used to categorize the likelihood of a hazard's occurrence (e.g., frequent, occasional, remote, etc.). | Model-based RCM |
| MIL-STD-882E - Severity | A measure of the potential consequences or impact of a hazard in terms of harm to personnel, damage to property, or effect on mission success. | Model-based RCM |
| MIL-STD-882E – Severity Category | A classification that defines the level of impact a hazard can have, based on the degree of harm to personnel, damage to equipment or property, environmental consequences, or mission degradation. | Model-based RCM |
| MIL-STD-882E – Risk Assessment Code | A combination of the mishap and the probability that the mishap will occur. | Model-based RCM |
| RPN - Occurrence | The overall likelihood or frequency of the entire failure path occurring and resulting in the end effect. | Model-based RCM |
| RPN - Severity | Severity classifications are assigned to provide a qualitative measure of the worst potential consequences resulting from design error or item failure. | Model-based RCM |
| RPN - Detection | Detection is a ranking from very low to very high of the difficulty associated with detecting a failure. The greater the difficulty the higher the value of detection and hence criticality of the failure mode. | Model-based RCM |
| RPN – Risk Priority Number | A numeric assessment of risks assigned to the system. Calculated by multiplying Severity, Occurrence and Detection. | Model-based RCM |
| Narrative | A field that captures information on the system. | Model-based RCM |
| Comment | A field that captures information on data entry to the model. | Model-based RCM |
Note: Refer to Section 1.1 (Model Item / Reliability Data Fields) to import component failure rate.
Source: Local MADE 3.9.1 installation: com.phm.made.help.plugin/documents/help/pdf/Import Configuration User Guide.pdf · retrieved 2026-07-09