{"text_format":"1","workbook":"xlsx","n_sheets":1,"sheets":["Basis of Preparation"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":1,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Basis of Preparation","index":0,"n_rows":348,"n_cols":7,"rows_kept":348,"cut":false,"hidden":false,"merged":[[345,2,345,6],[346,2,346,6],[347,2,347,6],[334,2,334,6],[333,2,333,6],[335,2,335,6],[336,2,336,6],[337,2,337,6],[338,2,338,6],[339,2,339,6],[340,2,340,6],[341,2,341,6],[342,2,342,6],[343,2,343,6],[344,2,344,6],[332,1,332,6],[331,1,331,6],[254,0,254,6],[262,0,262,6],[263,0,263,6],[315,5,319,5],[264,5,266,5],[264,6,266,6],[267,0,267,6],[321,0,321,6],[283,0,283,6],[289,0,289,6],[290,0,290,6],[299,0,299,6],[300,0,300,6],[311,0,311,6],[312,0,312,6],[320,0,320,6],[136,1,137,1],[138,1,139,1],[140,1,141,1],[163,1,164,1],[172,0,172,6],[206,0,206,6],[212,5,216,5],[189,0,189,6],[211,0,211,6],[144,0,144,6],[146,0,146,6],[147,0,147,6],[162,0,162,6],[163,5,164,5],[165,5,166,5],[90,6,96,6],[108,0,108,6],[98,5,106,5],[97,0,97,6],[165,1,166,1],[142,0,142,6],[325,0,325,6],[167,0,167,6],[210,0,210,6],[217,0,217,6],[224,0,224,6],[247,0,247,6],[249,0,249,6],[284,0,284,6],[246,0,246,6],[207,0,207,6],[223,0,223,6],[228,0,228,6],[232,0,232,6],[173,0,173,6],[291,5,298,5],[190,6,205,6],[324,0,324,6],[291,6,298,6],[0,0,0,6],[3,0,3,6],[15,0,15,6],[25,0,25,6],[2,0,2,6],[34,0,34,6],[62,0,62,6],[89,0,89,6],[43,0,43,6],[53,0,53,6],[63,0,63,6],[75,0,75,6],[83,0,83,6],[84,0,84,6],[86,0,86,6],[88,0,88,6],[98,6,106,6],[109,6,117,6],[119,0,119,6],[109,5,117,5],[134,1,135,1],[107,0,107,6],[118,0,118,6],[132,0,132,6],[133,0,133,6],[125,0,125,6],[126,0,126,6],[250,5,253,5],[255,5,261,5],[255,6,261,6],[250,6,253,6],[311,7,312,7],[4,5,9,5],[12,5,14,5],[26,5,29,5],[35,5,38,5],[4,6,9,6],[16,6,18,6],[16,5,21,5],[268,7,282,7],[285,5,288,5],[285,6,288,6],[285,7,288,7],[283,7,284,7],[190,5,205,5],[54,5,59,5],[233,6,245,6],[233,5,245,5],[268,6,282,6],[268,5,282,5],[212,6,216,6]]}
["ActewAGL Distribution: Basis of Preparation - CATEGORY ANALYSIS RIN 2014/15"]
["Variable code","Variable","Financial or\nNon-Financial","Consistent with the Notice \n- 2.2 (a)?","Actual or \nEstimated","Data Source","Methodology"]
["Worksheet 2.1 - EXPENDITURE SUMMARY"]
["Table 2.1.1 - STANDARD CONTROL SERVICES CAPEX"]
[null,"Replacement expenditure","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","Data has been extracted from the relevant RIN report templates through links. This is direct expenditure. "]
[null,"Connections","F",null,"A"]
[null,"Augmentation Expenditure","F",null,"A"]
[null,"Non-network","F",null,"A"]
[null,"Capitalised network overheads","F",null,"A"]
[null,"Capitalised corporate overheads","F",null,"A"]
[null,"Metering","N/A","N/A","N/A","x","x"]
[null,"Public Lighting","N/A","N/A","N/A","x","x"]
[null,"Balancing item","F",null,"A",null,"As above"]
[null,"TOTAL GROSS CAPEX (includes capcons)","F",null,"A",null,"As above"]
[null,"Capcons","F",null,"A"]
["Table 2.1.2 - STANDARD CONTROL SERVICES OPEX"]
[null,"Vegetation management","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","Data has been extracted from the relevant RIN report templates through links. This is direct expenditure. "]
[null,"Maintenance","F",null,"A"]
[null,"Emergency response","F",null,"A"]
[null,"Non-network","F",null,"A",null,"Data has been extracted from the relevant RIN report templates through links. This is direct expenditure. \nDouble counting for overheads has been removed as they are accounted for in Network Overheads."]
[null,"Network overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report templates through links. This is direct expenditure. "]
[null,"Corporate overheads","F",null,"A",null,"As above"]
[null,"Metering","N/A","N/A","N/A","x","N/A"]
[null,"Public Lighting","N/A","N/A","N/A","x","N/A"]
[null,"Balancing item","F",null,"A",null,"As above"]
["Table 2.1.3 - ALTERNATIVE CONTROL SERVICES CAPEX"]
[null,"Connections","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","Data has been extracted from the relevant RIN report through links. This is direct expenditure. "]
[null,"Capitalised network overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure.\nCapex & Opex portion has been separated as template 2.10 does not separate capex/opex for alternative control."]
[null,"Capitalised corporate overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure. "]
[null,"Metering","F",null,"A",null,"As above"]
[null,"Public lighting","N/A","N/A","N/A","N/A","N/A"]
[null,"Fee and quoted","F",null,"A",null,"As above"]
[null,"Balancing item","F",null,"A",null,"As above"]
[null,"TOTAL CAPEX","F",null,"A",null,"As above"]
["Table 2.1.4 - ALTERNATIVE CONTROL SERVICES OPEX"]
[null,"Connections","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","Data has been extracted from the relevant RIN report through links. This is direct expenditure. "]
[null,"Network overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure.\nCapex & Opex portion has been separated as worksheet 2.10 does not separate capex/opex for alternative control."]
[null,"Corporate overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure. "]
[null,"Metering","F",null,"A",null,"As above"]
[null,"Public lighting","N/A","N/A","N/A","N/A","N/A"]
[null,"Fee and quoted","F",null,"A",null,"As above"]
[null,"Balancing item","F",null,"A",null,"As above"]
[null,"TOTAL OPEX","F",null,"A",null,"As above"]
["Table 2.1.5 - DUAL FUNCTION ASSETS CAPEX"]
[null,"Replacement expenditure","F",null,"A"]
[null,"Connections","F",null,"A"]
[null,"Augmentation Expenditure","F",null,"A"]
[null,"Non-network","F",null,"A"]
[null,"Capitalised network overheads","F",null,"A"]
[null,"Capitalised corporate overheads","F",null,"A"]
[null,"Balancing item","F",null,"A"]
[null,"TOTAL GROSS CAPEX (includes capcons)","F",null,"A"]
[null,"Capcons","F",null,"A"]
["Table 2.1.6 - DUAL FUNCTION ASSETS OPEX"]
[null,"Vegetation management","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","Data has been extracted from the relevant RIN report through links. This is direct expenditure. "]
[null,"Maintenance","F",null,"A",null,"As above"]
[null,"Emergency response","F",null,"A",null,"As above"]
[null,"Non-network","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure. An adjustment has been made to take the transmissions portion of standard control opex by multiplying the direct portion of maintenance on transmission to total maintenance."]
[null,"Network overheads","F",null,"A",null,"Data has been extracted from the relevant RIN report through links. This is direct expenditure. \nAn adjustment has been made to take the transmissions portion of standard control opex by multiplying the direct portion of maintenance on transmission to total maintenance."]
[null,"Corporate overheads","F",null,"A",null,"As above"]
[null,"Balancing item","F",null,"A","N/A","N/A"]
[null,"TOTAL OPEX","F",null,"A","ActewAGL Distribution 2014/15 Category Analysis RIN report","As above"]
["Worksheet 2.2 - REPEX"]
["TABLE 2.2.1 - REPLACEMENT EXPENDITURE, VOLUMES AND ASSET FAILURES BY ASSET CATEGORY"]
[null,"All sub-categories below","F",null,"A","ORACLE Financial database","FINANCIAL: Oracle replacement capital expenditure history - ENAR (electricity networks asset replacement) capital projects extracted from Oracle data cube, and allocated to RIN categories.  In some instances there was a 1:1 mapping (eg pole reinforcement to staking a wood pole).  Some Oracle projects were allocated based on the project description to RIN asset classes.  Some have been allocated / pro-rated to RIN asset classes on the basis of non-financial information in the Category Analysis RIN report. "]
[null,"Poles by: Highest operating voltage; Material Type;  Staking (if wood)","NF",null,"A","CITYWORKS operations database \n\nCITYWORKS operations database\n\nCITYWORKS operations database\n\nApply Outage database\n","NON-FINANCIAL: For staking: Derived from the CityWorks work task completed for pole replacement. Report - Pole Reporting Suite - 20150706\nFor pole replacement: Derived from the Cityworks work task completed for pole replacement. Report - PoleReplacement \nFor transmission pole replacement: Based on FY14/15 transmission pole replacement\n\nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab."]
[null,"Pole Top Structures by: Highest Operating Voltage","NF",null,"A","ORACLE Financial database\n\n \n\n\nAPPLY Outage database\n\n\nORACLE Financial database  \nORACLE Financial database \n\n","For crossarm material: All crossarms booked to crossarm replacement projects are for REPEX. All crossarms booked to crossarm replacement project numbers are counted.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Crossarm Summary Tab. \n\nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE\n\nFor HV: Category: Use Insulator, Crossarm and Pole Top Structure - 7kV to 11kV.\nFor LV: Category: Use Insulator, Crossarm and Pole Top Structure - LV.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab\n\n"]
[null,"Overhead Conductors by: \nHighest Operating Voltage; Number of Phases (at HV)","NF",null,"A","ORACLE Financial database\n\n\n\nAPPLY Outage database\n\nORACLE Financial database\nTCS database\n","For conductor material: All conductors booked to replacement projects are for REPEX. All conductors booked to replacement project numbers are counted.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - OH Tab\nFilter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE\nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE\nFor HV conductor failure: Category: Conductor 7kV to 11.9kV. \nFor LV conductor failure: Category: Wires Down\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab"]
[null,"Underground Cables by: Highest Operating Voltage","NF",null,"A","ORACLE Financial database\n\n\n\nAPPLY Outage database\n \n","For UG cable material: All cables booked to replacement projects are for REPEX. All cables booked to replacement project numbers are counted.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - UGSummary Tab\nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE. \nUse Outage database, Category: Cable, Overhead termination, Structure termination, Switchgear termination, Transformer termination.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab Using ORACLE data.\nAll cables booked to replacement projects are for REPEX.\n"]
[null,"Service Lines by: Connection Voltage; Customer Type; Connection Complexity","NF",null,"A","ArcFM GIS database \n\n\nTCS database/ArcFM database\n\n\n\nTCS database\n\n","For Overhead Service Line & UG Service Line feature class: Using ArcFM GIS data for all service lines commissioned in FY14/15. Filter by: CommissionedDate >= '2014-07-01 00:00:00' AND CommissionedDate <= '2015-06-30 00:00:00' AND LifecycleStatus = 'InService' AND DataSource = 'WASPWORKPACK'\nFor asset failure: Using TCS Data - Spark/Fire/Explosion & Arcing. \nWhere DataSource is 'WASPWORKPACK', they are assumed to have been done as a replacement. Therefore, counted as REPEX. \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab. Note: Using ArcFM Data for all service lines commissioned in FY14/15.\nFor asset failure: Using TCS Data - Spark/Fire/Explosion & Arcing. \nWhere DataSource is 'WASPWORKPACK', they are assumed to have been done as a replacement. Therefore, counted as REPEX.\nNo AUGEX will be in overhead services as all greenfield sites are underground service."]
[null,"Transformers by: \nMounting Type; Highest Operating Voltage; Ampere Rating; Number of Phases (at LV)","NF",null,"A","ORACLE Financial database\n\n\n\n\n\n\n\nAPPLY Outage database\n\n\n\nCITYWORKS operations database\n\n","For transformer material: Oracle used to identify all capex projects of various types above specified thresholds.  Project documentation, cost estimates and event advices and emails (where applicable) used to determine asset additions, asset failures etc.  Oracle Projects Inquiry used to get capex total expenditure for FY14-15 from same report, excluding those reported as material. Project end-date interpreted as last year of expenditure shown within Oracle. Asset replacements such as 132kV Voltage Transformer, 11kV Sealing Ends and ZS property considered under other zone substation category as no specific field(s) available to consider this assets. \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - TXSummary Tab\nAll transformer booked to replacement projects are counted. \nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab \nAll TX booked to replacement projects are for REPEX.\nAsset replacements have been confirmed during various monthly inspections and safety audits. \nFinancial records confirmed the replaced assets. \nAsset register will be updated before project closure."]
[null,"Switchgear by: Highest Operating Voltage; Switch Function","NF",null,"A","ORACLE Financial database  \n\n\nAPPLY Outage database\n\n\n\nTCS database\nAPPLY Outage database","For switchgear material: \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - SWSummary Tab.\nAll switchgear booked to replacement projects are counted. \nFor asset failures: Filter: Design/Construction deficiencies, equipment failure, Fire & Inadequate maintenance. Multiple Entry: FALSE. \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - Summary Tab Using ORACLE data.\nAll switchgear booked to replacement projects are for REPEX.\nFor fuse asset failure : Using TCS Data = 174 Network equip Fault = Fuse blown\nFor switchgear failure : Using outage database."]
[null,"Public Lighting by: Asset Type; Lighting Obligation","NF",null,"A","ActewAGL Distribution does not own the streetlight network in the ACT","x"]
[null,"SCADA, Network Control and Protection Systems by: Function","NF",null,"A","Operational field approval form","Data obtained from the approval forms used for the Gilmore Zone sub-station relating to asset addition and retirement. A count of the protection relays on the form was performed."]
[null,"Other by: DNSP defined","x",null,"x","x","x"]
["TABLE 2.2 - SELECTED ASSET CHARACTERISTICS"]
[null,"All sub-categories below","F",null,"A","ORACLE Project Accounting","FINANCIAL: ORACLE replacement capital expenditure history - ENAR (electricity networks asset replacement) capital projects extracted from ORACLE data cube, and allocated to RIN categories.  In some instances there was a 1:1 mapping (e.g. pole reinforcement to staking a wood pole).  Some ORACLE projects were allocated based on the project description to RIN asset classes.  Some have been allocated / pro-rated to RIN asset classes on the basis of non-financial information in the Category Analysis RIN report. "]
[null,"Poles by: Feeder Type","NF",null,"A","ArcFM GIS database","Asset replacement does not include transmission poles.\nAsset volumes currently in commission does not include transmission poles as they are neither \"rural short\" or \"urban\" feeder.\nPoles in the urban inspection sector are urban poles.\nPoles in the rural inspection sector are rural short."]
[null,"Overhead Conductors by: Conductor Length by Feeder Type","NF",null,"A","ArcFM GIS database","Using AER classification of Urban & Rural Short feeders, there are 56 feeders identified as rural short this year. Overhead conductors do not include low voltage overhead conductor. Only high voltage conductor is included.\nUsing ArcFM data to summate the length.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - RawUGOH Tab"]
[null,"Overhead Conductors by: Conductor Length by Material","NF",null,"A","ArcFM GIS database","Includes both high voltage and low voltage.\nUsing ArcFM data to summate the length.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - RawUGOH Tab\n"]
[null,"Underground Cables by: Cable Length by Feeder Type","NF",null,"A","ArcFM GIS database","Using AER classification of Urban & Rural Short feeders, there are 56 feeders identified as rural short this year. Does not include low voltage underground cables. Only includes high voltage underground cables. \nUsing ArcFM data to summate the length.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - RawUGOH Tab"]
[null,"Service Lines by: Connection Voltage; Customer Type; Connection Complexity","NF",null,"A","UG/OH spreadsheet","\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - RawUGOH Tab"]
[null,"Transformers by: Total MVA","NF",null,"A","ORACLE Financial database","For TX Asset Replacement MVA Capacity - ORACLE data - \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.xlsx - TXSummary Tab\nFor TX MVA capacity, same as 3.5 Network Capacity.\nFor MVA disposed of use:\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_2 Repex\\2.2.2 TX MVA Disposed\\Stanley - ActewAGL Padmount & Tx Register & Configuration spreadsheet_RS (Master).xlsx"]
["Worksheet 2.3 - AUGEX PROJECT DATA"]
["TABLE 2.3.1 - AUGEX ASSET DATA - SUBTRANSMISSION SUBSTATIONS, SWITCHING STATIONS AND ZONE SUBSTATIONS"]
[null,"Substation ID","NF",null,"A","No work in 2014/15","There were no transmission (132 kV) or sub-transmission (66 kV) augmentation projects carried out during the 2014-15 financial year."]
["TABLE 2.3.2 - AUGEX ASSET DATA - SUBTRANSMISSION LINES"]
[null,"Line ID","NF",null,"A","No work in 2014/15","There were no transmission (132 kV) or sub-transmission (66 kV) augmentation projects carried out during the 2014-15 financial year."]
["TABLE 2.3.3 - AUGEX DATA - HV/LV FEEDERS AND DISTRIBUTION SUBSTATIONS"]
["Table 2.3.3.1 Descriptor Metrics"]
[null,"HV Feeder Augmentations - Overhead Lines\n(Circuit Line Length in KM)","NF",null,"E","ArcFM GIS database","No subtransmission works were undertaken during the 2014-15 financial year. \n\nDistribution assets added were obtained from the ArcFM GIS system, by filtering out all new assets commissioned between 1.7.14 and 30.6.15. The majority of these were assets added to the system. \n\nOnly a few replacement projects were done involving augmentation of assets. These included: One 11kV feeder replacement 270m of HV cable 3c/240mm2 to replace obsolete 3c/129mm2 cable, 5 x LV Consac cable replacement projects to replace 2765m of old 4c/171mm2 cable with new 4c/240mm2 cables. \n\nThese new cable sizes are ActewAGL's standard sizes being the \"next larger\" than the old cables they were replacing. Refer Cable Standard doc SM11137 and Cables Asset Strategy Plan SM1128."]
[null,"HV Feeder Augmentations - Underground Cables\n(Circuit Line Length in KM)","NF",null,"E","x"]
[null,"LV Feeder Augmentations - Overhead Lines\n(Circuit Line Length in KM)","NF",null,"E","x"]
[null,"LV Feeder Augmentations - Underground Cables\n(Circuit Line Length in KM)","NF",null,"E","x"]
[null,"Distribution Substation Augmentations - Pole Mounted","NF",null,"E","x"]
[null,"Distribution Substation Augmentations - Ground Mounted","NF",null,"E","x"]
[null,"Distribution Substation Augmentations - Indoor","NF",null,"E","x"]
["Table 2.3.3.2 - Cost Metrics"]
[null,"HV Feeder Augmentations - Overhead Lines","F",null,"A","ORACLE Project Accounting","Total project costs for each year and asset category taken from ORACLE capital projects data cube, split according to asset categorisation for each project.\n"]
[null,"HV Feeder Augmentations - Underground Cables","F",null,"A"]
[null,"HV Feeder Non-Material Projects","F",null,"A"]
[null,"LV Feeder Augmentations - Overhead Lines","F",null,"A"]
[null,"LV Feeder Augmentations - Underground Cables","F",null,"A"]
[null,"LV Feeder Non-Material Projects","F",null,"A"]
[null,"Distribution Substation Augmentations - Pole Mounted","F",null,"A"]
[null,"Distribution Substation Augmentations - Ground Mounted","F",null,"A"]
[null,"Distribution Substation Augmentations - Indoor","F",null,"A"]
["TABLE 2.3.4 - AUGEX DATA - TOTAL EXPENDITURE"]
["AUGMENTATION CAPEX"]
[null,"Sub transmission Substations, Switching Stations, Zone Substations","F",null,"A","ORACLE Project Accounting","Total project costs for each year and asset category taken from ORACLE capital projects data cube, split according to asset categorisation for each project.\n"]
[null,"Sub transmission Lines","F",null,"A"]
[null,"HV Feeders","F",null,"A"]
[null,"HV Feeders - Land Purchases and Easements","F",null,"A"]
[null,"Distribution Substations","F",null,"A"]
[null,"Distribution Substations - Land Purchases And Easements","F",null,"A"]
[null,"LV Feeders","F",null,"A"]
[null,"LV Feeders - Land Purchases And Easements","F",null,"A"]
[null,"Other Assets","F",null,"A"]
["2.5 CONNECTIONS"]
["TABLE 2.5.1 - DESCRIPTOR METRICS"]
[null,"All sub-categories below","F",null,"A","ORACLE Project Accounting","FINANCIAL: Total cost of customer connections is taken from ORACLE accounts (actual data).  Projects that did not include a new connection (relocation or replacement of existing services etc) have been excluded - these are reported as Quoted services in the RIN.  Small residential PV systems are also not reported in the figures here - as these are not a new connection.\nEach project has been categorised as to the type of customer (residential, C/I, subdivision, embedded generator) according to ORACLE project categories and inspection of project title.  Projects further categorised according to project type (simple / complex, HV LV etc) according to the split of capitalised assets in the fixed asset register, and OH/UG connections according to whether OH or UG capitalised amount is greater.  \n\nThe expenditure on different asset types has been determined from the fixed asset register, assuming the expenditure on each asset type (substation, HV and LV) is the same for each year on the project (i.e. the capitalisation data does not show whether there was expenditure on HV in year 1 and subs in year 2 of the project - we have assumed the same proportional expenditure on each asset type for each year of the project).\n\nThe totals reported in the RIN are calculated by summating total expenditure by year, asset type or connection type filtered according to the criteria contained in the RIN table and definitions.  HV and LV circuit km added have been estimated based on typical per unit rates, using ActewAGL unit rates for HV and LV feeders (audited by SKM).\n\nConnection volumes for basic (simple) connections have been extracted from the Farmer system used by ActewAGL for works management of connections.  3.4% of basic connections assumed to be Commercial/Industrial.  For complex connections, each project has a unique project number, and volumes are taken from a count of projects within the appropriate categories."]
[null,"Residential","NF",null,"E","VELOCITY billing database\n\n\n\n\n\n\n\n\nORACLE database\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nCITYWORKS operations database \n\n","Simple connection LV:  This is the summation of data extracted from Velocity for commercial and industrial basic connections, OH/UG connections & initial services to blocks (<100A connections with no LV reticulation works)\nMean days to connect residential customer\nA Velocity report is available that determines the mean days to connect residential customer with LV single phase connection (0's). Velocity determines the mean days to connect each individual connection by calculating the days between when the request is made and when Works Delivery close the work order (indicating that the physical work is complete). Velocity then determines the mean of all the individual projects for  a set specified period (e.g. financial year)\n\nCumulated net km's added for augmented HV & LV lines is actual data extracted from ActewAGL's ORACLE Inventory system. This system does break the data down into the categories of residential, commercial/industrial and greenfield. Filters in the ORACLE data spread sheet were applied to get the total lengths of HV & LV cables in these categories. Relocations and replacements works are excluded from this report. Inventory issues listing all the materials consumed for customer initiates projects for FY 2014/15.\n\nNumber of augmented substations are actual data extracted from ActewAGL's ORACLE Inventory system. This system does break the data down into the categories of residential, commercial/industrial and subdivision\nNumber of chamber substation were estimated based on the 2 Tx per chamber or 1 Tx per chamber. Relocations and replacements works are excluded from this report. Padmount substation and pole substation were actual quantities as per the inventory issues. Filters in the ORACLE data spread sheet were used to get the total quantities and capacity (MVA). \n\nWhere multiple connections occurred at the same address, this was assumed to be a block of units, and hence a complex LV connection; all other connections reported as simple LV connection. No residential complex HV connections provided in FY 14/15. Note: The data reported against services includes negotiated connections services.\n\nCITYWORKS report listing all Construction Lifecycle Work Orders for customer initiated works in FY 14/15. "]
[null,"Commercial/Industrial","NF",null,"E","VELOCITY billing database","Report listing all basic connections, initial service to blocks & move service from OH to UG. Data provided for all volume of commercial and industrial underground and overhead connection construction Life cycle work orders in FY 14/15 (> 100A connections with LV reticulation works)\n\nData provided for all volume of commercial and industrial underground and overhead connection with HV works construction Life cycle work orders in FY 14/15 (> 100A connections with HV & LV reticulation works)\n\nComplex connection HV ( Customer connected at LV with minor HV works):  Data provided for all volume of commercial and industrial underground and overhead connection with HV works construction Life cycle work orders in FY 14/15 (> 100A connections with HV & LV reticulation works)        \n\nFilters in the City Works & Velocity data spread sheets were applied to get the number of connections in this respective category.\n\nNote: The data reported against services does not include negotiated connections services. "]
[null,"Subdivision","NF",null,"E","VELOCITY billing database","Data provided for all subdivisions installed in FY 14/15; underground and overhead volumes. All subdivisions were underground, so summation of report listed in underground connections field.\nData provided for breakdown of subdivision Construction Life Cycle work orders in FY 14/15 (complex HV with no upstream asset works, complex HV with upstream asset works). \n\nNote: The data reported against services does not include negotiated connections services. "]
[null,"Embedded Generation","NF",null,"E","VELOCITY billing database","The data is based upon an assumption that residential PV is excluded where no connections works has been required."]
["TABLE 2.5.2 - COST METRICS BY CONNECTION CLASSIFICATION"]
[{"$f":"'[1]4. Assets (RAB)'!B17","v":"For overhead network assets less than 33kV:"}]
[null,"All sub-categories below","F",null,"A","ORACLE Project Accounting\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nFARMER database","FINANCIAL: Total cost of customer connections is taken from ORACLE accounts (actual data).  Projects that did not include a new connection (relocation or replacement of existing services etc) have been excluded - these are reported as Quoted services in the RIN.  Small residential PV systems are also not reported in the figures here - as these are not a new connection.\nEach project has been categorised as to the type of customer (residential, C/I, subdivision, embedded generator) according to ORACLE project categories and inspection of project title.  Projects further categorised according to project type (simple / complex, HV LV etc) according to the split of capitalised assets in the fixed asset register, and OH/UG connections according to whether OH or UG capitalised amount is greater.  \n\nThe expenditure on different asset types has been determined from the fixed asset register, assuming the expenditure on each asset type (substation, HV and LV) is the same for each year on the project (i.e. the capitalisation data does not show whether there was expenditure on HV in year 1 and subs in year 2 of the project - we have assumed the same proportional expenditure on each asset type for each year of the project).\n\nThe totals reported in the RIN are calculated by summating total expenditure by year, asset type or connection type filtered according to the criteria contained in the RIN table and definitions.  HV and LV circuit km added have been estimated based on typical per unit rates, using ActewAGL unit rates for HV and LV feeders (audited by SKM).\n\nConnection volumes for basic (simple) connections have been extracted from the Farmer system used by ActewAGL for works management of connections.  3.4% of basic connections assumed to be Commercial/Industrial.  For complex connections, each project has a unique project number, and volumes are taken from a count of projects within the appropriate categories."]
[null,"Residential","F",null,"A"]
[null,"Commercial/Industrial","F",null,"A"]
[null,"Subdivision","F",null,"A"]
[null,"Embedded Generation","F",null,"A"]
["2.6 NON NETWORK EXPENDITURE"]
["TABLE 2.6.1 NON-NETWORK EXPENDITURE"]
[null,"IT & Communications","F",null,null,"ORACLE Project Accounting","Project data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types.  All relevant project types (IT Systems, Motor Vehicles, Buildings & other non network assets) are reported for opex & capex."]
[null,null,"NF"]
[null,"Motor Vehicles","F",null,"A","ORACLE Project Accounting","Project data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types.  All relevant project types (IT Systems, Motor Vehicles, Buildings & other non network assets) are reported for opex & capex. The breakdown of vehicles types are based on the allocation of total finance & operating leases (2013/14) for operating expenditure & for capital expenditure total finance lease expenditure for 2014/15 was used."]
[null,"Motor Vehicles","NF"," ","A","Refer to attached worksheets","x"]
[null,"Buildings and Property","F",null,null,"ORACLE Project Accounting","Project data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types.  All relevant project types (IT Systems, Motor Vehicles, Buildings & other non network assets) are reported for opex & capex."]
[]
[null,"Other","F",null,"X","X","X"]
[]
["TABLE 2.6.2 ANNUAL DESCRIPTOR METRICS - IT & COMMUNICATIONS EXPENDITURE"]
[null,"IT & Communications","F",null,"A","HR systems","The number of employees for ActewAGL Distribution includes corporate FTE's that support distribution. A more accurate method for this measure is to record the Energy Networks division."]
["TABLE 2.6.3 ANNUAL DESCRIPTOR METRICS - MOTOR VEHICLES"]
[null,"Motor Vehicles","F",null,"Actual","Toyota Fleet Management Online","Information was taken from fuel reports available on Toyota Fleet Management Online for the financial period of July 2014 to June 2015. The information gathered shows how many kms were travelled for vehicles using the odometer reading put in manually by the drivers. If no fuel was used, an odometer reading was taken from TFM online. If a vehicle has been replaced, both the original and the replacement may show on the report as vehicles are not taken off and put on road on the same day and there is sometimes a cross over period. Because of this, we have counted the amount of vehicles for the year as the amount that were recorded on the fuel spreadsheets to keep with the consistency of the data. \n\nA recent change of leases from operating to finance was undertaken for ActewAGL Distribution.  They were all finalised by end of financial year but counted as operating lease for 14/15 financial year as the new lease didn't take effect until July 2015. \n\nNote: The percentage split for vehicles is based on 2 EWP and 5 light vehicles working on the streetlight contract work."]
["2.7 VEGETATION MANAGEMENT"]
["TABLE 2.7.1 - DESCRIPTOR METRICS BY ZONE (Refer to row 337 for legislative obligations)"]
[null,"Zone 1"]
[null,"Route Line Length",null,null,null,"CA RIN worksheet 5.2 Asset Age Profile","Assumes that there is no double circuit on the same pole and assume that there is minimal HV and LV lines and the same pole. Note: ACT network design is very different to other Australian utilities. Urban LV overhead lines are backyard reticulated. While the HV lines are along the street outside of the customer properties.\nAs a result, the number of HV + LV run along the same pole is minimal. And therefore assume the route line length is the overhead electric line.\n"]
[null,"Number of maintenance spans (0's)",null,null,null,"Calculated from spreadsheet","x"]
[null,"Total length of maintenance spans (KM)",null,null,"E","ArcFM GIS database","Average urban span length is 60m. Average urban span length excludes services x Number of maintenance span"]
[null,"Length of vegetation corridors (KM)",null,null,"E","ArcFM GIS database","Assume urban 80% have vegetation"]
[null,"Average number of trees per maintenance span (0's)",null,null,"A","Calculated from spreadsheet","Number of Trees divided by Number of maintenance span"]
[null,"Average frequency of cutting cycle (years)",null,null,null,"ActewAGL Vegetation Management Plan","Yearly in BFM and 3 yearly in the urban. Using data captured in the aerial flight: \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\Vegetation\\Vegetation.xlsx"]
[null,"Zone 2"]
[null,"Route Line Length",null,null,null,"CA RIN worksheet 5.2 Asset Age Profile","Asset Quantity should be aligned with 5.2 age profile. Average urban span length is 60m."]
[null,"Number of maintenance spans (0's)",null,null,null,"Calculated from spreadsheet","Rural vegetation includes lines in BFM area & transmission"]
[null,"Total length of maintenance spans (KM)",null,null,null,"Calculated from spreadsheet","Average urban span length excludes services x Number of maintenance span"]
[null,"Length of vegetation corridors (KM)",null,null,null,"ActewAGL Bushfire Management Plan","Yearly in BFM and 3 yearly in the urban. Using data captured in the aerial flight: \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\Vegetation\\Vegetation.xlsx"]
[null,"Average number of trees per maintenance span (0's)",null,null,null,"Calculated from spreadsheet","Number of Trees divided by Number of maintenance span"]
[null,"Average frequency of cutting cycle (years)","NF",null,"A","ActewAGL Vegetation Management Plan","x"]
["TABLE 2.7.2 - EXPENDITURE METRICS BY ZONE"]
[null,"Zone 1","F",null,null,"ORACLE Project Accounting","Projects are mapped directly to each defined category."]
[null,null,"NF",null,null,null,"Using data captured in the aerial flight : \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\Vegetation\\Vegetation.xlsx"]
[null,"Zone 2","F",null,null,"ORACLE Project Accounting","Projects are mapped directly to each defined category."]
[null,null,"NF",null,null,null,"Using data captured in the aerial flight : \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\Vegetation\\Vegetation.xlsx"]
["TABLE 2.7.3 - DESCRIPTOR METRICS ACROSS ALL ZONES - UNPLANNED VEGETATION EVENTS"]
[null,"Number of fire starts caused by vegetation grow-ins (DNSP responsibility)","NF",null,"A","Guardian (Safety Management software)","No fire incidents shown in Guardian"]
[null,"Number of fire starts caused by vegetation blow-ins and fall-ins (DNSP responsibility)","NF",null,"A","Guardian (Safety Management software)","No fire incidents shown in Guardian"]
[null,"Number of fire starts caused by vegetation grow-ins (other party responsibility)","NF",null,"A","Guardian (Safety Management software)","No fire incidents shown in Guardian"]
[null,"Number of fire starts caused by vegetation blow-ins and fall-ins (other party responsibility)","NF",null,"A","Guardian (Safety Management software)","No fire incidents shown in Guardian"]
["Worksheet 2.8 - MAINTENANCE"]
["TABLE 2.8.1 - DESCRIPTOR METRICS FOR ROUTINE AND NON-ROUTINE MAINTENANCE"]
[null,"Pole top, overhead line & service line maintenance","NF",null,"A","CA RIN worksheet 5.2 Asset Age Profile\n\n\n\n\nCITYWORKS operations database\n\n","The asset inspection strategy has changed in FY14/15. All urban poles are now inspected every 5 years. All rural poles are now inspected every 2 years from the ground and 2 years from the air. Therefore, all rural poles are inspected every year. This has changed from last year and there should be a reduction of inspection as a result this year. Average age is taking the weighted average for the numbers in 5.2.\n\nPole inspection: Ground inspection + Aerial inspection.\n11183 + 4320 = 15503\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_8 Maintenance\\Data.xlsx\n\nService Line: Number of services based on the pole inspection from CityWorks.\nFilter by the poles inspected in FY14/15. \nThen summate all the number of services recorded in the pole inspection.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_8 Maintenance\\Data.xlsx\n\nInspection Cycle:\nPole Top: 2 years in rural/ 3 years in urban\nPoles: 5 years in urban/2 years in rural\nService line: 5 years in urban/2 years in rural"]
[null,"Pole inspection and treatment","NF",null,"A","CA RIN worksheet 5.2 Asset Age Profile.\n\nCITYWORKS operations data\n","Asset Quantity should be aligned with 5.2 age profile.\nAverage age is taking the weighted average for the numbers in 5.2.\nOnly ground inspection and the maintenance of pole is counted. \nGround inspection data is from CityWorks which includes the transmission pole inspections. = 11183.\nPole maintenance are from the CityWorks extract. The filter used is actual completed work order in FY14/15, under 17560036 & 17560122, filter by Construction Overhead Works and previous legacy WASP carry over WO \"WO# - Administration\", Pole Maintenance description \"Urban or Rural Pole Defect Repair\". = 430.\n= 11183 + 430 = 11613\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_8 Maintenance\\Data.xlsx\n"]
[null,"Overhead asset inspection","NF",null,"E","CA RIN worksheet 5.2 Asset Age Profile\n\n","Asset Quantity aligned with CA RIN worksheet 5.2 Asset Age Profile. Average line length for line patrol = 6.945 km\nAverage line span = 60m.\nInspection Cycle - For lines there are multiple inspection methodologies as follows:\n-        the thermovision which is on selected lines at yearly or two-yearly Winter and Summer seasonal cycles\n-        the aerial patrols on the rural lines on a two yearly cycle \n-        the ground inspections on the rural lines on a two yearly cycle\n-        urban HV lines on a three yearly cycle\n-        the transmission lines on a yearly cycle. \nAverage age is taking the weighted average for the numbers in 5.2.\nLine reactive patrol # of line patrol x average line length (6.945x114) 791.73. This is an estimate.\nThermovision; based on feeder overhead line length 307.97km. It takes the feeder that has thermovision surveyed multiply by the total overhead line length for the feeder (ArcFM). This is an actual.\nAerial Inspection line 822. This is an actual number.\nGround Patrol  Ground Patrol (11183 x 60m) 670.98. This is an estimate.\n"]
[null,"Network underground cable maintenance: by voltage","NF",null,"A","CA RIN worksheet 5.2 Asset Age Profile\n\nORACLE Project data\n\n\n\n\nPole maintenance workbook","There is no routine condition monitoring of underground cables. Only selective section of several feeders are condition assessed. Average age is taking the weighted average for the numbers in 5.2.\n17560010 UG Unplanned 433 m Repairs; from ORACLE data filtering by the low voltage and high voltage cable materials. Filter out all building wire, SDI and service cables. (Actual)\n17560128 UG FR&E 444 m Repairs; from ORACLE data filtering by the low voltage and high voltage cable materials. Filter out all building wire, SDI and service cables. (Actual)\nUG Condition Monitoring 2342 m condition assessment, based on test result.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_8 Maintenance\\Data.xlsx"]
[null,"Network underground cable maintenance: by location","NF",null,"A","CA RIN worksheet 5.2 Asset Age Profile\n\nORACLE Project data\n\n\n\n\nPole maintenance workbook","There is no routine condition monitoring of underground cables. Only selective section of several feeders are condition assessed. Average age is taking the weighted average for the numbers in 5.2.\n17560010 UG Unplanned 433 m Repairs; from ORACLE data filtering by the low voltage and high voltage cable materials. Filter out all building wire, SDI and service cables. (Actual)\n17560128 UG FR&E 444 m Repairs; from ORACLE data filtering by the low voltage and high voltage cable materials. Filter out all building wire, SDI and service cables. (Actual)\nUG Condition Monitoring 2342 m condition assessment, based on test result.\n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\2_8 Maintenance\\Data.xlsx"]
[null,"Distribution substation equipment & property maintenance","NF",null,"A","CITYWORKS operations database","x"]
[null,"Zone substation equipment maintenance","NF",null,"A","CITYWORKS operations database/ORACLE database\n","Maintenance work stems from zone assets inspection (carried out on monthly basis). Minor maintenance works such as oil leak repair and general cleaning works, silica gel (breather) bottle replacements, weatherproof colour coating included under this category. Zone Transformers and Neutral Earthing Transformer asset registers have been used to determine average age of the asset group. CityWorks maintenance data extract used for this reporting purpose. Financial records confirmed the maintenance works on these assets. "]
[null,"Zone substation property maintenance","NF",null,"A","ArcFM GIS database/CITYWORKS operations database/ORACLE database ","This category includes maintenance works such as ZS property, building and yard maintenance. Maintenance work stems from zone assets inspection (carried out on monthly basis). Operational and maintenance works such as ZS rates and bills, graffiti removal, oil interceptor tanks inspection(s), property maintenance, gardening & cleaning considered under this category. CityWorks maintenance data extract and Oracle expenditure export used for this reporting purpose. Financial records confirmed the maintenance works on these assets. No new zone substation built during FY14-15\n"]
[null,"Public lighting maintenance","x",null,"N/A","ActewAGL Distribution does not own the streetlight network in the ACT","x"]
[null,"SCADA & network control maintenance","NF",null,"A","No maintenance performed on these equipment due to self monitoring feature","x"]
[null,"Protection systems maintenance","NF",null,"A","Spreadsheet 2.8.1 BOP Protection Maintenance Data","The data for protection maintenance has been obtained from the Relay Test Instruction( RTI) database. This database comprises of all the protection relays( both zone substation and distribution substation) in the ActewAGL network with its last maintained date. The last maintained date is assigned as and when a field protection specialist carries out maintenance works on the assets. Usually, the next maintenance date is three years hence for zone substation assets and five years for distribution substations assets. The RTI database has been queried for all assets that has been maintained in the calendar year July 2014 to June 2015. It has produced a database of 386 secondary protection devices that have been maintained."]
[null,"Sub transmission asset maintenance - for DNSPs with dual function assets","NF",null,"A","x","ActewAGL Distribution is now also licensed in the ACT as a TNSP. All our assets that were previously classed as sub-transmission will now be transmission assets based on the function they perform."]
[null,"Various assets","x",null,"N/A","x","x"]
[null,"Ground clearance - access tracks","x",null,"N/A","x","x"]
[null,"Other","x",null,"x","x","x"]
["TABLE 2.8.2 - COST METRICS FOR ROUTINE AND NON-ROUTINE MAINTENANCE"]
[null,"All sub-categories below","F",null,"A","ORACLE Project Accounting","FINANCIAL: No Adjustments\nProject data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types.  All maintenance activities are categorised into AER categories that best fit the description. "]
[null,"Pole top, overhead line & service line maintenance","F",null,"A"]
[null,"Pole inspection and treatment","F",null,"A"]
[null,"Overhead asset inspection","F",null,"A"]
[null,"Network underground cable maintenance: by voltage","F",null,"A"]
[null,"Network underground cable maintenance: by location","F",null,"A"]
[null,"Distribution substation equipment & property maintenance","F",null,"A"]
[null,"Zone substation equipment maintenance","F",null,"A"]
[null,"Zone substation property maintenance","F",null,"A"]
[null,"Public lighting maintenance","F",null,"A"]
[null,"SCADA & network control maintenance","F",null,"A"]
[null,"Protection systems maintenance","F",null,"A"]
[null,"Sub transmission asset maintenance - for DNSPs with dual function assets","F",null,"A"]
[null,"Various assets","F",null,"A"]
[null,"Ground clearance - access tracks","F",null,"A"]
[null,"Other","F",null,"A"]
["Worksheet 2.9 - EMERGENCY RESPONSE"]
["TABLE 2.9.1 - EMERGENCY RESPONSE EXPENDITURE (OPEX)"]
[null,"Total Emergency Response Expenditure","F",null,"A","ORACLE Project Accounting","No Adjustments\nProject data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types.  All maintenance activities are categorised into AER categories that best fit the description. "]
[null,"Major Events O&M Expenditure","F",null,"A"]
["2.10 OVERHEADS"]
["TABLE 2.10.1 - NETWORK OVERHEADS EXPENDITURE"]
[null,"Total Overhead Expenditure - Standard Control Services","F",null,"A","ORACLE general ledger","Activity data comes from ORACLE GL ATB  is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Activities relevant to overheads are entered excluding maintenance.  The current activity structure is mapped to the AER structure. For TABLE 2.10.2 Activity data comes from ORACLE GL ATB  is uploaded into TM1 & these figures are then adjusted for depreciation in the corporate charges. Corporate overheads are then separated into the following categories by the activity split of Standard Control operating/capital expenditure, Unregulated & Alternative control services."]
[null,"Total Overhead Expenditure - Alternative Control Services","F",null,"A"]
[null,"Total Overhead Expenditure - Negotiated Services","F",null,"A"]
[null,"Total Overhead Expenditure - Unregulated Services","F",null,"A"]
[null,"Capitalised Overheads - Standard Control Services","F",null,"A"]
["TABLE 2.10.2 - CORPORATE OVERHEADS EXPENDITURE"]
[null,"Total Overhead Expenditure - Standard Control Services","F",null,"A","ORACLE general ledger","Activity data comes from ORACLE GL ATB  is uploaded into TM1 & these figures are then adjusted for depreciation in the corporate charges. Corporate overheads are then separated into the following categories by the activity split of Standard Control operating/capital expenditure, Unregulated & Alternate control services."]
[null,"Total Overhead Expenditure - Alternative Control Services","F",null,"A"]
[null,"Total Overhead Expenditure - Negotiated Services","F",null,"A"]
[null,"Total Overhead Expenditure - Unregulated Services","F",null,"A"]
[null,"Capitalised Overheads - Standard Control Services","F",null,"A"]
["Worksheet 2.11 - LABOUR"]
["Table 2.11.1 - COSTS METRICS PER ANNUM"]
[null,"Corporate Overheads - Internal labour costs","F",null,"A","AURION, ORACLE Project Accounting"]
[null,"Network Overheads - Internal labour costs","F",null,"A","AURION, ORACLE Project Accounting","Labour ($) - The numbers were sourced from the current payroll system and reconciled back to Salary and Wages including Applied Payroll Costs in the General Ledger as per RIN guidelines. Where variances arose between the numbers in the AAG_salary cube and the General Ledger, the variance was appropriately apportioned (using weighting) over each of the categories to ensure that the numbers matched back to what was in the General Ledger.  To ensure that the above is representative only of salary and wages for Standard Control, an adjustment was made to the direct labour categories to take into account Non-Standard Control services i.e. metering. The total salary and wage costs for non-standard control services were appropriately apportioned (weighted) over the respective Direct categories and subtracted. The classifications were based on their classification levels as set out in ActewAGL's current Enterprise Bargaining Agreement (EBA). \nFTE's - The information above has been taken from the AAG_salary cube for 2014/15. To ensure that the above is representative only of FTE's for Standard Control, an adjustment was made to the direct FTE categories to take into account Non-Standard Control services i.e. metering. The total FTE's for non-standard control services were appropriately apportioned (weighted) over the respective Direct categories and subtracted. \nProductive work hours -  The information above has been primarily sourced from the labour productivity cube (which is sourced direct from timesheets entered into ORACLE) and the AAG_salary cube. Normal labour hours have been adjusted for all types of leave occurrences. "]
[null,"TOTAL Direct Network Labour - Internal labour costs","F",null,"A","As above","As above"]
["Table 2.11.2 - EXTRA DESCRIPTOR METRICS FOR CURRENT YEAR"]
[null,"Corporate Overheads - Internal labour costs","F",null,"A","AURION, ORACLE Project Accounting"]
[null,"Network Overheads - Internal labour costs","F",null,"A","AURION, ORACLE Project Accounting","Labour ($) - The numbers were sourced from the current payroll system and reconciled back to Salary and Wages including Applied Payroll Costs in the General Ledger as per RIN guidelines. Where variances arose between the numbers in the AAG_salary cube and the General Ledger, the variance was appropriately apportioned (using weighting) over each of the categories to ensure that the numbers matched back to what was in the General Ledger.  To ensure that the above is representative only of salary and wages for Standard Control, an adjustment was made to the direct labour categories to take into account Non-Standard Control services i.e. metering. The total salary and wage costs for non-standard control services were appropriately apportioned (weighted) over the respective Direct categories and subtracted. The classifications were based on their classification levels as set out in ActewAGL's current Enterprise Bargaining Agreement (EBA). \nFTE's - The information above has been taken from the AAG_salary cube for 2014/15. To ensure that the above is representative only of FTE's for Standard Control, an adjustment was made to the direct FTE categories to take into account Non-Standard Control services i.e. metering. The total FTE's for non-standard control services were appropriately apportioned (weighted) over the respective Direct categories and subtracted. \nProductive work hours -  The information above has been primarily sourced from the labour productivity cube (which is sourced direct from timesheets entered into ORACLE) and the AAG_salary cube. Normal labour hours have been adjusted for all types of leave occurrences. "]
[null,"TOTAL Direct Network Labour - Internal labour costs","F",null,"A","AURION, ORACLE Project Accounting","As Above"]
["Worksheet 2.12 - INPUT TABLES"]
[null,"Vegetation Management","F",null,"A","AURION,  ORACLE Project Accounting","Data from each financial template are broken up by the categories of labour, materials, contract payments & other costs. For each templates projects are broken down into these categories using the financial statements from ORACLE & TM1 and copied into the input sheet."]
[null,"Routine Maintenance","F",null,"A"]
[null,"Non-Routine Maintenance","F",null,"A"]
[null,"Overheads","F",null,"A"]
[null,"Augmentation","F",null,"A"]
[null,"Connections","F",null,"A"]
[null,"Emergency Response","F",null,"A"]
[null,"Public Lighting","F",null,"A"]
[null,"Metering","F",null,"A"]
[null,"Fee-Based Services","F",null,"A"]
[null,"Quoted Services","F",null,"A"]
[null,"Replacement","F",null,"A"]
[null,"Non-Network Expenditure","F",null,"A"]
["Worksheet 4.1 - PUBLIC LIGHTING"]
["Table 4.1.1 - DESCRIPTOR METRICS"]
[null,"Population of Lights","NF",null,"A","ActewAGL Distribution does not own the streetlight network in the ACT.","x"]
["Table 4.1.2 - DESCRIPTOR METRICS ANNUALLY (Service/Service Quality - Volumes and Expenditure)"]
[null,"Light Installation","NF",null,"A","ActewAGL Distribution does not own the streetlight network in the ACT.","x"]
[null,"Light Replacement","NF",null,"A"]
[null,"Light Maintenance","NF",null,"A"]
[null,"Quality of Supply","NF",null,"A"]
["Table 4.1.3 - COST METRICS"]
[null,"Light Installation - Major Road","F",null,"A","ActewAGL Distribution does not own the streetlight network in the ACT.","x"]
[null,"Light Installation - Minor Road","F",null,"A"]
[null,"Light Replacement - Major Road","F",null,"A"]
[null,"Light Replacement - Minor Road","F",null,"A"]
[null,"Light Maintenance - Major Road","F",null,"A"]
[null,"Light Maintenance - Minor Road","F",null,"A"]
[null,"Quality of Supply","F",null,"A"]
["Worksheet 4.2 - METERING"]
["Table 4.2.1 - METERING DESCRIPTOR METRIC"]
[null,"Meter Type 4","NF",null,"A","VELOCITY billing database","Data was generated from Velocity into a spreadsheet. Then, using SQL's, the data was counted using different categories."]
[null,"Meter Type 5","NF",null,"A"]
[null,"Meter Type 6","NF",null,"A"]
["Table 4.2.2 - COST METRICS"]
[null,"Meter purchase","F",null,"A","ORACLE Project Accounting","FINANCIAL: \n\nProject data from ORACLE is uploaded into TM1 by expense type. \nCorporate overheads are excluded from the calculations.\nProjects are categorised by project types.\nAll metering related types are picked up and entered into the template.\nAll commercial projects have been entered as type 5 & domestic as type 6 where data for type 5 is unknown invoices from contractors are used to complete.\n\nNON-FINANCIAL:\n\nPurchase Order summary for purchased meters obtained from Supply Centre."]
[null,"Meter testing","F",null,"A"]
[null,"Meter investigation","F",null,"A"]
[null,"Scheduled meter reading","F",null,"A"]
[null,"Special meter reading","F",null,"A"]
[null,"New meter installation","F",null,"A"]
[null,"Meter replacement","F",null,"A"]
[null,"Meter maintenance","F",null,"A"]
[null,"Remote meter reading","F",null,"A"]
[null,"Remote meter re-configuration","F",null,"A"]
[null,"Other metering","F",null,"A"]
[null,"IT infrastructure Capex","F",null,"A"]
[null,"IT infrastructure Opex","F",null,"A"]
[null,"Communications infrastructure Capex","F",null,"A"]
[null,"Communications infrastructure Opex","F",null,"A"]
["Worksheet 4.3 - ANCILLARY SERVICES - FEE BASED SERVICES"]
["Table 4.3.1 - Cost Metrics for Fee-based Services"]
[null,"Common fee Based Services - Energisation","F",null,"A","ORACLE Project Accounting/Velocity billing database","FINANCIAL: \nProject data from ORACLE is uploaded into TM1 by expense type.\nCorporate overheads are excluded from the calculations.\nProjects are categorised by project types.\nNon financial data (volumes) comes from Velocity & ORACLE receivables.\nVolumes are calculated by dividing total revenue by price & number of work orders were relevant."]
[null,"Common fee Based Services - De-Energisation","F",null,"A"]
[null,"Common fee Based Services - Re-Energisation","F",null,"A"]
[null,"Miscellaneous Fee Based Services","F",null,"A"]
["Worksheet 4.4 - ANCILLARY SERVICES - QUOTED SERVICES"]
["Table 4.4.1 - Cost Metrics for Quoted Services"]
[null,"Quoted Services","F",null,"A","ORACLE Project Accounting","Project data from ORACLE is uploaded into TM1 by expense type. Corporate overheads are excluded from the calculations.  Projects are categorised by project types. Non financial data (volumes) comes number of work orders."]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
[null,null,"F",null,"A"]
["Worksheet 5.2 - ASSET AGE PROFILE"]
["Table 5.2.1 - Asset Age Profile"]
[null,"Poles by: Highest operating voltage; Material Type;  Staking (if wood)","NF",null,"A","ArcFM GIS system\n","1. Find all poles (Transmission and Distribution) that are in service and owner AAD.  Due to data error, poles classified wrongly as streetlight only poles, are also included but; \n2. If Commission date missing use Manufacturer date, if manufacturer date missing, classified as missing year.\n3. If commission year is 1900, classified as missing year (that’s the database default minimal which is similar as null)\n4. Intersect (within 2 meter range, except OverheadTransmissionLine which use 10m range) poles with cables and conductors (HV, LV, transmission).  Each pole may have many intersection. \n5. Get the max voltage of the line for each pole. \n6. For any pole that doesn’t have an intersection, if the assetnum start with POL, then it is LV. \n7. Material mapping rules \ncase when Material in ('CREOSOTE', 'NATURALROUNDTIM' , 'TANALITH') then 'Wood'\nwhen Material in ( 'STOBIE' , 'UNKNOWN' , NULL) then 'Other'\nelse Material end\n8. For asset with 1900 commission year, use the suburb year. \n9. Provide the final output group by financial year.  \\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_Poles_with_SL_only_poles_Prod_1.xlsx"]
[null,"Pole Top Structures by: Highest Operating Voltage","NF",null,null,"ArcFM GIS system","x"]
[null,"Overhead Conductors by: \nHighest Operating Voltage; Number of Phases (at HV)","NF",null,"A","ArcFM GIS system","1. Find all OH Conductors that are in service and owner AAD.   \n2. If Commission date missing use Manufacturer date, if manufacturer date missing, classified as missing year.\n3. If commission year is 1900, classified as missing year (that’s the database default minimal which is similar as null)\n4. For asset with 1900 commission year, use the suburb year. \n5. If the Conductors  is HV & commission Financial year is still 1900 or 1995, we use the minimum (exclude 1900) commission year of the other HV Conductors  of the same feeder\n6. Provide the final output group by financial year. \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_OH_Conductor_feeder_year_update gazettal year Prod STLength.xlsx"]
[null,"Underground Cables by: Highest Operating Voltage","NF",null,"A","ArcFM GIS system","1. Find all UG Cables that are in service and owner AAD.   \n2. If Commission date missing use Manufacturer date, if manufacturer date missing, classified as missing year.\n3. If commission year is 1900, classified as missing year (that’s the database default minimal which is similar as null)\n4. For asset with 1900 commission year, use the suburb year. \n5. If the UG Cables is HV & commission Financial year is still 1900 or 1995, we use the minimum (exclude 1900) commission year of the other UG Cables of the same feeder\n6. Provide the final output group by financial year. System length is used. \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_UG_Cable_Prod update gazettal year STLength feeder year.xlsx"]
[null,"Service Lines by: Connection Voltage; Customer Type; Connection Complexity","NF",null,"A","ArcFM GIS system","1. Find all Service line that are in service and owner AAD.   \n2. If Commission date missing use Manufacturer date, if manufacturer date missing, classified as missing year.\n3. If commission year is 1900, classified as missing year (that’s the database default minimal which is similar as null)\n4. For asset with 1900 commission year, use the suburb year. \n5. Provide the final output group by financial year. System length is used. \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_Serviceline_prod with update gazettal year_2.xlsx"]
[null,"Transformers by: \nMounting Type; Highest Operating Voltage; Ampere Rating; Number of Phases (at LV)","NF",null,"A","ArcFM GIS system","1. Find all transformer (DISTRIBUTIONTRANSFORMER and POWERTRANSFORMER) that are in service and owner AAD.   \n2. If Commission date missing use Manufacturer date, if manufacturer date missing, classified as missing year.\n3. If commission year is 1900, classified as missing year (that’s the database default minimal which is similar as null)\n4. Find all ELECTRICSUPPLYSITE and GroundMountedStructure.\n5. Join the result from step 1 and step 4. \n6. If the Transformer can join to ELECTRICSUPPLYSITE:\na. if it’s [SubTypeCD] = 80205 then it is ‘Pole Sub’. else, it is ‘'Ground Outdoor / Indoor Chamber Mounted'’\n7. If the Transformer can join to GroundMountedStructure, then it is ‘Kiosk Mounted’\n8. Phase rules \ncase when PhaseDesignation = 7 or PhaseDesignation = 1 then 'Multiple'\n  else 'Single' end \n9. For asset with 1900 commission year, use the suburb year. \n10. Provide the final output group by financial year. \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_Transformers_Prod.xlsx\nTransmission:\nArcFM database and CityWorks extracts used for this reporting purpose. \nZone Neutral Earthing Transformers (qty. 28) reported under Other as this field was not editable.\nAudits were carried out to ensure any assets replacement works.\n\n\n"]
[null,"Switchgear by: Highest Operating Voltage; Switch Function","NF",null,"A","ArcFM GIS database\n","ACT Government legislation specifies where the network boundary is through the Electricity Network Boundary Code.  The service line is part of the utility network; therefore the pillar/pit fuses will be protecting/isolating the service line that is part of the network and therefore are switchgear - not connection assets. The network boundary is at the house end of the service line – there is a useful diagram in the ActewAGL Distribution Electrical Safety Rules (Blue book) page 89. Those rules are approved by the ACT Technical Regulator and AAD must conform to them. Therein lies a major difference between AAD and other states DNSPs utilising electrical contractors to install services. For AAD, the local Technical Regulator and the ICRC specify network boundaries. Accordingly, it requires the network boundary to be at the house/meter connection rather than the property boundary. Hence, AAD assets include the pillars, mini-pillars, etc up to the Point of Attachment or the meter box as part of ActewAGL's Regulated Asset Base. \n\n1. Find all Fuse (exclude subtype 30502, 30505, 30508), Switch (exclude subtype 30606, 30608), Circuit Breaker, Recloser that are in service and owner AAD, and can be linked to a switchgear.    \n2. Classify the AER type (reclose as CIRCUITBREAKER, Fuse 30506 or 30507 as Switch)\n3. Find all ELECTRICSUPPLYSITE and GroundMountedStructure.\n4. Join result step 1 (switchgear can link to ELECTRICSUPPLYSITE and GroundMountedStructure) with step 3, using either ELECTRICSUPPLYSITEUID or GroundMountedStructureUID. \n5. If a switchgear has more than 1 components and they are of the different date, use the min minimal date to apply to all other components.\n6. If a unit commission year is 1900, use switchgear commission year ( or manufacturer year in the case that Commission date missing).  \n7. If a unit commission year is 1900, use ELECTRICSUPPLYSITE  or GroundMountedStructure commission year ( or manufacturer year in the case that Commission date missing).  \n8. For asset with 1900 commission year, use the suburb year. \n9. Provide the final output group by financial year. \n\\\\jeeves\\AssetPerformance\\Network Performance\\Regulator\\RIN\\CAT 201415\\5_2 Age Profile\\Final Working\\AER_Switchgear_prod with update gazettal year (2).xlsx\n\nTransmission:\nZone Neutral Earthing Transformers reported under Other as this field was not editable.\nAudits were carried out to ensure any assets replacement works. ArcFM database and CityWorks extracts used for this reporting purpose. \n11kV, 66kV & 132kV Circuit Breaker asset registers have been used to determine average age of the asset group. No new assets added during FY14-15 under 11kV & 66kV circuit breaker & IES category hence input provided under \"> 66 kV & < = 132 kV  ; Circuit Breaker\" category only.\nFinancial records confirmed no replacement works on these assets."]
[null,"Public Lighting by: Asset Type; Lighting Obligation","x",null,"x","x","x"]
[null,"SCADA, Network Control and Protection Systems by: Function","NF",null,"A","Refer to spreadsheets:\n5.2.1 BOP Asset Age profile Protection\n5.2.1 DDRN Radio ArcFM Data\n5.2.1 RTU ArcFM Data","The data for both protection, communication assets and RTU has been obtained from ActewAGL's geographical information system, ArcFM. From ArcFM database, an excel spreadsheet has been derived that acts as a master database for providing information relating to asset count and age profile. Newer assets that are not included in ArcFM, have been included manually for protection relays. The count does not include protection and RTU assets that are not in service. The age profile of the field devices has been obtained by calculating an average age of assets installed over a period of time inclusive of the year 2015 in the network."]
[null,"Other by: DNSP defined","x",null,"x","x","x"]
["Worksheet 5.3 - MAXIMUM DEMAND AT NETWORK LEVEL"]
["TABLE 5.3.1 - RAW AND WEATHER CORRECTED COINCIDENT MD AT NETWORK LEVEL - (Summed at transmission connection point)"]
[null,"Raw network coincident MD","NF",null,"A","MD information sourced from SQL Reporting - Network Peak Demand Report","Weather corrected/normalisation methodology: Monte Carlo Residual Simulation "]
[null,"Date MD occurred","NF",null,"A",null,"1) Collect raw data* to run weather corrected regression such as Seasonal daily MDs of the year (the season where peak demand occurs, e.g.. \"Winter\" or \"Summer\") and its corresponding HDD** or CDD and Holiday status (\"1\" for weekend and public holiday, \"0\" for business day."]
[null,"Half hour time period MD occurred","NF",null,"A","Weather Data from Bureau of Meteorology","2) Run linear regression in R and feed its results (regression coefficients and Residual standard error) into simulation model as show below:"]
[null,"Winter/summer peaking","NF",null,"A",null,"3) Run Monte Carlo Simulation via the model with input of past 25 years of weather data and holiday status inform. Total of 60,000 annual MD simulation results should be created at the end of simulation. (See template for details)"]
[null,"Embedded generation","NF",null,"A",null,"4) Calculate 50% POE and 10% POE based on the simulation results from Step 3. \n      50% POE = 50th Percentile of Simulation Results; 10% POE = 90th Percentile of Simulation Results"]
[null,"Weather corrected (10% POE) network coincident MD","NF",null,"E",null,"* The raw unadjusted maximum demand data has been used.\n** CDD = Max(0, Daily  Average Temperature - 18.5oC); HDD = Max(0, 18.5oC - Daily Average Temperature)."]
[null,"Weather corrected (50% POE) network coincident MD","NF",null,"E",null,"**Denote: C0 = Intercept; C1= Coefficient of HDD or CDD; C2 = Coefficient of Holiday Status; σt = Residual standard error"]
["Worksheet 5.4 - MAXIMUM DEMAND and UTILISATION AT SPATIAL LEVEL"]
["TABLE 5.4.1 - NON-COINCIDENT & COINCIDENT MAXIMUM DEMAND"]
[null,"Sub-transmission Substation","NF",null,"E","VELOCITY billing database\n","1) Weather corrected/normalisation methodology: Monte Carlo Residual Simulation (see 5.3.1)\n2) Power Factor (PF) estimation: No MVAR data for Williamsdale, so Canberra Sub's PF at time of peak is assumed for MW to MVA conversion.\n3) Sub-transmission/Zone Substation Weather Corrected Coincident MD 50% POE and 10% POE calculation:\n\n\n\n4) Normal continuous ratings have been used and that ActewAGL does not use cyclic ratings.\n\nReport Name: Interval Reading Throughput\nLog into Velocity and following the below path:\nPath: Gentrack Launch Pad -> Operations -> Finance\n "]
[null,"Network Level - Zone Substation","NF",null,"E","Weather Data from Bureau of Meteorology","All methodology same as above. Note if Canberra Sub's PF is not available at time of peak, East Lake ZS' PF is considered as a substitute (for zone substations only). And the Queanbeyan power factor has been used for the Fyshwick power factor."]
["Worksheet 6.3 - SUSTAINED INTERRUPTIONS TO SUPPLY"]
["Table 6.3.1 - Sustained Interruptions to Supply"]
[null,"Multi Premises Outages","NF"," ","A","APPLY Outage database","Outage record includes substation number information. Substation number is mapped to a feeder using information from ENMAC. Each feeder is classified as Urban or Short Rural based on feeder length information from ArcFM (GIS) and maximum demand data from TrendSCADA to derive MVA/km rating. \n\nAll outage records are in the table, including planned outages and outages with duration <1 minute. The table is a combined list of all the records from the APPLY database and the TCS database for the whole financial year.\n"]
[null,"Single Premises Outages","NF"," ","A","TCS database","Outage record includes substation number information. Substation number is mapped to a feeder using information from ENMAC. Each feeder is classified as Urban or Short Rural based on feeder length information from ArcFM (GIS) and maximum demand data from TrendSCADA to derive MVA/km rating. \n\nAll outage records are in the table, including planned outages and outages with duration <1 minute. The table is a combined list of all the records from the APPLY database and the TCS database for the whole financial year."]
[]
[]
[]
[null,"VEGETATION MANAGEMENT EXPENDITURE"]
[null,"RIN 13.7 - Provide:\n\n• a list of regulations that impose a material cost on performing vegetation management (including bushfire mitigation regulations) and\n• a list of self imposed standards from the DNSP’s vegetation management program; and.\n• an explanation of the cost impact of regulations and self-imposed standards on performing vegetation management work.","Brief description"]
[null,"Emergencies Act 2004","A range of subordinate legislation has been created under the (parent) Emergencies Act 2004. Of relevance to ActewAGL are the following pieces of sub-ordinate legislation:\n- Emergencies (Emergency Plan) 2012 (No 1). This document forms the ACT Emergency Plan which outlines the principles of emergency management in the Territory,\n- Emergencies (Bushfire Abatement Zone) Declaration 2006. The instrument declares essentially all land outside the built up urban areas of the ACT as a bushfire abatement zone\n- Emergencies (ESA Incident Notification Procedure) Commissioner‘s Guidelines 2011."]
[null,"Environment Protection Act 1997 (ACT)","To protect and, where practicable, restore and enhance the quality of the environment through management of the environment as an integrated and dynamic whole.\n"]
[null,"Heritage Act 2004","Covers listed and potential places and objects of heritage significance, including aboriginal sites of significance. It requires any person who discovers a site of potential significance not to damage that site and to report it to the Heritage Council within five days, as well as ensuring that owners or occupiers of recognised heritage sites ensure that those sites are not damaged.\n"]
[null,"Nature Conservation Act 1980 (ACT)","This Act provides for the management and protection of native fauna and flora and the declaration and management of nature reserves in the Australian Capital. Territory. It also regulates certain activities in relation to some animals other than native animals.\n"]
[null,"Planning and Building Regulation 2008 ","The Act establishes a faster, simpler and more effective system of planning in the ACT. \n"]
[null,"Planning and Development Act 2007","Development in the ACT is controlled through the Planning and Development Act 2007 and Planning and Building Regulation 2008 and the Territory Plan 2008. With respect to the assessment of the potential environmental constraints of a site and the required planning approvals, the Planning and Development Act 2007 and Territory Plan establish specific criteria, which if met by a proposal, trigger the requirement for an Environmental Impact Statement (EIS) to be completed before the application can be assessed for planning approval.\n"]
[null,"Territory Plan 2008","The key statutory planning document in the ACT, providing the policy framework for the administration of planning in the ACT. The purpose of the Territory Plan is to manage land use change and development in a manner consistent with strategic directions set by the ACT Government, Legislative Assembly and the community.\n"]
[null,"Tree Protection Act 2005","The Tree Protection Act was introduced in 2005, and provides for the establishment of an ACT Tree Register across leased and unleased urban land that will identify and protect trees of exceptional value.\n","4.5.3. Safety Obligations "]
[null,"Utilities (Public Safety) Regulation 2001","The ACT Utility Networks (Public Safety) Regulation 2001 specifies prescriptive distances of clearance from utility assets.\n","4.7.8 Details of new regulatory obligations and costs\n\n\n"]
[null,"Utilities (Technical Regulation) Act 2014","Introduced in 2015 by the ACT Government to broaden the coverage of utilities activities.","4.7 Detail of new regulatory obligations and costs "]
[null,"Utilities Act 2000","The Utilities Act 2000 (ACT) is the key Act in the ACT that gives a utility service provider the power to own, operate and maintain an electricity distribution network in the ACT. It imposes a range of obligations on the providers of electricity distribution services, including significant information and reporting requirements. The Utilities Act also restricts the actions of utility service providers in some instances.\n","4.5.2 Technical Obligations"]
[null,"Utilities Service Licence","Under the terms of the Utility Services Licence, a utility operating in the ACT must comply with all applicable laws, codes of practice, guidelines or directions, and inform the ICRC of any material breaches of the licence or any applicable laws, codes of practice, guidelines or directions.\n","4.4 Categories of regulatory obligations"]
[null,"Electricity Service and Installation Rules Code","This code requires electricity distributors to develop service and installation rules that set out the requirements and associated obligations and procedures for the safe, reliable and efficient connection of electrical installations to an electricity network.\n"]
[null,"Emergency Planning Code 2011","The purpose of this code is to ensure a utility has in place appropriate procedures, structures and arrangements for preventing, anticipating and responding to emergency events and potential emergency events. Utilities must develop, maintain and implement emergency management procedures, develop annual review emergency plans, report to the chief executive on compliance with this Code and with emergency plans; and develop co-operative arrangements with other utilities or agencies.\n","4.5.3 Safety obligations"]
[null,"Management of Electricity Network Assets Code 2000","This code requires electricity distributors to design, construct, operate and maintain their electricity networks with reasonable care to avoid injury to any person or property.\n","4.5.3 Safety obligations"]