Product documentation
Repair center - HSO > Setup > Components > Component type
Besides the Repair objects, Dynamics Repair Center also makes use of components. These components can be used for multiple reasons. In general components are used in a repair object structure to define some parts of the structure that aren’t important enough to keep track of financially and logistically, but you still want to know that they are there. When you want to keep track of the financial and logistical data you need to make a repair object since repair objects generate projects in the background. Components don’t create a project in the background and are therefore purely basic information.
Components can be linked underneath repair objects and are always the lowest level in a repair object structure.
Components can also be used for operations since an operation is always related to a combination of a component type, an object type, and a repair schedule.
| Field | Description |
| Component type |
The unique identifier of the component type. |
| Description | Extended description of the component type |
| Parent Object types | |
| Component of |
The selected object types shown here can be linked to this component type. This setup is similar to the setup of component types from the object type form. |
| Remaining object types |
The (remaining) object types shown here can’t be used in the creation of a structure with this component type. |
The button 'Operations' opens the operations form filtered on the selected object type. Information on what Operations are and how they work can be found here. Please note that the drop down fields at the top part of this form are for filtering only. The filter(s) will only be active once the "Lock" field is enabled.
Repair center - HSO > Setup > Meters > Meters
Meters can be created manually or automatically, using auto-create meters function. In this form all the created meters are visible, as well as some information regarding the meters, like the lastest reading. In case the meter is also used as an item in the company, a connection with the item (and serial) number can be made (for information purposes only).
| Field | Description |
| Meters |
| Meter | The unique indentifier of the meter. The meter ID of the component is used on equipment. |
| Description | The description of the meter |
| Details | |
| General | |
| Meter type | The type of meter |
| Item |
| Item number | The related item number if a meter is also defined as an item |
| Serial number | The related serial number if a meter is also defined (as an item) with a specific serial number. |
| Usage | |
| Calculated reading | Usaually meter values are entered via the meter reading. If no meter reading exists but still a value is desired to determine planned maintenance, it is possible to calculate (interpolate) a meter value. |
| Latest reading | |
| Meter reading | Latest actual meter reading |
| Meter reading type | Type of the meter reading |
| Reading date and time | The date and time of the meter reading |
| Description | The description of the meter reading. |
This function is used to register a new meter reading for the selected meter.
| Field | Description |
| Latest reading |
| Transaction time | Date and time of latest reading, this field is editable to correct the date and time if needed. |
| Meter reading | Reading from selected meter, this is only read only. |
| Meter reading type | The meter reading type, this field is editable to correct the type if needed. |
| Description | Description of the meter reading. |
| New reading | |
| Transaction time | Date and time of the new meter reading. The date and time can be entered manually or by pressing the "current date and time" button for registering live readings. |
| Meter reading | New meter reading value |
| Meter reading type | Type of meter reading. |
| Description | Description of meter reading. |
This form shows an overview of all the registered readings for the selected meter.
| Field | Description |
| Meter |
| Meter | The meter ID of the component that is used on an equipment |
| Description | Description of the meter |
| Usage | |
| Calculated reading | The value in case a reading has been calculated. |
| TAB Meter type | |
| Meter type | The meter reading type |
| Description | Description of the meter type. |
| Unit | Unit of measure for the meter readings |
| Number of digits | Number of digits for the meter readings. |
| Decimals | Number of decimals allowed on the meter reading. |
| Counting direction |
Specifies if (follow-up) readings have to go in a certain direction.
|
| Meter timeline |
| Valid from | Date the (component of the) meter was first taken into use |
| Valid until | Date the meter use was ended (for exmaple in case of a meter replacement) |
| Description | Meter description |
| Component connection | Component number related to the meter number |
| Estimated usage | The estimated usage of the meter |
| Number of periods | Quantity of periods used for estimated readings |
| Period | Unit for period used for estimated readings |
| TAB meter readings |
| Show deleted | Incorrect meter readings can be deleted and will not be used in planned maintenance calculations, however with "show deleted", they can be made visible for review. |
| Initial | Indicates that this is the initial meter reading |
| Meter | The meter ID of the component that is used on an equipment. |
| Reading date and time | The date and time of the meter reading. |
| Log | Indicator whether a value is correct or not. In case a meter reading is not in line with the expectation, e.g. a meter reading is lower than the previous one, despite the counting direction being set to "up", this displays a warning signal. |
| Meter reading | The actual value read from the meter. |
| Type |
The type of meter reading.
|
| Description | Description of the meter reading. |
| Created by | The user ID of the user that has entered the reading. |
| Create date and time | The date and time the meter value was entered/created. |
| Correction (Button) | Can be used to correct a registered meter reading. |
| Validate (Button) | Validates the entered value. |
Repair center - HSO > Setup > Meters > Meter types
One of the first things to set up is Meter types. Here the meter types are defined that can be used in measuring the equipment/component usage.
Meters can be set up according to the properties of the different meter types.
| Field | Description |
| Meter type | The type of the meter |
| Description | Description of the meter type. |
| General | |
| Unit | Unit of measure. |
| Number of digits | Number of digits for the meter |
| Decimals | Number of decimals allowed on the meter reading |
| Counting direction |
Specifies if meter readings need to have a logical order.
|
| Validation | |
| Upper limit | Maximum value allowed in a period |
| Number of periods | Number of periods |
| Period | Type of period (e.g. year, month) |
| Compontent type | |
| Compont type | Applicable component type |
Repair center - HSO > Setup > Meters > Meter timeline
To gain insight on the history of the meter itself, the meter timeline can be used. It gives some more detailed information about the meter and additional information can be added by using the description field.
| Field | Description |
| General |
| Meter | The meter ID |
| Description | Description of the meter |
| Component connection | The related component number |
| Expiration | Date the meter use was ended (in case of a meter replacement for example) |
| Effective | Date the meter was taken into use |
| Reading estimates |
| Estimated usage | Estimated usage of the meter |
| Lower limit | The lower limit as applicable for this reading. |
| Upper limit | The upper limit as applicable for this reading |
| Number of periods | Number of periods (used for estimated usage) |
| Period | Period of a reading (e.g. year, month) |
The form also contains buttons to acces the 'Meter', 'Enter meter reading' and 'Meter readings' forms of the specific meter from the selected meter timeline.
Operations are operational, recurring standard actions to be executed (possibly in a repair schedule) for a specific type of components. These actions are presented as a checklist: effectively a detailed work instruction to accompany repair orders. When a task is performed, it can be helpful to be able to have some reference values to check if a specific aspect of the equipment is ok or not. In total 6 operations exist: Check, Measure, Counter readout, Calibrate, Exchange and Operations.
Repair center - HSO > Setup > Operations > Reference Groups
| Field | Description |
| Code | The code for the reference group |
| Name | Description for the reference group |
Repair center - HSO > Setup > Operations > Reference values
The reference values are defined per reference group and their sorting determines which references are OK and which are not. When it is defined on the operation that the reference value is 6, then only 6 and the records below 6 are OK values.
| Field | Description |
| Group | Selection of the Reference group that these reference values are part of/valid for. |
| Check type | Code for the reference value |
| Name | Description of the reference value |
Sorting of the records can be done by using the arrow buttons in the ribbon. As mentioned, the sort order determines which values are OK (and which are not), so making sure that the order of the records is correct is very important.
Repair center - HSO > Setup > Operations > Component parts
Component parts can be used for those parts of a repairable item that aren't relevant as an equipment or component. These parts are typically the generic (replacable) parts of a repairable item, like the powerplug or cable. These parts can be serviced/repaired/replaced, but are never part of an object structure.
While registering operations on a work order task, it can be defined per operation on which part the operation was performed.
| Field | Description |
| Part | The code of the part. This code will be visible on the work order task. |
| Description | Description for the part. |
Repair center - HSO > Setup > Operations > Operations
Operations are recurring standard actions to be executed (possibly in a maintenance schedule) for a specific type of components. These actions are presented as a checklist: effectively a detailed work instruction to accompany the maintenance tasks. In total 6 types of operations exist: Check, Measure, Counter readout, Calibrate, Exchange and Operation.
| Field | Description |
| Operations |
| Operation no. | Unique identifier for an operation. The number will be assigned based on the parameter settings. |
| Type of operation | Selection of the operation type: check, measure, counter readout, calibrate, exchange or operation. |
| Description | Description of the selected operation. The description will also be printed on documentation. |
| Details - Identification | |
| Repair schedule | The repair schedule related to this type of operation. It is mandatory to link an operation to a maintenance schedule. When linked to a "manual" repair schedule, it will be a generic operation. These generic operations will be presented in the task. |
| Object type | The object type related to this type of operation |
| Component type | Component type related to this type of operation. An operation is always linked to a component type. |
| Estimation | |
| Estimated duration |
Estimated duration of the operation (in HH:MM:SS). When used in preventative maintenance this duration will be added to the total estimated number of hours of the task. |
| Frequency | |
| Frequency | Defines how many times an operation should take place in a defined period. |
| Period | Definition of the period. |
| Usage volume |
The operation should be performed when this quantity is reached. Be aware that there is no automatic volume checking. Specify the volume in comma seperated values (related to the selected volume usage unit). |
| Usage volume unit | Unit of the volume (e.g. running hours, km's) |
| Setup - Reference values | Note that the shown fields vary based on operation type |
| Return value |
The return value can be "Manual" or "Object property". When "manual" is chosen, the upper and lower limits need to be defined on the maintenance operation. When "object property" is chosen, the upper and lower limits can be linked to fields of the equipment property sheets. |
| Return value reference | The reference of the value, possible options are: integer, real or alphanumeric. |
| Upper limit | The upper limit as applicable for this operation. This upper limit will be visible on the task and the relevant documentation. |
| Minimum Limit | The minimum limit as applicable for this operation. This minimum limit will be visible on the task and the relevant documentation. |
| Unit | The unit of the measured return value. |
| Part | The (spare) part related to the operation. The part is not integrated into the product master data of Microsoft Dynamics 365 for Finance and Operations. |
Repair center - HSO > Setup > Resources > Region codes
A region code can be specified for a customer. Regions can be set up as geographical locations, but also as holding companies for all subsidiaries for example. Region codes can be used for multiple purposes such as filtering.
Once the region is defined on the customer card, all repair contracts, repair objects and repair calls for this customer inherit the region code.
In all the commen forms of the repair contracts, repair objects and repair calls it is possible to filter on a specific region.
| Field | Description |
| Location code | Unique code for the region. This code will be visible in multiple forms. |
| Description | Description of the location code. |
Repair center - HSO > Setup > Resources > Resource selection setup
The resource selection setup defines (for a variety of combinations) which resource/employee is the best fit for a certain task.
| Field | Description |
| Object route type code |
Relation of the record to the region code selection. Table/Group/All type of setup. |
| Region code | Depending on the selection made in the 'Object route type code" field select either a region code (group), an object (table) or leave it blank (all). |
| Skill type code | Relation of the record to the skill selection. Table/Group/All type of setup. |
| Skill |
Depending on the selection made in the 'Skill type code' field select either a skill (group), an event code (table) or leave it blank (all) |
| Resource | Select the resource (group) which best fits the previous settings. |
Repair center - HSO > Setup > Repair schedule
A Repair schedule defines periodic intervals, in both usage volume and/or time. This can be planned maintenance or expected (average) breakdowns. Per object type details can be defined for estimated usage of time and material, based on the schedules defined here.
If a specific contract or object does not have a counter value setup, only the time interval is used. If a usage volume is defined, the repair schedule is adjusted according to the volume as defined in the contract. This will in turn affect the forecast and planned maintenance.
A Repair schedule is based on a schedule type. There are 3 schedule types: manual, frequency and interval.
Manual types can be used for repairs outside of the normal schedule. A frequency schedule sets a certain number of repairs within a specified period. The interval type sets repair after a predefined usage (running hours, kilometers etc.). When using the interval schedule type the column ‘Usage volume unit’ should also be filled in the upper part of the form, but note that this volume won’t be used in forecasting.
Depending on the contract category a repair schedule can be linked to a repair contract and repair object combination. To be able to select a repair schedule on a contract, the repair schedule needs to be linked to one or more object types.
Operations can also be linked to a repair schedule through this form.
| Field | Description |
| Repair schedule |
ID or code of the repair schedule. |
| Description | Description of the repair schedule |
| Setup - Setup | |
| Usage volume unit | The unit used for the usage volume. this can be i.e. hours, kilometers etc. This is used for information only. |
| Schedule type |
Manual, visit lines define manually operations, to be used outside of the normal scheduled maintenance. |
| Object types | |
| Remaining object types |
The (remaining) object types shown here are not allowed to use this schedule. |
| Selected object types |
The (selected) object types shown here are allowed to use this schedule. This setting only allows the use of a schedule, activating the scheduling is done via the repair contract. |
The operations button can be used for setting up operations connected to the selected service schedule. More information regarding operations can be found here.
The copy service schedules button allows you to copy the selected service/repair schedule to a new or existing repair schedule. When clicking the button a new pane will open where you specify to which Repair schedule the copy is written and which data to include (service schedules, object type repair schedule, operations). It also provides the option to overwrite the (existing) data.
Repair center - HSO > Setup > Repair schedule < Repair schedule selection
| Field | Description |
| Schedule type | Selection of schedule type: Interval or Frequency. The list will only show the records of the selected type. |
| Contract ID | Relation to the Contract. Table/Group/All type of setup. |
| Contract relation | Select the contract relation in accordance to the selection made in the 'Contract ID' field. |
| Object code type | Relation to the object. Table/Group/All type of setup. |
| Object relation | Select the object relation in accordance to the selection made in the 'Object code type' field. |
| Repair schedule | Select the repair schedule applicable for the created combination. |