Operational systems

What it is

The systems an organisation runs on internally: scheduling, dispatch, case management, asset registers, stock, compliance records and reporting.

They rarely get investment because they are not customer-facing, and they are usually where the operational risk actually sits.

Typical requirements we are asked about

• A shared spreadsheet that several people edit and nobody fully trusts
• A process where the same information is entered into three systems
• A compliance or inspection regime that has to be evidenced with a full record of what happened and when
• Reporting that takes a person two days a month to assemble by hand

What Astri Devs delivers

• A single authoritative record, with the workflow modelled on how the work is actually done
• Role-based access so people see and change what their job requires and no more
• Audit trails covering who changed what and when, which is normally a regulatory requirement as well as a practical one
• Reporting and export built in, rather than bolted on after the first month-end
• Import and migration from whatever is being replaced, including the messy historic data

Typical outputs

• A deployed internal system with user administration
• Migrated historic data, with a written record of what was cleaned and what was excluded
• Operator documentation and training for the team that will use it
• Reporting and extracts in formats the organisation already uses

Engagement approach

Discovery is done with the people doing the work, not only with the people specifying it. Delivery is phased so the first release replaces the most painful part of the process rather than everything at once.