01Modules
The catalogue shows what each module provides, what it requires and which modules must be activated with it. Deactivating a module hides its menus and screens; data, documents and permissions are kept.
- Who sets it
- The authority’s administrator, in the module catalogue.
- Example
- A municipality activates the inventory and the legal register. Maintenance will follow when the technical department is ready.
02The country
The localisation provides the available languages, currency, time zone, public holidays, third-party identifier types, legal procedures and edition templates. The main language and time zone are set at creation.
- Who sets it
- The platform operator, when the authority is created, with the country localisation.
- Example
- A Senegalese demonstration authority works in French and English, in CFA francs, on Dakar time. Its public holidays are installed for the year from the public holidays screen.
03The organisation
Units and sub-units of the organisation chart, roles and accounts, dated delegations. A permission applies to an entity and, optionally, its sub-entities. Pairs of incompatible roles stop the same person from preparing and then validating a file.
- Who sets it
- The authority’s administrator.
- Example
- The asset department creates a validator role, then grants a dated delegation during a leave of absence, with the reference of the delegation document.
04Records and their fields
Asset classes are organised with inheritance. The authority defines their fields, and those of the object types designed for it such as third parties: data type, unit, list of values, entry rules. Each change is checked, then published as a new version.
- Who sets it
- The authority’s administrator.
- Example
- The green spaces department creates a class for street trees, under a parent class, with its own fields.
05Approval workflows
The editor adds intermediate states and assigns at least one role to each transition. A trial run without writing checks the workflow before it is published. Files in progress keep the version they started under, and steps required by regulation stay in place.
- Who sets it
- The authority’s administrator, in the workflow editor.
- Example
- An authority adds a director’s approval state before a record is validated, tries it out, then publishes the new version.
06Formulas
A formula calculates a value from attributes, for example a condition score. It is tested against test cases with their expected result, saved as a draft, then published. Each calculation keeps a record of the data used.
- Who sets it
- Authorised people, in the formula editor.
- Example
- The technical department adjusts the condition score formula for a class of equipment and checks the result against its test cases before publishing it.
07Regulatory settings
Deadlines, thresholds and rates are dated settings. Each version carries its source, effective date and approval. The default value supplied stays in the history, and a file keeps the setting in force when it was created.
- Who sets it
- Authorised people, with approval by a second person.
- Example
- For a regulatory deadline, the authority sets reminders before the due date, follow-ups after it, and carry-over to the next working day.
08Packs
A pack supplies ready-to-install content: asset classes, lists of values, workflows and formulas. It has a version and prerequisite packs. When a pack is updated, a conflicting local customisation is kept and flagged in a report.
- Who sets it
- The authority’s administrator, from the pack catalogue.
- Example
- The “Local authorities” and “Local authority technical services” packs install starter asset classes, which the authority then completes. Their content is still to be validated in workshops with pilot authorities.