Product review
Source records, agreed data scope, product versions and restrictions.
Scope details
Identify the agreed data available in the product, its source records and how they change. Document system versions and limitations.
SORM / product integration
A software adapter for a SORM environment.
Integrate an operator’s product with the selected system. Specifications and supplier interfaces determine the exchange scope.
Discuss the technical scopeExplore the scope01Operator product
02Agreed adapter
03Supplier system
04Test environment
Scope is defined by the specific connection
There is no universal adapter. Define the operator scope, supplier system and acceptance criteria.
Exchange model and format
Identifiers, required fields, events and failures — under the selected supplier’s documentation.
Scope details
Map data to the selected system’s documentation. Agree identifiers, required fields, events, transfer direction and rejection handling.
Software adapter
Data validation, transmission and result logging. Access is configured for the specific scope.
Scope details
Implement the agreed interface, validation, transmission and result recording. Access and operational settings are defined for the specific environment.
Testing and handover
An agreed test environment, responsible parties, documentation and support within the contract.
Scope details
Validate the adapter in an agreed test environment with the responsible parties. Provide technical documentation and support rules within the contract.
Define the work boundaries before development
Software integration is a defined part of the operator project. The data and operations are taken from the agreed specification and interface documentation.
01Source data
02Validation and adapter
03System interface
04Technical confirmation
Workflow schematic · scope agreed for the project
Dependencies
Scope depends on the operator, product, activity category, system supplier and technical specifications. A change in any of them requires reviewing the exchange model.
Responsibilities
Separate the work of the developer, client, equipment supplier and other parties. External approvals and procedures are recorded in the project plan.
Adapter outcome
A technical transmission confirmation is not a finding that all requirements are met. Acceptance criteria for the adapter and the complete system are defined separately.
Adapter acceptance and complete-system acceptance follow separate procedures.
What is needed for the technical review
Without these inputs, only preliminary boundaries can be described. Documentation and access are shared through an agreed process.
- Operator and productApplicable technical-scope description
- Supplier systemAgreed exchange contract
- Technical specificationsSoftware-adapter boundaries
- Test environment and acceptanceTechnical validation record
Data scope and exchange rules
| Source / scope | What we define | Outcome |
|---|---|---|
| Operator and product | Activity category, architecture and versions | Applicable technical-scope description |
| Supplier system | Model, version, interfaces and documentation | Agreed exchange contract |
| Technical specifications | Data, operations and restrictions | Software-adapter boundaries |
| Test environment and acceptance | Test data, owners and scenarios | Technical validation record |
Work against agreed interfaces
Check implementation feasibility before development. External procedures, system readiness and test-environment availability are separate dependencies.
01
Review input documentation
Collect the product description, selected system documentation and technical specifications. Confirm parties and interface availability.
02
Agree the specification
Document the data model, operations, format and validation criteria. Identify work performed by other parties.
03
Develop the adapter
Implement transmission, field validation and result recording. Check duplicate events, invalid records and recovery after failure.
04
Validate and hand over
Perform agreed technical checks and provide documentation. Define change control when the product or system is upgraded.
Questions before starting
Is SORM required for our product?
This is determined for the specific operator and activity category under applicable requirements. We begin technical work after the client defines the applicable scope.
Does this provide the whole system?
This page describes software-adapter development. Equipment scope, supply and procedures for the full system must be separately defined in the project.
Can all requirements be guaranteed?
No. Our deliverable is validated against the agreed adapter specification. Legal assessment, external approvals and full-system acceptance have their own procedures.
Can a new product connect to the existing system?
First review available interfaces, version compatibility and technical specifications with the responsible parties. Then determine feasibility and development scope.
Documentation and related needs
Which interfaces are already defined?
Tell us the product, operator and selected system. We will start with the available documentation and agreement on technical boundaries.
Discuss the technical scope