User Manual
This document is a unified, structured guide to Inside Information Platform (IIP). It includes an overview of regulatory requirements, instructions for using the platform.
Table of Contents
General Information
What is the REMIT Inside Information Platform?
The REMIT Inside Information Platform (IIP) is Webware's solution for European energy market participants to disclose inside information. It centralises, standardises, registers and monitors information about outages or other market events affecting production, consumption or transmission.
A closed, access-controlled section where registered publishers can create and manage Urgent Market Messages (UMMs).
A public section where anyone can view published messages.
Automatic data validation and forwarding to ACER to meet Article 4 reporting obligations.
Accessing & Registering
The platform is fully web-based. To become a publisher, organisations must register via the portal or email support. Webware reviews registration requests within 15 working days and sends login credentials when information is complete. Users must change the password at first login. A main user can then create additional service accounts.
Language & Time Zone
Publications on the IIP are in English. Date and time values use Central European Time (CET/CEST).
Regulations
The IIP is built to comply with European regulatory requirements for inside information disclosure:
REMIT (Regulation (EU) No 1227/2011)
Enhances transparency and stability of EU energy markets, discouraging insider trading and market manipulation.
Article 4
Obliges market participants to disclose inside information publicly. ACER and national regulators oversee compliance.
Article 10 of the REMIT Implementing Regulation
Allows market participants to use third-party providers, such as the IIP, to fulfil their disclosure obligations.
From 1 January 2017:
Inside information related to power and gas outages must be forwarded to ACER via ATOM web feeds; the IIP handles this forwarding automatically.
Service Subscription
A REMIT Article 4 subscription ensures that all Urgent Market Messages published on the IIP are automatically reported to ACER in the required format. When publishing, the company must specify the ACER Market Participant(s) on whose behalf the message is made. The system validates mandatory fields and rejects incomplete submissions.
Viewing Published Information
The public section of the IIP shows a live list of messages, with the most recent at the top. Messages are displayed in three separate boards—Electricity, Gas and Other—and can be downloaded in XML or CSV formats.
Message Statuses:
Active
The latest update on an event that is forthcoming or ongoing.
Inactive
The latest update on an event that has already occurred.
Dismissed
Messages withdrawn or replaced. No longer valid.
Key Features:
- ✓ Filtering: Filter messages by market participant, event status, event type, times, capacity, zones, etc.
- ✓ Sorting: Click column headers to sort ascending or descending; default is by publication time.
- ✓ Notifications: ATOM feeds provide alerts about new messages based on filter settings.
- ✓ Unique URLs: Each published message has a unique URL containing its ID and version.
User Management
User accounts are personal but linked to the organisation. All users belonging to the same organisation share the same rights to publish, update and delete messages.
Publisher
The organisation actively publishing messages. Can publish on behalf of one or multiple market participants.
Market Participant
The organisation defined by ACER as subject to the disclosure obligation.
Administrator Functions:
- ✓ Log in via the platform with credentials
- ✓ Manage users: add, delete or modify accounts
- ✓ Reset passwords via the login page
Publishing Market Information
Registered users can create Urgent Market Messages via a web form. Before publishing for the first time, they must maintain the company's master data—Market Participant ID and Asset Information. Messages are based on the fields defined in the ACER Implementation Guide.
New Urgent Market Message
When composing a UMM, users select the message category, type and type of unavailability according to the information being disclosed. The system validates required fields and provides information icons with explanatory comments. Users can publish new messages and update existing ones.
UMM History
A UMM history is a thread of messages about the same event. Updates on the same event must be published within the same UMM series to provide a clear timeline and ensure that web‑based tools send information correctly.
Field Explanations
The publication form contains numerous fields. Below is a consolidated summary of the key fields:
Market Participant
Identifies the party responsible for disclosing the information. Multiple participants can be listed if they share ownership or liabilities.
Event Status
Indicates whether a message is Active, Dismissed or Inactive.
Type of Event
Specifies the subject of unavailability—Production, Transmission, Consumption or Other.
Event Start / Event Stop
The start and end times of the event. Times should be precise to the minute where possible.
Unit of Measurement
Defines the unit for capacity values (e.g., MW, cubic metres). Required for capacity fields.
Unavailable / Available / Installed Capacity
Quantify how much capacity is unavailable, available and the nominal technical capacity, respectively.
Type of Unavailability
Indicates whether the unavailability is Planned (e.g., maintenance) or Unplanned (e.g., outage).
Reason of Unavailability
A mandatory text field describing the cause of the event.
Remarks
Provides additional context; mandatory for the ‘Other market information’ scheme.
Fuel Type
Required when reporting production unavailability, specifying the energy source.
Bidding Zone / Balancing Zone
Identifies the areas where the affected unit or transmission asset is located using EIC codes.
Affected Asset or Unit / EIC Code
Specifies the facility involved, including the EIC W, T or Z code.
Overlapping Messages & Draft Function
The system does not allow overlapping UMMs (messages with the same type, unit and time interval). Users should update or cancel existing messages instead. A draft function lets users save incomplete messages. Drafts are stored at company level and can be created, updated or deleted. Field validation occurs only when publishing from a draft.
UMM Use Cases
This section provides practical guidance for typical scenarios and clarifies how to meet regulatory requirements:
Updating the UMM series
When new inside information arises, publish a new message within the same UMM series. Compare updates with previous messages to ensure consistency.
Event Start
Should generally not change once the event has begun, unless the original information was incorrect.
Event Stop
For unavailability of electricity or gas facilities, always specify the event stop time. For "Other market information" (permanent events), the stop time is optional.
Dismissing events
If an event will no longer occur, edit the UMM and set the status to "Dismissed," providing a reason. Dismissing a UMM series cannot be undone.
Special Cases
When traditional schemas (electricity/gas unavailability) are unsuitable, use the "Other market information" schema and explain the situation in the remarks.
Ready to Get Started?
Contact our team to register for the Inside Information Platform or start testing today.
