The component type of the object type controls the way the object hierarchy can be build. Object types can only be used as child, if the parent object allows its component type as setup in this field. (See tab "component types" on the parent object type). The selected component type in this field determines the relation between a component type and an object type.

When a newly created object (which is a project) should belong to a certain parent project it can be defined here. The newly created object will then be a subproject. This can be convenient for grouped reporting.

In case an object needs to be repaired in-house and you want to keep track of the logistical movement a repair item needs to be setup. The tracking dimension ‘Serial number’ must be active for this item. When creating a workshop repair task (see event code setup) for an object of this type the system will automatically create a negative item line for this repair item. Either the serial number of the object will be used or the system will generate a serial number based on the object number.

Code that identifies the manufacturer. This code will be visible in the object type setup and on the individual objects.

Code that identifies the object category. This code will be visible in the object type setup and on the individual objects.

The (remaining) component types shown here can’t be used in the creation of a structure based on this object type.

The selected components shown here can be linked underneath this object type. Besides these components it is also allowed to add objects underneath this "main object". The allowed object types are derived based on a combination of the allow component types and the relation between the component types and the object types.

The selected components can be linked underneath this object type. Besides these components it is also allowed to add objects underneath this "main object". The allowed object types are derived based on a combination of the allow component types and the relation between the component types and the object types.

The (remaining) component types shown here can’t be used in the creation of a structure based on this object type.

Only applicable when using Dynamics Software Maintenance Management

If a primary meter type is applicable for this object type, it can be selected via the dropdown.

The (remaining) service schedules shown here can’t be linked/activated for this object type.

The selected service schedules can be used in combination with this object type. These service schedule(s) are allowed, but won’t be added automatically. The service schedules can be created from a contract.

The (remaining) diagnostic trees shown here can’t be linked/activated for this object type.

The selected diagnostic trees can be used in combination with this object type. These diagnostic trees are allowed, but won’t be added automatically. The diagnostic tree will be displayed in the repair call, depending on the object type of the selected repair object from the repair call.

Unique identification of a work package, possible to perform on this object type. The event code can be selected from the event code main table.

Parts list for this particular combination of object type and work package. The items which are part of this BOM can be selected on the individual service tasks.

Title to print on the work order in case of using this event code. Setup can be done by language and event code

Average repair time to use for the work package. Used for capacity deduction and scheduling.

Item(s) that will be used for this object type & event code combination. Item(s) will appear on the repair task. Item(s) will be consumed as spare part(s). The selection can be made from the item master table from Microsoft Dynamics 365 for Finance and Operations.

Configuration id of the item. Also based on the configurations defined on the item master from Microsoft Dynamics 365 for Finance and Operations

The item name will be copied from the selected item number.

Quantity to consume for the event.

Unique number of the operation to be performed on this event. They can be selected from the list with allowed operations for this object type.

Description of the operation above. This description will be inherited from the operation setup.

Selects the sub-objects the operation is to be applied on. The sub-objects need to be below the parent object on the repair call for the task the event code is selected on.

Select items for application of trade-agreements and description. Keep in mind revenue does never create any inventory transactions. Items are only used as vehicle for addition functionality.

Description of the item.

For information purposes, partial invoicing and price-calculations a quantity can be used.

Via this drop down you can define the resource type. The resource types can be skills /certificates/ course/ resource/ resource groups/ Capability/ Title. Based on the chosen resource type the requirement drop down will show different values. The setup of these values needs to be done in the Microsoft Dynamics 365 for Finance and Operations HR module.

This level is the most detailed level of defining the required resource requirements.

This dropdown will show a list with available requirements. The content of the list is determined by the chosen resource type.

This is a non-editable field and displays the description of the chosen requirement type.

This check box is related to standard Microsoft Dynamics 365 for Finance and Operations functionality and isn’t required for repair management.

By default this check box is activated. When set this requirement is actively used while scheduling in the graphical scheduling overview. When disabled the requirement stays valid, but isn’t actively checked while scheduling in the repair management module.

This checkbox is only set by the system in case it is a system driven requirement based on drag and drop capabilities.

If the chosen resource type is set to ‘skill’ you can determine the level of skill that is required. During scheduling the system will see this level as a minimum, therefore the resource that you are trying to schedule needs to have the same or higher level skill.

Gives you the possibility to switch between simple and advanced (viewing) mode.

The chosen item group will act as a filter for the items shown in the "items with no setup" list

The chosen coverage group will act as a filter for the items shown in the "items with no setup" list

The buyer group will act as a filter for the items shown in the "items with no setup" list

Some fields are only available in the section "Items with setup".

Select item(s) that should be linked to this object type. Multiple items can be linked to the same object type.

The object type to be used

Default catalog value to put into the object

The contract template linked to this object item

Brief description of the operation. This description will also be printed on documentation

The repair schedule related to this type of operation. It is mandatory to link an operation to a repair schedule. When linked to a ‘manual’ repair schedule it will be a generic operation. These generic operations will be presented in the repair task

Component type related to this type of operation. An operation is always linked to a component type. The execution of an operation is also done against a component type. This can be directly on a component or indirectly via a sub-object.

Estimated duration of the operation. When used in preventive maintenance this duration will be added to the total estimated amount of hours of the repair task.

Defines how many times an operation should take place in a defined period. Only used in preventative maintenance.

Definition of the period in combination with the frequency. Only used in preventative maintenance.

Give the volume in comma separated values, related to the volume usage unit. The operation should be performed when this quantity is reached. Be aware that there is no automated volume checking.

Unit of the volume (running hours, miles/km's, copies, etc.).

The return reference value can be ‘Manual’ or ‘Object property’. When ‘Manual’ is chosen the upper and lower limits need to be defined on the repair operation. When ‘Object property’ is chosen the upper and lower limits can be linked to fields of the object property sheets.

The possible options are: Integer, Real, Alphanumeric.

The upper limit as applicable for this operation. This upper limit will be visible on the repair task and the relevant documentation.

The minimum limit as applicable for this operation. This lower limit will be visible on the repair task and the relevant documentation.

The unit of the measured return value.

The part can be used to further identify the part on which the operation is perfumed. This is an optional field and only used in case the components are setup generic and the part is needed to help the resource to determine on which level he/she should perform the operation.

Identifying number for the object property, this sequence determines the sequence on the individual repair objects.

Brief description of the object property.

Select the component type from the list. The list with available components types will be filtered based on the allowed component types defined for the selected object type.

Description of the selected component type.