Telecoms Data and Outputs
This page describes Telecoms data and outputs that are not covered in the Telecoms Tasks guide.
The data import and configuration sections are intended for Rail BI administrators. General users should start with Telecoms Tasks.
Telecoms Data
Telecoms asset data is stored in DataStore and imported into Rail BI as Telecoms assets. When source data changes, updated values appear after the normal data refresh and any required option rebuild or cache.
Key Telecoms Data Fields and Filters
| Category | Examples |
|---|---|
| Key DataStore fields | Ellipse site identifier, route and devolved route, SRS, MDU, ELR, miles, yards, Control Point, primary TOC/SFO, asset location, site type, asset type, manufacturer, model, primary group, primary asset, volume type, service dates, renewal dates, quantity, service life and the DataStore unique identifier |
| Area selector filters | Telecoms, Route (including devolved route), SRS, MDU, asset location, site type, Control Point and primary TOC/SFO |
| Calendar groupings | Off, Primary Asset, Volume Type, Asset Type and Site Type |
The current Telecoms calendar does not provide MDU or Control Point as calendar grouping or filter options. These attributes remain available in the area selector and on other screens where the Telecoms filter controls are exposed.
Telecoms filters are also used by the Telecoms Business Plan, cost and volume views, and maps where that screen exposes the Telecoms filter controls. These filters apply to Telecoms asset locations rather than to interlocking or level crossing areas.
For calendar grouping options, see Calendar View.
Telecoms Configuration
Telecoms configuration maintains the following Rail BI settings:
- the Telecoms technology group and Telecoms technology application;
- Telecoms technologies, technology levels, work types and renewal policies;
- the Telecom asset-discipline category and its work-type links;
- Telecoms interaction rules between work types and technology levels; and
- the default Telecoms spike profile used by work types that do not already have one.
The Telecoms configuration also defines the attribute used for like-for-like filtering. Like-for-like renewal can be enabled by default, depending on the configuration. See Telecoms Interventions.
For the general administration workflow, see Telecoms tasks.
Technology Group administration is intended for administrators. See Technology Groups for the shared administration page.
Telecoms Outputs
Telecom volumes are calculated from the Telecoms quantity attribute rather than interlocking SEUs. This quantity is used for activity volumes, affected volumes, cost and volume views, and pro-rata calculations.
The cost and volume graph supports the Telecom-specific groupings Volume Type and Asset Type. These groupings are only available for Telecoms.
Package and Business Plan tables can include Telecoms attributes as columns. Telecoms fields can also be included in package and CP Planning exports, depending on the filters and columns selected.
For the output screens, see Workbank outputs and Costs and Volumes Configuration.
Maps and Exports
Telecoms options expose asset positions to map layers. The filters available on a map depend on the map view; do not assume that every Telecoms calendar filter is available there.
Telecoms fields are available in discipline package-plan and CP Planning exports. Overlay option comparisons are not available for the by-route or by-region Telecoms cost exports.
For the general workflows, see Intervention Map, Workbank Exports and Package CapEx Costs.
Additional Notes
Telecom quantities are sourced from the Telecoms asset data. They are displayed in the Telecoms calendar and used to calculate Telecoms cost and volume outputs. The intervention modal does not provide a field for editing the source quantity; contact the Telecoms data owner if the source value needs correcting.