Demarcations are used to define who is responsible for the costs and maintenance within the context of a request (via the related service type). For instance, if a request is linked to a service type "Sewer problems", a demarcation list can be used to specify if the cost for fixing this problem is for the tenant or the landlord for the specific building or contract linked to the request.
It is possible to register and manage a default demarcation list. Within this list, you can determine which role (based on predetermined roles) is responsible for the costs and which role is responsible for the maintenance of certain demarcations.
Description
Demarcation roles
Additional demarcation roles can only be created by an administrator using report FMB-REP-193. By default, the FMB provides two Demarcation roles: Tenant and Landlord. On client level, you can add more demarcation roles if necessary. Depending on the demarcation setting (Per building or per contract) you can determine which Contact field(s) within the building or contract should be used to determine the contact that has this role with the context of the building or contract:
Demarcation per building
If demarcation is done based on buildings , per demarcation role, the contactId field of the building that is used to determine the contact for this role should be set (A selection from alle contactId fields of the object Property is possible). For example, the (baseline) demarcation role Tenant uses the building field fmb-TenantContactId.
Demarcation per contract
Since the default contactId field on a contract (Party one) is always used to set the clients organization in, regardless of whether or not the contract is payable or receivable, two fields need to be set when demarcation is done based on contracts, one contactId field (of the Contract object) needs to be set for payable contracts and one for receivable contracts.
For example, the demarcation role Tenant will be the contact in the Contract.contactId field if the contract is receivable (the client is the tenant) and the Contract.partyContactId field if the contract is payable (the client is the landlord).
Manage the default demarcation list
Via the BasicInfoButtonBar on the StartBoard, the FMB-G064 group (5. Manage demarcation) a default demarcation list can be created and managed. By creating one default demarcation list, it makes is easier to create a demarcation list for each building or contract.
Add demarcations to an object (Building / Contract)
On the building or Contract page a Demarcation tab is available (depending on the setting "Use demarcation"). Via this tab, the object-specific demarcation list can be generated. This is done by selecting the necessary demarcations from the default demarcations list. All fields will be copied from the default, but changes to the default demarcation can be made.
Link a demarcation to a service type
By linking one of the demarcations from the default demarcation list to a service type (Field is visible based on the setting "Use demarcation"), it becomes possible to automatically show the demarcation details for a specific request (for whom are the costs and the maintenance).
Demarcation evaluation in request
The following fields are shown on a request (based on the setting "Use demarcation"):
- Contract with requestor
- Costs for
- Maintenance by
- Contact costs
- Maintenance by Contact
These fields are filled based on the demarcation linked to the service type and the corresponding demarcation of the object Building or Contract. Below the criteria to determine the demarcation is explained :
Demarcation on Building :
The following criteria are used to determine which demarcation should be applied in the request:
- A building must be linked
- A service type must be linked
- A demarcation must be linked to the service type
- A demarcation must be available in the building , that is equal to the demarcation of the service type
The demarcation role linked to the demarcation determines which contact field of the object Property (DemarcationRole.fmb-PropertyObjectFieldId) needs to be evaluated to determine which contact is responsible for the costs and which for the maintenance.
Demarcation on Contract:
The following criteria are used to determine which demarcation should be applied in a request:
- A building must be linked
- A service type must be linked
- A demarcation must be linked to the service type
- A demarcation must be available in the Contract that is equal to the demarcation of the service type
- There must be at least 1 contract where the building is linked to a contract item and the requestor of the request is Party 1 or Party 2.
*If no contracts can be found, de demarcation fields stay empty.
*If 1 contract is found, the demarcation field will be based on that contract.
*If more contracts are found, the first contract is linked to the request by default but the user can select one of the other contracts.
- The field Payment in the contract must be on Payable or Receivable.
The demarcation role linked to the demarcation, determines which contact field of the object Contract (DemarcationRole.fmb-PayableContractObjectFieldId if contract is payable and DemarcationRole.fmb-ReceiveContractObjectFieldId if contract is receivable) needs to be evaluated to determine which contact is responsible for the costs and the maintenance.
Authorizations
The following system groups are relevant for demarcations:
Group | Reference | Comment |
|---|---|---|
| FMB-G064 | Group gives access to the default demarcation lists and object demarcations |
Configuration options
Settings can be found via Admin - Settings - Requests:
Setting | Options | Description | |
|---|---|---|---|
Use demarcation | Empty / Per building / Per contract | Empty: Demarcations are not used. All tabs, fields and default reports are not visible. | |
Demarcation contract category | Drop-down with Contract categories | Empty: All contracts will be evaluated when determining the contracts that apply in the request. |
Data imports
Default imports are available:
- FMB-F-071 Import demarcations
- FMB-F-072 Import demarcation objects