Requirements for the "Remote management of meters" category
| Id |
Requirement |
| GRID-1 |
A meter stores manufacturer information |
| GRID-2 |
A meter stores screen display information |
| GRID-3 |
A meter stores a voltage ratio |
| GRID-4 |
A meter stores a current ratio |
| GRID-5 |
A meter has a firmware |
| GRID-6 |
A meter stores network information |
| GRID-7 |
A meter can send its manufacturer information |
| GRID-8 |
A meter can modify and send its network information |
| GRID-9 |
A meter can modify and send its voltage ratio |
| GRID-10 |
A meter can modify and send its current ratio |
| GRID-11 |
A meter can modify and send its display information |
| GRID-12 |
A meter can update its firmware |
| GRID-13 |
A meter can reconnect or disconnect a client to the electrical network |
| GRID-14 |
A meter has a power threshold |
| GRID-15 |
A power threshold is measured as a percentage |
| GRID-16 |
A meter stores reconnect or disconnect requests scheduled for a specific time |
| GRID-17 |
A meter can be instantly disconnected/reconnected to the low voltage network |
| GRID-18 |
A meter can be scheduled to be disconnected/reconnected to the low voltage network at a given time |
| GRID-19 |
A meter has different types of contracts |
| GRID-20 |
A contract has an activity calendar |
| GRID-21 |
A contract has a power limit |
| GRID-22 |
The power limit of a contract can be disabled |
| GRID-23 |
The power limit of a contract is measured in watts (W) |
| GRID-24 |
A meter can modify the power limit of a contract |
| GRID-25 |
A meter can modify the activity calendar of a contract |
| GRID-26 |
A meter measures the active energy import in each phase |
| GRID-27 |
A meter measures the active energy export in each phase |
| GRID-28 |
Active energy is measured in watt hour (Wh) or kilowatt hour (kWh) |
| GRID-29 |
A meter measures different types of reactive energy in each phase |
| GRID-30 |
Reactive energy is measured in volt-ampere reactive hour (VArh) or kilovolt-ampere reactive hour (kVArh) |
| GRID-31 |
A meter stores incremental and absolute values for each active and reactive energy measure |
| GRID-32 |
A meter stores a timestamp for each active and reactive energy measure |
| GRID-33 |
A meter can send an hourly incremental load profile |
| GRID-34 |
An hourly incremental load profile is represented by the incremental values of the measures performed by the meter each hour |
| GRID-35 |
A meter can send a reduced hourly incremental load profile |
| GRID-36 |
A reduced hourly incremental load profile is represented by the incremental active energy values measured by the meter each hour |
| GRID-37 |
A meter can send a daily billing values profile |
| GRID-38 |
A daily billing values profile is represented by the absolute values of the measures performed by the meter each day |
| GRID-39 |
A meter can send a monthly billing values profile |
| GRID-40 |
A monthly billing values profile is represented by the absolute and incremental values of the measures performed by the meter each month |
| GRID-41 |
A meter has a threshold for voltage sags, voltage swells, and long power failures |
| GRID-42 |
Thresholds are measured as percentages |
| GRID-43 |
A meter has a time threshold for voltage sags, voltage swells, and long power failures |
| GRID-44 |
Time thresholds are measured in seconds |
| GRID-45 |
A meter stores the number of voltage swells, voltage sags, and long power failures that occur in each phase |
| GRID-46 |
A meter stores the duration of each voltage swell, voltage sag, and long power failure that occurs in each phase |
| GRID-47 |
Durations are measured in seconds |
| GRID-48 |
A meter can send a voltage failure report |
| GRID-49 |
A voltage failure report is represented by the time threshold, number, and duration of the long power failures in each phase |
| GRID-50 |
A meter can send a power quality report |
| GRID-51 |
A power quality report is represented by the number and duration of voltage swells, voltage sags, and long power failures in each phase |
Requirements for the "Management of tertiary sensor devices" category
| Id |
Requirement |
| GRID-52 |
A data concentrator manages a set of meters |
| GRID-53 |
A data concentrator stores the identifier of the meters it manages |
| GRID-54 |
A data concentrator collects information from the meters it manages |
| GRID-55 |
A data concentrator stores manufacturer information |
| GRID-56 |
A data concentrator has a firmware |
| GRID-57 |
A data concentrator stores network information |
| GRID-58 |
A data concentrator stores tasks configuration |
| GRID-59 |
A data concentrator stores data collection configuration |
| GRID-60 |
A data concentrator can stop managing a meter |
| GRID-61 |
A data concentrator can update its firmware |
| GRID-62 |
A data concentrator can receive an order to execute a task at the moment |
| GRID-63 |
A data concentrator can receive an order to execute a scheduled task |
| GRID-64 |
A data concentrator can modify its network information |
| GRID-65 |
A data concentrator can send its task configuration |
| GRID-66 |
A data concentrator can send the identifier of the meters that it manages |
| GRID-67 |
A data concentrator can send its collect configuration |
| GRID-68 |
A data concentrator can send its network information |
| GRID-69 |
A data concentrator can generate a daily communication report |
| GRID-70 |
A data concentrator can generate an hourly communication report |
| GRID-71 |
A data concentrator can generate a performance report with information about the tasks in progress |
| GRID-72 |
A data concentrator can generate a performance report with historical information about the finished tasks |
| GRID-73 |
A data concentrator can generate a performance report with information about scheduled tasks |
| GRID-74 |
A data concentrator can generate a maintenance report with information about firmware updates performed in the meters that it manages |
| GRID-75 |
A data concentrator can generate a historical quality report |
| GRID-76 |
A data concentrator can generate a historical maintenance report with information about the parameters modified in the concentrator |
| GRID-77 |
A line supervision card stores manufacturer information |
| GRID-78 |
A line supervision card has a firmware |
| GRID-79 |
A line supervision card stores communication information |
| GRID-80 |
A line supervision card can send its manufacturer information |
| GRID-81 |
A line supervision card can send its firmware information |
| GRID-82 |
A line supervision card can update its firmware |
| GRID-83 |
A line supervision card can send its communication information |
| GRID-84 |
A line supervision card can modify its communication information |
| GRID-85 |
A remote terminal unit manages a set of line supervision cards |
| GRID-86 |
A remote terminal unit stores the identifier of the line supervision cards that it manages |
| GRID-87 |
A remote terminal unit collects information from the line supervision cards that it manages |
| GRID-88 |
A remote terminal unit stores manufacturer information |
| GRID-89 |
A remote terminal unit has a firmware |
| GRID-90 |
A remote terminal unit stores its task configuration |
| GRID-91 |
A remote terminal unit stores its data collection configuration |
| GRID-92 |
A remote terminal can stop managing a line supervision card |
| GRID-93 |
A remote terminal can modify its dynamic parameters |
| GRID-94 |
A remote terminal can send its dynamic and static parameters |
| GRID-95 |
A remote terminal unit can update its firmware |
| GRID-96 |
A remote terminal unit can send it task schedule |
| GRID-97 |
A remote terminal unit can send its event information |
| GRID-98 |
A remote terminal unit can send the identifier of the line supervision cards it manages |
Requirements for the "Management of OLTC transformers" category
| Id |
Requirement |
| GRID-99 |
A meter stores each second the voltage, current and power measured in each phase |
| GRID-100 |
A line supervision card stores each second the voltage, current and the active and reactive power measured in each phase |
| GRID-101 |
A meter stores each second the voltage amplitude measured in each phase |
| GRID-102 |
A remote terminal unit stores each second the voltage amplitude measured in each phase |
| GRID-103 |
A meter can send an instantaneous values profile |
| GRID-104 |
An instantaneous values profile is represented by the instant data values that the meter measures |
| GRID-105 |
A meter can send a voltage and current profile |
| GRID-106 |
A voltage and current profile is represented by the average voltage/current/power measured in each phase over a period of time |
| GRID-107 |
A meter can send an extended voltage profile |
| GRID-108 |
An extended voltage profile is represented by the average voltage/current/power measured in each phase during a period of time and the maximum and minimum values registered in that period per phase |
| GRID-109 |
A meter can send an hourly instantaneous values profile |
| GRID-110 |
An hourly instantaneous values profile is represented by the instant data values measured in a meter each hour |
| GRID-111 |
A meter can send a voltage profile |
| GRID-112 |
A voltage profile is represented by the average, maximum, and minimum values of the voltage measured in each phase over a period of time |
| GRID-113 |
A line supervision card can send a real time values report |
| GRID-114 |
A real-time values report is represented by the voltage/current/active and reactive power magnitudes measured in each phase |
| GRID-115 |
A line supervision card can send an average voltage and current profile |
| GRID-116 |
An average voltage and current profile is represented by the average voltage/current/active and reactive power magnitudes measured in each phase over a period of time |
| GRID-117 |
A meter can send a voltage amplitude profile |
| GRID-118 |
A remote terminal unit can send a voltage amplitude profile |
| GRID-119 |
A voltage amplitude profile is represented by the average voltage amplitude measured in each phase during a period of time |
