Based in standard F2 and experiences with Danish municipalities, cBrain is working to further develop a new digital production platform for local government called Council-as-a-Service (Caas).
Many local authorities,are looking to reduce costs while improving service quality for residents.
To do this the council needs first to be able to understand the individual needs of residents, and then streamline internal processes and be in control of what needs doing and when.
A challenge many municipalities and councils face are an environment with multiple line of business applications, each with its own data store and user interface.
CaaS offers the council an opportunity to create a shared digital archive where data is available to whoever should be able to see it – whether that’s a council leader, a member of staff, or the resident.
By re-using the Danish F2 model for digital public administration, CaaS ensures that residents, directors and employees can get mobile access to council data using smartphones or tablets.
Residents can start a process online, and stay updated on how the council handles their case. Councils can reduce the number of business applications needed, and simplify their business processes. And employees get more done each day, without having to keep multiple systems in synch.
Council-as-a-Service is a complete production platform for council work. It supports council employees and residents by providing a shared database holding all council data.
The CaaS platform is enabled by two layers: the core Foundation Layer that supports base processes like communication, generic case processing, document and records management; and the extensible Process Layer that supports specialized council processes, self-service and integration with external systems through a set of open APIs.
CaaS allows residents and authorities to work together online, in realtime on shared documents and cases, while reducing the number of internal business systems needed to support the resident.
The general F2 layer supports generic processes including case management, knowledge sharing, collaboration, correspondence management, document and records management.
Based on configuration, related to case types and based on the F2 checklist process case type specific processes can be set up and supported, including support for self-service and integration for other systems based on REST-API's.
All case processing data, generic as well as case type specific, are stored in the F2 database, and all user interaction is based on the Email-alike user interface called the knowledge worker desktop.