The table contains the definitions of the fields used in the FMECA table. The accepted values and definitions are provided to assist mapping FMECA files into OnPlan. The only required columns to load preventative maintenance tasks into OnPlan are Component and Task Details. Other columns are provided to document the reasons for included the preventative maintenance task. 


Column NameOther NamesDescriptionAccepted ValuesCharacters Limit
AreaGeographic AreaThe area where the plant is located. Used to geographically group the plant or equipment. Mobile asset may go under a catch all such as 'Surface Equipment'.  If an Area does not exist, it is added to the Area table on upload.Text145
SystemTask System

The major grouping of Components. There is a System table that contains a list of systems. If a System does not exist, it is added to the System table on upload.

Text145
SubsystemTask Subsystem

The sub-grouping of Components. There is a Subsystem table that contains a list of Subsystems. If a Subsystem does not exist, it is added to the Subsystem table on upload.

Text145
Component *Maintainable item
A name for the component or equipment system. The component is used to group preventative tasks. It is a required field. this may be the maintainable item if the maintainable item is a high enough grouping level.
Text
255
Component Code
Functional locationA short code for the component. The Functional Location for the component would be used here. Text50
PositionPositionThe position of the component if multiple exists. e.g. FrontText50
CounterCounterThe number of the component if multiple exist in the same position. e.g. 3Text50
Maintainable ItemSub-component, Sub-maintainable itemA secondary component. For example, if the component is a pump. A sub-component would be an impeller.Text1000
Grouping CategoryOperation GroupStandard selection for grouping within a document is based on Area, System and subsystem. This field is provides an option for a user defined grouping.Text
225
Document GroupingTask GroupingStandard selection for document grouping is based on Frequency, Trade and Plant Status. This field is provided if another document group is required.Text
150
FunctionComponent Function

The Function(s) of the System or Component

Text225
Functional FailureFunctional Failure
The Function Failure(s) of the System or Component
Text
255
Failure ModeModeHow the failure is presented / identified. If Failure Mode does not exist it is automatically added to the table. 
Text45
Failure CauseCauseThe root cause of the failure. If Failure Cause does not exist it is automatically added to the table.
Text
45
Failure EffectEffectThe potential effect of the failure occurring.Text
1000
Failure PatternFailure TypeThe typical failure pattern of the component. Usually conforms to the RCM failure types, wear-out, random, increasing random etc.Text100
P-F IntervalTime from Potential Failure to Functional FailureThe P-F interval is the time or cycles between the initial detection of a potential failure and the time of the actual failure.
A general rule of thumb is that maintenance inspections should be performed between 1/5 and 1/2 of the P-F interval, depending on the criticality of your plant, to ensure that failure are detected before functional failure occurs
Decimal Number-
HiddenHidden FailureDenotes the failure mode is hidden.Y / N
1 / 0
Yes / No
True / False
T / F
-
Task TypeMaintenance TypeThe type of task such as inspection, component change out, overhaul etc. The Task Type is linked to a table. The task type must exist in the table or the value will not be accepted by the upload tool.Text.
Must match a value in the Task Type table.
Unlimited
Task Details *
Task Description
What needs to be done to avoid the failure.
Text5000
Strategy Task
Major TaskDenotes an important stand-alone task such as a major component change-out or overhaul. Strategy Tasks are not included in the output when generating Inspection documents, they instead create a blank work instruction in the task list, denoted with blue PM(ST) badge.
Y / N
1 / 0
Yes / No
True / False
T / F 
-
Statutory Task
Regulatory Task, Safety Task
An important task that must be done due to legislative or safety requirements
Y / N
1 / 0
Yes / No
True / False
T / F
-
GeneratedGenerated Task
Controls if the task will be included in the generated PM Tasks.Y / N
1 / 0
Yes / No
True / False
T / F
-
FrequencyInterval, Task Interval
How often should the task be carried out.
Integer-
Frequency OffsetSequence Offset

Defaults to 0. Can be used to shift a job step to another PM Task without changing the frequency of the task. See Frequency Offset for more details.

Integer-
Unit of MeasureFrequency Type, Interval TypeThe unit of measure of the task frequency. If the unit of measure doesn't exist it will be added to the table. Text
45
Trade TypeQualification, Skill TypeThe type of skill required to perform the task. If the skill type doesn't exist it will be added to the table.TextUnlimited
Plant StatusStatusIndicates the status of the plant or equipment during maintenance. The Plant Status must match a value from the Plant Status table.Text
45
QuantityNumbers requiredThe number of people required to perform the task.Integer-
HoursTimeThe number of hours required to perform the task.Decimal Number-
ZoneZone
Controls the zone assigned to the operations created in the PM Tasks. The Zone must match a value from the Zone table and must be the same for all job steps in the operation.Text100
ConsequenceSeverity
The most likely result of the failure modeInteger, 1-5-
LikelihoodProbability
The probability the consequence will occurInteger, 1-5
-
RiskRisk RatingOverall risk risk of the failure mode. Calculated field based on Consequence multiplied by Likelihood.N/A-
OEM FrequencyOEM Frequency
Task frequency nominated by the OEMDecimal Number-
Image URLsImage URLs
Allows users to upload images through the strategy import process.TextUnlimited
Alternate Frequency 1Alternate Frequency 1
Alternate task frequencyDecimal Number-
Alternate Frequency 2
Alternate Frequency 2

Alternate task frequency
Decimal Number-
Component LifeComponent Life
Average component life
Decimal Number
-
Strategy Type
Strategy Type
The strategy type of the task, e.g. On Condition.Text155
CommentsNotesAny notes on the decisions made for the task.Text1000
External IDExternal ID
Link to external system. To be used for tracking or integrations.Text100


* Required