Organisation Structure
The following data structure can be defined in the system. Not all customers will use/require all elements of this structure.
Each sales order (works order/job) is linked to these organisation units for filtering and reporting purposes.
|
Element |
Description |
|---|---|
|
Contract |
Defines how the order is controlled from a financial viewpoint. Enables separate pricing by contract. Integral to the visit checking and invoicing process. Each contact is linked to an Organisation. Note: Some customers have a contract for all work for a given client whereas some customers have a contract for different categories of work e.g. reactive, voids, adaptations |
|
Work stream |
Defines the category of work that is being undertaken e.g. Reactive Maintenance, Voids, Cyclical Maintenance, Planned Maintenance, Adaptations Enables a user to break a contract into sub elements. Enables a user to review category of work across all contracts. |
|
Sub work stream |
Used on planning board to split work down into Major or Minor voids or Fire checks etc. |
|
Team |
Used to indicate which part of the organisation is responsible for the order. Teams could be by contract, work categories, end client or a combination. A “Team” might have 4 works teams - Reactive A, Reactive B, Voids A, Adaptations A Each order is managed by a "Team". Each resource is in a team. |
|
Work team |
Used on the diary and planning board to allow work to be viewed / allocated to a smaller group of resources. |