Ratings Provider Querying in-use Limit Forecast from the Transmission Provider

Assuming a MonitoringSet “my-monitoring-set” that contains TransmissionFacilities of interest, then the current in-use forecasted limits may be fetched with the following command:

1
2
3

curl -H "Accept: application/vnd.trolie.forecast-limit-set-slim.v1+json" \
-o output.json \
"https://trolie.example.com/rating-proposals/forecasts?monitoring-set=my-monitoring-set"

This will return the current version of the in-use ratings for the next 240 hours into output.json. See the following for an example:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79

{
    "snapshot-header": {
        "last-updated": "2023-07-12T16:00:00-07:00",
        "snapshot-provenance": {
            "provider":"X-AMPL",
            "last-updated": "2023-07-12T16:00:00-07:00",
            "origin-id": "//trolie.example.com/snapshots/2024-08-05T11%3a00%3a00-07%3a00"
        },
        "default-emergency-durations": [
            {
                "name": "lte",
                "duration-minutes": 240
            },
            {
                "name": "ste",
                "duration-minutes": 30
            },
            {
                "name": "dal",
                "duration-minutes": 15
            }
        ],
        "power-system-resources": [
            {
                "resource-id": "8badf00d",
                "alternate-identifiers": [
                    {
                        "name": "segmentX",
                        "authority": "TO-NERC-ID"
                    },
                    {
                        "name": "LINE1 SEG-X",
                        "authority": "RC-NERC-ID",
                        "mrid": "8badf00d"
                    }
                ]
            }
        ]
    },
    "limits": [
        {
            "resource-id": "8badf00d",
            "periods": [
                {
                    "period-start": "2023-07-12T16:00:00-07:00",
                    "period-end": "2023-07-12T17:00:00-07:00",
                    "updated-time": "2023-07-12T13:05:43.044267100-07:00",
                    "continuous-operating-limit": {
                        "mw": 160,
                        "pf": 1.0
                    },
                    "emergency-operating-limits": [
                        {
                            "duration-name": "lte",
                            "limit": {
                                "mw": 170,
                                "pf": 1.0
                            }
                        },
                        {
                            "duration-name": "ste",
                            "limit": {
                                "mw": 180,
                                "pf": 1.0
                            }
                        },
                        {
                            "duration-name": "dal",
                            "limit": {
                                "mw": 190,
                                "pf": 1.0
                            }
                        }
                    ]
                }
            ]
        }
    ]
}

The above example assumes the next 240 hours as determined by the computer clock where TROLIE server is running. Given that there are edge cases in time and the user’s clocks are likely slightly off from the TROLIE server’s clock, it is recommended to specify the times more explicitly to ensure that users are getting what is expected. This may be done by specifying the “offset-period-start” parameter, like in the following example:

1

https://trolie.example.com/rating-proposals/forecasts?monitoring-set=my-monitoring-set&offset-period-start=2025-11-02T02:00:00-06:00

NOTE: This query is an example of an HTTP GET. In addition to curl, the same URL may also be placed in a web browser to see the data.