Uncia
FR / EN Demo

Glossary

IT urbanization

IT urbanization is the French-rooted name for planning how an organization's applications and infrastructure evolve, the way a city is planned: a functional zoning plan and shared rules for every project. English speakers call the same practice enterprise architecture and application landscape rationalization.

Updated

What is IT urbanization?

IT urbanization is a literal translation of the French urbanisation du système d'information. It names a practice English speakers know as enterprise architecture, and more specifically as application landscape rationalization: planning how applications and infrastructure evolve with an overall plan, a division into sectors and shared rules, instead of one project at a time. You will meet the term in French companies and public bodies, in tenders, and in the job title urbaniste.

The French State's common framework for it, published in 2012 by the interministerial IT directorate, gives a one-line definition: to urbanize is to organize the progressive and continuous transformation of the information system.

That document spells out the city metaphor. A city has utility networks, buildings grouped into zones, districts and blocks, the uses citizens make of them, and regulations. An organization has infrastructure, applications, functions and business processes. The framework adds that the parallel has limits.

The vocabulary dates from the late 1990s and early 2000s. A book by Jacques Sassoon titled Urbanisation des systèmes d'information was published by Hermès in 1998, and the French national library catalogs it under enterprise information systems and banking IT. Club Urba-EA, an inter-company association, was created in 2000 by AXA, FNAC, ORESYS, RATP and SUEZ Lyonnaise des Eaux.

What are the four views?

Club Urba-EA's reference model sorts the elements of an organization's systems into four views. The business view models the business world. The functional view describes the functional architecture; the Club calls it an abstract view that provides a structured path from business to applications. The application view describes the software components and data that implement those functions. The technical view describes the infrastructure that runs them in production.

The French State framework has five: it adds a strategy view on top, for missions and objectives, and says infrastructure where the Club says technical. The functional view is the distinctive part.

It describes what the systems must do, independently of the software chosen. Order management is a function; the ERP that performs it today is an application, and it can be replaced without the function moving. Keeping the two apart is what lets you spot two applications doing the same job, or a function nothing covers. That is the question behind most application landscape reviews.

What are zones, districts and blocks in the functional zoning plan?

The central artifact is the plan d'occupation des sols, or POS, a name borrowed from French municipal land-use plans. The State framework uses it for the overall functional map of the estate. Think of it as a capability-style map with strict rules.

The division is hierarchical. A zone is the first level and carries one major business function. The framework classes its zones by nature: operations, support, management and control, shared data, exchanges. A zone breaks down into districts (quartiers), which group blocks that are homogeneous in the information they handle or the business purpose they serve. A block (bloc) is the finest grain: a coherent set of functions and business objects, described as a replaceable, modular unit. The framework mentions a further level, the îlot, as an exceptional subdivision of a block.

The plan is a partition: a function or a business object belongs to one sector only. Each zone has a named business owner responsible for its transformation. Once applications are placed on the plan, you can see the blocks covered by three applications and the ones covered by none.

What rules does urbanization set?

The rules frame every project so that the landscape stays readable afterwards. The State framework prefers the word principles and warns that they are not to be applied dogmatically: the decision stays with the project's governance bodies.

Three of its design principles give the idea. Simplicity and modularity: divide along the agreed nomenclature, with standardized interfaces between blocks. From this the framework derives a concrete rule, that a new application should cover at most one functional block of the plan. Subsidiarity and coherence: share common functions and isolate the special cases that would complicate the general one. Loose coupling: components cooperate without depending tightly on each other, which translates into a single source for each piece of data, pivot exchange formats and standardized interfaces. A governance principle completes the set: introduce solutions progressively.

Other rules concern the portfolio: keep a single directory of applications, including small local ones and those bought as SaaS, and manage their life cycle. The framework borrows from planning law a building permit to create an application and a removal permit to retire one.

A rule is best judged on a case. Two applications that both write the same customer record break the single-source rule, and on migration day nobody knows which one is authoritative.

How does it differ from enterprise architecture and from IT landscape mapping?

IT urbanization and enterprise architecture now describe almost the same practice. Club Urba-EA places the origin of enterprise architecture in the United States in the late 1980s, with John Zachman's framework, and writes that it developed in France through urbanization initiatives from the early 2000s. The State document carries both names: its title says urbanization, its subtitle says enterprise architecture. In usage, urbanization stresses functional zoning and rules, while enterprise architecture names the wider discipline, its frameworks and notations such as ArchiMate. The entry on IT architecture covers that side.

IT landscape mapping is a means to both. Architects need maps to describe the current state, draw the target and plan the path between them; the Club lists maps and representations among the deliverables of enterprise architecture. A map of the IT estate can exist without any urbanization effort, for security or operations for instance. Rules, on the other hand, cannot be set for a landscape nobody can describe.

How do you start, and with which tools?

Start with the current state, not the target. You need a directory of applications with an owner for each (application mapping provides it), then a rough first zoning plan drawn with the business. Place the applications on the blocks. Duplicates and gaps show up, and they point to the two or three rules the organization needs first. The State framework works this way: its own plan is refined step by step as projects come along.

A spreadsheet and a drawing tool are enough for a first plan, and they force you to keep it simple. They reach their limit when contributors multiply.

An enterprise architecture tool brings a repository, linked views, a notation and validation workflows. It is what large organizations use, and it needs a team to keep it alive. Open source modeling tools exist as well.

A CMDB describes the application and technical views in operation well, and the functional view poorly.

Source-derived mapping (exports, cloud inventories, flow matrices) quickly gives a verifiable current state for the lower layers. It does not produce the zoning plan: functional division remains work for people.

What Uncia adds, and what it does not do

Uncia does not do the urbanization for you and does not draw a zoning plan. It supplies the current state the work rests on. It reads your sources read-only (clouds, hypervisors, CMDB, firewalls and scanners through connectors; exports such as RVTools, flow matrices and architecture documents as dropped-in files) and reconciles them in a knowledge base, changing nothing. It generates Architecture, Infrastructure and Network maps, from the business domain down to the firewall rule, with a record and sources for each element. Architecture documents are checked against the sources, which shows where the documentation has drifted from them.

Maps export to ArchiMate, draw.io, PNG or SVG so they can go back into your enterprise architecture tool, which Uncia complements and does not stand in for. The knowledge base updates with every collection. What the sources do not say still has to be filled in by a person; when the language model proposes a value, someone decides. See the page on maps generated from your sources.

Sources

Frequently asked questions

Is IT urbanization the same as enterprise architecture?

Nearly. Club Urba-EA writes that enterprise architecture developed in France through urbanization initiatives, and the French State's urbanization framework describes itself as a common enterprise architecture framework. The word urbanization puts the emphasis on functional zoning and rules.

What is a POS in IT urbanization?

POS stands for plan d'occupation des sols, a land-use plan. In IT it is the overall functional map, divided into nested sectors. In the French State framework, zones break down into districts and then blocks, and each function belongs to one sector only.

What is an application landscape?

It is the full set of applications an organization runs, seen together with what each one does and how they connect. Urbanization gives that landscape a structure by placing every application on a functional plan.

Who owns IT urbanization in an organization?

An enterprise architect, or urbaniste in French, runs the practice, but decisions belong to governance. The French State framework assigns each zone of the plan a functional zone owner from the business, in charge of its transformation, and an urbanization correspondent.

Do you need a dedicated tool to start?

Not at first. A directory of applications and a first functional plan fit in a spreadsheet and a drawing tool. An enterprise architecture tool becomes useful as the number of contributors and views grows.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.