Definition of IT urbanisation
IT urbanisation (urbanisation du SI, SI standing for système d’information, information system) refers, in French usage, to the approach that drives the gradual and continuous transformation of an information system according to an overall plan. The methodological guide to information system governance published in 2008 by Amue (Agence de mutualisation des universités et établissements, the French agency for shared services among universities and institutions) defines it as follows: organising, defining and carrying out this transformation, in order to simplify the information system, optimise its value relative to its cost and make it more responsive to changes in strategy.
The term rests on a metaphor. The information system is designed like a city, according to an urban plan that sets a lasting partitioning, independent of technologies. The French administration uses it: the choisirleservicepublic.gouv.fr website describes the job of information systems urban planner, and a document from the Urba-ESR group published by Amue, “L’urbanisation au service de la gouvernance des établissements de l’ESR”, cites a common framework for State IT urbanisation, dated 2012.
Changing one part without undoing the whole: what urbanisation is for
When an information system grows through successive projects, each project can add its own interfaces and copies of data to it. Urbanisation aims to allow one part to be modified or replaced without disrupting the others. According to the Amue guide, urban planning defines rules and a coherent, stable and modular framework, to which stakeholders refer for every investment decision.
The State job profile translates this into activities: the urban planner assesses the relevance of projects against the target architecture and existing systems, and favours the reuse of components.
The urban plan: zones, districts, blocks and rules
- A partitioning, called by analogy a land use plan. It divides the information system into zones, subdivided into districts and then into blocks. In the Amue guide, the districts correspond to the institution’s areas of activity.
- Rules. The partitioning aims to reduce and isolate the interfaces between districts, so that each one evolves independently. The same guide associates a principle of subsidiarity with it: pooling the information and services that guarantee consistency, and leaving room for manoeuvre to local systems.
- A map of the existing landscape, a target and the steps that lead from one to the other.
IT urbanisation, enterprise architecture, IT master plan, API management: not to be confused
Enterprise architecture is the term used in international publications, to which TOGAF belongs. The Urba-ESR group document sees it as a broader activity, which includes all the resources of the enterprise, and makes urbanisation its application within the information system.
The IT master plan is a document, drawn up for a given period. Urbanisation continues from one master plan to the next: the State job profile asks the urban planner to guarantee the integrity of the map in line with the master plan.
API management provides tooling for exposing and controlling application programming interfaces. It can enforce an urban planning rule, such as going through a block’s published interface, without saying which blocks exist or which one is responsible for a given piece of data.
Finally, mapping is an instrument of the approach: it describes, whereas urbanisation sets a partitioning and rules.
Illustration: three applications and a single member file
Take a mutual insurer whose three applications (subscription, benefits management, member relations) each record members’ addresses. A change of address entered in one does not reach the other two, and letters are sent to an out-of-date address.
The urban plan creates, in a master data zone, a “persons” district and a “members” block, solely responsible for this data. The rule laid down fits in one sentence: the other blocks read and modify the address through this block’s interface. The roadmap proceeds in steps: new projects consult the master data first, then the three applications stop, one after the other, recording the address themselves.
Our page on IT architecture presents the views of an urbanised information system and how to draw up this plan, its target and its integration rules.