Type at least two characters.
Cameras, traffic, parking, lighting and the environment in a single platform. The city stops guessing and starts deciding on what is actually happening.
Most cities do not suffer from a shortage of technology. They suffer from the fact that every piece of it stands on its own.
The camera system has its own software and its own supplier. Parking has a second one. Public lighting a third. The weather station feeds a fourth interface that nobody looks at. When the mayor has to answer a question touching two of them at once, the answer does not exist — someone would have to assemble it by hand from several systems, and by the time they do, the question is no longer current.
FlexiCity does not replace these systems. It connects them. Existing technology stays in place; above it comes a layer that unifies the data into a single picture of the city — a digital twin that reveals the connections the individual systems cannot show.
A single data platform. Collection and consolidation of data from sensors, cameras and municipal information systems. Heterogeneous sources are normalised into one model, validated and stored so they remain usable years later.
A dispatcher workstation. One interface for every module — map, event list, intervention history. The operator does not switch between applications or remember five passwords.
Automation and alerts. Rules that respond to a defined situation on their own, and notifications that reach the responsible person while they can still act — not in a monthly report.
Overviews for city leadership. Indicators and reports you can decide from, and that hold up when defending a budget or facing a grant audit.
Openness outwards. An API for connecting other municipal systems and for publishing selected data to citizens.
Data travels upwards: from field devices through collection and integration into a shared data platform, above which sits the city's digital twin and then the presentation layer. Security and operations are not a separate layer — they run through the whole solution: identity management, two-factor authentication, encryption in transit and at rest in the database, an audit journal, monitoring, backups, service desk and change control.
The city does not buy a server for the back office. Both the management information system and the data platform are delivered as a SaaS licence — the city receives access to an operated service, and we carry responsibility for keeping it running.
Cloud operation. The solution runs in a public, private or hybrid cloud, or as a containerised deployment. The design covers the choice of cloud and specific services, automatic scaling under load, central logging and monitoring, backups with verified restores, and automated promotion of changes between environments.
Three environments. Production, test and demo — so that nothing is tested on live data and the city has somewhere to demonstrate the system without risk.
A digital twin, not just a dashboard. Above the data layer sits a model of the city in which events from different sources combine into a single picture. That is the difference between a city seeing five separate charts and a city seeing the connection between them.
Bespoke parts stay with the city. Source code developed specifically for the city is handed over under the open EUPL licence, including documentation and build instructions.
Modules are deployed independently. A city starts with what hurts most and adds the rest on the same data layer — without a second integration and without a second control room.
Faster decisions. A question that takes a week to answer today is answered at once — and backed by data rather than impression.
Better safety. Events from cameras, traffic and sensors are evaluated together. A situation that looks unremarkable in one system may, combined with a second signal, warrant an intervention.
Lower operating costs. A lighting fault is handled from a system alert, not from an inspection round. Waste collection follows actual need. Consumption becomes visible before the invoice arrives.
Evidence for EU funds and audits. Measurable indicators and an audit trail are in the system from the start, not assembled before an inspection.
Independence from a single supplier. The platform is technology-neutral — what matters is whether a device can submit data over a documented interface, not who manufactured it. The city is not locked into one brand.
We address security in the design, not after go-live. For municipalities this is now a legal obligation, not a premium extra.
A project for a municipality is not just technology. It is a public-administration information system with everything that entails — and most trouble on such projects does not arise in the code, but from a supplier who did not account for the methodology.
Project management and deliverables follow Slovak Act No. 95/2019 Coll. on information technology in public administration, Decree No. 78/2020 Coll. on standards for public-administration IT, and Decree No. 401/2023 Coll. on project management. Delivery proceeds in stages accepted through separate acceptance protocols — the city pays for what has been delivered and accepted, not for promises.
Documentation is part of the delivery, not an appendix at the end. A detailed solution design covering business, application and cloud architecture; a statement of which parts are managed cloud services and which are our own components; wireframes and user interface design; test scenarios; a description of backup and recovery; functional and load test results; user and technical documentation; training materials for each role.
Testing. Functional and load tests, user acceptance tests with the city’s subject-matter owners, and separate security testing following the OWASP WSTG methodology.
Security under Slovak legislation — Act No. 69/2018 Coll. on cybersecurity and Decree No. 179/2020 Coll. on categorisation and security measures, together with the GDPR and Act No. 18/2018 Coll.
Operations with processes, not just a phone number. A service desk as the single point of contact, a record of every request, incident management, problem management and change management — every change recorded, approved and deployed under control. Regular preventive maintenance, encrypted and tested backups with verified restores.
Source code for bespoke parts is handed to the city under the open EUPL licence — including comments, technical documentation and build instructions. The city is therefore not dependent on us, or on anyone else.
Delivery proceeds in stages under the project management decree. Each stage is accepted through a separate acceptance protocol and invoiced separately — the city pays for what has been delivered and accepted, not for promises.
Phase 1 – Analysis and design: mapping what the city already has, what data it produces and where that data is lost. The output is a solution proposal and an estimate of the benefit — before anything is procured.
Phase 2 – Pilot: deployment of one module on a selected agenda. The city sees the result in operation, not in a presentation.
Phase 3 – Rollout: connecting further modules and existing technologies onto the shared data layer, training, handover of documentation.
Phase 4 – Operation and development: support with an agreed response time, continuous development, and an exit plan guaranteeing the city keeps its data even if it chooses a different supplier.
The city has one partner to negotiate with and one party answerable for the result. Behind that stands a division that makes sense: each part is done by whoever does it every day.
The Institute of Advanced Studies delivers the intellectual part of the solution — analysis, architecture, the data layer, integrations, security and methodology:
The implementation partner supplies and physically installs the field technology — cameras, sensors, poles and mounting structures, digital panels, electrical installations, cable routes, inspections and subsequent equipment servicing. We do not carry out physical installation ourselves; it is done by a partner with comparable deployments in Slovak municipalities behind them.
Municipalities today place requirements on projects of this kind that go well beyond the technology itself. Here is how we meet them.
| Requirement | How we meet it |
|---|---|
| Management information system and shared data platform | Delivered as a SaaS licence, with a data warehouse and integration to the city’s existing subsystems |
| Connecting further smart solutions in the future | New sources connect through connectors and APIs on the same data layer, without a second integration |
| Open standards and data publishing | Application interfaces, data connectors and publication of selected datasets for citizens and higher-level platforms |
| Cloud operation with scaling | Public, private or hybrid cloud; automatic scaling, central logging, monitoring |
| Readiness for artificial intelligence | Data is stored in a form that supports advanced analytical and AI scenarios on a common foundation |
| Project management under legislation | Act No. 95/2019 Coll., Decree No. 78/2020 Coll., Decree No. 401/2023 Coll. on project management |
| Documentation deliverables | Detailed solution design, architectures, wireframes and UX, test scenarios, documentation, training materials |
| Testing | Functional, load and user acceptance tests; security testing under OWASP WSTG |
| Cybersecurity | Act No. 69/2018 Coll. and Decree No. 179/2020 Coll. — system categorisation and mapping of security measures |
| Personal data protection | GDPR and Act No. 18/2018 Coll.; configurable retention, controlled access, DPIA inputs |
| Environments | Production, test and demo |
| Availability and recovery | An agreed availability level, defined recovery times, encrypted and tested backups |
| Operational support | Service desk as the single point of contact, incident, problem and change management, regular preventive maintenance |
| Extended technical warranty | Continuous availability of support throughout the agreed warranty period |
| Property rights to bespoke code | Handover under the open EUPL licence including documentation and build instructions |
| Training and handover | Operator and administrator training, trial operation, acceptance protocol, exit plan |
| Supply and field installation | Implementation partner — cameras, sensors, poles, panels, electrical installations and inspections |
We have taken part in delivering systems for towns and municipalities — Holíč, Dunajská Streda, Dolný Kubín and others. These are not pilot installations built for show: they are solutions municipalities use daily in ordinary operation.
An intelligent city is not created by buying more technology. It is created when what the city already owns finally starts speaking one language.
Next step: a no-obligation consultation and an assessment of which of your city’s systems can be connected first, and what you gain by doing so.
Contact: office@ioas.pro · +421 903 667 654
