The technical manager of a private industrial park — forty hectares, twenty-five tenants, five years in operation — takes the call on a Thursday morning. A medium-voltage breaker at the substation has tripped, and two of the industrial units are without power. The first attempt to resolve the incident is to identify which contractor holds the electrical maintenance contract and what number to call. The second is to locate an up-to-date single-line diagram. The third is to clarify whether the breaker falls under the maintenance of the park owner or under the tenant downstream. The incident closes in four hours. The event is not exceptional; it is the normal state of the park at year five.
The shared infrastructure of a private industrial park is a set of services that grew by accretion rather than by design. Medium-voltage substation and main switchboards, potable and firefighting water pumping, sanitation and stormwater separation, street lighting, CCTV and access control, HVAC in shared indoor areas, and, increasingly, electric vehicle chargers and fiber backbones. Each service was procured at a different time with a different installer, documented in a different format, and today lives in a different spreadsheet maintained by a different person. As long as the park counted fewer than two hundred common assets and fewer than ten tenants, that way of operating held. Past a certain threshold, it stops scaling.
Why shared services fragment
The root cause of fragmentation is historical. No private industrial park is born with a unified asset register; it is born with one construction specification per service. Each installer hands over its own documentation in the format of its own firm. Every downstream maintenance contract inherits the original installer's documentation and adds its own layer of work orders. Five years and three contractor swaps later, the same asset lives in two incompatible versions, is updated by two people who do not speak, and holds a geographic location that does not match between the two files. Fragmentation is not neglect; it is the natural outcome of a contractual cycle that does not require data convergence.
The second cause is organizational. Each service reports through its own channel — the park's technical committee, the property owner, the tenant depending on the segment — and each channel uses the information in its own meeting. Cross-service consolidation is not part of any committee's reporting cycle. The data exists; nobody looks at it together.
The threshold at which fragmentation breaks
Fragmented operations hold up while the volume is low and the internal team knows each service by memory. The critical threshold arrives around two hundred common assets or five tenants with defined SLAs, and it shows up in three measurable symptoms. The first is overlap: three contractors coincide on a Thursday with independent preventive orders, none of them coordinates with the others, and access through common gates forces the same safety barrier to be sealed twice on the same day. The second is the loss of traceability under incident: when an element fails, the first half hour is spent determining which service it belongs to and who is responsible for it. The third is the inability to refactor common costs across tenants with any precision; without criticality and service ownership properly coded, the shared fee is spread by rough allocation rules and ends up in dispute.
These three symptoms anticipate the conversation with the park owner when the offer arises to expand the surface or add three tenants. Present operations run in the present state, but twenty-percent growth on a single axis pushes coordination from sustainable to unworkable within months. The cost of keeping the fragmented model does not show up in the maintenance line of the budget. It shows up in the technical manager's hours spent reconciling information between contractors, in disputed common fees returned by tenants, and in delayed commissioning of new services because the master is not ready to absorb them. It is a distributed cost that invoices against no single supplier, and precisely for that reason it goes unnoticed for years.
The common base as a transverse layer
The answer is not a CMMS per service; it is a georeferenced common inventory that sits as a transverse layer beneath every contract. Each asset in the park is recorded once, with its owning service, its contracted counterpart, its criticality, its maintenance window and its topological relation with the rest of the network. The preventive plan is generated against that common inventory, not against each service's spreadsheet, and work orders leave a single queue with cross visibility. A contractor arriving on Thursday sees the orders that two other contractors have open for the same day in the same section of the park. The operator handling the breaker incident knows in seconds that the element belongs to the general substation, that the maintenance contract is the one that corresponds, that the downstream impact is two industrial units and that the committee to notify is technical services.
At Maptainer we work with this operator profile by deploying the common georeferenced inventory module first, on top of the consolidated master; the corrective and preventive modules are activated later, per service and per contractor, without disrupting the existing contractual operation. The transition happens by addition, not by replacement.
What measures the technical manager
The classic conversation between the technical manager of a private industrial park and the property owner focuses on whether each service works. That is a floor, not a differentiator. The conversation that actually assesses management is a different one: how much does the internal team grow every time the park adds a hectare or a tenant. When the common asset register is in place, that growth tends toward zero. When it is not, each increment in the park forces a proportional increase in the internal headcount dedicated to coordination. A manager who can show a flat line under park growth is not defending a tool; they are defending the operating model that will support the next expansion. That is the shift in framing that turns the park's technical function from a cost center that scales with the property into a capability that the property owner can use as a lever when the market opens the door to growth.