Turn connected operating data into role-specific decisions. Operational Intelligence combines workbooks, queries, charts, dashboards, exception views and governed assistance so teams can move from a signal to its source, owner and authorised next action.
Role-specific dashboardsConnected data sourcesException-led workGoverned assistance
Operational measures defined against accountable source recordsRole views aligned to a decision and review cadenceExceptions traced to their source documents and ownersAssisted summaries and suggestions reviewed before authorised action
Actual application interface from the official module documentation; final configuration and scope are confirmed per deployment.
Analysis applicationBusiness dashboard
Actual application interface from the official documentation. View source · CC BY-SA.
01Postings
02Reconciliation
03Accruals
04Review
05Lock period
06Statements
Working coverage
Capability where the transaction and responsibility meet.
Leadership and functional teams that need a shared operating picture without replacing accountable source transactions with an opaque reporting layer.
Data sources and workbooks
Organise approved data, transformation and analysis into reusable working contexts.
Approved database and file sources
Source-table selection
Filter, join and summarise operations
Reusable queries
Workbook organisation
Controlled sharing
Charts and dashboards
Compose measures into role-specific operating views with relevant filters and drill context.
Number, line, bar and table views
Dashboard composition
Shared filters
Dependent filters
Role and topic views
Saved analysis
Financial intelligence
Connect receivable, payable, cash, budget and close signals to their accountable transactions.
Ageing and collections
Payables and due exposure
Cash and bank reconciliation
Budget and cost-centre views
Entity and currency views
Close exceptions
Operational intelligence
Bring demand, supply, stock, production, people and service exceptions into current working views.
Order and fulfilment status
Material availability
Production progress
Attendance and payroll readiness
Pipeline and forecast context
Service-level exposure
Exception control
Make unresolved work visible with evidence, ownership and an explicit next step.
Threshold and rule-based signals
Ageing and due-state views
Source-document links
Assignment and escalation
Resolution state
Recurring-exception analysis
Governed assistance
Reduce review effort while preserving source context and human authority.
Contextual operational enquiry
Document extraction for review
Summary and explanation
Reconciliation suggestion
Draft customer or supplier communication
Human-authorised action path
End-to-end flow
From signal to accountable action
Each view should identify what changed, the records behind it, the responsible role and the route to a verified outcome.
01
Observe
Refresh an agreed measure or exception from approved source records.
Data product02
Trace
Open the records, definitions and filters behind the signal.
Reviewer03
Assign
Confirm the responsible role and action date rather than leaving the signal on a dashboard.
Process owner04
Act
Complete the correction, approval or operational command through the responsible application.
Authorised user05
Verify
Confirm that the expected business state changed and retain unresolved discrepancies.
Control owner
Role views
The same process. Different working context.
Each person sees the queues, measures, records and actions that belong to their responsibility.
01
Executive
Enterprise position
Cash and collectionsDemandSupply exposureClose readiness
02
Finance controller
Financial exceptions
AgeingReconciliationPosting issuesBudget variance
03
Operations leader
Delivery and material
OrdersAvailabilityProductionQuality
04
People leader
Workforce readiness
AttendanceLeavePayrollCapacity
05
Service leader
Customer commitments
PipelineSLA exposureEscalationsRecurring issues
Controls retained in the flow
Approved data sources
Role and row-level access design
Measure definitions and owners
Source lineage
Review and publication lifecycle
AI use-case and human-authority boundary
Configured for the operating model
Data sources
Workbooks and queries
Charts and dashboards
Filters and sharing
Exception rules
Approved assistance use cases
Data access, freshness, row-level restrictions, source performance and AI use-case controls are designed per deployment. Public or embedded dashboards require an explicit disclosure and access decision.
Connected applications
Continue the operating cycle.
Move into the responsibilities that sit immediately before, after or alongside this application.
Swaves ERP solutions may use and extend established open-source business platforms, including the ERPNext and Frappe ecosystem, alongside Swaves configuration, integration and managed services. Capabilities and interface patterns shown here are referenced against current published module documentation. ERPNext and Frappe are trademarks of their respective owner. Swaves does not claim partner certification, endorsement or ownership of upstream products.
Current companies, sites and systemsUsers, roles and approval authorityPriority process and known exceptionsMigration, statutory and integration requirements