Lumen
Dashboards and decision support for department heads
Lumen brings scheme, service and finance data into one place, shows it by district and programme, and answers questions in plain language.
What Lumen does
Lumen is the dashboard a secretary actually opens. It pulls from Civis, Fulcrum, Tenure and legacy MIS, shows spend and outcomes down to block level, and flags what changed since the last review.
- One dashboard, every systemCivis, Fulcrum, Tenure and state MIS
- Outcomes down to block levelDistrict, block and ward on a map
- Flagged before the meetingAlerts by email and WhatsApp
- Answers you can checkAsk in plain words, the query shown
- Scheme progress against targetPhysical and financial progress
Modules
7 modules, all working on the same records and answerable by the same assistant. Buy the ones you need and add the rest later.
- KPI dashboardsDepartment, scheme and office scorecards with targets, trends and drill-down.
- Schemes and programmesPhysical and financial progress, utilisation certificates and beneficiary coverage.
- Data pipelinesConnectors to Westra products, state MIS, spreadsheets and APIs, with a governed warehouse.
- Geographic viewsState, district, block and ward maps of coverage, pendency and spend, with drill-down from the total.
- Alerts and anomaliesThreshold and pattern alerts delivered by email and WhatsApp before the review meeting.
- Ask in plain languageQuestions answered from the warehouse through Copilot, with the underlying query shown.
- Scheduled reportsWeekly and monthly packs generated and circulated automatically in PDF and spreadsheet form.
Integrations
The systems and standards Lumen connects to. Each integration runs with the credentials and approvals your organisation already holds.
- Civis
- Fulcrum
- Tenure
- State MIS systems
- PFMS
- Spreadsheets and APIs
Who it is for
Each of these has its own section on the solutions page, with the constraints that shape it.
The rest of the public sector suite
See Lumen on your own material
We will run a demo against your own documents and your own workflow, and set out what a deployment inside your perimeter would involve.