{"text_format":"1","workbook":"xlsx","n_sheets":16,"sheets":["2.1 Exp Summary","2.2 Repex","2.3(a)(b) Augex","2.5 Connections","2.6 Non-Network","2.7 Veg Management","2.8 Maintenance","2.9 Emergency Response","2.10(A) Overheads","2.11 Labour","2.12 Input Tables","4.2 Metering","5.2 Asset Age","5.3 Max Demand Network Lvl","5.4 Max Dem & Utilise - Spatial","6.3 Sustained Intrp"],"not_rendered":{"charts":0,"images":3,"macros":0,"external_links":12,"defined_names":240,"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":"2.1 Exp Summary","index":0,"n_rows":51,"n_cols":10,"rows_kept":51,"cut":false,"hidden":false,"merged":[[1,1,1,3]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CA RIN Table Ref / EB RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.1.1 - STANDARD CONTROL SERVICES CAPEX"]
[null,"2.1.1","Row 11 - Replacement expenditure","Financial","Total Replacement expenditure as per Table 2.2.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of Replacement expenditure capital activities in isolation to provide base expenditure.  A detailed review of every individual Network capital project was then undertaken, with the cost of incorrectly assigned projects either added or deducted from the base Replacement expenditure as necessary in line with CA RIN definitions to arrive at the reported value. ","Replacement expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total capitalised network overheads reported in row 15 of Table 2.1.1 and row 18 of Table 2.10.1.","Also reconciles to total Replacement expenditure reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 12 - Connections","Financial","Total Connections expenditure as per Table 2.5.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of Connections expenditure capital activities in isolation to provide base expenditure.  A detailed review of every individual Network capital project was then undertaken, with the cost of incorrectly assigned projects either added or deducted from the base Connections expenditure as necessary in line with CA RIN definitions to arrive at the reported value. ","Connections expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total capitalised network overheads reported in row 15 of Table 2.1.1 and row 18 of Table 2.10.1.","Also reconciles to total Connections expenditure reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 13 - Augmentation expenditure","Financial","Total Augmentation expenditure as per Table 2.3.4 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of Augmentation expenditure capital activities in isolation to provide base expenditure.  A detailed review of every individual Network capital project was then undertaken, with the cost of incorrectly assigned projects either added or deducted from the base Augmentation expenditure as necessary in line with CA RIN definitions to arrive at the reported value. ","Augmentation expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total capitalised network overheads reported in row 15 of Table 2.1.1 and row 18 of Table 2.10.1.","Also reconciles to total Augmentation expenditure reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 14 - Non-network","Financial","Total Non-network Capex as per Table 2.6.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of Non-network expenditure capital activities (e.g. IT, property, vehicles) in isolation to provide base expenditure.  A detailed review of every individual Network capital project was then undertaken, with the cost of any projects not meeting any of the CA RIN definitions of Replacement expenditure, Connections or Augmentation Expenditure added to arrive at the reported value. ","Non-network expenditure from SAP excludes specifically identifiable business overheads (where relevant).  These business overheads represent a component of the total capitalised network overheads reported in row 15 of Table 2.1.1 and row 18 of Table 2.10.1.","Also reconciles to total Non-network expenditure reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 15 - Capitalised network overheads","Financial","Represents the amount reported in row 18 of Table 2.10.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","Represents the total of the specifically identifiable business overheads from SAP that were excluded from reported Capex in rows 11 to 14 above.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year.","Refer Assumptions for rows 11 to 14 above.","Also reconciles to total Capitalised network overheads reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 16 - Capitalised corporate overheads","Financial","Represents the amount reported in row 33 of Table 2.10.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","As per SA Power Networks' Cost Allocation Method, superannuation is reported on a cash payments basis for regulatory reporting.  This value represents the standard control services capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense.","N/A","Also reconciles to total Capitalised corporate overheads reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 17 - Metering","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Metering capital is classified as an Alternative Control Service.  A nil value was therefore reported for standard control services.","N/A"]
[null,"2.1.1","Row 18  - Public lighting","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Public lighting capital is classified as a Negotiated Service.  A nil value was therefore reported for standard control services.","N/A"]
[null,"2.1.1","Row 26  - Balancing item","Financial","Summary of Balancing Items for Capex 2017-18","Actual","N/A","As per the requirements of the RIN, SA Power Networks has provided the AER with a summary showing a reconciliation of the Balancing items values reported in Tables 2.1.1 to 2.1.4.","N/A","Also reconciles to Balancing item reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response."]
[null,"2.1.1","Row 27  - Capcons (included in the above)","Financial","Capital contributions from Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response.","Actual","N/A","Total Standard Control Services Capital contributions reported in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response and a component of the amount reported against variable DRAB13 deducted from the Standard Control Services RAB in Tables 3.3.1 and 3.3.2 of SA Power Networks' 2017-18 Benchmarking RIN response (with the balance representing Gifted Assets). ","N/A","N/A"]
[null,"2.1.1","Row 28  - Total gross capex (including capcons)","Financial","Rows 11 to 27 above.","Actual","N/A","Refer Methodology for rows 11 to 27 above.","Refer Assumptions for rows 11 to 27 above.","Reconciles to total actual capex in Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.2 - STANDARD CONTROL SERVICES OPEX"]
[null,"2.1.2","Row 33 - Vegetation management","Financial","Total Vegetation management expenditure as per Table 2.7.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of the Vegetation management operating activities in isolation to provide reportable expenditure.  Cost assignments versus activities were also reviewed to ensure compliance with CA RIN definitions, with any necessary adjustments made to the reported value.","Vegetation management expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total network overheads reported in row 37 of Table 2.1.1 and row 15 of Table 2.10.1.","Reconciles to Vegetation Management expenditure in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response (excluding amount reported as Network Overheads in Table 2.10.1)"]
[null,"2.1.2","Row 34 - Maintenance","Financial","Total Maintenance expenditure as per Table 2.8.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of the Maintenance operating activities in isolation to provide reportable expenditure.  Cost assignments versus activities were also reviewed to ensure compliance with CA RIN definitions, with any necessary adjustments made to the reported value.","Maintenance expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total network overheads reported in row 37 of Table 2.1.1 and row 15 of Table 2.10.1.","Reconciles to the total of the Inspections and Maintenance and repair lines in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response (excluding amounts reported as Network Overheads in Table 2.10.1)"]
[null,"2.1.2","Row 35 - Emergency response","Financial","Total Emergency response expenditure as per Table 2.9.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of the Emergency response operating activities in isolation to provide reportable expenditure.  Cost assignments versus activities were also reviewed to ensure compliance with CA RIN definitions, with any necessary adjustments made to the reported value.","Emergency response expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent a component of the total network overheads reported in row 37 of Table 2.1.1 and row 15 of Table 2.10.1.","Reconciles to Emergency response expenditure in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response (excluding amount reported as Network Overheads in Table 2.10.1)"]
[null,"2.1.2","Row 36 - Non-network","Financial","Standard Control Services component of total Non-network Opex as per Table 2.6.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","IT and property expenditure was obtained by the allocation of these corporate costs from SAP in accordance with SA Power Networks' cost allocation method, Network telephony costs are captured against specific SAP activities, while vehicle costs were derived through a combination of data obtained from SAP and our external fleet services provider. ","Represents the following expenditure (with reference to Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN Response):  IT and Property expenditure reported as a component of the Corporate costs and other operating line; Network telephony costs reported as part of the Network operating costs line; and Vehicle costs which are spread across operating expense categories.","N/A"]
[null,"2.1.2","Row 37 - Network overheads","Financial","Represents the amount reported in row 15 of Table 2.10.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","The reported total represents the aggregate of the various costs described in the Data source.  These costs are all directly attributable to standard control services in accordance with SA Power Networks' cost allocation method.  Expenditure was obtained from a variety of SAP reports. ","Represents the total of the following cost categories from Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN: Distribution licence fee; Network operating costs; Substation property maintenance; Guaranteed service level payments; Network insurance; Call centre; Customer billing; and Other customer services.  Also includes the Network overhead amounts excluded from rows 33 to 35 above.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year.","N/A"]
[null,"2.1.2","Row 38 - Corporate overheads","Financial","Represents the amount reported in row 30 of Table 2.10.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","Represents the total allocation of corporate costs to standard control services as detailed in SA Power Networks' cost allocation method.","Reconciles to the Corporate costs and other operating  expenditure in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN.","N/A"]
[null,"2.1.2","Row 39 - Metering","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Metering opex is classified as either an alternative control or negotiated service.  A nil value was therefore reported for standard control services.","N/A"]
[null,"2.1.2","Row 40  - Public lighting","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Public lighting maintenance is classified as a Negotiated Service.  A nil value was therefore reported for standard control services.","N/A"]
[null,"2.1.2","Row 48  - Balancing item","Financial","Summary of Balancing Items for Opex 2017-18","Actual","N/A","As per the requirements of the RIN, SA Power Networks has provided the AER with a summary showing a reconciliation of the Balancing items values reported in Tables 2.1.1 to 2.1.4.","Represents a balancing item to back out duplicated expenditure from Total Opex in row 49.","N/A"]
[null,"2.1.2","Row 49  - Total opex","Financial","Rows 33 to 48 above.","Actual","N/A","Refer Methodology for rows 33 to 48 above.","Refer Assumptions for rows 33 to 48 above.","Reconciles to total actual opex for standard control services in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.3 - ALTERNATIVE CONTROL SERVICES CAPEX"]
[null,"2.1.3 ","Row 54 - Connections","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","Capex associated with Alternative Control Services Connections has been reported under the Metering category in Tables 2.1.3.  SA Power Networks has no other Alternative Control Services aside from Metering.","N/A"]
[null,"2.1.3 ","Row 55 - Capitalised network overheads","Financial","Represents the amount reported in row 19 of Table 2.10.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","Represents the total of the specifically identifiable business overheads from SAP that were excluded from reported Metering Capex in row 57 below.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year.","Refer Assumptions for row 57 below.","Represents a component of costs reported against Metering services in Table 8.2.3 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.3 ","Row 56 - Capitalised corporate overheads","Financial","Represents the amount reported in row 34 of Table 2.10.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","As per SA Power Networks' Cost Allocation Method, superannuation is reported on a cash payments basis for regulatory reporting.  This value represents the alternative control services capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense.","N/A","Represents a component of costs reported against Metering services in Table 8.2.3 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.3 ","Row 57 - Metering","Financial","Total Metering capital expenditure as per Table 4.2.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of Metering expenditure capital activities in isolation to provide base expenditure.  A detailed review of every individual Network capital project was then undertaken, with the cost of incorrectly assigned projects either added or deducted from the base Metering expenditure as necessary in line with CA RIN definitions to arrive at the reported value. ","Metering expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent the total capitalised network overheads reported in row 55 of Table 2.1.3 and row 19 of Table 2.10.1.   Capital contributions are reported against variable DRAB13 deducted from the Alternative Control Services RAB in Tables 3.3.1 and 3.3.2 of SA Power Networks' 2017-18 Benchmarking RIN response.","Represents gross capital expenditure (inclusive of Capital contributions) on new meter installations and meter replacements, excluding amounts reported as Capitalised network overheads in row 55.  Net capex represents a component of the costs reported against Metering services in Table 8.2.3 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.3","Row 58  - Public lighting","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Public lighting capital is classified as a Negotiated Service.  A nil value was therefore reported for alternative control services.","N/A"]
[null,"2.1.3","Row 59 - Fee and quoted","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, all of SA Power Networks' fee and quoted works are classified as Negotiated Services.  Hence Alternative Control Services values are nil.","N/A"]
[null,"2.1.3","Row 67  - Balancing item","Financial","Summary of Balancing Items for Capex 2017-18","Actual","N/A","As per the requirements of the RIN, SA Power Networks has provided the AER with a summary showing a reconciliation of the Balancing items values reported in Tables 2.1.1 to 2.1.4.","A nil value has been reported against the Balancing item line in Table 2.1.3.","N/A"]
[null,"2.1.3","Row 68  - Total capex","Financial","Rows 54 to 67 above.","Actual","N/A","Refer Methodology for rows 54 to 67 above.","Refer Assumptions for rows 54 to 67 above.","Reconciles to total Alternative Control Services capex in Table 8.2.3 of SA Power Networks' 2017-18 Annual Reporting RIN plus Metering capital contributions."]
[null,"2.1.4 - ALTERNATIVE CONTROL SERVICES OPEX"]
[null,"2.1.4","Row 73 - Connections","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","Opex associated with Alternative Control Services Connections has been reported under the Metering category in Tables 2.1.4.  SA Power Networks has no other Alternative Control Services aside from Metering.","N/A"]
[null,"2.1.4","Row 74 - Network overheads","Financial","Represents the amount reported in row 16 of Table 2.10.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","The reported total represents the aggregate of the various costs described in the Data source.  These costs are all directly attributable to alternative control services in accordance with SA Power Networks' cost allocation method.  Expenditure was obtained from a variety of SAP reports. ","Represents the total of the following cost categories from Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN: Customer billing and Other customer services.  Also includes the Network overhead amounts excluded from row 76 below.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year.","N/A"]
[null,"2.1.4","Row 75 - Corporate overheads","Financial","Represents the amount reported in row 31 of Table 2.10.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","Represents the total allocation of corporate costs to alternative control services as detailed in SA Power Networks' cost allocation method.","Reconciles to the Corporate costs and other operating  expenditure in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN.","N/A"]
[null,"2.1.4","Row 76 - Metering","Financial","Total Metering opex as per Table 4.2.2 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the reporting of the Meter maintenance operating activities in isolation to provide reportable expenditure.  Meter reading costs are separately captured against specific SAP orders and allocated between alternative control and negotiated services based on expenditure service breakdowns provided by the external contractors who carried out the work.  Cost assignments versus activities were also reviewed to ensure compliance with CA RIN definitions, with any necessary adjustments made to the reported value.","Meter maintenance and repair expenditure from SAP excludes specifically identifiable business overheads.  These business overheads represent the total network overheads reported in row 74 of Table 2.1.4 and row 16 of Table 2.10.1.","Reconciles to the total of the Maintenance and repair and Meter reading lines in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN (excluding amounts reported as Network Overheads in Table 2.10.1)"]
[null,"2.1.4","Row 77  - Public lighting","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, Public lighting maintenance is classified as a Negotiated Service.  A nil value was therefore reported for alternative control services.","N/A"]
[null,"2.1.4","Row 78 - Fee and quoted","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","In accordance with our current classification of services, all of SA Power Networks' fee and quoted works are classified as Negotiated Services.  Hence Alternative Control Services values are nil.","N/A"]
[null,"2.1.4","Row 79 - Non-network","Financial","Alternative Control Services component of total Non-network Opex as per Table 2.6.1 of SA Power Networks' 2017-18 Category Analysis RIN Response.","Actual","N/A","IT and property expenditure was obtained by the allocation of these corporate costs from SAP in accordance with SA Power Networks' cost allocation method.   ","Represents the following expenditure (with reference to Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN):  IT and Property expenditure reported as a component of the Corporate costs and other operating line.","N/A"]
[null,"2.1.4","Row 86  - Balancing item","Financial","Summary of Balancing Items for Opex 2017-18","Actual","N/A","As per the requirements of the RIN, SA Power Networks has provided the AER with a summary showing a reconciliation of the Balancing items values reported in Tables 2.1.1 to 2.1.4.","Represents a balancing item to back out duplicated expenditure from Total Opex in row 87.","N/A"]
[null,"2.1.4","Row 87  - Total opex","Financial","Rows 73 to 86 above.","Actual","N/A","Refer Methodology for rows 73 to 86 above.","Refer Assumptions for rows 73 to 86 above.","Reconciles to total actual opex for alternative control services in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.1.5 - DUAL FUNCTION ASSETS CAPEX"]
[null,"2.1.5","Rows 92-107","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","SA Power Networks has no assets which are classified as Dual Function in accordance with RIN definitions, hence all reported values in Tables 2.1.5 are nil.","N/A"]
[null,"2.1.6 - DUAL FUNCTION ASSETS OPEX"]
[null,"2.1.6","Rows 112-126","Financial","N/A","Actual","N/A","Not applicable to SA Power Networks","SA Power Networks has no assets which are classified as Dual Function in accordance with RIN definitions, hence all reported values in Tables 2.1.6 are nil.","N/A"]

{"sheet":"2.2 Repex","index":1,"n_rows":66,"n_cols":10,"rows_kept":66,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.2 REPEX (General Comments)"]
[null,2.2000000000000002,"Applies to entire 2.2 Repex tab.","Non-financial","-","Estimated","More than half of the data for 2.2 was obtained through SAP, and in general, we only have complete information of:\n- Date of completion And Date of failure\nLimited information of:\n- Work order number\n- Function Location (Feeder ID)\n- LV/HV (not into specific voltage e.g. 7.6kV 11kV etc.)\nNo or very limited information of:\n- Specific operating voltage (of asset)\n- Feeder type (CBD, URBAN etc.)\n- Material of overhead conductor (steel/copper etc.)\n- Length of overhead conductor (replaced)\n- Length of underground conductor (replaced)","For these we have no information:\n\n- Financial Year\n    - Convert date of completion into financial year\n- Specific operating voltage (of asset)\n    - look up into the database, look for the voltage of the specific feeder, then assume the voltage for the specific feeder is the operating voltage of this asset\n- Feeder type (CBD, URBAN etc.)\n    - look up into the database, look for the feeder type of the specific feeder\n- Material of overhead conductor (steel/copper etc.)\n    - In database, assign a single material type for each feeder (by determine which material is used the most for this feeder), then look for the material of the specific feeder, then assume the material for the specific feeder is the material for the replaced overhead conductor\n(Continue ->)\n\n","- Length of overhead conductor assumptions (replaced)\nLengths are determined by voltage\n - FM – 20m (conductor length)\n - DD – LV = 64m per span (route) = 256m (conductor)\n - DD – 11kv = 98m per span (route) = 294m (conductor)\n - DD – 33kv = 175m per span (route) = 525m (conductor)\n - DD – SWER = 154m per span (route) = 154m (conductor)\n - DD – 66kv = 150m per span (route) = 450m (conductor)\n\n- Length of underground conductor (replaced)\n - HV Cable = 10m\n - LV Cable = 10m\n\n- Wherever key information is missing (e.g. unknown feeder), the ratio of knowns is calculated and applyed where key information is missing\n\n- Where replacements are completed as projects (i.e. not completed with the standard DD or FM notifications process) the project has been counted if it is completed in the financial year under consideration. It is assumed that all of the project cost is spent in the financial year of completion.","In general,\n- For Replacement consider DD+FM+Project (if applicable)\n- For Replacement exclude all FM replacements completed on all Major Event Days or caused by third party damage\n- For DD \n     - Do not count DERR/DLFL (For everything)\n     - Do not count PROJ (Only for OH Conductors)\n     - Do not count items with no order number\n- For FM\n     - Do not count items with no order number\n     - Do not count DERR/DLFL (For everything)\n     - All items with follow up numbers or matched J numbers in AR will be regarded as duplicated items and therefore excluded for counting\n- For Failure only consider FM\n- Create date is used for counting failures; Completion date (Reference date) will be used for counting replacement\n\n- For applying ratio to unknown items\n If (A=50%|B=30%|C=10%|D=10%) then: AAAAABBBCDAAAAABBBCD\n Note: Item with ratio < 5% will be ignored\n"]
[null,2.2000000000000002,"General comment on consolidation and reconciliation of financial figures within 2.2 and 2.12.","Financial","Financial amounts are derived from SAP/BEX reports and a reconciliation is provided back to the Regulatory Accounts. Any movement from the regulated accounts has an offset within another of the CATRIN categories. ","Estimated","The figures contained within 2.2 and 2.12 (repex section) reconcile back to the Regulatory accounts after taking into account two offsetting adjustments, one with Non Network and the other with Augex. The apportionment of non asset specific costs between the various AER categories has required assumptions that require the figures to be classified as estimates","The figures presented in 2.2 and associated 2.12 for Repex, as with the Regulated Statements are collected within identifiable codes within SAP.  There are two exceptions to this which refer to Safety and Non Network Telecommunication costs.  Both of these have required a manual process of splitting the one SAP classification code.  Telecommunications spend has been split between Repex and Non Network and Safety split between Augex and Repex.  Allowing for these two adjustments, the totals will match the Regulated accounts. The basis of preparation below, will demonstrate that the business base their financial results on SAP reports which use existing classification codes and which further breakdown these classifications so that AER reporting classifications can be determined.  Once this analysis is done, the results are provided to Finance branch.  Finance will check that the values are consistent with the regulated accounts.  Finance will also provide for an adjustment for orders that were not related to a specific asset being replaced.  Orders which did not relate to a specific category have been apportioned on a percentage of costs of the orders which could be assigned to a specific category.  Finance branch will also apportion Project Support over the direct cost figures provided by the business (after the non asset specific costs adjustment) on a pro rata basis. ","The apportionment of non asset specific costs between the various AER categories has required assumptions that require the figures to be classified as estimates"]
[null,2.2000000000000002,"General information for all cost data \nIs applicable for Stobie Poles, Pole top structure, Overhead Conductor, Underground Cable, Service Lines, Recloser and Sectionaliser","Financial","Always use \"SAP + BEX report\" unless otherwise stated","Estimated","All cost data is dependent on replacement and failure data collected in the above Non-financial steps, which means, all effects of assumption/estimation we've made before will affect the cost, as a result all cost data are estimated as well.","Process to get expenditure data for 2.2\n- Load BeX report which contains all expenditure data for current financial year\n- Each time when a valid SAP noti is processed, compare the noti number and order number with the BeX report and see if there's a match for them, if a match is found and the item itself is a valid item then count the expenditure","- Assume cost information provided by Network Finance team covers all cost\n\nAll calculation follows the following rules:\n- Material ->Direct Material Cost\n- Labour+Labour OH+Contract -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Direct Material Cost + Direct Labour Cost + Contract Cost + Other Cost = Direct Cost","this row has to be read in conjunction with the Non-financial BOP for a complete understanding"]
[null,"2.2.1 - REPLACEMENT EXPENDITURE, VOLUMES AND ASSET FAILURES BY ASSET CATEGORY"]
[null,"2.2.1","POLES BY: \n(Expenditure) Rows 11-30","Financial",{"$f":"\"Refer to Row \"&ROW(E41)&\" of 2.2 BOP\"","v":"Refer to Row 41 of 2.2 BOP"}]
[null,"2.2.1","POLES BY: \n(Asset Replacements/Asset Failures) Rows 11-30","Non-financial",{"$f":"\"Refer to Row \"&ROW(E42)&\" of 2.2 BOP\"","v":"Refer to Row 42 of 2.2 BOP"}]
[null,"2.2.1","POLE TOP STRUCTURES BY: \n(Expenditure) Rows 31-37\n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV\n> 22 KV & < = 66 KV\n> 66 KV & < = 132 KV\n","Financial",{"$f":"\"Refer to Row \"  &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 9 of 2.2 BOP"},"Estimated",{"$f":"\"Refer to Row \"   &ROW($E$8)&   \" and \"   &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 8 and 9 of 2.2 BOP"}]
[null,"2.2.1","POLE TOP STRUCTURES BY: \n(Asset Replacements/Asset Failures) Rows 31-37\n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV\n> 22 KV & < = 66 KV\n> 66 KV & < = 132 KV\n","Non-financial","SAP","Estimated","The only information we have is Date of replacement/failure and some of locations, therefore, we need to estimate voltage for the purpose of RIN.","All replacement codes were extracted from SAP on the completion date and the failures from SAP on created date.\n\nThe following categories are included under this section: \n- DF, Air break, LS, LSDF, Tie wire, earth, lugs, taps, joint, pot head \n- LFI (Line fault indicators)\n- Crossarm\n- Insulator","In SAP Extraction (HV) for these with known Feeder IDs, we assume the operating voltage of Pole is the same as the highest voltage of the feeder. \n\nFor these that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown ones"]
[null,"2.2.1","OVERHEAD CONDUCTORS BY: \n(Expenditure) Rows 38-46\n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV  ; SWER\n˃ 11 KV & < = 22 KV ; SINGLE-PHASE\n˃ 11 KV & < = 22 KV ; MULTIPLE-PHASE\n> 22 KV & < = 66 KV\n","Financial",{"$f":"\"Refer to Row \"  &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 9 of 2.2 BOP"},"Estimated",{"$f":"\"Refer to Row \"   &ROW($E$8)&   \" and \"   &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 8 and 9 of 2.2 BOP"}]
[null,"2.2.1","OVERHEAD CONDUCTORS BY: \n(Asset Replacements/Asset Failures) Rows 38-46\n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV  ; SWER\n˃ 11 KV & < = 22 KV ; SINGLE-PHASE\n˃ 11 KV & < = 22 KV ; MULTIPLE-PHASE\n> 22 KV & < = 66 KV\n","Non-financial","SAP + Project data - Conductor Replacement Log.xlsx (Operational Asset Management)","Estimated","For Project data, most data is comprehensive and accurate\n\nFor SAP data, the only information we have is Date of replacement/failure and some of locations, therefore, we need to estimate voltage for the purpose of RIN.","All replacement codes were extracted from SAP on the completion date and the failures from SAP on created date.\nThe additional project information was added to the replacement numbers.","- Replacement is in CONDUCTOR LENGTH\n- Replacement is in unit of KMs\n\n- Consider all 19kV conductors as SWER conductors\n\nIn SAP Extraction (HV) for those with known Feeder IDs, we assume the operating voltage of Pole is the same as the highest voltage of the feeder. \n\nFor these that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown one\n\nThen for replacement, from the voltage we can derive the lengths we replaced by the rule we set->","- Length of overhead conductor assumptions (replaced)\nLengths are determined by voltage\n - FM – 20m (conductor length)\n - DD – LV = 64m per span (route) = 256m\n - DD – 11kv = 98m per span (route) = 294m\n - DD – 33kv = 175m per span (route) = 525m\n - DD – SWER = 154m per span (route) = 154m\n - DD – 66kv = 150m per span (route) = 450m\n"]
[null,"2.2.1","UNDERGROUND CABLES BY: \n(Expenditure) Rows 47-54\n˂ = 1 kV\n> 1 kV & < = 11 kV\n> 11 kV & < = 22 kV\n> 22 kV & < = 33 kV\n> 33 kV & < = 66 kV\n","Financial",{"$f":"\"Refer to Row \"  &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 9 of 2.2 BOP"},"Estimated"]
[null,"2.2.1","UNDERGROUND CABLES BY: \n(Asset Replacements/Asset Failures) Rows 47-54\n˂ = 1 kV\n> 1 kV & < = 11 kV\n> 11 kV & < = 22 kV\n> 22 kV & < = 33 kV\n> 33 kV & < = 66 kV\n","Non-financial","SAP + PROJ - Cable Retrench Log.xlsx (Operational Asset Management) ","Estimated","For Project data, most data are comprehensive and accurate\n\nFor SAP data, the only information we have is Date of replacement/failure and some of locations, therefore, we need to estimate voltage for the purpose of RIN.","All replacement codes were extracted from SAP on the completion date and the failures from SAP on created date.\nThe additional project information was added to the replacement numbers.","- Replacement in in ROUTE LENGTH\n- Replacement is in unit of KMs\n\nIn SAP Extraction (HV) for these with known Feeder IDs, we assume the operating voltage is the same as the highest voltage of the feeder. \n\nFor these that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown one\n\nThen for replacement, from the voltage we can derive the lengths we replaced by the rule we set->","- Length of underground conductor (replaced)per notification\n - HV Cable = 10m\n - LV Cable = 10m\n"]
[null,"2.2.1","SERVICE LINES BY: \n(Expenditure) Rows 55-70\n˂ = 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n˂ = 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE \n","Financial",{"$f":"\"Refer to Row \"  &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 9 of 2.2 BOP"},"Estimated","For SAP data, the only information we have is Date of replacement/failure and some of locations, therefore, we need to make assumptions on their Voltage, Customer Type and Connection Complexity","From the total population it was determined that the Residential service lines are 90% of total and Commercial service lines are 10% of total. This ratio is applied to the total cost."]
[null,"2.2.1","SERVICE LINES BY: \n(Asset Replacements/Asset Failures) Rows 55-70\n˂ = 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n˂ = 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE \n","Non-financial","SAP","Estimated","For SAP data, the only information we have is Date of replacement/failure and some of locations, therefore, we need to make assumptions on their Voltage, Customer Type and Connection Complexity","All replacement codes were extracted from SAP on the completion date and the failures from SAP on created date.","- No service line length information were recorded for failure/replacement, therefore only number of incidents will be recorded\n- From the total population, we assume the Residential service lines are 90% of total and Commercial service lines are 10% of total, this ratio is applied to all recorded items\n- Assume all Residential service line as Simple and all Commercial service lines as Complex"]
[null,"2.2.1","TRANSFORMERS BY: \n(Expenditure) Rows 71-76, 138, 139\nPole Mounted ; < = 22kV ;  < = 60 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  > 600 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  < = 60 kVA  ; Multiple Phase\nPole Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA  ; Multiple Phase\nPole Mounted ; < = 22kV ;  > 600 kVA  ; Multiple Phase\nPole Mounted ;> = 22 kV & < = 33 kV ;  < = 60kVA\nPole Mounted ;> = 22 kV & < = 33 kV ; > 60 KVA AND < = 600 KVA \n(Line Transformer)","Financial","SAP/ Bex report\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","We have used SAP, Switchgear replacement (Optional) and BEX report data to work out the estimated financial cost. ","1. Get total cost for pole mounted TF from relevant FM notis as total unplanned pole mounted replacement cost\n2. Get total cost for pole mounted TF from relevant DD notis as total planned pole mounted replacement cost\n3. Evenly distribute total cost to all pole mounted replacements\n\nL09 - Line Capacity Upgrades were considered","- Assume SAP (DD+FM) covers all cost\n- Assume every replaced Kiosk/GL TF (under the same category) has same average overall cost (e.g. same cost for labour, material etc.)\n- Sometimes the transformer in TC (transformer cubicle) is replaced due to the whole cubicle is replaced. In this case, 50% expenditure is allocated to transformer and 50% is allocated for switchgears. ","For TF >22kV, due to no line is available under Transformer Category, we have had to created some lines under \"Others\" to include these > 22kV TF\n\nTo know the size and voltage of the transformers an incomplete transformer databse was used. Where the TF size and voltage was unknown an estimate was made base on the feeder voltage and most common size for the feeder."]
[null,"2.2.1","TRANSFORMERS BY: \n(Asset Replacements/Asset Failures) Rows 71-76, 138, 139\nPole Mounted ; < = 22kV ;  < = 60 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  > 600 kVA ; Single Phase\nPole Mounted ; < = 22kV ;  < = 60 kVA  ; Multiple Phase\nPole Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA  ; Multiple Phase\nPole Mounted ; < = 22kV ;  > 600 kVA  ; Multiple Phase\nPole Mounted ;> = 22 kV & < = 33 kV ;  < = 60kVA\nPole Mounted ;> = 22 kV & < = 33 kV ; > 60 KVA AND < = 600 KVA \n(Line Transformer)\n","Non-financial","SAP + NOCLOG (text records of all HV outage events) +  Transformer database\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","The information we have from SAP doesn’t state the transformer size or the number of phases. In CA RIN the AER wants the transformers by Highest Operating Volatge, size and Number of phases.\n\n","All replacements were extracted from SAP on the completion date, or extracted from NOCLOG of 2017_18 financial year\n\nFor Asset Failure we have used the NOCLOG information only\n\nFrom the NOCLOG and TF database we could find some of the operating voltage, Ampere rating and number of phases. Where it was unknown refer to the SAPN Additional Comments.\nL09 - Line Capacity Upgrades were considered","The assumptions that were used in NOCLOG  which were used in both Failure and Replacement:\n\n- The following causes have been filtered to identify eligible items:\n   - TF Failed - age\n   - TF Failed - lightning\n   - TF Failed - internal\n- All TF replacements were whole unit replacement\n- Replacement will be done immediately after the failure (otherwise customer will be without power supply) \n","For TF >22kV, due to no line being available under Transformer Category, we have had to created some lines under \"Others\" to include these > 22kV TF\n\nTo know the size, voltage and phase of the transformers, the transformer databse was used. The Transformer database is not comprehensive.Where the transformer voltage was unknown the feeder voltage was assumed. Where the phase was unknown it was assumed to be 3 phase except where the voltage was 19kV (SWER). Where the size was unknown the most common size for the feeder was used."]
[null,"2.2.1","TRANSFORMERS BY: \n(Expenditure) Rows 71-76\nPOLE MOUNTED ; < = 22KV ;  < = 60 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 600 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  < = 60 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 600 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; > 22 KV ;  < = 60 KVA \nPOLE MOUNTED ; > 22 KV ;  > 60 KVA AND < = 600 KVA \nPOLE MOUNTED ; > 22 KV ;  > 600 KVA\n(Substation Transformer)","Financial","SAP (BeX reports - L14, L54, L36)","Estimated",null,"1. SAP BeX reports (project numbers and direct costs by financial year) are used to capture failure/replacement/refurbishment expenditures from the list of NW numbers by RIN replacement category.\n2. Project construction specifications are used to provide a breakdown of composite replacement works into respective asset groups (TF, CB, Switch, Protection categories) when consolidated into a single project.\n3. Residual project expenditure (after separating component costs) are taken to be the cost of primary asset (TF or CB) replacement.\n4. Refurbishment costs are 100% allocated to each respective asset 'Refurbished' category.","All resudual costs (after removing switchgear & protection relay contributions) are assumed to be the cost of TF replacement.\n(e.g. civils, earthing, AC/DC Auxiliaries etc required for the new asset) ","All replacement expenditures are reported in the financial year they're incurred, which may be outside of the (financial) year of asset replacement (taken as the asset commissioning date).\nReplacement expenditures are based on cost of assets installed (not necessarily equal to the volume of units removed)."]
[null,"2.2.1","TRANSFORMERS BY: \n(Asset Replacements/Asset Failures) Rows 71-76\nPOLE MOUNTED ; < = 22KV ;  < = 60 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 600 KVA ; SINGLE PHASE\nPOLE MOUNTED ; < = 22KV ;  < = 60 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; < = 22KV ;  > 600 KVA  ; MULTIPLE PHASE\nPOLE MOUNTED ; > 22 KV ;  < = 60 KVA \nPOLE MOUNTED ; > 22 KV ;  > 60 KVA AND < = 600 KVA \nPOLE MOUNTED ; > 22 KV ;  > 600 KVA\n(Substation Transformer)\n","Non-financial","No single database or asset register captures all required information.\nInformation collected from:\n- asset movements in SAP;\n- Failure investigations;\n- SAP FM & SD Notis\n- Asset replacement projects (captured in SAP); and\n- Primary plant contract running sheets.","Actual",null,"Data sources were cross-referenced to build a consolidated list of TF changes over the relevant financial year, including:\n- Assets that failed;\n- When the asset failed or was retired (financial year);\n- The driver for replacement (e.g. failure, condition replacement etc);\n- Assets that were refurbished\n- What unit was installed as a replacement for failed/retired assets (if any);\n- When the asset was replaced (financial year);\n- Relevant NW project for replacement/refurbishment expenditure and the corresponding RIN asset category.","1. Capitalised repairs/refurbishment expenditure is reported by asset group in the 'DNSP Defined' refurbishment categories by asset category.\n2 Temporary TF installations/movements (for load management as part of asset replacement) are not captured as replacements.\n3. Replacement volumes and categories are classified based on the assets removed.\n4. Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.","1. Asset condition-driven replacements incorporated into capacity or customer projects are not reported in repex totals.\n2. SAP assignment errors for projects that are wholly asset replacement are reported under REPEX totals.\n3. Assets that have failed but have not been replaced by the end of the relevant financial year are not included in reported replacement figures.\n4. Asset Replacement figures exclude costs of decommissioned assets (i.e. Redundant' or 'Disposed Of' assets) are unreported unless permanently replaced.\n5. Replacement assets may appear in a different RIN category to the unit removed (e.g where a replacement transformer has a different MVA rating).\n6. Assets replacement projects frequently span multiple financial years:\n  - Replacement volumes are reported on installation/commissioning\n  - Failure numbers are reported on event/decommissioning\n  - Replacement expenditures are reported as incurred."]
[null,"2.2.1","TRANSFORMERS BY: \n(Expenditure) Rows 77-98, 140\nKiosk Mounted ; < = 22kV ;  < = 60 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  > 600 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  < = 60 kVA  ; Multiple Phase\nKiosk Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA  ; Multiple Phase\nKiosk Mounted ; < = 22kV ;  > 600 kVA  ; Multiple Phase\nKiosk Mounted; > = 22 kV & < = 33 kV ; \n(Line Transformer)","Financial","SAP + NOCLOG + Operational Asset Management Ground level Switchgear Replacement Spreadsheet + BEX report\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","We have used SAP, NOCLOG, Switchgear replacement and BEX report data to work out the estimated financial cost. ","1. Get total cost for padmount(Kiosk) TF from relevant FM notis as total unplanned pole mounted replacement cost\n2. Get total cost for padmount(Kiosk) TF from relevant DD notis as total planned pole mounted replacement cost\n3. Evenly distribute total cost to all padmount(Kiosk) replacements\nL09 - Line Capacity Upgrades were considered","- Assume SAP (DD+ER+AR) covers all cost\n- Assume every replaced Kiosk/GL TF (under the same category) has same average overall cost (e.g. same cost for labour, material etc.)\n- In some case the transformer in TC (transformer cubicle)  is replaced when the whole cubicle is replaced. In this case, 50% expenditure is allocated to transformer and 50% is allocated for switchgears. ","For TF >22kV, due to no line is available under Transformer Category, we have had to created some lines under \"Others\" to include these > 22kV TF"]
[null,"2.2.1","TRANSFORMERS BY: \n(Asset Replacements/Asset Failures) Rows 77-98, 140\nKiosk Mounted ; < = 22kV ;  < = 60 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  > 600 kVA ; Single Phase\nKiosk Mounted ; < = 22kV ;  < = 60 kVA  ; Multiple Phase\nKiosk Mounted ; < = 22kV ;  > 60 kVA and < = 600 kVA  ; Multiple Phase\nKiosk Mounted ; < = 22kV ;  > 600 kVA  ; Multiple Phase\nKiosk Mounted; > = 22 kV & < = 33 kV ; \n(Line Transformer)","Non-financial","SAP + NOCLOG + Operational Asset Management Ground level Switchgear Replacement Spreadsheet+ Operational Asset Management Ground level Switchgear failure spreadsheet + TF Database\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","The information we have from SAP doesn’t state the transformer size or the number of phases. In CA RIN the AER wants the transformers by Highest Operating Volatge, size and Number of phases.\n\n","All replacements were extracted from SAP on the completion date, or extracted from NOCLOG of 2017_18 financial year\n\nFor Asset Failure we have used the NOCLOG information only\n\nFrom the NOCLOG and TF database we could find some of the operating voltage, Ampere rating and number of phases. Where it was unknown refer to the SAPN Additional Comments.\nL09 - Line Capacity Upgrades were considered","The assumptions that were used in NOCLOG  which were used in both Failure and Replacement:\n\n- The following causes have been filtered to identify eligible items:\n   - TF Failed - age\n   - TF Failed - lightning\n   - TF Failed - internal\n- All TF replacements were whole unit replacement\n- Replacement will be done immediately after the failure (otherwise customer will be without power supply) \n","For TF >22kV, due to no line being available under Transformer Category, we have had to created some lines under \"Others\" to include these > 22kV TF\n\nTo know the size, voltage and phase of the transformers, the transformer databse was used. Where the transformer voltage was unknown the feeder foltage was assumed. Where the phase was unknown it was assumed to be 3 phase except where the voltage was 19kV (SWER). Where the size was unknown the most common size for the feeder was used.\n\nSome years, transformers get replaced in switchgear projects. In the 17/18 year there no such replacements."]
[null,"2.2.1","TRANSFORMERS BY: \n(Expenditure)\nKIOSK MOUNTED ; < = 22KV ;  < = 60 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 600 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  < = 60 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 600 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; > 22 KV ;  < = 60 KVA \nKIOSK MOUNTED ; > 22 KV ;  \nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂ 22 KV ;  < = 60 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  > 60 KVA  AND < = 600 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  >  600 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  < = 60 KVA ; MULTIPLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  > 60 KVA  AND < = 600 KVA ; MULTIPLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  >  600 KVA ; MULTIPLE PHASE\n","Financial","SAP (BeX reports - L14, L54, L36)","Estimated",null,"1. SAP BeX reports (project numbers and direct costs by financial year) are used to capture failure/replacement/refurbishment expenditures from the list of NW numbers by RIN replacement category.\n2. Project construction specifications are used to provide a breakdown of composite replacement works into respective asset groups (TF, CB, Switch, Protection categories) when consolidated into a single project.\n3. Residual project expenditure (after separating component costs) are taken to be the cost of primary asset (TF or CB) replacement.\n4. Refurbishment costs are 100% allocated to each respective asset 'Refurbished' category.","All resudual costs (after removing switchgear & protection relay contributions) are assumed to be the cost of TF replacement.\n(e.g. civils, earthing, AC/DC Auxiliaries etc required for the new asset) ","All replacement expenditures are reported in the financial year they're incurred, which may be outside of the (financial) year of asset replacement (taken as the asset commissioning date).\nReplacement expenditures are based on cost of assets installed (not necessarily equal to the volume of units removed)."]
[null,"2.2.1","TRANSFORMERS BY: \n(Asset Replacements/Asset Failures)\nKIOSK MOUNTED ; < = 22KV ;  < = 60 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 600 KVA ; SINGLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  < = 60 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 60 KVA AND < = 600 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; < = 22KV ;  > 600 KVA  ; MULTIPLE PHASE\nKIOSK MOUNTED ; > 22 KV ;  < = 60 KVA \nKIOSK MOUNTED ; > 22 KV ;  \nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂ 22 KV ;  < = 60 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  > 60 KVA  AND < = 600 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  >  600 KVA ; SINGLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  < = 60 KVA ; MULTIPLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  > 60 KVA  AND < = 600 KVA ; MULTIPLE PHASE\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ; ˂  22 KV ;  >  600 KVA ; MULTIPLE PHASE\n","Non-financial","No single database or asset register captures all required information.\nInformation collected from:\n- asset movements in SAP;\n- Failure investigations;\n- SAP FM & SD Notis\n- Asset replacement projects (captured in SAP); and\n- Primary plant contract running sheets.","Actual",null,"Data sources were cross-referenced to build a consolidated list of TF changes over the relevant financial year, including:\n- Assets that failed;\n- When the asset failed or was retired (financial year);\n- The driver for replacement (e.g. failure, condition replacement etc);\n- Assets that were refurbished\n- What unit was installed as a replacement for failed/retired assets (if any);\n- When the asset was replaced (financial year);\n- Relevant NW project for replacement/refurbishment expenditure and the corresponding RIN asset category.","1. Capitalised repairs/refurbishment expenditure is reported by asset group in the 'DNSP Defined' refurbishment categories by asset category.\n2 Temporary TF installations/movements (for load management as part of asset replacement) are not captured as replacements.\n3. Replacement volumes and categories are classified based on the assets removed.\n4. Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.","1. Asset condition-driven replacements incorporated into capacity or customer projects are not reported in repex totals.\n2. SAP assignment errors for projects that are wholly asset replacement are reported under REPEX totals.\n3. Assets that have failed but have not been replaced by the end of the relevant financial year are not included in reported replacement figures.\n4. Asset Replacement figures exclude costs of decommissioned assets (i.e. Redundant' or 'Disposed Of' assets) are unreported unless permanently replaced.\n5. Replacement assets may appear in a different RIN category to the unit removed (e.g where a replacement transformer has a different MVA rating).\n6. Assets replacement projects frequently span multiple financial years:\n  - Replacement volumes are reported on installation/commissioning\n  - Failure numbers are reported on event/decommissioning\n  - Replacement expenditures are reported as incurred."]
[null,"2.2.1","SWITCHGEAR BY: \n(Expenditure) Rows 100-113\nSwitch Categories\n","Financial","SAP (BeX reports - L14, L54, L36, L13)","Estimated",null,"1. SAP BeX reports (project numbers and direct costs by financial year) are used to capture failure/replacement/refurbishment expenditures from the list of NW numbers by RIN category.\n2. Project construction specifications are used to provide a breakdown of composite replacement works into respective asset groups (TF, CB, Switch, Protection categories) when consolidated into a single project.\n3. When not directly estimated, unit replacement costs have been used to proportion relative expenditues by asset groups across the life of the project.\n4. Component costs from all replacement projects were summed by RIN switch category to give the total replacement expenditure.","1. unit cost assumed to be the average cost of component asset replacement as part of a CB/TF driven replacement.\n2. All resudual costs (after removing TF & protection relay contributions) are assumed to be the cost of switchgear replacement.\n(e.g. civils, earthing, AC/DC Auxiliaries etc required for the new asset) ","1. Asset Replacement figures exclude costs/volumes associated with permanently decommissioned assets (i.e. 'Redundant', 'Abandoned' assets are unreported).\n2. Replacement expenditures are based on cost of assets installed (not necessarily equal to the volume of units removed).\n3. Assets replacement projects frequently span multiple financial years:\n  - Replacement numbers are reported on installation/commissioning\n  - Replacement expenditures are reported as incurred."]
[null,"2.2.1","SWITCHGEAR BY: \n(Asset Replacements/Asset Failures) Rows 100-113\nSwitch Categories\n","Non-financial","No single database or asset register captures all required information.\nInformation collected from:\n- asset movements in SAP;\n- Failure investigations;\n- SAP FM & SD Notis\n- Asset replacement projects (captured in SAP); and\n- Primary plant contract running sheets.","Actual",null,"Data sources were cross-referenced to build a consolidated list of switch changes over the relevant financial year, including:\n- Assets that failed;\n- When the asset failed or was retired (financial year);\n- The driver for replacement (e.g. failure, condition replacement etc);\n- Assets that were refurbished\n- What unit was installed as a replacement for failed/retired assets (if any);\n- When the asset was replaced (financial year);\n- Relevant NW project for replacement/refurbishment expenditure and the corresponding RIN asset category.","1. Replacement volumes and categories are classified based on the assets removed, where there is a permanent replacement planned.\n2. Disconnector/switch failures are in-service functional failures and devices in poor condition & considered unsafe for live operation and require capital replacement works.\n3. Where replaced as part of a coordinated project (i.e. replaced with CB or TF), switches are assumed to have been replaced in the same financial year as the CB(s) or TF.\n4. Capitalised repairs/refurbishment expenditure is reported by asset group in the 'DNSP Defined' refurbishment categories by asset category.\n5. Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.","1. Asset condition-driven replacements incorporated into capacity or customer projects are not reported in repex totals.\n2. Replacement volumes/expenditures include capital upgrade projects only (failures/replacements captused as OPEX are not reported).\n3. Asset Replacement figures exclude costs of decommissioned assets (i.e. Redundant' or 'Disposed Of' assets) are not reported as replacements.\n4. Assets that failed but have not been replaced by the end of the relevant financial year are not included in reported replacement figures.\n5. Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.\n6. Switchgear asset replacements driven by safety projects are reported under repex totals.\n7. SAP assignment errors for projects that are wholly asset replacement are reported under REPEX totals.\n8. Assets replacement projects frequently span multiple financial years:\n  - Replacement numbers are reported on installation/commissioning\n  - Replacement expenditures are reported as incurred."]
[null,"2.2.1","SWITCHGEAR BY: \n(Expenditure) Rows 100-113\nCircuit Breaker Categories\n","Financial","SAP (BeX reports - L14, L54, L36, L13)","Estimated",null,"1. SAP BeX reports (project numbers and direct costs by financial year) are used to capture failure/replacement/refurbishment expenditures from the list of NW numbers by RIN replacement category.\n2. Project construction specifications are used to provide a breakdown of composite replacement works into respective asset groups (TF, CB, Switch, Protection categories) when consolidated into a single project.\n3. Residual project expenditure (after separating component costs) are taken to be the cost of primary asset (TF or CB) replacement.\n4. Refurbishment costs are 100% allocated to each respective asset 'Refurbished' category.","All resudual costs (after removing TF & protection relay contributions) are assumed to be the cost of CB replacement.\n(e.g. civils, earthing, AC/DC Auxiliaries etc required for the new asset)","All replacement expenditures are reported in the financial year they're incurred, which may be outside of the (financial) year of asset replacement (taken as the asset commissioning date).\nReplacement expenditures are based on cost of assets installed (not necessarily equal to the volume of units removed)."]
[null,"2.2.1","SWITCHGEAR BY: \n(Asset Replacements/Asset Failures) Rows 100-113\nCircuit Breaker Categories\n","Non-financial","No single database or asset register captures all required information.\nInformation collected from:\n- asset movements in SAP;\n- Failure investigations;\n- SAP FM & SD Notis\n- Asset replacement projects (captured in SAP); and\n- Primary plant contract running sheets.","Actual",null,"Data sources were cross-referenced to build a consolidated list of CB changes over the relevant financial year, including:\n- Assets that failed;\n- When the asset failed or was retired (financial year);\n- The driver for replacement (e.g. failure, condition replacement etc);\n- Assets that were refurbished\n- What unit was installed as a replacement for failed/retired assets (if any);\n- When the asset was replaced (financial year);\n- Relevant NW project for replacement/refurbishment expenditure and the corresponding RIN asset category.","1. Switchgear installed temporarily for load management prior to permanent switchgear replacement is not reported as replacement volumes.\n2. Switchboard CB truck replacements are assumed to be a single asset failures &/or replacement.\n3. A single failure that necessitates replacement of a complete switchboard is assumed to be a failure of all CBs in that switchboard.\n4. Replacement numbers reported are assumed to be the number of CBs in the decommissioned switchboard.\n5. Capitalised repairs/refurbishment expenditure is reported by asset group in the 'DNSP Defined' refurbishment categories by asset category.\n6. Areva (Alstom) S1 CB replacements are (replaced/refurbished on failure) - from 2017/18 are reported in 66kV CB refurbishments\n7. Horizon CB replacements are recorded as asset refurbishments (not replacements), when part of planned replacement/refurbishment programs\n8. Date of replacement is assumed to be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.","1. Asset condition-driven replacements incorporated into capacity or customer projects are not reported in repex totals.\n2. Replacement volumes/expenditures include capital upgrade projects only (failures/replacements captused as OPEX are not reported).\n3. SAP assignment errors for projects that are wholly asset replacement are reported under REPEX totals.\n4. Switchboard failures are excluded if the failure relates to a VT, cables or terminations & did not result in a CB failure or replacement.\n5. Uneconomically repairable Horizon failures in service are included in failure/replacement repex reporting.\n6. 11kV CB refurbishment numbers are reported where the installation date (as shown on the plant movement form) falls within the relevant financial year\n7. Assets that failed but have not been replaced by the end of the relevant financial year are not included in reported replacement figures.\n8. Asset Replacement figures exclude costs of decommissioned assets (i.e. Redundant' or 'Disposed Of' assets) are not reported as replacements.\n9. Assets replacement projects frequently span multiple financial years:\n  - Replacement numbers are reported on installation/commissioning\n  - Replacement expenditures are reported as incurred."]
[null,"2.2.1","PUBLIC LIGHTING BY: \n(Expenditure)","Financial"]
[null,"2.2.1","PUBLIC LIGHTING BY: \n(Asset Replacements/Asset Failures)","Non-financial"]
[null,"2.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \n(Expenditure) Row 123\nField Devices","Financial","Report from Network Finance for all Protection Asset Replacement projects in 2017/18 (Budget lines 18975, 18976 & 19505)","Estimated",null,"NW no's from the Protection Asset Replacement budget lines were crosschecked against all NW no's in lines L14,L54,L36 & L39. Protection projects were summed to give the total repex spend in 2017/18. Any protection projects that replaced other assets (e.g. reclosers) had expenditure allocated to their respective lines. \n\nWhere protection assets were replaced under other projects (e.g. a switchboard replacement), protection expenditure was allocated to this line. Expenditure in these cases is based on standard unit costs for the protection scheme being replaced.","Report from Network Finance included all required projects."]
[null,"2.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \n(Asset Replacements/Asset Failures) Row 123\nField Devices","Non-financial","No single database or asset register currently captures all required information.\nInformation collected from:\n- Failure investigations Database\n- Asset replacement projects (captured in SAP); and\n- Protection Settings Database (PSS6)","Actual",null,"Number of asset replacements was calculated by summing the number of relays installed under the protection asset replacement budget (on a per-project basis). Any relays replaced under other repex projects (e.g. switchboard replacement) are also added to this line. This is then cross checked against the protection settings database to ensure the total number of replacements correlates.\n\nFailures are tracked using a Relay Failure Register. This was crosschecked against the capitalized relay replacements listed under the Network Finance L54 report.\n\nAdditional asset replacement volumes include protection relay replacements incorporated with CB/TF/Switch replacement, based on project construction specifications.","All relay failures are captured in the Relay Failure Register and listed as a line item under L54","Any relays replaced under augex projects (e.g. reliability) are excluded, therefore the total number of relays installed in 2017/18 will not be equal to the number of repex replacements.\n\nNo allowance has been made for silent failures that can only  be discovered when the relay is required to trip or during planned  maintenance."]
[null,"2.2.1","Row 125, 127, 128  SCADA,Network control and protection systems - Communications Network Assets, Communications Site Infrastructure and Communications Linear Assets  Column E","Financial","SAP","Actual",null,"Data was extracted from SAP by finance department using Analysis Reports. Search was conducted under specific Telco cost numbers. Analysis Reports are filtered according to Communications Network Assets, Communications Site Infrastructure & Communications Linear Assets.","No assumptions, just collated data into the form required"]
[null,"2.2.1","Row 125, 127, 128  SCADA,Network control and protection systems - Communications Network Assets, Communications Site Infrastructure and Communications Linear Assets  Column F and G","Non-financial","SAP","Actual",null,"Go through each projects in the Analysis reports and calculate the number of asset replacements."]
[null,"2.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \n(Expenditure) Rows 126\nMaster Station Assets","Financial","SCADA Configurations","Actual",null,"Asset replacement project numbers are traceable and were extracted from SCADA configuration files. No SCADA assets were replaced in 2017/18."]
[null,"2.2.1 - REPLACEMENT EXPENDITURE, VOLUMES AND ASSET FAILURES BY ASSET CATEGORY \"OTHER\""]
[null,"2.2.1","OTHER BY: \n(Expenditure) Rows 131-136\n˂ = 1 kV; stobie pole\n> 1 kV & < = 11 kV; stobie pole\n˃ 11 kV & < = 22 kV; stobie pole\n> 22 kV & < = 66 kV; stobie pole\n> 66 kV & < = 132 kV; stobie pole\n> 132 kV; stobie pole\n","Financial",{"$f":"\"Refer to Row \"  &ROW($E$9)&   \" of 2.2 BOP\"","v":"Refer to Row 9 of 2.2 BOP"}]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Rows 131-136\n˂ = 1 kV; stobie pole\n> 1 kV & < = 11 kV; stobie pole\n˃ 11 kV & < = 22 kV; stobie pole\n> 22 kV & < = 66 kV; stobie pole\n> 66 kV & < = 132 kV; stobie pole\n> 132 kV; stobie pole","Non-financial","SAP","Estimated","The only information we have is Date of replacement/failure and some of locations, therefore, we need to estimate voltage for the purpose of RIN.\n\nWe do also believe that Stobie pole is different from any of listed type of poles in terms of structures, materials and life, therefore a new section of stobie poles has been created due to this reason.","All codes were extracted from SAP on the completion date for replacements and created date for failures.\n\nVoltage: \n- For FM, coding groups can tell if they are LV or HV, if they are HV then assume highest feeder voltage as noti voltage. For these ones that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown ones\n- For DD, search for noti voltage from notification, if nothing found then assume highest feeder voltage as noti voltage. For these ones that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown ones","Previously we have combined LV, 7.6kV and 11kV poles into a single category < = 11KV; STOBIE. This time we have decided to change it back to AER's default category\n\nIn SAP Extraction (HV) for these with known Feeder IDs, we assume the operating voltage of Pole is the same as the highest voltage of the feeder. \n\n"]
[null,"2.2.1","OTHER BY: \n(Expenditure) Row 137\nPole Refurbished; STOBIE\n","Financial","BEX report","Estimated","We have used \"BU-CMT-000073-02\" - CMT: POLE REPLACE / REFURB - PLANNED in BEX Report L35 to count the cost, which should capture the vast majority of the cost but they are still estimated as crews sometimes book jobs under the wrong code","- Count everything under \"BU-CMT-000073-02\" - CMT: POLE REPLACE / REFURB - PLANNED in BEX Report L35"]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Row 137\nPole Refurbished; STOBIE\n","Non-financial","SAP","Estimated","We are able to get the total number of plating per financial year from SAP. As all the plating data is from SAP Notifications. However it could be possible to line crews to record work under different category so we're unable to confirm this data is 100% accurate.","For Pole Plating  exclude all P4 notis as they are not valid entries.","- Result has been populated under \"Asset Replacement\" columns.\n- All items have been counted as valid items, that includes jobs done in MED date, items with no order numbers etc."]
[null,"2.2.1","OTHER BY: \n(Expenditure) Rows 138-140\nPole Mounted ;> = 22 kV & < = 33 kV ;  < = 60kVA\nPole Mounted ;> = 22 kV & < = 33 kV ; > 60 KVA AND < = 600 KVA \nKiosk Mounted; > = 22 kV & < = 33 kV ; ","Financial","For \nPOLE MOUNTED TRANSFORMER ; > 22 KV ;  < = 60 KVA \nPOLE MOUNTED TRANSFORMER; > 22 KV ;  > 60 KVA AND < = 600 KVA \n\nRefer to row 21\n\nFor\nKiosk Mounted; > = 22 kV & < = 33 kV ; \n\nRefer to row 25","Estimated","Refer to Row 21 and 25 of 2.2 BOP"]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Rows 138-140\nPole Mounted ;> = 22 kV & < = 33 kV ;  < = 60kVA\nPole Mounted ;> = 22 kV & < = 33 kV ; > 60 KVA AND < = 600 KVA \nKiosk Mounted; > = 22 kV & < = 33 kV ; \n","Non-financial","For \nPOLE MOUNTED TRANSFORMER ; > 22 KV ;  < = 60 KVA \nPOLE MOUNTED TRANSFORMER; > 22 KV ;  > 60 KVA AND < = 600 KVA \n\nRefer to row 22\n\nFor\nKiosk Mounted; > = 22 kV & < = 33 kV ; \n\nRefer to row 26","Estimated","Refer to Row 22 and 26 of 2.2 BOP"]
[null,"2.2.1","OTHER BY: \n(Expenditure) Row 139\nRecloser; SWITCHGEAR\n","Financial","SAP Bex Reports and SAP ERP project Data","Estimated","See row 9","The FM and DD numbers are used to lookup the associated costs from SAP BEX/analysis report. The costs for projects are obtained from SAP ERP.","It is assumed that all the costs for the recloser projects finished in the 17/18 year were spent in the 17/18 year. Where projets included much more work than a single recloser replacement, the unit cost from the other recloser replacement projects was used."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Row 139\nRecloser; SWITCHGEAR\n","Non-financial","OOS Spreadsheet + Project data +SAP DDs","Estimated","As there is no Recloser category in the final CAT RIN so we had to insert a separate category for Recloser separately.","OOS Spreadsheet has been manually maintained to capture the unplanned failures. The planned replacements are captured as distribution defects in SAP and in some Project spreadsheets.","Count Recloser Controller, Recloser all as-Recloser","The reported Reclosers quantities include distribution lines + substation"]
[null,"2.2.1","OTHER BY: \n(Expenditure) Row 140\nSectionalizer; SWITCHGEAR\n","Financial","N/A",null,null,"There were no replacements as we do not replace failed sectionalisers."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Row 140\nSectionalizer; SWITCHGEAR\n","Non-financial","OOS Spreadsheet","Estimated","As there is no Sectionaliser category in the final CAT RIN so we had to insert a separate category for  Sectionaliser  separately.","OOS Spreadsheet has been manually maintained to capture most of unplanned failures. The current stratagy is to replace failed sectionalisers with solid links."]
[null,"2.2.1","OTHER BY: \n(Expenditure) Rows 143-144\n>= 11 kV & < ≈ 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n> 22 kV & < ≈ 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n","Financial","Operational Asset Management Ground level switchgear Replacement Spreadsheet (Lorids Asset Replacements .xls) + BEX report\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","In some case the transformer in TC (transformer cubicle)  is replaced when the whole cubicle is replaced. In this case, 50% expenditure is allocated to transformer and 50% is allocated for switchgears. There were no such cases in the 2017/2018 year.\n\nIn BEX report, multiple assets could be booked under the same job, where we believe switching cubicle has the major proportion of this job, we will classify all cost under switching cubicle.","\nOnce valid replacements are identified, their corresponding FM/DD/NW number will be used to seek for all the associated costs from BEX report\n\nBecause we need to split cost when TF is also replaced, we need to do the following to identify these special cases:\n- apply filter on \"Equipment ID\", only select items contains \"TC\"\n- apply filter on \"Replacement Type\", only select items does not contain \"Retrofit\"\nThese items are the items we need to allocate 50% cost to TF and 50% to switchgear\n\nL09 - Line Capacity Upgrades were considered","In case the transformer in TC (transformer cubicle)  is replaced when the whole cubicle is replaced, we assume 50% expenditure is allocated to transformer and 50% is allocated for switchgear ","In some case the transformer in TC (transformer cubicle)  is replaced when the whole cubicle is replaced. In this case, 50% expenditure is allocated to transformer and 50% is allocated for switchgears."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Rows 143-144\n>= 11 kV & < ≈ 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n> 22 kV & < ≈ 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n","Non-financial","Operational Asset Management Ground level switchgear Replacement Spreadsheet (Lorids Asset Replacements .xls) + Operational Asset Management Ground level switchgear Failure Spreadsheet (Plant Failures Data Base Revision C.xlsm)\nL09 (line capacity upgrade) projects transferred to Repex","Estimated","The switches in the TC and Ground Level Switching Cubicles are classified as Load Break Switch\n\nAll data is based on Operational Asset Management Ground Level switchgear Replacement/Failure spreadsheet and some assets transferred from L09 (line capacity upgrade project) \n\nIn the meantime, we are only aware of the number of jobs completed but the total number of repalcement remains unknown, we've assumed 1 replacement per job in RIN preparation.","For Failure:\n- Open Plant Failures Data Base Revision C.xlsm\n- apply filter on years and dates\n- apply filter on type, only select items with \"transformer\" or \"switching cubicle\"\n- Get voltage from \"Feeder Name\"\n- Count the number and allocate to corresponding voltage level\n\nL09 - Line Capacity Upgrades were considered\n\nFor Replacement:\n- Open Lorids Asset Replacements.xls\n- apply filter on years and dates\n- apply filter on type, only select items with \"transformer\" or \"GL cubicle\"\n- Get voltage from \"Voltage\"\n- Count the number and allocate to corresponding voltage level\n","A switching cubicle consists on average 4-6 SWITCHES but when one fails we replace the whole switching cubicle and not each separate switch inside. For the CAT RIN we have counted one Switching Cubicle as one LBS.","In some case the transformer in TC (transformer cubicle)  is replaced when the whole cubicle is replaced. These transformer component replacement will be counted in TF Category. "]
[null,"2.2.1","OTHER BY: \n(Expenditure) Rows 133-139\n˂ = 11 kV ;  Circuit Breaker REFURBISHED\n> 22 kV & < = 33 kV ; Circuit Breaker REFURBISHED\n> 33 kV & < = 66 kV ; Circuit Breaker REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  > 15 MVA and < = 40 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > = 22 kV & < = 33 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; ˂  22 kV ;  >  600 kVA ; Multiple Phase ; REFURBISHED","Financial","SAP (BeX reports - L14, L54, L36)","Actual",null,"1. SAP BeX reports (project numbers and direct costs by financial year) capture refurbishment expenditures, which are allocated to each asset category.\n2. Refurbishment costs are 100% allocated to each respective asset 'Refurbished' category."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Rows 133-139\n˂ = 11 kV ;  Circuit Breaker REFURBISHED\n> 22 kV & < = 33 kV ; Circuit Breaker REFURBISHED\n> 33 kV & < = 66 kV ; Circuit Breaker REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  > 15 MVA and < = 40 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > = 22 kV & < = 33 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; ˂  22 kV ;  >  600 kVA ; Multiple Phase ; REFURBISHED\n","Non-financial","SAP (asset movements and capital project reporting)","Actual",null,"1. Refurbishment numbers reported under this category are the numbers of individual CB/TF assets completed by each program over the financial year.",null,"1. Capitalised repair/refurbishment expenditure is reported by asset group in the ‘DNSP Defined’ refurbishment categories. Works falling into these categories cover a range of capital projects (& general programs of work) to address differnt aspects of asset condition/performance. Reported volumes are the number of assets addressed by each program during the period.\n2. 11kV CB refurbishment numbers are reported where the installation date falls within the relevant financial year. Costs associated with the refurbishment program are reported as incurred. Tasks typically perfromed include bushing replacements, mechanical strip, clean, repairs and replacement of & asbestos contactors for their modern equivalent (captured under safety - included as part of routine refurbishment works from 2017)\n3. Areva (Alstom) S1 CB replacements are reported as 66kV refurbishments from 2017/18. The S1 has a design deficiency that results in flange corrosion and gas leaks managed by a ‘fix on failure’ strategy of changeover/refurbishment . Uneconomically repairable failures (gas leaks, failed HV tests) are reported as failures/replacements\n4. Hawker Siddeley Horizon 33kV CBs replacements are reported as 33kV CB refurbishments when proactively replaced as part of planned manufacturer assisted refurbishment/repair works. Uneconomically repairable Horizon failures in service (gas leaks, failed HV tests) are reported as failures/replacements."]
[null,"2.2.1","OTHER BY: \n(Expenditure) Row 132\nPipework Bus Substation Replacements","Financial","SAP (BeX reports - L14, L54, L36, L13)","Actual",null,"Financial reports were obtained from SAP to provided the direct and component costs for each asset replacement project by financial year.","1. Expenditure on ‘Pipework Bus Substation’ Replacements represents the total expenditure on pipework bus substation asset replacement projects. Expenditure under this category is not separated into component (e.g. TF, switchgear, protection) asset replacement categories.","Replacement of pipework assets are not reported unless their replacement has been captured under a dedicated NW (L13, L14, L36 or L54) project number. SAP assignment errors for projects that are wholly asset replacement are reported under REPEX totals."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Row 132\nPipework Bus Substation Replacements","Non-financial",null,"Actual",null,"Replacement volumes (where they occur in this category) are based on  practical completion and substation commissioning dates.","1. ‘Pipework Bus Substation’ Replacements represent the number of substation sites completed (decommissioned or rebuilt) under the replacement program in the financial year.","1. Replacements are assumed as complete when the new substation construction is energised (or existing structure is retired)"]
[null,"2.2.1","OTHER BY: \n(Expenditure) Row 131\nOTHER - Non Category Substation asset replacement/refurbishment\n","Financial","SAP (BeX reports - L14, L54, L36, L13)","Actual",null,"‘OTHER - Non Category Substation asset replacement/refurbishment’ costs are the sum of:\n1. Safety based (SAP L36) asset replacement expenditure not allocated to TF/CB/Switch categories;\n2. All other substation capital expenditure recorded under planned (L14) and unplanned (L54) replacement/refurbishment SAP budget categories, less all allocation to:\n- TF replacement\n- TF refurbishment\n- CB replacement\n- CB refurbishment\n- Switch replacement\n- Protection replacement\n- SCADA (RTU/TDU) replacement.","1. Dedicated protection & SCADA replacement expenditure (i.e. where not funded as part of CB, TF or Switch replacements) is excluded from this category based on project numbers provided by Network SCADA and Network Protection groups.","1. This category includes a variety of minor replacement programs, one-off substation capital replacement & refurbishment projects across substation assets (excluding CBs & TFs). e.g. poles, insulators and substation civil infrastructure. It also includes a range of miscelaneous expenditures used to manage in service assets & asset failures:\n- It also covers one-off expenditure and a diverse range of asset types with little or no commonality in economic life or age profile.\n- Not all expeditures included in this category relate to physical asset replacements.\n- Expenditure is reported in the financial year incurred and may relate to asset replacements reported outside of the current financial year."]
[null,"2.2.1","OTHER BY: \n(Asset Replacements/Asset Failures) Row 131\nOTHER - Non Category Substation asset replacement/refurbishment\n","Non-financial","Replacement volumes (where they occur in this category) are based on data sources contained in;\n- SAP asset movement records\n- Failure investigation reports\n- SAP FM & SD Notis\n- SAP stock movements\n- Annual asset replacement projects (NW projects captured in SAP L14, L54, L36, L13 categories)\n- Annual capital budget tracking sheets","Actual",null,"1. Replacement and failure numbers reported include the include major, ongoing asset replacement programs within this category:\n- Instrument Transformer replacements (safety),\n- DC (battery bank and charger) replacements,\n- Surge arrester replacements\n- Capacitor can replacements\n- Cable Termination Support replacements","1. Failures and replacement volumes reported in this category are approximated based on the average (annual) number of replacements across the consecutive calendar years that make up the regulatory year reported.","1. This category covers a variety of replacement programs and one-off capitalised replacement/refurbishment works across poles, civil infrastructure, AC/DC auxiliaries and minor primary plant. It also includes capital purchases and other areas of asset management for substations and system spare assets.\n- It covers one-off expenditure and a diverse range of minor asset types with little or no commonality in economic life or age profile.\n- Failure/replacement numbers reported include ongoing programs within this category but do not represent a large proportion of refurbishment & 'one-off' capital expenditures in this line item.\n- Ongoing capital replacement projects are managed by calendar year, replacement numbers by regulatory year are an approximation from planned (calendar year) works programs."]
[]
[null,"2.2.2 - SELECTED ASSET CHARACTERISTICS"]
[null,"2.2.2","TOTAL POLES BY: (feeder Type)\nTotal CBD poles; \nTotal urban poles; \nTotal rural long poles; \nTotal rural short poles","Non-financial","Inspection Data + SAP + Circuit_length.xlsx, Sheet1 (Reg.Reset Team)\n","Estimated","For Asset Replacement, the information we have is the Date of replacement and some of locations, therefore, we need to estimate feeder type for the purpose of RIN.\n\nFor Asset Volumes currently in commission, the number of poles or spans are not 100% known. An estimation on the total volume of poles had to be made and is based on the Inspection Data for poles. The feeder type of poles is not known and has to be estimated.","For Pole Replacement DD+FM catalogue codes for poles were extracted from SAP on the completion date \nThe pole volume was based on inspection data. For the feeder type of the poles, the same ratio was used as reported in the 2016/2017 RIN. The ratio in the 2016/2017 RIN was based on the overhead conductor length in the GIS data.\n\n","For Asset Replacement:\nAssume data required is based on Financial Years\n\nIn SAP Extraction for poles with known Feeder IDs, we assume the feeder type of Pole is the same as the feeder type of the feeder. \n\nFor those that Feeder IDs are missing, we then calculate the feeder type ratio of known items apply to these unknown ones"]
[null,"2.2.2","OVERHEAD CONDUCTORS BY: (conductor length by feeder Type KM)\nConductors CBD;\nConductors urban;\nConductors rural long;\nConductors rural short\n","Non-financial","SAP + Project data - Conductor Replacement Log.xlsx (Operational Asset Management) +  SCONNR_Lengths.xls (Network Records Group) + GIS system","Estimated","For Asset Replacement, the only information we have is Date of replacement and some of locations, therefore, we need to estimate feeder type for the purpose of RIN.\n\nFor Asset Volumes currently in commission, data has to be estimated from GIS Snapshots","All codes were extracted from SAP + Project on the completion date \n\nFor Asset Volumes currently in commission, the ratio of the different feeder types was based on the 2016/2017 RIN which was based on GIS. This ratio was then applied to the current total length in GIS.\n\nALL ASSET VOLUMES CURRENTLY IN COMMISSION ARE GIVEN IN CONDUCTOR LENGTH.","For Asset Replacement:\nAssume data required is based on Financial Years\nIn SAP Extraction for those with known Feeder IDs, we assume the feeder type/material type of conductor is the same as of the feeder. For those that Feeder IDs are missing, we then calculate the feeder type/material type ratio of known items and apply to these unknown ones\n\n"]
[null,"2.2.2","OVERHEAD CONDUCTORS BY: (Conductor length Material Type KM)\nOH Conductor LV ABC;\nOH Conductor steel;\nOH Conductor ACSR;\nOH Conductor AAAC;\nOH Conductor AAC;\nOH Conductor HDBC\n","Non-financial","SAP + Project data - Conductor Replacement Log.xlsx (Operational Asset Management) +  SCONNR_Lengths.xls (Network Records Group) + GIS system","Estimated","For Asset Replacement, the only information we have is Date of replacement and some of locations, therefore, we need to estimate material type for the purpose of RIN.\n\nFor Asset Volumes currently in commission, data has to be estimated from GIS Snapshots","All codes were extracted from SAP + Project on the completion date \n\nFor Asset Volumes currently in commission, the ratio of the different feeder types was based on the 2016/2017 RIN which was based on GIS. This ratio was then applied to the current total length in GIS.\n\nALL ASSET VOLUMES CURRENTLY IN COMMISSION ARE GIVEn IN CONDUCTOR LENGTH.","Material types are determined by feeder ID, in some case, one feeder ID could be assigned with more than one Material types, in such a case, whichever material type is used most will be chosen as the only material type of this feeder id.\nThe total length from GIS includes the services lines which are greater than 20m as it is regarded as part of the LV network.\n\nThe asset volumes in commission by material type were populated by using the ratio of the material for conductors from GIS data and then applying that ratio to the Economic Benchmarking data obtained. "]
[null,"2.2.2","UNDERGROUND CABLES BY: (Cable length by feeder Type KM)\nCable CBD;\nCable urban;\nCable rural long;\nCable rural short\n","Non-financial","SAP + PROJ - Cable Retrench Log.xlsx (Operational Asset Management) +  GIS_Feeder_Lengths_BFRA_SCONNR_20180626.xls (Network Records Group)","Estimated","For Asset Replacement, the only information we have is Date of replacement and some of locations, therefore, we need to estimate feeder type  for the purpose of RIN.\n\nFor Asset Volumes currently in commission, data has to be estimated from GIS Snapshots","All codes were extracted from SAP + Project on the completion date \n\nFor Asset Volumes currently in commission, the ratio of the different feeder types was based on the 2016/2017 RIN which was based on GIS. This ratio was then applied to the current total length in GIS.\n\nALL ASSET VOLUMES CURRENTLY IN COMMISSION ARE ROUTE LENGTH  AND ARE USED IN ECONOMIC BENCHMARKING RIN","For Asset Replacement:\nAssume data required is based on Financial Years\n\nIn SAP Extraction for those with known Feeder IDs, we assume the feeder type of conductor is the same as of the feeder. \nFor these that Feeder IDs are missing, we then calculate the feeder type ratio of known items apply to these unknown ones"]
[null,"2.2.2","TRANSFORMERS BY: (Total MVA)\nTotal MVA replaced;\nTotal MVA disposed of\n(Line Assets)","Non-financial","NOC-LOG, Transformer Database, SAP, Operational Asset Management Ground level switchgear Replacement Spreadsheet+ Operational Asset Management Ground level switchgear failure spreadsheet, Substation group data","Estimated","The information we have from SAP doesn’t state the transformer size so the transformer database spreadsheet is used to give us this. In some cases the transformer databse does not give the transformer size in which case it  needs to be estimated. Refer Row 22.\n","The NOC Log is used to determine the failed transformers. The KVA of failed transformers is estimated using the data in the TF database.\nThe SAP DD notifications give the planned replacements. The planned replacement KVA is estimated using the TF database. The total replacement KVA is the failed KVA + Planned Replacement KVA.","The assumption is made that we always replace transformers like for like.","We have combined the line transformers MVA and the substation transformers MVA in the 2.2.2 RIN for Total MVA disposed and replaced "]
[null,"2.2.2","TRANSFORMERS BY: (Total MVA)\nTotal MVA replaced;\nTotal MVA disposed of\n(Substation Assets)","Non-financial",null,"Actual",null,"-The ‘Total MVA Replaced’ is the sum of nameplate MVA capacity of TF installations as part of repex projects over the period.\n'-The ‘Total MVA Disposed Of’ is the sum of nameplate MVA capacity of TFs decommissioned as part of repex projects over the period.\n",null,"1. ‘Total MVA Replaced’ (interpreted as the total network capacity installed through repex projects) is the sum of MVA capacity installed on the network in the period, including MVA installed as part of Pipework Bus Substation replacements.\n2. ‘Total MVA Disposed Of’ (interpreted as the total network capacity removed through repex projects) is the sum of MVA capacity removed (& not necessarily replaced) in the period, including MVA removed as part of Pipework Bus Substation asset replacements."]

{"sheet":"2.3(a)(b) Augex","index":2,"n_rows":28,"n_cols":10,"rows_kept":28,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.3 REPEX (General Comments)"]
[null,2.2999999999999998,"2.3 Augex tab general comments","Financial","N/A","N/A",null,"The information presented in the 2.3 Augex tabs (ie 2.3a and 2.3b) relate to network augmentation projects and expenditure only.\n\nGifted assets (clause 7.1(c)) and connection assets (clause 7.1(e)) have not been included in this RIN response. No material project was engaged to a related party contract for the period covered by this RIN.\n\nCosts allocated to the augmentation category across each Regulatory Year have been in accordance with the approved cost allocation methodology (Schedule 2, Appendix E, clause 1.1). \n\nClauses 7.2 - 7.4 of the RIN require asset volume data to be presented on a 'Project Close' basis.\n\nProject overheads have been separated and excluded from the financial data reported in the Augex information supplied as detailed in the methodology (clause 1.12)."]
[null,2.2999999999999998,"2.3 Augex tab general comments","Non-financial","N/A","N/A",null,"All capital expenditure has been converted from SAPN Financial Year (Calendar Year) to a regulatory / financial year basis. The information reported within this RIN, reflects SA Power Networks' total augmentation capital expenditure over the requested period.  SAPN has identified the month and year of each financial transaction and converted this data into regulatory financial year reported in the BeX report.\n\nNominal dollars have been used throughout regulatory template 2.3 with the exception of tables 2.3.1 and 2.3.2 (clause 1.9).  Financial values reported within Tables 2.3.1 and 2.3.2 are reported on a project close basis in 2017/18 dollars as per clause 7.2(c) of the RIN.  For consistency across all tables used in the RIN, the calculations used to convert nominal dollars to 2017/18 dollars have been undertaken by SA Power Networks' finance department and have been applied as detailed elsewhere within the Basis of Preparation submission (clause 1.10).  The conversion from nominal dollars to real 2017/18 dollars is based on the financial breakdown of nominal dollars for each project provided by the Network Planning Department for those projects meeting the criterion for individual reporting."]
[null,"2.3.1 - AUGEX ASSET DATA - SUBTRANSMISSION SUBSTATIONS, SWITCHING STATIONS AND ZONE SUBSTATIONS"]
[null,"2.3.1 ","Rows 14 to 65 - Projects above the threshold","Both","SAP,\nProject financial reports,\nAsset Records","N/A",null,"A list of capital projects finalised in the 2017 - 2018 period and exceeding $5 million threshold for substations and sub-transmission lines was compiled from historic capital budget's actual spend - no such augmentation projects exist for the reporting period and therefore values have only been submitted within the non-material category."]
[null,"2.3.1 ","Rows 66 - non-material projects","Financial","SAP\nProject financial reports","Actual  ",null,"For projects less than the relevant cost thresholds, annual costs were determined for each financial year based on the total expenditure within SA Power Networks' budget category definitions (ie L code).  Summations were produced from the relevant BEx report for each budget category, minus the costs of those listed projects in Tables 2.3.1 and 2.3.2 or those projects still known to be in progress (ie incomplete).\nThese ’residual‘ costs were allocated to substations, sub-transmission, HV distribution and LV distribution as applicable on a real or nominal dollars as per clause 7.2(c), 7.3(c) and 7.4(b) of the RIN.\nThe following budget categories were summated for each financial year (excluding major project costs or those already accounted for within other RIN categories (eg Repex)) and provided within the Augex tab on a financial year basis:\ni) L13 – Substation works (residual of those works not explicitly listed);\nii) L09 – Sub-transmission line / distribution feeder / LV feeder works (residual of those works not explicitly listed);\niii) L33 – Power Line Environment Committee (PLEC);\niv) L36 – Safety (excluding those costs contained within other expenditure categories eg Repex);\nv) L38 – Environment; and\nvi) L39 – Reliability.Items i, iv, v and vi were entered in table 2.3.1 as 'other' projects. Item ii projects were entered in table 2.3.2 as 'other' or tables 2.3.3.1 and 2.3.3.2, while item iii costs were included within Table 2.3.3.1. "]
[null,"2.3.1 ","Rows 66 - non-material projects (cont.)","Financial","SAP\nProject financial reports","Actual",null,"Distribution transformer costs associated with Quality of Supply projects have been included in tables 2.3.3.1, 2.3.3.2 and 2.3.4.\nSummary information in tables 2.3.3.1, 2.3.3.2, and descriptor metrics for units upgraded and table 2.3.4 were calculated on a individual project basis prior to aggregating.  SA Power Networks’ systems do not presently provide a method of readily populating the circuit length of augmentation (ie new) or upgraded HV feeders.  An estimate was used based on the assumption that only those projects explicitly listed (ie > $0.5 million) will contain new feeder augmentations while all projects below this value represent feeder upgrade projects.\nFor Substation and Sub-transmission Projects less than the $5 million threshold, the penultimate row in tables 2.3.1 and 2.3.2 were completed by calculating the difference between the total augmentation expenditure as reported in the Bex Report with the total of project above the threshold. A similar process was followed to calculate values for non-material HV and LV Feeders in table 2.3.3.2 and to fully populate table 2.3.4."]
[null,"2.3.2 - AUGEX ASSET DATA - SUBTRANSMISSION LINES"]
[null,"2.3.2\n","Rows 75 to 128 - projects above the threshold","Both","SAP,\nProject financial reports,\nAsset Records","N/A",null,"A list of capital projects finalised in the 2017 - 2018 period and exceeding $5 million threshold for substations and sub-transmission lines was compiled from historic capital budget's actual spend - no such augmentation projects exist for the reporting period and therefore values have only been submitted within the non-material category."]
[null,"2.3.2\n","Rows 130 - non-material projects","Financial","SAP\nProject financial reports","Actual",null,"Refer to non-material projects methodology for table 2.3.1"]
[null,"2.3.3 - AUGEX DATA - HV/LV FEEDERS AND DISTRIBUTION SUBSTATIONS"]
[null,"2.3.3 (2.3(b) Augex)","Sub-transmission line length metrics","Non-financial","Project specific line design pole schedules & SAP material reports","Estimated",null,"Project design line schedules and SAP material reports were used to determine alterations in overhead and underground added or upgraded as a result of the relevant augmentation project.  For the purposes of the RIN, the length of conductor upgraded was taken to represent that conductor which was replaced.  Where a project involved the \"uprating\" of the line's design temperature, no length was provided."]
[null,"2.3.4 - AUGEX DATA - TOTAL EXPENDITURE"]
[null,"2.3.4 \n(2.3(b) Augex)","Row 38 - Subtransmission Substations","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  Howeveer the total reconciles to the BeX reports.","Subtransmission substation data is primarily sourced from the BeX report L13 though some project data has been sourced from budget categories L09, L13, L36, L38, L39 and L03.  After overheads and land have been removed the total spend for each year are summed to the appropriate cells.  The data includes all spend on BeX projects for the reporting period which differs from those reported in table 2.3.1 which only includes projects that are finalised during the reporting period."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 39 - Subtransmission Lines","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","Subtransmission line data is primarily sourced from the BeX report L09 though project data may also be sourced from budget categories L13, L36 and L03. After overheads and land have been removed the total spend for each year are summed to the appropriate cells.  The data includes all spend on BeX projects for the reporting period which differs from those reported in table 2.3.2 which only includes projects that are finalised during the reporting period."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 40 - HV Feeder projects","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","HV Feeder projects were identified manually from BeX report L09 and L33.  As L09 is also the source for Subtransmission lines, LV Feeders and Distribution substation data, the HV Feeder category is the difference between identified LV project from L09 and QS project spend provided via another BeX report for QS.  "]
[null,"2.3.4 \n(2.3(b) Augex)","Row 41 - HV Feeder Land and Easement Purchases","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","HV Feeder Land purchases were identified visually and summed to the relevant cells."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 42 - Distribution Substations","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","Distribution substation augmentations (Pole and Pad) were sourced from analysis of those Quality of Supply (QoS) projects contained within budget category L09. This analysis examined those work orders which contained the ordering of either pole or pad mounted transformers.  These costs were then summated (respectively) to arrive at the costs associated with the upgrade of existing or installation of new distribution substations."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 43 - Distribution Substations Land","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","No data was identified for this category"]
[null,"2.3.4 \n(2.3(b) Augex)","Row 44 - LV Feeder ","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required based on those QoS projects performed in 2017/18.  However the total reconciles to the BeX reports.","LV Feeder expenditure was calculated based upon the number of kms added or upgraded as a ratio of the total HV and LV augmentation undertaken under a particular project.  Where a project involved the installation or upgrade of a distribution transformer, the material cost of the transformer was subtracted from the total project cost and multiplied by the ratio of LV to HV augmentation."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 45 - LV Feeder land and easements","Financial","SAP reports L03, L09, L13, L33, L36, L38 and L39","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","LV Feeder land and easements costs were seperately identified by the Quality of Supply group for each year in the reporting period.  No such costs were identified."]
[null,"2.3.4 \n(2.3(b) Augex)","Row 46 - Other Assets","Financial","SAP report L34.","Estimated","Data is not stored directly in the categories that the AER require and manual sorting and calculation has been required.  However the total reconciles to the BeX reports.","Budget categories such as PLEC - BeX L33, Safety - BeX L36 (augmentation projects visually identified), Environment - BeX L38 and Reliability - BeX L39 have been associated with either Substation, Sub-transmission, HV Feeder, LV Feeder or Distribution Substation categories."]
[null,"2.3.4 \n(2.3(b) Augex)","Table reconciliation","Financial",null,null,null,"Clause 7.7(b) requires SA Power Networks to explain how the sum of the asset group augmentation expenditures reconciles to the augmentation expenditure in tables 2.3.1 to 2.3.5.  The following points are provided to assist with that reconcilliation:\nTable 2.3.3.2: \n - The sum of the HV Feeders row (table 2.3.4) is the sum of all HV Feeder projects costs (cells D24:D26) in table 2.3.3.2.  The values in table 2.3.4 and table 2.3.3.2 are expressed in nominal terms.\n - The sum of the LV Feeders row (table 2.3.4 (cells M178) in the 2.3 Augex tab) is the sum of all LV Feeder projects costs (cells M155:M157) in table 2.3.3.2.  The values in table 2.3.4 and table 2.3.3.2 are expressed in nominal terms.\n - The sum of the Distribution transformers row (table 2.3.4 (cells M176) in the 2.3 Augex tab) is the sum of all Distribution Transformer projects costs (cells M158:M160) in table 2.3.3.2.  The values in table 2.3.4 and table 2.3.3.2 are expressed in nominal terms.\nTable 2.3.4: \n - The sum of the HV Feeders - Land Purchases and Easements row (table 2.3.4, cells M175), does not appear in other tables and therefore cannot be reconciled within the regulatory template 2.3.\n - The sum of the Distribution Transformers - Land Purchases and Easements row (table 2.3.4, cells M177), does not appear in other tables and therefore cannot be reconciled within the regulatory template 2.3.\n - The sum of the LV Feeders-Land and Easements and Other Assets rows (M179:M180) do not appear in other tables and therefore cannot be reconciled within the regulatory template 2.3."]

{"sheet":"2.5 Connections","index":3,"n_rows":76,"n_cols":10,"rows_kept":76,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.5.1 - DESCRIPTOR METRICS"]
[null,"2.5.1","RESIDENTIAL\nUnderground Connections (0's) (E13)","Non-financial","SAP & CIS O/V","Estimated","Based on scoping information, however assumptions are made for when no service type is available","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003) \nUsed SAP status and used SAP start / End Date","Assumed that the Service types of - Use Existing or Unknown are for Overhead Connections"]
[null,"2.5.1","RESIDENTIAL \nOverhead Connections (0's) (E14)","Non-financial","SAP & CIS O/V","Estimated","Based on scoping information, however assumptions are made for when no service type is available","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003) Used SAP status and used SAP start / End Date","Assumed that the Service types of - Use Existing or Unknown are for Overhead Connections"]
[null,"2.5.1","RESIDENTIAL \nDistribution Substations Installed (MVA added) (E15)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","The project sub category is not documented (i.e. Residential, Commercial/Industrial, Subdivision, Embedded Generation). Subcategory has been interpreted using the project name and number. The transformers allocated to each project have been identified from SAP.  The transformers associated with connections completed in the year are summed to provide total MVA added.","Source project definition from BEX analyser and transformer data from SAP cost element reporting for the project definition. Interpret subcategory based on project name and project number into relevant category.  Calculate total MVA from actual transformer stock item data in cost element report.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that Transformers have been correctly assigned to the project. Additional MVA based on total MVA of all T/F ordered. Some of these T/Fs are used for upgrades, and are not all used for new T/F stations. Subcategory has been interpreted from the project name and project number. "]
[null,"2.5.1","RESIDENTIAL \nDistribution Substations Installed (0's) (E16)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","Project sub category is not documented, the subcategory has been interpreted using the project name and number. Date of installation is not documented. Date of installation has been based on whether the connection has been made in the relevant year.","Source project definition from BEX and transformer order data from SAP. Interpret subcategory based on project name and project number. Calculate total substations installed based on Project Definition.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that T/F orders have been correctly assigned to projects."]
[null,"2.5.1","RESIDENTIAL\nDistribution Substations Installed Total Spend ($0's) (E17)","Financial","SAP, Building Block Estimate, RealEst","Estimated","Installation costs for each substation is not documented. Purchase cost of T/F is known however, the project cost also includes other extension and connection cost. Substation installation cost has been estimated using building block and RealEst data. Number and size of substation has been based on SAP data and BEX Analyser.","Source Transformer allocation from BEX Analyser. Interpret subcategory based on project name and project number. Filter data based on project subcategory. Estimate substation installation cost using building block and RealEst. Calculate total substation installation cost based on filtered data and estimate.  ","Assumed that projects have been recorded in SAP correctly including project name and project number. Assumed that T/F orders have been correctly entered into SAP.  Additional MVA based on total MVA of all T/F booked to projects. Some of these T/F are used for upgrades, and are not all used for new T/F stations. Substation installation cost has been estimated using building block and RealEst. Substation installation cost includes network labour, field services labour, external resources, materials, overheads, Average transformer cost is included in calculation."]
[null,"2.5.1","RESIDENTIAL\nAugmentation HV (Net Circuit KM Added) (E18)","Non-financial","SAP BEX reporting and confirmation from Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","RESIDENTIAL\nAugmentation HV (Total Spend $0's) (E19)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","RESIDENTIAL\nAugmentation LV (Net Circuit KM Added) (E20)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","RESIDENTIAL\nAugmentation LV (Total Spend $0's) (E21)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","RESIDENTIAL\nMean Days to Connect Residential Customer with LV Single Phase Connection (0's) (E22)","Non-financial","SAP  ","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","CC Notification transaction in SAP with appropriate budget codes required. ","Assumptions were made that the estimated number of single phase connections are a percentage of the total number.   The number recorded is actual calendar days."]
[null,"2.5.1","RESIDENTIAL\nVolume of GSL Breaches for Residential Customers (0's) (E23)","Non-financial","SAP, CC Notifications Database","Estimated","There is considerable manual interrogation of report to establish actual records.","Report is received via work batch user on a weekly basis and then each CC notification (new supply only) is vetted to confirm is payment is warranted. Information is derived from SAP CC (REX) notifications","Assumptions are made when the data is reviewed; it is assumed the customer has disputed the connection date provided by SA Power Networks. The number recorded is actual number of GSL breaches"]
[null,"2.5.1","RESIDENTIAL\nVolume Customer Complaints Relating to Connection Services (0's) (E24)","Non-financial","SAP, CC Notifications Database","Estimated","No Correlation between capture of complaint and the SAP notification","This information is derived from SAP CARE and has no relation to SAP Notification payments, however it is possible that the same customer has complained to the Customer Response team about the SAP CC notification","There is no assumption made about a customer complaint, however there is currently no known relationship between a CARE complaint associated with connections and the dispute raised against the SAP CC notification as the functions are managed by separate business groups. The number recorded is the actual volume of customer complaints.","Connection complaints relate to appointment timeframe, application process and procedure only"]
[null,"2.5.1","RESIDENTIAL\nGSL Payment ($000's) (E25)","Financial","Manually gathered information","Actual",null,"Payments are derived manually based on the information provided weekly via the work batch user reports. Payments are generated through raising financial invoice in SAP, cheque is generated and sent manually to the customer with accompanying letter. ","Payments are derived from interrogation of the notification. Assumptions are made about the payments generated, but only as far as the interrogation of records supports a payment."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nConnections (0's) (E26)","Non-financial","SAP & CIS O/V","Estimated","Based on scoping information, however assumptions are made for when no service type is available","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003)  Used SAP status and used SAP start / End Date","Assumed that the Service types of - Use Existing or Unknown are for Overhead Connections"]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nOverhead Connections (0's) (E27)","Non-financial","SAP & CIS O/V","Estimated","Based on scoping information, however assumptions are made for when no service type is available","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003)  Used SAP status and used SAP start / End Date","Assumed that the Service types of - Use Existing or Unknown are for Overhead Connections"]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nDistribution Substations Installed (MVA added) (E28)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","The project sub category is not documented (i.e. Residential, Commercial/Industrial, Subdivision, Embedded Generation). Subcategory has been interpreted using the project name and number. The transformers allocated to each project have been identified from SAP.  The transformers associated with connections completed in the year are summed to provide total MVA added.","Source project definition from BEX analyser and transformer data from SAP cost element reporting for the project definition. Interpret subcategory based on project name and project number into relevant category.  Calculate total MVA from actual transformer stock item data in cost element report.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that Transformers have been correctly assigned to the project. Additional MVA based on total MVA of all T/F ordered. Some of these T/Fs are used for upgrades, and are not all used for new T/F stations. Subcategory has been interpreted from the project name and project number. "]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nDistribution Substations Installed (0's) (E29)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","Project sub category is not documented, the subcategory has been interpreted using the project name and number. Date of installation is not documented. Date of installation has been based on whether the connection has been made in the relevant year.","Source project definition from BEX and transformer order data from SAP. Interpret subcategory based on project name and project number. Calculate total substations installed based on Project Definition.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that T/F orders have been correctly assigned to projects."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nDistribution Substations Installed Total Spend ($0's) (E30)","Financial","SAP, Building Block Estimate, RealEst","Estimated","Installation costs for each substation is not documented. Purchase cost of T/F is known however, the project cost also includes other extension and connection cost. Substation installation cost has been estimated using building block and RealEst data. Number and size of substation has been based on SAP data and BEX Analyser.","Source Transformer allocation from BEX Analyser. Interpret subcategory based on project name and project number. Filter data based on project subcategory. Estimate substation installation cost using building block and RealEst. Calculate total substation installation cost based on filtered data and estimate.  ","Assumed that projects have been recorded in SAP correctly including project name and project number. Assumed that T/F orders have been correctly entered into SAP.  Additional MVA based on total MVA of all T/F booked to projects. Some of these T/F are used for upgrades, and are not all used for new T/F stations. Substation installation cost has been estimated using building block and RealEst. Substation installation cost includes network labour, field services labour, external resources, materials, overheads, Average transformer cost is included in calculation."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nAugmentation HV (Net KM Added) (E31)","Non-financial","SAP BEX reporting and confirmation from Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nAugmentation HV (Total Spend $0's) (E32)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nAugmentation LV (Net Circuit KM Added) (E33)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","COMMERCIAL/INDUSTRIAL\nAugmentation LV (Total Spend $0's) (E34)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","SUBDIVISION\nUnderground Connections (0's) (E35)","Non-financial","SAP - BEX Analyser Project list - verification by Project Officers.","Estimated","The project sub category is not documented but has been investigated by Project Officers using the project name and number to determine connection type. ","Use BEX analyser to get the project numbers and ask Project Officer Responsible to provide connection information.","Assumed that where the developer installs underground assets the connection type is underground."]
[null,"2.5.1","SUBDIVISION \nOverhead Connections (0's) (E36)","Non-financial","SAP - BEX Analyser Project list - verification by Project Officers.","Estimated","The project sub category is not documented but has been investigated by Project Officers using the project name and number to determine connection type. ","Use BEX analyser to get the project numbers and ask Project Officer Responsible to provide connection information.","Assumed that where the developer installs overhead assets the connection type is Overhead"]
[null,"2.5.1","SUBDIVISION\nDistribution Substations Installed (MVA added) (E37)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","The project sub category is not documented (i.e. Residential, Commercial/Industrial, Subdivision, Embedded Generation). Subcategory has been interpreted using the project name and number. The transformers allocated to each project have been identified from SAP.  The transformers associated with connections completed in the year are summed to provide total MVA added.","Source project definition from BEX analyser and transformer data from SAP cost element reporting for the project definition. Interpret subcategory based on project name and project number into relevant category.  Calculate total MVA from actual transformer stock item data in cost element report.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that Transformers have been correctly assigned to the project. Additional MVA based on total MVA of all T/F ordered. Some of these T/Fs are used for upgrades, and are not all used for new T/F stations. Subcategory has been interpreted from the project name and project number. "]
[null,"2.5.1","SUBDIVISION\nDistribution Substations Installed (0's) (E38)","Non-financial","SAP cost element report, BEX Analyser report for project number, Confirmation of project status from nominated officer","Estimated","Project sub category is not documented, the subcategory has been interpreted using the project name and number. Date of installation is not documented. Date of installation has been based on whether the connection has been made in the relevant year.","Source project definition from BEX and transformer order data from SAP. Interpret subcategory based on project name and project number. Calculate total substations installed based on Project Definition.","Assumed that projects have been recorded in SAP correctly, such as project name and project number. Assumed that T/F orders have been correctly assigned to projects."]
[null,"2.5.1","SUBDIVISION\nDistribution Substations Installed Total Spend ($0's) (E39)","Financial","SAP, Building Block Estimate, RealEst","Estimated","Installation costs for each substation is not documented. Purchase cost of T/F is known however, the project cost also includes other extension and connection cost. Substation installation cost has been estimated using building block and RealEst data. Number and size of substation has been based on SAP data and BEX Analyser.","Source Transformer allocation from BEX Analyser. Interpret subcategory based on project name and project number. Filter data based on project subcategory. Estimate substation installation cost using building block and RealEst. Calculate total substation installation cost based on filtered data and estimate.  ","Assumed that projects have been recorded in SAP correctly including project name and project number. Assumed that T/F orders have been correctly entered into SAP.  Additional MVA based on total MVA of all T/F booked to projects. Some of these T/F are used for upgrades, and are not all used for new T/F stations. Substation installation cost has been estimated using building block and RealEst. Substation installation cost includes network labour, field services labour, external resources, materials, overheads, Average transformer cost is included in calculation."]
[null,"2.5.1","SUBDIVISION\nAugmentation HV (Net KM Added) (E40)","Non-financial","SAP BEX reporting and confirmation from Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","SUBDIVISION\nAugmentation HV (Total Spend $000's) (E41)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","SUBDIVISION\nAugmentation LV (Net Circuit KM Added) (E42)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.","Assumption is that the additional conductor was added to the network at the same time that the connection was made, this may vary slightly.  ","The assumptions also rely on the Project Officer providing accurate information."]
[null,"2.5.1","SUBDIVISION\nAugmentation LV (Total Spend $0's) (E43)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Use BEX analyser to select projects that have expenditure in the relevant year then obtain information on the length of HV or LV mains installed.  Multiply this by the average cost per Km of construction type.  The Average cost per KM was derived from Realest and is an estimate of the installation cost of HV overhead and underground conductors and cables.","Assumptions were made regarding the average type of conductors used for augmentation and therefore the average cost per km to install.  It is assumed that a cable or conductor is installed when the connection is completed.","The assumptions are based on relevant experience and an overview the type of projects being detailed and the project officers providing correct information."]
[null,"2.5.1","SUBDIVISION\nCost per Lot ($) (E44)","Financial","SAP - BEX Analyser Project list - verification by Project Officers.","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source residential development project data from  the BEX Report in SAP. Project Officers determine the number of lots connected in 2014/15.  Total costs attributed to Development projects is divided by the number of lots connected to get the average.","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet. Total costs attributed to these projects has been used."]
[null,"2.5.1","EMBEDDED GENERATION\nUnderground Connections (0's) (E45)","Non-financial","SAP","Estimated","Based on scoping information, however assumptions are made for ratio of mix between connection and project data","Determination of underground vs. Overhead not possible due to high levels of 'blank' data. Totals given for both overhead and underground. This total is split as overhead and underground in the same ratio percentage as a regular residential connection. ","Assumed connection type is in the same ratio as for residential new connections"]
[null,"2.5.1","EMBEDDED GENERATION\nOverhead Connections (0's) (E46)","Non-financial","SAP","Estimated","Based on scoping information, however assumptions are made for ratio of mix between connection and project data","Determination of underground vs. Overhead not possible due to high levels of 'blank' data. Totals given for both overhead and underground. This total is split as overhead and underground in the same ratio percentage as a regular residential connection. ","Assumed connection type is in the same ratio as for residential new connections"]
[null,"2.5.1","EMBEDDED GENERATION\nDistribution Substations Installed (MVA added) (E47)","Non-financial","SAP, interpretation of project name and project number","Actual",null,"One distribution substation was recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. "]
[null,"2.5.1","EMBEDDED GENERATION\nDistribution Substations Installed (0's) (E48)","Non-financial","SAP, interpretation of project name and project number","Actual",null,"One distribution substation was recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. "]
[null,"2.5.1","EMBEDDED GENERATION\nDistribution Substations Installed Total Spend ($0's) (E49)","Financial","SAP, interpretation of project name and project number","Actual",null,"One distribution substation was recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. "]
[null,"2.5.1","EMBEDDED GENERATION\nAugmentation HV (Net KM Added) (E50)","Non-financial","SAP","Actual",null,"No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. No augmentation or extension were allocated to projects in this subcategory."]
[null,"2.5.1","EMBEDDED GENERATION\nAugmentation HV (Total Spend $0's) (E51)","Financial","SAP","Actual",null,"No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. No augmentation or extension were allocated to projects in this subcategory."]
[null,"2.5.1","EMBEDDED GENERATION\nAugmentation LV (Net Circuit KM Added) (E52)","Non-financial","SAP","Actual",null,"No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. No augmentation or extension were allocated to projects in this subcategory."]
[null,"2.5.1","EMBEDDED GENERATION \nAugmentation LV (Total Spend $0's) (E53)","Financial","SAP","Actual",null,"No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required.  Project sub category is not documented. Subcategory has been interpreted using the project name and number. No augmentation or extension were allocated to projects in this subcategory."]
[null,"2.5.2 - COST METRICS BY CONNECTION CLASSIFICATION"]
[null,"2.5.2","RESIDENTIAL \nSimple Connection LV ($0's) (D60)","Financial","CIS/OV and BEX reports","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003)  All costs from L01 Bucket in SAP allocated across residential and simple commercial connections in line with number of connections.","Assumed that the breakdown of costs are based on the same ratio of residential to commercial connections from cc notification report."]
[null,"2.5.2","RESIDENTIAL \nSimple Connection LV (000's) (E60)","Non-financial","SAP","Actual",null,"Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003) "]
[null,"2.5.2","RESIDENTIAL \nComplex Connection LV ($0's) (D61)","Financial","CIS/OV and BEX reports","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). Compare and interpret report and those with associated upstream works. Costs for these projects were calculated in SAP with the Project reporting transaction. ","Any residential connection that has associated pole, T/F etc. works were considered complex. Allocation from L01, L02 and L05 Bucket in line with total number of projects"]
[null,"2.5.2","RESIDENTIAL \nComplex Connection LV (000's) (E61)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). Compare and interpret report and those with associated upstream works. ","Any residential connection that has associated pole, T/F etc. works were considered complex."]
[null,"2.5.2","RESIDENTIAL \nComplex Connections HV ($0's) (D62)","Financial","SAP","Actual",null,"There are no HV connections to residential premises within the SA Power Networks distribution system."]
[null,"2.5.2","RESIDENTIAL \nComplex Connections HV (000's) (E62)","Non-financial","SAP","Actual",null,"There are no HV connections to residential premises within the SA Power Networks distribution system."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nSimple Connections LV ($0's) (D63)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003).. Apportioned total costs based on project approval. ","Assumed that the breakdown of costs are based on the same ratio of residential to commercial connections from cc notification report. Costs were split in same proportion as project approval costs. Allocation from L01, L02 and L05 Bucket in line with total number of projects."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nSimple Connections LV (000's) (E63)","Non-financial","SAP","Actual",null,"Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). "]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at LV, Minor HV Works) ($0's) (D64)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). BEX list of projects interpreted and direct costs taken from there.","Any commercial connection that has associated pole, T/F or cable works were considered complex.  From a master list of projects the ratio of projects requiring augmentation was determined by consulting the project officer to determine those with and without augmentation. Allocation from L01, L02 and L05 Bucket in line with total number of projects."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at LV, Minor HV Works) (000's) (E64)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). Master list of projects from BEX Analyser interpreted.  ","Any commercial connection that has associated pole, T/F or cable works were considered complex.  From a master list of projects, the projects not requiring augmentation was determined."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at LV, Upstream Asset Works) ($0's) (D65)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.\n","BEX list of projects interpreted and direct costs taken from there.","Any commercial connection that has associated pole, T/F or cable works were considered complex.  From a master list of projects the ratio of projects requiring augmentation was determined by consulting the project officer to determine those with and without augmentation. Allocation from L01, L02 and L05 Bucket in line with total number of projects."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at LV, Upstream Asset Works) (000's) (E65)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes (CCC-001, CCC-002, CCC-003). Master list of projects from BEX Analyser interpreted.  ","Any commercial connection that has associated pole, T/F or cable works were considered complex.  From a master list of projects, the projects requiring augmentation was determined."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at HV) ($0's) (D66)","Financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","BEX list of projects interpreted and direct costs taken from there.","The projects where HV connections were required were assumed from the master list of projects and HV metering group for that year."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection HV (Customer Connected at HV) (000's) (E66)","Non-financial","SAP","Actual",null,"Interpret information from BEX Analyser to identify projects in this category.  ","The projects where HV connections were required were assumed from the master list of projects for that year."]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection Sub-Transmission ($0's) (D67)","Financial","SAP","Actual"]
[null,"2.5.2","COMMERCIAL/INDUSTRIAL\nComplex Connection Sub-Transmission (000's) (E67)","Non-financial","SAP","Actual",null,"Interpret information from BEX Analyser to identify projects in this category.  "]
[null,"2.5.2","SUBDIVISION\nComplex Connection LV ($0's) (D68)","Financial","SAP     Confirmed by Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source project data from Bex Report. Data distributed to NPO's for completing a spreadsheet using information sourced from the project folders and project designs. Costs extracted from BEX Report.","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","SUBDIVISION\nComplex Connection LV (000's) (E68)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source residential development project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","SUBDIVISION\nComplex Connection HV (No Upstream Asset Works) ($0's) (D69)","Financial","SAP     Confirmed by Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source project data from Bex Report. Data distributed to NPO's for completing a spreadsheet using information sourced from the project folders and project designs. Costs extracted from BEX Report.","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","SUBDIVISION\nComplex Connection HV (No Upstream Asset Works) (000's) (E69)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source residential development project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","SUBDIVISION\nComplex Connection HV (With Upstream Asset Works) ($0's) (D70)","Financial","SAP     Confirmed by Project Officers","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source project data from Bex Report. Data distributed to NPO's for completing a spreadsheet using information sourced from the project folders and project designs. Costs extracted from BEX Report.","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","SUBDIVISION\nComplex Connection HV (With Upstream Asset Works) (000's) (E70)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source residential development project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","Assumed that projects have been recorded in SAP correctly. Assume that NPO's have correctly entered data into spreadsheet and understood definitions for the data requested."]
[null,"2.5.2","EMBEDDED GENERATION\nSimple Connections LV ($0's) (D71)","Financial","SAP, Project Cost Reports, BEX Analyser","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes CCC-003 ","Assumed that the costs are listed in BEX Reports are accurate.  Some standard meters included in EG category have been removed.  The numbers reflect less than 30kW installations."]
[null,"2.5.2","EMBEDDED GENERATION\nSimple Connections LV (000's) (E71)","Non-financial","SAP","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Input from SAP, CC notification transaction, enter appropriate budget codes CCC-003 "," The numbers reflect less than 30kW installations."]
[null,"2.5.2","EMBEDDED GENERATION\nComplex Connections HV (small capacity) ($0's) (D72)","Financial","SAP, Project Cost Reports, BEX Analyser","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Source embedded generation project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","This category generally contains projects of between 30kW and 200kW"]
[null,"2.5.2","EMBEDDED GENERATION\nComplex Connection HV (Small Capacity) (000's) (E72)","Non-financial","SAP, Project Cost Reports, BEX Analyser","Actual",null,"Source embedded generation project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","This category generally contains projects of between 30kW and 200kW"]
[null,"2.5.2","EMBEDDED GENERATION\nComplex Connection HV (Large Capacity) ($0's) (D73)","Financial","SAP, Project Cost Reports, BEX Analyser","Actual",null,"Source embedded generation project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","This category contains projects over 200kW.  The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require"]
[null,"2.5.2","EMBEDDED GENERATION\nComplex Connection HV (Large Capacity) (000's) (E73)","Non-financial","SAP, Project Cost Reports, BEX Analyser","Actual",null,"Source embedded generation project data from SAP through BEX. Data distributed to NPO's for completing spreadsheet using information sourced from the project folders and project designs. ","This category contains projects over 200kW"]

{"sheet":"2.6 Non-Network","index":4,"n_rows":30,"n_cols":10,"rows_kept":30,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.6.1 - NON-NETWORK EXPENDITURE"]
[null,"OPEX"]
[null,"2.6.1","IT & COMMUNICATIONS\nF12, F13, F14","Financial","SAP Functional Area / Activities report. ","Actual","N/A","Actual's data derived by executing SAP P&L drill down report then categorising the expenditure as either Recurrent, Non-recurrent or Client Devices.","All Actual's data sourced from SAP.  Expenditure is categorised as either Recurrent, Non-recurrent or Client Devices as defined by AER definitions.  Assumes all actual 'IT costs' reside in the IT profit centre group (00046).  The actual Opex numbers are adjusted to remove any costs considered to not be Standard and Alternative Control Services related .  The adjustment is based on the same Standard + Alternative Control % allocation applied to derive FTE & User numbers.  This % allocation is derived by the Regulatory team using the approved Cost Allocation Method (CAM).\n\n"]
[null,"2.6.1","MOTOR VEHICLES \nF15-F19; \nF22-F24","Financial","Operating Expenditure Reports from SG Fleet Australia Pty Limited (our Fleet Managers) to allocated cost per Asset Category.\nInternal SAP workshop expenditure and Fleet cost centre reports.","Actual",null,"Full absorption costing applies to fleet operating costs such that they are charged out to operating and capital activities, plus the direct control allocation to corporate groups. Motor vehicles are used for work across different regulated services (e.g. standard control, negotiated distribution etc.) within any period. The allocation of costs to Standard Control Services is based on the approved Cost Allocation Method (CAM). ","The split between the vehicle types is based on a sample of actual data including: (i) Maintenance costs obtained from SG Fleet and SAP Workshop Report (IW38); (ii) Other costs such as fuel; registration & insurance are sourced from the SG Fleet Report. Expenditure reported in these reports does not include an allocation of the corporate overheads, it is for this reason that the reports are used to align the costs to the relevant vehicles categories, with the total expenditure (using cost centre reports) then allocated across the individual categories using the same apportionment."]
[null,"2.6.1","BUILDINGS & PROPERTY\nF20","Financial","SAP Functional Area / Activities report.  \nIndentiified as reporting line in the AER RIN (Financial) Reporting Working Papers","Actual",null,"RIN supporting workings: Operations & Maintenance Expenditure Analysis - Property"]
[null,"2.6.1","OTHER \nOPEX F21","Financial","Calculation","Actual",null,"SUM of rows 22-32"]
[null,"2.6.1","OTHER - DNSP Nominated\nNetwork Telephony (A80) F25","Financial","SAP Functional Area / Activities report. ","Actual",null,"Data generated from SAP for activity A80, which is a subset of Network Telephony"]
[null,"CAPEX"]
[null,"2.6.1","IT & COMMUNICATIONS\nF34, F35 & F36","Financial","SAP Functional Area / Activities report. ","Actual","N/A","Actual data derived by executing SAP Capex drill down report then categorising the expenditure as either Recurrent, Non-recurrent or Client Devices.","All data sourced from SAP.  Expenditure is categorised as either Recurrent, Non-recurrent or Client Devices as defined by AER definitions.  Assumes all actual IT Capex resides in the IT profit centre group and any other Capex assigned to functional code L24 ('IT Systems') outside of the IT profit centre group."]
[null,"2.6.1","MOTOR VEHICLES\nF37-F41; \nF44-F46","Financial","SAP - Capital Order Report & Transaction (IE37)","Actual",null,"Fleet capex by order BW report generated for the regulatory year. Individual order per vehicle includes a Purchase Authority number, which is then mapped to the fleet number via SAP transaction IE37. Fleet number is then categorised"]
[null,"2.6.1","BUILDINGS & PROPERTY\nF42","Financial","SAP Functional Area / Activities report.  \nIndentiified as reporting line in the AER RIN (Financial) Reporting Working Papers","Actual",null,"RIN supporting workings: Capital Expenditure Analysis - Property"]
[null,"2.6.1","OTHER \nCAPEX F43","Financial","Calculation","Actual",null,"SUM of rows 44-54"]
[null,"2.6.1","OTHER - DNSP Nominated\nNon-Network Projects F48-F50","Financial","SAP - Project Order Listing Report","Actual",null,"Financial data based on individual non network strategic project actual expenditure (data extracted from SAP)"]
[null,"2.6.1","OTHER - DNSP Nominated\nNon-Network Telecommunications F51","Financial","SAP - Project Order Listing Report","Actual",null,"Financial data based on individual non network strategic project actual expenditure (data extracted from SAP)"]
[null,"2.6.1","OTHER - DNSP Nominated\nOther Plant and Tools F52","Financial","SAP Functional Area / Activities report.  \nIndentiified as reporting line in the AER RIN (Financial) Reporting Working Papers","Actual",null,"RIN supporting workings: Capital Expenditure Analysis - Plant & Tools and Non Network Other"]
[null,"2.6.2 - ANNUAL DESCRIPTOR METRICS - IT & COMMUNICATIONS EXPENDITURE"]
[null,"2.6.2","IT & COMMUNICATIONS\nEmployee Numbers (F62)\n","Non-Financial","Refer Table 2.11 Labour \nASLs have been extracted from table 2.11.1. These relate to Standard Control Services only (in line with the RIN definition).","Actual",null,"Refer Table 2.11.1; Methodology for determination of ASLs for internal employees and labour hire employees. This relates to Standard Control Services only as prescribed in the CA RIN definitions."]
[null,"2.6.2","IT & COMMUNICATIONS\nUser Numbers (F63)\n","Non-Financial","Active Directory","Actual","N/A","1. Identity Management Team provide extract of all users from IIQ (includes HR data cross referenced with Active Directory data and key dates on last logon to ActiveDirectory and Azure).  Key data elements include:\n    - Start Date   (used to support calculations on number of days active in period)\n    - End Date     (used to support calculations on number of days active in period)\n    - Company   (used to exclude users who work for unregulated business (Enerven)\n    - Last Logon AD   (used to identify users as 'active')\n    - Last Logon Azure   (used to identify users as 'active')\n\n2.  Based on the data provided the following calculations/assessments are made for each user:\n    - Whether or not a user was 'active' in the period\n    - Number of days a user was 'active' in the period \n    - FTE for a user being active in the period (number of days 'active' / 365)\n\n3.  Total Users calculated as sum of FTE for each user active in the period\n\n4.  Number of users are scaled to remove any users considered to not be completing Standard Control Services work. The  % allocation applied to derive FTE & Opex numbers is followed.  (Unregulated business users are removed and then % Opex for Standad Control Services of total OPEX (removing unregulated opex)","1. HR Start and End dates are sufficiently accurate.\n\n2. Azure and AD last logon dates capture all 'active users'\n\n3. Actual number of users is adjusted to remove any users considered to not be completing Standard Control Services Work.  The adjustment is based on the same % allocation applied to derive FTE & Opex Numbers.  This % allocation is derived by the regulatory team using the approved Cost Allocation model (CAM).\nNB: Unregulated users are directly removed before applying the appropraite % for standard control services.","SA Power Networks uses many external service providers, including in the field.  The method outlines captures ALL active users which is distinct from employee numbers which do not reflect external service providers.\n\nAn FTE calculation is used to appropriately proportion the number (headcount) of users to the actual workload they reflect to IT in supporting them.\ne.g. A contract Asset Inspector who works for 6 months will have been an active user of IT services (as we provide them a field device, email services and application access via mobile applications) for only half of the year.\n\nOur user numbers are likely to be higher than reported in FY17 and earlier due to our identity management system (IIQ) now providing the capability to accurately report on user logons from the field.  e.g. A contract Asset Inspector in the past may never have had to login to AD, just Azure for access from the field.  In addition our HR data is combined into our identity management system which allows us to determine the number of days an active user was with us during the peroid and calculate an appropriate FTE figure for them (number of days active in period/number of days in year)."]
[null,"2.6.2","IT & COMMUNICATIONS\nNumber of Devices (F64)\n","Non-Financial","Cherwell (Asset Management software) & Telstra reports.","Actual","N/A","1. Obtain cherwell device export from IT Asset Management Team (as close to end of FY as possible, but not earlier)\n\n2. Pivot on appropraite asset types (refer comments) and exlude any devices with status that indicates the device isn't actively being managed (e.g. exclude 'ordered', 'planned', 'stolen', 'expired' etc, but keep 'Active', 'In repair' etc)\n\n3. Obtain mobile plan reports from IT Asset Management Team and validate number of phones is accurate compared to usage.\n\n4. Scale number of devices to remove any devices considered to not be completing Standard Control Services work. The  % allocation applied to derive FTE & Opex numbers is followed. ","The actual number of devices is adjusted to remove any user devices considered to not be completing Standard and Alternative Control Services work.  The adjustment is based on the same Standard + Alternative Control % allocation applied to derive FTE & Opex numbers.  This % allocation is derived by the Regulatory team using the approved Cost Allocation Method (CAM).","`Items included as Client Devices are:\n> Tablet PC's\n>Laptop\n> Desktop Computer\n> Toughbook\n> Ultrabook\n> Toughpad\n\nNew Devices for FY18 and beyond (as they are used for displaying information from client devices)\n> Televisions\n> Large Monitors\n> Projectors"]
[null,"2.6.3 - ANNUAL DESCRIPTOR METRICS - MOTOR VEHICLES"]
[null,"2.6.3","MOTOR VEHICLES\nAverage Km's Travelled\nF70, F75, F80, F85, F90","Non-Financial","SAP reports containing a listing of all vehicles and their relevant details (e.g. description, classification, date in service, km's odometer readings etc.)","Actual",null,"Average KM's are calculated by obtaining total KM's by vehicle (utilising opening and closing odometer readings for the year). The total Km's are then grouped into the respective vehicle categories and averaged over the number of vehicles in use during the year. Each category has then been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.  "]
[null,"2.6.3","MOTOR VEHICLES\nNumber Purchased \nF71, F76, F81, F86, F91","Non-Financial","SAP reports containing a listing of all vehicles and their relevant details (e.g. description, classification, date in service, km's odometer readings etc.)","Actual",null,"SAP Fleet composition report which is then sort into respective categories. Categories have been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.   "]
[null,"2.6.3","MOTOR VEHICLES\nNumber Leased \nF72, F77, F82, F87, F92","Non-Financial","SAP reports containing a listing of all vehicles and their relevant details (e.g. description, classification, date in service, km's odometer readings etc.)","Actual",null,"SAP Fleet composition report which is then sort into respective categories. Categories have been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.   "]
[null,"2.6.3","MOTOR VEHICLES\nNumber in Fleet\nF73, F78, F83, F88, F93","Non-Financial","SAP reports containing a listing of all vehicles and their relevant details (e.g. description, classification, date in service, km's odometer readings etc.)","Actual",null,"SAP Fleet composition report which is then sort into respective categories. Categories have been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.   "]
[null,"2.6.3","MOTOR VEHICLES\nProportion of Total Fleet expenditure\nF74, F79, F84, F89, F94","Non-Financial","Calculated using the total vehicle expenditure reported in table 2.6.1 and the percentage allocation to Standard Control Services as per the Cost Allocation Method.","Actual",null,"Regulated % based on the total standard control fleet capex plus opex costs by category divided by the total fleet capex and opex costs by category. "]

{"sheet":"2.7 Veg Management","index":5,"n_rows":19,"n_cols":10,"rows_kept":19,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.7.1 - DESCRIPTOR METRICS BY ZONE"]
[null,"2.7.1","ZONE 1:\nRoute line length within zone","Non-financial","Vegetation clearance data ","Estimate","Estimate of route line length based on circuit length data. ","Route line length based on estimate of percentage of route for each voltage that runs parallel to other voltages. Conductor on the same route was estimated by voltage starting with LV and working up to 132kV. Estimate of route line length for earlier years has been pro-rated by historical GIS circuit length data. "]
[null,"2.7.1","ZONE 1:\nNumber of maintenance spans","Non-financial","Vegetation clearance data ","Estimate","Estimate as number of poles or spans not recorded. ","Figures based on number of maintenance spans cut over last few years. Pro-rata estimate based on number of spans for each feeder category. "]
[null,"2.7.1","ZONE 1:\nTotal length of maintenance spans","Non-financial","Vegetation clearance data ","Estimate","SA Power Networks does not record the length of maintenance spans. An estimate has been provided based on the route line length which equates to km of maintenance spans. ","The total length of maintenance spans has been estimated based on an internal estimate of the average span length in bushfire risk areas, medium = 125m and high = 90m, so average length in bushfire risk areas is 107.5m, and in non-bushfire risk areas the average length is 45m. ",null,"SA Power Networks erects different voltages on the same structures (e.g. 11kV and LV) and runs underground cables operating at different voltage levels in the same trench.  Consequently, SA Power Networks estimated in 2015 the percentage of higher voltages (i.e. 11kV and above) that run parallel (i.e. on same structures) for each voltage level.  This percentage (or duplication factor) is used to convert the route length of a specified voltage (e.g. 11kV) that that route length that does not run parallel to another lower voltage.  The same factors used for overhead conductor route length are used for underground cable length.  The same duplication factors have been used  each year. "]
[null,"2.7.1","ZONE 1:\nLength of vegetation corridors","Non-financial","Vegetation corridors are not maintained under distribution lines and the current legislation does not allow clearance beyond the buffer zone. "]
[null,"2.7.1","ZONE 1:\nAverage number of trees per maintenance span","Non-financial","Vegetation clearance contractor ","Estimate","This information is currently not collected and an estimate has been provided following discussions with the vegetation clearance contractor. The estimate has been based on expert knowledge from the field. ","Based on discussions with the contractor and internal vegetation inspectors estimates have been provided. The average number of trees has been estimated at 8.58 trees per span in rural areas and 3.378 trees in urban and CBD areas. ","The average number of trees has been estimated at 9 trees per span in bushfire and 2.7 non-bushfire risk areas. "]
[null,"2.7.1","ZONE 1:\nAverage frequency of cutting cycle","Non-financial","Vegetation clearance program ","Estimate",null,"In 2012, SA Power Networks shifted to a annual cycle (scoping/ cutting) in high and medium bushfire risk areas to address non compliance issues. Prior to this the vegetation program was a 3 year cyclic program in all areas.","Annual inspection in high bushfire risk areas, a 1-3 year cycle in medium bushfire risk areas (based on risk) and a 3 year cycle in non-bushfire risk areas. "]
[null,"2.7.2 - EXPENDITURE METRICS BY ZONE"]
[null,"2.7.2","Whole table","Financial","Sourced from work order descriptions within SAP ","Actual",null,"The data provided has been sourced from work order descriptions from SA Power Networks SAP system (generated from BeX reporting on Activity M04/Vegetation Management). The work orders are quite descriptive and differentiate between different vegetation management activities e.g. scoping, cutting etc."]
[null,"2.7.3 - DESCRIPTOR METRICS ACROSS ALL ZONES - UNPLANNED VEGETATION EVENTS"]
[null,"2.7.3","Number of fire starts caused by vegetation grow-ins (NSP responsibility)","Non-financial","Information collected following fire starts ","Actual ",null,"Data provided based on information collected - all assumed to be NSP responsibility as NSP responsible for clearance "]
[null,"2.7.3","Number of fire starts caused by vegetation blow-ins and fall-ins (NSP responsibility)","Non-financial","Information collected following fire starts ","Actual ",null,"Data provided based on information collected - all assumed to be NSP responsibility as NSP responsible for clearance "]
[null,"2.7.3","Number of fire starts caused by vegetation grow-ins (other party responsibility)","Non-financial","Information collected following fire starts ","Actual",null,"One incident of owner cutting a tree, tree falling on conductor causing it to fail. "]
[null,"2.7.3","Number of fire starts caused by vegetation blow-ins and fall-ins (other party responsibility)","Non-financial",null,"Actual",null,"No data provided - SAPN responsible for clearance around powerlines "]

{"sheet":"2.8 Maintenance","index":6,"n_rows":40,"n_cols":10,"rows_kept":40,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"\nState the table reference (CAT) or Variable Code (EBT)","\nState the applicable row, column, cell, or entire tab","Select whether the referenced information is financial or non-financial","Explanation of the data source for the referenced information","Select whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.8.1 - DESCRIPTOR METRICS FOR ROUTINE AND NON-ROUTINE MAINTENANCE"]
[null,"2.8.1","F12 - H13\nPole Top, Overhead Line & Service Line Maintenance","Non-Financial","a) 5.2 Asset Age Profile\n\nb) Priority Asset Tool PAT) and Works Manager (WM)\n\nc) Manual No. 12, Section 6.3.5","Estimated",null,"Asset quantity is based on input data in 5.2 Asset Age Profile tab. Average age of the asset was calculated by setting the year concerned with 'Year 1', the year number (multiplier) was multiplied by the total number of assets. The result was added across the years and the total number of assets per year was also added together to give a total. The total number of assets with the multiplier was divided by the total number of assets give an average age of asset for the particular year. \n\nHence, the overall quantity at year end for Pole tops and overhead lines it is 647,497 poles while for  Service Lines it is 796,125 customers.\n\nAs for Average Age for Pole tops and overhead lines it is 45.6 years, and for Service lines it is 28.6 years, respectively.\n\nThe number of poles and overhead lines inspected/maintained is based on the number of poles inspected (G14) which is 100,102 poles obtained from the PAT and WM by Asset Assessment.\n\nAsset Inspected/Maintained for Service Lines is unavailable. This is because number/length of service lines inspected falls under OCI/GCI program (G14) which does not allow us to split the numbers into different asset classes.\n\nPlease refer WI1 - Work Instructions - CA RIN 2.8 Maintenance (draft).\n",null,"Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F14 - H14\nAll Poles","Non-Financial","a) 5.2 Asset Age Profile\n\nb) Priority Asset Tool (PAT) and Works Manager (WM)\n\nc) Manual No. 12, Section 6.2.5","Estimated",null,"Asset quantity is based on input data in 5.2 Asset Age profile tab or F12 of this report. \n\nHence, for All Poles they are 647,000 poles per Pole tops and overhead lines above.\n\nThe asset quantity inspected/maintained is based on the the total number of poles inspected which is 100,102 (data obtained from Asset Assessment group)\n\nAverage Age for All Poles it is 48.7 years based on 5.2 Asset Age profile tab.\n\nPlease refer WI2 - Work Instructions - CA RIN 2.8 Maintenance (draft).",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F15 - H15\nAll Overhead Assets","Non-Financial","a) 5.2 Asset Age Profile\nb) AER EB RIN 3.7 Operating Environment 2019-17\nb) Pre-Bush Fire Patrol List\nc) SAP\nd) Manual No. 12, Section 6.2.5","Estimated",null,"The overall overhead circuit route length KMs based is provided  by the Facilities Records Coordinator, Facilities Records group.\n\nThe total route kms covered for the annual pre-bush fire patrols for 2017-2018  is approximately 49,898 kms (obtained from Asset Assessment group). OCI/GCI conducted in 2017-2018 is estimated to be 11,815 kms (according to Asset Assessment group), however some of the areas inspected as part of OCI/GCI overlap the pre-bush fire patrolled areas. Hence, due to this overlap, the total route kms for 2017-2018 is taken as 49,898 kms. \n\nThe average age is 50.5 years using data from 2.2 Repex.\n\nPlease refer WI3 - Work Instructions - CA RIN 2.8 Maintenance (draft).",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F16 to F19\nH16 to H19\nNetwork Underground Cable Maintenance -asset quantity and average age","Non-Financial","5.2 Asset Age Profile","Estimated",null,"Asset quantity is based on input data in 5.2 Asset Age profile tab. Average age of the asset by voltage was calculated  by setting the year concerned with as 'Year 1', the year number (multiplier) was multiplied by the total number of assets. The result was added across the years and the total number of assets per year was also added together to give a total. The total number of assets with the multiplier was divided by the total number of assets to give an average age of asset for the particular year.\n\nHence, for LV - 11 to 22 KV the asset quantity based on 5.2 Asset Age Profile is 17,876 kms whilst for 33 kV and above it is 188 kms. The lengths obtained for 2017-2018 is said to be more accurate than in previous years due to the introduction of a new asset management system last year. The average age is 24 years for LV - 11 to 22 kV and 28.9 years for 33 kV and above.\n\nThe total length for CBD and non-CBD is obtained from 2.2 Repex which are 272 kms and 17,792 kms, respectively.\n\nAs for the average age, CBD is assumed to be 28.9 years as most, if not all, underground cable network in the CBD comprises mostly 33kV and above (see H17). In the case of non-CBD  it is assumed to 24 years which is the figure for LV.\n\nPlease refer WI4 - Work Instructions - CA RIN 2.8 Maintenance (draft).",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","G16 to G17\nNetwork Underground Cable Maintenance  -asset quantity inspected/maintained","Non-Financial","\n\na) 2017-18 UG Online Cable Test\n\nb) 2017-18 UG Offline Cable Test\n\nc) 2017-18 33kV and Above Cable Test\n\nd) SAP","Actual","A Network Underground Cable Maintenance programme was launched in 2016 comprising of on-line and off-line tests. The results for 2017/2018 were tabulated on  spreadsheets and used to generate the data required. ","For LV - 11 to 22 KV (from 2017-18 Online Cable Tests and Offline Cable Tests data), a total of 835.5 km of underground cables were tested.\n\nSimilarly for 33kV and Above (from 2017-18 33kV and Above Test data, a total of 11.6 km of 33kV and Above of underground cables were tested.\n\nPlease refer WI5 UG Cable - asset qty insp - Work Instructions - CA RIN 2.8 Maintenance (draft) ","\n\n","Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","G18 to G19\nNetwork Underground Cable Maintenance  -asset quantity inspected/maintained","Non-Financial","\n\na) 2017-18 UG Online Cable Test\n\nb) 2017-18 UG Offline Cable Test\n\nc) 2017-18 33kV and Above Cable Test","Actual","A Network Underground Cable Maintenance programme was launched in 2016 comprising of on-line and off-line tests. The results for 2017/2018 were tabulated on  spreadsheets and used to generate the data required. ","The total cable lengths of LV - 11 to 22 kV and 33 kV and Above  is 847.12 kms. \n\nFor CBD cable lengths it is the sum of CBD UG Offline Test and 33 kV and Above Test results which is 15.47 kms. Hence, for non-CBD it is 831.65 kms (i.e. 847.12 kms less 15.47 kms).\n\nPlease refer WI5 UG Cable - asset qty insp - Work Instructions - CA RIN 2.8 Maintenance (draft) ",null,"Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","I16 - I19\nNetwork Underground Cable Maintenance - inspection cycle","Non-Financial","Network Maintenance Manual No. 12 (March 2017)","Estimated","For 33 kV and above, the lines are inspected once every half yearly.","Per Network Maintenance Manual No 12\n\n",null,"Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F20 - H20\nDistribution Substation Transformers - quantity, quantity inspected/maintained, age","Non-Financial","5.2 Asset Age Profile/SAP","Estimated",null,"Asset quantity is based on input data in 5.2 Asset Age profile tab. Average age of the asset was calculated  by setting the year concerned with as 'Year 1', the year number (multiplier) was multiplied by the total number of assets. The result was added across the years and the total number of assets per year was also added together to give a total. The total number of assets with the multiplier was divided by the total number of assets to give an average age of asset for the particular year.\n\nThe asset quantity at year's end is 79,497 which is based on the total distribution substation transformers less the total number of transformers (zone substation) of 693.\n\nThe quantity inspected is 401  based on data provided by Asset Assessment group.\n\nThe average age is 30.2 years based on CA RIN 5.2 Asset Age profile.\n\nPlease refer Work Instructions - CA RIN 2.8 Maintenance (draft) - WI6 Distribtion Substation Transformers.",null,"Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F21 - H21 \nDistribution Substation Switchgear (within substations and stand-alone switchgear) - quantity, quantity inspected/maintained, age","Non-Financial","a) 5.2 Asset Age Profile\nb) SAP\nc) Distribution Substation Switchgear Inspection Report (from Operational Asset Management group)\n","Estimated","For this purpose, Distribution Substation Switchgears include all reclosers, sectionalisers and Ground Level (Switching Cubicle) Switchgears. (This is in-line with the SA Power Networks - Final Distribtion Category Analysis RIN, p74). ","Asset quantity is based on input data in 5.2 Asset Age profile tab. Average age of the asset was calculated  by setting the year concerned with as 'Year 1', the year number (multiplier) was multiplied by the total number of assets. The result was added across the years and the total number of assets per year was also added together to give a total. The total number of assets with the multiplier was divided by the total number of assets to give an average age of asset for the particular year. \n\nIncludes Reclosers, Sectionalisers, and Load Break Switches (ground level switchgear) giving a total number of 9,621 with an average age of 13.9 years.\n\nThe total number inspected/maintained is based on the Recloser readings (SAP) of 777 plus the total number of Distribution Substation Switchgear inspected (from Operational Asset Management group) of 1030 giving a total of 1807. (Note that there is no specific sectionalisers inspection program and these get inspected as part of the OCI/GCI program. Defect notifications are raised only if a defect is found.)\n\nPlease refer - WI7 Distribution Substation Switchgear - Work Instructions - CA RIN 2.8 Maintenance (draft)",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F22 - J22\nDistribution Substation - Other Equipment (earth mat)","Non-Financial","Not applicable","Not applicable","Not applicable","Not applicable","Not applicable","Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F23 - H23\nDistribution Substation Property - quantity, quantity inspected/maintained, age","Non-Financial","a) 5.2 Asset Age Profile\nb) M18 Distribution Substation Property (BEX Report)","Estimated",null,"The total estimated number and average age of Distribution Substation Properties is derived from 5.2 Asset Age Profile under the descriptor \"Transformers\" excluding all zone substation transformers (F24).\n\n35 is the total number of switches inspected/maintained is based on the total number of Distribution Substation - Property inspected derived from M18 Distribution Substation Property  report.\n\nPlease refer WI8 Distribution Substation Property - Work Instructions - CA RIN 2.8 Maintenance (draft) ",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F24 - H24\nTransformers - Zone Substation","Non-Financial","Asset quantity - 5.2 Asset Age Profile / SAP\n\nAsset inspected/maintained - SAP\n\nAverage age -  5.2 Asset Age Profile / SAP","Estimated","Asset quantity - 5.2 Asset Age Profile / SAP\n\nAsset inspected/maintained - SAP\n\nAverage age -  5.2 Asset Age Profile / SAP","Asset quantity - Calculated from substation transformer Asset Age Profile (Table 5.2.1; Transformer Asset Group)\n\nAsset inspected/maintained - actual\n\nAverage age - Calculated from substation transformer Asset Age Profile (Table 5.2.1; Transformer Asset Group)\n\nPlease refer WI (draft) for sub mtce RIN response, Section 6.1.1, Section 6.2.2, and Section 6.3.2 ","Asset quantity - assumes SAP accurate (refer BoP 5.2.1 Asset Age Profile)\n\nAsset inspected/maintained - includes all mtce cycles but excludes inspections (refer 'Zone substation asset inspection')\n\nAverage age  - assumes SAP accurate (refer BoP 5.2.1 Asset Age Profile)","Asset quantity - Assets included in age profile data:\n- Substation TFs & Regulators in service at 30/6/18:\n- Hot/Cold Standby TFs & Regs\n- TFs/Regs associated with mobile plant\n- Earthing and GSU TFs at Kingscote Substation\n- HV/LV TFs when allocated to a SSD substation and used for primary power distrubution (i.e. not a station AUX TF)\n\nExclusions to population numbers:\n- Unregulated TFs & Regs\n- TFs & Regs installed at the Angle Park and Davenport training substations\n- Substation AUX TFs\n\nAsset inspected/maintained - nil\n\nAverage age - nil\n\nThis has been subjected to a maintenance cycle of up to 6 years"]
[null,"2.8.1","F25 - H25\nTransformers - Distribution (within substations)","Non-Financial","SAP\nRIN 2015/16","Estimated","SAP\n\nRIN 2017/2018 data","About 10% have unknown age\n\nYear 2000 is used as a default, which is loosley the average age of all assets\n\n\nPlease refer WI (draft) for sub mtce RIN response, Section 6.1.3, Section 6.2.3, and Section 6.3.3","Asset quantity - SAP dump 14Jul18\n\nAsset inspected/maintained - inspected during sub site inspection, maintained by defect\n\nAverage age - 90% accurate (year of manufacture not consistently recorded in SAP)","Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F26 - H26\nTransformers - HV","Non-Financial","not applicable","Not applicable",null,"Not applicable","Not applicable","no assets defined as 'TRANSFORMERS - HV' in zone substations"]
[null,"2.8.1","F27 - H27\nZone Substation - Other Equipment","Non-Financial","Asset quantity - Asset Mgt Plan, SAP, 2017/18 CAT RIN\n\nAsset inspected/maintained - SAP\n\nAverage age - refer Asset Qty","Estimated","Asset inspected/maintained - actual\n\nAsset records from maintenance database\n\nAverage age - see comment re quantity","Asset quantity - qty based on 2016/17 CAT RIN, cross referenced with 2018 sub site list & adjusted for changes during 2017/18 - sum profile from nominated year end back to start of profile\n\nAsset inspected/maintained -  SAP dump broken down by mtce strategy codes etc & then re-grouped to match table reporting categories\n\nAverage age - average based on previous age profile (2016/17 CAT RIN) & adjusted for changes during 2017/18 - sum/count profile from nominated year end back to start of profile & maintenance change over records\n\nPlease refer WI (draft) for sub mtce RIN response","Asset quantity - only covers battery banks\n\nAsset inspected/maintained - covers everything described in 'additional comments'\n\nAverage age - refer comments re quantity","Other potentially covers batteries/chargers, VT/CT, insulator washing, mobiles, earthing, phones/TDU's, pole plating, joints, cap banks, fuses, surge arrestors, buswork/switchyard repairs\n\nThis has been subjected to a Maintenance Cycle of up to 10 years (e.g. batteries)\n"]
[null,"2.8.1","F28 - H28\nAll Zone Substation Properties","Non-Financial","Asset quantity - LAN/intranet spreadsheets\n\nAsset inspected/maintained - SAP\n\nAverage age - historical spreadsheet","Estimated","Asset quantity - actual\n\nAsset inspected/maintained - actual\n\nAverage age - estimation results from assumption","Asset quantity - number of sites based on number of noti's raised in SAP for cycle 1 inspection of subs/properties\n\nAsset inspected/maintained - SAP dump broken down by mtce strategy codes etc & then re-grouped to match table reporting categories\n\nAverage age - used sub age profile\n\nPlease refer WI (draft) for sub mtce RIN response","Asset quantity - covers site inspections only\n\nAsset inspected/maintained -  covers site inspections + specific tasks as described in 'additonal comments'\n\nAverage age - number of properties inspected etc is slightly greater than the number of substations (as future undeveloped sub sites included) so used sub age profile as a close approximation","Covers site inspections, building cleans, emergency lights, air-conditioners, fire extinguishers, site security\n\nAsset quantity - source is LAN directory for PM work plan preparation\n\n"]
[null,"2.8.1","F29 - H30\nPublic Lighting","Non-Financial","Not applicable","Not applicable","Not required to report as negotiated services","Not applicable","Not applicable","Not applicable"]
[null,"2.8.1","F31\nSCADA and Network Control Maintenance - asset quantity","Non-Financial","ADMS","Actual",null,"Total number of SCADA assets (substation RTU's) was achieved from running a query in the ADMS SCADA system. The number reported is the total number of substations with a SAPN RTU installed on site.\n\nPlease refer Work Instructions - CA RIN 2.8 Maintenance (draft) - WI9   .",null,"Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","G31\nSCADA and Network Control - quantity inspected/maintained","Non-Financial","SAP","Actual",null,"There is currently no SCADA assest inspection or maintance plan, SCADA assets are repaired on failure. Number of sites repaired in 2017/18 are captured in SAP.\n\nPlease refer Supporting Document_Reference to Manual 12","SCADA asset maintenance is based on reactive work, there is no routine maintenance program in place due to the nature of the assets and the components that form them. There are monitoring alarms for each asset which are seen by the network operations centre, if abnormal alarms appear, this triggers a job to be raised, and hence a defect.","Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","H31\nSCADA and Network Control - average age","Non-Financial","SCADA configuration files ","Estimated",null,"Average asset age from 2016/2017 was aggregated with new assets added in 2017/2018. New assets were given an age of 1 year.\n\nPlease refer WI (draft) for sub mtce RIN response\n",null,"Some of these assets have been in service over their expected manufacturer life, for example the TDU has a life expectancy or approx 15 years, the TDU has been in service since 2000/2001, which means its already 14 years (close to end of life), its therefore unfair to assume average is 9 years for 2012/2013 when some old assets might be above that average.\n\nAssets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero."]
[null,"2.8.1","F32 - H32\nProtection Systems ","Non-Financial","Asset quantity - SAP\n\nAsset inspected/maintained - SAP\n\nAverage age - LAN spreadsheet","Asset quantity - actual \n\nAsset inspected/maintained - actual\n\nAverage age - estimate",null,"Asset quantity - qty based on # plans in SAP linked to prot'n related mtce scheme strategies\n\nAsset inspected/maintained - SAP dump broken down by mtce strategy codes etc & then re-grouped to match table reporting categories\n\nAverage age - average based on relay age profile (provided by others for RIN 5.2) - sum/count profile from nominated year end back to start of profile\n\nPlease refer WI (draft) for sub mtce RIN response","Asset quantity - assumes mtce plan exists in SAP for every prot'n scheme in distribution network\n\nAsset inspected/maintained - nil\n\nAverage age -based on 2017/18 age profile of relays (provided by others for RIN 5.2) & therefore 'inherit' assumptions made to compile age profile","Asset is subjected to a 4 year maintenance cycle"]
["`","2.8.1","F33 - H33\nSubtransmission Asset Maintenance","Non-Financial","Not applicable","Not applicable","Not applicable","Not applicable","Not applicable","Not applicable"]
[null,"2.8.1","F34 - H34\nVarious assets","Non-Financial","SAP\nMaintenance Records","Estimated",null,"Asset quantity is based on input data in 5.2 Asset Age profile tab. Average age of the asset was calculated  by setting the year concerned with as 'Year 1', the year number (multiplier) was multiplied by the total number of assets. The result was added across the years and the total number of assets per year was also added together to give a total. The total number of assets with the multiplier was divided by the total number of assets to give an average age of asset for the particular year. The asset quantity inspected/maintained is based on SAP and maintenance reports.\n\nPlease refer WI (draft) for sub mtce RIN response",null,"This is subjected to a 1.5 years Maintenance cycle"]
[null,"2.8.1","F35 - H35\nGround Clearance access tracks","Non-Financial","Not applicable","Not applicable","We do not have sufficient information to make a good or acceptable estimation on Ground Clearance access tracks, hence, this has not been reported.","Not applicable","Not applicable","Not applicable"]
[null,"2.8.1","F36 - H36\nOther - (1) Substation asset inspection","Non-Financial","Asset quantity - LAN spreadsheets\n\nAsset inspected/maintained - SAP\n\nAverage age - historical spreadsheet, RIN 2017/18","Asset quantity - actual\n\nAsset inspected/maintained - actual\n\nAverage age - estimate (refer methodology)","Asset quantity - number of sites based on number of noti's raised in SAP for cycle 1 inspection of substations\n\nAsset inspected/maintained - cycle 1 (major) + cycle 2 (minor) inspections for nominated year\n\nAverage age - used year of earth grid installation to set age of substation site","Asset quantity - units are substation sites/properties\n\nAsset inspected/maintained - data is for general site inspection only, not inspection of individual assets within each site - maintenance covered in other rows of table\n\nAverage age - if earth grid date unknown, used date SSD drawing for sub first published\n\nPlease refer WI (draft) for sub mtce RIN response","Asset quantity - source is LAN directory for PM work plan preparation\n\nAsset inspected/maintained - nil\n\nAverage age - nil","Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F37 - H37\nOther - (2) Zone substation equipment maintenance (switchgear)","Non-Financial","Asset quantity - SAP\n\nAsset inspected/maintained - SAP\n\nAverage age - SAP","Asset quantity - actual\n\nAsset inspected/maintained - actual\n\nAverage age - actual","Asset quantity - qty based on age profile (provided by others for RIN 5.2) - sum profile from nominated year end back to start of profile\n\nAsset inspected/maintained - SAP dump broken down by mtce strategy codes etc & then re-grouped to match table reporting categories\n\nAverage age - average based on age profile (provided by others for RIN 5.2) - sum/count profile from nominated year end back to start of profile","Asset quantity - only covers circuitbreakers & disconnectors (excludes RMU's & load switches) - assumes age profile in RIN 5.2 (by others) SAP based & accurate\n\nAsset inspected/maintained - covers circuitbreakers, disconnectors, RMU's & load switches - includes all mtce cycles but excludes inspections (refer 'Zone substation asset inspection')\n\nAverage age - see comment re quantity\n\nPlease refer WI (draft) for sub mtce RIN response","Asset quantity - nil\n\nAsset inspected/maintained - nil\n\nAverage age - nil","This is subjected to a 4.5 years Maintenance cycle"]
[null,"2.8.1","F38, H38\nOther - (3) Numbers of signages & IDs replaced","Non-Financial","SAP","Estimated","The total number of signages and IDs are assumed to be equal to the number of distribution substation transformers on the network.","The total quantity of signages and IDs at the end of the year is assumed to be equal to the number of installed transformers i.e. Distribution Substation Transformers plus Transformers - zone substation which is 79,497.\n\nMeanwhile, the average age is assumed to be 30 years.\n\nPlease refer WI10 No of Signages & IDs - Work Instructions - CA RIN 2.8 Maintenance (draft)\n","Signages and IDs are replaced only as and when required. ","Assets are subject to condition based maintenance only – That is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","G38 \nOther - (3) Numbers of signages & IDs replaced","Non-Financial","SAP","Estimated",null,"The number of signages and IDs replaced for transformers are estimated based on the total number of notifications raised in SAP which is 2049 for distribution substation transformers only.\n\nPlease refer  WI10 No of Signages & IDs - Work Instructions - CA RIN 2.8 Maintenance (draft) ",null,"Assets are subject to condition based maintenance only – that is, no planned (or minimum) maintenance is undertaken, and as such, cell value has been reported as zero"]
[null,"2.8.1","F39 - H39\nOther - (4) Power Station Maintenance, Asset Records Feeder Diagram Maintenance, Compliance Auditing, Asset Location Services, Customer Service Penalties","Non-Financial",null,null,null,"No records are kept on quantities of Power Station Maintenance, Asset Records Feeder Diagram Maintenance, Compliance Auditing, Asset Location Services, and Customer Service Penalties other than OPEX spent which is based on SAP."]
[null,"2.8.2 - COST METRICS FOR ROUTINE AND NON-ROUTINE MAINTENANCE"]
[null,"2.8.2","All","Financial","SAP/BEX Analysis ","Actual",null,"The figures contained within 2.8 and 2.12 (mtce section) are collated by including specific functional areas defined as maintenance. These are M01-M99 as well as A80-A87.  A reconciliation is down back to the Regulatory accounts, with the one difference being A80-A87 (Telecommunications  Asset expenditure) which are included in 2.8 and excluded from the Non-Network. \nAn Analysis report (ZFIGL_CP04) is ran on these functional areas, which shows a further breakdown by order, maintenance activity type (MAT) and expenditure category.  The MAT codes have been mapped to fit with the various AER reporting categories after discussions with operational managers. These splits have been consistent since the first CATRIN report. Project Support overhead has been allocated to the specific AER reporting categories using actual information rather than spreading the total value of Project Support OH.   \nA mapping table has been provided within the 2.8 & 2.12 Rec.xls file. The reconciliation to the regulatory accounts can be found in the 2.8 & 2.12 Rec.xls file. This file takes the total direct costs + project support as captured in the 2.12 & 2.8 Rec.xls file."]
[null,"2.8.2","F58-G58\nNetwork underground Cable -maintenance  expenditure","Financial","SAP/BEX Analysis ","Actual",null,"As above, an Analysis report (ZFIGL_CP04) is ran on these functional areas, and for each maintenance activity type (MAT).\nThe MATs included align with that reported in the regulatory accounts",null,"SAPN/SAP does not have a breakdown of costs (by MAT or otherwise) for CBD and non-CBD network underground cable maintenance. Hence, figures shown are the total for both CBD and non-CBD."]
[null,"2.8.2","F71\nSCADA and Network Control Maintenance\n- Routine Maintenance","Financial","SAP","Actual",null,"Routine maintanance is not currently performed on SCADA equipment as such there is no cost associated with this.",null,"SCADA asset maintenance is based on reactive work, there is no routine maintenance program in place due to the nature of the assets and the components that form them. There are monitoring alarms for each asset which are seen by the network operations centre, if abnormal alarms appear, this triggers a job to be raised, and hence a defect."]
[null,"2.8.2","G71\nSCADA and Network Control Maintenance\n- Non-routine Maintenance","Financial","SAP","Actual",null,"There is currently no SCADA assest inspection or maintance plan, SCADA assets are repaired on failure. Number of sites repaired in 2017/18 are captured in SAP. The value in this field is total number of defects worked on in 2017/18.",null,"SCADA asset maintenance is based on reactive work, there is no routine maintenance program in place due to the nature of the assets and the components that form them. There are monitoring alarms for each asset which are seen by the network operations centre, if abnormal alarms appear, this triggers a job to be raised, and hence a defect."]

{"sheet":"2.9 Emergency Response","index":7,"n_rows":9,"n_cols":10,"rows_kept":9,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.9.1 - EMERGENCY RESPONSE EXPENDITURE (OPEX)"]
[null,"2.9.1","TOTAL EMERGENCY RESPONSE EXPENDITURE\nD12","Financial","SAP","Actual",null,"The figures contained within 2.9 and 2.12 (Emerg Resp section) are collated by including specific functional areas defined as maintenance. These are E01-E99.  A reconciliation is down back to the Regulatory accounts, with the one reconciliation difference for Irrecoverable Third party asset damage. This is also included in the Emergency response total. \nAn Analysis report (ZFIGL_CP04) is ran on these functional areas, which shows a further breakdown by order, maintenance activity type (MAT) and expenditure category.  \nThe source data containing the Analysis reports is provided within 2.12 Input Table Workingv1 1718.xls file. The reconciliation to the regulatory accounts can be found in the 2.9 Emerg Resp Rec.xls. This file takes the total direct costs + project support as captured in the 2.12 Input table workingv1 1718.xls file.",null,"Please note that the total of Major Storms also includes Major Event days. The structure of the table doesn’t make this clear.\nIn 2.9. the top line (Total Emergency Response Expenditure is the total, with the major event day values included both within this total and shown separately below by day.\nIn 2.12 The total is shown by expenditure category.\n"]
[null,"2.9.1","MAJOR EVENT DAYS O&M EXPENDTURE\nC15","Non-financial","MED Log","Actual",null,"There were no Major Event Days recorded throughout the period from 01/07/2017 to 30/06/2018. Hence, the total expenditure is $0.00."]
[null,"2.9.1","MAJOR EVENT DAYS O&M EXPENDITURE\nC59","Financial","SAP","Actual",null,"There were no Major Event Days recorded throughout the period from 01/07/2017 to 30/06/2018. Hence, the total expenditure is $0.00."]

{"sheet":"2.10(A) Overheads","index":8,"n_rows":19,"n_cols":10,"rows_kept":19,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.10.1 - NETWORK OVERHEADS EXPENDITURE"]
[null,"2.10.1","Row 15 - Standard Control Services (Opex)","Financial","Data was obtained from a variety of sources in SAP, including General Ledger, Order, Functional Area and Cost Centre reports. ","Actual",null,"The reported total represents the aggregate cost of the various expenditure categories described in the Assumptions.  These costs are all directly attributable to standard control services in accordance with SA Power Networks' cost allocation method.  ","Represents the total of the following cost categories from Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN: Distribution licence fee; Network operating costs; Substation property maintenance; Guaranteed service level payments; Network insurance; Call centre; Customer billing; and Other customer services.  Also includes the Network overhead component of reported totals against the following categories from Table 8.4.1: Inspections; Maintenance and repair; Vegetation management; and Emergency response.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year."]
[null,"2.10.1","Row 16 - Alternative Control Services (Opex)","Financial","Refer Data Source for Row 15 - Standard Control Services (Opex).","Actual",null,"The reported total represents the aggregate cost of the various expenditure categories described in the Assumptions.  These costs are all directly attributable to alternative control services in accordance with SA Power Networks' cost allocation method.  ","Represents the total of the following cost categories from Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN: Customer billing and Other customer services.  Also includes the Network overhead component of the reported total against the Maintenance and repair category from Table 8.4.1 .  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year."]
[null,"2.10.1","Row 18 - Standard Control Services (Capex)","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Networks' Standard Control Services Capital Activities.  Costs are included in total amounts reported for these Activities in the Annual RIN.","Actual",null,"SA Power Networks has a specific SAP GL account to capture Business Overhead transfers against individual Activities (lines of work).  These costs represent general business overheads to operate the Network and thus are not considered to be direct costs.  Reported costs are directly reconcilable to SAP B/W reports.","Represents total Network overheads excluded from the following categories from Table 8.2.1 of SA Power Networks' 2017-18 Annual Reporting RIN:  Replacement Expenditure; Connections; Augmentation Expenditure; and Non-Network (where relevant).  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year."]
[null,"2.10.1","Row 19 - Alternative Control Services (Capex)","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Networks' Alternative Control Services Capital Activities.  Costs are included in total amounts reported for these Activities in the Annual RIN.","Actual",null,"Refer Methodology for Row 18 - Standard Control Services (Capex)","Represents total Network overheads excluded from the Metering services category in Table 8.2.3 of SA Power Networks' 2017-18 Annual Reporting RIN.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year."]
[null,"2.10.1","Row 21 - Negotiated Services (Other Distribution Services)","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Networks' Negotiated Service Activities.  Costs are included in total amounts reported for these Activities in the Annual RIN.","Actual",null,"Refer Methodology for Row 18 - Standard Control Services (Capex)","Reported costs represent Network Overheads charged against all of SA Power Networks' Negotiated Service Activities.  The reported cost includes an allocated writeback of SAPN over-recoveries in the 2017/18 regulatory year.  The writeback allocation was based on a pro rata split of network overheads attributed to all direct network capital and operating functions for the year."]
[null,"2.10.1","Row 22 - Unregulated Services (Other Distribution Services)","Financial","Not applicable to SA Power Networks.","Actual",null,"SA Power Networks does not have any functions classified as Unregulated Distribution Services by the AER in the 2015-20 Regulatory Control Period, hence a nil value has been reported.  While certain services have been classified as Unregulated Distribution Services in the latest version of SA Power Networks' Cost Allocation Method, this has been done in anticipation of the service classifications set to be applied by the AER in the 2020-25 Regulatory Control Period, and hence to be referenced by SA Power Networks in our upcoming 2020-25 Reset submission.  These services will continue to be reported as Unregulated Services for the remainder of the 2015-20 Regulatory Control Period."]
[null,"2.10.2 - CORPORATE OVERHEADS EXPENDITURE"]
[null,"2.10.2","Row 30 - Standard Control Services (Opex)","Financial","Corporate overhead data was primarily obtained from SAP Cost Centre reports, with some data was also sourced from SAP General Ledger, Order and Functional Area reports.  Relevant information was provided by a number of areas of the business which was relied upon to perform specific cost allocations. ","Actual",null,"Represents the total allocation of corporate costs to standard control services as detailed in Section 6.3 of SA Power Networks' cost allocation method.","Represents the Corporate costs and other operating  expenditure value for standard control services in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.10.2","Row 31 - Alternative Control Services (Opex)","Financial","Refer Data Source for Row 30 - Standard Control Services (Opex).","Actual",null,"Represents the total allocation of corporate costs to alternative control services as detailed in Section 6.3 of SA Power Networks' cost allocation method.","Represents the Corporate costs and other operating  expenditure value for Metering services in Table 8.4.1 of SA Power Networks' 2017-18 Annual Reporting RIN."]
[null,"2.10.2","Row 33 - Standard Control Services (Capex)","Financial","Specific GL account for Superannuation (accounting) expense /   SAP reports showing the distribution of productive labour hours booked against Functional Areas / Summary of Superannuation Contributions paid on behalf of employees.","Actual",null,"As per SA Power Networks' Cost Allocation Method, superannuation is reported on a cash payments basis for regulatory reporting.  This value represents the standard control services capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense.","The allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 34 - Alternative Control Services (Capex)","Financial","Refer Data Source for Row 33 - Standard Control Services (Capex).","Actual",null,"As per SA Power Networks' Cost Allocation Method, superannuation is reported on a cash payments basis for regulatory reporting.  This value represents the alternative control services capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense.","The allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 36 - Negotiated Services (Other Distribution Services)","Financial","Refer Data Sources for Row 30 - Standard Control Services (Opex) + Row 33 - Standard Control Services (Capex)","Actual",null,"Represents the total allocation of corporate costs to negotiated distribution services as detailed in Section 3 of SA Power Networks' cost allocation method plus the negotiated distribution services capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense.","The allocation of costs to Negotiated Distribution Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 37 - Unregulated Services (Other Distribution Services)","Financial","Not applicable to SA Power Networks.","Actual",null,"Refer Methodology for Row 22 - Unregulated Services (Other Distribution Services)"]

{"sheet":"2.11 Labour","index":9,"n_rows":32,"n_cols":10,"rows_kept":32,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"2.11.1 - COST METRICS PER ANNUM"]
[null,"2.11.1","Rows 13 - 30\nColumn D - Average Staffing Levels\n",{"$f":"D8","v":"Financial"},null,"Actual",null,"Sum of internal employees and labour hire employee Average Staffing Levels as calculated below.","Whilst we do not report on the AER's defined job classifications, all positions are reviewed and assigned to classifications as described below. There are based on the best fit between internal classifications and the definitions contained in the AER Final Category Analysis RIN for DNSPs (March 2014). \n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,null,"Average Staffing Levels - Employees\n","Financial","Headcount Reports Provided by HR - provides details of internal employees at point in time including wage type (e.g. Salaries/Wages/Contract/part-Time/Casual etc.), job title, job description, division etc.","Actual",null,"For each reporting period, job positions are mapped to a job description, which in turn is mapped to a RIN defined job classification (refer Assumptions for details). Checks are made to ensure consistency of classification from previous years. \n\nEmployees are consolidated into the RIN classifications and split between Corporate and Network/Field groups in line with the template requirements. Property/Real Estate and Risk & Insurance employees are reported separately for further allocation to Corporate and Network Overhead groups in line with CAM allocations (note that these are allocated in line with the CAM allocation that applies for the current regulatory year). \n\nAn average of the employees is calculated for prior June 30, December 31 and June 30 end of Regulatory Year to represent ASLs for each RIN classification.","In line with AER definitions, employees are assigned as follows:\nExecutive Manager - CEO, General Managers, Department Managers; represents the policy and strategy developers and key decision makers in the organisation;\nSenior Manager - Branch Managers; responsible for delivering outcomes that comply with policies and directives, and deliver the organisation's defined strategies;\nManager - Team Leaders and Coordinators; manage teams within the Branch to deliver strategic outcomes;\nProfessional - Engineers, Accountants, Legal etc.; degree qualified personnel that undertake network management, IT development, financial or legal roles that are not managers;\nSemi-Professional - Technical Officers, Design Officers, Project Managers, Analysts etc.; have some qualification and high levels of training, but not necessarily degree qualified;"]
[null,null,null,null,null,null,null,"Total ASLs are multiplied by a percentage calculated in the Annual RIN process to derive ASLs utilised for Standard Control activities (in accordance with the RIN requirement to report labour utilised on Standard Control services only). \n\nA separate calculation of the percentage of hours worked on Standard Control activities by Corporate and Field personnel is made each year in the Annual RIN and is used in the allocation of corporate costs in accordance with the approved CAM.","Support Staff - Administrative and consulting personnel; employees that support the organisation's skilled workforce to deliver electricity services;\nTrainee - Vocational or personnel training towards core positions (e.g. trainee project officers);\nSkilled Electrical Worker - Trade skilled electrical workers qualified to work on the electrical distribution system;\nSkilled Non Electrical Worker - trade skilled workers other than electrical (e.g. bricklayers, welders, mechanics etc.);\nApprentice - employed under an approved apprenticeship program to achieve trade skilled worker accreditation;\nUnskilled Worker - general skilled workers; field workers that do not have trade skilled electrical worker accreditation (e.g. crane drivers)."]
[null,null,"Average Staffing Levels - Labour Hire\n","","Supplementary Labour reports provided by HR - provides details of hours worked for each supplementary labour hire person for the year.","Actual",null,"For each reporting period, job positions are mapped to a job description, which in turn is mapped to a RIN defined job classification (refer Assumptions for Employees for details). \n\nSupplementary labour hours for each job classification are divided by the Average Productive Work Hours per ASL described in line 16 to calculate ASLs for Labour Hire employees.\n\n\n\n","As supplementary labour is predominantly used to backfill temporarily vacant positions or to meet short term resourcing requirements, assumptions are made to determine average FTEs in line with the RIN definition.\n\nThe majority of supplementary labour employees are employed on a less than full-time basis, but it is not practical to review every supplementary labour employee to determine their specific available hours in order to calculate average FTEs.\n\nAn assumption has been made that the ordinary time average productive work hours for supplementary labour employees are equivalent to their internal labour counterparts, plus a 20% loading to allow for leave etc."]
[null,"2.11.1","Rows 13-30\nColumn E - Total Labour Cost\n","Financial",null,"Actual",null,"Sum of internal employees and labour hire employee Total Labour Cost as calculated below.","Whilst we do not report on the AER's defined job classifications, all positions are reviewed and assigned to classifications as described in Rows 8 to 10 above. \n\nActual labour cost information is derived from our mainframe SAP information system and is utilised to  assign costs to each classification. An apportionment of total labour costs is made based on actual salaries and wages paid to each employee and reported in their annual Payment Summary for the relevant regulatory year. \n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Total Labour Cost - Employees\n",{"$f":"D13","v":"Financial"},"Payroll Costs extracted from SAP (separate GL accounts exist for payroll costs), plus additional cost categories defined in the Category Analysis RIN for Labour Cost, extracted from SAP, i.e.:\n- workers compensation expense\n- protective clothing\n- training and study assistance\n(note that these costs are not classified and reported as labour costs in SA Power Networks' general ledger)","Actual",null,"Total payroll costs extracted from SAP align with the costs identified in the RIN definition of Total Labour Cost. Superannuation expense is deducted from payroll costs and replaced with actual superannuation paid (allocated on the basis of superannuation expense) in line with the methodology in the approved CAM. These costs are collected at a cost centre (rather than individual job classification) level.\n\nTotal payroll costs extracted from SAP are multiplied by a percentage calculated in the Annual RIN process to derive labour costs allocated to Standard Control activities (refer explanation in Row 15).\n\nTotal salary and wages payments are also obtained for each employee and consolidated for each classification, from the same source and in the same manner as the ASL allocations described above. These salary and wage payments are used to allocate labour costs reported for standard control services in the Annual RINs across each labour classification.\n\nAdditional costs described in the Data Source column are allocated on the basis of ASLs and added to the reported labour cost to calculate Total Labour Cost."]
[null,"","Total Labour Cost - Labour Hire\n","Financial","Labour Hire Costs extracted from SAP (a separate GL account exists for supplementary labour hire costs).","Actual",null,"Total supplementary labour costs extracted from SAP are multiplied by a percentage calculated in the Annual RIN process to derive labour hire costs allocated to Standard Control activities (refer Row 15).\n\nTotal supplementary labour costs are allocated across job classifications on the basis of average salary and wage costs per ASL for internal employees multiplied by the supplementary labour hire  ASLs for each.","Whilst total supplementary labour costs are verified, they are not recorded against the classifications defined in the RIN. Salaries and wages paid to internal employees are used to allocate costs between labour classifications, consistent with the methodology for internal employees.\n\nThis methodology is appropriate as SA Power Networks has parity arrangements defined in its Enterprise Bargaining Agreement. This requires that any supplementary labour employee is paid at equivalent rates to their internal counterparts for the same classification."]
[null,"2.11.1","Rows 13 - 30\nColumn F - Average Productive Work Hours Per ASL\n","Financial",null,"Actual",null,"Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL as calculated below.","It is impractical to extract the ordinary time hours recorded by each employee separately for each year (this would represent hundreds of thousands of entries). Ordinary time hours are therefore collected at a summary level and allocated across ASLs, however overtime hours are collected for each employee and attributed on an actual basis based on the job title described for the calculation of ASLs above.\n\n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Average Productive Work Hours Per ASL - Employees\n",{"$f":"D16","v":"Financial"},"Hours recorded by employees extracted from SAP.\n\nApproximately 95% of employees; those that are covered by salary and wage awards; record their time daily in SAP against cost centres or job orders. This represents their time at work, which complies with the RIN definition for Productive Work Hours. Time is not entered when employees are not at work (e.g. public holidays, leave etc.).\n","Actual",null,"An allocation of ordinary time per ASL has been determined by taking total ordinary time hours for standard control activities and allocating across ASLs. Senior personnel (executive and senior management) on term contracts are not required to enter times in SAP. An assumption of 2,025 hours per year (refer assumptions tab) based on a 9.0 hour day has been calculated for these employees.\n\nTotal training hours are derived and allocated across all employees, except apprentices, on the basis of ASLs. Apprentice training is separately derived and reported against Apprentices in the template. Training hours are deducted from total ordinary time hours in line with the RIN definition. \n\nOvertime hours paid are extracted for each employee and added to the ordinary hours allocation to derive total hours for each labour classification.\n\nTotal hours are divided by the reported ASLs to obtain Average Productive Work Hours per ASL.","A calculation has been made of 2,025 hours for executive and senior managers paid on term contracts. These employees do not enter work times in SAP. The calculation is based on:\n\nWorking Days (261 week days per annum)\nLess Public Holidays (10 days per annum)\nLess Annual Leave (20 days per annum)\nLess Other Leave Days (e.g. sick, assumed to be 6 days per annum)\nMultiplied by 9.0 hours (assumed working day hours).\n\nTEC employees represent only 5% of total employees and this assumption does not have a material impact on the outcome."]
[null,"","Average Productive Work Hours Per ASL - Labour Hire\n","Financial","Supplementary Labour reports provided by HR - provides details of hours worked for each supplementary labour hire person, including overtime and stand down hours (separately).","Actual",null,"Ordinary time Average Productive Work Hours are assumed to be the same as for internal labour employees, plus a 20% loading for leave etc.\n\nOvertime hours per supplementary ASL are added to the ordinary time hours to arrive at total Average Productive Work Hours, based on actual hours provided by HR. \n\n","Refer Row 19 above - calculation of Average Staffing Levels\n\nSupplementary labour is predominantly used to backfill temporarily vacant positions or to meet short term resourcing requirements, assumptions therefore must be made as to what constitutes average hours per ASL.As described above, Average Productive Work Hours are assumed to be the same as for internal labour employees, plus loading.\n\n"]
[null,"2.11.1","Rows 13 - 30\nColumn G - \nStand-Down Occurrences Per ASL\n","Financial",null,"Actual",null,"Weighted average of internal employees and labour hire employee Stand Down Occurrences per ASL as calculated below.","Stand-down 'occurrences' are not reported separately. Hours recorded for stand-down have been reported in lieu.\n\nActual stand down hours per employee are obtained from SAP. In line with the explanations above, assumptions are made for the derivation of AER defined labour classifications.\n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Stand-Down Occurrences Per ASL - Employees\n",{"$f":"D19","v":"Financial"},"Hours recorded by employees extracted from SAP.\n\nA separate labour attendance type exists for stand-down hours. Employees record any stand-down hours against job orders in their daily timesheets. \n","Actual",null,"The hours recorded against Standard Control Services for stand-down time are extracted from SAP and reported in the labour classification that the employee has been defined."]
[null,"","Stand-Down Occurrences Per ASL - Labour Hire\n","Financial","Actual stand down hours paid to each labour hire employee provided by HR.","Actual",null,"Actual stand down hours paid to each labour hire employee are provided by HR. Stand down hours paid for each classification are divided by ASLs to derive Average Stand Down Hours per ASL"]
[null,"2.11.2 - DESCRIPTOR METRICS",null,null,null,null,null,null,""]
[null,"2.11.2","Rows 38 - 55\nColumn D - Ordinary Time - Per ASL\n",{"$f":"D22","v":"Financial"},null,"Actual",null,"Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL - Ordinary Time as calculated below.","It is impractical to extract the ordinary time hours recorded by each employee separately for each year (this would represent hundreds of thousands of entries). Ordinary time hours are therefore collected at a summary level and allocated across ASLs.\n\n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,null,"Ordinary Time - Per ASL - Employees","Financial","Hours recorded by employees extracted from SAP.","Actual",null,"Refer Row 15 above - calculation of Average Productive Work Hours Per ASL\n\nOvertime hours are deducted from Total Productive Work Hours to derive Ordinary Time Productive Hours\n\n",""]
[null,null,"Ordinary Time - Per ASL - Labour Hire","Financial","Supplementary Labour reports provided by HR - provides details of hours worked for each supplementary labour hire person, including overtime and stand down hours (separately).","Actual",null,"Refer Row 16 above - calculation of Average Productive Work Hours Per ASL\n\nOrdinary hours for internal employees are escalated by 20% to represent additional payments to supplementary labour personnel for leave etc. (for which their is no entitlement).\n(note that for classifications where no ASLs have been determined, ordinary hours are recognised as zero)\n\nOvertime hours are deducted from Total Productive Work Hours to derive Ordinary Time Productive Hours\n\n"]
[null,"2.11.2","Rows 38 - 55\nColumn E - Ordinary Time - Hourly Rate Per ASL\n",{"$f":"D25","v":"Financial"},null,"Actual",null,"Weighted average of internal employees and labour hire employee Average Productive Work Hours Hourly Rate per ASL - Ordinary Time as calculated below.","Refer Rows 11 to 16 above for the calculation of Total Labour Cost and Average Productive Work Hours Per ASL. Total Labour Cost is divided by the Average Productive Work Hours Per ASL to calculate Hourly Rates. Overtime hours and costs are deducted from totals to calculate Ordinary Time.\n\nAs above, we believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Ordinary Time - Hourly Rate Per ASL - Employees","Financial","Refer Row 12  less overtime costs described in line 31 for the calculation of Total Labour Cost - Ordinary Time and Row 22 for the Average Productive Work Hours Per ASL - Ordinary Time","Actual",null,"Overtime costs are extracted from SAP (refer row 31 for methodology) and deducted from Total Labour Costs to derive Ordinary Time Labour Costs.\n\nThis is divided by the number of ASLs (in column D of Table 2.11.1) and the Average Productive Work Hours Per ASL - Ordinary Time (in column D of Table 2.11.2) to derive an hourly rate."]
[null,"","Ordinary Time - Hourly Rate Per ASL - Labour Hire","Financial","Refer Row 13  less overtime costs described in line 32 for the calculation of Total Labour Cost - Ordinary Time and Row 23 for the Average Productive Work Hours Per ASL - Ordinary Time","Actual",null,"Overtime costs are calculated from the HR report for each employee for overtime attendance types as hours multiplied by the hourly rates obtained from purchase orders for individual supplementary labour employees, and reported in the labour classification that the employee has been defined. \n\nThis is divided by the number of ASLs (in column D of Table 2.11.1) and the Average Productive Work Hours Per ASL - Ordinary Time (in column D Table of 2.11.2) to derive an hourly rate."]
[null,"2.11.2","Rows 38 - 55\nColumn F - Overtime - Per ASL\n",{"$f":"D28","v":"Financial"},null,"Actual",null,"Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL - Overtime as calculated below.","Actual overtime hours are obtained for each employee from SAP or HR and are attributed to the labour classification assigned to that employee, as described above.\n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Overtime - Per ASL - Employees","Financial","Overtime hours recorded by employees extracted from SAP.\n\nSeparate labour attendance types exist for overtime categories as defined in SA Power Networks' Enterprise Bargaining Agreement.","Actual",null,"Overtime hours are extracted from SAP for each employee for overtime attendance types and reported in the labour classification that the employee has been defined.\n\n",""]
[null,"","Overtime - Per ASL - Labour Hire","Financial","Overtime hours per supplementary labour hire employee provided by HR.","Actual",null,"Overtime hours are provided by HR for each employee for overtime attendance types and reported in the labour classification that the employee has been defined.\n\n"]
[null,"2.11.2","Rows 38 - 55\nColumn G - Overtime - Hourly Rate Per ASL",{"$f":"D31","v":"Financial"},null,"Actual",null,"Weighted average of internal employees and labour hire employee Average Productive Work Hours Hourly Rate per ASL - Overtime as calculated below.","Actual overtime costs are obtained for each employee from SAP for internal employees, and for supplementary labour are calculated as actual overtime hours provide by HR multiplied by their purchase order hourly rate. Overtime costs are attributed to the labour classification assigned to that employee, as described above.\n\nWe believe that this accords with the AER's definition of actual information in that it is based on 'historical accounting information', and 'is not contingent on judgments and assumptions for which there are valid alternatives, which could lead to a Materially different presentation'."]
[null,"","Overtime - Hourly Rate Per ASL - Employees","Financial","Overtime hours per employee are extracted from SAP. Separate attendance types identify overtime categories.\n\nOvertime costs are extracted from SAP. Separate GL accounts identify overtime payments to employees.\n\nSeparate GL accounts also identify additional payroll classifications (e.g. superannuation, payroll, tax, allowances) that may also apply to overtime costs","Actual",null,"Total overtime costs extracted from SAP are multiplied by a percentage calculated in the Annual RIN process to derive labour costs allocated to Standard Control activities (refer explanation in Row 15).\n\nAverage salary and wage payments as described in Row 18 above are used to allocate overtime costs across each labour classification.\n\nAdditional costs described in the Data Source column are allocated on the basis of ASLs and added to the reported labour cost to calculate Total Labour Cost. Overtime costs in SAP represent penalty time payments to employees only. An allocation of allowances (allocated on basis of Normal Time/Overtime ratio) and payroll tax costs (allocated on basis of (Normal Time + Other Pay Related Costs)/Overtime ratio) is made between ordinary time and overtime costs, as overtime also attracts these costs.\n\nOvertime costs are divided by the number of ASLs (in column D of Table 2.11.1) and the Average Productive Work Hours Per ASL - Overtime (in column F of Table 2.11.2) to derive an hourly rate.",""]
["`","","Overtime - Hourly Rate Per ASL - Labour Hire","Financial","Supplementary Labour reports provided by HR - provides details of hours worked for each supplementary labour hire person, including overtime and stand down hours (separately).\n\nOvertime costs for supplementary labour are derived by multiplying overtime hours by hourly rates obtained from purchase orders for individual supplementary labour employees.","Actual",null,"Overtime hours are calculated from HR data for each employee for overtime attendance types and reported in the labour classification that the employee has been defined.\n\nOvertime costs are divided by the number of ASLs (in column D of Table 2.11.1) and the Average Productive Work Hours Per ASL - Overtime (in column F of Table 2.11.2) to derive an hourly rate.\n"]

{"sheet":"2.12 Input Tables","index":10,"n_rows":50,"n_cols":10,"rows_kept":50,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology\n(actual and estimated","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"VEGETATION MANAGEMENT"]
[null,2.12,"Whole table","Financial","Annual RIN workings, SAP, Project Reporting","Actual ",null,"Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table. "]
[null,2.12,"Related Party Contract Expenditure \n(Row 12, Columns H & I)","Financial","N/A","Actual ",null,"No related party margin expenditure or margin has been incurred in the input costs reported for Vegetation management in Row 12."]
[null,"ROUTINE & NON-ROUTINE MAINTENANCE"]
[null,2.12,"Routine and Non-Routine Maintenance\nRows 30 to 53","Financial","SAP/BW reports on functional areas M01-M99 plus A81-A87","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs by classification of GL expenditure codes. Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table. "]
[null,2.12,"Related Party Contract Expenditure \n(Rows 30 to 53, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Estimated","The total of the related party contract expenditure and margin for routine and non-routine maintenance allocated across Rows 30 to 53 represents actual data.  SA Power Networks does not presently have established reports to capture this information broken down at the requested individual category level in Table 2.12.  Endeavours will be made to rectify this issue for future reporting.","Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Maintenance and repair costs allocated across Rows 30 to 53.  These related party values were allocated across the categories in Rows 30 to 53 based on the raw pro rata contract expenditure reported against those categories.  The value of the related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for routine and non-routine maintenance in Table 2.12.1."]
[null,"OVERHEADS"]
[null,2.12,"Network Overheads\nRow 54 ","Financial","SAP Account listings balancing to total Opex and Capex in Table 2.10.1 (excluding Other Distribution Services)","Actual","N/A","For the majority of the data, direct costs were able to be clearly split between direct materials, direct labour, contracts and other costs using SAP reports for the various activities that comprised Table 2.10.1.  In some cases, however, it was necessary to allocate indirect operational support costs and income offsets across categories using pro-rata direct costs for the associated activities on a pro-rata basis.","Network overheads were attributed to distribution service types in accordance with the AER's 2015-20 Distribution Determination and SA Power Networks' Cost Allocation Method."]
[null,2.12,"Network Overheads\nRelated Party Contract Expenditure \n(Row 54, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report (Enerven) /\nInvoice listing from SAP vendor reports (Other related parties)","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  In the 2017-18 regulatory year the consolidated entity (SA Power Networks) also purchased call centre, customer billing, IT support and substation monitoring services from the following related parties, on normal commercial terms and conditions: CKI/HEI Distribution Holdings (Australia) Pty Ltd; and Hutchison Telecommunications (Australia) Ltd.  This provided the total related party contract expenditure and margin associated with Network overheads in Row 54.  The total of these related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for Network overheads in Table 2.12.1.","Related party contract expenditure reported in Column H represents transferred costs from Enerven plus total amounts invoiced (excluding GST) by CKI/HEI Distribution Holdings (Australia) Pty Ltd and Hutchison Telecommunications (Australia) Ltd.  As SA Power Networks does not have a direct control relationship with either CKI/HEI Distribution Holdings (Australia) Pty Ltd or Hutchison Telecommunications (Australia) Ltd, we do not have any information relating to the actual costs incurred by those related parties in providing these services, and consequently are unable to report margins associated with those services in Column I.  It is SA Power Networks' firm belief, however, that the services were provided on standard commercial terms and conditions.  Should actual cost information be required, the AER will need to request this information directly from the related parties.  The margin reported in Column I pertains to services provided by Enerven only."]
[null,2.12,"Corporate Overheads\nRow 55","Financial","SAP Account listings balancing to total Opex and Capex in Table 2.10.2 (excluding Other Distribution Services)","Actual","N/A","For the majority of the data, direct costs were able to be clearly split between direct materials, direct labour, contracts and other costs using SAP reports for the various cost centres and activities that comprised Table 2.10.2.  In some cases, however, it was necessary to allocate indirect costs and income offsets across categories using pro-rata direct costs for the associated cost centres and activities on a pro-rata basis.","Corporate overheads were allocated to distribution service types in accordance with SA Power Networks' Cost Allocation Method."]
[null,2.12,"Corporate Overheads\nRelated Party Contract Expenditure \n(Row 55, Columns H & I)","Financial","Invoice listing from SAP vendor reports","Actual",null,"In the 2017-18 regulatory year the consolidated entity (SA Power Networks) purchased miscellaneous financial and telecommunications services from the following related parties, on normal commercial terms and conditions: CKI/HEI Distribution Holdings (Australia) Pty Ltd; and Hutchison Telecommunications (Australia) Ltd.  The value of the related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for Corporate overheads  in Table 2.12.1.","Related party contract expenditure reported in Column H represents the total amounts invoiced (excluding GST).  As SA Power Networks does not have a direct control relationship with either of the related parties from which services were purchased, we do not have any information relating to the actual costs incurred by the related parties in providing these services, and consequently are unable to report margins as requested in Column I.  It is SA Power Networks' firm belief, however, that the services were provided on standard commercial terms and conditions.  Should actual cost information be required, the AER will need to request this information directly from the related parties."]
[null,"AUGMENTATION"]
[null,2.12,"AUGMENTATION:\nSubtransmission substations, switching stations , zone substations\nRow 56","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nSubtransmission lines\nRow 57","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nHV Feeders\nRow 58","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nDistribution substations\nRow 59","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nLV Feeders\nRow 60","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nOther assets\nRow 61","Financial","Annual RIN workings, SAP, Project Reporting","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table."]
[null,2.12,"AUGMENTATION:\nRelated Party Contract Expenditure \n(Rows 56 to 61, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Estimated","The total of the related party contract expenditure and margin for Augmentation allocated across Rows 56 to 61 represents actual data.  SA Power Networks does not presently have established reports to capture this information broken down at the requested individual category level in Table 2.12.  Endeavours will be made to rectify this issue for future reporting.","Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Augmentation costs allocated across Rows 56 to 61.  These related party values were allocated across the categories in Rows 56 to 61 based on the raw pro rata contract expenditure reported against those categories.  The value of the related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for Augmentation in Table 2.12.1."]
[null,"CONNECTIONS"]
[null,2.12,"CONNECTIONS:\nSimple and Complex Customer connections\nRow 62\n","Financial","Annual RIN workings, SAP, Project Reporting","Actual",null,"Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table. "]
[null,2.12,"CONNECTIONS:\nRelated Party Contract Expenditure \n(Row 62, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Connections.  The value of the related party allocations were deducted from the raw contract expenditure value to produce the final input allocations for Connections in Table 2.12.1."]
[null,"EMERGENCY RESPONSE"]
[null,2.12,"EMERGENCY RESPONSE\nRow 63 to 64","Financial","SAP/BW reports on functional areas E01-E99. In additional a further GL code has been included that captures irrecoverable Third Party Asset Damage.","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs by classification of GL expenditure codes. Adjustments have been made for direct project support costs that can be attributed to direct expenditure, based on a proportional / pro-rata basis across the table. Irrecoverable third party damage has been attributed to contracts as refers to unrecovered contract expenditure.","The total of all categories equals the total of costs reported in Table 2.9.1.\nAs there is no listed category for non-major storm non- MED events in the AER template SA Power have reported all emergency response expenditure as part of 'Major Event Days'. This has been done in order to reconcile the emergency response input table line to the emergency response template 2.9."]
[null,2.12,"EMERGENCY RESPONSE\nRelated Party Contract Expenditure \n(Rows 63 to 64, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Emergency response costs.  The value of the related party allocations were deducted from the raw contract expenditure value to produce the final input allocations for Emergency response in Table 2.12.1."]
[null,"METERING"]
[null,2.12,"METERING\nRow 66","Financial","Functional Area / Activities reports and Order report from SAP","Actual","N/A","SA Power Networks has a comprehensive Functional Area structure within SAP containing capital and operating activities relating to specific lines of work which are identifiable by ID codes.  This enabled the specific reporting of expenditure associated with Metering capital and maintenance activities.  Costs relating to Scheduled Meter Reading were obtained from a specific internal Order report in SAP.  An account view of these SAP reports provided the splits for direct materials, direct labour, contracts and other costs.","The total of all categories equals the total of costs reported in Table 4.2.2, excluding rows 28-30 (Meter Purchases), which are duplicated costs that have been included to comply with RIN requirements."]
[null,2.12,"METERING\nRelated Party Contract Expenditure \n(Row 66, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Metering functions.  The value of the related party allocations were deducted from the raw contract expenditure value to produce the final input allocations for Metering in Table 2.12.1."]
[null,"REPLACEMENT"]
[null,2.12,"REPLACEMENT:\nGeneral Information","Financial","CA RIN 2.2","Estimated","Since all 2.12 Data in the Replacement section are the total summation of certain assets in 2.2, some 2.12 Data are therefore estimated data ","Please reference to the attached table for a mapping of 2.2 assets and 2.12 assets categories","- Assume all figures are required to be rounded to 000's\n\nAll calculation follows the following rules:\n- Material ->Direct Material Cost\n- Labour+Labour OH+Contract -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Direct Material"]
[null,2.12,"REPLACEMENT:\nRow: 'Transformers'","Financial","SAP (BeX reports - L14, L54, L36)","Estimated",null,"Refer 2.2 - same methodology used","Refer 2.2 - same assumptions used"]
[null,2.12,"REPLACEMENT:\nRow: 'Switchgear'","Financial","SAP (BeX reports - L14, L54, L36)","Estimated",null,"Refer 2.2 - same methodology used","Refer 2.2 - same assumptions used"]
[null,2.12,"REPLACEMENT:\nRow: 'SCADA network control and protection systems'","Financial","Network Finance Reports","Estimated",null,"Refer 2.2 - same methodology used","Refer 2.2 - same assumptions used"]
[null,2.12,"REPLACEMENT:\nRow: 'OTHER - Non Category Substation asset replacement/refurbishment'","Financial","SAP (BeX reports - L14, L54, L36)","Estimated",null,"Refer 2.2 - same methodology used","Refer 2.2 - same assumptions used"]
[null,2.12,"REPLACEMENT:\nRelated Party Contract Expenditure \n(Rows 69 to 78, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Estimated","The total of the related party contract expenditure and margin for Replacement expenditure allocated across Rows 69 to 78 represents actual data.  SA Power Networks does not presently have established reports to capture this information broken down at the requested individual category level in Table 2.12.  Endeavours will be made to rectify this issue for future reporting. ","Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Replacement expenditure allocated across Rows 69 to 78.  These related party values were allocated across the categories in Rows 69 to 78 based on the raw pro rata contract expenditure reported against those categories.  The value of the related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for Replacement expenditure in Table 2.12.1."]
[null,"NON-NETWORK EXPENDITURE - IT & Communications"]
[null,2.12,"NON-NETWORK:\nIT and Communications \nRow 79","Financial","SAP\nTable 2.6.1 (IT and Communication opex and capex)","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs. Where necessary expenditure items have been adjusted to equate to the reported totals on a pro-rata basis.","All calculations follows the following rules:\n- Material+Material OH ->Direct Material Cost\n- Labour+Labour OH+Contract Labour -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Remaining costs -> Other Cost"]
[null,2.12,"NON-NETWORK:\nIT and Communications\nRelated Party Contract Expenditure \n(Row 79, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report (Enerven) /\nInvoice listing from SAP vendor reports (Other related parties)","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  In the 2017-18 regulatory year the consolidated entity (SA Power Networks) also purchased IT systems development services from CKI/HEI Distribution Holdings (Australia) Pty Ltd, on normal commercial terms and conditions.  This provided the total related party contract expenditure and margin associated with Non-network IT and Communications in Row 79.  The total of these related party allocations were then deducted from the raw contract expenditure values to produce the final input allocations for Non-network IT and Communications in Table 2.12.1.","Related party contract expenditure reported in Column H represents transferred costs from Enerven plus total amounts invoiced (excluding GST) by CKI/HEI Distribution Holdings (Australia) Pty Ltd.  As SA Power Networks does not have a direct control relationship with CKI/HEI Distribution Holdings (Australia) Pty Ltd, we do not have any information relating to the actual costs incurred by the related party in providing these services, and consequently are unable to report margins associated with those services in Column I.  It is SA Power Networks' firm belief, however, that the services were provided on standard commercial terms and conditions.  Should actual cost information be required, the AER will need to request this information directly from the related parties.  The margin reported in Column I pertains to services provided by Enerven only."]
[null,"NON-NETWORK EXPENDITURE - Excluding IT & Communications"]
[null,2.12,"NON-NETWORK:\nMotor Vehicles\nRows 80","Financial","SAP\nTable 2.6.1 (Motor Vehicle opex and capex)","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs. Where necessary expenditure items have been adjusted to equate to the reported totals on a pro-rata basis.","All calculations follows the following rules:\n- Material+Material OH ->Direct Material Cost\n- Labour+Labour OH+Contract Labour -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Remaining costs -> Other Cost"]
[null,2.12,"NON-NETWORK:\nMotor Vehicles\nRelated Party Contract Expenditure \n(Row 80, Columns H & I)","Financial","N/A","Actual ",null,"No related party margin expenditure or margin has been incurred in the input costs reported for Motor vehicles in Row 80."]
[null,2.12,"NON-NETWORK:\nBuildings and property\nRows 81","Financial","SAP \nTable 2.6.1 (Buildings and Property opex and capex)","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs. Where necessary expenditure items have been adjusted to equate to the reported totals on a pro-rata basis.","All calculations follows the following rules:\n- Material+Material OH ->Direct Material Cost\n- Labour+Labour OH+Contract Labour -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Remaining costs -> Other Cost"]
[null,2.12,"NON-NETWORK:\nBuildings and property\nRelated Party Contract Expenditure \n(Row 81, Columns H & I)","Financial","Specific SAP GL accounts and Functional Area report.","Actual",null,"Since 1 January 2018, SA Power Networks has had specific General Ledger accounts established in SAP to identify transfers to the distribution business from its affiliated entities, Enerven Energy Infrastructure Pty Ltd and Enerven Energy Solutions Pty Ltd (collectively referred to as Enerven).  One account reports the transfer of direct costs from Enerven, while a second account reports the margin associated with those transfers.  These General Ledger accounts were run against SA Power Networks' Functional Area structure for the half year ended 30 June 2018.  This provided the total related party contract expenditure and margin associated with Buildings and Property costs.  The value of the related party allocations were deducted from the raw contract expenditure value to produce the final input allocations for Buildings and property in Table 2.12.1."]
[null,2.1,"NON-NETWORK:\nOther\nRows 82","Financial","SAP\nTable 2.6.1 (\"Other\" opex and capex)","Actual",null,"SAP reports provided splits for materials, labour, contracts and other costs. Where necessary expenditure items have been adjusted to equate to the reported totals on a pro-rata basis.","All calculations follows the following rules:\n- Material+Material OH ->Direct Material Cost\n- Labour+Labour OH+Contract Labour -> Direct Labour Cost\n- Services ->Contract Cost\n- Vehicles -> Other Cost\n- Remaining costs -> Other Cost"]
[null,2.12,"NON-NETWORK:\nOther\nRelated Party Contract Expenditure \n(Row 82, Columns H & I)","Financial","N/A","Actual ",null,"No related party margin expenditure or margin has been incurred in the input costs reported for Non-network Other in Row 82."]

{"sheet":"4.2 Metering","index":11,"n_rows":29,"n_cols":10,"rows_kept":29,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"4.2.1 - METERING DESCRIPTOR METRIC"]
[null,"4.2.1","All","Non-financial","The quantities for all meter stock item codes have been extracted from the CISOV database. This meter population report has been analysed to determine the various meter types. \nCIS-OV database","Estimated","While most of this is purportedly 'Actual' information, we have received conflicting messages about its reliability. They acknowledge it's not perfect but say it is 'the best we have'. As noted at right, they are confident about their analysis of meter types.","Meters sorted into different types by way of stock item code. Certain meter stock item codes can be used for either Type 1-4 or Type 5 installations. Similarly, certain stock item codes can be used for Type 5 or Type 6 installations. To overcome this issue the actual Type 5 population was obtained from the CIS-OV database. The relevant stock item code populations could then be split and assigned appropriately. \nBesides the abovementioned stock item codes, the remaining meters have specific characteristics to suit the different installation types so we can be confident that the categorisation for the remaining stock item codes are correct.","We are reporting 'meter numbers' here, which will differ from the number of NMIs and from customer numbers because a NMI and a customer can have more than one meter and a customer can have more than one NMI.\nWhere the AER has asked for Type 4 meters, we have assumed that they were asking for Type 1, Type 2, Type 3, and Type 4 meters.","Meter number data is as at 03 August 2018. Although this differs from the end of period date (30 June 2018), it is expected that there is minimal variation in meter number data between these dates. \nMeter T1-4 include both alternative control services meters (those installed for free before July 2005) and negotiated distributed services (NDS) meters (all others). All T5 meter provision services are NDS. A very small number of T6 meters are NDS."]
[null,"4.2.2 - COST METRICS"]
[null,"4.2.2","Meter Purchases\nRows 28-30","Financial","SAP","Estimated","Meter purchases are not recorded by NER meter type. Some meters can be configured as either Type 5 or 6. The analysis of meters into Type 5 and 6 requires assumptions to be made regarding the meter model and capabilities.","Direct report from SAP showing meter models and costs, analysed into meter types 5 and 6.",null,"The costs shown are actual costs. The costs of meters is also included in New Meter Installation and Meter Replacement expenditure categories. This cost has been netted from total metering costs for reconciliation purposes."]
[null,"4.2.2","Meter Purchases\nRows 28-30","Non-financial","SAP","Estimated","Meter purchases are not recorded by NER meter type. Some meters can be configured as either Type 5 or 6. The analysis of meters into Type 5 and 6 requires assumptions to be made regarding the meter model and capabilities.","Direct report from SAP showing meter models and costs, analysed into meter types 5 and 6.",null,"The volumes shown are actuals. Meters purchased are included in also New Meter Installation and Meter Replacement volumes."]
[null,"4.2.2","Meter Testing\nRows 31-33","Financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed service volume and where possible meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. It was not possible generate a report from SAP that combined this data with the costs associated with each service order. The costs relating to meter testing activities were collected from SAP by order and cost component.  The cost and volume data were combined to provide primary testing costs for each meter type by year.  \nMeter Services - Meter Services reviewed their Annual Meter Testing Log to determine volumes and meter services timesheets to identify order numbers related to meter testing. Order numbers were run in SAP in identifying costs.  Order numbers effectively provide the split between Types 4, 5 and 6 other than order numbers for cyclical testing data that needed to be apportioned between Type 5 and 6. Metering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item."]
[null,"4.2.2","Meter Testing\nRows 31-33","Non-financial","SAP\nMetering Maintenance and Replacement Plan","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed volume and meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. \nMeter Services - Meter Services reviewed their Annual Meter Testing Log to determine volumes. Order numbers effectively provide the split between Types 4, 5 and 6 other than order numbers for cyclical testing data that needed to be apportioned between Type 5 and 6. Metering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item."]
[null,"4.2.2","Meter Investigations\nRows 34-36","Financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed service volume and where possible meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. It was not possible generate a report from SAP that combined this data with the costs associated with each service order. The costs relating to meter investigation activities were collected from SAP by order and cost component.  The cost and volume data were combined to provide primary investigation costs for each meter type by year.  The actual meter costs are not costed against individual service orders so these costs were allocated to meter type based on a manually maintained data sheet showing meter investigation quantities. \nMeter Services - The cost are identified by running SAP order numbers that are related to meter advice and investigations. The volumes and split between Types 4, 5 and 6 are estimated based on the order numbers. Tasks volumes are not recorded due to its adhoc nature; the number of tasks was based on the allocated budget allocation per task divided by total cost. "]
[null,"4.2.2","Meter Investigations\nRows 34-36","Non-financial","SAP\nMetering Services' spreadsheet \"Meter Test Summary\"","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed service volume and where possible meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. \nMeter Services - Order numbers effectively provide the split between Types 4, 5 and 6.  Tasks volumes are not recorded due to its adhoc nature; the number of tasks was based on the allocated budget allocation per task divided by total cost. "]
[null,"4.2.2","Scheduled meter reading\nRows 37-39","Financial","Contractor Invoice Summary","Estimated","For cyclic reading the quantities are based around the completion of a monthly round of cycle days rather than a completed calendar month, as months are not always the same length we are not always able to complete a round of cycle dates within the calendar month, this means that from an invoicing and statistical perspective we based our numbers around cycle days and not calendar months.","Scheduled meter read data is uploaded to the Customer Information System. Statistical quantities are sourced from the Meter Reading performance report. This data is forwarded to the meter reading provider and forms the basis for invoicing. Annual costs are sourced from SAP.","T5/T6 split is based on relevant volumes"]
[null,"4.2.2","Scheduled meter reading\nRows 37-40","Non-financial","Meter Reading Performance Report","Estimated","For cyclic reading the quantities are based around the completion of a monthly round of cycle days rather than a completed calendar month, as months are not always the same length we are not always able to complete a round of cycle dates within the calendar month, this means that from an invoicing and statistical perspective we based our numbers around cycle days and not calendar months.","Scheduled meter read data is uploaded to the Customer Information System. Statistical quantities are sourced from the Meter Reading performance report. This data is forwarded to the meter reading provider and forms the basis for invoicing. "]
[null,"4.2.2","Special Meter Reading\nRows 40-42","Financial","N/A",null,null,null,null,"Special MR is a Negotiated Distribution Service"]
[null,"4.2.2","Special Meter Reading\nRows 40-43","Non-financial","N/A",null,null,null,null,"Special MR is a Negotiated Distribution Service"]
[null,"4.2.2","New Meter Installation\nRows 43-45","Financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","Detailed service volume and where possible meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. It was not possible generate a report from SAP that combined this data with the costs associated with each service order. The costs relating to meter installation activities were collected from SAP by order and cost component. The cost and volume data were combined to provide primary installation costs for each meter type by year. The actual meter costs are not costed against individual service orders so these costs were allocated to meter type based on a manually maintained data sheet showing meter installation quantities.","All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","New Meter Installation\nRows 43-46","Non-financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","Detailed volume data was extracted from SAP at the service order level to ascertain the volumes of relevant services.","All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Replacement\nRows 46-48","Financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed volume data was extracted from SAP at the service order level to ascertain the volumes of relevant services. It was not possible generate a report from SAP that combined this data with the costs associated with each service order. The costs relating to meter replacement activities were collected from SAP by order and cost component.  The cost and volume data were combined to provide primary replacement costs for each meter type by year.  The actual meter costs are not costed against individual service orders so these costs were allocated to meter type based on a manually maintained data sheet showing meter replacement quantities. \nMeter Services - The costs data was extracted from SAP by relevant order numbers.  Metering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task and meter type. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item. ","All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Replacement\nRows 46-49","Non-financial","SAP\nMetering Maintenance and Replacement Plan","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","The sum of Customer Connect and Meter Services data: \nCustomer Connect - Detailed volume data was extracted from SAP at the service order level to ascertain the volumes of relevant services. Meter Services - Volumes are based from meter services job logs and work orders.  Metering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item.","All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Maintenance\nRows 49-51","Financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","Meter maintenance costs were identified by running Meter Services order numbers related to meter maintenance in SAP.  Volumes were identified based from the job logs and the split between Types 4, 5 and 6 were based on the order numbers.\nMetering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item.","The calendar year to financial year adjustment assumes that work undertaken evenly throughout the year."]
[null,"4.2.2","Meter Maintenance\nRows 49-52","Non-financial","SAP","Estimated","We do not collect data as it was sought, particularly in respect of the different types of meters.","Meter maintenance volumes were identified based from the job logs and the split between Types 4, 5 and 6 were based on the order numbers.  Metering Services (M11) metering work from 01-07-2017 to 31-06-2018 was extracted from SAP, there are separate work orders for each task. The data was reviewed and each work order was aligned to the AER specified task. The job log was used to determine the number of tasks per specified item. ","The calendar year to financial year adjustment assumes that work undertaken evenly throughout the year."]
[null,"4.2.2","Remote MR (T4) \nRow 52","Financial",null,null,null,null,null,"SAPN are not a T4 MDA"]
[null,"4.2.2","Remote Meter Reconfigure (T4)\nRow 53","Financial",null,null,null,null,null,"SAPN are not a T4 MDA"]
[null,"4.2.2","Other Metering\nRows 54-57","Financial",null,null,null,null,null,"There are no \"other metering costs\""]
[null,"4.2.2","IT infrastructure cap/opex (T4)\nRows 58-59","Financial",null,null,null,null,null,"Minor amount only reported as IT costs in Non-Network template"]
[null,"4.2.2","Comms infrastructure cap/opex (T4)\nRows 60-61","Financial",null,null,null,null,null,"SAPN are not a T4 MDA"]

{"sheet":"5.2 Asset Age","index":12,"n_rows":29,"n_cols":10,"rows_kept":29,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"5.2.1 - ASSET AGE PROFILE - GENERAL COMMENTS"]
[null,5.2,"General Assumption\nApplies to the whole 5.2 Tab","Non-financial",null,null,null,"Asset installation year is recorded in calendar years, thus for consistency, this format is followed in general otherwise where stated differently i.e. data entered for 2017-18 corresponds to 2018 data and data entered for 2016-17 corresponds to 2017 data. \nFor the 17/18 financial year asset population; functional location for Reclosers, Sectionalizer, Pole top and Kioskmounted transformer and Groundlevel Switchgear was extracted from SAP and replacement data was added to that.\nFor Pole, OH_Conductor and UG_Cables, the new OH_Conductor and UG_Cable added to the network was taken from GIS and the replacement data was added to that.",null,"Applies to Poles, Transformers Pole top and Kiosk mounted, Ground level Switchgear, Recloser, Sectionalizer"]
[null,"5.2.1 - ASSET AGE PROFILE"]
[null,"5.2.1","ECONOMIC LIFE (YEARS)\nMean and Standard Deviation\nColumns D & E","Non-financial","Repex model\nHistorical CA RIN","Estimated","Mean and Standard Deviation are all estimated figures based on limited asset failure/replacement information","1. Average annual asset replacement volumes have been calculated for each asset category\n2. Using goal seek in Repex model to calibrate the mean lives","2016/17 data has been used as by the time this RIN is prepared SAPN hasn't rerun the Repex model with 2017/18 data yet"]
[null,"5.2.1","5.2 Asset Age Profile\nPOLES; Rows: 124-131\n\nROWS: (<=11kV STOBIE;\n>11kV & <= 33kV STOBIE; \n>33kV & <=66kV STOBIE; \n>66kV & <=132kV STOBIE) \nPole Refurbished;STOBIE\nCOLUMNS: (2017/18, 2016/17 - 2008/09)","Non-financial","Asset Replacement 2017/18 data, Inventory data 2016/17 - 2008/09, SAP data","Estimated","An estimate is required as actual data does not exist. Stobie poles have been used extensively throughout the distribution network. \n\nIn 2017/18, most poles have been captured through the Pole Inspection Program which resulted in Pole Volume reducing from 743,000 to 647,000. Even though, the exact number/age/highest operating voltage of all poles are yet to be determined and hence an estimation is required.","Asset Replacement data was used from 2009-2018. From inventory data it was found that 27,940 poles were produced between 2009 and 2018, with 3,500 in 2017/18\n\nThe maximum operating voltage of poles was estimated based on the model number.\n\nPoles produced for Electra net were excluded from the analysis.\n\nSince less than 0.01% of poles are 132kV, it has been omitted from the report\n\nSAP Notification data was used for plated poles since 2006/07\n\nFor 2017/18, Asset Replacement data from CA -2017/18 2.2 Repex was used.","It was assumed that pole production date was equal to its installation date. Pole Production data for inventory was used in this instance.\n\nFor certain pole models which could be used for both 19kV and 33kV it was assumed that 70% were used for 19kV and the remaining 30% used for 33kV.\n\n","The newly installed poles were added to the last regulatory year 2017-18. This data was sourced from the 2.2 Repex Asset Replacement data for 2017-18\n\n"]
[null,"5.2.1","5.2 Asset Age Profile\nPOLES; Rows: 124-131\n\n (<=11kV STOBIE; \n>11kV & <= 33kV STOBIE; \n>33kV & <=66kV STOBIE; \n>66kV & <=132kV STOBIE) \nPole Refurbished;STOBIE\nCOLUMNS: (2007/08-1910/11)","Non-financial","RIVA Pole data,\nSAP data, \nGIS data","Estimated","An estimate is required as actual data does not exist. Stobie poles have been used extensively throughout the distribution network. \n\nIn 2017/18, most poles have been captured through the Pole Inspection Program which resulted in Pole Volume reducing from 743,000 to 647,000. Even though, the exact number/age/highest operating voltage of all poles are yet to be determined and hence an estimation is required.","1. This population of stobie poles was estimated by cross-referencing a (RIVA) SAP extract of all stobie poles with a GIS extract of all stobie poles.\n2. A pole was counted when it was identified as being present in both databases.\n3. The resulting pole number was then scaled to meet cooperate numbers for the period between 1910 to 2008.\n4. The installation year column was updated as follows: \n(a) Replacement year or platted year data was used first, where not applicable then\n(b) Installation year according to SAP records was used then,\n(c) An average of known pole year per Feeder was used, and after that,\n(d) Feeder date (an average installation date of poles on the Feeder the pole belongs) was used\n\nThere was no data available on pole refurbishment before 2007.","It was assumed that the corporate numbers (GIS) are a fair representation of the pole population.  "]
[null,"5.2.1","OVERHEAD CONDUCTORS BY: \nHighest Operating Voltage; Rows 31-39\n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV  ; SWER\n˃ 11 KV & < = 22 KV ; SINGLE-PHASE\n˃ 11 KV & < = 22 KV ; MULTIPLE-PHASE\n> 22 KV & < = 66 KV\n","Non-financial","SAP OH Conductor data;\nGIS Data","Estimated","An estimate is required as actual data does not exist. OH conductor has been used extensively throughout the distribution network. \n\n\nData capture programs have not yet been able to measure the exact number/age/highest operating voltage of all OH conductor. Hence an estimation is required.","1. A departmental master list establishing a conductor age profile for OH Conductors, done in May of this year, was obtained. This master list contains an installation year column where installation year calculated/estimated:\n\nI. For HV Conductors by:\na) Using older date of two adjacent poles (from a list of all poles sorted in order of adjunct to each other\nb) Using average pole date in the same feeder\nc) Using average Transformer date in the same feeder\nd) Using average switching cubicle date in the same feeder\ne) Use Feeder start-up date (get from SAP)\n\nII. For LV Conductors by:\na) Pole population was broken-down per feeder then each feeder was broken-down per installation year. So each installation year showed pole count as a ratio of the total pole in the parent feeder. \nb) LV Conductor route length was taken per feeder with each feeder showing the total route length of LV Conductors within it.\nc) By multiplying route length per feeder b) with pole distribution a), the distribution of route length within a feeder per year is obtained. \n\nThe master list of was cross-referenced with OH conductors from GIS.\n\nConductors appearing in both databases were counted. \n\nA lookup of GIS conductors against the installation year column in the master list was used to obtain installation year. \n\nRoute length data from the GIS data based was used to calculate route length.\n\nConductor length was taken to be route length multiplied by number of conductors per span (length between two poles carrying conductors). \n\nFor 2017-18, figures were obtained from 2.2 Repex CA RIN Asset Replacement section\n\nFor 2008-2017, figures were obtained from the last RIN exercise\n\n","1. Conductors less than 10 meters in length in the LV_Service Conductor database were assumed to be service lines and were not counted in this exercise.\n\n2. The departmental master list used for part of this work was assumed to have the most correct  installation year information available. \n\n3. GIS data was assumed to have the most accurate route length data.\n\n4. For LV Conductors, it was assumed the conductor and associated poles were erected/installed at the same time.  \n\n5. The following multipliers are used when converting from Route length to conductor length:\n- LV: 4x\n- 19kV: 1x\n- All others: 3x "]
[null,"5.2.1","UNDERGROUND CABLES BY: \nHighest Operating Voltage; Rows 40-47\n˂ = 1 KV\n> 1 KV & < = 11 KV\n> 11 KV & < = 22 KV\n> 22 KV & < = 33 KV\n","Non-financial","SAP, GIS, Cable Drawings, Network Record, TF Database","Estimated","An estimate is required as actual data does not exist. UG Cable has been used extensively throughout the distribution network. \n\nData capture programs have not yet been able to measure the exact number/age/highest operating voltage of all UG Cables. Hence an estimation is required.","I. For HV Cable by:\na) Pad TF population was broken-down per feeder then each feeder was broken-down per installation year. So each installation year showed Pad TF count as a ratio of the total Pad TF in the parent feeder\nb) HV Cable route length wastaken per feeder with each feeder showing the total route length of HV cable within it\nc) by multiplaying HV cable route length per feeder (b) with Pad TF distribution (a), the distribution of HV cable route length within a feeder per year is obtained \nd) for all HV cables with no attached Feeder or attached to a Feeder with no known TF, the volume will be evenly distributed to all HV cables with known info\n\nII. For LV Cable by:\na) Supplying TF installation date\nb) Using average Transformer date in the same feeder\nc) Using average switching cubicle date in the same feeder\nd) Using average pole date in the same feeder\ne) Use Feeder start-up date\n\nFor 2017/18 data, use 2.2 replacement volume as installation volume","As described on the left cell"]
[null,"5.2.1","SERVICE LINES BY: \nConnection Voltage, type and complexity \nRows 48-63\n˂ = 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n˂ = 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE","Non-financial","CIS/OV and NES","Estimated","An estimate is required as actual data does not exist. Service lines have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age of all service lines. Hence an estimation is required.","Customer information was extracted from CIS/OV where one customer would represent one service line. In addition any units or flats were combined into one record for the group to represent the one service line for the group. The age of the service lines was based on their minimum installation date. Based on this data an age profile was created with the proportions of the total number of service lines installed each year.  The age profile obtained from the CIS/OV data was then used to  achieve the number of service lines.\nFor the last regulatory year a data dump for new service installation is obtained from IT and combined with replacement data (DD and FM notifications) to determine the of service lines to be added. Then the replacements are deducted from old service lines (55 year old and older) proportionally.","It is assumed every customer has a service line however all flats/units have only one service line for the group.\nIt is assumed that any records which list the age of a service line installed before 1940 is inaccurate and hence excluded from this analysis.\nIt is assumed that all residential connections are of simple type.\nIt is assumed that all commercial and industrial connections are of complex type"]
[null,"5.2.1","TRANSFORMERS BY: \nMounting Type; Highest Operating voltage; Ampere Rating; Number of Phases (at LV) \nRows 64-92, 132-134\n*LINE TRANSFORMER ONLY\nPOLE MOUNTED ; \nKIOSK MOUNTED;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED","Non-financial","SAP + NOCLOG + Operational Asset Management Ground level Switchgear Replacement Spreadsheet + Inventory Data+ TF Database","Estimated","An estimate is required as actual data does not exist. Transformers and voltage regulators have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/type/voltage/capacity/phasing of all transformers. Hence an estimation is required","Base population:\n- See document attached in Column J\n\nA. New installations to be added into Base population:\n- For all new installations in this year, inventory data has been used to determine the quantity/type/voltage/capacity/phase and distribute the final numbers to corresponding categories\n\nB. Replaced assets to be taken out from Base population:\n- From 2.2 we have a list with all replaced TFs which mostly have TF ID attached to them\n- We run through these TF IDs in a TF database to find quantity/type/voltage/capacity/phase/installation year information and take the final numbers out from corresponding categories and year\n\nSteps: \n1. Data from previous years copied to new spreadsheet.\n2. Substation TFs removed from data in step 1 leaving only line TFs\n3. New line installations added to step 2\n4. Total substation TFs obtained from substation group and added to step 3\n5. Line TF replacements taken out of step 4\n6.  Result of step 5 adjusted for figures less than 0. To balance the -1 value in a cell in any row, you can subtract 1 from the last cell on the right (oldest year) where the value is greater than zero. By following this method the -1 value will become 0\n7. Special step: obtain total distribution TF counts from SAP, scale up/down distrution TFs from above steps to align with the total SAP count","1. Base population:\n- See document attached in Column J\n\n2. Balancing of assets where a calculation as resulted in an unrealistic number, such as -1 (see step 6 in column H)."]
[null,"5.2.1","TRANSFORMERS BY: \nMounting Type; Highest Operating voltage; Ampere Rating; Number of Phases (at LV) \nRows 64-92\n*SUBSTATION TRANSFORMER ONLY\nPOLE MOUNTED ; \nKIOSK MOUNTED;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED","Non-financial","SAP","Actual",null,"1. Start with SAP extract of Substation TF & Regulator asset records\n2. Removed Aux Station supply and SWD TF types\n3. Removed unregulated TF assets.\n4. Removed SAPN Training Centre assets.\n5. Added records for new TFs installed during 2017-18, but not captured in SAP updates as of 30/6/2018.\n6. Removed records for TFs decommissioned during 2017-18, not captured in SAP updates as of 30/6/2018.\n7. Updated/corrected records with missing rating/acquisition date data (various sources - including SAP order data, plant running sheets, test certificates etc)\n8. Final population combined and summarised by year of installation (assumed as the SAP 'Acquisition' Year), highest operating voltage and nominal kVA rating to populate age profile.","1. SAP 'Acquisition' date has been used to calculate the age of each asset - meant to represent the original installation date of the asset (e.g. a TF acquired in 1980 but installed/recommissioned in 2010 will be shown as a 1980 TF in the age profile.)\n2. Equipment acquisition dates (by calendar year) have been allocated to the financial year that begins in that calendar year (e.g. a TF with an acquisition date of 1966 has been recorded as installed in 1966/67).\n3. TF records are allocated to RIN asset categories by their:\n- highest operating voltage / SAP 'rated voltage' (e.g. a 0.4/11kV step-up TF is included in 11kV data)\n- nameplate kVA rating\n- number of phases on the secondary side of the TF","Substation TFs of a 'Pole top' construction are included in 'Ground / Outdoor' categories to separate them from 'traditional' pole mounted distribution assets.\nSingle exception is substation installed single phase regulators - all are reported under 'Pole Top' category\n\nAssets included in age profile data:\n- Substation TFs & Regs in service at 30/6/18:\n- Hot/Cold Standby TFs & Regs\n- TFs/Regs associated with mobile plant\n- Earthing and GSU TFs at Kingscote Substation\n- HV/LV TFs when allocated to a SSD substation and used for primary power distribution (i.e. not a station AUX TF)\n\nExclusions to population numbers:\n- Unregulated TFs & Regs\n- TFs & Regs installed at the Angle Park and Davenport training substations\n- Substation AUX TFs"]
[null,"5.2.1","SWITCHGEAR BY: \nHighest Operating Voltage; Switch Function \nRows 93-106\nSwitch Categories\n","Non-financial","SAP","Actual",null,"1. Start with SAP extract of Substation CB asset records\n2. Removed LV circuit breakers types\n3. Removed unregulated CB assets.\n4. Updated/corrected missing SAP equipment record voltage/acquisition date data (various sources - including SAP order data, plant running sheets, test certificates etc)\n5. Removed SAPN Training Centre assets.\n6. Removed records for CBs decommissioned during 2017-18, not captured in SAP updates as of 30/6/2018.\n7. Added records for CBs installed during 2017-18, not captured in SAP as of 30/6/2018.\n8. Updated/corrected records with missing rating/acquisition date data (various sources - SAP order data, plant running sheets, test certificates etc)\n9. Final population summarised by year of installation (assumed as the SAP 'Acquisition' Year) and operating voltage to populate age profile.","1. SAP 'Acquisition' date has been used to calculate the age of each asset - meant to represent the original installation date of the asset (e.g. a CB acquired in 1980 but installed/recommissioned in 2010 will be shown as a 1980 CB in the age profile.)\n2. Equipment acquisition dates (by calendar year) have been allocated to the financial year that begins in that calendar year (e.g. a CB with an acquisition date of 1966 has been recorded as installed in 1966/67).\n3. CB records are allocated to RIN asset categories by their SAP 'operating voltage' (e.g. a 33kV rated CB operating at 11kV has been recorded as an 11kV CB in the age profile.)","Included in population data:\n- HV CBs In service at 30/6/18.\n- CBs associated with mobile plant.\n- Substation 11kV OCB RMU CBs\n\nExclusions to population numbers:\n- Unregulated CB assets\n- CBs installed at the Angle Park and Davenport training substations\n- Substation switching cubicles\n- Substation reclosers"]
[null,"5.2.1","PUBLIC LIGHTING BY: \nAsset Type; Lighting Obligation\nRows 107-115","Non-financial"]
[null,"5.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \nFunction Row 116\nField Devices","Non-financial","PSS6/RIVA Project","Actual",null,"Number of relays currently in commission is available in PSS6. Where the exact date of relay commissioning is known from  the RIVA project, the relay is allocated to that year. Otherwise, relays are evenly distributed over the period in which the relays were being purchased.","PSS6 is up to date as of 2017/18. Relay installation is approximately evenly distributed over the period in which they were being purchased."]
[null,"5.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \nRow 118, 120, 121 \nCommunications Network Assets, Communications Site Infrastructure and Communications Linear Assets ","Non-financial","Manual entry","Estimated","Complete record keeping of install date has not been done in the past.  But the last three years' entries are correct.","Go through each projects in the Analysis reports and calculate the number of new installs.","Assumptions for old equipment, not for this year's installs"]
[null,"5.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \nFunction Row 119\nMaster Station Assets\n","Non-financial","SCADA configuration files and \nSCADA design/secondary drawings","Actual",null,"Data of assets mostly obtained from SCADA configuration files, however some assets were obtained prior to privatisation and hence the records are limited. Based on design drawings this data is its most accurate state."]
[null,"5.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS BY: \nFunction Row 119\nMaster Station Assets\n","Non-financial","Microsoft CRM","Actual",null,"Projects were filtered in CRM to obtain the number of projects completed in 2017/2018 that installed SCADA to a substation that previously did not have any SCADA."]
[null,5.2,"OTHER BY: \nAsset Age Profile - DNSP Defined  \nRow 131\nPole Refurbished; STOBIE\n","Non-financial","SAP","Estimated","Refurbished poles are determined in 2.2 as an estimation, this row has naturally become \"estimated\" itself","Pole plating notifications are obtained from 2.2","It is assumed that all replaced poles are unrefurbished poles as we don't currently have the information if replaced pole is refurbished or not"]
[null,5.2,"OTHER BY: \nAsset Age Profile - DNSP Defined  \nRow 135\nRecloser; SWITCHGEAR\n","Non-financial","SAP and recloser maintenance plan provided by Richard Bulalet (recloser and sectionaliser asset expert)","Estimated","An estimate is required as actual data does not exist. Reclosers have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/type of all reclosers. Hence an estimation is required.","An amalgamation of the three sources was used as a starting point removing all duplicates. For the majority of reclosers listed in the recloser maintenance plan the first installed date was recorded. The information provided from SAP although it did not provide first installation dates it did detail whether the recloser was a substation or line recloser. Information from PSS6 did not provide first installation date information or the type of recloser however it did detail the type of recloser. Between the three sources of information there was much overlap of reclosers and hence the majority of required information was available. \n\nAs the type of most reclosers was also known, for those reclosers without a first installation date it was able to be estimated based on the vintage of the recloser type.\n\nFor those reclosers still without a first installation date, they were evenly distributed between 1970 and 2010 as this is when the majority of the recloser population was installed.\n\nFor those reclosers still without a type they were distributed to reflect the known population. ","It is assumed that the known population of reclosers is a fair representation of the total population it includes both (distribution lines + substation)"]
[null,"5.2.1","OTHER BY: \nAsset Age Profile - DNSP Defined \nRow 136\nSectionalizer; SWITCHGEAR\n","Non-financial","SAP, Sectionaliser Database provided by Richard Bulalet (recloser and sectionaliser asset expert)","Estimated","An estimate is required as actual data does not exist. Sectionalisers have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/Voltage of all reclosers. Hence an estimation is required.","Firstly using the list of sectionalisers found from the equipment search in SAP, first instillation dates were able to be applied from the “Sectionaliser Database” using the ETSA ID of the equipment. In addition the operating voltage of the sectionaliser was able to be found based on the type of sectionaliser. These sectionalisers found as equipment in SAP were able to be matched with those found as functional locations based on the functional location of the sectionaliser. Those sectionalisers found as functional locations were then able to be updated with a type, voltage and first installation date of its corresponding equipment.\n\nFor some sectionalisers a type was also listed under the functional location. Based on advice from the asset expert, those sectionalisers should firstly have their type assigned from the “Sectionaliser Databased”. Those with no associated type from the “Sectionaliser Database” would then have their type assigned based on the type recorded under the functional location if available (NOTE: AK Power and Haycolec sectionalisers are synonymous).\n\nA number of sectionalisers had a type however did not have a first installed year. For these sectionalisers the first installed date was estimated based on the vintage of the type of sectionaliser.\n\nThe remaining sectionalisers with unknown first installation dates were distributed based on the age and operating voltage profiles respectively. ","It is assumed that the known population of sectionalisers is a fair representation of the total population."]
[null,"5.2.1","OTHER BY: \nAsset Age Profile - DNSP Defined  \nRows 137-138\n>= 11 kV & < ≈ 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n> 22 kV & < ≈ 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (switching cubicle)\n","Non-financial","GIS,\nGL Switch Rep and Exp.xlsx, \nMaster Summary Switching Cubicle Profile.xlsx","Estimated","An estimate is required as actual data does not exist. Switch gear has been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/voltage of all switch gear. Hence an estimation is required.","This year, a Master Summary Switching Cubicles spreadsheet, prepared for the previous RIN, was updated and used for this exercise. It was updated in the following steps:\n\n1. GL Switch Replacement and Expenditure data for 2017-18 was obtained.\n2. A lookup of GL Switches from step 1 was done on the Master Summary Switching Cubicles spreadsheet. Matching results in the Master Summary Switching Cubicles spreadsheet were updated to reflect the new installation dates from the Replacement and Expenditure list. \n3. A pivot table of the updated Master Summary Switching Cubicles spreadsheet from step 2 is used to count the GL Switches according to date of installation.\n4. This result is pasted in the 5.2 RIN.\n","1. The Master Summary Switching Cubicles spreadsheet is assumed to have the most UpToDate information on GL Switch installation year and count for the all GL Switches up to the previous year.\n2. GL Switch Replacement and Expenditure data for 2017-18 is accepted has having the most UpToDate data on GL Switch replacements.  "]
[null,"5.2.1","OTHER BY: \nAsset Age Profile - DNSP Defined   \nRow 139\nPipework Bus Substation Replacements","Non-financial","SAP","Actual",null,"1. Pipework Switchyard Asset Plan describes the asset type of the 56 sites to included in the remediation/replacement program.\n2. Age data reported in the 2016-2017 RIN Submission has been used as the starting point for the 2017-2018 Age Profile.\n3. Pipework Bus substation sites are removed from the age profile when the pipework switchyard is decommissioned.","1. Substation age is assumed to be the same as the substation earth grid (used to populate the initial age profile for these assets).\n2. Substation installation for original substation sites are assumed to have occurred in Q3-Q4 of the calendar year of installation (i.e. 1977 calendar year installation has been reported in the 1977-78 financial year). \n3. Switchyard deenergisation date has been taken as the date of decommissioning."]
[null,"5.2.1","OTHER BY: \nAsset Age Profile - DNSP Defined \nRows 144-147\nGround Outdoor / Indoor Chamber Mounted; > = 22 kV & < = 33 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  < = 15 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; > 33 kV & < = 66 kV ;  > 15 MVA and < = 40 MVA REFURBISHED\nGround Outdoor / Indoor Chamber Mounted; ˂  22 kV ;  >  600 kVA ; Multiple Phase REFURBISHED\n","Non-financial","SAP","Actual",null,"1. Age profiles for TF & Switchgear refurbishments are identical to the parent (non-refurbishment) RIN asset category.",null,"Note: The reported age profiles for substation asset refurbishments include all installed assets (both refurbished and non-refurbished) within each RIN asset category - This population is a duplication of the parent age profile reported in rows 64 -92.\n\nThe age profiles for refurbished Stobie poles represent the ‘age from plating’ profile for all plated Stobie poles only. This population plus the age profiles reported in 124 – 131 represent the full population of installed Stobie poles on the network.\n"]
[null,"5.2.1","OTHER BY: \nAsset Age Profile - DNSP Defined  \nRows 141-143\n˂ = 11 kV ;  Circuit Breaker REFURBISHED\n> 22 kV & < = 33 kV ; Circuit Breaker REFURBISHED\n> 33 kV & < = 66 kV ; Circuit Breaker REFURBISHED\n","Non-financial","SAP","Actual",null,"1. Age profiles for TF & Switchgear refurbishments are identical to the parent (non-refurbishment) RIN asset category.",null,"Note: The reported age profiles for substation asset refurbishments include all installed assets (both refurbished and non-refurbished) within each RIN asset category - This population is a duplication of the parent age profile reported in rows 93 -106.\n\nThe age profiles for refurbished Stobie poles represent the ‘age from plating’ profile for all plated Stobie poles only. This population plus the age profiles reported in 124 – 131 represent the full population of installed Stobie poles on the network.\n"]

{"sheet":"5.3 Max Demand Network Lvl","index":13,"n_rows":12,"n_cols":10,"rows_kept":12,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"5.3.1 - RAW AND WEATHER CORRECTED COINCIDENT MD AT NETWORK LEVEL  (Summed at transmission connection point)"]
[null,"5.3.1","Raw Network coincident MD","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"Maximum demand observed in 12 month period of metered data"]
[null,"5.3.1","Date MD occurred","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"Date of day when maximum demand occurred"]
[null,"5.3.1","Half-hour time period MD occurred","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"Half-hour when maximum demand occurred"]
[null,"5.3.1","Winter/Summer peaking","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"Season when maximum demand occurred (always Summer)"]
[null,"5.3.1","Embedded Generation","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"Summated demand of all metered embedded generation that exports into SA Power Networks grid (Major Embedded)"]
[null,"5.3.1","Weather corrected (10% POE) network coincident MD\nWeather corrected (50% POE) network coincident MD","Non-financial","Metered data stored in SA Power Networks' Network Energy Site System (NESS)","Actual",null,"The weather-adjusted outcome is based on combining a major customer calculation and a temperature/demand regression for all other customers.\n\nWe determine 10% and 50% POE maximum demand for major business by looking at the diversified maximum demand during February on workdays at the time of co-incident demand (1830 EST, ie 7pm local time is now used).\n\nWe determine10% and 50% POE demand for all other customers by conducting a regression for load at 1830 EST on days when residential air-conditioning is used.  Typical temperatures for 10% POE and 50% POE are determined, and the regression is extrapolated to that temperature.  The period late January to mid-March (workdays) is used, with perhaps 10 to 15 days in that period providing the regression data.\n\nThe same methodology has been used since 2000.  This data now comprises the net load as AEMO does, ie any non-utility scale PV output is treated as a negative customer load.\n"]

{"sheet":"5.4 Max Dem & Utilise - Spatial","index":14,"n_rows":10,"n_cols":10,"rows_kept":10,"cut":false,"hidden":false,"merged":[[7,1,7,9],[1,1,1,3],[1,4,1,9],[6,1,6,9],[9,9,10,9],[9,1,10,1],[9,2,10,2],[9,3,10,3],[9,4,10,4],[9,5,10,5],[9,6,10,6],[8,8,10,8],[8,7,10,7]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accoun","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"5.4.1 NON-COINCIDENT & COINCIDENT MAXIMUM DEMAND"]
[null,"5.4 Definitions\n\nContinuous Metered: Substations that have demand recording equipment permanently installed (SCADA, NGM or Smart Meter) and output regular interval demand recordings with associated date/time stamp.\nDemand: Where available recorded MW/MVA/MVAr, else calculated from recorded AMP.\nSub-transmission substation: A substation that steps down transmission voltage (275kV or 132kV) to a lower voltage (66kV, 33kV or 11kV). SA Power Networks' terminology is Connection Point substation.\nNon-metered: Zone substation that DO NOT have demand recording equipment permanently installed.\nZone substation: A substation that steps down voltage (66kV or 33kV) to a lower voltage (11kV, 7.6kV or 3.3kV)."]
[null,"5.4 Glossary\n\nAEMO: Australian Energy Market Operator\nCF: Coincident Factor\nMD: Maximum Demand\nNESS: Network Energy Sites System\nPoE: Probability of Exceedance\nPF: Power Factor\nPV: Photo Voltaic\nSubsload: Substation Load"]
[null,"5.4.1","All","Non-financial","Demand Forecast Tool Database established by ACIL Allen\n\nPV Installed Capacity March 2017 and March 2018 SAP download\n\nACIL Allen and SAPN created PV calculator\n\nAEMO Forecasting Insights 2017 (SA Forecasts for demand, PV uptake)\n\nDistribution Annual Planning Report 2017/18 to 2021/22 Version 1.0.\n\nSensitive Customers (where data is not published):\nHistorical SA Power Networks Databases (10% PoE and 50% PoE MASTER Load Forecasts 2017, MASTER Substation Transformer Ratings)\n\n\n","Estimated","1. Unknown and possibly out of date normal cyclic ratings for some Sub-transmission Substations (asset owner is ElectraNet).\n\n2. For continuous metered sites, the weather corrected demand forecasts provided are statistically calculated from 2017/18 measured demands and temperatures in combination with a simulation approach to generate a long run distribution of maximum demands from which PoE demands are obtained.\n \n3. For non-continuous metered sites, very limited demand records are available. There is no ability to refer to retrospective “snapshots” of peak demand, or to statistically calculate PoE demands, for the 2017/18 summer.\n\nSome demand records were obtained by installing temporary demand loggers (typically every third year) over the summer period.  There is no guarantee the logger was on site at the same time when the Zone Substation actually peaked.  The captured peak reading is assumed to be the actual peak.\n\n4. PV methodology is based on the behaviour at an independent measured single site – refer to Maximum Demand Forecast Tool (Methodology and Users Guide for SA Power Networks Maximum Demand Forecasting Tool) Section 3.6, Section 3.6.1, Section 3.6.2, Section 3.6.3 and 3.6.4.\n","The following steps were undertaken to compile the data submitted:\n\n1. Substation Rating:\nPublished summer normal cyclic ratings were extracted and collated from the following SA Power Networks’ databases:\n• Sub-transmission Substations – Distribution Annual Planning Report 2016/17 to 2020/21 Version 1.0, nameplate rating used.  NOTE: data was not published in 2017/18 equivalent report.\n• Zone Substations – Distribution Annual Planning Report 2017/18 to 2021/22 Version 1.0, normal rating used 2017/2018.\n• Zone Substations – for sensitive sites and sites that required adjustment (eg: TF change or revised calculated rating), used MASTER Substation Transformer Ratings or emails received from Mark Pynn.\n\n2. Raw Adjusted MD for Continuous Metered Sites:\nRecorded peak MD were extracted and collated from the following SA Power Networks’ demand storage databases:\n• Sub-transmission Substations and some Customer Zone Substations – NESS.\n• Zone Substations – SubsLoad.\nCollation and storage of the above data is within Peak Load Summary Spreadsheet, specific for each Area.\n\nRaw adjusted MD refers to recorded maximum actual power (MW).  The recorded apparent power (MVA) and reactive power (MVAr) at this time were also extracted and collated.   Refer to Assumptions section for the scenario where the unit of MW is not available.\n\nTime of peak refers to local Adelaide time.\n\nWhen a substation was in a temporary abnormal condition (eg: fault condition), demand data was corrected to reflect normal operating conditions.  Long standing abnormal conditions (eg: planned upgrades, major faults) for the majority or entire summer period were generally not corrected.\n\n3. Raw Adjusted MD for Non-Continuous Metered Sites:\nFor non-continuous metered sites, recorded peak MD are not available.  Reported data was obtained and extrapolated simplistically from SA Power Networks’ historically produced 2017 Zone Substation Forecasts (10 POE and 50 POE). \n\n4. Winter / Summer peaking:\nSA Power Networks experiences peak demand during sustained heatwave periods throughout the summer months (large increase in electricity usage primarily due to residential air conditioning).  Recorded summer demands and summer plant ratings are used for forecasting purposes and determining the timing of site upgrades due to lack of spare capacity.\n\n5. Embedded Gens:\nPV installed capacity per Substation for the 2018 summer was collated where available.  Using the ACIL Allen and SAPN PV Calculator as the basis, an estimated amount of PV was calculated for each Sub-transmission and Zone Substation based on the time of day of recorded non-coincident and coincident peak. \n\nEmbedded Gens (other) were included only when the generator operation was deemed consistent throughout the summer and was not operating due to market or weather conditions. Sites include Port Adelaide North, Kilburn, Metro West Region, Prospect and Metro East Region.\n\nThe total amount of generation (PV + other) has been collated in the data submitted.\n\n6. POE Levels for Continuous Metered Sites:\nPlease refer to Maximum Demand Forecast Tool (Methodology and Users Guide for SA Power Networks Maximum Demand Forecasting Tool) document for a detailed explanation of the methodology used to calculate 2017/18 summer non-coincident POE demand forecasts.\n\n• Using 2017/18 measured summer data (demand and temperature), non-coincident 10 POE and 50 POE forecasts (MW) were extracted and collated from the Demand Forecast Tool Database.  The tab of interest is Raw Sim, referring directly to the 2017/18 summer summarised data.  Corresponding MVA and MVAr where then calculated using measured non-coincident PF.\n\n• CF = (Actual peak non-coincident MD) / (Actual peak MD at time of State peak)\n\n• Coincident POE forecast (MW) = Non-coincident POE forecast (MW) x CF\n\n• Coincident POE forecast (MVA) = (Coincident POE forecast (MW)) / (PF at time of State peak)\n\n7. POE Levels for Non-Continuous Metered Sites:\nReported data was obtained and extrapolated simplistically from SA Power Networks’ historically produced Zone Substation Forecasts. \n\n• Assumed ratio between 50 POE and 10 POE is a factor of 0.9 (50 POE = 0.9 x 10 POE).\n\n\n","In compiling the data contained within the table, the following assumptions were made:\n\n1. Sub-transmission Substation Ratings are the nameplate ratings as provided by the transformer owner (ElectraNet) and published within Distribution Annual Planning Report 2016/17 to 2020/21 Version 1.0.\n\n2. Coincident refers to the time of System Peak using local Adelaide time (SA Power Networks peak demand only and excludes ElectraNet direct connected customer demands).  \n\n3. For non-continuous metered Zone Substations, weather corrected forecasts were not produced.  Instead, SA Power Networks employed the methodology as described in Section 2.5.\n\n4. For non-continuous metered Zone Substations, the time of day peak is assumed to be at time of System demand peak (ie: coincident and non-coincident peaks are at the same time).\n\n5. Where actual demand data is only available in Amps, MW and MVA values have been determined assuming nominal voltage and the typical PF of the upstream Sub-transmission Substation.\n\n"]
[null,"5.4.1","ALL","Non-financial","Demand Forecast Tool Database established by ACIL Allen\n\nPV Installed Capacity March 2017 and March 2018 SAP download\n\nACIL Allen and SAPN created PV calculator\n\nAEMO Forecasting Insights 2017 (SA Forecasts for demand, PV uptake)\n\nDistribution Annual Planning Report 2017/18 to 2021/22 Version 1.0.\n\nSensitive Customers (where data is not published):\nHistorical SA Power Networks Databases (10% PoE and 50% PoE MASTER Load Forecasts 2017, MASTER Substation Transformer Ratings)\n\n\n","Actual"]

{"sheet":"6.3 Sustained Intrp","index":15,"n_rows":7,"n_cols":10,"rows_kept":7,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,9]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.2,2,3,4,5,6,7,8]
[null,"CAT RIN Table Ref / EBT RIN Variable Code","RIN Row/ Column/ Cell or All (entire tab)","Financial /\nNon-Financial","Data Source","Actual / Estimated","Justification\n(if estimated)","Methodology \n(actual and estimated)","Assumptions\n(actual and estimated)","SAPN Additional Comments\n(if any)"]
[null,"State the table reference (CA) or Variable Code (EB)","\nState the applicable row, column, cell, or entire tab","\nSelect whether the referenced information is financial or non-financial","\nExplanation of the data source for the referenced information","\nSelect whether the information from data source is either actual or estimated?","\nExplanation of why an estimate is required and why actual data does not exist\n\nFor financial information, explanation of why financial information is not in accordance to the financial reporting framework and any changes, impacts and deviations to accounting policies (for any regulatory years).","\nExplanation of the method applied to provide the requested data. This should include an explanation of how the data was derived from other sources (if applicable) where this was undertaken and explain any allocation the approach applied.","\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"6.3.1 - SUSTAINED INTERRUPTIONS TO SUPPLY (for 2015-16)"]
[null,"6.3.1","Entire tab","Non-financial","OMS / GIS / CIS-OV","Actual",null,"1. The reliability data is extracted from OMS from pre-defined standard regulatory reliability reports and saved in a spreadsheet to assist with formatting the data in accordance with the RIN requirements.\n2. A pivot table is created to identify the outages that occurred for each day of the RIN reporting period.\n3. The date, time, asset ID, feeder classification, reason, detailed reason, no. of affected customers, average duration, effect on unplanned SAIDI, effect on unplanned SAIFI and MED status are then populated by either a 'vlookup' function against the OMS data, mapping table or a specific calculation.\n4. Average duration = Unplanned SAIDI / Unplanned SAIFI\n5. Unplanned SAIDI (by feeder classification) = Unplanned Sustained Customer Minutes / Distribution Customers by  feeder classification\n6. Unplanned SAIFI (by feeder classification) = Unplanned Sustained Customers Interrupted / Distribution Customers by  feeder classification\n7. MEDs are identified by calculating the daily unplanned SAIDI excluding excluded outages for each day and identifying those days that exceed Tmed.","Where an interruption affects a phase(s), the number of customers affected is estimated as follows: 1/3rd if only one LV phase is affected, 2/3rds if two LV phases are affected and 2/3rds if only one HV phase is affected.\nThe only alternative method to the above (with current systems) is to perform a physical field check to determine the actual customers affected where a fuse or fuses have operated.  Not only is this method considered impractical and costly, it is not likely to lead to a materially different outcome to the figures currently reported."]