...

Corrective work orders can be used as an extension for requests. A corrective work order is always created as a result of a request. Corrective work order can not be created without a request. As the word 'corrective' already suggests, something needs to be corrected or fixed. Reasons to use corrective work orders is that corrective work orders can be planned (via a planboard), more than one corrective work order can be created from a single request and costs can be added to the corrective work orders.

In this case, for every request, corrective work orders can be created. Creating corrective work orders can also be depending on the problem type. For some problem types it might be not applicable to create work orders and for other problem types it might be applicable.

...

The Knowledge base is a functionality with which relevant knowledge base items/articles can be created and can be shared with all users in Workplace Management. Knowledge base can be used as a stand-alone functionality or with requests. When a knowledge base item is created from a request, the knowledge base item is then linked to the specific request and also the requests problem type. When choosing this problem type in a next request, the knowledge base item linked to the problem type is also shown, which the service group can consult and will help with handling the request.

Enabling the The Knowledge base is a functionality to document and share relevant information. Knowledge base can be done via the articles can be created to provide information on specific subjects (in general or related to a specific problem type), these articles could then help users with certain (often asked) questions or problems without the need to contact the service desk. These are articles similar to the article you are currently reading.

Enabling the Knowledge base can be done via the ‘Module settings' → ‘Requests: Knowledge base’ → 'Use Knowledge base’ setting.

...

If Workplace Experience is also used, a request can also be created via the Workplace App. More information about Workplace Experience can be found here: Workplace Experience integration: Reservations module activation and information.

1.8.4 Demarcations

Demarcations are used to define who is responsible for the costs and maintenance within the context of a request (via the related problem type). Demarcations can be used on either property level or contract level and the administrator can decide which demarcation role (Tenant, Landlord, etc.) is linked to which contact field (Party 1, Party 2, Property manager, etc.).

For example, demarcations are used on Contract level. If the ‘Landlord’ is responsible for the maintenance, the contact in the ‘Party 1’ field of the contract is taken over to the request as responsible for the maintenance. If the ‘Tenant’ is responsible for the costs, the contact in the ‘Party 2’ field of the contract is taken over to the request as responsible for the costs.

The service group user handling the request, now knows to whom the work order need to be assigned and who will receive the invoice of the executed work.

More information about demarcations see Demarcations.

2. Additional information on this module

...