Igoudar

An adaptable ERP

One base, set up for each authority and each country.

One base for all authorities, set up for each one: modules, country, organisation, records, workflows, formulas and settings, without bespoke development.

A common core, with modules that plug into it

All authorities share the same product. What sets them apart is configured, on top of the core.

AssetsInventoryLegal registerCensusRevenueRevenueOccupancies and leasesAuctionsOperationsMaintenanceCondition and inspectionsProgrammingLinear roadsEnergy and lightingField inspectionLogisticsFleetFuelStoresReportingDashboardsConsolidated reportingEach module is activated to suit you and relies on the coreCommon coreUsers and permissionsOrganisation chartThird partiesDocumentsApproval workflowsDeadlinesNotificationsFormulasConfigurable fieldsImportsMapLogCountry localisationLanguages, currency, time zone, procedures, edition templatesPortal and field appThe same records, for the public and for staffAssetsInventoryLegal registerCensusRevenueRevenueOccupancies and leasesAuctionsOperationsMaintenanceCondition and inspectionsProgrammingLinear roadsEnergy and lightingField inspectionLogisticsFleetFuelStoresReportingDashboardsConsolidated reportingEach module is activated to suit you and relies on the coreCommon coreUsers and permissionsOrganisation chartThird partiesDocumentsApproval workflowsDeadlinesNotificationsFormulasConfigurable fieldsImportsMapLogCountry localisationLanguages, currency, time zone,procedures, edition templatesPortal and field appThe same records, for the publicand for staff
The common core holds shared data and rules. Each family’s modules plug into it when the authority activates them. The country localisation provides what varies from one country to another; the portal and the field app work on the same records.

What is configured without development

Eight settings. For each one: who does it, and an example.

Modules

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.

The 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.

The 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.

Records 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.

Approval 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.

Formulas

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.

Regulatory 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.

Packs

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.

Three situations

Built with functions that exist today.

A municipality starts with its register

  1. It activates the inventory and the legal register.

  2. It imports its asset spreadsheet: column mapping, simulation, report.

  3. When the technical department is ready, it activates maintenance: work orders apply to assets already registered.

  4. Later, with the stores, work orders draw their parts from stock. Nothing is re-entered.

An authority in another country

  1. It is created with its country’s localisation.

  2. It works in French and English, in CFA francs with no decimals, on Dakar time.

  3. Its third parties carry the country’s identifiers: NINEA, RCCM, CNI, IBAN. No Arabic field is required.

  4. The local rules of this trial localisation still need to be validated with lawyers from the country.

A department adapts its records and its workflow

  1. It creates an asset class with its fields, checks it, then publishes the version.

  2. It adds an intermediate state to the approval workflow and assigns a role to each transition.

  3. It tries the workflow without writing, then publishes it; files in progress keep their version.

  4. A published formula then calculates the condition score of these assets.

What cannot be configured

Flexibility has limits. Here they are.

What the Igoudar team does

Screens, new modules and new business object types are written in code, by our team. Authorities configure; they do not add code.

What the platform operator does

Creating an authority, choosing its localisation and version, its main language and time zone. A later change goes through the operator and leaves a record.

A new country needs a localisation

It is written as data, without touching the shared code. But it has to be written: identifiers, procedures, edition templates and public holidays must be prepared, then validated with lawyers and officials from the country.

Two people for some settings

Regulatory settings, deterioration curves and several approvals require a second authorised person. This is deliberate, so plan for two people.

What Igoudar does not do

No budget, official accounting, payroll, civil registration or purchase orders. Exchanges with state software depend on agreements, country by country.

See the settings in a demonstration

We configure a field, a workflow or a setting in front of you, on a demonstration authority.

Request a demo