General Information

Cases/Enablers
OOP Enabling Infrastructure
Appetizer
The Integrability model is a framework for the digital coexistence of computer applications. Based on the e-Estonia developments. Security features of the authentic source are implemented with the X-road security servers.

OOP synonym
Digital Urbanism
Short summary
INTEGRABILITY MODEL– ON THE ROAD TO THE PUBLIC VALUE
The government of the province of Neuquén has more than 20 years of history in relation to technological information and is travelling a path that leads in a sustainable way to generate public value. In this way one of the most difficult gaps to cover is to achieve ”Connected Government". Achieving connected government implies being able to connect and then integrate the multiple "silos" that are generated by different public organisms, satisfying the following needs:

• Ensure the security and privacy of the information by digitally identifying all the actors, both people and systems, covering the wide range of cases ranging from Habeas Data to Open Data
• Share the data from your own Authentic Sources.
• Create participatory (co-create) processes that cross both organisations and the various systems involved.
• Release services openly so that other actors and developers can extend them using any technology. (Releasing the “last mile”)

Finding and implementing sustainable solutions to these needs is the purpose of the
transversal programs of the Integrability Model. Achieving a Connected Government, it is then possible to have an Open Government on the road to the Public Value.
By releasing open and extensible services, public value and open government become sustainable.
• Co-created processes allows to empower and support multiple existing services
• Today, in Neuquen more than 150 WebServices have been published through which data is shared online from Authentic Sources in a secure and confidential way.
• Data sharing from authentic sources simplifies and eliminates processes.
• By connecting to all actors in the community allows you to exchange on-line data achieving the once-only principle.

The approach is 1-Necessity, 2-Solution, 3-Problem, knowing that meeting needs is the challenge and different solutions bring each one its own problems, that is why it is necessary to work with stakeholders in Communities of Practice (CoPs) to be able to define the needs using all the knowledge and casuistic dispersed in people and organisations, then other CoPs of experts contribute solutions aligned with them. The road is not fast but robust and sustainable.

To work together, minimum rules of coexistence are agreed and respected, which allow to do it in parallel and in convergence, avoiding that some block others, demanding each one to do what legally corresponds to him. In this way a model of self-organisation is achieved from the needs, bridging gaps, building bridges, where everyone can develop and innovate supporting the diversity of all types and releasing the "good" innovation.
Focus
Citizens
Business
NGO's
Government
Start date
Scope
Province/State
Country
Argentina
Nature and status of project
Rolled Out
Is the OOP case/enabler mandatory?
Mandatory

ENABLING ASSETS OR COMPONENTS

Political commitment
Integrability Agreements as an Authentic Source and as a Client System

The Agreements of Integrability as an Authentic Source and as a Client System were signed between each organization or organizations that adheres to the integrability model and the governing body (The Secretary of Public Administration) both as provider (Authentic Source) and data consumer. These agreements ensure the MULTILATERAL standardization of data transport between all parties.
--------
Use Licenses and Service Level Agreements

Having signed theIntegrability agreements, the representatives of the agencies participate in the Community of Practice called called "Data Fair", where they present the list of data they need from other actors and with each of them agree the data to be shared, the use that will be given and the level of services required. This is reflected in the use licenses and service level agreements that are then parameterized in the
integration platform. These meetings are facilitated by trained personnel who apply the concept of "sharing on demand" of the anthropologist Peterson
Socio-cultural influence factors
Change management is key for projects of this magnitude. We currently use Dave Snowden's Cynefin framework to navigate the stairs, from Chaos to Complexity to Complicated to the desired Simple model. The three needs of "sharing data", "co-creating processes" and "liberating services" are aligned with these stages.

Participation in Communities of Practice (CoPs) is essential to achieve agreements without imposition. Needs must be clearly defined, for this we use the Job To Be Done (JTBD) approach. The needs are stable and determinant, and from them, the CoPs of "solutions" (legal, technology, thematic) can work and generate alternatives that are easily comparable and selectable.

We use different techniques of gamification to achieve that the change is dominated by the involved people at all times. We are currently working with Stafford Beer techniques "team syntegrity" to get stakeholders to achieve sustainable basic agreements when the conflict of interests is very marked and recurrent.

The good news is that much of what is needed to apply the OnceOnly principle is based on the 1st stage of data sharing.

DATA HANDLING / DATA EXCHANGE

Type of data sharing
Actual data
Confirmation of a status, group/class membership
Data handler
Stakeholder name
Tribunal Superior de Justicia (Poder Judicial)
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Legislatura de Neuquen (Poder Legislativo)
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Ministerio de Salud
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Secretaria de Gestión Púnlica
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Secretaria de la Produccion
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Secretaria de trabajo
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Secretaria Desarrollo social
Stakeholder category
Government
Stakeholder Role
Data provider
Stakeholder name
Direccion Provincial de Vialidad
Stakeholder category
Government
Stakeholder Role
Data consumer
Stakeholder name
Direccion Provincial de Catastro
Stakeholder category
Government
Stakeholder name
Dirección Provincial de Ingresos Publicos
Stakeholder category
Government
Stakeholder name
Direccion Provincial de Rentas
Stakeholder category
Government
Stakeholder name
Direccion Provincial deTurismo
Stakeholder category
Government
Stakeholder name
IADEP (Instituto Autárquico de Desarrollo Productivo)
Stakeholder category
NGO
Stakeholder name
Centro PyME
Stakeholder category
NGO
Stakeholder name
ISSN (Instituto de Seguridad Social de Neuquén)
Stakeholder category
NGO
Stakeholder name
Hospital Castro Rendon
Stakeholder category
NGO
Stakeholder name
Hospital Heller
Stakeholder category
NGO
Stakeholder name
IPVU (Instituto Provicial VIvienda y Urbanismo)
Stakeholder category
NGO
Stakeholder name
Municipalidad Villa la Angostura
Stakeholder category
Government
Stakeholder name
Municipalidad San Martin de los Andes
Stakeholder category
Government
Stakeholder name
Municipalidad de Centenario
Stakeholder category
Government
Stakeholder name
Municipalidad de Alumine
Stakeholder category
Government
Stakeholder name
Municipalidad de Junin de los Andes
Stakeholder category
Government
Architecture
The security protocols established between the different layers (Data, Processes, Services) allow to support the wide range of cases ranging from Habeas Data to Open Data.

- Habeas Data: the citizen involved, receives a message from the data transfer request and can approve or reject it
- The Coordinator through a model MABAC performs authorizations within a certain scope of operation with high prescience.
- When the process layer activates, the access requests are subordinated to it, for example a doctor can access the clinical history of the patient while he is attending but not after the same.
- When accessing as a client system (without processes) the access controls are delegates to the client system.

We exchange all types of data
- Alphanumerics
- GIS

We distinguish different types of cases
- Instantly available - Accessing the Authentic Source Data layer
- Those that require a process - Accessing the Process layer and firing an instance of a process.
- Those that integrate information from multiple sources - Accessing the service layer (unification).
Lessons learned
- The data must be fresh from its own source, it is not right to be excited about having the large database, because Data such as food will rot.
- Instead of breaking organizational silos, they must first interconnect, reinforce their natural competencies and integrate them.
- As in the real urbanism in the digital, the common areas of circulation and transport must be part of the infrastructure, used by all and not developed by each one, thus the security does not have fissures.
- The rules that are defined should clarify the needs, facilitate governance and free up both the technological innovation and the business models to implement it.
- The power model must be balanced avoiding concentration of power with technology. Today technology is monarchical and this model democratizes it.
- Only minimal rules of coexistence should be imposed to allow a harmonious and sustainable development, based on the real needs of the Government to achieve Public Value. This is called Digital Urbanism.