Relay295 is an integration-planning concept for engineers mapping data producers, transformations and downstream contracts.
The problem to solve
A connection diagram can show endpoints while omitting the meaning of the fields that cross between them.
The proposed approach
State the source of truth and transformation rule for each critical field. Document what happens when a dependency is unavailable.
Working with the example
CRM event
The sample records “Validate identifier” as context and “Source” as its state. In a real integration planning process, the source and responsible role should be checked before acting on that state.
Mapping step
The sample records “Normalise currency” as context and “Transform” as its state. In a real integration planning process, the source and responsible role should be checked before acting on that state.
Analytics store
The sample records “Reject duplicates” as context and “Destination” as its state. In a real integration planning process, the source and responsible role should be checked before acting on that state.
This preview shows the product direction. It has no account system, integrations or live record storage.
View example ↗