MIMs Framework 2025
The minimal interoperability mechanisms (MIMs) enable a minimal but sufficient level of interoperability for data, systems, and services specifically in the context of smart city solutions.
The intended audience for this document are:
Solution providers that wish to make sure their solutions are interoperable with other and allow fluid exchange of data within a Smart Cities and Communities context
Procurers that wish to procure solutions that are future-proof and allow cost-effective intergration within an existing Smart Cities and Communities ICT architecture
The (new & improved) MIMs Framework
This MIM Specification adheres to the new MIMs framework introduced in release 7.0. This new MIM Framework is built on the following principles:
MIMs are developed needs-based only, by building on use cases
We strive to minimise duplicate discussions within separate Working Groups
MIMs should focus on interoperability issues only
We separate foundational MIMs, which address recurring interoperability issues across domains and applications, and application specific MIMs, which address interoperability issues that emerge from specific applications
MIM development is result-driven, producing interoperability solutions, best practices, recommendations and PPIs
All MIMs in this specification apply specifically to cities and communities
Foundational MIMs
The new structure proposes several foundational MIMs that provide the core functionalities needed to have data interoperability within a city's data ecosystem. These MIMs focus on complementary capabilities with a clear separation of concerns. The foundational MIMs can also be considered incrementally for a city’s data journey when building an interoperable local data ecosystem. The relation to the MIMs in specification 6.5 are made clear through the numbering, even though some concepts in specification 6.5, such as Context Information Management, may now span multiple MIMs.
The figure below shows an overview of these MIMs and how they build upon each other. It is important to note that while the foundational MIMs represent subsequent steps in the data journey, and thus may be applicable in sequence (depending on where on this data journey the implementing or procuring party is), the application-specific MIMs are not sequential, and should only be considered when this specific application domain is under scrutiny.
Before any data can be made available in a city's data ecosystem, access to relevant data sources to encompass that ecosystem has to be ensured. All data should be made available via APIs, ideally based on interoperable standards. (MIM0)
Once data is accessible, it should be represented in an interoperable way using standards-based data format so it can be effectively used across an organisation or the wider data ecosystem. (MIM2)
The next step in establishing an interoperable data ecosystem is to ensure that data is discoverable and adequately described (meta-data) to facilitate its reuse by others and that usage terms are clearly defined in an interoperable way. A data ecosystem also requires suitable value flow and trust mechanisms to ensure that providers and consumers in a data ecosystem can exchange data in an interoperable and trusted way. (MIM3)
In order to better extract insights and knowledge from data, data users need a way to interlink data sources in a data ecosystem to express contextual relationships that aid further interpretation. Management of such contextual relationships should be achieved in interoperable ways across different data sources. (MIM1)
When information is transferred, between parts of the data platform or externally, this must be done securely. Furthermore, data processors know what requirements concerning security and interoperability to make of suppliers and systems when evaluating, procuring, developing, operating, and using solutions. (MIM6)
No.
Name
Key concerns
MIM0
Accessing Data
Ensuring that data is accessible across diverse systems of an organisation via interoperable APIs
MIM2
Representing Data
Ensuring data can be more effectively used within an organisation by representing it using standards-based interoperable data formats
MIM1
Interlinking Data
Ensuring that data sources can be inter-related to each other based on their contextual relationships in an interoperable way to enable improved interpretation and exploitation of the data
MIM6
Securing data
Ensuring that data is adequately secured and protected within a data ecosystem (in storage or during transit) in an interoperable way
MIM3
Exchanging Data
Ensuring that data can be effectively discovered by data users across an organisation and stakeholders in a wider data ecosystem, exchanged in interoperable ways to enable data reuse and value creation by others.
Application MIMs
These MIMs address other issues to be solved in order for the local ecosystem to realise its full potential. These MIMs will enhance the functionalities of the data ecosystem by introducing interoperability in application-specific domains. They draw strongly on the foundational MIMs. They address particular application areas of data sharing in which further interoperability issues might exist.
The currently defined application-specific MIMs are as follows:
No.
Name
Key concerns
MIM4
Personal data
To enable individuals to be able to easily manage data about themselves so that it can enable outcomes they want, both for themselves and their community, while not compromising on privacy.
MIM7
Geolocation
MIM7 aims to provide Minimal Interoperability Mechanisms related to geospatial data, to tackle the challenge faced by cities and communities of being able to integrate and transfer data between internal and external IT systems. It also takes into account the fact that spatial assets need to be accessed as linked data by many IT- and IoT-systems, and over a long period of time, and thus the vital role of the use of persistent identifiers.
MIMs structure
Objectives
Capabilities
Requirements
Mechanisms
Interoperability guidance
Conformance and compliance testing
In addition, MIM documentation may include informative content regarding:
Relevance to public policy
Procurement guidelines
Implementation guidelines
For those amongst us, who think in pictures:
MIMs PDCA process cycle
First the Objectives are defined, as a short description of the desired outcome of the implementation of a MIM.
Then the Capabilities are given, as as a short description of the core set of business requirements needed within a MIM to enable the Objectives to be met in a minimal, yet sufficient fashion. Where applicable, we refer to [de-facto] industry and/or available guidelines and reference architectures.
This is followed by a list of the functional and quality Requirements needed to achieve the Capabilities described in a MIM. These should be clear and specific enough to enable 'proper' Conformance & Compliance Testing with suggested Mechanisms for the MIM.
The Mechanisms section describes each of one or more alternate sets of tried, tested and proven technical solutions that can deliver the functional and quality Requirements covered in the MIM. These may be taken from technical specifications and guidelines and/or from emerging, de-facto and/or formal standards documentation .
In Conformance & Compliance Testing we provide a description of how to test conformance to, and compliance with, the MIM. This section supports the delivery implementation team by enabling them to be sure that their implementation conforms to the MIM, industry by enabling them to demonstrate that their products and services comply with the MIMs, and procurement officers by showing how they can check that the proposals they are assessing are MIMs compliant. In public procurement tender processes our members can use the Key [procurement] requirements: a table with suggested/possible Mechanisms alongside the list of the use-case specific and/or societal challenges tailored Requirements.
In our Implementation guidelines we provide a description of methods that realize minimal, yet sufficient, levels of interoperability between the different Mechanisms or individual technical solutions that meet the Requirements covered by one or more MIMs. This may include the identification of PPIs and connectors and guidance as to how these can be used to support integration within a data ecosystem. With these Implementation guidelines , we support our members and partners in [Public] Decision making, by suggesting how to integrate different technical solutions within a city or community and helping product and solution providers to design their offerings to address those different approaches.
License Notice (CC BY-SA 4.0)
This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0).
You are free to:
Share – copy and redistribute the material in any medium or format.
Adapt – remix, transform, and build upon the material for any purpose, even commercially.
Under the following terms:
Attribution – You must give appropriate credit to OASC, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
ShareAlike – If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
For more details, see the full license: https://creativecommons.org/licenses/by-sa/4.0/
Last updated
