Product sheet
In design
The situation this answers
After mergers and years of gradual system growth, nobody can say which systems the company actually owns, who maintains them, or what depends on what.
We want to talk with those of you who
- have just merged two system landscapes and do not know what came along.
- run everything from ERP to SCADA, and need office systems and operational technology kept apart.
- need to show which systems support an essential function, and how critical they are.
- find out a vendor agreement is expiring only when the renewal lands on the desk.
- have tried a generic tool before, and missed it knowing the power sector.
What it is meant to give
- Will give one consolidated answer to which systems you own, and who maintains them
- Will show which systems connect to which, and what role each of them plays towards Elhub
- Will separate the systems that support an essential function from those that do not
- Will make technical debt visible: software that is outdated or out of support
- Will be kept current automatically, not by hand
VIT stands on its own and requires no other modules.
What we do not cover: VIT is to describe the systems, not run them: no monitoring, no access control.
VIT · Product sheet
How it works
After mergers and years of gradual system growth, many grid companies hold an IT landscape nobody has a full picture of. Which systems actually exist, who maintains them, what depends on what, and which vendor agreements are approaching renewal. VIT brings this together in one place. The usual reason such overviews are never maintained is that they demand continuous manual entry, so VIT builds on automated discovery of the IT environment and adds an energy-domain layer on top: Elhub role per system, a split between IT and operational technology, and criticality assessment. The engine is generic and works in other industries. The content is built for the power sector. VIT is also the data foundation LEIDAR builds on. Building the overview is often as valuable as having it: it forces an honest meeting between stated strategy and the way the organisation actually works.
The functions in detail
- Application inventory
- A full overview of every IT system, carrying both technical and business information per system.
- Dependency map
- Which systems talk to which, including the Elhub integrations.
- User tracking
- Who uses what, per system and per department.
- Version monitoring
- Flags outdated or end-of-life software before it becomes a problem.
- Vendor overview
- Agreements, service levels and renewal windows in one place.
- Criticality assessment
- An assessment of whether a system supports an essential function, and how critical it is. The model follows the Norwegian preparedness regulation, and is prepared for NIS2 once the directive enters Norwegian law.
- Elhub role tagging
- Every system is tagged with its actual market role, such as metered data collection, data hub connection, balance responsibility or power supply.
The status, explained
- In design
- Under construction. We would gladly shape it around your needs.
Works together with
- LEIDAR
- Industry knowledge of which systems and vendors exist in the energy sector, useful for procurement.
- In design
Terms used here tvimenning.no/en/ordbok
- ERP
- Enterprise Resource Planning - business system integrating finance, HR, logistics and operations.
- SCADA
- Supervisory Control and Data Acquisition - system for real-time monitoring and control of industrial processes.
- Elhub
- National hub for metering data and market processes in the Norwegian electricity market.
- Technical debt
- Accumulated costs of quick, short-term technological decisions - makes future development slower and more expensive.
- NIS2
- EU directive on network and information security - imposes strict security requirements on critical infrastructure.
