What is STUBB?
Stubb is Tvimenning's product line for mock services. Each Stubb simulates an external system with realistic behaviour, correct protocols, and real data formats. Grid companies switching ERPEnterprise Resource Planning - business system integrating finance, HR, logistics and operations., system vendors testing their ElhubNational hub for metering data and market processes in the Norwegian electricity market. integration, consultants and developers who want to onboard quickly - STUBBTvimenning's simulator platform for integration testing - we build mock environments of the counterparties your systems talk to, so they can be tested without touching production. gives everyone a complete test environment without touching production. Errors are caught early, and migrationProcess of moving data, systems or services from one platform or environment to another. becomes predictable.
What it looks like
STUBB in use
Key features
Realistic simulation
Each Stubb is the reduced core of a real system: same protocol, same data formats, same failure modes as production. Enough of the real system to carry the test, and no more.
The Elhub stub
Simulates the Elhub central system. File-based SOAPSimple Object Access Protocol - XML-based messaging protocol used in enterprise integrations, including Elhub. and XMLExtensible Markup Language - universal markup language for structured data, standard in Elhub's Ediel messages. exchange compatible with EMIF XSDThe name of the XSD set that defines the message formats towards Elhub. It is versioned, and the version number is what decides whether two systems speak the same language. v2.4.3: your system sends the message, the stub generates the ACKThe receipt that says the message arrived. Its counterpart NACK says it was not accepted. Without one of them the sender knows nothing. and updates the status.
Six BRS processes
Registration (BRS-NOElhub’s process specifications. Each BRS describes one market process step by step - who sends what, when, and what happens when something fails.-121) and activation (BRS-NO-122) of a metering pointThe fundamental unit in Elhub - the unique point in the electricity network where energy is measured and settled, identified by an 18-digit GSRN number., master dataThe authoritative source data in a System of Record (Master) - data owned, maintained and edited in one place, from which all other systems retrieve copies. on meter change and address change (BRS-NO-302), a query with a structured XML reply (BRS-NO-303), supplier switchProcess where an electricity customer changes their power supplier - handled through standardised messages via Elhub. notices (BRS-NO-101) and submetering (BRS-NO-701).
The Elsmart stub
Simulates the ElsmartNorwegian AMI platform for collecting, validating and distributing metering data from smart electricity meters for grid companies. work order engine over JSONJavaScript Object Notation - lightweight data format for data exchange between systems, standard in REST APIs. and HTTP. Covers creating a work order, receiving meter data and automatic installation.
The Kartverket stub
Simulates the Kartverket property register over RESTRepresentational State Transfer - architectural style for APIs based on HTTP and resource-oriented design.. Covers cadastre lookups, ownership data, addresses and D-numbers.
The field service stub
Simulates Handyman, SpeedyCraft and Powercatch over REST with webhooks, so field serviceSystem for planning, assigning and following up work carried out in the field - meter changes, component installation and inspections. can be tested without access to a production environment. Covers field assignments, status updates and technician allocation.
The Cubit stub
Simulates the CubitCompliance module for Norwegian grid companies that streamlines reporting and documentation to NVE and RME. inspection system over SSE and REST. Covers inspection cases, inspectors, deviations and the communication between them.
End to end, on your schedule
The whole workflow runs through the test environment without touching production or external parties. Testing does not wait for anyone else to open a window or keep an environment up.
Migration rehearsed before it happens
A data migration with no test environment is an import nobody gets to validate before it is done. Against the stubs the data can be verified up front, so the risk sits in the test phase, where an error is cheap to fix.
Results you can expect
- ✓Remove risk from migrations and upgrades by testing against realistic mock services
- ✓Reduce dependency on access to production systems during development and testing
- ✓Shorter debugging time - errors are caught in the test environment, not in production
- ✓Compatible with all products in the Tvimenning platform
Get started quickly
STUBB is built for rapid implementation. Typical setup takes weeks, not months.
- Dedicated implementation support
- Integration with existing systems
- Training for your team
- Ongoing support after go-live
Who uses STUBB?
System vendors
Test your Elhub integration in a realistic environment before go-liveThe transition from test to live operation against Elhub. The final step in the approval process, and the only one that cannot be undone without someone noticing. and avoid costly errors in production.
Grid companies and retailers
Carry out system migrations safely by validating all message types against STUBB before switching.
Developers
Onboard new developers quickly with access to a complete test environment with no requirement for external access.
Ready to see STUBB in action?
Book a demo and we will show you how STUBB can solve your specific challenges.