Error Log

 

 

This article aims to outline common error and info messages in Orien. Each section will provide an example of the error or info and an explanation of the message.

Error and Info messages may use value of the data from action performed for better guidance. This article will address each of these variables as {{variable}}. When searching for a specific message, don't include your variables in the search.

If your error isn't present in this Article, contact Orien Support ([e-mail]) for a custom response and update the Article accordingly.

Hierarchy View Import

---

These are the error messages and info message explanations for the Hierarchy View Import.

Error Message	Cause	Resolution
Location {{Location Description}} has parent with non-unique code/description	2+ Parent Locations have the same Description and Code combination	Change the Description or Code of the Parent Locations so they are unique.
Matched {{number of parent locations with same Description}} possible options	2+ Parent Locations have the same Description and Code combination	Change the Description or Code of the Parent Locations so they are unique.

Info Message	Cause	Resolution
Location {{Location Description}} will not have make set, as '{{Provided Make Value}}' does not exist.	The Make value assigned to {{Location Description}} hasn't been created in the Config.	If the Make is a wanted value, add it to the Hierarchy Config -> Make Table. If the {{Provided Make Value}} isn't correct, provide a valid value.
Location {{Location Description}} will not have model set, as '{{Provided Model Value}}' does not exist.	The Model value assigned to {{Location Description}} hasn't been created in the Config.	If the Model is a wanted value, add it to the Hierarchy Config -> Model Table and assign it to the correct Make value. If the {{Provided Make Value}} isn't correct, provide a valid value.
Location {{Location Description}} will not have location category set, as '{{Provided Location Category Value}}' does not exist.	The Location Category value assigned to {{Location Description}} hasn't been created in the Config.	If the Location Category is a wanted value, add it to the Hierarchy Config -> Location Category Table. If the {{Provided Location Category Value}} isn't correct, provide a valid value.
Invalid data: {{number}} floating locations that will not be imported	Imported Locations don't have a root folder/hierarchy defined.	Define a Parent Location/Hierarchy for the wanted Location.
Loop Found with Location {{code}} - {{description}}	The Parent-Child Location relationship links back to itself.	Don't define the parent of a location structure to be one of its children.
Sheet has invalid location export token	A token provided to a location has since been edited or deleted.	Re-export the Hierarchy and use the updated token.
Parent record '{{code}} {{description}}' does not exist	The Parent defined for a location doesn't exist within the structure.	Ensure that the parent's details are wanted and that it's defined before the child's Location.
Multiple parent records found, please ensure parent name and code are unique	2+ Parent Locations have the same Description and Code combination	Change the Description or Code of the Parent Locations so they are unique.
Location {{code}} {{description}} will not have units set, as '{{reading}}' does not exist.	The unit value of {{Reading}} is not a valid unit in the Tactics Config	Ensure that the {{reading}} value is correct. If so, the {{reading}} will need to be added to the Tactics Config -> Units table.
Location {{code}} {{description}} {{field}} is not a number: {{reading}}	{{field}} requires a number value and {{reading}} isn't a number	Ensure that the {{reading}} is a number and that a value like '10' is used and not '$10' or 'ten'.
Location {{code}} {{description}} {{field}} is not a valid date: {{reading}}	{{field}} requires a date and {{reading}} isn't a date	Ensure that the {{read}} is a date in a date format.
Location {{code}} {{description}} has parent with non-unique code/description. Matched {{reading}} possible options	2+ Parent Locations have the same Description and Code combination	Change the Description or Code of the Parent Locations so they are unique.
Sheet has invalid location export token. Location might have been deleted or from another database	A token provided to a location has since been edited or deleted.	Re-export the Hierarchy and use the updated token.

 

Component Hierarchy Import

---

These are the error messages and info message explanations for the Component Hierarchy Import.

Info Message	Cause	Resolution
Invalid Model: {{ model }}. Please make a selection from the dropdown provided.	The {{make}} value assigned to a component hasn't been created in the Config.	If the Make is a wanted value, add it to the Hierarchy Config -> Make Table. If the {{Provided Make Value}} isn't correct, provide a valid value.
Loop Found with Components {{Component}}	The Parent-Child Component relationship links back to itself.	Don't define the parent of a Component structure to be one of its children.
Sheet has invalid structure revision token	A token provided for a revision that has since been edited or deleted.	Re-export and use the updated token.
Multiple parent records found ({{count}}), please ensure parent name and code are unique	2+ Parent Components have the same Description	Ensure that Components are uniquely named. Please note that Code isn't considered for uniqueness.
{{count}} Component(s) with blank description	1 or more components don't have a description but have a token	A Component's description is mandatory and the sheet can't be imported. Ensure that all details of a component (including tokens) are removed if you want to delete a component.
Found non-unique parent names: {{names}}	2+ Parent Components have the same Description	Ensure that Components are uniquely named. Please note that Code isn't considered for uniqueness.
Structure Revision no longer exists	A token is provided for a revision that has since been edited or deleted.	Re-export and use the updated token.
Structure Revision Version has changed since export. Please re-export	A token is provided for a revision that has since been edited or deleted.	Re-export and use the updated token.
Structure Revision Finalised ... Can not import	The Tactics revision has been finalised and therefore can't be updated.	Create a new Tactics Revision and then export again.
Invalid Make: {{ make }}. Please make a selection from the dropdown provided.	The {{make}} value assigned to a component hasn't been created in the Config.	If the Make is a wanted value, add it to the Hierarchy Config -> Make Table. If the {{Provided Make Value}} isn't correct, provide a valid value.

 

Single Sheet Tactics Import

---

These are the error messages and info message explanations for the Tactics Single Sheet Import.

Error Message	Cause	Resolution
{{x}} rows have invalid activity tokens	The Activity Token provided can't be found or it doesn't match the current revision	Please ensure that the tokens haven't been edited and that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
{{x}} rows have invalid component tokens	The Component Token provided can't be found or it doesn't match the current revision	Please ensure that the tokens haven't been edited and that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
{{x}} rows have invalid location tokens	The Location token provided is invalid and isn't for the correct location.	Please ensure that the tokens haven't been edited and that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
{{x}} rows have invalid failure mode tokens	The Failure Mode Token provided can't be found or it doesn't match the current revision	Please ensure that the tokens haven't been edited and that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
{{x}} rows have duplicate labours	The same Labour is allocated to an activity more than once.	Combine the Labour allocations into a single allocation. Ensure that the Work = the total Work since it will be divided by the Personnel Required
{{x}} rows have duplicate materials	The same Material is allocated to an activity more than once.	Combine the Material Allocations and Sum the their Quantities. If you've accidentally allocated it twice, deleted one allocation.
{{x}} rows have duplicate Custom Costs	The same Custom Cost is allocated to an activity more than once.	Combine the Custom Cost Allocations and Sum the their Total Costs If you've accidentally allocated it twice, deleted one allocation.
{{x}} rows have invalid materials	The Material Details provided can't find a match in the Materials Config or the Material details provided aren't unique.	Ensure that you're providing the correct details for your materials and each character is the same as a material in your Material Config. Also ensure that the details provided point to a unique Material record. Description, Part Number, Stock Code, and Plant Code are all used to determine uniqueness.
{{x}} rows have labour assignment which does not have activity	A Labour is allocated to a row where an Activity hasn't been defined.	Ensure that all wanted Activities are defined and that your Labour allocations are on their correct rows.
{{x}} rows have custom cost assignment which does not have activity	A Custom Cost is allocated to a row where an Activity hasn't been defined.	Ensure that all wanted Activities are defined and that your Custom Cost allocations are on their correct rows.
{{x}} rows have invalid labour work	Allocated Labour's Work value needs to be a number	Please ensure that the values provided are only numbers e.g. 10 is valid while "Ten" is not.
{{x}} rows have invalid labour personal required	Allocated Labour's Personnel value needs to be a number	Please ensure that the values provided are only numbers e.g. 10 is valid while "Ten" is not.
{{x}} rows have invalid material quantity	Allocated Material's Quantity value needs to be a number	Please ensure that the values provided are only numbers e.g. 10 is valid while "Ten" is not.
{{x}} rows have invalid custom cost quantity	Allocated Custom Cost's Quantity value needs to be a number	Please ensure that the values provided are only numbers e.g. 10 is valid while "Ten" is not.
{{x}} rows have invalid custom cost total cost	Allocated Custom Cost's Total Cost value needs to be a number	Please ensure that the values provided are only numbers e.g. 10 is valid while $10 and "Ten" are not.
{{x}} rows have invalid failure mode custom fields values	A Failure Mode's Custom Field value doesn't match the defined criteria	This will occur if the Failure Mode Custom Field is a dropdown where only predetermined values are available. The dropdown will be available on all cells of that Custom Field's column.  The predetermined values can be changed in the Custom Field Config, check that these haven't changed while after the asset was developed.
{{x}} rows have invalid activity custom fields values	An Activity's Custom Field value doesn't match the defined criteria	This will occur if the Activity Custom Field is a dropdown where only predetermined values are available. The dropdown will be available on all cells of that Custom Field's column.  The predetermined values can be changed in the Custom Field Config, check that these haven't changed while after the asset was developed.
{{x}} rows have invalid component tactics custom fields values	A Component's Custom Field value doesn't match the defined criteria	This will occur if the Component Custom Field is a dropdown where only predetermined values are available. The dropdown will be available on all cells of that Custom Field's column.  The predetermined values can be changed in the Custom Field Config, check that these haven't changed while after the asset was developed
{{x}} rows have invalid custom cost custom fields values	A Custom Cost's Custom Field value doesn't match the defined criteria	This will occur if the Custom Cost Custom Field is a dropdown where only predetermined values are available. The dropdown will be available on all cells of that Custom Field's column.  The predetermined values can be changed in the Custom Field Config, check that these haven't changed while after the asset was developed
{{x}} rows have invalid linked activities	The Linked Activity defined hasn't been defined or doesn't exist at the Component yet.	Ensure that linked activities are defined before they are assigned as a linked activity.  Also check that the Activity description is matching an existing Activity
{{x}} rows have invalid allocation type for linked activities	An Activity is defined but the Action Type defined isn't a Follow On Action Type	Ensure that Linked Activities are only defined for Preparation and Follow On Action Types as these are the only types where Linked Activities are allowed.
{{x}} rows have component without description	A Component's Description is a mandatory field.	Ensure that all Components have a description.  Descriptions are mandatory while Codes are optional.
Found non-unique parent components: {{ParentComponents}}	A parent component's parent needs to be to be unique for allocating a component beneath	Ensure the parent component details are unique (based on Description and Component) and  the Parent Component is previously defined in a row above.
Parent component with description missing : {{ParentComponent}}	A Parent Component's Description is missing. This is a mandatory field.	Ensure that a Description is defined for both the Parent Component and the Component itself. Component Descriptions are mandatory.
Cannot find parent component with description : {{ParentComponentDescription}}	The Parent Component's details cannot be found as a Component in the Import	Ensure that the Parent Component Description matches a previously defined Component. Use the provided Parent Component Description to identify the issue Description.
Cannot find component with token : {{ComponentToken}}	The Component Token used isn't correct or is from a previous revision	Please ensure that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version. Also ensure that the Tokens haven't been edited.
Structure Revision no longer exists	The Structure Revision Token defined doesn't match	Please ensure that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
Structure Revision Version has changed since export. Please re-export	The Structure Revision Number used doesn't match the token used.	Please ensure that the data in Orien hasn't been changed after you've exported. It's best to re-export the Single Sheet and implement the changes to the new version.
Dominant replacement do not have replacement activity	The Value of 'Is Dominant' is Marked as Y but an activity hasn't been defined. An Activity description is required to create a Component Replacement Activity.	Ensure that the Component Requires a Replacement Activity. If it does, add an activity to the row or move the 'Is Dominant' flag to the correct row.
Parent {{Parent Component}} was not found or processed already	A component has been defined as a child of a Parent that is defined later in the Import Sheet	Ensure that Parent Components are defined as Components before they are referenced as Parents. Users will need to reorder the Imports rows to ensure this.

 

Maintenance Strategy Import

---

These are the error messages and info message explanations for the Maintenance Strategy Import.

Error Message	Cause	Resolution
Maintenance Strategy '{{package}}' will not have unit set as unit '{{unit}}' does not exist	The {{unit}} defined for {{package}} does not exist in this database.	If the {{unit}} is a wanted value, add it to the Tactics Config -> Unit Table. If the {{unit}} isn't correct, provide a valid value.
Maintenance Strategy found with empty description	A Maintenance Strategy's description is a required field for this import.	Add the Maintenance Strategy's description to the Import. The Import doesn't allow deletions.
Maintenance Strategy Package found with empty description	A Maintenance Strategy Package's description is a required field for this import.	Add the Maintenance Strategy Package's description to the Import. The Import doesn't allow deletions.
Maintenance Strategy '{{strategy}}' with package '{{package}}' has invalid numeric value in '{{cell}}'	Only number values are allowed for packages.	Please ensure that Package Cycle Length, Package Hierarchy, and Package Offset values are numbers only.

Tactics Config - Default Beta Point for Mechanism and Cause Import

---

Error Message	Cause	Resolution
A beta value was not set for the record corresponding to mechanism: {{mechanism}}, and cause: {{cause}}. Please set a beta value for this record before reattempting to import the file	Default Beta Values are required when importing.	Ensure that the beta value is used on each row.

Tactics Config - Tactics Wizard

---

Error Message	Cause	Resolution
Adding this follow-up question would cause a loop	The next question will link back to a previous question, creating a loop.	Ensure that a question previously asked in the current branch of questions isn't set as the next follow up question.

Tactics Config - Data Capture Imports

---

Error Message	Cause	Resolution
Description is a required field	Descriptions are a mandatory field for Data Capture Definitions.	Ensure that each Data Capture Definitions have a Description.
No matching capture type for:{{field}}	The Capture type defined isn't available.	A dropdown is provided in the Data Capture Flag Export will all the acceptable Types. Only these are able to be selected e.g. Only shown for Text captures
No matching value type for:{{field}}	The Value type defined isn't available.	Ensure that all Value Types match the values able to be selected from the dropdown e.g. Text
No matching value type for:	The Data Capture Customisation Value Type defined isn't allowed.	Please ensure that each Data Capture Customisation is either: Text, Dropdown, Numeric, or Boolean (Yes/No)

Tactics Config - Symbols

---

Error Message	Cause	Resolution
No symbols available for allocation to these activities	No Symbols have been added to the Tactics Config -> Symbols Table	Add Symbols to the Tactics Config. They can then be selected on activities.

Tactics Config -Labour Imports

---

Error Message	Cause	Resolution
Labour {{ description }} will not have expense element set, as expense element {{ expenseElement }} does not exist	The Expense Element defined cannot be found and will not be allocated to the Labour	Ensure that the Expense Element Description provided matches an existing Expense Element in the Budget Config.  Expense Elements cannot be created through the Labour Config.
Labour {{ description }} will not have labour category set, as labour category {{ labourCategory }} does not exist.	The Labour Category defined cannot be found and will not be allocated to the Labour	Ensure that the Labour Category Description provided matches an existing Labour Category in the Tactics Config.  Labour categories cannot be created through the Labour Config.

Tactics Config - Units Imports

---

Error Message	Cause	Resolution
Please select a unit without a value set for 'Hours per unit (when time based)'	An number for Hours per Unit hasn't been defined. This is a required field for Time-Based Units for Budget Generation	Provide its 'Hour Equivalent' in the wanted column. For example: Calendar Hours = 1 Calendar Days = 24 Calendar Weeks =  168 Calendar Months = 732 (30.5 Days)

Budget Config - Production Imports

Error Message	Cause	Resolution
Production can not be less than 0.	A Production per Year or Production per hour value is defined as 0	Define a positive number to the Production value
Please ensure the unit is defined on the Unit's Sheet	The Unit Description defined does not exist in the Tactics Config's Unit Config.	Ensure that the Unit's Description provided matches a Non-Time-Based Unit in the Units Config.
Cannot assign two productions with the same unit to a location or structure	The selected location already has a allocated Production of the same Non-Time-Based Unit. Only one can be defined at a specific location	Remove the existing allocation if the newer production is the preferred Production Value.  Productions can be allocated at any level of the Hierarchy (Component specific, Location, Fleet Level, Plant Level). A Location will utilise the closest allocated production (looking up the hierarchy). Rather than allocating the production to each location of a fleet, allocate it once to the fleet level and all assets will utilise the production value.

Operational Costs

Error and Info messages seen when importing in the Operational Costs Module.

Info Message	Cause	Resolution
Invalid units	The Unit Description provided on a Location's Operational Cost Import doesn't exist.	Use the Dropdown on each cell in the Unit column to view all the available Units. Ensure that the spelling of each Unit matches the dropdown value and that the export is recent.
Invalid currencies	The Currency Description provided on a Location's Operational Cost Import doesn't exist.	Use the Dropdown on each cell in the Currency column to view all the available Currencies. Ensure that the spelling of each Currency matches the dropdown value and that the export is recent.
Operational cost forecast requires start and end date	When editing Operational Cost Overrides in Orien, a Start Date and End Date for the Override value are Mandatory.	Ensure that all rows in Orien have a Start and End Date value.
Operational cost override requires a non-negative value	Override Costs cannot be a negative number	Ensure that all Override costs provided are positive numbers.

Budget Period and Production Validations

Error and Info messages seen in the Budget Period and Production Modules.

Info Message	Cause	Resolution
No Budget Periods Found	No Descriptions can be found for Budget Periods.	Ensure that each Budget period as a Description. These Descriptions should be unique.
Insufficient available production found for Failure Mode	No Production allocated for the Failure Mode Activity's Interval Unit	Ensure that each Failure Mode Activity assigned as an OPEX Cost and is a Non-Time-Based Interval Unit has a Production assigned to the Component, Parent Component, or Location Structure.
Frequencies need to be set for this activity	A budgeted Failure Mode Activity in the Tactics Module doesn't have a frequency	Ensure that all budgeted Failure Mode Activities have a Frequency and Unit set.  Frequencies need to be a number. 10 is accepted while "Ten" isn't. This should be restricted on the screen and through the import.
Insufficient available production found assigned to {Object}}	A production isn't configured or correctly to the {{object}}	All Non-Time-Based Units need to have a production configured when generating a budget. Please ensure that this is the case by checking in the Production Config.
No interval assigned to replacement	A Component Replacement Activity doesn't have an interval set.	Please ensure that if a Component has a Replacement Activity that an Interval and Interval Unit are assigned.
Replacement activity interval is larger than 500 Years	The Component Replacement Activity's Interval exceeds 500 Years	This is a validation to ensure that reasonable intervals are provided. If the Component's Replacement Activity shouldn't be budgeted, assign it as 'Non Budgeted'
Budgeted activity interval is larger than 500 Years	The Budgeted Activity's Interval exceeds 500 Years	This is a validation to ensure that reasonable intervals are provided. If the Activity shouldn't be budgeted, assign it as 'Non Budgeted'
Operation interval is larger than 500 Years	The Operation's Interval exceeds 500 Years	This is a validation to ensure that reasonable intervals are provided. If the Operation shouldn't be budgeted, assign it as 'Non Budgeted'.
Replacement activity will occur more than 500 time per day	The Replacement Activity's frequency is above a reasonable rate.	Ensure that an Activity's frequency is a reasonable value. If so, ensure that the Hours-Per-Unit in the Unit Config are correct.
Budgeted activity would occur more than 500 time per day	The Budgeted Activity's frequency is above a reasonable rate.	Ensure that an Activity's frequency is a reasonable value. If so, ensure that the Hours-Per-Unit in the Unit Config are correct.
Operation would occur more than 500 time per day	The Operation's frequency is above a reasonable rate.	Ensure that an Operation's frequency is a reasonable value. If so, ensure that the Hours-Per-Unit in the Unit Config are correct.
No production assigned for budgeted activity	There isn't a Production allocated for the Budgeted Activity's Non-Time-Based Unit	Allocate a Production to the Component/Location (or Location/s above) of that Unit.  Otherwise, change the Unit to a Unit with a Production Allocated.
No production assigned for replacement	There isn't a Production allocated for the Replacement Activity's Non-Time-Based Unit	Allocate a Production to the Component/Location (or Location/s above) of that Unit.  Otherwise, change the Unit to a Unit with a Production Allocated.
No production assigned for operation	There isn't a Production allocated for the Operation's Non-Time-Based Unit	Allocate a Production to the Component/Location (or Location/s above) of that Unit.  Otherwise, change the Unit to a Unit with a Production Allocated. If the Operation is using Maintenance Strategies, check that all Applied Maintenance Strategies' Units have a Production.
No interval units assigned to this operation	The Interval Value on the Operation is missing.	Ensure that all Operation's Intervals are populated if you aren't using Maintenance Strategies.
No production assigned for operational costs	There isn't a Production allocated for the Operational Cost's Non-Time-Based Unit	Allocate a Production to the Component/Location (or Location/s above) of that Unit.  Otherwise, change the Unit to a Unit with a Production Allocated.
A Unit must be assigned to the Operational Cost	An Operational Cost doesn't have a Unit assigned.	Please ensure that all Operational Costs have a unit assigned.  Check that the Units haven't been deleted since the allocation of that Operational Cost

Budget Generation Errors and Validations

Error and Info messages seen when importing in the Budget generation Module.

Info Message	Cause	Resolution
Unable to locate any data for the report	The selected Location doesn't have the necessary data for the report.	Ensure that all necessary data for the Report or Table that you're viewing has been generated and exists. Ensure that the generated budget is of the correct state (Finalised vs Active). Ensure that the data types are marked as Opex Cost or Capital Costs if appropriate.
No Activities Found	The selected Report requires Activities to be present but is unable to find them.	Ensure that all necessary data for the Report or Table that you're viewing has been generated and exists. Change the report parameters to the time frame of the generated budget. Ensure that the generated budget is of the correct state (Finalised vs Active). Ensure that the data types are marked as Opex Cost or Capital Costs if appropriate.
No Replacement Found	The selected Report requires Replacement Activities to be present but is unable to find them.	Ensure that all necessary data for the Report or Table that you're viewing has been generated and exists. Change the report parameters to the time frame of the generated budget. Ensure that the generated budget is of the correct state (Finalised vs Active). Ensure that the data types are marked as Opex Cost or Capital Costs if appropriate.
No Production With Assignable Units For Replacement Found	An OPEX Cost Component Replacement's Interval Unit doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No interval assigned to replacement	A OPEX Cost Componen Replacement Activity doesn't have an interval assigned.	Ensure that all replacements have an Interval and an Interval Unit. If the Interval Unit isn't a Time-Based Unit, ensure that a production of that unit is assigned. Production allocations can be found in the Budget Config.
No Production With Assignable Units For Preventative Failure Mode Activity Found	A Preventative Failure Mode Activity's Interval Unit doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Production With Assignable Units For Other Failure Mode Activity Found	An Failure Mode  Activity's Interval Unit doesn't have a Production allocated. This is allocated to a Failure Mode Activity with an Action Type of Other.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Production With Assignable Units For Preparation Failure Mode Activity Found	A Preparation Failure Mode Activity's Interval Unit doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Production With Assignable Units For Followup Failure Mode Activity Found	A Follow Up Failure Mode Activity's Interval Unit doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Production Forecasts Assigned To {{x}}	The shown Component or Location doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Production Data Found For	The shown Component or Location doesn't have a Production allocated.	Ensure that all Non-Time-Based Units used have a Production allocated. Production allocations can be found in the Budget Config.
No Interval Unit Found For Operation	An Operation doesn't have a required Interval Unit.	Cyclic Operations have an Interval + Interval Unit. Strategic Operations use Maintenance Strategies + Maintenance Packages. Ensure that the correct one is used for each Operation and all required fields are filled.
Interval is 0 For	The provided Task (Replacement Activity, Operation, Project Cost etc.)  have an Interval of 0.	Ensure that Intervals are higher than 0. If the Task shouldn't appear in the budget, change its Cost Type to 'Not Budgeted'
No Units Assigned To	A Task  (Replacement Activity, Operational Cost, Project Cost etc.) doesn't have a required Interval Unit.	Ensure that each Task has an appropriate Unit assigned. Units can be Time-Based or Non-Time-Based.  If don't want that task to appear in the budget, simply change its Cost Type to 'not Budgeted'.
No Finalised Structure With Associated Tactics Found	The select Location/Locations don't have finalised Tactics associated to them	Finalised Tactics are required to Sync Tactics to your Packaging Location/Locations and for other functions. Ensure that Tactics are in the correct State (Working or Finalised)
Budgeted Max Years Too Long For The Replacement Activity - Got	The lifespan of the Component exceeds 500 Years.	It is unlikely that a Component has a lifespan more than 500 years. Please ensure that the Interval, Interval Unit, and Production allocations are all correct.
Replacement Activity Occurs More Than 500 Times Per Day - Got	The frequency of Component Replacements occur more than 500 times in a day.	It is unlikely that a Component should be replaced more than 500 times a day.  Please ensure that the Interval, Interval Unit, and Production allocations are all correct.
Production & Replacement Activity Units Don't Match In	A Production allocated to a Component doesn't match that Component's Replacement Activity's Interval Unit	It seems unlikely that a Production is allocated specifically to a component and the Replacement Activity's Interval Unit are different. Ensure that this is the correct configuration. If it's intended and all required productions are assigned, there won't be further issues.
Structure is being revised, please finalise changes first:	The Tactics of this location is currently in a Working State.	Ensure that the Tactics Revision is in its wanted State (Working vs Finalised). While Budget Generations can be run on Working Tactics and Packaging Revisions, it can be a common mistake that revisions aren't finalised.
Location needs In-Service Date Assigned	The current Location doesn't have an In-Service Date assigned.	Ensure that the Location has an In-Service Date. In Service Dates are very useful for establishing a baseline of when the Asset needs to be accounted for in the Budget. If all Components have a Meter Reading Data, and Operations have an Operation Last Performed Date, it isn't required.
A Unit must be assigned to the Replacement Activity	The Component's Replacement Activity doesn't have an Interval Unit assigned.	Ensure that all Component Replacements wanted in the Budget have an Interval and Interval Unit assigned.
A Unit must be assigned to the budgeted activity	A Failure Mode Activity doesn't have an Interval Unit assigned.	Ensure that all Failure Mode Activities wanted in the Budget have an Interval and Interval Unit assigned.
A Unit must be assigned to the Operation Activity	An Operation  doesn't have an Interval Unit assigned.	Ensure that all Cyclic Operations wanted in the Budget have an Interval and Interval Unit assigned. If they are a Strategy Plan Operation, ensure they have a Maintenance Strategy and Package assigned.
No Matching Unit is assigned to this Operation	The Interval Unit assigned to this Operation is invalid.	Ensure that all assigned Interval Units are correct and match the Productions allocated.
No Matching Unit is assigned to this Maintenance Strategy	The Unit assigned to the provided Maintenance Strategy cannot be found.	Ensure that all Units used are appropriate and haven't been removed from the Configuration (Tactics Config -> Units)
No Unit assigned to Maintenance Strategy	The Unit assigned to the provided Maintenance Strategy cannot be found.	Ensure that all Units used are appropriate and haven't been removed from the Configuration (Tactics Config -> Units)
Invalid Maintenance Strategy	The Maintenance Strategy assigned to the Task List cannot be found.	Ensure that all assigned Maintenance Strategies exist and that they haven't been deleted.
Error encountered running validation on Object {{Object}}	There is an issue on the provided {{Object}}.	Ensure that there aren't any deleted values or data corruption.  Contact Orien Support ([e-mail]) if the issue persists.
Budgeted replacement is also budgeted as an activity on a failure mode	The Budgeted Replacement is also used as a Budgeted Failure Mode Activity.	Budgeted Replacement Activities should not be Budgeted also as a Failure Mode Activity as it will duplicate the costs.  Ensure that the activity is budgeted as a Replacement or a Failure Mode Activity. You can allocated either as Non-Budgeted to prevent this happening but retain the frequencies.
Budgeted follow on and preparation activities are linked to other follow on and preparation activities at {{component}}	A Follow On or Preparation Failure Mode' Linked Activity is used in another Follow On or Preparation Activity.	Ensure that Follow On and Preparation Linked Activities aren't used as Activities for other Follow On and Preparation Failure Mode Activites. This is to prevent Linked and Preparation Activities from Looping on themselves.
A Budgeted Preparation Activity is linked to a non-Budgeted activity at the following location {{component}}	A Budgeted Preparation Activity is assigned to another Failure Mode Activity as Non-Budgeted.	Ensure that the Activity is Budgeted or Non-Budgeted throughout all of its instances. This ensures that each time the activity is performed it is either budgeted - since Activities can be allocated to many Failure Mode Activities.
A Budgeted Follow-up Activity is linked to a non-Budgeted activity at the following location	A Budgeted Follow On Activity is assigned to another Failure Mode Activity as Non-Budgeted.	Ensure that the Activity is Budgeted or Non-Budgeted throughout all of its instances. This ensures that each time the activity is accounted for correctly when it's performed- since Activities can be allocated to many Failure Mode Activities.
There are overlapping production forecasts found at the assigned Production: {{object}}	There are multiple Production forecasts for the Production	Ensure that the each Production only has one Forecast created for it. Check the Production forecast details in the Config (Budget Config -> Production) This is likely the cause of a corrupted import. If you are unable to resolve it, contact Orien Support ([e-mail])
Location contains working packaging	The Packaging of this location is currently in a Working State.	Ensure that the Packaging Revision is in its wanted State (Working vs Finalised). While Budget Generations can be run on Working Tactics and Packaging Revisions, ensure that it's in the correct state for your Budget Generation.
SequelizeDatabaseError: The value of "Value" is out of range. It must be >00n and <2n **64n.	There was an error with rounding calculated values and storing it in Orien.	Regenerate the failed location's Budget. If it consistently occurs, please contact Helpdesk.

Escalations

---

Error Message	Cause	Resolution
There can only be one definition for this escalation type	Two escalations cannot exist for the same Type (Labour, Materials, Defined Operational Costs)	If you are creating two escalations of the same type through the import, remove one and only import one. If you are creating a single escalation through Orien's Interface, edit the existing escalation instead.
There can only be one definition for each operational cost	Two escalation values cannot exist for the same Start Date or Operational Cost.	Ensure that each Escalation value is scheduled appropriately and that there aren't any duplicate values set for the same Date.

Total Cost of Ownership (TCO)

---

Error Message	Cause	Resolution
Retain years outside maximum value.  If you wish to see more data please increase Opex date range and regenerate	The Retain Years provided in the TCO tab exceed the Budget Generation.	Reduce the Retain Years to their appropriate amount. If the Retain Years is correct, regenerate the budget to the last of the Retain Year.

Packaging

---

Error Message	Cause	Resolution
Can not synchronize due to unfinalised tactics	All Locations' Tactics need to be finalised for Packaging to be Synced.	Finalise the wanted Locations' Tactics. If there are multiple Locations that need to be finalised, finalise them all.  If there is at least 1 Location with finalised Tactics, the Sync will run.
Only packaging revisions in a working state can be updated	An Import was attempted on a Packaging Revision in a finalised State.	Packaging data can be finalised to prevent editing of it's data. Open a new revision of packaging, export the file again, make the wanted changes, and import again.
Packaging is not in working state - cannot finalise.	The packaging is under an integration process and cannot be finalised.	The current location is in an inbetween state of Working vs Finalised and is currently going through its defined integration steps.  The current progress can be viewed on the Packaging Revision's View Integration Log.

Images

---

Error Message	Cause	Resolution
File must be less than {{maxFileSize}} KB	Image files have a max size to prevent slow load times of images.	Reduce the Image file size. The current image size should have enough detail for detailed diagrams on Locations and Activities.  You may need to reduce the image size outside of Orien.

High Level Tactic Exports

---

Error Message	Cause	Resolution
Unable to find failure mode for {{what}}	'What' is a mandatory field in Orien.	Ensure each Failure Modes have a 'What' value.

Criticality Config

---

Error Message	Cause	Resolution
You must add the probability and severity before you can configure their colours.	Criticality Probability and Severity need be defined before Criticality Colours	Create all the required Criticality Probabilities and Criticality Severity. Once done, the error should disappear and the screen will load.
You need to add criteria before populating the criteria comparison.	Criticality Criteria need be defined before Criticality Comparison	Create all the required Criticality Criteria. Once done, the error should disappear and the screen will load.

Operation Organisation Import

These are the error messages and info message explanations for the Operation Organisation Export from Packaging's Document Screen.

---

Error Message	Cause	Resolution
Error: Activities don't exist anymore on operation	An activity has been deleted from the file OR an activity has been allocated since the Export	Export the Operation Organisation Export and make the changes again.

Global Messages

Global errors and Info Messages.

 

---

Info Message	Cause	Resolution
Too many validation messages to display	There are too many messages to appropriately display on the screen. Many will be displayed but not all.	Not resolution required. Just a message informing you that there are more validation messages than the ones displayed.
No access to communication preferences.	Your user account doesn't have the correct permissions.	If you require access to the communication preferences, please contact Orien Support ([e-mail])
No Document Exports Templates Exist .... Please Contact Administrator	The Database doesn't have any PRT Templates allocated.	Contact Orien Support ([e-mail]) and request a specific template. Otherwise the default Ausenco template can be provided.
Unable to log in. Please contact Orien Helpdesk.	The email address that you are trying to log in with doesn't seem to work.	Contact Orien Support ([e-mail]) with the url that you are trying to access and the email address that you are trying to access with.
Cannot delete folders that contain referenced assemblies	The folder which contains a referenced assembly was attempted to be deleted.	This is a business rule preventing unwanted data loss. Remove the reference/s from the assets beneath the folder and try again.
Cannot delete assemblies that are currently referenced elsewhere	The Assembly is referenced to another location and cannot be deleted.	This is a business rule preventing unwanted data loss. Remove the reference/s from the asset and try again.
Structure is not in working state - cannot finalise.	The tactics structure was attempted to be finalised while it is in a Finalised State.	Please ensure that the Tactics is in it's wanted state (Working / Finalised).
Location not found - perhaps it was deleted?	The Location that you've selected through a link no longer exists.	The asset has been deleted, or your user account doesn't have access to that Database.
API endpoint not found. Please contact helpdesk for assistance.	An API call was made, in Orien or through an API, where the endpoint doesn't exist.	Ensure that the Endpoint details are correct, the API Key being used is correct and hasn't expired, and that you are connecting to the correct Client Data.
The server is taking too long to respond. Please contact helpdesk if the problem persists.	The request is taking too long and may have an error.	Please wait a few minutes and see if there have been any changes. Try the function again. If it still occurs, contact Orien Support ([e-mail])
Permission Denied. Your user is not permitted to perform that operation on this client data.	Your user permissions don't allow you to perform this function.	If you need to perform this function, contact Orien Support ([e-mail]) with the URL of the error and any other details.
The server is temporarily unavailable. Please contact helpdesk if the problem persists.	The server is unavailable.	If it doesn't come online in a few minutes, contact Orien Support ([e-mail]) with the URL you are currently at.
Component cannot be referenced. Please finalise the library component and try again	The Component in the Component Library isn't finalised	Only finalised Components in the Component Library can be referenced. Finalise, and approve if necessary, the Component. Once done, it can be referenced.
Not a Orien import sheet. Invalid header.	The Import file does not match Orien's Import sheets.	Run the export again and fill in the necessary data.  If the attempted import is not styled like an Orien export, it will not be imported.  If you cannot find an appropriate Export Sheet, contact Orien Support ([e-mail])
User does not have import access to this module	Your user permissions don't allow you to perform this function.	If you need to perform this function, contact Orien Support ([e-mail]) with the URL of the error and any other details.
Sorry, this function is not available. It may not supported by your Microsoft account.	Your user permissions don't allow you to perform this function.	Confirm that your email is the correct one. If so, contact Orien Support ([e-mail]) with the URL of the error and any other details.
Sorry, it appears we do not have access to your files. You might need to log out of the application and log back in again.	Your user permissions don't allow you to perform this function.	Confirm that your email is the correct one. If so, contact Orien Support ([e-mail]) with the URL of the error and any other details.
Sorry, this export file is too large to open with Office Online	The export is too large for it to be handled in Office Online.	Please download this file onto your Device and use a Local version of Excel to view/edit it.  Please contact your Company's IT for Microsoft Office assistance.
This action won't work on multiple selections	The values copied doen't match the pasted area. This is likely as some Orien Exports contain a Very Hidden Sheet in Excel. This is required to provide dropdown values in the exports.	Use Excel's Developer tab to access Visual Vasic for Applications (VBA) and delete the sheet. Please note, this will remove all dropdown functionality in the Export.
You can't paste this here because the Copy area and paste area aren't the same size, and try pasting again.	The values copied doen't match the pasted area. This is likely as some Orien Exports contain a Very Hidden Sheet in Excel. This is required to provide dropdown values in the exports.	Use Excel's Developer tab to access Visual Vasic for Applications (VBA) and delete the sheet. Please note, this will remove all dropdown functionality in the Export.
It appears you have reached your Office Online storage quota.	Your Office Online Storage Limit has been reached.	Please contact your Company's IT for Microsoft Office assistance.
There was a problem accessing the Microsoft Graph service. Please try again.	There is an issue with using Microsoft's Graph Service.	Please contact your Company's IT for Microsoft Office assistance.
Non-numeric values found for \"{{field}}\"	The {{field}} requires only numeric details	Ensure that the data is input correctly. Some fields have validations to ensure that only the correct data is used.
Invalid values found for \"{{field}}\"	The {{field}} contains invalid details.	Ensure that the data provided is appropriate to the {{field}} and that it doesn't contain any illegal characters or fomulas.
Invalid tokens found in sheet.	The tokens provided are incorrect.	Ensure that the top 10 rows of any Orien Import aren't edited and other tokens aren't edited as well.  If the issue persists, export that location again and try the import again. If it persists, contact Orien Support ([e-mail])
Server taking too long to respond, action may still be processing.	The action that you have selected is still processing in the background.	Wait a few minutes for any updates. If it's an Import, view the Import tab at the top of Orien for any updates. If it's an Export, view the Generated Documents module. If it's any other action and it hasn't succeeded after a few minutes, contact Orien Support ([e-mail])
The application is currently unavailable. Please try again and contact helpdesk if the problem persists.	Orien cannot be accessed at this time.	Try and connected again in a minute. If the issue persists and it is outside of the Orien maintenance period, contact Orien Support ([e-mail])

Spares Analysis Imports

---

Error Message	Cause	Resolution
Missing tokens in Initialise Process	The Location or Spares Analysis Token is missing	Ensure that all tokens haven't been edited or removed.
No spares analysis at location {{location}}	The {{location}} provided doesn't have Spares Analysis enabled.	If you have access to the Spares Analysis, enable it on that Location.

Tactics Config - Material

Error and Info messages seen when importing in the Tactics Configuration.

Error Message	Cause	Resolution
Found empty cost on row {{x}}, for material {{material}}	The {{material}} is missing it's cost.	Cost is a required field for all Materials. Ensure that it's populated. If the Material doesn't have a cost. give it a cost of 0.
Material {{material}} will not have expense element set as expense element {{field}} does not exist	The provided {{field}} doesn't exist in the Expense Element Config	Ensure that the {{material}}'s Expense Element is spelt correctly and exists in Budget Config's Expense Element Tab.
Many rows have invalid {{field}}	Various rows have invalid {{field}} values	Ensure that the data provided in all {{field}} fields are appropriate to the field. Some fields required specific data types (Numeric, Dates, Dropdown Values).
Many rows have emtpy costs	Various materials don't have a cost assign	Material Costs are a required field in Orien. Ensure that all values are provided. If the Material doesn't have a cost, give it a cost of 0.
Material {{material}} will not have currency set as currency {{currency}} does not exist	The provided {{currency}} doesn't exist.	Ensure that the currency provided is spelt correctly and exists in Budget Config's Currency Tab.

Measurements

Error and Info messages seen when importing in the Measurements Module.

Info Message	Cause	Resolution
{{field}} at {{location}} - {{node}} is not a number: {{reading}}	The {{reading}} for the Component {{node}} is not a number.	Ensure that all Meter reading Values are numbers. The unit of the Meter Reading is its own column called Meter Reading Unit.
{{field}} at  {{location}} - {{node}} is not a valid date: {{reading}}	The Component Last Replace Date for {{node}} is not in the correct Date Format	Ensure that all dates are provided in the correct field and as YYYY-MM-DD.
Meter Reading for {{location}} - {{node}} will not import due to missing token(s)	The Meter Reading Token for {{node}} is missing or invalid	Ensure that tokens are not edited or deleted. Export the Meter Reading Export again and use the tokens provided.  If the issue persists, contact Orien Support ([e-mail])
Meter Reading for {{location}} - {{node}} will not have units set, as '{{reading}}' does not exist	A Meter Reading without a Unit is provided.	Ensure that each Meter Reading and Meter Reading Date is accompanied by a Meter Reading Unit.

Operation Last Performed

Error and Info messages seen when importing Operation Last Performed Details.

Error Message	Cause	Resolution
{{field}} at {{plan}} - {{task}} - {{op}} is not a number: {{reading}}	The field listed is expecting a number value but a different type is provided	Provide a number instead of the value given at {{reading}}
{{field}} at  {{plan}} - {{task}} - {{op}} is not a valid date: {{reading}}	A valid date isn't provided.	Provide a date instead of the value given at {{reading}}
Last Performed for {{plan}} - {{task}} - {{op}} will not import due to missing token(s)	A token has been deleted or edited since exported from Orien	Export a new Operation Last Performed and implement values on the correct tokens.
Records found with no token	A row is provided which doesn't have a correct token allocated.	The Operation Last Performed Import doesn't allow for the creation of Operations or for Operations to have more than one Last Performed Value.  Ensure that Tokens haven't been deleted or edited.

External Hierarchy Alignment

Error and Info messages seen when Merging Locations into the External Hierarchy

Error Message	Cause	Resolution
{{External Hierarchy Location Code}} destination has data.	The target Location in the External Hierarchy contains Tactics, Packaging, Criticality, Project Costs, Shutdowns, Operational Costs, Capital Items or Spares Analysis in the External Hierarchy Location.	Delete that data from the External Hierarchy Location. This could be by either deleting the Tactics/Packaging Revisions or deleting any records from the other listed modules.
'{{Working Area Location Code}}' Code not found on destination	A match cannot be found in the External Hierarchy for the Working Area's {{Working Area Location Code}}.	Change the Working Area Location's Code to a Location that exists in the External Hierarchy. Or Cut the Working Area Location to the External Hierarchy before the alignment process.
Duplicate location code exists in destination tree	There are duplicate Locations with the same Location Code. Location Codes need to be unique.	Change the Working Area Location Codes to be unique and to match the External Hierarchy values.
High Level packaging exists. Packages will be made invalid and will not be migrated across.	There is packaging at a higher level in the hierarchy than where is currently selected for merging.	This is a warning message to let users know that their data is also using in a different Location. This can be a valid process when the hierarchy structures between the Working Area and External Hierarchy aren't identical. Please refrain from Syncing Packaging at that high level packaging until it's been properly aligned. This will remove activity allocations from the moved Locations.
Location with no data will be deleted during the move into process.	The Merge process removes locations from the Working Area if they have no data.	These locations don't need to be moved and will be deleted to simplify the process.