{"id":41571,"date":"2026-09-03T18:06:36","date_gmt":"2026-09-03T16:06:36","guid":{"rendered":"https:\/\/www.i3s.es\/blog\/erp-centralizado-o-two-tier-que-modelo-elegir-ante-adquisiciones-filiales-y-segregaciones\/"},"modified":"2026-09-03T18:11:38","modified_gmt":"2026-09-03T16:11:38","slug":"erp-centralizado-o-two-tier-que-modelo-elegir-ante-adquisiciones-filiales-y-segregaciones","status":"publish","type":"post","link":"https:\/\/www.i3s.es\/en\/blog\/erp-centralizado-o-two-tier-que-modelo-elegir-ante-adquisiciones-filiales-y-segregaciones\/","title":{"rendered":"ERP centralizado o Two-Tier. Qu\u00e9 modelo elegir ante adquisiciones, filiales y segregaciones"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Jose Luis<\/p>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/p>

An acquisition, the creation of a new subsidiary, a spin-off, or entry into a new market can change a company’s structure in a very short time. When that happens, one of the decisions that usually comes up quickly is what to do with the systems that need to support that new reality. <\/p>

Should the new company be integrated into the corporate ERP system? Does it make sense to maintain a separate system? How can the parent company ensure control? What about data, reporting, and financial processes? <\/p>

The answer isn’t always the same.<\/p>

For years, many organizations have moved toward highly centralized models, in which the various companies within the group operate on a single ERP system and share processes, data, and governance standards. This approach offers significant advantages in terms of standardization and control. <\/p>

However, when the corporate structure changes frequently, situations arise in which extending that corporate model to each new company may require a complex project that is difficult to align with business timelines.<\/p>

It is precisely in this context that a two-tier ERP<\/strong> strategy makes sense.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

What is a two-tier ERP strategy?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/p>

A two-tier ERP is a model in which the parent company maintains its corporate ERP as the primary system, while certain subsidiaries, companies, or business units use a second ERP that is connected to the first.<\/p>

Headquarters thus retains control over the processes and information that must be managed at the corporate level, while certain entities have greater autonomy to address their own operational needs.<\/p>

The key lies precisely in that combination.<\/p>

Two-Tier does not involve creating technologically isolated subsidiaries or abandoning standardization. Nor does it mean that each company is free to decide how to manage its systems. <\/p>

The goal is to determine what should remain the same for the entire group and what can be handled differently where specific needs exist.<\/p>

For example, an organization may want to centralize certain financial criteria, corporate reporting, or some master data, while at the same time allowing a subsidiary to manage certain operational processes or regulatory requirements locally.<\/p>

The goal is to strike a balance between corporate control, integration, and local autonomy<\/strong>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Centralized ERP vs. Two-Tier: What's the Difference?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

The existence of a two-tier strategy does not mean that a centralized model is no longer relevant.<\/p>

On the contrary.<\/p>

When the various subsidiaries of an organization operate in a similar manner, share processes, and require a high level of standardization, using a single ERP system can offer significant advantages.<\/p>

It enables a more consistent architecture, simplifies certain reporting processes, and maintains a shared view of the information. It also facilitates the implementation of policies and procedures shared across the entire group. <\/p>

The problem arises when we try to apply that same logic to any situation.<\/p>

A newly acquired subsidiary may have different processes. A company located in another country may face specific tax or regulatory requirements. A joint venture may need a degree of independence that a traditional subsidiary does not have. A spun-off business unit may need to quickly establish its own infrastructure. <\/p>

In these cases, the question shouldn’t simply be how to integrate the new entity into the corporate ERP system.<\/p>

The question should be: Which ERP model best addresses that organization’s specific situation and the group’s objectives<\/strong>?<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

When the corporate ERP system can't keep up with the pace of the business<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

Let’s think about an acquisition.<\/p>

The corporate transaction is completed, and from that point on, another, less visible but equally important integration begins: the technological and operational integration.<\/p>

We need to analyze how master data will be managed, how financial information will be integrated, what will happen with purchases, sales, and inventory, how intercompany processes will be handled, and how the new company will be incorporated into corporate reporting.<\/p>

In addition, the acquired company must continue to operate.<\/p>

It cannot suspend its operations until the technology integration is complete.<\/p>

If the only option on the table is to incorporate all of its processes into the central ERP system, we may be facing a major project: harmonizing master data, reviewing existing customizations, integrating systems, redefining organizational structures, migrating data, or adapting processes.<\/p>

In some cases, that will be exactly the right thing to do.<\/p>

In other cases, it may make more sense to maintain a greater degree of autonomy initially, using a Tier 2 ERP system connected to the corporate system.<\/p>

The difference is significant.<\/p>

The debate is no longer \u201cHow do we integrate this company into our ERP?\u201d but rather \u201cWhat do we really need to integrate, and what can continue to be managed independently?\u201d<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Two-Tier ERP in Procurement<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

Acquisitions are one of the areas where this consideration is particularly relevant.<\/p>

An acquired company typically comes with its own history: its systems, its data, its operating model, its processes, and, in many cases, its unique technological features.<\/p>

Integrating everything immediately into the group’s ERP system may require a significant transformation effort.<\/p>

A two-tier ERP strategy allows for another option: implementing an ERP system for the new company that meets its operational needs and connecting it to the parent company for those processes where the group requires integration.<\/p>

Finance, reporting, master data, purchasing, sales, or certain intercompany processes can be part of that integration architecture.<\/p>

In this way, the acquired company can operate in an environment tailored to its situation, while the group maintains the visibility and control it needs.<\/p>

This does not mean that the two-tier model has to be the definitive one.<\/p>

In some organizations, it may be part of a long-term strategy. In others, it may be a step in a gradual process of convergence. <\/p>

The important thing is that the decision align with the business strategy and not simply with the need to automatically replicate the same technological model across all companies.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

New Subsidiaries and International Expansion<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

The same reasoning applies to the creation of a new subsidiary.<\/p>

A company that is just starting to operate in a new market does not always need all the functional complexity of a large organization’s ERP system.<\/p>

In addition, you may have specific legal, tax, or operational requirements that make it difficult to replicate the matrix model exactly.<\/p>

In that scenario, Two-Tier makes it possible to consider a different architecture.<\/p>

The subsidiary can have an ERP system that includes the processes it actually needs while maintaining a connection to the corporate systems.<\/p>

The goal is not to make each branch different.<\/p>

It is to prevent standardization from becoming a barrier when there are valid reasons for maintaining a certain degree of autonomy.<\/p>

For organizations with an active international growth strategy, this aspect is particularly important. If establishing new subsidiaries is a regular part of business development, it may make more sense to define a repeatable model for incorporating them than to treat each new subsidiary as a completely independent project. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Spin-offs and New Independent Companies<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

Segregation poses a different problem.<\/p>

In this case, we are not incorporating an organization, but rather dissolving it.<\/p>

Processes, data, users, assets, accounts, systems, and integrations that were previously part of a single structure must begin to operate independently.<\/p>

And, once again, time is often a critical factor.<\/p>

The new company needs to operate, issue invoices, make purchases, manage its finances, and have access to information to make decisions.<\/p>

A two-tier strategy can provide a separate ERP environment for that new entity while determining what information should continue to be exchanged with the parent organization during the transition period.<\/p>

The technological challenge is to achieve this separation without compromising operational continuity or data integrity.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Centralization and autonomy are not necessarily opposing concepts<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

One of the mistakes made when discussing the two-tier system is to present the decision as a choice between control and autonomy.<\/p>

It doesn’t have to be that way.<\/p>

A subsidiary can have operational autonomy without the parent company losing visibility into its financial information or key performance indicators.<\/p>

The real issue is correctly identifying which processes need to be managed centrally and which can be managed locally.<\/p>

In many organizations, for example, it makes sense to maintain corporate standards for certain master data, financial consolidation, reporting, or common policies.<\/p>

At the same time, there may be business, logistical, or regulatory processes that need to be adapted to the specific circumstances of a particular subsidiary.<\/p>

That allocation cannot be determined in a general way.<\/p>

It depends on the group’s structure, its processes, the level of autonomy it wishes to grant to each entity, and the existing technology architecture.<\/p>

For this reason, a two-tier strategy should always begin with a business analysis rather than with the selection of a technological solution.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Integration is a fundamental part of the Two-Tier model<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

Implementing a second ERP system without properly defining how it will interface with the corporate system simply replaces one problem with another.<\/p>

Integration is one of the core elements of any two-tier strategy.<\/p>

The organization must decide which are the master data sources, which data should be replicated across systems, how often, and which processes need to operate in a coordinated manner.<\/p>

It may be necessary to integrate data on customers, suppliers, or products. This may also include financial information, orders, purchases, inventory, intercompany processes, or reporting. <\/p>

The scope will depend on each scenario.<\/p>

Therefore, before selecting an architecture, it is advisable to answer some seemingly simple but crucial questions: What does the parent company need to know? What information can the subsidiary manage locally? Who is responsible for each piece of data? Which processes must operate in real time, and which ones can exchange information in other ways?<\/p>

Answering these questions correctly is much more important than jumping right into the technology.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

SAP Cloud ERP and GROW as Tier 2<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

Within an SAP environment, one possible strategy is to keep the parent company\u2019s ERP as Tier 1 and deploy SAP Cloud ERP for certain subsidiaries or units as Tier 2.<\/p>

This approach makes it possible to handle the onboarding of new entities using a cloud-based model and standardized processes, while maintaining the necessary integration with the corporate system.<\/p>

GROW with SAP is specifically designed to facilitate the adoption of SAP Cloud ERP through a model based on best practices and a “fit-to-standard” approach.<\/p>

This last concept is especially important.<\/p>

Rather than systematically replicating every existing feature through custom developments, the starting point is to use standard processes and extend only those aspects that truly provide the differentiation the business needs.<\/p>

When applied correctly, this approach can help keep technological complexity in check and facilitate the solution’s future evolution.<\/p>

But once again, technology must come after strategy.<\/p>

Before deciding to use SAP Cloud ERP as a Tier 2 solution, it is important to understand which entities should operate under that model, which processes they need to manage, how they will integrate with headquarters, and what the overall governance model should be.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Centralized ERP or Two-Tier?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

There is no one-size-fits-all answer.<\/p>

An organization with uniform operations and a high need for standardization may find that a centralized model is the most efficient option.<\/p>

Another company, subject to frequent acquisitions, international expansion, spin-offs, or the creation of new companies, may need a more flexible structure.<\/p>

That’s why it’s a good idea to ask yourself a few questions before making a decision.<\/p>

How much time do we have to get the new entity up and running?<\/p>

Are their processes really similar to those of the parent company?<\/p>

How much autonomy do you need?<\/p>

What information should the group monitor?<\/p>

What are some local characteristics?<\/p>

Are we facing an exceptional situation, or will we likely find ourselves in the same situation again in a few months?<\/p>

The last question is especially important.<\/p>

When a company makes acquisitions on a recurring basis, enters new markets, or regularly changes its corporate structure, it may not make sense to design a different solution each time.<\/p>

It may be time to establish an ERP architecture model capable of consistently supporting that growth.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Two-Tier ERP is a business decision, not just a technology decision<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/h2>

The ERP architecture must align with the way an organization wants to operate.<\/p>

For this reason, a two-tier decision should not begin by comparing solutions or analyzing features alone.<\/p>

First, we must understand the corporate structure, the processes, the governance needs, the existing systems, the specific characteristics of each entity, and the group’s future strategy.<\/p>

From there, we can determine what should remain centralized, where it makes sense to grant greater autonomy, and how to bridge the two worlds.<\/p>

At i3s, we work with organizations facing scenarios such as these: corporate integrations, rollouts, new subsidiaries, mergers, or spin-offs. Our experience with both centralized SAP models and two-tier architectures allows us to approach decision-making from a perspective that combines business, processes, and technology. <\/p>

Because the issue isn’t whether to centralize everything or decentralize everything.<\/p>

The key is to have an architecture capable of maintaining control where necessary and providing agility where the business needs it<\/strong>.<\/p>

On September 17, we\u2019ll take a closer look at this very scenario in our webinar \u201cSAP GROW: The Two-Tier Response to Corporate Changes<\/strong>, \u201d<\/strong> where we\u2019ll analyze the main use cases, the differences between centralized and Two-Tier models, the integration architecture, and how to approach an implementation project with SAP Cloud ERP.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tWEBINAR REGISTRATION<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"patricia\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Jose Luis<\/p>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t\t\t\t<\/span>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

SAP FI & S\/4HANA Cloud Consultant | Financial Process Optimization & Regulatory Compliance | SAP Certified Professional in i3s<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tLinkedin<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tContact Us<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

We analyze when it makes sense to maintain a centralized ERP system and when a two-tier strategy can provide greater agility, autonomy, and integration in the face of acquisitions, new subsidiaries, or spin-offs.<\/p>\n","protected":false},"author":3,"featured_media":41555,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"default","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[287],"tags":[465,340,526,539],"class_list":["post-41571","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-i3s-blog-en","tag-cloud-en","tag-erp-en","tag-sap-grow","tag-two-tier"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/posts\/41571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/comments?post=41571"}],"version-history":[{"count":1,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/posts\/41571\/revisions"}],"predecessor-version":[{"id":41572,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/posts\/41571\/revisions\/41572"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/media\/41555"}],"wp:attachment":[{"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/media?parent=41571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/categories?post=41571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.i3s.es\/en\/wp-json\/wp\/v2\/tags?post=41571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}