TARGET Services T2 – System Analysis Article Series
Part 1: Strategic & Business Context
Article 4
When I analyse payment infrastructures, I start with context. I skip screens and message fields at first. Instead, I map where T2 in TARGET Services sits and why its neighbours matter. This matches the Certified Professional Requirements Engineer (CPRE) of the International Requirements Engineering Board (IREB) mindset. First, I define scope and interfaces. Then, I derive requirements that fit reality. T2 works with CLM, TIPS, T2S, and ECMS. Therefore, I treat interactions as core analysis objects and avoid rework.
The TARGET Services landscape
TARGET Services consist of four closely connected services:
- T2 for payment settlement and liquidity management
- T2S for securities settlement
- TIPS for instant payments
- ECMS for collateral management
Each service has a clear purpose. However, they depend on each other through liquidity, settlement, and credit processes.
Therefore, I analyse T2 as part of a connected settlement infrastructure, not as an isolated platform.
T2 consists of CLM and RTGS
T2 contains two main components.
CLM manages central liquidity and Main Cash Accounts. It also supports liquidity distribution across TARGET Services.
RTGS settles payments and ancillary system transactions in real time.
This distinction matters because a requirement about liquidity usually belongs to CLM, while a requirement about payment settlement usually belongs to RTGS.
I therefore assign every requirement to the correct T2 responsibility as early as possible.
CLM connects liquidity across TARGET Services
CLM has a central role because participants use it to manage liquidity across T2, T2S, and TIPS.
Liquidity can move between relevant cash accounts so that each service has sufficient funds for settlement. However, these transfers are complete processes. They require instructions, validation, settlement, confirmation, and error handling.
For requirements engineering, I therefore analyse the entire interaction rather than only the outgoing transfer request.
CLM also provides liquidity information across accounts.
A system that moves liquidity must also provide enough transparency to understand where that liquidity is and what happened to it.
T2 and T2S
T2S settles securities in central bank money. Therefore, participants need sufficient liquidity on their T2S cash accounts.
This creates a direct dependency on T2 liquidity management.
From a requirements perspective, I ask three questions:
- Can liquidity reach T2S?
- When does it become available?
- How do the systems report the result?
The answers depend on settlement cycles, operating schedules, and available liquidity.
Therefore, liquidity availability forms part of the securities settlement context.
T2 and TIPS
TIPS processes instant payments continuously.
However, continuous payment settlement does not mean that every related function remains continuously available. Cross-service liquidity transfers can depend on maintenance windows and the availability of other TARGET components.
Therefore, I distinguish between instant payment availability and liquidity-management availability.
A requirement such as “TIPS must be available 24/7” is too broad unless I define which process must remain available.
T2 and ECMS
ECMS manages collateral for Eurosystem credit operations.
Collateral affects the credit available to a participant. ECMS communicates relevant credit-line information to CLM.
This creates an important dependency:
collateral → credit line → available liquidity → settlement capacity.
A change in collateral can therefore affect the liquidity available for payments in T2.
ECMS also connects to T2S because marketable collateral often requires securities settlement. T2S settles the securities movement, and ECMS updates the collateral position after receiving the settlement result.
As a result, one business process can cross several service boundaries.
Shared components and operating schedules
TARGET Services also use common infrastructure for areas such as access, reference data, and operational support.
Therefore, I include shared components whenever they influence the requirement under analysis.
Time also matters. TARGET Services operate with defined schedules, cut-offs, settlement phases, and maintenance windows.
TIPS may continue processing instant payments while some liquidity transfers are unavailable. Other processes must finish before end-of-day activities can continue.
For TARGET Services, operating schedules are part of the business behaviour, not merely technical configuration.
How I derive requirements from the landscape
I use four steps.
First, I define the system boundary. T2 contains CLM and RTGS. T2S, TIPS, and ECMS are separate services.
Second, I identify important business objects such as payments, liquidity transfers, cash accounts, collateral, and credit lines.
Third, I identify the interfaces and responsibilities between the services.
Finally, I capture constraints such as cut-offs, maintenance windows, authorisation rules, and failure behaviour.
This gives me a clear path from business purpose to system interaction and finally to a testable requirement.
Conclusion
T2 provides payment settlement and central liquidity management. However, its behaviour depends heavily on the surrounding TARGET landscape.
T2S connects securities settlement with liquidity. TIPS combines continuous instant payments with controlled liquidity transfers. ECMS connects collateral with credit availability. Shared components and operating schedules add further dependencies.
Therefore, I consider the TARGET landscape the correct starting point for analysing T2 requirements.
Once I understand these boundaries and interactions, I can analyse individual T2 processes with much greater precision.
For more content and documents, consult the European Central Bank’s pages on TARGET Services.