Product sheet
LEIDAR
Industry knowledge and application landscape
In design
The situation this answers
You know your own systems, but only part of the market you are choosing in: who supplies what in this domain, and what could replace what you run today.
We want to talk with those of you who
- are about to map the application landscape and do not want to start from scratch.
- are choosing between off-the-shelf solutions and do not know which exist for this domain.
- know a system has to go, but not what could take its place.
- are debating which system should own master data, and inherit today's answer without choosing it.
- have been handed an empty modelling tool before, and spent the time afterwards filling it.
What it is meant to give
- Will start from a finished capability map
- Will name the applications known in the sector
- Will show what can replace today's system
- Will show which systems can own an object
- Will come with the industry code lists loaded
LEIDAR requires VIT: your own systems are VIT's part, the industry landscape is LEIDAR's.
What we do not cover: LEIDAR is to show what exists, not choose for you: no recommendation, no pricing.
LEIDAR · Product sheet
How it works
LEIDAR builds on VIT, adding Tvimenning's own accumulated industry knowledge about which systems and vendors exist in the Norwegian and Nordic energy sector. Where VIT answers what a company itself has, LEIDAR answers "What else exists in the industry, and does it fit us?"
The functions in detail
- IT4IT capability map
- The capability map for the domain is to be in place from the start, structured on the IT4IT reference model.
- Nine domains
- DSO, hydropower, wind power, solar, hydrogen, power supply, retail, district heating and use of energy data.
- Known applications
- For each capability, the applications known in the sector are to be listed by name.
- Replacement map
- The map is to show which products can stand in for each other, for example which MDM alternatives exist for a given system.
- Modernisation planning
- The basis for planning a replacement is to be in place before a migration starts, not gathered along the way.
- Domain object ownership
- Which systems can own a domain object is to be visualised, so the choice of who holds master data is made and not inherited.
- Content from the sector
- The reference base is to be built from work done in the energy sector, not from a generic industry template, and to grow more precise as it is used.
The status, explained
- In design
- Under construction. We would gladly shape it around your needs.
Works together with
- VIT
- Application overview built for the energy sector - criticality, preparedness and Elhub roles built in.
- In design
Terms used here tvimenning.no/en/ordbok
- Off-the-shelf Solutions
- Ready-made software products sold to many customers without customisation - as opposed to custom-built software.
- Master Data
- The authoritative source data in a System of Record (Master) - data owned, maintained and edited in one place, from which all other systems retrieve copies.
- MDM
- Meter Data Management - system for collection, storage, quality assurance and distribution of metering data from the electricity grid.
- Migration
- Process of moving data, systems or services from one platform or environment to another.
- DSO
- Distribution System Operator - grid company that operates the distribution network and is responsible for electricity supply to end users.