{"text_format":"1","workbook":"xlsx","n_sheets":18,"sheets":["2.1 Exp Summary","2.2 Repex","2.3 Augex","2.5 Connections","2.6 Non-Network","2.7 Veg Management","2.8 Maintenance","2.9 Emergency Response","2.10 Overheads","2.11 Labour","2.12 Input Tables","4.2 Metering","5.2 Asset Age","5.3 Max Demand Network Lvl","5.3 MD Alternative","5.4 Max Dem & Utilise - Spatial","6.3 Sustained Intrp","Sheet1"],"not_rendered":{"charts":0,"images":2,"macros":0,"external_links":4,"defined_names":55,"comments":6,"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":26,"n_cols":11,"rows_kept":26,"cut":false,"hidden":false,"merged":[[23,7,23,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[17,7,17,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[21,7,21,8],[22,7,22,8],[16,7,16,8],[5,7,5,8],[6,7,6,8],[7,7,7,8],[8,7,8,8],[9,7,9,8],[10,7,10,8],[11,7,11,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[15,7,15,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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","Row 16 - Replacement expenditure","Financial","Table 2.2.1 and Table 2.12","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to the 2014/15 Annual RIN (excluding amount reported as Network Overheads in table 2.10.1) and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.1","Row 17 - Connections","Financial","Table 2.5.1 and Table 2.12","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to the 2014/15 Annual RIN (excluding amount reported as Network Overheads in table 2.10.1) and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.1","Row 18 - Augmentation expenditure","Financial","Table 2.3.4 and Table 2.12 ","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to table 2.3.4 and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.1","Row 19 - Non-network","Financial","Table 2.6.1 and Table 2.12 ","Estimated","Uplift applied to allocate project support component of business overheads on a pro-rata basis between some Capex categories.","Total expenditure has been reconciled to the Capex rows of Table 2.6.1 and represents a portion of the total Non-Network category input costs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.1 and 2.1.3","Rows 20 and 64 - Capitalised network overheads","Financial","Table 2.10.1 and Table 2.12 ","Actual",null,"Total capitalised network overheads for Standard and Alternative Control Services have been reconciled to the Network management line in table 2.10.1 and represents a portion of the the total Network Overhead category inputs in table 2.12.",null,"Reported costs represent Network Overheads charged against the following SA Power Networks' Standard and Alternative Control Capital Activities:  Asset Replacement (includes Metering), Capacity, Connections (includes Metering), Environmental, PLEC, Reliability, Safety and Strategic."]
[null,"2.1.1 and 2.1.3","Rows 21 and 65 - Capitalised corporate overheads","Financial","Table 2.10.2 and Table 2.12 ","Actual",null,"Total capitalised corporate overheads for Standard and Alternative Control Services have been reconciled to the Other Allocated Cost lines under Capitalised Overheads in table 2.10.2 and represents a portion of the the total Corporate Overhead category inputs in table 2.12.",null,"As per SA Power Networks' Cost Allocation Method, superannuation is reported on a cash payments basis for regulatory reporting.  Values represent the capital component of the regulatory adjustment for the difference between superannuation cash contributions and the accounting expense."]
[null,"2.1.1 and 2.1.2","Rows 22 and 46 - Metering","Financial","Not applicable to SA Power Networks","Actual",null,"In accordance with our current classification of services, Metering is classified as either an Alternative Control Service or a Negotiated Distribution Service.  Hence Standard Control Services values are nil."]
[null,"2.1.1 to 2.1.4","Rows 23, 47, 67 and 88  - Public lighting","Financial","Not applicable to SA Power Networks","Actual",null,"In accordance with our current classification of services, Public Lighting  is classified as a Negotiated Distribution Service.  Hence Standard and Alternative Control Services values are nil."]
[null,"2.1.2","Row 40 - Vegetation management","Financial","Table 2.7.2 and Table 2.12","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to the 2014/15 Annual RIN (excluding amount reported as Network Overheads in table 2.10.1) and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.2","Row 41 - Maintenance","Financial","Table 2.8.2 and Table 2.12","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to the 2014/15 Annual RIN (excluding amount reported as Network Overheads in table 2.10.1) and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.2","Row 42 - Emergency response","Financial","Table 2.9.1 and Table 2.12","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Total expenditure has been reconciled to the 2014/15 Annual RIN (excluding amount reported as Network Overheads in table 2.10.1) and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.2","Row 43 - Non-network","Financial","Table 2.6.1 and Table 2.12 ","Estimated","Table 2.6.1 contains an estimate of some costs that apply to Standard Control Services.  These costs are replicated in other tables (e.g. vehicle costs) and can not be readily reconciled to the Annual RIN.","Total expenditure represents the Standard Control Services portion of the Opex rows of Table 2.6.1 and represents a portion of the total Non-Network category input costs in table 2.12."]
[null,"2.1.2 and 2.1.4","Rows 44 and 85 - Network overheads","Financial","Table 2.10.1 and Table 2.12 ","Actual",null,"Total network overheads have been reconciled to the 2014/15 Annual RIN and represent a portion of the the total Network Overhead category inputs in table 2.12."]
[null,"2.1.2 and 2.1.4","Rows 45 and 86 - Corporate overheads","Financial","Table 2.10.2 and Table 2.12 ","Actual",null,"Total expenditure has been reconciled to the 2014/15 Annual RIN and represent a portion of the the total Corporate Overhead category inputs in table 2.12."]
[null,"2.1.3 and 2.1.4","Rows 63 and 84 - Connections","Financial","Not applicable to SA Power Networks","Actual",null,"Capex and opex associated with Alternative Control Services Connections has been reported under the Metering category in tables 2.1.3 and 2.1.4.  SA Power Networks has no other Alternative Control Services aside from Metering."]
[null,"2.1.3 and 2.1.4","Rows 66 and 87 - Metering","Financial","Table 4.2.2 and Table 2.12","Estimated","Table 4.2.2 includes some Negotiated Distribution costs in line with RIN requirements and therefore does not reconcile to the Annual RINs.","Total expenditure has been reconciled to table 4.2.2 and the total inputs in table 2.12.",null,"Adjustment to the Annual RIN total has been made for the separation of direct operational support costs and business overheads reported in Network Overheads in line with RIN definitions."]
[null,"2.1.3 and 2.1.4","Rows 68 and 89 - Fee and quoted","Financial","Not applicable to SA Power Networks","Actual",null,"In accordance with our current classification of services, all of SA Power Networks' fee and quoted workas are classified as Negotiated Distribution Services.  Hence Alternative Control Services values are nil."]
[null,"2.1.4","Row 90 - Non-network","Financial","Table 2.6.1 and Table 2.12 ","Estimated","Table 2.6.1 contains an estimate of costs that apply to Alternative Control Services.  These costs are replicated in other tables (e.g. vehicle costs) and can not be readily reconciled to the Annual RIN.","Total expenditure represents the Alternative Control Services portion of the Opex rows of Table 2.6.1 and represents a portion of the total Non-Network category input costs in table 2.12."]
[null,"2.1.1 to 2.1.4","Rows 31, 55, 76 and 97 - balancing item","Financial","2014/15 AER Annual RIN","Estimated","Reconciling lines to agree to the 2014/15 Annual RIN that includes amounts reported as Negotiated Distribution costs and reconciling differences.  ","As per the requirements of the RIN, SA Power Networks has provided the AER with a summary showing a reconciliation between Annual RIN and Category Analysis RIN values.  This reconciliation shows the calculations for reconciling items reported in the balancing item lines of Tables 2.1.1 to 2.1.4."]
[null,"2.1.1","Row 33 - capcons","Financial","2014/15 AER Annual RIN","Actual",null,"Total Standard Control Services Capital contributions reported in the 2014/15 Annual RIN."]
[null,"2.1.5 and 2.1.6","Rows 105-118, 120 and 127-140","Financial","Not applicable to SA Power Networks","Actual",null,"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 and 2.1.6 are nil."]

{"sheet":"2.2 Repex","index":1,"n_rows":51,"n_cols":10,"rows_kept":51,"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.1000000000000001,4,5,6,8,9,10,11]
[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","\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.2000000000000002,"\nGeneral Assumptions(Non-financial)\n(Applies to the whole Repex 2.2 Tab)","Non-financial","SAP","Estimated","More than half of the data for 2.2 were obtained through SAP, and in general, we only have \nComplete information of:\n- Date of completion \n\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)\n\nNo information of:\n- Financial Year\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)\n","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 = 60m per span (route) = 240m\n - DD – 11kv = 90m per span (route) = 270m\n - DD – 33kv = 175m per span (route) = 525m\n - DD – SWER = 120m per span (route) = 120m\n - DD – 66kv = 150m per span (route) = 450m\n\n- Length of underground conductor (replaced)\n - HV Cable = 10m\n - LV Cable = 10m\n\n- Wherever the key information is missing e.g. unknown feeder, then the ratio of knowns would be calculated and apply to these unknown ones\n\n- It's been discovered that from time to time, some job could be closed in the current financial year but with cost incurred prior to the current financial year. We decided not to count such jobs in failure/replacement/cost unless there's non-zero cost incurred in the current period\n- For a job that we don't count, if there's a follow up job attached to it, the follow up job will NOT be counted as well","In general,\n- For Replacement consider DD+FM\n- For Replacement exclude all items completed on all Major Event Days\n- For Failure only consider FM\n- For DD \n     - Do not count DERR (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 (For everything)\n- From this RIN, we will not generate separate file for failures, instead, we will use number of replacement as it is normally a very good estimation of number of failure\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\n\n"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOTHER\nROWS: \n˂ ≈ 11 kV ; STOBIE Pole\n> 11 kV & <≈ 33 kV ; STOBIE Pole\n> 33 kV & <≈ 66 kV ; STOBIE Pole\n\nCOLUMNS: \nASSET REPLACEMENTS\nASSET FAILURES ","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 from (01.07-2014-30.06.2015)\n\nVoltage: we have separate spreadsheet for voltage we assume the voltage of the feeders, and applied it the Notifications (DD+FM) for Poles.\n","We have combined LV, 7.6kV and 11kV poles into a single category < = 11KV; STOBIE. The reason being we are unable to have them separated in 5.2 Age Profile, in order to keep the consistency we will keep 2.2 the same\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\nFor these that Feeder IDs are missing, we then calculate the voltage ratio of known items apply to these unknown ones","We used the following categories:\n< = 11 KV; STOBIE; \n˃ 11 KV & < = 33 KV; STOBIE; \n> 33 KV & < = 66 KV; STOBIE;\n\ninstead of \n< = 11 KV; STOBIE; \n˃ 11 KV & < = 22 KV; STOBIE; \n> 22 KV & < = 66 KV; STOBIE;\n\nin order to keep consistency with Tab 5.2"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.2 DESCRIPTOR METRICS\nPOLES\nROWS: \nTotal Poles By:\nTOTAL CBD POLES \nTOTAL URBAN POLES \nTOTAL RURAL LONG POLES \nTOTAL RURAL SHORT POLES \n\nCOLUMNS: \nASSET VOLUMES CURRENTLY IN COMMISSION\nASSET REPLACEMENTS ","Non-financial","SAP + Circuit_length.xlsx, Sheet1 (Reg.Reset Team)","Estimated","For Asset Replacement, the 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, number of poles or spans not recorded.  Estimation had to be made and is based on the Economic Benchmarking RIN","For Pole Replacement DD+FM catalogue codes for poles were extracted from SAP on the completion date from (01.07-2014-30.06.2015)\n\nThe poles volumes were calculated based on the length of the network by calculating the circuit length based on the lowest voltage conductor (only in cases they are two feeders on a pole) by using complex  GIS Queries\n\n","For Asset Replacement:\nAssume data required is based on Financial Years\n\nIn SAP Extraction for these with known Feeder IDs, we assume the feeder type of Pole is the same as the feeder type of the feeder. \n\nFor these that Feeder IDs are missing, we then calculate the feeder type ratio of known items apply to these unknown ones","For Asset Volumes currently in commission:\n\nEstimation/assumption is made Based on route length and average span length per base voltage level.  Based on average span length per base voltage level.  (NB Estimate by SCONNR region pro-rated by conductors)"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOTHER\nROWS: \nPole Refurbished; STOBIE\n\nCOLUMNS: \nASSET REPLACEMENTS","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 Notification.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  DD Catalogue codes EXCLUDING P4's(Pole Age Size) were extracted from SAP on the completion date from (01.07-2014-30.06.2015)\n","- 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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nPOLE TOP STRUCTURES\nROWS: \n˂ = 1 KV\n> 1 KV & < = 11 KV\n˃ 11 KV & < = 22 KV\n> 22 KV & < = 66 KV\n> 66 KV & < = 132 KV\n\nCOLUMNS: \nASSET REPLACEMENTS\nASSET FAILURES ","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 codes were extracted from SAP on the completion date from (01.07-2014-30.06.2015)\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)","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","Pole Top Structure consists of the following assets :\n\n- DF, Air break, LS, LSDF, Tie wire, earth, lugs, taps, joint, pot head \n- LFI (Line fault indicators)"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOVERHEAD CONDUCTORS\nROWS: \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\nCOLUMNS: \nASSET REPLACEMENTS (KMs)\nASSET FAILURES ","Non-financial","SAP + Project data - Conductor Replacement 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 codes were extracted from SAP + Project on the completion date from (01.07-2014-30.06.2015)","- Replacement is in unit of KMs\n\n- Consider all 19kV conductors as SWER conductors\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\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 = 60m per span (route) = 240m\n - DD – 11kv = 90m per span (route) = 270m\n - DD – 33kv = 175m per span (route) = 525m\n - DD – SWER = 120m per span (route) = 120m\n - DD – 66kv = 150m per span (route) = 450m\n"]
[null,"2.2.2","2.2 REPEX\n2.2.2 DESCRIPTOR METRICS\nOVERHEAD CONDUCTORS\nROWS: \nCONDUCTORS CBD (KM)\nCONDUCTORS URBAN (KM)\nCONDUCTORS RURAL LONG (KM)\nCONDUCTORS RURAL SHORT (KM)\n\nOH conductor LV ABC\nOH conductor steel\nOH conductor ACSR\nOH conductor AAAC\nOH conductor AAC\nOH conductor HDBC\n\nCOLUMNS: \nASSET VOLUMES CURRENTLY IN COMMISSION\nASSET REPLACEMENTS ","Non-financial","SAP + Project data - Conductor Replacement Log.xlsx (Operational Asset Management) +  SCONNR_Lengths.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 and 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 from (01.07-2014-30.06.2015)\n\nFor Asset Volumes currently in commission, data was collected based on historical snapshots collected from GIS.\n\nALL ASSET VOLUMES CURRENTLY IN COMMISSION ARE CONDUCTOR LENGTH.","For Asset Replacement:\nAssume data required is based on Financial Years\n\nIn SAP Extraction for these with known Feeder IDs, we assume the feeder type/material type of conductor is the same as of the feeder. For these that Feeder IDs are missing, we then calculate the feeder type/material type ratio of known items apply to these unknown ones\n\nThe asset volumes in commission by material type were populated by using the ration of the material for conductors for CBRM data and then applying that ratio to the Economic Benchmarking data. For the split of the overhead conductor volumes  by SCONRR region  (CBD, Urban, Rural short & Rural long) that was what was reported in the Economic Benchmarking RIN.CONDUCTOR LENGTH was used for these tab as to sychronize with the CONDUCTOR LENGTH in the 5.2 Age Profile Tab.\n\n","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 10m as it is regarded as part of the LV network."]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nUNDERGROUND CABLES\nROWS: \n˂ = 1 KV\n> 1 KV & < = 11 KV\n> 11 KV & < = 22 KV\n> 22 KV & < = 33 KV\n\nCOLUMNS: \nASSET REPLACEMENTS (KMs)\nASSET FAILURES  ","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 codes were extracted from SAP + Project on the completion date from (01.07.2014-30.06.2015)","- Replacement is in unit of KMs\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\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.2000000000000002,"2.2 REPEX\n2.2.2 DESCRIPTOR METRICS\nUNDERGROUND CABLES\nROWS: \nCONDUCTORS CBD (KM)\nCONDUCTORS URBAN (KM)\nCONDUCTORS RURAL LONG (KM)\nCONDUCTORS RURAL SHORT (KM)\n\nCOLUMNS: \nASSET VOLUMES CURRENTLY IN COMMISSION\nASSET REPLACEMENTS ","Non-financial","SAP + PROJ - Cable Retrench Log.xlsx (Operational Asset Management) +  SCONNR_Lengths.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 from (01.07-2014-30.06.2015)\n\nFor Asset Volumes currently in commission, data was collected based on historical snapshots collected from 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 these 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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nSERVICE LINES\nROWS: \n˂ = 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n˂ = 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE \n\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES  ","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 codes were extracted from SAP on the completion date from (01.07-2014-30.06.2015)","- Since only 0.025% service lines are HV lines, all service lines are assumed as LV lines\n- 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 89% of total and Commercial service lines are 11% 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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nTRANSFORMERS BY: MOUNTING TYPE; HIGHEST OPERATING VOLTAGE ; AMPERE RATING; NUMBER OF PHASES (AT LV)\nOther\n\nROWS:\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\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES  ","Non-financial","SAP +HV DataBase (Reliability Group)","Estimated","The information we have from SAP doesn’t state the Ampere Rating of the Transformer at all and the number of phases, In CAT RIN the AER wants the transformers by Highest Operating Volatge,Ampere Rating and Number of phases.\n\nFrom the HV Database Reliability Group we have the operating voltage,Ampere rating and number of phases .Then we applied the ratio from the HV database to the SAP information.\n","All codes were extracted from SAP + HV Database on the completion date from (01.07-2014-30.06.2015)\n\nFor Asset Failure we have used the HV database Reliability Group which records a log of failure due to which a outage has occurred,HV database contains good quality of information.","The assumptions that were used in HV data base Reliability Group which were used in both Failure and Replacement :\n- assume all unassigned 33kV TF 3ph\n- Exclude TF earthing issue – TF not replaced due to this reason \n- For all data in HV Data Base, they are all for TF whole unit replacement\n- For all data in HV Data Base, assume the replacement will be done immediately after the failure (otherwise customer will be without power supply)\n\nThe assumptions that were used in SAP Pole TF(DD) that were used for Replacement:\n-We applied the Capacity and Number of Phase ratio from the HV database Reliability Group and applied it to the SAP data\n","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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nTRANSFORMERS BY: MOUNTING TYPE; HIGHEST OPERATING VOLTAGE ; AMPERE RATING; NUMBER OF PHASES (AT LV)\nOther\n\nROWS:\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 ;  > 60 KVA AND < = 600 KVA \nKIOSK MOUNTED ; > 22 KV ;  > 600 KVA\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\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES  ","Non-financial","SAP +HV DataBase + Operational Asset Management Ground level Switchgear Replacement Spreadsheet+ Operational Asset Management Ground level Switchgear failure spreadsheet","Estimated","The information we have from SAP doesn’t state the Ampere Rating of the Transformer at all and the number of phases, In CAT RIN the AER wants the transformers by Highest Operating Volatge,Ampere Rating and Number of phases.\n\nFrom the HV Database Reliability Group we have the operating voltage,Ampere rating and number of phases .Then we applied the ratio from the HV database to the SAP DD.\n\nIn Operational Asset Management Ground level Switchgear replacement and failure spreadsheet we assumed all the PAD mount are three phase  and took the ampere rating from the Functional location they were installed in","All codes were extracted from SAP + HV Database on the completion date from (01.07-2014-30.06.2015)\n\nFrom Operational Asset Management Ground level Switchgear Replacement Spreadsheet we filtered on \"GL Pad Transformers\" for padmount TF and \"Elizabeth GL transformer Stn\" for Ground level TF.\nAsset Failure we use the HV database Reliability Group which records a log of failure due to which a outage has occurred,HV database contains good quality of information and Operational Asset Management Ground level Switchgear failure Spreadsheet","-All the transformers in the TC’s in HV database and Operational Asset Management Ground Level switchgear spreadsheet are PAD MOUNT TF’s.\n'- For Padmount failure, filter has been applied to “Type” in “Plant Failures Data Base Revision ”. Only “Transformer/Transformer Cubicles” are selected.\n'- Estimated replacement for a category in (Padmount) DD is worked out by ratio against (Padmount/GL) HV Database. E.g. (Number of replacement for this item in HV Database)/(Total replacement in HV Database)*(Total (Padmount) replacement in DD) = estimated (Padmount/GL)  replacement for this item in SAP DD\n","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.2000000000000002,"2.2 REPEX\n2.2.2 DESCRIPTOR METRICS\nTransformers by Total MVA \nTotal MVA Disposed \nTotal MVA Replaced \n\n","Non-financial","HV Data base, SAP, Operational Asset Management Ground level switchgear Replacement Spreadsheet+ Operational Asset Management Ground level switchgear failure spreadsheet, Substation group data","Estimated","For the transformers MVA Replaced and disposed for the lines - Pole Top TF,Pad Mount and  GL Transformers we always replace like for like MVA FOR MVA i.e. if we take out a 300KVA Transformer we always put a 300KVA transformer back in .","The Methodology used is as we know the KVA of the failed transformers from the HV database and the Capacity rating for the SAP DD Notification were unknown so we took the ratio for the line transformers from the HV database and applied it to the DD Notifications","The assumptions that were used for populating this information was that for lines we assume that we always replace like for like transformer and applied the capacity rating from the HV database to the DD Notifications ","We have combined the line transformers MVA and the substation transformers MVA in the 2.2 RIN for Total MVA disposed and replaced "]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOTHER\n\nROWS:\n>= 11 kV & < ≈ 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical)\n> 22 kV & < ≈ 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical)\n\n\n\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES  ","Non-financial","Operational Asset Management Groundlevel switchgear Replacement Spreadsheet + Operational Asset Management Groundlevel switchgear Failure Spreadsheet\n\nSAP DD","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 spreadsheet .(01.07-2014-30.06.2015)\n\n","For Replacement of switching cubicle and GL switches in TC just going by Operational Asset Management Ground level switchgear Replacement spreadsheet.\n\nFor failure of switching cubicle and GL switches in TC just going by Operational Asset Management Ground level switchgear Failure spreadsheet.\n\nAs some replacments were don’t on Noti so all the LMC007 coding code from SAP was extratced for the last financial year(14/15) and were filtered through manually","‘- In Operational Asset Management Ground level switchgear failure and replacement spreadsheet, filter “GL Switch” for Switches and \"C\" for Switching Cubicle\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.\n-The LBS also consists of switching cubicle and we replace the whole cubicle not the switches inside it.\n- For LBS switches, most replacements are of 11kV except few of 7.6kV, we assume they are all 11kV and put them under the same line\n- For LBS switches, most failures are of 11kV except few of 7.6kV, we assume they are all 11kV and put them under the same line\n- For LBS failure, filter has been applied to “Type” in “Plant Failures Data Base Revision C.xlsm”. Only “Switching Cubicles” are selected.\n","Doug Lorimer is the SME for Switching Cubicles and TC's He maintains his own database of all the failure from (FM's) and Replacement (Fm's +DD+Projects) So we have used his database for Ground level switch gear to fill this Row of CAT RIN.\n\nWe have used SAP codes LMC-007 AND filtered through them manually to find the extra units replaced.Assume Doug Lormier replacement spreadsheet and LMC007 manually cleaned spreadsheet covers all the replacement volumes associated with Switching Cubicals."]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOther\n\nROWS:\nRecloser ;SWITCHGEAR\n\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES  ","Non-financial","SAP","Estimated","As there is no Recloser category in the final CAT RIN so we had to insert a separate category for Recloser separately.\n","All codes were extracted from SAP on the completion date from (01.07-2014-30.06.2015)","Count Recloser Controller, Recloser all as-Recloser","The reported Reclosers quantities include distribution lines + substation"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOther\n\nROWS:\nSectionalizer ;SWITCHGEAR\n\nCOLUMNS: \nASSET REPLACEMENTS \nASSET FAILURES \n","Non-financial","SAP","Estimated","As there is no Sectionaliser category in the final CAT RIN so we had to insert a separate category for  Sectionaliser  separately.","All codes were extracted from SAP on the completion date from (01.07-2014-30.06.2015)"]
[null,2.2000000000000002,"2.2 REPEX\nGeneral information for all cost data (exclude items outlined In Cells below)\nIs applicable for Stobie Poles, Pole top structure, Overhead Conductor,Underground Cable,Recloser and Sectionaliser","financial","SAP","Estimated","All cost data are dependent on replacement and failure data we collected in the above Non-financial steps, which means, all effects of assumption/estimation we've made before will affect the cost, which means 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 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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOTHER\nROWS: \nPole REFURBISHED; STOBIE Pole\n\nCOLUMNS: \nEXPENDITURE ($000'S) 2014-2015","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 Notification.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.","- Disregards all order numbers on the spreadsheet, FS staff normally only use 1 order number for all jobs for one Calendar Year, therefore if we are working on a Financial Year there should be 2 order numbers"]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nSERVICE LINES\nROWS: \n˂ = 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n˂ = 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE \n\nCOLUMNS: \nEXPENDITURE ($000'S) 2014-2015","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","- Previously from the total population, we assume the Residential service lines are 89% of total and Commercial service lines are 11% of total, this ratio is applied to all recorded items\n- Total cost has therefore been split into 89% and 11 % into Simple type and Complex type"]
[null,2.2000000000000002,".2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nOTHER\n\nROWS:\n>= 11 kV & < ≈ 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical)\n> 22 kV & < ≈ 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical)\n\n\n\nCOLUMNS: \nEXPENDITURE-2014-2015","financial","SAP + BEX Reports","Estimated","For the Switching Cubical we got the number of Replacements from Doug Lorimer's spreadsheet and matched it up against the L35,L55 and L66 Bex financial reports to get the cost.\n\nAs the Gas refilling , repairs and some replacmeent jobs are booked under SAP code LMC007 so had to extratct that from SAP .The LMC007 code represents BU-CMT-000070 and BU-CMT-000078 under activity type L35 so had to count the expenditure seperately.","The Project (NW and DD numbers were from Doug Lorimers switching cubical replacement spreadsheet were looked up against finical BeX reports for the expenditure.\nThe LMC007code represents BU-CMT-000070 and BU-CMT-000078 under activity type L35 so had to count the expenditure seperately.\n","Assume Doug Lorimers spreadsheet projects +BU-CMT-000070 and BU-CMT-000078 covers all expenditure associated with switching cubicals."]
[null,2.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nTRANSFORMERS BY: MOUNTING TYPE; HIGHEST OPERATING VOLTAGE ; AMPERE RATING; NUMBER OF PHASES (AT LV)\n\nROWS:\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\nCOLUMNS: \nEXPENDITURE ($000'S) 2014-2015","financial","SAP +HV DataBase (Reliability Group)","Estimated","For replacement data, we have used SAP (DD) data and HV Database. However, for the cost we don't have any work order number for HV Database, and we don't have any capacity information for SAP (DD), therefore we have to make some estimation","We decided to use SAP (DD/ER/AR) data to get the overall total cost,  then work out the cost for each category, as below:\n\n- Pole Top TF: \n      - For HV Database (HD) Data\n  Cost(ER+AR)/Total No. of HD Replacement* No. of HD Replacement per category\n       - For DD\n  Cost(DD)/Total No. of DD Replacement*No. of DD Replacement per category\n","- Assume SAP (DD+ER+AR) covers all cost\n- Assume every replaced TF (under the same category) has same average overall cost (e.g. same cost for labour, material etc)","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.2000000000000002,"2.2 REPEX\n2.2.1 - COST METRICS BY ASSET CATEGORY\nTRANSFORMERS BY: MOUNTING TYPE; HIGHEST OPERATING VOLTAGE ; AMPERE RATING; NUMBER OF PHASES (AT LV)\n\nROWS:\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 ;  > 60 KVA AND < = 600 KVA \nKIOSK MOUNTED ; > 22 KV ;  > 600 KVA\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\nCOLUMNS: \nEXPENDITURE ($000'S) 2014-2015","financial","SAP +HV DataBase + Operational Asset Management Groundlevel Switchgear  Replacement Spreadsheet+ Operational Asset Management Groundlevel Switchgear failure spreadsheet","Estimated","For replacement data, we have used SAP (DD) data, HV Database, and  Operational Asset management ground level switchgear spreadsheet. However, for the cost we don't have any work order number for HV Database, and we don't have any capacity information for SAP (DD), and we don't have all cost data from Finance group for Operational Asset management ground level switchgear spreadsheet, therefore we have to make some estimation","For HV Database and SAP (DD) part, we decided to use SAP (DD/ER/AR) data to get the overall total cost,  then work out the cost for each category, as below:\n\n- Padmount/GL TF: \n      - For HV Database (HD) Data\n  Cost(ER+AR)/Total No. of HD Replacement* No. of HD Replacement per category\n      - For DD\n  Cost(DD)/Total No. of DD Replacement*No. of DD Replacement per category\n - For Operational Asset management\n  Cost(Operational Asset Management ground level switch gear actual data)\n\nFor Operational Asset Management Groundlevel Switchgear Replacement Spreadsheet, wherever finance team unable to provide the cost, we:\n- used actual cost from spreadsheet\n- only consider 65% of the actual cost as Direct Cost\n- used the existing ratio (for labour, material etc) from the known breakdown cost","- Assume SAP (DD+ER+AR)  and Operational Asset Management Groundlevel switchgear spreadsheet cover all cost\n- Assume every replaced TF(under the same category)  has same average overall cost (e.g. same cost for labour, material etc)","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","Transformer  Group, All Categories, Asset Replacements and Asset Failures Columns","Non-financial","No single database or asset register currently exists in SA Power Networks that captures all required RIN information.\nInformation was assembled from the following sources:\n-SAP asset movement records;\n-Failure investigation reports;\n-SAP FM & SD Notis\n-Annual asset replacement projects (NW projects captured in SAP); and\n-Primary plant contract running sheets.","Estimated",null,"The data sources were cross-referenced to build a consolidated list containing:\n-The asset that failed;\n-A reason for replacement (e.g. failed, condition replacement, asset refurbishment);\n-When the asset failed (at least by month and financial year);\n-What unit was installed as a replacement;\n-When the replacement was installed (at least by month and financial year);\n-Relevant NW project or Noti numbers for replacement/refurbishment  expenditure; and\n-Allocation of NW/Noti numbers to their respective RIN category (categorised by asset installed).","-'Redundant' or 'Disposed Of' assets have been excluded from report.\n- Only asset replacements have been included in report (i.e. failures with in situ repairs are excluded).\n- Capitalised repairs/refurbishment expenditure is included by asset group in the DNSP Defined refurbishment categories by asset category.\n- Substation three phase ground level regulators are included, substation single phase pole mounted regulators are excluded.\n- Commissioning failures and replacements are excluded.\n- Where TFs are installed temporarily (for load management as part of asset replacement) replacement by the permanent TF was not captured as an additional replacement.\n- Replacement of Gladstone 11kV regulator was replaced to allow refurbishment – it has been reported as capital refurbishment repex.\n- Replacement volumes and categories are installed units (not units failed/replaced).\n- Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.","-Asset replacements incorporated in capacity or customer driven projects have not been reported.\n-Assets that failed but have not been replaced by 30/6/15 do not have a replacement in the report.\n-Asset Replacement figures include number & costs of installed assets (not necessarily equal to the number of units removed).\n-Replacement assets may appear in a different RIN category to the unit removed (different MVA rating).\n-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","Transformer  Group, Expenditure Columns","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, L36 & Opex) which provided the direct and component costs of asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- SAP BeX financial reports (containing project numbers and direct costs by financial year) were used to capture failure, replacement and refurbishment expenditure from the list of NW & Noti numbers by RIN category.\n- Project construction specs were used to determine the breakdown of coordinated replacement works within each asset group (either TF, CB, Switch, Protection categories) captured in the total project cost.\n- Component costs were removed from the project total cost to give the total estimated replacement cost of the TF.\n- Refurbishment expenditure has been allocated to the 'OTHER - Non Category Substation asset replacement/refurbishment' category.","- All replacement OPEX was assumed to be dedicated to primary asset replacement (either CB or TF, i.e. no coincident replacement of other asset categories).\n- Any \"other\" costs (civils, earthing etc) required as part of TF replacement (and not broken down into CB, switch, protection relay expenditures) are included in TF replacement category.\n- Replacement of Gladstone 11kV regulator was replaced to allow refurbishment – it has been reported with other refurbishment expenditure under 'OTHER - Non Category Substation asset replacement/refurbishment'\n- All expenditure is reported in the financial year incurred.","- To avoid possible cost duplication - capitalised Notis are excluded from OPEX replacement expenditure.\n- Replacement costs are reported in the financial year incurred and may relate to asset replacements outside of the reported financial year.\n- Residual/post installation expenditure for ABC & Yankalilla TF replacements relate to site tidy up and fencing works & are included with general civil works in 'OTHER - Non Category Substation asset replacement/refurbishment'"]
[null,"2.2.1","Switchgear Group, Circuit Breaker Categories, Asset Replacements and Asset Failures Columns","Non-financial","No single database or asset register currently exists in SA Power Networks that captures all required RIN information.\nInformation was assembled from the following sources:\n-SAP asset movement records;\n-Failure investigation reports;\n-SAP FM & SD Notis\n-Annual asset replacement projects (NW projects captured in SAP); and\n-Primary plant contract running sheets.","Estimated",null,"The data sources were cross-referenced to build a consolidated list containing:\n-The asset that failed;\n-A reason for replacement (e.g. failed, condition replacement, asset refurbishment);\n-When the asset failed (at least by month and financial year);\n-What unit was installed as a replacement;\n-When the replacement was installed (at least by month and financial year);\n-Relevant NW project or Noti numbers for replacement/refurbishment expenditure; and\n-Allocation of NW/Noti numbers to their respective RIN category (categorised by asset installed).","-'Redundant' or 'Disposed Of' assets have been excluded from report.\n- Only asset replacements have been included in report (i.e. failures & in situ repairs are excluded).\n- Commissioning failures and replacements are excluded.\n- Replacement volumes and categories are installed units (not units failed/replaced).\n- Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.\n- Circuit breakers installed as replacements for fuses, ganged interrupters or fault throwers (protection driven project) are reported under repex. CBs are considered as a modern equivalent protection device.\n- Switchboard CB carriage replacements were included as single failures &/or replacements.\n- A single CB or bus failure that necessitates replacement of a complete switchboard is considered a failure of all CBs in the switchboard (i.e. Pt Pirie 6.6kV swbd replacement).\n- Replacement numbers are assumed to equal the number of CBs in the replacement switchboard (e.g. Campbelltown: 9 failed, 13 replaced).","- Switchboard failures were excluded where the failure related to a VT, cables or terminations that did not result in a CB failure or replacement.\n- CB replacements as part of Hawker Siddeley Horizon replacement/refurbishment are excluded from replacement numbers/expenditure.\n- Hawker Siddeley Horizon 33kV CB replacements are counted as refurbishments when they occur as part of a planned manufacturer changeover program.\n- Horizon failures in service have been included in failure/replacement repex reporting.\n- Areva (Alstom) S1 CB replacements are included as condition replacements (S1 CBs have a known design deficiency which is being managed with the manufacturer as a changeover program upon a condition failure).\n- Asset replacements incorporated in capacity or customer driven projects have not been reported.\n- Assets that failed but have not been replaced by 30/6/15 do not have a replacement in the report.\n- Asset Replacement figures include number & costs of installed assets (not necessarily equal to the number of units removed).\n- 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 Group, Circuit Breaker Categories, Expenditure Columns","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, L36 & Opex) which provided the direct and component costs of each asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- SAP BeX financial reports (containing project numbers and direct costs by financial year) were used to capture failure and replacement expenditure from the list of NW & Noti numbers by RIN category.\n- Project construction specs were used to determine the breakdown of coordinated replacement works within each asset group (either TF, CB, Switch, Protection categories) captured in the total project cost.\n- Component costs were removed from the project total cost to give the total estimated replacement cost of the CB.\n- Refurbishment expenditure has been allocated to the 'OTHER - Non Category Substation asset replacement/refurbishment' category.","- All replacement OPEX was assumed to be dedicated to primary asset replacement (either CB or TF, i.e. no coincident replacement of other asset categories).\n-Any \"other\" costs (civils, earthing etc) required as part of CB replacement (and not broken down into CB, switch, protection relay expenditures) are included in CB replacement category.","- To avoid possible cost duplication - capitalised Notis are excluded from OPEX replacement expenditure.\n- Switchgear category contains all expenditure on CB and switch (disconnector/DF/LSDF/LS) replacements.\n- Capital expenditure relating to Pt Pirie Swbd failure/bypass installation has been included in the 'OTHER - Non Category Substation asset replacement/refurbishment' catgory.\n  - expenditure includes material purchases (cables/terms etc), capital improvements to the mobile swbd & civil works/replacement of sub infrastructure.\n- Expenditure on Angaston LS replacement related to protection relay capital purchases and have been included under 'Field Devices'.\n- Residual/post installation expenditure for TTG swbd replacement relates to site tidy up and fencing works & are included with other general civil works in 'OTHER - Non Category Substation asset replacement/refurbishment'"]
[null,"2.2.1","Switchgear Group, Switch Category, Asset Replacements and Asset Failures Columns","Non-financial","No single database or asset register currently exists in SA Power Networks that captures all required RIN information.\nInformation was assembled from the following sources:\n-SAP asset movement records;\n-Failure investigation reports;\n-SAP FM & SD Notis\n-Annual asset replacement projects (NW projects captured in SAP); and\n-Primary plant contract running sheets.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category."," The data sources were cross-referenced to build a consolidated list containing:\n- Assets that failed;\n- A reason for replacement (e.g. failed, condition replacement, asset refurbishment);\n- When the asset failed (at least by month and financial year);\n- What unit was installed as a replacement;\n- When the replacement was installed (at least by month and financial year);\n- Relevant NW project or Noti numbers for replacement/refurbishment expenditure; and\n- Allocation of NW/Noti numbers to their respective RIN category (categorised by asset installed).\n- When part of coordinated replacement works (i.e. replaced with CB or TF), disconnectors are considered to be replaced in the same financial year as the CB(s) or TF.","-'Redundant' or 'Disposed Of' assets have been excluded from report.\n- Only asset replacements have been included in report (i.e. failures & in situ repairs are excluded).\n- Capitalised repairs/refurbishment expenditure is included by asset group in the 'OTHER - Non Category Substation asset replacement/refurbishment' category\n- All expenditure is reported in the financial year incurred.\n- Commissioning failures and replacements are excluded.\n- Replacement volumes and categories are installed units (not units failed/replaced).\n- Date of replacement may be either: 1.Date of installation, 2. Date commissioned, or 3. Date unit placed into service.\n- Replacement/Failures have only been recorded based on 2014-15 (capital project) data.\n- Disconnector/switch failures are considered to be in-service mechanical/electrical failures and devices in poor condition & considered unsafe for live operation.","- Installation of new disconnectors with replacement of old CB/TF/Other not included in switch category (expenditure included as part of CB/TF/Other replacement)\n- Replacement volumes/expenditures reported incorporate capital upgrade projects only (OPEX failures/replacements not included in reporting).\n- Morphett Vale East has A5569 has had to be replaced twice (original AK Power disco failed, was replaced with a subsequent AK Power unit that failed in the same manner & was replaced with an AEM disco)."]
[null,"2.2.1","Switchgear Group, Switch Categories, Expenditure Columns","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54 & L36) which provided the direct and component costs of each asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- Project scopes were reviewed to determine the number of disconnectors and switches replaced in each project. \n- Unit cost of disconnector replacement formulated:\n-- Comparison of historical costs of CB replacement works with/without disconnector replacement.\n-- Unit cost for replacement determined from averaging the per unit difference between projects.\n-- To account for economies of scale, a decreasing unit cost was calculated based on the total number of disconnectors installed as part of the project.\n- Estimated disconnector replacement cost was converted to a percentage of the total project cost (as spent or estimated total) to provide proportional expenditure across the life of the replacement project.\n- The allocation of costs from each replacement project was summed by financial year and RIN switch category to give the total switch replacement expenditure for that financial year.","-Unit cost assumed to be the average marginal cost of disconnector replacement with a CB over the period (2008/09 to 2012/13).\n-Disconnector replacements assumed to have economies of scale based on the number of disconnectors replaced, as the required network isolation allows subsequent replacements.\n-Due to the relatively small capital cost difference relative to installation between 33kV and 66kV disconnectors, unit costs were assumed to be equal for 33kV and 66kV replacements.","-Installation of new disconnectors with replacement of old CB/TF/Other not included in switch category (expenditure included as part of CB/TF/Other replacement)\n- To avoid possible cost duplication - capitalised Notis are excluded from OPEX replacement expenditure.\n- Replacement costs are reported in the financial year incurred and may relate to asset replacements outside of the reported financial year."]
[null,"2.2.1","Protection Group, Field Devices Category, Asset Replacements and Asset Failures Columns","Non-financial","No single database or asset register exists in SA Power Networks which captures the required RIN information. As a result, this information was assembled from the following sources:\n-Information provided by Network Protection Team;\n-SAP FM & SD Notis\n-Annual asset replacement projects (NW projects captured in SAP).","Estimated","Protection device replacements are obtained from project scopes.\nReplacements are based on protection 'schemes' & not number of relays/devices replaced as a more consistent unit of work/equipment/cost.","-Number of replacements were determined from protection schemes replacements works embedded in CB/TF/Switch replacement projects.\n-Project scopes were reviewed to determine the number of protection schemes replaced.\n-Where a partial protection scheme was replaced, the reported total was rounded up to a whole number (e.g. 2.5 units were rounded to 3 units).","-A protection scheme (eg TF prot, CB prot, Bus etc) may include multiple relays & simple replacement works may consist of a fraction of a scheme.\n-All protection replacements incorporated into CB/TF/Switch replacement projects are reported as replacements (not failures).\n-Protection units were considered to have been replaced in the same financial year as the CB(s) or TF included in the project.","-Number of replacements included in the 'FIELD DEVICES' asset category.\n-This number represents the number of protection 'schemes' replaced."]
[null,"2.2.1","Protection Group, Field Devices Category, Expenditure Columns","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54 & L36) which provided the direct and component costs of each asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- Project scopes were reviewed to determine the number of protection schemes replaced.\n- The costs for embedded protection replacements were determined by the number of protection schemes multiplied by a representative scheme unit cost.\n- Unit cost of disconnector replacement formulated:\n-- Based on protection relay replacement expenditure over the period (2008/09 to 2014/15 supplied by network protection group), averaged to give a scheme replacement cost.\n- Estimated protection replacement cost (number schemes x unit cost) was converted to a percentage of the total project cost (as spent or estimated total) to provide proportional expenditure across the life of the replacement project.\n- The allocation of costs from each replacement project was summed by financial year and RIN switch category to give the total protection replacement expenditure for that financial year.","-Unit cost assumed to be the average protection scheme replacement cost over the period (2008/09 to 2014/15).\n-The average scheme replacement cost = $72,000 (ex O/H).","-Replacement expenditure included in the 'FIELD DEVICES' asset category"]
[null,"2.2.1","Other Group, Other - Non Category Substation asset replacement/refurbishment Category, Asset Replacements and Asset Failures Columns","Non-financial","Replacement volumes (where they occur in this categoty) are based on data sources contained in;\n- SAP asset movement records\n- Failure investigation reports\n- SAP FM & SD Notis\n- Network Operators Centre (NOC) log\n- Email history & archive\n- Annual asset replacement projects (NW projects captured in SAP L14, L54, L36 categories)\n- Annual budget forecast sheets (Finance)\n- Primary plant contract running sheets","Estimated","-The numbers of units failed and replaced are based on the sum of known and estimated quantities within this general category (noting that this category is intended to include all substation expenditure on asset replacement and refurbishment not allocated to switchgear, TFs, Protection & SCADA categories).","-Replacement and failure numbers reported in Table 2.2.1 include the ongoing substation asset replacement programs within these categories:\n- VT replacements (safety),\n- DC (battery bank and charger) replacements,\n- Surge arrester replacements\n- Capacitor can replacements\n- Unsafe Substation replacement/refurbishments.\n- TF and CB refurbishments","-Replacement of surge arrestors and DC systems for the 2014/15 period are an approximation based on 0.5*(projects completed in 2014 calendar year + projects to be completed in 2015 calendar year).\nThe following data was used:\nSurge Arrestors: 39 replacements\nBattery Banks: 24 replacements,\nChargers: 2 failures, 2 replacements\nCapacitor Cans: no replacements or failures\nInstrument TFs: 9 replacements, 3 failures\nUnsafe Substations: no replacements\nTF Refurbishments: 10 units (differing scope of works for each)\nCB Refurbishments: 30 units (includes 11kV refurbishments and 33kV Horizon replacements)","- This category includes a variety of replacement programs, capitalised refurbishment works across substation assets. It also includes a range of miscelaneous capital expenditure used to manage in service assets & 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- Failure numbers reported in Table 2.2.1 include ongoing asset replacement programs within this category but do not represent many small and 'one-off' expenditures included in this line item.\n- Ongoing capital replacement projects are managed by calendar year. Replacement numbers are an approximation based on 0.5*(projects completed in 2014 calendar year + projects to be completed in 2015 calendar year)."]
[null,"2.2.1","Other Group, Other - Non Category Substation asset replacement/refurbishment Category, Expenditure Columns","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, & L36) which provided the direct and component costs of each asset replacement project by financial year.","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.","-‘OTHER - Non Category Substation asset replacement/refurbishment’ costs are determined as the sum of:\n1. Safety based (SAP L36) asset replacement expenditure not allocated to TF/CB/Switch categories;\n2. Safety based (SAP L36) substation replacement expenditure (Nangwarry, Synagogue Pl & Birdwood rebuilds); and\n3. The total 2014-2015 substation capital expenditure under planned (L14) and unplanned (L54) replacement/refurbishment SAP budget categories, less all allocation to:\n- TF replacement\n- CB replacement\n- Switch replacement\n- Protection replacement\n- Dedicated SCADA (RTU/TDU) replacement.","- This category relies on information contained in the other categories of TFs, CBs, Disconnectors and Protection. These assumptions are inherited here.\n- Dedicated protection & SCADA replacement expenditure (i.e. not funded as part of CB, TF or Switch replacements) has been excluded from ‘OTHER - Non Category Substation asset replacement/refurbishment’ expenditure based on NW project numbers provided by Network SCADA and Network Protection groups.","- This category includes a variety of replacement programs, capitalised refurbishment works across substation assets (excluding CBs & TFs). i.e. poles, civil infrastructure. It also includes a range of miscelaneous capital expenditure used to manage in service assets & 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 expediture included in this category relates to replacement works.\n- Expenditure is reported in the financial year incurred and may relate to asset replacements outside of the reported financial year."]
[null,"2.2.2","Transformers","Non-financial","No single database or asset register currently exists in SA Power Networks that captures all required RIN information.\nInformation was assembled from the following sources:\n-SAP asset movement records;\n-Failure investigation reports;\n-SAP FM & SD Notis\n-Annual asset replacement projects (NW projects captured in SAP); and\n-Primary plant contract running sheets.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","-The ‘Total MVA Replaced’ is calculated as the sum of nameplate MVA capacity of TFs installed (replaced) in the period.\n'-The ‘Total MVA Disposed Of’ is the sum of nameplate MVA capacity of TFs removed in the period."]
[]
[null,2.2000000000000002,"Row 125, 127, 128  SCADA,Network control and protection systems - Communications Network Assets, Communications Site Infrastructure and Communications Linear Assets  Column D","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.","Data was extracted from SAP by finance departement using Telco category numbers","No assumptions, just collated data into the form required"]
[null,2.2000000000000002,"Row 125, 127, 128  SCADA,Network control and protection systems - Communications Network Assets, Communications Site Infrastructure and Communications Linear Assets  Column E and F","Non-financial","SAP","Estimated","Multiple installs of small equipment, complete count of number of assets installed can only be estimated in this timeframe","Estimated using the number of projects in each year and discussions with installers","Assumption that each project only replaces one piece of equipment per year for row 125 and 127, for row 128 discussed with installers","All communication linear asset section  lengths are reported in KM"]
[]
[null,2.2000000000000002,"Table 2.2.1 - \nReplacement Expenditure, volumes and asset failures by category:\n\nProtection Relays (Field Devices Category): Expenditure\n","Financial","Actual direct costs for protection asset replacement projects obtained from network finance (protection asset replacement projects only)\n\nUnit cost for the protection portion  transferred from primary asset replacements projects.","Estimated","When a primary asset (e.g. Circuit Breaker) is replaced the protection is generally also replaced for efficiency reasons. The costs for the protection portion are not separately tracked. An average cost of a protection upgrade (\"unit cost\") for each financial year has been calculated based on actual costs for protection asset replacement only projects. This allows an estimated protection asset replacement cost to be separated from primary asset repalcement projects.","For protection replacement projects, a list of project numbers (NW) for the Protection Asset Replacment budget line was obtained from financial tracking sheets. The direct costs for each project for the last financial year was then obtained.\n\nFor protection asset replacements that have taken place as a part of primary asset replacements (e.g. CB replacements), a unit cost for one protection asset replacement was derived for each financial year. This unit cost is then taken from each primary asset replacement project and added to the protection asset replacement line.\n\nUnit costs for a protection relay replacement have been calculated by dividing the sum of the protection asset replacement direct costs for each year by the number of assets replaced. Final unit costs have then been taken from a linear trend to remove any anomalies. \n\nThese replacements are for planned asset replacement projects only. Unplanned replacements (failures) are captured in maintenance/operational lines","Costs for each project entered into SAP are assumed to be accurate.\n\nWhen a primary asset is replaced (CB replacement), one protection scheme is also replaced.\n\nIt is recognised that all project costs are captured in the year of actual spend,  and the asset replacement quantity is captured in the year of majority spend and not neccesaarily the year of project completion.","Unit costs for protection asset replacements have been provided to the Substation Planning group, who then transfer protection asset replacement costs into this line from the respective primary asset replacement projects."]
[null,2.2000000000000002,"Table 2.2.1 - \nReplacement Expenditure, volumes and asset failures by category:\n\nProtection Relays (Field Devices Category): Asset Replacements\n","Non-financial","Deduction of number of assets replaced for each NW project, sourced from design drawings and project scopes","Estimated","To find actual date of asset installation requires significant effort for a likely minimal improvement in accuracy.","Definition of a one \"Protection Asset Replacement\" or \"scheme\":  A protection scheme is defined in section 4.3 of the current Protection and Control Asset Management Plan. The number of relays per standard scheme are as follows:\n\n1. Bus Protection - 2 relays\n2. Feeder Protection - 1 relay\n3. Transformer Protection - 2 relays\n4. Sub-Transmission Line Protection - 2 to 4 relays (A meshed line has total of 4 relays for 1 scheme.  Has 2 relays at each end of the line for meshed systems.)\n5. Other\n\nThese replacements are for planned asset replacement projects only. Unplanned replacements (failures) are captured in maintenance/operational lines.\n\nOne \"scheme\" is approximately equivalent to a \"unit\", as reported in the previous CAT RIN and therefore can be used interchangeably. The decision to change terminology was made to align with the Asset Management Plan and the \"unit' is no longer used.","Number of new assets shown on as constructed drawings have been actually installed\n\nIt is recognised that all project costs are captured in the year of actual spend,  and the asset replacement quantity is captured in the year of majority spend and not neccesaarily the year of project completion."]
[null,2.2000000000000002,"Table 2.2.1 - \nReplacement Expenditure, volumes and asset failures by category:\n\nProtection Relays (Field Devices Category): Asset Failures\n","Non-financial","Data not captured for all asset failures. Data provided is published failure rates from the Protection and Control 2009-2015 AMP","Estimated","Failure data has begun to be captured, but it is likely that some failures are not reported correctly. Measures to increase accuracy of failure data are underway for the 2014/15 year.","Data was obtained from Substation Defect Notifications as well as recorded failures when Protection and Control Planning are notified. When failures or out-of-tolerance relays are found as a part of planned maintenance, it is likely that many relays are replaced or adjusted as a part of that planned maintenance job and a separate notifcation is not raised. In addition, it is possible that emergency replacements organised from the operation centre are not always captured. \n\nThese failures are replaced under maintenance and do not correspond with the planned asset replacements.\n\nFailure numbers reported are individual relays rather than schemes.","\n"]
[]
[null,"2.2.1","SCADA - SCADA Assets (Other)","Financial","SAP and SCADA configurations","Estimated","N/A","Asset replacement project numbers are traceable and were extracted individually from SAP by the finance group to obtain actual financial data.","N/A"]
[null,"2.2.1","SCADA, - SCADA Assets (Other)","Non-financial","SCADA configurations file","Estimated",null,"Asset replacement project numbers are traceable and were extracted from a project register and SCADA configuration files.\n","N/A","N/A"]
[null,2.2000000000000002,"Network Finance  comment on consolidation and escalation of all financial figures within 2.2 and 2.12.","Financial","Samir/Bolei reports (BEX based) and Regulatory Accounts. Also Anna Roussis has provided the Safety adjustment offset figure with Augex.","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. However the split of Repex figures between the various AER categories has required various assumptions that require the figures to be classified as estimates.","The figures presented in both 2.2 and associated 2.12 for Repex tie to the Regulated accounts after two adjustments. The first difference is safety. The safety activity has been split between Repex and Augex on a project by project basis. See file: Safety - Reconciliation (AR).xlsx in the Finance folder.  As highlighted in the reconciliation, this has increased the Repex total reported and reduced the Augex figures (predominantly). The second adjustment is for Telecommunications Non Network Costs that has an offset in the Non Network Tab. The 2.2 figures are collated from Samir/Bolei in the methodology described above and were provided to Network Finance. This information is contained within the file: \"DNSP - CA RIN - template 2014-15 consolidated @ 20150910 3pm.xlsm\" saved within the working draft folder.  To this total, an adjustment was made for orders that did not relate to a specific asset being replaced. These orders were investigated and assigned directly to a reported category. Orders which did not relate to a specific category were apportioned on a % of costs of the orders which could be assigned to a specific category. Details of this calculation can be found in the file: 2.2 NW Finance Rec.xlsm found in the working draft folder. Lastly, adjustments have been made that include Project Support, a small corporate capital adjustment and an small misc variance. These costs have been spread over the gross amount (after the non asset specific costs adjustment) on a pro rata basis. "]

{"sheet":"2.3 Augex","index":2,"n_rows":56,"n_cols":10,"rows_kept":56,"cut":false,"hidden":false,"merged":[[10,8,10,9],[8,8,8,9],[4,8,4,9],[6,8,6,9],[7,8,7,9],[9,8,9,9]]}
[]
[null,1,1.1000000000000001,4,5,6,8,9,10,11]
[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","\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 Augex","2.3 Augex tab general comments","Financial","SAP\nBeX project financial reports","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.",null,"The information presented in the 2.3 Augex tab relates to network augmentation projects and expenditure only."]
[null,"2.3 Augex","2.3 Augex tab general comments","Financial","SAP\nBeX project financial reports","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.","All capital expenditure has been converted from SAPN Financial Year (Calendar Year) to a regulatory / financial year basis and converted to 2012/13 dollars where required. The information reported within this RIN, should reflect 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.","Assumptions are that the month and year for each transaction have been correctly identified."]
[null,"2.3 Augex","2.3 Augex tab general comments","Financial","N/A",null,null,null,"Gifted assets (clause 7.1(c)) and connection assets (clause 7.1(e)) have not been included in this RIN response. SA Power Networks did not engage in related party contracts for the period covered by this RIN."]
[null,"2.3 Augex","2.3 Augex tab general comments","Financial","N/A","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.",null,"Costs 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). "]
[null,"2.3 Augex","2.3 Augex tab general comments","Financial","N/A","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.",null,"Nominal 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 2012/13 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 2012/13 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 2012/13 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 Augex","2.3 Augex tab general comments","Financial","N/A","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.",null,"Clauses 7.2 - 7.4 of the RIN require asset volume data to be presented on a 'Project Close' basis."]
[null,"2.3 Augex","2.3 Augex tab general comments","Financial","N/A","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.",null,"Project 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.3.1 and 2.3.2","Rows 13 to 64 and rows 74 to 127 - projects above the threshold","Both","SAP,\nBeX project financial reports,\nAsset Records","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.","The following process was followed in order to complete tables 2.3.1 and 2.3.2 for Substation and Sub-transmission Projects exceeding the $5 million threshold.\nA list of capital projects finalised in the 2014 - 2015 period and exceeding $5 million threshold for substations and sub-transmission lines was compiled from historic capital budget's actual spend (refer Network Capital Performance Reports (2014 and 2015))."]
[null,null,null,null,null,null,null,"1.) For each material project identified, a SAP 'materials report' was run to extract the quantity and cost of the materials and equipment requested for Tables 2.3.1 and 2.3.2.  The materials report also provides the month and year of purchase. Materials extracted for each project include:\n• Transformers;\n• Switchgear;\n• Capacitors;\n• Poles;\n• Pole top structures;\n• Overhead conductors;\n• Underground cables;\n• Pole footings; and\n• Non-stock items."]
[null,null,null,null,null,null,null,"2.) A report providing a cost summary for each project within a given budget category, for each financial year in which costs were incurred was prepared using BEx (ie Business Objects).  This report detailed the cost allocations for each project by Work Breakdown Structure (WBS) allocated for the project in SAP.\n3) SA Power Networks developed an Excel model, to combine the output of the two reports (ie materials and BEx total expenditure breakdowns) and consolidated on a individual project basis.  The model enabled a project's annual costs to be analysed and formatted to the required RIN table format. SA Power Networks has reconciled the project costs to the annual capital budget tracking data.\n"]
[null,null,null,null,null,null,null,"4) Each project model include a ‘Materials’ tab, an expenditure tab for each year in the reporting period and a ‘Summary’ tab used for population of the relevant RIN table. \nData in the ‘Materials’ tab enables plant and materials costs to be identified and summarised to the requested RIN categories.  Most substation plant items are considered as ‘non stock’ items.  Stock items are not segregated by voltage (eg a pole used for sub-transmission purposes is not separately identifiable from an 11kV or LV pole).\nA ‘material code’ was allocated to each item required to be explicitly identified by the Augex tab.  The following ‘material codes’ were used:\ni) P - feeder poles (eg 11kV feeder poles);\nii) LP - line poles (sub-transmission);\niii) PT - pole tops (eg 11kV feeder pole tops);\niv) LPT - line pole tops (sub-transmission);\nv) FF - feeder footings;\nvi) SF - sub-transmission footings;\nvii) FCo - feeder conductor;\nviii) SCo - sub-transmission conductor;\nix) FC - feeder cable;\nx) SC - sub-transmission cables;\nxi) TF - transformers (substations);\nxii) SW - switchgear; and\nxiii) Cap - capacitors.\nNB: sub-transmission pole costs are the summation of items ’LP’, ‘LPT’ and ‘SF’ (ie poles, pole top structures and footings) and similarly for HV poles.\nA summary section at the top of the ’Materials’ tab calculates the quantities and costs of each material category according to the financial year in which the costs were incurred using Excel's ’SUMIFS‘ function.\n"]
[null,null,null,null,null,null,null,"5) Within each of the 'annual expenditure' tabs, the relevant portions of the BEx report related to the given project and financial year were extracted and copied to the relevant tab.  The WBS data contains a breakdown of activity costs by materials, labour (internal and external), contracts, vehicles and overheads.  The total cost of civil works activities may include all or none of these items and are identified at the WBS level.\nEach cost element within the BeX reports for the given project has been assigned a code indicating whether the relevant expenditure is attributable to either:\ni) Substations (S);\nii) Sub-transmission Lines (L);\niii) HV Feeders (F);\niv) LV Feeders (LV);\nv) Civil works (C); or\nvi) Land / Easements (Land).\nThe annual expenditure tabs contain a summary section at the top that identifies and calculates materials costs, labour hours and overheads from the BEx data extract.  Materials costs not required to be explicitly listed within the Augex tables are included in ‘Other Materials’. ’Other Plant’ is the difference between the total of the listed material costs and the total material costs.  ’Other Plant cover items such as protection systems, protection telecommunications, SCADA, bus structures, instrument transformers (ie CTs and VTs), AC and DC supplies etc.\nWBS labour elements associated with substation, sub-transmission line, feeder and civil construction were identified and summed to the associated category in the summary at the top of the tab.\n"]
[null,null,null,null,null,null,null,"The annual expenditure summarise data into the following elements :\ni) materials costs;\n Sub-transmission poles;\n Sub-transmission conductor;\n Sub-transmission cable;\n Transformers;\n Switchgear;\n Capacitors;\n Feeder poles; and\n Feeder cable.\nii) Other Plant costs (the difference between total annual material costs and listed material costs in i) above);\niii) substation, sub-transmission and feeder labour costs;\niv) civil costs;\nv) contracts;\nvi) land / easements; and\nvii) other direct(eg vehicles).\n"]
[null,null,null,null,null,null,null,"6) The 'Summary' tab consolidates and summarises annual expenditures (in nominal dollars) into the Category Analysis RIN's Table 2.3.1 and 2.3.2 as applicable.  Conversion to 2012/13 dollars and those required for reconciliation purposes by SA Power Networks with its historic internal capital budget's actual expenditure is a separate process."]
[null,"2.3.1 and 2.3.2","Columns AW, AX, AU and AV - land and easements","Financial",null,null,null,"Costs for all land and easements associated with substations above the threshold were identified and entered into columns AW and AX in table 2.3.1 while for line porjects, these costs were entered within columns AU & AV in table 2.3.2."]
[null,null,null,null,null,null,null,"Following reconciliation and conversion to 2012/13 dollars, the required values for a specific project are then entered in the Augex tab's respective substation, sub-transmission and HV feeder sections.  Where a project involved works at more than one substation (eg sub-transmission line projects), multiple substation line entries were created based upon further breakdown of the costs apportioned by the number of explicitly listed items required at each site.  SA Power Networks' existing WBS structures do not enable this breakdown to be explicitly determined and therefore some level of engineering judgement was required to be applied in determining this breakdown of costs.  This breakdown of the project's costs into overhead and underground components was based on the ratio of the overhead to underground material costs.\n"]
[null,"2.3.1 and 2.3.2","Rows 65 and 128 - non-material projects",null,"SAP\nBeX project financial reports","Estimated",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."]
[null,null,null,null,null,null,null,"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. 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.1","Substation normal cyclic rating pre and post augmentation","Non-financial","\tSubstation Load v Capacity spreadsheets from 2008 to 205 (inclusive)1;\r\n1Substation load vs capacity spreadsheets are used by SA Power Networks to compare annual load forecasts to substation equipment ratings. \n2Sub-transmission load vs capacity spreadsheets are used by SA Power Networks to store sub-transmission line details, ratings and forecast loads and are used for comparison of loads vs forecasts.\n",null,null,"Historic transformer rating spreadsheets (eg Substation load vs capacity) were used to determine alterations in normal cyclic capacity as a result of the relevant augmentation project.",null,"The \"Pre\" transformer rating has been left 0 (as per clause 7.2(k)) for new substations and for projects where no increase in transformer capacity was delivered."]
[null,"2.3.1","Definition of normal cyclic rating (for substations) and therrmal rating (for lines and cables).","Non-financial",null,"Actual","The AER has defined normal cyclic ratings as \"The maximum peak loading based on a given daily load cycle that a substation can supply each day of its life under normal conditions resulting in a normal rate of wear.\" SA Power Networks has applied this definition of normal cyclic rating consistently across all transformers in the SA Distribution network and these ratings have been used to complete the relevant sections in this RIN response (clause 7.1(b).  ","SA Power Networks' substation transformer normal cyclic ratings are based on (unity) ageing and calculated to be equivalent overall to sustained operation at the transformer's nameplate rated load and standard ambient conditions. Periods of time within a cycle at ageing rates greater than unity are compensated for by a period of time with ageing rate less than unity. These ratings are calculated in accordance with AS2374.7 using a commercially available package called “TLS”.\nSA Power Networks normal ratings are based on the use of an average daily load profile appropriate to the type of load being supplied by the zone substation transformers (eg residential, commercial, industrial etc), with varying PV penetration levels as well as average and high summer daily temperature curves.  TLS is set to determine the rating when any of the following limits are reached:\n• Maximum current = 1.5 p.u.\n• Maximum hot-spot temp = 130oC on a 44oC day\n• Maximum top-oil temp = 105oC\n• Average rate of life consumption = 1 p.u on a 31oC day.\n",null,"No definition of SA Power Networks' criteria for determining the \"thermal rating\" of its lines and cables is provided as no where within the Augex portion of the RIN does it request rating changes to be provided in relation to these assets."]
[null,"2.3.2","Sub-transmission line length metrics","Non-financial","Project specific line design pole schedules & SAP material reports","Actual",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.\n\nWithin the RIN is contained project NW-9244, Bolivar to Virginia 66kV Line Uprate.  This saw 14km of existing Copper conductor's design temperature increased from 50oC to 80oC through the installation of additional intermediate poles or the upgrading of existing poles."]
[null,"2.3.4","Table reconcilliation","Financial",null,"Estimated",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:"]
[null,null,null,null,null,null,null,"Relationship to Table 2.3.1: the sum of the Sub-transmission Substations et al row (table 2.3.4, cells M172 in the 2.3 Augex tab) is the sum of all direct and non-related third party contracts from all projects conducted during the 2014/15 financial year on a 'as-incurred' basis designated as \"Substation\" expenditure within the BeX reports for all augmentation expenditure categories of work (ie L09, L13, L33, L36, L38 & L39).  The data in Table 2.3.1 contains a subset of this data and is not directly relatable given the data in Table 2.3.1 is expressed on an 'as commissioned' or 'project close' basis. "]
[null,null,null,null,null,null,null,"Relationship to Table 2.3.2: the sum of the Sub-transmission Lines  (table 2.3.4, cells M173 in the 2.3 Augex tab) is the sum of all direct and non-related third party contracts from all projects conducted during the 2014/15 financial year on an 'as-incurred' basis designated as \"Line\" expenditure within the BeX reports for all augmentation expenditure categories of work (ie L09, L13, L33, L36, L38 & L39).  The data in Table 2.3.2 contains a subset of this data and is not directly relatable given the data in Table 2.3.2 is expressed on an 'as commissioned' or 'project close' basis. "]
[null,null,null,null,null,null,null,"Table 2.3.3.2: the sum of the HV Feeders row (table 2.3.4 (cells M174) in the 2.3 Augex tab) is the sum of all HV Feeder projects costs (cells M152:M154) in table 2.3.3.2.  The values in table 2.3.4 and table 2.3.3.2 are expressed in nominal terms."]
[null,null,null,null,null,null,null,"Table 2.3.4: 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."]
[null,null,null,null,null,null,null,"Table 2.3.3.2: 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."]
[null,null,null,null,null,null,null,"Table 2.3.4: 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."]
[null,null,null,null,null,null,null,"Table 2.3.3.2: 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."]
[null,null,null,null,null,null,null,"Table 2.3.4: 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."]
[null,"2.3.1 and 2.3.2","Project data",null,"Network Capital Performance Reports (2008 to 2013);\nSAP ;\nBEx reports (derived from SAP);\nSubstation Load v Capacity spreadsheets from 2008 to 2013 (inclusive) ;\nProject specific line design pole schedules & SAP material reports","Estimated","Some data has been estimated as there is either no equivalent or the costs have not been recorded in the divisions needed to complete the input cells required.  Where this has occurred, an explanation as to why actual information was not used, how the estimate was derived and why the estimate is the best estimate in the circumstance (clause 1.8) is provided here.","Project Ref: NW-11587\nProject Name: Morphettville to Glenelg North 66kV Line\nProject Type: New 66kV sub-transmission line\nProject Trigger: Capacity\nTotal Project Cost: $8.4 million\nYears of expenditure: 2011/12, 2012/13, 2013/14, 2014/15.\nRelated Project(s): -\nOperating Voltage: 66kV\nAugex Table References: 2.3.1, 2.3.2.\nProject synopsis: This project delivered a new 66kV cable, teed off the existing Morphettville to Plympton 66kV line to provide an alternate (ie second) 66kV supply to Glenelg North Zone Substation.  The project involved works within Glenelg North Substation's 66kV yard (eg 66kV CB and bus works) to facilitate connection of the new cable entry and remediate the existing 66kV yard which had suffered significant subsidance since its initial construction.\n"]
[null,null,null,null,null,null,null,"Project Ref: NW-9244\nProject Name: Bolivar to Virginia 66kV Line Uprate\nProject Type: Sub-transmission\nProject Trigger: Capacity\nTotal Project Cost: $5.2 million\nYears of expenditure: 2009/10, 2011/12, 2012/13, 2013/14, 2014/15\nRelated Project(s): -\nOperating Voltage: 66kV\nAugex Table References: 2.3.1, 2.3.2 \nProject synopsis: Thermally uprate the existing 66kV line between Bolivar and Virginia Zone Substations from its existing design temperature of 50oC to 80oC to increase the line's normal and emergency rating.  As the line represents the only source of supply to Virginia Zone Substation and required the total offload of the Zone Substation during the performance of the line works, works were also undertaken to construct a new 66kV line exit (ie 66kV disconnectors and CB) at Virginia to facilitate the connection of a new line to the proposed Two Wells Zone Substation planned for construction in 2015, thereby reducing costs associated with this future project."]
[null,null,null,null,null,null,null,"Project Ref: CP-13020\nProject Name: Smithfield West Sub Upgrade\nProject Type: New Substation Establishment\nProject Trigger: Capacity\nTotal Project Cost: $8.6 million\nYears of expenditure: 2011/12, 2012/13, 2013/14, 2014/15\nRelated Project(s): NW-12327, NW-12328\nOperating Voltage: 66/11kV\nAugex Table References: 2.3.1, 2.3.2\nProject synopsis: Convert former switching station site into a new zone substation consisting of a single 32MVA 66/11kV transformer, new 11kV switchboard, control building and associated protection to supply increased customer demand within the region.  Minor 66kV line works were required to take supply at 66kV from an existing line running adjacent to the site.\nThis project was driven by a customer load increase which saw the creation of this new zone substation.  \nAs the majority of this customer initiated project saw the augmentation of the shared network rather than the creation of the dedicated connection assets, this project has been reported within the Augex tab of the RIN."]
[null,null,null,null,null,null,null,"Project Ref: CP-13646\nProject Name: Kilburn South Sub Upgrade\nProject Type: Zone Substation Upgrade\nProject Trigger: Capacity\nTotal Project Cost: $7.9 million\nYears of expenditure: 2012/13, 2013/14, 2014/15\nRelated Project(s): -\nOperating Voltage: 66/11kV\nAugex Table References: 2.3.1\nProject synopsis: Upgrade existing transformer with a new 32MVA unit,11kV switchboard, 66kV line protection and associated 66kV switchgear.\nThis project was driven by a customer load increase which saw the upgrade of this zone substation.  \nAs the majority of this customer initiated project saw the augmentation of the shared network rather than the creation of the dedicated connection assets, this project has been reported within the Augex tab of the RIN."]
[null,null,null,null,null,null,"For those projects involving HV feeder works with a value in excess of $0.5 million, a separate template was created to reconcile the length of overhead conductor and underground cable associated with the project and the overall project costs.\n\nGiven the simplified nature of Table 2.3.3, the BEx reports were again used to assign project expenditure according to financial years while any costs incurred on a given project prior to the 2008/09 financial year were determined as the difference in the total cost contained in SAP and those costs contained within the BEx reports.","Project Ref: NW-10982\nProject Name: Evanston South 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $2.2 million / $1.8 million in 2014/15\nYears of expenditure: 2011/12, 2012/13, 2013/14, 20014/15.\nRelated Project(s): -\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder from Evanston Zone Substation to supply a new residential area.  The work involved construction of approximately 3.2km of overhead and underground works."]
[null,null,null,null,null,null,null,"Project Ref: NW-12327\nProject Name: Andrews Farm 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $0.5 million / $40k in 2014/15\nYears of expenditure: 2013/14, 20014/15.\nRelated Project(s): CP-13020\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder exit from Smithfield West Zone Substation to supply a new residential area.  The work involved construction of approximately 0.7km of underground works to integrate the new exit within the existing network."]
[null,null,null,null,null,null,null,"Project Ref: NW-12328\nProject Name: Smithfield Plains 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $0.5 million / $303k in 2014/15\nYears of expenditure: 2013/14, 20014/15.\nRelated Project(s): CP-13020\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder exit from Smithfield West Zone Substation to supply a new residential area.  The work involved construction of approximately 0.4km of underground works and 2.3km of overhead feeder works to upgrade and integrate the new exit within the existing network."]
[null,null,null,null,null,null,null,"Project Ref: NW-12917\nProject Name: Mawson Lakes North 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $0.59 million / $0.58 million in 2014/15\nYears of expenditure: 2013/14, 20014/15.\nRelated Project(s):\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder exit from Parafield Gardens Zone Substation to enable load to be transferred from the adjacent Cavan Zone Substation, thereby deferring the need for this substation's upgrade.  The work involved construction of approximately 0.5km of underground works and 2km of overhead feeder works to integrate the new feeder within the existing network."]
[null,null,null,null,null,null,null,"Project Ref: CP-13642\nProject Name: Liebherr Australia, Nelson Rd 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $1.2 million / $0.74 million in 2014/15\nYears of expenditure: 2012/13, 2013/14, 20014/15.\nRelated Project(s):\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder exit from Ingle Farm Zone Substation to enable a customer load increase.  Whilst triggered by a customer load increase, this work has been included within the augex analysis since it also saw augmentation of the shared network.  The works involved construction of approximately 0.6km of underground cable and 0.8km of overhead feeder works to integrate the new feeder within the existing network."]
[null,null,null,null,null,null,null,"Project Ref: NC-273\nProject Name: Murray Bridge North Meatworks 11kV Feeder\nProject Type: HV Feeder\nProject Trigger: Capacity\nTotal Project Cost: $0.7 million / $0.49 million in 2014/15\nYears of expenditure: 2013/14, 20014/15.\nRelated Project(s):\nOperating Voltage: 11kV\nAugex Table References: 2.3.3.\nProject synopsis: This project involved the creation of a new 11kV feeder exit from Murray Bridge North Zone Substation to enable a customer load increase.  Whilst triggered by a customer load increase, this work has been included within the augex analysis since it also saw augmentation of the shared network.  The works involved construction of approximately 0.1km of underground cable and 0.7km of overhead feeder works to integrate the new feeder within the existing network."]
[null,"2.3.4","Row 172 - Subtransmission Substations","Financial","BeX 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","Row 173 - Subtransmission Lines","Financial","BeX 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","Row 174 - HV Feeder projects","Financial","BeX 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 visually 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","Row 175 - HV Feeder Land and Easement Purchases","Financial","BeX 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","Row 176 - Distribution Substations","Financial","BeX 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","Row 177 - Distribution Substations Land","Financial","BeX reports L03, L09, L13, L33, L36, L38 and L39","Estimated","No data was identified for this category"]
[null,"2.3.4","Row 178 - LV Feeder augmentation","Financial","BeX 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 2014/15.  However the total reconciles to the BeX reports.","LV Feeder expenditure was calculated based upon the number of kms added or upgraded, multiplied by a unit cost in $2012/13 (adjusted for inflation over the period)"]
[null,"2.3.4","Row 179 - LV Feeder land and easements","Financial","BeX 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."]
[null,"2.3.4","Row 180 - Other Assets","Financial","BeX 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.  The costs contained within the Other Costs category relates to a short term strategic project aimed at improving network switching flexibility through the installation of HV switches at strategic locations across the network.  This expenditure is not expected to continue after the 2015/16 financial year and is therefore not a \"business as usual\" expenditure."]
[null,"2.3.4","Totals","Financial","BeX reports L02, L03, L09, L13, L33, L36, L38 and L39","Estimated",null,null,null,"The totals of these tables reconcile to the total augmentation expenditure incurred in 2014/15, they do not reconcile however to the summation of tables 2.3.1, 2.3.2 and 2.3.3.2 however.  The main reason is the difference in reporting methodologies across asset categories (ie some are reported on a \"project close\" basis, whilst other are on an \"as incurred\" basis)."]
[null,"2.3.4","Whole table","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. \nImmaterial reconciling differences have been apportioned to agree to the Annual RIN."]
[null,"2.3.1 & 2.3.2","Whole table","Financial","2.3.4","Estimated","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","After proportional application of project support costs, figures converted to reflect Real$ with reference to the June quarter ABS CPI for each of 2014 and 2015"]

{"sheet":"2.5 Connections","index":3,"n_rows":87,"n_cols":10,"rows_kept":87,"cut":false,"hidden":false,"merged":[[1,1,1,3]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,10,11]
[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","\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","Residential Underground Connections (0's) (D14)","Non-financial","SAP & CIS O/V","Actual",null,"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 Overhead Connections (0's) (D15)","Non-financial","SAP & CIS O/V","Actual",null,"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 Distribution Substations Installed (MVA added) (D16)","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 definitioin 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 Distribution Substations Installed (0's) (D17)","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 beeen made in the relavant 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 Distribution Substations Installed Total Spend ($0's) (D18)","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 Augmentation HV (Net KM Added) (D19)","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 Augmentation HV (Total Spend $0's) (D20)","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 Augmentation LV (Net Circuit KM Added) (D21)","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 Augmentation LV (Total Spend $0's) (D22)","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 Mean Days to Connect Residential Customer with LV Single Phase Connection (0's) (D23)","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 Volume of GSL Breaches for Residential Customers (0's) (D24)","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 Volume Customer Complaints Relating to Connection Services (0's) (D25)","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 timframe, application process and procedure only"]
[null,"2.5.1","Residential GSL Payment ($000's) (D26)","Financial","Manually gathered information","Estimated","Payment of this GSL payment is robust and auditable","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 Underground Connections (0's) (D27)","Non-financial","SAP & CIS O/V","Actual",null,"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 Overhead Connections (0's) (D28)","Non-financial","SAP & CIS O/V","Actual",null,"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 Distribution Substations Installed (MVA added) (D29)","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 definitioin 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 Distribution Substations Installed (0's) (D30)","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 beeen made in the relavant 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 Distribution Substations Installed Total Spend ($0's) (D31)","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 Augmentation HV (Net KM Added) (D32)","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 Augmentation HV (Total Spend $0's) (D33)","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 Augmentation LV (Net Circuit KM Added) (D34)","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 Augmentation LV (Total Spend $0's) (D35)","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 Underground Connections (0's) (D36)","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 Overhead Connections (0's) (D37)","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 Distribution Substations Installed (MVA added) (D38)","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 definitioin 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 Distribution Substations Installed (0's) (D39)","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 beeen made in the relavant 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 Distribution Substations Installed Total Spend ($0's) (D40)","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 Augmentation HV (Net KM Added) (D41)","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 Augmentation HV (Total Spend $000's) (D42)","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 Augmentation LV (Net Circuit KM Added) (D43)","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 Augmentation LV (Total Spend $0's) (D44)","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","Cost per Lot ($) (D45)","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 Underground Connections (0's) (DN46)","Non-financial","SAP","Estimated",null,"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 Overhead Connections (0's) (D47)","Non-financial","SAP","Estimated",null,"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 Distribution Substations Installed (MVA added) (D48)","Non-financial","SAP, interpretation of project name and project number","Actual","Project sub category is not documented. Subcategory has been interpreted using the project name and number. No substations were allocated to projects in this subcategory.","No distribution substations were recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly."]
[null,"2.5.1","Embedded Generation Distribution Substations Installed (0's) (D49)","Non-financial","SAP, interpretation of project name and project number","Actual","Project sub category is not documented. Subcategory has been interpreted using the project name and number. No substations were allocated to projects in this subcategory.","No distribution substations were recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly."]
[null,"2.5.1","Embedded Generation Distribution Substations Installed Total Spend ($0's) (D50)","Financial","SAP, interpretation of project name and project number","Actual","Project sub category is not documented. Subcategory has been interpreted using the project name and number. No substations were allocated to projects in this subcategory.","No distribution substations were recorded against projects in this sub-category.","Assumed that projects have been recorded in SAP correctly."]
[null,"2.5.1","Embedded Generation Augmentation HV (Net KM Added) (D51)","Non-financial","SAP","Actual","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.","No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required."]
[null,"2.5.1","Embedded Generation Augmentation HV (Total Spend $0's) (D52)","Financial","SAP","Actual","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.","No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required."]
[null,"2.5.1","Embedded Generation Augmentation LV (Net Circuit KM Added) (D53)","Non-financial","SAP","Actual","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.","No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required."]
[null,"2.5.1","Embedded Generation Augmentation LV (Total Spend $0's) (D54)","Financial","SAP","Actual","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.","No projects in this category required extensions to or augmentation of the network.","As no augmentation was required, no assumptions regarding costs are required."]
[]
[null,"2.5.2"," Residential Simple Connection LV ($0's) (H14)","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 simle 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 Complex Connection LV ($0's) (H15)","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 Complex Connections HV ($0's) (H16)","Financial","SAP","Actual",null,"There are no HV connections to residential premises within the SA Power Networks distribution system."]
[]
[null,"2.5.2","Commercial Simple Connections LV ($0's) (H17)","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 Complex Connection HV (Customer Connected at LV, Minor HV Works) ($0's) (H18)","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 Complex Connection HV (Customer Connected at LV, Upstream Asset Works) ($0's) (H19)","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 Complex Connection HV (Customer Connected at HV) ($0's) (H20)","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 Complex Connection Sub-Transmission ($0's) (H21)","Financial","SAP","Actual",null,"There was only 1 subtransmission connection for this year however there was expenditure on projects that will have a sub transmission connections in future years.","Future sub transmission connections were assumed from project data."]
[]
[null,"2.5.2","Subdivision Complex Connection LV ($0's) (H22)","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 Complex Connection HV (No Upstream Asset Works) ($0's) (H23)","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 Complex Connection HV (With Upstream Asset Works) ($0's) (H24)","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","Embedded Generation Simple Connections LV ($0's) (H25)","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 Complex Connections HV (small capacity) ($0's) (H26)","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","This list of projects from P Driver shows projects in this category.  Costs were extracted from SAP using project cost reporting.","This category generally contains projects of between 30kW and 200kW"]
[null,"2.5.2","Embedded Generation Complex Connection HV (Large Capacity) ($0's) (H27)","Financial","SAP, Project Cost Reports, BEX Analyser","Actual","The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require","This list of projects from V Ho shows projects in this category.  Costs were extracted from SAP using project cost reporting.","This category contains projects over 200kW"]
[]
[null,"2.5.2"," Residential Simple Connection LV (000's) (J14)","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 Complex Connection LV (000's) (J15)","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 Complex Connections HV (000's) (J16)","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 Simple Connections LV (000's) (J17)","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 Complex Connection HV (Customer Connected at LV, Minor HV Works) (000's) (J18)","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 Complex Connection HV (Customer Connected at LV, Upstream Asset Works) (000's) (J19)","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 Complex Connection HV (Customer Connected at HV) (000's) (J20)","Non-financial","SAP","Actual",null,"Interpret information from BEX Analyser to identify projects in this category.  There were 8 projects involving HV connections.","The projects where HV connections were required were assumed from the master list of projects for that year."]
[null,"2.5.2","Commercial Complex Connection Sub-Transmission (000's) (J21)","Non-financial","SAP","Actual",null,"Interpret information from BEX Analyser to identify projects in this category.  There was one project involving subtransmission connection."]
[]
[null,"2.5.2","Subdivision Complex Connection LV (000's) (J22)","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 Complex Connection HV (No Upstream Asset Works) (000's) (J23)","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 Complex Connection HV (With Upstream Asset Works) (000's) (J24)","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 Simple Connections LV (000's) (J25)","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 Complex Connection HV (Small Capacity) (000's) (J26)","Non-financial","SA Power Networks Master Embedded Generation List","Actual",null,"This list of projects from P Driver shows projects in this category.  Costs were extracted from SAP using project cost reporting.","This category generally contains projects of between 30kW and 200kW"]
[null,"2.5.2","Embedded Generation Complex Connection HV (Large Capacity) (000's) (J27)","Non-financial","SA Power Networks Master Embedded Generation List","Actual",null,"This list of projects from V Ho shows projects in this category.  Costs were extracted from SAP using project cost reporting.","This category contains projects over 200kW"]
[null,"2.5.2","Whole table","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. \nImmaterial reconciling differences have been apportioned to agree to the Annual RIN."]
[null,2.12,"Whole table","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. \nImmaterial reconciling differences have been apportioned to agree to the Annual RIN."]

{"sheet":"2.6 Non-Network","index":4,"n_rows":33,"n_cols":11,"rows_kept":33,"cut":false,"hidden":false,"merged":[[30,7,30,8],[31,7,31,8],[32,7,32,8],[22,7,22,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[28,7,28,8],[29,7,29,8],[21,7,21,8],[10,7,10,8],[11,7,11,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[15,7,15,8],[16,7,16,8],[17,7,17,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[9,7,9,8],[0,7,0,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[5,1,5,2],[5,7,5,8],[6,7,6,8],[7,7,7,8],[8,7,8,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,"IT & Communications"]
[null,"2.6.1","E14, E16 & E18\nIT OPEX","Financial","SAP / BW ","Estimated","Whilst the figures included as part of the submission are Actual, the client device expenditure has been estimated for OPEX. This is due to the account hierarchy changing over the period and the labour component of the client device expenditure not being able to be easily derived.","To derive the IT OPEX information the following methodology has been used.\n\n> Run Pctr Drilldown on each financial period using the Pctr Summary Drilldown Report – Profit Centre Hierarchy: Total Profit Centre Hierarchy, ETSA Activity Hierarchy: Blank, Account Hierarchy: 1000EU_P_L, Fiscal Year Variable: Varies depending on drilldown year, Posting Period: Varies depending on period i.e. 1- 6, 7 – 12\n> Once run change the profit centre to include all Information Technology Profit Centres for the period excluding FRC.\n> Next, Select the following Account Numbers to give you the OPEX Drilldown: Total Other Income,  Transferred Costs (Settlement), Internal Labour, Consultants and Contractors, Materials, Material On-Cost, Services, Transferred Costs, Capital Recovery\n> Remove Drilldown Profit Centre, Add Drilldown Account Number\n> The next step is to derive client device expenditure for OPEX. To do this two assumptions have been made, 1. All client device expenditure sits within Desktop, IT Infrastructure, IT Customer Services & Mobile Phone costsgroups 2. A percentage of each cost centre expenditure has been used to derive the percentage of costs attributable to client service devices.\n> The next step is to add in mobile device expenditure into client device expenditure, note IT only pays for IT's portion of mobile phone costs, the rest is re-allocated to the business.\n> Any non-recurrent expenditure must be split out, for the purposes of this exercise and expenditure under the Consultants & Recruitment GL have been considered non-recurrent expenditure plus an adjustment for the operational impact of capital work.\n> Now that both Client Device Expenditure & Non-Recurrent expenditure has been calculated the manual adjustments made to the accounts for each period must be received from the Regulatory Accountant. As these Manual Adjustments apply to the same criteria each period, the adjustment either +/- is to be applied to the recurrent expenditure field. Once applied, the recurrent expenditure is established.\n",null,"The percentage allocation of costs to Standard Control and Alternative Control Services is in accordance with the AER-approved Cost Allocation Method. \n\nThat the % of client device expenditure related to labour remained the same over the period of reporting.\n\nAll Non-Recurrent expenditure is captured in the correct GL accounts\n\nAll Non-IT Mobile Phone Expenditure is captured within business expenditure"]
[null,"2.6.1","E15, E17 & E19\nIT CAPEX","Financial","SAP / BW ","Estimated","SA Power Networks does not record or report costs on the specific categories requested. Assumptions were required to allocate costs as requested.","To derive the IT CAPEX information the following methodology has been used.\n\nFirst Run BW Query Order by GL Account Group\n> Profit Centre Hierarchy - Total Profit Centre\n> Profit Centre Authorisation - Information Technology (100000046)\n> ETSA Activity Hierarchy - 196\n> Period/Fiscal Year - Enter Fiscal Period relevant (i.e. 2013/14)\n> Once loaded all CAPEX data from Period/Fiscal Year will show\n> Each project needs to be categoried as either Client Device Expenditure, Recurrent Expenditure or Non-Recurrent Expenditure\n> Categorise those projects submitted as \"IT Projects\" via the capital submission to be \"Run\", anything related to Business / one off expenditure should be categorised as Non-Recurrent. From here, split out any projects deemed Client Device Expenditure as per the AER definition.\n> Once each project has been categorised the corporate overhead total must be split out. The IT Profit Centre Order Number drilldown allows you to add in only the business & PMO overhead excluding corporate overhead.\n> To establish what the total should be for CAPEX in each financial year, then run the Pctr Drilldown report.\n> Profit Centre = Information Technology, Fiscal Year = drilldown year, Period = Jan-Jun/Jul-Dec\n> Account Number should be Capital recovery, Transferred Costs, Labour Overhead Transfers. \n> The Sum of these drilldowns gives the total capital costs for the financial year\n> Once you have these totals then run a separate Pctr Drilldown, using the same parameters as above however changing the account number to Corporate Overheads.\n\n",null,"No Changes to overall profit centre hierarchy in the period"]
[null,null,null,null,null,null,null,"> To give you what should be the Reported regulatory numbers (excluding manual adjustments) you then subtract the total of the first Pctr drilldown (corporate recovery etc) from the total of the corporate overhead drilldown. (Total CAPEX for the period – Total Corporate Overheads for the period -/+ Manual Adjustments = Reported Regulatory Numbers for the period).from the total of the corporate overhead drilldown. (Total CAPEX for the period – Total Corporate Overheads for the period -/+ Manual Adjustments = Reported Regulatory Numbers for the period).\n> Note: As there were differences between the reported regulatory account manual adjustments must be made (refer to CAPEX Adjustments to reg numbers for full details).\n> To make these adjustments take the numbers calculated above for each financial year for client device, recurrent and non-recurrent expenditure.> Populate separate tabs with the Regulatory Numbers (Submitted and sent via Regulatory Accountant)\n> Work out what % of the Pre-Adjusted total (prior to removing/adding expenditure to = Reg Numbers) each category (client device etc) makes up of the financial year \n> Apply this same formula across each category.\n> Once this has been done all numbers should total the reported Reg Numbers (inc Manual Adjustments).",null,"The percentage allocation of costs to Standard Control and Alternative Control Services is in accordance with the AER-approved Cost Allocation Method. "]
[null,"Fleet"]
[null,"2.6.1","E20; E22; E24; E26; E28; E36; E38; E40","Financial","SG Fleet; SAP (IW38) & BW Reports","Estimated","Motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of proportion of fleet expenditure that applies to regulated services.","Full absorption costing applies to fleet operating costs such that they are charged out to operating and capital activities, plus the 2014/15 direct control % allocation to corporate groups. The split between the vehicle types is based on %'s derived from 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."]
[null,"2.6.1","E21; E23; E25; E27; E29; E37; E39; E41","Financial","SAP - BW Capital Order Report & Transaction (IE37)","Actual",null,"Fleet capex by order BW report generated for the 2014/15 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 then categorised"]
[null,"Property"]
[null,"2.6.1","E30","Financial","2014/15 AER RIN (Financial) Working Papers","Actual",null,"2014/15 RIN supporting workings: Operations & Maintenance Expenditure Analysis - Property"]
[null,"2.6.1","E31","Financial","2014/15 AER RIN (Financial) Working Papers","Actual",null,"2014/15 RIN supporting workings: Capital Expenditure Analysis - Property"]
[null,"Total Other"]
[null,"2.6.1","E32","Financial","Calculation","Estimated / Actual","Other motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of costs that apply to direct control services.\nTherefore this component of other operating expenditure has been reported as estimated. The remainder is included as Actuals.","Sum of Rows 34; 36; 38; 40; 42; 44; 46; 48; 50; 52"]
[null,"2.6.1","E33","Financial","Calculation","Actual",null,"Sum of Rows 35; 37; 39; 41; 43; 45; 47; 49; 51; 53"]
[null,"Non-Network Other"]
[null,"2.6.1","E34","Financial","SAP & Regulatory Working Papers","Actual",null,"Data generated from SAP for activity A80, which is a subset of Network Telephony"]
[null,"2.6.1","E43; E45; E47; E49","Financial","SAP","Actual",null,"Financial data based on individual non network strategic project actual expenditure for 2014/15 (data extracted from SAP)"]
[null,"2.6.1","E51","Financial","SAP","Actual",null,"Financial data based on individual Non Network Telecommunication projects actual expenditure for 2014/15 (data extracted from SAP) "]
[null,"2.6.1","E53","Financial","2014/15 AER RIN (Financial) - Capex","Actual",null,"2014/15 RIN supporting workings: Capital Expenditure Analysis - Plant & Tools and Non Network Other"]
[null,"IT - Non Financial"]
[null,"2.6.2","I14\nIT & Comms Employee Numbers","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).","Estimated","Refer Template 2.11.1.\nASLs are not dedicated to Standard Control.activities only. Assumptions are needed to derive ASLs by regulatory classification, as has been done in template 2.11.","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.\n"]
[null,"2.6.2","I15\nIT & Comms User Numbers","Non-financial","Active Directory","Estimated","The data for SA Power Network User Numbers is estimated as it cannot be easily derived from Active Directory. Active Directory provides a list of unique users that SA Power Networks has at any given point in time, what cannot be derived from this information is the split of these unique ID's into three distinct categories (Services, Internal FTE's & the length of time the employee was employed as SA Power Networks). This split is important when trying to scale the unique ID's (i.e. A minimum of x number of logins = 1 User), therefore a number of calculated estimations have been made to derive this data (explained in Methodology).","To derive SA Power Networks User Numbers the following methodology is used.\n\n> Request Server Technical Engineer to run user ID reports in Active Directory\n> From here, Server Technical Engineer will run a report with a number of parameters, these remove duplicates and filter the information into the format required (To see Formula, please view comment). \n>  Once run, the report is moved into Microsoft Excel.\n> Place the data into a pivot table, from here the data is filtered into the following categories: Those with 400 or more logins within the chosen period. The report is then re-run in 50 log in intervals reducing in value (350, 300) etc..\n> The user ID's are then required to be scaled. To do this, first calculate those Users with > 400 Log Ins for the period, these = 1 user number.\n> As the data is then run in 50 log in blocks i.e. 399 - 350, 349 - 300 etc. a % is then applied to scale these user log ins into a user number. As an example anyone with between 350-399 log ins would be considered .88 of a user (350/400), or between 300-349 log ins would be considered .75 of a user (300/400) etc.\n> From here, the number of users are scaled to remove any users considered to not be completing Standard Control Services work. The same % allocation applied to derive FTE numbers is followed.\n> The numbers of users are then collated and entered into the spreadsheet. \n",null,"> That all user ID duplications are removed.\n> 200 Working days was used as the base to calculate a full user, this is to remove unknowns such as annual leave, sick leave etc taken throughout the year which would reduce user numbers. \n> Assuming each user logs in and out each day","The reason FTE numbers were not used as a measuring base is that this could not be scaled for use. For example, an FTE does not necessarily mean they are 1 user, those working in the field may not log in at all but are considered as an FTE employee. Further, those employed by SA Power Networks as a Service are not included in FTE numbers but would have a userID an access SA Power Networks services."]
[null,"2.6.2","I16","Non-financial","VSM / Infra","Estimated","SA Power Networks does not currently have an Asset Management Tracking Tool that can be accurately relied upon. All data has been input Manually and therefore requires certain disciplines to ensure all salvaged/deleted & purchased items are captured. All data from Infra (previous asset tracking tool) was copied over to VSM (current asset tracking tool) in 2011, it is assumed all data was maintained during this transition.","To derive the Number of Devices currently within SA Power Networks the following methodology is used. Note, this is done in two stages.\n\n> First, request IT Product Officer to provide a report out of VSM detailing Current \"Active Assets\" as at the period you are looking for (i.e. 30 June 2014)\n> Remove all Assets not deemed to be Client Devices\n\n> Secondly, the number of active mobile phone devices is to be requested via the IT Commercial Manager (through Telstra).\n> The numbers provided are for mobile phone devices within the organisation that connect to the server. As the data has been sent in financial years an average over of the last two financial year is taken to get the average number of devices over that period. i.e. 2013/2014.\n> From here, the number of users are scaled to remove any users considered to not be completing Standard Control or Alternative Control Services work. The same % allocation applied to dervive FTE numbers is followed.\n> The numbers of users are then collated and entered into the spreadsheet. ",null,"> That all active assets are captured within VSM\n> That all \"salvaged\" items are removed from the active assets list.\n> That items are updated in VSM when salvaged or purchased\n> That Computer Screens should not be included in total Client Devices","Items included as Client Devices are:\n\n> Tablet PC's\n>Laptop\n> Desktop Computer\n> Toughbook\n> Ultrabook\n> Toughpad\n"]
[null,"Fleet - Non Financial"]
[null,"2.6.3","N14, N19, N24, N29, N34","Non-financial","SG Fleet Report","Estimated","Motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of the proportion of fleet expenditure that applies to regulated services.","Report by Fleet number 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 2014/15 regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.  "]
[null,"2.6.3","N15, N20, N25, N30, N35","Non-financial","SAP - BW Capital Order Report & Transaction (IE37)","Actual",null,"Fleet capex by order BW report generated by 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 then categorised. "]
[null,"2.6.3","N16, N21, N26, N31, N36","Non-financial","SG Fleet Report & Toyota Finance Records","Estimated","Motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of the proportion of fleet expenditure that applies to regulated services.","SG Fleet report by Fleet number which is then sort into respective categories. For earlier years, manual records from Toyota Finance utilised. Based on number leased at June. Categories have been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the 2014/15 regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.   "]
[null,"2.6.3","N17,N22, N27, N32, N37","Non-financial","SG Fleet Report","Estimated","Motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of the proportion of fleet expenditure that applies to regulated services.","SG Fleet report by Fleet number which is then sort into respective categories. Based on number as at June. Categories have been scaled back to Standard Control as follows:\n(i) Car & Light Commercial - based on the Corporate Standard Control % in the 2014/15 regulatory accounts;  \n(ii) EWP & Heavy Commercial - based on the Operating Standard Control % as per the Operating expenses.    "]
[null,"2.6.3","N18,N23, N28, N33, N38","Non-financial","SAP","Estimated","Motor vehicles are used for work across different regulated services (eg standard control, negotiated distribution etc) within any period. An estimate has therefore been made of the proportion of fleet expenditure that applies to regulated services.","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":24,"n_cols":11,"rows_kept":24,"cut":false,"hidden":false,"merged":[[23,7,23,8],[12,7,12,8],[13,7,13,8],[21,7,21,8],[10,7,10,8],[9,7,9,8],[22,7,22,8],[5,7,5,8],[8,7,8,8],[11,7,11,8],[20,7,20,8],[16,7,16,8],[17,7,17,8],[15,7,15,8],[19,7,19,8],[18,7,18,8],[6,7,6,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,2,4,5,6,7,8,null,9,10]
[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)",null,"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","\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.",null,"\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,null,null,"Non-financial",null,null,null,null,null,null,"The legislation determining vegetation clearance requirements in South Australia is the Electricity Act 1996 and the Electricity (Principles of Vegetation Clearance) Regulations. The legislation designates areas as bushfire and non-bushfire risk (with a subset defined as prescribed area which only includes the Adelaide Metro area) and this is one of the key factors that determines the required clearance zones. \n\nIn addition, internally SA Power Networks splits the bushfire risk areas into high and medium bushfire risk areas. An annual program is now in place for all bushfire risk areas. The legislation outlining vegetation clearance requirements in South Australia is more stringent than other states which impacts on clearance costs and clearance activities eg no provision for tree removals, defined clearance zones. Information provided is based on how SA Power Networks reports and collects data for bushfire and non bushfire risk areas.\n\nSA Power Networks vegetation clearance program consists of the following programs to manage vegetation near powerlines:\n• Annual cyclic program in bushfire risk areas (1,145 feeders in state) \n• Pre-fire danger season program in bushfire risk areas – repatrol all spans in high bushfire risk areas that were inspected as part of the annual cyclic program prior to 1 May in that year \n• 3 year cyclic program in non-bushfire risk areas except Metropolitan 33kV/66kV which are inspected and cleared annually due to their greater risk.\n• Metropolitan Council program – 3 year cyclic program (ie prescribed areas)\nWe have included the above explanation in the basis of preparation document.\n"]
[null,"2.7.3","All","Non-financial","Fire start data ","Estimated","SA Power Networks does not record all the data being requested by the AER in relation to unplanned events (ie fire starts) ","An estimate has been provided based on the information available. For the purposes of the data, all fire starts have been considered as SA Power Networks responsibility as data is not collected on the age of the tree, location (eg private property/ road verge) to determine responsibility.",null,"All fire starts have been considered as SA Power Networks responsibility as data is not collected on the age of the tree, location (eg private property/ road verge) to determine responsibility. "]
[null," Descriptor metrics by zone"]
[null,"2.7.1","Route line length within zone","Non-financial",null,"Estimated","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," "]
[null,"2.7.1","Number of maintenance spans","Non-financial","Vegetation clearance data ","Estimated","Estimate as number of poles or spans not recorded. ","Figures based on number of maintenance spans cut between July 2014 and June 2015. "]
[null,"2.7.1","Total length of maintenance spans","Non-financial","Vegetation clearance data ",null,"SA Power Networks does not record the length of maintenance spans. An estimate has been provided based on the number of maintenance span multiplied by the average length of maintenance span.","The number of trees cut in NBFRA and the number of spans cleared in BFRA were determined from contractor records.  It was assumed that there are two trees cut per span in NBFRA to determine the number of maintenance spans in NBFRAs.  The total number of maintenance spans were then prorated on the basis of the estimated total number powerline spans for each feeder category in designated BFRAs."]
[null,"2.7.1","km 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,null,"No data provided. ",null,"No data provided. "]
[null,"2.7.1","Average number of trees per span","Non-financial","Vegetation clearance contractor ","Estimated","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.5 trees per span in both bushfire and 3.3 in non-bushfire risk areas. The number of trees were then apportioned between CBD/Urban and rural.",null," The average number of trees has been estimated at 8.5 trees per span in both bushfire and 3.3 in non-bushfire risk areas. "]
[null,"2.7.1","Average frequency of cutting cycle ","Non-financial","Vegetation clearance program ","Actual",null,"Annual inspection in bushfire risk areas and a 3 year cycle in non-bushfire risk areas. The average cycle was then apportioned between CBD/Urban and rural."]
[null,"Cost metrics by zone"]
[null,"2.7.2","All","Financial","Work Order Data/SAP","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","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 eg scoping, cutting etc. In addition, an annual pre and post-summer audit is undertaken in the bushfire risk areas. No external audits were undertaken in the non-bushfire risk areas.  "]
[null,"2.7.2","Hazard tree cutting","Financial","N/A","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","SA Power Networks do not currently undertake hazard tree removal as there is no provision for tree removal is provided under the Act and Regulations. "]
[null,"2.7.2","Ground clearance","Financial","N/A","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","SA Power Networks do not currently undertake ground clearance activity ",null,"Reported as nil balance"]
[null,"2.7.2","Vegetation corridor clearance ","Financial","N/A","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","SA Power Networks do not currently undertake vegetation corridor clearance and the current legislation does not allow clearance beyond the buffer zone. ",null,"Reported as nil balance"]
[null,"2.7.2","Inspection ","Financial","Work Order Data/SAP","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","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 eg scoping, cutting etc. In addition, an annual pre and post-summer audit is undertaken in the bushfire risk areas. No external audits were undertaken in the non-bushfire risk areas.  "]
[null,"2.7.2","Audit (internal/ external costs)","Financial","Work Order Data/SAP","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","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 eg scoping, cutting etc. In addition, an annual pre and post-summer audit is undertaken in the bushfire risk areas. No external audits were undertaken in the non-bushfire risk areas.  ",null,null,"Copies of audits undertaken by GHD included as attachment. \n\nCosts for 2012 and 2013 includes both the pre and post fire danger season summer audit and the cyclic audit. Prior to 2012, the pre bushfire danger season was only undertaken and no post fire danger season or cyclic audits were undertaken."]
[null,"2.7.2","Contract liaison ","Financial","N/A","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","Contract negotiations are undertaken by a corporate group and are not separately recorded for specific contracts; costs have therefore reported as overhead. \n\nThe contract liaison and negotiation costs are reported as corporate overheads and are detailed in this section of the RIN Reporting.",null,"Reported as nil balance"]
[null,"2.7.2","Tree replacement program costs","Financial","N/A\nSA Power Networks does not have a tree replacement program in place for the 2010-2015 regulatory period. ","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","SA Power Networks does not have a tree removal program in place as part of its vegetation clearance program as tree removals are currently not allowed under the legislation. ",null,"Reported as nil balance"]
[null,"2.7.2","Other costs ","Financial","Work Order Data/SAP","Estimated","Uplift applied to allocate project support component of business overhead on a pro-rata basis between each category.","If there were any data provided, it would have 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 managment activities e.g. scoping, cutting, etc. .",null,"Reported as nil balance"]

{"sheet":"2.8 Maintenance","index":6,"n_rows":42,"n_cols":11,"rows_kept":42,"cut":false,"hidden":false,"merged":[[11,7,11,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[5,7,5,8],[6,7,6,8],[7,7,7,8],[8,7,8,8],[9,7,9,8],[10,7,10,8],[23,7,23,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[15,7,15,8],[16,7,16,8],[17,7,17,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[21,7,21,8],[22,7,22,8],[36,7,36,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[27,7,27,8],[28,7,28,8],[29,7,29,8],[31,7,31,8],[32,7,32,8],[33,7,33,8],[34,7,34,8],[35,7,35,8],[37,7,37,8],[38,7,38,8],[39,7,39,8],[40,7,40,8],[41,7,41,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,null,null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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.",null,"\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.2","All","Financial","SAP/Bex Analyzer","Estimated","The figures contained within 2.8 and 2.12 (mtce section) reconcile back to the Regulatory accounts, however the split between the various AER categories has required various assumptions that require the figures to be classified as estimates.","Bex report 'Order by GL for Regulatory Year' was produced for the 14-15 Financial year on each maintenance activity and further down to material code and then by expenditure category. The material codes or activity codes have been mapped to fit with the various AER reporting categories after discussions with operational managers.\nA mapping table has been provided within the 2.12 Input Table Working.xls file. The reconciliation to the regulatory accounts can be found in the 2.8 Mtce - Reconciliation 1415v2.xls file. This file takes the total direct costs as captured in the 2.12 Input table working.xls file and adds Project Support and Works management costs in line with Regulatory accounting. The maintenance figures reconcile to the regulatory accounts after adjusting for the inclusion of activities A81-A87 and A18 which are included as Telecommunications Asset expenditure which is an offset in the non network figures.\n"]
[null,"2.8.2","M17-N20\nNetwork underground cable maintenance - expenditure","Financial","SAP/Bex Analyzer","Estimated"," The information is not captured in enough detail to accurately extract actual data from SAP in the format that the AER require.","Bex reports 'Order by GL for Regulatory Year' for each maintenance activity and further down to material code which are then re-grouped to match table reporting categories.\nThe activities included align with that reported in the regulatory accounts",null,null,"SAPN does not have a breakdown of costs for CBD and non-CBD network underground cable maintenance. Hence, figures shown are the total for both CBD and non-CBD."]
[null,"2.8.1","All","Non-financial","N/A","Estimated",null,null,null,"All values are stated in 0s, unless stated in the Basis of Preparation"]
[null,"2.8.1","E13-G14         Pole tops, overhead lines & service lines maintenance","Non-financial","5.2 Asset Age Profile and 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. The asset quantity inspected/maintained is based on the the number of DD notifications raised to plate poles.",null,null,"Inspection cycle is 5 and 10 years based on corrosion zones. SA Powernetworks do not maintain service lines."]
[null,"2.8.1","E15-G15             All poles","Non-financial","5.2 Asset Age Profile and PAT","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 the the total number of poles recorded in PAT (Priority Asset Tool) download.",null,null,"Inspection cycle is 5 and 10 years based on corrosion zones."]
[null,"2.8.1","E16-G16\nAll overhead assets","Non-financial","5.2 Asset Age Profile/Patrol Feeder List/SAP","Estimated",null,"The overall total network route KMs based on GIS data  is approximately 65,355 kms.  \nThe total line patrolled (route KM) is based on pre-bush fire patrols conducted every year which is approximately 49,861 kms (inclusive of 8,889 kms of OCI/GCI). Data recorded in PBF Patrol Feeder List. ",null,null,"Total route covered for OCI/GCI only in 2014/15 is 8,889 kms based on Work Orders in SAP"]
[null,"2.8.1","E17-E20, G17-G20\nunderground cable asset quantity and average age","Non-financial","(1) 2AMP 2.1.07 CBD 2009 to 2020 ;   (2) AMP for Metropolitan Distribution Cables up to 11kV and City Manholes - August 2003 ;  (3) AMP Sub Transmission Cable - August 2003;        (4) 5.2 Asset Age Profile","Estimated",null,"The estimated length of underground cable repairs carried out is based on number of FM notifications raised (HV and LV) multiplied by 2 metres per repair (or per FM notification).  ",null,"The average age by voltage is determined from 5.2 Asset Age Profile data whereas the the average age by CBD and non-CBD is based on estimations.The first batch of underground cables were installed in the early 1950s predominantly within the CBD area and this was progressively carried out over the years to includ non-CBD areas as well up till the present. The past 20 years have seen the most increase in the installation of the underground cables both in the CBD and non-CBD. Hence it is estimated that the average age of underground cables within the CBD is about 30 years, and in non-CBD approximately 20 years as at end of 2013. A 2% escalation is applied to each year, hence, the average age at end of 2014 is 31.2 years and 21.2 years for CBD and non-CBD respectively."]
[null,"2.8.1","F17-F19\nunderground cable asset quantity inspected/maintained","Non-financial","(1) 2AMP 2.1.07 CBD 2009 to 2020  (2) AMP for Metropolitan Distribution Cables up to 11kV and City Manholes - August 2003            (3) AMP Sub Transmission Cable - August 2003                ","Estimated",null,"Total length KM split between CBD and non-CBD is based on estimates derived mainly through Data Source (1) and (2) (Column G) i.e. 3% of UG cable network is in CBD, and 97% in non-CBD. The data available does not differentiate whether cable repairs are carried out in CBD or non-CBD. Hence, the figure of 1.13 km reported is based on the total UG cable repairs for both LV and HV.",null,"Number of FM notifications is obtained from SAP. ","The figure of 1.13 km in cell F19 covers the total for both CBD and Non-CBD underground cable repairs. "]
[null,"2.8.1","E17 - G20\nunderground cable inspection cycle","Non-financial","Network Maintenance Manual No. 12","Estimated",null,"Per Network Maintenance Manual No. 12"]
[null,"2.8.1","E21 -  G21 distribution 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.  Asset quantity inspected/maintained is based on SAP."]
[null,null,"E22 - G22 distribution substation switchgear (within substations and stand-alone switchgear) - quantity, quantity inspected/maintained, age","Non-financial","5.2 Asset Age Profile/SAP/GL switchgear 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.  Asset quantity inspected/maintained is based on SAP. Asset quantity includes GL switchgears, and reclosers and sectionalisers but excludes CBs and disconnectors (this is covered in \"Other\" under \"Zone substation equipment maintenance (switchgear)\" ",null,"The quantity of assets inspected include GL switchgears (from GL switchgears record) and reclosers (based on number of recloser reading jobs in SAP). CBs and disconnectors were previously captured under this asset category but are now captured under \"Other\" (E38-G38) - Zone Substation Equipment Maintenance (Switchgear)"]
[null,"2.8.1","E23 - I23\nearth mats","Non-financial","Not applicable","Estimated","Not reportable as new category. Refer to AER clarification received 8 Aug 14 from Scott Haig, in particular:\n\n7. Where we have introduced new categories into the templates (eg. Tab 2.2 Repex “Asset Category”) that are not relevant to your business, you may respond by leaving that row blank (the data validation permits a null response)."]
[null,"2.8.1","E24 - G24\ndistribution substation properties - quantity, 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 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. ",null,null,"The quantity 74,624 excludes : 1) Ground Outdoor/Indoor Chamber Mounted; 2) CB Refurbished; 3) Pipe Buswork Substations "]
[null,"2.8.1","F24\ndistribution substation properties - quantity inspected/maintained","Non-financial","5.2 Asset Age Profile and BEX Analyser","Estimated","The total estimated number and average age of Distribution Substation Properties is derived from 5.2 Asset Age Profile under the descriptor \"Transformers\" for all \"Ground Outdoor/Indoor Chambers Mounted (ref: AJ83 to EJ99). The number of properties maintained annually is based on the number of work orders raised, and compared against the total opex (non-routine).","The estimated number of Distribution Substation Property maintained  is worked out based on the total opex (non-routine) and number of work orders raised. Cost incurred per site maintained on average in the past 5 years is $700.00. For 2014/15, the OPEX spend is $48,188. Therefore, $48,188/$700 = 69 properties.",null,"Run SAP transaction IW28/LMD020/All subcodes","Distribution substation properties maintained entails cleaning, repairing, weeding, trimming of grass, etc."]
[null,"2.8.1","E25 - G25\nzone substation transformers","Non-financial","Asset quantity, average age - 5.2 Asset Age Profile\n\nAsset inspected/maintained - SAP\n","Estimated","Asset quantity - estimation results from methodology used to define earlier years in nominated period\n\nAsset inspected/maintained - actual\n\nAverage age - see comment re quantity","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",null,"Asset quantity - assumes age profile 5.2 (by others) SAP based & accurate\n\nAsset inspected/maintained - includes all mtce cycles but excludes inspections (refer 'Zone substation asset inspection')\n\nAverage age - see comment re quantity","The data in 5.2 for this category includes both substation and line transformers."]
[null,"2.8.1","E26 - G26\ndistribution transformers within zone substations","Non-financial","SAP","Estimated",null,"Asset quantity - SAP dump 09 Jun 2015\n\nAsset inspected/maintained - inspected during sub site inspection, maintained by defect\n\nAverage age - not reported as data quality low (year of manufacture not consistently recorded in SAP), making age calculation accuracy low (questionable)"]
[null,"2.8.1","E27 to G27\nTransformers - HV","Non-financial","Not applicable",null,null,null,null,null,"no assets defined as 'TRANSFORMERS - HV' in zone substations"]
[null,"2.8.1","E28-G28\nzone substation - other equipment","Non-financial","5.2 Asset Age Profile, SAP, Asset Mgmt Plan","Estimated","Asset quantity - based on 2013/14 year (previous CAT RIN), adjusted for changes during 2014/15\n\nAsset inspected/maintained - actual\n\nAverage age - see comment re quantity","Asset quantity - qty based on 2013/14 CAT RIN, cross referenced with 2015 sub site list & adjusted for changes during 2014/15 - 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 (2013/14 CAT RIN) & adjusted for changes during 2014/15 - sum/count profile from nominated year end back to start of profile",null,"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"]
[null,"2.8.1","E29-G29\nzone substation properties","Non-financial","5.2 Asset Age Profile, SAP","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",null,"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"]
[null,"2.8.1","E30-G31\nPublic lighting",null,"Not required to report as negotiated services"]
[null,"2.8.1","E32\nSCADA and network control maintenance - asset quantity","Non-financial","SCADA configuration files                  ","Estimated",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."]
[null,"2.8.1","F32\nSCADA and network control maintenance - quantity inspected/maintained","Non-financial","SAP","Estimated",null,"There is currently no SCADA assest inspection or maintance plan, SCADA assets are repaired on failure. Number of sites repaired in 2014/15 are captured in a defect spreadsheet managed by the field service works  scheduler. The value in this field is total number of defects worked on in 2014/15.",null,"Not Applicable"]
[null,"2.8.1","G32\nSCADA and network control maintenance - average age","Non-financial","SCADA configuration files                           Tracking spreadsheet","Estimated",null,"Average asset age from 2013/2014 was aggregated with new assets added in 2014/2015. New assets were given an age of 1 year.",null,"Not Applicable","Some of these assets have been in service over their expected manufacturer life, for example the TDU16 has a life expectancy or approx 15 years, the TDU has been in service since 2000/2001, which means its already 13 years (close to end of life), its ther"]
[null,"2.8.1","E33 - G33\nprotection system maintenance","Non-financial","5.2 Asset Age Profile, SAP, LAN spreadsheet","Estimated","Asset quantity - actual\n\nAsset inspected/maintained - actual\n\nAverage age - estimate","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",null,"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 2014/15 age profile of relays (provided by others for RIN 5.2) & therefore 'inherit' assumptions made to compile age profile"]
["`","2.8.1","E34-G34\nSubtransmission asset maintenance",null,"Not applicable",null,"Not applicable","Not applicable"]
[null,"2.8.1","E35 to G35\nVarious assets","Non-financial","SAP and maintenance records","Estimated","Asset quantity, asset quantity inspected and average age figures are only for Communications Network Assets","For Asset Quantity, used information in tab 5.2. For Asset Quantity Inspected, used SAP and maintenance reports."]
[null,"2.8.1","E36 to G36\nGround Clearance access tracks",null,"Not applicable",null,"Not applicable","Not Applicable"]
[]
[]
[]
[]
[]
[null,"2.8.1","E37-G37\nOther - (1) Substation asset inspection","Non-Financial","Asset quantity - LAN spreadsheets\n\nAsset inspected/maintained - SAP\n\nAverage age - historical spreadsheet","Estimated","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",null,"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","Asset quantity - source is LAN directory for PM work plan preparation\n\nAsset inspected/maintained - nil\n\nAverage age - nil"]
[null,"2.8.1","E38-G38\nOther - (2) Zone substation equipment maintenance (switchgear)","Non-Financial","Asset quantity - 5.2 Asset Age Profile\n\nAsset inspected/maintained - SAP\n\nAverage age - 5.2. Asset Age Profile","Estimated",null,"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",null,"Asset quantity - only covers circuitbreakers & disconnectors (excludes RMU's & load switches) - assumes age profile 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","Asset quantity - nil\n\nAsset inspected/maintained - nil\n\nAverage age - nil"]
[null,"2.8.1","E39-G39\nOther - (3) Numbers of signages & IDs replaced","Non-Financial","Asset Quantity - SAP                                          Asset Inspected/Maintained - SAP                                                 Average Age - SAP                       ","Estimated",null,"The number of signages and IDs replaced are estimated based on the number of notifications raised in SAP.",null,"The number of signages/IDs is assumed to be equivalent to the number of distribution substation transformers installed (ref E21)."]
[null,"2.8.1","E40-G40\nOther - (4) Power Station Maintenance, Asset Records Feeder Diagram Maintenance, Compliance Auditing, Asset Location Services, Customer Service Penalties","Non-Financial","SAP","Estimated",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."]

{"sheet":"2.9 Emergency Response","index":7,"n_rows":8,"n_cols":11,"rows_kept":8,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[9,7,9,8],[5,7,5,8],[6,7,6,8],[7,7,7,8],[8,7,8,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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","D11","Financial","SAP","Estimated",null,"Bex report 'Order by GL for Regulatory Year' was produced for the 2014/15 Financial year on each maintenance activity and then by expenditure category. Consistent with Regulatory reporting, the total emergency response figures are a total of E01-E19 activity types plus an allocated project support component, works management costs and irrecoverable third party damage as per regulatory accounts.  The raw data is found in 2.12 input data working.xls. This feeds the 2.9 Emerg Resp rec.xls file that includes the inclusion of the regulatory adjustments and reconciliation to the regulatory accounts."]
[null,"2.9.1","C55, C57, C59","Non-financial","MED Log","Estimated",null,"Major event days are recorded accordingly."]
[null,"2.9.1","D55, D57, D59","Financial","SAP ","Estimated","The manner in which fault maintenance (FM) notifications are recorded in SAP makes it difficult to differentiate which notifications raised are associated to a major event  day (MED) or otherwise, as the description on a FM notification is very brief and usually makes no mention if the defect is MED related. Hence, all FMs that are raised on a major event day are assumed to be defects as a result of the major event. ","1. Run SAP transaction IW28 to obtain all FM notifications and their associated work orders for the specified MED dates.                                       2. Run SAP query transaction SARP/PS91 (Activity Code : E01 for Emergency Response) with the lists of work orders acquired in (1) to obtain the associated costings.                                                                                  3. Project support overhead allocation is applied across all MED costs",null,"On a typical day, the average number of FM notifications raised is around 150 while on a MED the average number can be over 500. Hence, it is assumed that all fault maintenance (FM) notifications raised on a MED are MED associated defects.","Costs for Corporate overheads have been excluded"]

{"sheet":"2.10 Overheads","index":8,"n_rows":50,"n_cols":11,"rows_kept":50,"cut":false,"hidden":false,"merged":[[1,1,1,3],[1,4,1,10],[10,7,10,8],[7,7,7,8],[8,7,8,8],[9,7,9,8],[16,7,16,8],[2,7,2,8],[3,7,3,8],[4,7,4,8],[11,7,11,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[15,7,15,8],[5,7,5,8],[6,7,6,8],[29,7,29,8],[17,7,17,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[22,7,22,8],[23,7,23,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[27,7,27,8],[28,7,28,8],[21,7,21,8],[41,7,41,8],[30,7,30,8],[31,7,31,8],[32,7,32,8],[33,7,33,8],[34,7,34,8],[35,7,35,8],[36,7,36,8],[37,7,37,8],[38,7,38,8],[39,7,39,8],[40,7,40,8],[48,7,48,8],[49,7,49,8],[50,7,50,8],[42,7,42,8],[43,7,43,8],[44,7,44,8],[45,7,45,8],[46,7,46,8],[47,7,47,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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","Row 12 - Network Management","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Netwoks' Standard Control Services Operating Activities (Maintenance, Emergency Response and Vegetation Management).  Costs are included in total amounts reported for these Activities in 2014/15 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.",null,"Reported costs represent Network Overheads charged against the following SA Power Networks' Activities:  Maintenance, Emergency Response; and Vegetation Management."]
[null,"2.10.1","Row 13 - Network Planning","Financial","Reported as part of Network Operating Costs in 2014/15 Annual RIN.","Actual",null,"Costs reported as Network Operating Costs in SA Power Networks' annual regulatory reports comprise various operational functions that are distinguishable by specific Activity codes in SAP.  SAP B/W reports were run and the costs associated with each of these Activities were mapped to one of the cost categories in rows 13-18 in Table 2.10.1 in accordance with the definitions provided by the AER in the Regulatory Information Notice.  Network Operating Costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method.",null,"Reported costs against Network Planning represent the following SA Power Networks' Activities:  Easement management for assets leased from the Distribution Lessor Corporation; and Network Planning (excluding costs reported as Demand Management)."]
[null,"2.10.1","Row 14 - Network Control and Operational Switching","Financial","Refer Data Source for Row 13 - Network Planning.","Actual",null,"Refer Methodology for Row 13 - Network Planning",null,"Reported costs against Network Control and Operational Switching represent the following SA Power Networks' Activities:  Network Operations; Outage Management System Support; and other Systems Support. "]
[null,"2.10.1","Row 15 - Quality and Standard Functions","Financial","Refer Data Source for Row 13 - Network Planning.","Actual",null,"Refer Methodology for Row 13 - Network Planning",null,"Reported costs against Quality and Standard Functions represent the following SA Power Networks' Activities:  Reliability Management; Regulatory Compliance; Quality of Supply; Asset Records; Core Material and Equipment Management; Network Operation Standards and Manuals; Regulatory NEM; Asset Management; Compliance Auditing; Maintenance Planning; and Asset Location Services."]
[null,"2.10.1","Row 16 - Project Governance and Related Functions","Financial","Not applicable","Actual",null,"SA Power Networks does not report these functions as Network Operating Costs.  Rather, these type of functions are directly costed to SA Power Networks' capital projects and network maintenance activities as incurred."]
[null,"2.10.1","Row 17 - Other Network Overheads","Financial","Refer Data Source for Row 13 - Network Planning.","Actual",null,"Refer Methodology for Row 13 - Network Planning",null,"Reported costs against the Other Network Overheads category represent the following SA Power Networks' Activities:  Customer Service and Enquiries (excluding costs reported as Guaranteed Service Level Payments); Mobile Equipment; and Quality Assurance.  The costs in this category represent those which were previously reported in the mandatory Network operating Cost category called Other in the historical Category Analysis RIN.  For consistency, SA Power Networks have continued to report these costs in their own separate category. "]
[null,"2.10.1","Row 18 - Network Telephony","Financial","Refer Data Source for Row 13 - Network Planning.","Actual",null,"Refer Methodology for Row 13 - Network Planning",null,"Reported costs against the Network Telephony category represent the following SA Power Networks' Activities:  Network Business Telephone Access; Network Mobile Radio; Network Power Systems Management; Network Telecommunications Planning; and Network Telecommunications Operations.  Network Telephony has been included as a separate category in the Table to capture these Network Operating Costs due to (a) materiality, and (b) SA Power Networks does not consider that these activities meet the definition of any of the mandatory Network Operating Cost categories in the Regulatory Information Notice."]
[null,"2.10.1","Row 19 - Demand Management","Financial","Total of specified reporting lines for Demand Management and Demand Management Innovation Fund from the 2014/15 Annual RIN.","Actual",null,"Demand Management costs are captured against individual projects in SAP.  The reported value in the Table represents the total of these projects.  ",null,"Demand Management costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 20 - Guaranteed Service Level Payments","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Guaranteed Service Level Payments are captured against various Activities that sum to an individual GL expense account in SAP.  The reported value in the Table represents the total cost against the GL account. ",null,"Guaranteed Service Level Payments are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 21 - Call Centre","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Call Centre charges are captured against a specific Order and GL account in SAP.  The reported value in the Table represents this cost.  ",null,"Call Centre charges are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 22 - Full Retail Contestability","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Full Retail Contestability costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents the total cost in these cost centres excluding certain costs that are reported as specific cost lines in the Annual RIN, e.g. Meter Reading.",null,"Full Retail Contestability costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 23 - Network Insurance","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Network Insurance costs are contained within a specific Cost Centre in SAP relating to Risk and Insurance.  The reported value in the Table represents a percentage allocation of the total operating costs reported against the Risk and Insurance Cost Centre which are considered to relate directly to the Distribution Network.",null,"Network Insurance costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 24 - Distribution Licence Fee","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"The cost of the Distribution Licence Fee paid by SA Power Networks is captured against a specific Order and GL account in SAP.  The reported value in the Table represents this cost.  ",null,"Distribution Licence Fee costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 25 - Substation Property Maintenance","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Substation Property Maintenance costs are contained within specific Cost Centres in SAP relating to the Property Services and Real Estate & Easements groups.  The reported value in the Table represents a percentage allocation of the total operating costs reported against these Cost Centres which are considered to relate directly to the Distribution Network.",null,"Substation Property Maintenance costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 26 - Other Network Operation Costs","Financial","Specified reporting line in 2014/15 Annual RIN that relates to Debt Raising Costs.","Actual",null,"Debt Raising Costs are captured against a specific GL expense account in SAP.  The reported value in the Table represents the total cost against this GL account. ",null,"Debt Raising Costs are directly attributed to Standard Control Services as per SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 27 - Other Customer Services","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Other Customer Services costs are contained within specific Cost Centres in SAP and relate to SA Power Networks' Customer Relations department.  The reported value in the Table represents an allocation of the total cost in these cost centres excluding Call Centre charges that are reported separately in row 21. ",null,"The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.1","Row 40 - Network Management ","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Netwoks' Alternative Control Services Operating Activities (Metering).  Costs are included in total amounts reported for these Activities in 2014/15 Annual RIN.","Actual",null,"Refer Methodology for Row 12 - Network Management",null,"Reported costs represent Network Overheads charged against SA Power Networks' Meter Maintenance Activities."]
[null,"2.10.1","Rows 41-44 - Network Operating Costs","Financial","Not applicable","Actual",null,"SA Power Networks reports all Network Operating Costs as directly attributable to Standard Control Services, thus values are nil for Alternative Control Services."]
[null,"2.10.1","Row 45 - Other Customer Services","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Refer Methodology for Row 27 - Other Customer Services",null,"The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.1","Row 68 - Total Overhead Expenditure - Negotiated 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 2014/15 Annual RIN.","Actual",null,"Refer Methodology for Row 12 - Network Management",null,"Reported costs represent Network Overheads charged against all of SA Power Networks' Negotiated Service Activities."]
[null,"2.10.1","Row 69 - Total Overhead Expenditure - Unregulated Services","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Networks' Unregulated Service Activities.  Costs are included in total amounts reported for these Activities in the 2014/15 Annual RIN.","Actual",null,"Refer Methodology for Row 12 - Network Management",null,"Reported costs represent a portion of the Business Overhead transfers charged against all of SA Power Networks' Unregulated Service Activities.  The reported portion relates to Network Overheads charged to Unregulated Services against Network-related cost centres only.  Overheads charged against Non-network related cost centres, e.g. SA Power Networks' Construction and Maintenance Services group (being a group dedicated to external business) are assumed to relate to the recovery of that group's own Business Overheads, thus are not considered to be Network Overheads."]
[null,"2.10.1","Row 70 - Network Management","Financial","Business Overhead transfers as per SAP B/W reports for SA Power Networks' Standard and Alternative Control Services Capital Activities (Asset Replacement, Capacity, Connections, Environmental, PLEC, Reliability, Safety and Strategic).  Costs are included in total amounts reported for these Activities in the 2014/15 Annual RIN.","Actual",null,"Refer Methodology for Row 12 - Network Management",null,"Reported costs represent Network Overheads charged against the following SA Power Networks' Standard and Alternative Control Capital Activities:  Asset Replacement (includes Metering), Capacity, Connections (includes Metering), Environmental, PLEC, Reliability, Safety and Strategic."]
[null,"2.10.1","Rows 71-74 - Network Operating Costs","Financial","Not applicable","Actual",null,"SA Power Networks reports all Network Operating Costs as directly attributable Standard Control Services operating expenditure, thus values are nil for capitalised overheads."]
[null,"2.10.2","Row 109 - CEO, Planning and Audit","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"CEO, Planning and Audit costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"Reported costs against CEO, Planning and Audit represent the following SA Power Networks' Cost Centres:  CEO and Chairman; Strategic Business Development; Strategic Planning; and Audit Services.  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 110 - Communications","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Communications costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"Reported costs against Communications represent the following SA Power Networks' Cost Centres:  Communications; and Sponsorship (excluding Sponsorship GL account expense).  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 111 - Regulation and Company Secretary","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Regulation and Company Secretary costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"Reported costs against Regulation and Company Secretary represent the following SA Power Networks' Cost Centres:  Regulation (excluding Distribution Licence Fee reported separately in row 24); and Company Secretary.  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 112 - Finance","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Finance costs are contained within specific Cost Centres and GL account codes in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres and GL accounts.",null,"Reported costs against Finance represent the following SA Power Networks' Cost Centres:  CFO; Finance Branch; Finance Adjustments; Taxation; Treasury; Network Management Finance; Field Services Finance; Regulatory Finance; Accounts Payable; Payroll and Systems Updating; Purchasing and Contracts; Purchasing; and Inventory, together with specific GL accounts to capture costs relating to Employee Bonuses and Voluntary Separation Packages.  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 113 - HR and Training","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"HR and Training costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"Reported costs against HR and Training represent the following SA Power Networks' Cost Centres:  GM People and Culture; Employee Relations; Workforce Management; Learning and Development; Employee Foundation; Training Centre - Apprenticeship Services; Training Centre - Management; Training Centre - Administration Services; Training Centre - Electrical Training; Training Centre - Poleline Training; and Training Centre - Davernport Training Centre.  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 114 - Property","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Property costs are contained within specific Cost Centres in SAP relating to the Property Services and Real Estate & Easements groups.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres excluding costs reported separately against Substation Property Maintenance in row 25.",null,"The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 115 - Information Systems","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Information Systems costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 116 - Risk Management","Financial","Specified reporting line in 2014/15 Annual RIN.","Actual",null,"Risk Management costs are contained within specific Cost Centres in SAP.  The reported value in the Table represents an allocation of the total operating costs reported against those Cost Centres.",null,"Reported costs against Risk Management represent the following SA Power Networks' Cost Centres:  Risk and Insurance (excluding amounts reported separately as Network Insurance in row 23); GM Corporate Services; Legal Services; OHS; Environmental Services; and Printing Services.  The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 117 - Other Allocated Costs","Financial","Specified reporting line in 2014/15 AER Annual RIN.","Actual",null,"SA Power Networks reports Self Insurance and Superannuation costs on the basis of cash payments rather than the accounting expense.  This reporting is consistent with the methodology described in SA Power Networks' Cost Allocation Method.   This line item represents actual Self Insurance costs and the regulatory adjustment made to Superannuation to report on a cash payments basis.",null,"The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 130 - CEO, Planning and Audit","Financial","Refer Data Source for Row 109 - CEO, Planning and Audit.","Actual",null,"Refer Methodology for Row 109 - CEO, Planning and Audit.",null,"Refer Assumptions for Row 109 - CEO, Planning and Audit for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 131 - Communications","Financial","Refer Data Source for Row 110 - Communications.","Actual",null,"Refer Methodology for Row 110 - Communications.",null,"Refer Assumptions for Row 110 - Communications for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 132 - Regulation and Company Secretary","Financial","Refer Data Source for Row 111 - Regulation and Company Secretary.","Actual",null,"Refer Methodology for Row 111 - Regulation and Company Secretary.",null,"Refer Assumptions for Row 111 - Regulation and Company Secretary for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 133 - Finance","Financial","Refer Data Source for Row 112 - Finance.","Actual",null,"Refer Methodology for Row 112 - Finance.",null,"Refer Assumptions for Row 112 - Finance for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 134 - HR and Training","Financial","Refer Data Source for Row 113 - HR and Training.","Actual",null,"Refer Methodology for Row 113 - HR and Training.",null,"Refer Assumptions for Row 113 - HR and Training for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 135 - Property","Financial","Refer Data Source for Row 114 - Property.","Actual",null,"Refer Methodology for Row 114 - Property.",null,"The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 136 - Information Systems","Financial","Refer Data Source for Row 115 - Information Systems.","Actual",null,"Refer Methodology for Row 115 - Information Systems.",null,"The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 137 - Risk Management","Financial","Refer Data Source for Row 116 - Risk Management.","Actual",null,"Refer Methodology for Row 116 - Risk Management.",null,"Refer Assumptions for Row 116 - Risk Management for list of Cost Centres cmprising this category.  The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method."]
[null,"2.10.2","Row 138 - Other Allocated Costs","Financial","Refer Data Source for Row 117 - Other Allocated Costs.","Actual",null,"Refer Methodology for Row 117 - Other Allocated Costs.",null,"The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 151 - Total Overhead Expenditure - Negotiated Services","Financial","Reported value represents total corporate cost allocations (shared costs) to Negotiated Services plus adjustments to Negotiated Services capital expenditure (being the regulatory adjustment made to Superannuation to report on a cash payments basis) as reported in the 2014/15 Annual RIN.","Actual",null,"The total shared cost allocation to Negotiated Services was derived through the application of SA Power Networks' Allocated Cost approach (refer Table 4 of SA Power Networks' Cost Allocation Method).",null,"The percentage allocations of costs to Negotiated Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 152 - Total Overhead Expenditure - Unregulated Services","Financial","Reported value represents total corporate cost allocations (shared costs) to Unregulated Services plus adjustments to Unregulated Services capital expenditure (being the regulatory adjustment made to Superannuation to report on a cash payments basis) as reported in the 2014/15 Annual RIN.","Actual",null,"The total shared cost allocation to Unregulated Services was derived through the application of SA Power Networks' Allocated Cost approach (refer Table 4 of SA Power Networks' Cost Allocation Method).",null,"The percentage allocations of costs to Unregulated Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 153 - Other Allocated Costs - Standard Control Services","Financial","Reported value represents the regulatory adjustment made to Standard Control Services capital to report Superannuation on a cash payments basis as per the 2014/15 Annual RIN.","Actual",null,"SA Power Networks reports Superannuation costs on the basis of cash payments rather than the accounting expense.  This reporting is consistent with the methodology described in SA Power Networks' Cost Allocation Method.   This line item represents the regulatory adjustment made to Superannuation to report on a cash payments basis.",null,"The percentage allocation of costs to Standard Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]
[null,"2.10.2","Row 154 - Other Allocated Costs - Alternative Control Services","Financial","Reported value represents the regulatory adjustment made to Alternative Control Services capital to report Superannuation on a cash payments basis as per the 2014/15 Annual RIN. ","Actual",null,"Refer Methodology for Row 153 - Other Allocated Costs - Standard Control Services.  Note, SA Power Networks have separately reported this line under the 'Capitalised Overheads - Standard Control Services' heading as, although it relates to Alternative Control Services, there was no provision made in Template 2.10 to otherwise report this information.  The reporting of this value is necessary in order for SA Power Networks to reconcile total Alternative Control Services capital in Table 2.1.3 of the Category Analysis RIN.",null,"The percentage allocation of costs to Alternative Control Services is in accordance with SA Power Networks' Cost Allocation Method. "]

{"sheet":"2.11 Labour","index":9,"n_rows":31,"n_cols":11,"rows_kept":31,"cut":false,"hidden":false,"merged":[[10,7,10,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[5,7,5,8],[6,7,6,8],[7,7,7,8],[8,7,8,8],[9,7,9,8],[22,7,22,8],[11,7,11,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[15,7,15,8],[16,7,16,8],[17,7,17,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[21,7,21,8],[29,7,29,8],[30,7,30,8],[31,7,31,8],[23,7,23,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[27,7,27,8],[28,7,28,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\nExplanation/list of any assumptions made for data source, justification and methodology applied or made.","\nState any additional comments, notes or explanations."]
[null,{"$f":"B7","v":"2.11.1 Cost Metrics Per Annum"},"Column E - Average Staffing Levels\n\nConsolidated",{"$f":"D7","v":"Financial"},"Refer Rows 14 and 15 below.",{"$f":"F7","v":"Estimated"},"Refer Rows 14 and 15 below.","Sum of internal employees and labour hire employee Average Staffing Levels as calculated below.","",null,""]
[null,"2.11.1 Cost Metrics Per Annum","Column E - Average Staffing Levels\n\nEmployees","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.","Estimated","Whilst information on all employees is available, we do not report on the AER's defined job classifications. Assumptions are therefore made to assign positions to the RIN classifications. \n\nAdditionally it is impractical to undertake this exercise on a monthly basis to obtain completely accuracy on ASLs (this would require classification of approx 2,000 employees for 12 periods), therefore averages are calculated by taking data at 30 June and 31 December each year.","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). Note that 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 this 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.",null,"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;\n"]
[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.",null,"Professional - 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;\nSupport 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);"]
[null,"",null,"","","","","","","Skilled 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,"2.11.1 Cost Metrics Per Annum","Column E - Average Staffing Levels \n\nLabour Hire","Financial","Supplementary Labour reports provided by HR - provides details of hours worked for each supplementary labour hire person for the year.","Estimated","Whilst information on all supplementary labour employees is available, including hours worked, we do not report on the AER's defined job classifications. Assumptions are been made to assign positions to the AER RIN classifications. \n\nAdditionally, 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.","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 15 to calculate ASLs for Labour Hire employees.\n\n\n\n","","As described in the Justification tab, the majority of supplementary labour employees are employed on a less than full-time basis. It has not been practical to review every supplementary labour employee to determine available hours for each employee for the calculation of average full-time equivalent 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,{"$f":"B12","v":""},"Column F - Total Labour Cost\n\nConsolidated",{"$f":"D12","v":"Financial"},"Refer Rows 19 and 20 below.",{"$f":"F12","v":"Estimated"},"Refer Rows 19 and 20 below.","Sum of internal employees and labour hire employee Total Labour Cost as calculated below.",""]
[null,"","Column F - Total Labour Cost\n\nEmployees","Financial","Payroll Costs extracted from SAP (separate GL accounts exists for payroll costs), plus additional costs defined in the Category Analysis RIN for Labour Cost and 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)","Estimated","Whilst in total costs can be verified, they are not recorded against the classifications defined in the RIN and are allocated in line with the methodology described.","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,"Salaries and wages paid to employees is the most accurate representation to the allocation of total labour costs across the organisation."]
[null,"","Column F - Total Labour Cost\n\nLabour Hire","Financial","Labour Hire Costs extracted from SAP (a separate GL account exists for supplementary labour hire costs).","Estimated","Whilst in total costs can be verified, they are not recorded against the classifications defined in the RIN and are allocated in line with the methodology described.","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.","","Salaries and wages paid to internal employees is the most accurate representation to the allocation of supplementary labour costs per ASL.\n\nThis assumption is considered reasonable as SA Power Networks has parity arrangements defined in its Enterprise Bargaining Agreement. This requires that any supplementary labour is paid at equivalent rates to their internal counterparts for the same classification."]
[null,{"$f":"B15","v":""},"Column G - Average Productive Work Hours Per ASL\n\nConsolidated",{"$f":"D15","v":"Financial"},"Refer Rows 22 and 23 below.",{"$f":"F15","v":"Estimated"},"Refer Rows 22 and 23 below.","Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL as calculated below.",""]
[null,"","Column G - Average Productive Work Hours Per ASL\n\nEmployees","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","Estimated","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.","As described in the justification, 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 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)."]
[null,"","Column G - Average Productive Work Hours Per ASL\n\nLabour 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).","Estimated","Refer Row 17 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.","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 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","","As described above, Average Productive Work Hours are assumed to be the same as for internal labour employees, plus loading.\n\n"]
[null,{"$f":"B18","v":""},"Column H - \nStand-Down Occurrences Per ASL\n\nConsolidated",{"$f":"D18","v":"Financial"},"Refer Rows 25 and 26 below.",{"$f":"F18","v":"Estimated"},"Refer Rows 25 and 26 below.","Weighted average of internal employees and labour hire employee Stand Down Occurrences per ASL as calculated below.",""]
[null,"","Column H - \nStand-Down Occurrences Per ASL\n\nEmployees","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","Estimated","Actual stand down hours per employee are obtained. In line with the explanations above, assumptions are made for the derivation of AER defined labour classifications.","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,"","Column H - \nStand-Down Occurrences Per ASL\n\nLabour Hire","Financial","Actual stand down hours paid to each labour hire employee provided by HR.","Estimated","Actual stand down hours paid to each labour hire employee are provided by HR. In line with the explanations above, assumptions are made for the derivation of AER defined labour classifications.","Stand down hours for paid each classification are divided by ASLs to derive Average Stand Down Hours per ASL","",""]
[null,{"$f":"B21","v":"2.11.2 Extra Descriptor Metrics for Current Year"},"Column M - Average Productive Work Hours Per ASL - Ordinary Time\n\nConsolidated",{"$f":"D21","v":"Financial"},"Refer Rows 28 and 29 below.",{"$f":"F21","v":"Estimated"},"Refer Rows 28 and 29 below.","Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL - Ordinary Time as calculated below.",""]
[null,"2.11.2 Extra Descriptor Metrics for Current Year","Column M - Average Productive Work Hours Per ASL - Ordinary Time\n\nEmployees","Financial","Hours recorded by employees extracted from SAP.","Estimated","Refer Row 22 above - calculation of Average Productive Work Hours Per ASL","Refer Row 22 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,"2.11.2 Extra Descriptor Metrics for Current Year","Column M - Average Productive Work Hours Per ASL - Ordinary Time\n\nLabour Hire","Financial","Refer Row 23 above - Average Productive Work Hours Per ASL","Estimated","Refer Row 23 above - calculation of Average Productive Work Hours Per ASL","Refer Row 23 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\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","","It is reasonable to assume a correlation between  Average Productive Work Hours per ASL - Ordinary Time of internal and supplementary labour hire employees."]
[null,{"$f":"B24","v":""},"Column N - Average Productive Work Hours Hourly Rate Per ASL - Ordinary Time\n\nConsolidated",{"$f":"D24","v":"Financial"},"Refer Rows 31 and 32 below.",{"$f":"F24","v":"Estimated"},"Refer Rows 31 and 32 below.","Weighted average of internal employees and labour hire employee Average Productive Work Hours Hourly Rate per ASL - Ordinary Time as calculated below.",""]
[null,"","Column N - Average Productive Work Hours Hourly Rate Per ASL - Ordinary Time\n\nEmployees","Financial","Refer Rows 19 and 22 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL - Ordinary Time","Estimated","Refer Rows 19 and 22 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL","Overtime costs are extracted from SAP (refer row 37 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 E and the Average Productive Work Hours Per ASL - Ordinary Time in column M to derive an hourly rate.","",""]
[null,"","Column N - Average Productive Work Hours Hourly Rate Per ASL - Ordinary Time\n\nLabour Hire","Financial","Refer Rows 20 and 23 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL","Estimated","Refer Rows 20 and 23 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL","For 2014/15 supplementary labour overtime costs have been calculated as data was not available (refer Row 38 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 E and the Average Productive Work Hours Per ASL - Ordinary Time in column M to derive an hourly rate.","",""]
[null,{"$f":"B27","v":""},"Column O - Average Productive Work Hours Per ASL - Overtime\n\nConsolidated",{"$f":"D27","v":"Financial"},"Refer Rows 34 and 35 below.",{"$f":"F27","v":"Estimated"},"Refer Rows 34 and 35 below.","Weighted average of internal employees and labour hire employee Average Productive Work Hours per ASL - Overtime as calculated below.",""]
[null,"","Column O - Average Productive Work Hours Per ASL - Overtime\n\nEmployees","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.","Estimated","Refer Row 22 above - calculation of Average Productive Work Hours Per ASL","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,"","Column P - Average Productive Work Hours Per ASL - Overtime\n\nLabour Hire","Financial","Overtime hours per supplementary labour hire employee provided by HR.","Estimated","Refer Row 23 above - calculation of Average Productive Work Hours Per ASL","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,{"$f":"B30","v":""},"Column P - Average Productive Work Hours Hourly Rate Per ASL - Overtime\n\nConsolidated",{"$f":"D30","v":"Financial"},"Refer Rows 37 and 38 below.",{"$f":"F30","v":"Estimated"},"Refer Rows 37 and 38 below.","Weighted average of internal employees and labour hire employee Average Productive Work Hours Hourly Rate per ASL - Overtime as calculated below.",""]
[null,"","Column P - Average Productive Work Hours Hourly Rate Per ASL - Overtime\n\nEmployees","Financial","Refer Rows 19 and 22 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL","Estimated","Refer Rows 19 and 22 above - calculation of Total Labour Cost and Average Productive Work Hours Per ASL","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 E and the Average Productive Work Hours Per ASL - Overtime in column O to derive an hourly rate.","",""]
[null,"","Column O - Average Productive Work Hours Hourly Rate Per ASL - Overtime\n\nLabour Hire","Financial","Refer Row 32 above - calculation of Average Productive Work Hours Per ASL - Ordinary Time","Estimated","Refer Row 32 above - calculation of Average Productive Work Hours Per ASL - Overtime","Overtime costs for supplementary labour hire employees have been unable to be obtained for 2014/15. An Hourly Rate per ASL - Overtime has been calculated as total supplementary labour cost divided by total supplementary labour hours, plus a 14% mark-up for additional payments for overtime. The mark-up is equivalent to the average mark-up to the hourly rate for internal employees for overtime for the 2012/13 regulatory year.\n\nOvertime costs are divided by the number of ASLs in column E and the Average Productive Work Hours Per ASL - Overtime in column O to derive an hourly rate.\n","","Overtime rates for internal employees reflect rates paid to labour hire employees.\n\nThis assumption is considered reasonable as SA Power Networks has parity arrangements defined in its Enterprise Bargaining Agreement. This requires that any supplementary labour is paid at equivalent rates to their internal counterparts for the same classification (including overtime).\n\n2012/13 is a representative year in relation to ordinary and overtime rates."]

{"sheet":"2.12 Input Tables","index":10,"n_rows":41,"n_cols":10,"rows_kept":41,"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.1000000000000001,4,5,6,8,9,10,11]
[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)","Methodolody\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","\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,"Replacement","2.12 Input tables\nREPLACEMENT"]
[null,2.12,"General Information","Financial","Various sources","Estimated","All cost data are dependent on replacement and failure data we collected before, which means, all effects of assumption/estimation we've made before will affect the cost, which means all cost data are estimated as well.","Process to get expenditure data for 2.12:\n- From Bex report we could extract the breakdown cost for each item. The summation of each individual cost summarised the total cost for each category in 2.12","- 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","NOTE: Strategic Asset Management Personnel (Bolei & Samir) are responsible for the \"Rreplacement\" Part of 2.12. Herein is the basis of preparation for all data contributed by Groups other than Strategic Asset management.  Please contact the relevant group as per column D."]
[null,2.12,"Replacement","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, all 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"]
[null,2.12,"Row 66 to 74 - Replacement","Financial","Table 2.2.1","Estimated","Data is estimated as it was necessary to adjust source SAP reports to reported totals in Table 2.2.1","SAP reports provided splits for materials, labour, contracts and other costs.  It was necessary to adjust these values to equate to the reported totals on a pro-rata basis.","Refer methodology for row 13 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.2.1."]
[null,2.12,"Row 74 - Communications Network Assets, Communications Site Infra, Communications Linear Assets  & Scada (other)","Financial","SAP","Estimated","Data is estimated as it was necessary to make some assumptions in order to split costs between categories,  e.g. in order to allocate the project support component of business overhead between the categories on a pro-rata basis.","Data was extracted from SAP by finance departement using BW Reports. Search was conducted under specific cost numbers","No assumptions, just separated data in required categories","Spread sheets used:  'Repex Telco projects list' and Bex reports on L27 & L56 and \"Repex Scada projects list - TasnimV4\""]
[null,2.12,"Row: 'Transformers'","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, L36) which provided the direct and component costs of asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- SAP BeX financial reports (containing project numbers and direct costs by financial year) were used to capture failure, replacement and refurbishment expenditure from the list of NW & Noti numbers by RIN category.\n- Project construction specs were used to determine the breakdown of coordinated replacement works within each asset group (either TF, CB, Switch, Protection categories) captured in the total project cost.\n- Component costs were removed from the project total cost to give the total estimated replacement cost of the TF.\n- TF Refurbishment costs are included against 'Other' expenditure.","- All replacement OPEX was assumed to be dedicated to primary asset replacement (either CB or TF, i.e. no coincident replacement of other asset categories).\n- Any \"other\" costs (civils, earthing etc) required as part of TF replacement (and not broken down into CB, switch, protection relay expenditures) are included in TF replacement category.\n- Replacement of Gladstone 11kV regulator was replaced to allow refurbishment – it has been reported as capital refurbishment repex\n- All expenditure is reported in the financial year incurred.","- To avoid possible cost duplication - capitalised Notis are excluded from OPEX replacement expenditure.\n- Replacement costs are reported in the financial year incurred and may relate to asset replacements outside of the reported financial year."]
[null,2.12,"Row: 'Switchgear'","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, L36) which provided the direct and component costs of asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- SAP BeX financial reports (containing project numbers and direct costs by financial year) were used to capture failure, replacement and refurbishment expenditure from the list of NW & Noti numbers by RIN category.\n- Project construction specs were used to determine the breakdown of coordinated replacement works within each asset group (either TF, CB, Switch, Protection categories) captured in the total project cost.\n- Switchgear expenditure contains total expenditure derived for CBs and switches of all voltages.\n- CB Refurbishment costs are included against 'Other' expenditure.\n","- All replacement OPEX was assumed to be dedicated to primary asset replacement (either CB or TF, i.e. no coincident replacement of other asset categories).\n- Any \"other\" costs (civils, earthing etc) required as part of TF replacement (and not broken down into CB, switch, protection relay expenditures) are included in TF replacement category.\n- All expenditure is reported in the financial year incurred.","- To avoid possible cost duplication - capitalised Notis are excluded from OPEX replacement expenditure.\n- Switchgear category contains all expenditure on CB and switch (disconnector/DF/LSDF/LS) replacements.\n- Replacement costs are reported in the financial year incurred and may relate to asset replacements outside of the reported financial year."]
[null,2.12,"Row: 'SCADA network control and protection systems'","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54 & L36) which provided the direct and component costs of each asset replacement by budget category and financial year.","Estimated","At the project level, costs from SAP are actual costs. However, as projects often involve replacements of multiple asset categories (ie TFs, CBs, switches, protection devices) it has been necessary to estimate the proportion of assigned costs to each asset category.","- The costs for embedded protection replacements were determined by the number of protection schemes multiplied by a representative scheme unit cost.\n- Unit cost of disconnector replacement formulated:\n-- Based on protection relay replacement expenditure over the period (2008/09 to 2014/15 supplied by network protection group), averaged to give a scheme replacement cost.\n- Estimated protection replacement cost (number schemes x unit cost) was converted to a percentage of the total project cost (as spent or estimated total) to provide proportional expenditure across the life of the replacement project.\n- The allocation of costs from each replacement project was summed by financial year and RIN switch category to give the total protection replacement expenditure for that financial year.","- Unit cost assumed to be the average protection scheme replacement cost over the period (2008/09 to 2014/15).\n-The average scheme replacement cost = $72,000 (ex O/H).\n- All expenditure is reported in the financial year incurred.","- Replacement expenditure included in the 'SCADA network control and protection systems' asset category\n- Replacement costs are reported in the financial year incurred and may relate to asset replacements outside of the reported financial year."]
[null,2.12,"Row: 'OTHER - Non Category Substation asset replacement/refurbishment'","Financial","Financial reports were obtained from SAP (BeX reports - L14, L54, & L36) which provided the direct and component costs of each asset replacement project by financial year.","Estimated",null,"-‘OTHER - Non Category Substation asset replacement/refurbishment’ costs are determined as the sum of:\n1. Safety based (SAP L36) asset replacement expenditure not allocated to TF/CB/Switch categories;\n2. Safety based (SAP L36) substation replacement expenditure (Nangwarry, Synagogue Pl & Birdwood rebuilds); and\n3. The total 2014-2015 substation capital expenditure under planned (L14) and unplanned (L54) replacement/refurbishment SAP budget categories, less all allocation to:\n- TF replacement\n- CB replacement\n- Switch replacement\n- Protection replacement\n- Dedicated SCADA (RTU/TDU) replacement.","- This category relies on information contained in the other categories of TFs, CBs, Disconnectors and Protection. These assumptions are inherited here.\n- Dedicated protection & SCADA replacement expenditure (i.e. not funded as part of CB, TF or Switch replacements) has been excluded from ‘OTHER - Non Category Substation asset replacement/refurbishment’ expenditure based on NW project numbers provided by Network SCADA and Network Protection groups.","- This category includes a variety of replacement programs, capitalised refurbishment works across substation assets (excluding CBs & TFs). i.e. poles, civil infrastructure. It also includes a range of miscelaneous capital expenditure used to manage in service assets & 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 expediture included in this category relates to replacement works.\n- Expenditure is reported in the financial year incurred and may relate to asset replacements outside of the reported financial year.\n- Expenditure in this category includes all CB and TF refurbishment expenditure (to be consistent with 2008-2014 RIN reporting)."]
[null,"Vegetation Management"]
[null,2.12,"Row 9 - Vegetation Management","Financial","Table 2.7.2","Estimated","Data is estimated as it was necessary to make some assumptions in order to split costs between categories,  e.g. in order to allocate the project support component of business overhead between the categories on a pro-rata basis.","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.7.2.  In some cases, however, it was necessary to allocate direct operational support costs across categories using pro-rata direct costs for the associated activities on a pro-rata basis.","The direct materials category consists of materials plus a proportional allocation of direct operational support costs.  The direct labour category comprises internal and external labour employed by SA Power Networks plus a proportional allocation of direct operational support costs.  The contracts category consists of contract costs with external service providers plus a proportional allocation of direct operational support costs.  The other cost category represents all other costs not captured in the aforementioned categories or the related party contract category plus a proportional allocation of direct operational support costs.  The total of all categories for each year equals the total of costs reported in Table 2.7.2."]
[null,"Routine & Non-routine Maintenance"]
[null,2.12,"Rows 27 to 50 - Routine and Non-Routine Maintenance","Financial","Table 2.8.2","Estimated","Data is estimated as it was necessary to make some assumptions in order to split costs between categories,  e.g. in order to allocate the project support component of business overhead between the categories on a pro-rata basis.","SAP reports provided splits for materials, labour, contracts and other costs.  It was necessary to adjust these values to equate to the reported totals on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.8.2."]
[null,"Overheads"]
[null,2.12,"Row 51 - Network Overheads","Financial","Table 2.10.1 excluding allocations to Negotiated and Unregulated Services","Estimated","Data is estimated as it was necessary to make some assumptions in order to split costs between categories,  e.g. in order to allocate network overheads across categories.","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 direct operational support costs across categories using pro-rata direct costs for the associated activities on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.10.1 (excluding Negotiated and Unregulated Services).","Note, as SA Power Networks does not have a direct control relationship with any of our related parties, we are unable to obtain or report related party margin information in Table 2.12.  Should the AER require this information, this will need to be sought directly from our Related Parties. "]
[null,2.12,"Row 52 - Corporate Overheads","Financial","Table 2.10.2 excluding allocations to Negotiated and Unregulated Services","Estimated","Data is estimated as it was necessary to make some assumptions in order to split costs between categories,  e.g. in order to allocate revenue offsets across categories.","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 perform allocations  across categories using pro-rata direct costs for the associated cost centres and activities on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.10.1.","Note, as SA Power Networks does not have a direct control relationship with any of our related parties, we are unable to obtain or report related party margin information in Table 2.12.  Should the AER require this information, this will need to be sought directly from our Related Parties. "]
[null,2.12,"Row 51 to 52 - Columns Q-R - Related Party Contracts","Financial","Related party costs as reported in the 2014/15 Annual RIN together with additional related party expenditure which did not meet the materiality threshold for disclosure in the Annual RIN.","Actual",null,"Values reported are as per data source.  Related Party values were deducted from other cost lines in Table 2.12 to ensure totals reconcile to each individual tab.",null,"Note, as SA Power Networks does not have a direct control relationship with any of our related parties, we are unable to obtain or report related party margin information in Table 2.12.  Should the AER require this information, this will need to be sought directly from our Related Parties. "]
[null,"Augmentation"]
[null,2.12,"Augmentation - SUBTRANSMISSION SUBSTATIONS, SWITCHING STATIONS , ZONE SUBSTATIONS","Financial","BeX reports L02, 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. ","Direct costs from all Augex BeX report categories designated as being related to \"Substations\" are summed for the relevant regulatory year and input into the Direct Cost cells for the appropriate years.  Adjustments were made to exclude projects that were classified as Repex but include projects which incurred costs but are not yet completed.  Direct costs for identified projects are summed for each year are also input into the Direct Cost cells for the appropriate year.   Labour, contract and other costs were calculated  the same way."]
[null,2.12,"Augmentation - SUBTRANSMISSION LINES","Financial","BeX reports L02, 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. ","Direct costs from all Augex BeX report categories designated as being related to \"Sub-transmission lines\" are summed for the relevant regulatory year and input into the Direct Cost cells for the appropriate years.  Adjustments were made to exclude projects that were classified as Repex but include projects which incurred costs but are not yet completed.  Direct costs for identified projects are summed for each year are also input into the Direct Cost cells for the appropriate year.   Labour, contract and other costs were calculated  the same way."]
[null,2.12,"Augmentation - HV FEEDERS","Financial","BeX reports L02, 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. ","Direct costs from all Augex BeX report categories designated as being related to \"HV Feeders\" (excluding Distribution Subs) are summed for the relevant regulatory year and input into the Direct Cost cells for the appropriate years.  Adjustments were made to exclude projects that were classified as Repex but include projects which incurred costs but are not yet completed.  Direct costs for identified projects are summed for each year are also input into the Direct Cost cells for the appropriate year.   Labour, contract and other costs were calculated  the same way."]
[null,2.12,"Augmentation - DISTRIBUTION SUBSTATIONS","Financial","BeX reports L02, 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. ","An analysis of those QoS projects within budget category L09 was undertaken to identify those projects involving the purchase of pole or padmounted transformers was undertaken.  The costs of these projects has been summated to arrive at the value submitted.","All distribution substation works (either new or upgrade) are attributable either to connections, asset replacement or QoS activities.  Of these, only QoS falls within the Augex category.  Therefore , only QoS initiated projects have been examined in detail."]
[null,2.12,"Augmentation - LV FEEDERS","Financial","BeX reports L02, 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. ","Distribution substation and LV Feeder augmentation data is combined in BeX L09.  SAPN is unable to be seperately identify the groupings for Distribution substations and LV Feeders in this table so apportioning has been applied.\nThe cost data of LV projects from BeX L09 was arrived at through examination of those QoS projects contained within L09 BeX report.  This examination involved identifying those QoS projects which involved augmentation of the LV network.  Where found, a unit rate was used to apportion the cost of the LV expenditure relative to the other expenditure incurred on the overall project.","All LV feeder works (either new or upgrade) are attributable either to connections, asset replacement or QoS activities.  Of these, only QoS falls within the Augex category.  Therefore , only QoS initiated projects have been examined in detail."]
[null,2.12,"Augmentation - OTHER ASSETS","Financial","BeX reports L02, 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. ","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.  The costs contained within the Other Costs category relates to a short term strategic project aimed at improving network switching flexibility through the installation of HV switches at strategic locations across the network.  This expenditure is not expected to continue after the 2015/16 financial year and is therefore not a \"business as usual\" expenditure."]
[null,"Connections"]
[null,2.12,"Row 59 - Connections","Financial","Table 2.5.1","Estimated","Data is estimated as it was necessary to adjust source SAP reports to reported totals in Table 2.5.1.","SAP reports provided splits for materials, labour, contracts and other costs.  It was necessary to adjust these values to equate to the reported totals on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.5.1."]
[null,2.12,"Connections table","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. \nImmaterial reconciling differences have been apportioned to agree to the Annual RIN."]
[null,"Emergency Response"]
[null,2.12,"Row 60 to 61 - Emergency Response","Financial","Table 2.9.1","Estimated","Data is estimated as it was necessary to adjust source SAP reports to reported totals in Table 2.9.1","SAP reports provided splits for materials, labour, contracts and other costs.  It was necessary to adjust these values to equate to the reported totals on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.9.1.\n\"As 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,"IT & Communications"]
[null,2.12,"Row 76 - IT and Communications \n(Columns M to P)","Financial","Table 2.6.1 rows 14-19","Estimated","Data is estimated as it was necessary to adjust source SAP reports to reported totals in Table 2.6.1 rows 14-19","SAP reports provided splits for direct materials, direct labour, contracts and other costs.  It was necessary to adjust these values on a pro rata basis to equate to the total cost reported in Table 2.6.1 rows 14-19.","The total of all categories (including Related Party Contracts from Column Q) equals the total of costs reported in Table 2.6.1 rows 14-19."]
[null,2.12,"Column Q - Related Party Contract Expenditure","Financial","Related party costs as reported in the 2014/15 Annual RIN together with additional related party expenditure which did not meet the materiality threshold for disclosure in the Annual RIN.","Actual",null,"Values reported are as per data source.  Related Party values were deducted from other cost lines in Table 2.12 to ensure totals reconcile to each individual tab.",null,"Note, as SA Power Networks does not have a direct control relationship with any of our related parties, we are unable to obtain or report related party margin information in Table 2.12 Column R.  Should the AER require this information, this will need to be sought directly from our Related Parties. "]
[null,"Non-Network excl ICT"]
[null,2.12,"Row 77 to 79 - Non-Network (excluding ICT)","Financial","Table 2.6 rows 20-35","Actual/Estimated","Actual data relates to Fleet (Motor Vehicles and Other Vehicles) and Non Network Telecommunications. Other Non Network data is estimated as it was necessary to adjust source SAP reports to align to reported totals","SAP reports provided splits for materials, labour, contracts and other costs. For the estimated expenditure items it was necessary to adjust these values to equate to the reported totals on a pro-rata basis.","Refer methodology for row 16 - Vegetation Management  The total of all categories for each year equals the total of costs reported in Table 2.6.1 rows 20-33."]
[null,"Metering"]
[null,2.12,"Row 63 - Metering","Financial","Table 4.2.2","Estimated","Data is estimated as it was necessary to adjust source SAP reports to reported totals in Table 4.2.2","SAP reports provided splits for direct materials, direct labour, contracts and other costs.  It was necessary to adjust these values on a pro rata basis to equate to the total cost reported in Table 4.2.2.","The total of all categories equals the total of costs reported in Table 4.2.2 (excluding rows 12-14 (Meter Purchases) which are duplicated costs that have been included to comply with RIN requirements."]

{"sheet":"4.2 Metering","index":11,"n_rows":28,"n_cols":11,"rows_kept":28,"cut":false,"hidden":false,"merged":[[17,7,17,8],[15,7,15,8],[16,7,16,8],[10,7,10,8],[11,7,11,8],[12,7,12,8],[13,7,13,8],[14,7,14,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[27,7,27,8],[18,7,18,8],[19,7,19,8],[20,7,20,8],[21,7,21,8],[22,7,22,8],[23,7,23,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[6,7,6,8],[7,7,7,8],[8,7,8,8],[9,7,9,8],[5,7,5,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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,"All",null,null,null,null,"Where 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 as any other assumption would not make sense."]
[null,"4.2.1","All","Non-financial","The meter population quantities have been obtained from SAP BI reports, which tabulate quantities for all meter stock item codes from the CIS-OV database.  This meter population report has been analysed to determine the various meter types. ","Estimated","While most of this is purportedly \"Actual\" information, we have received conflicting meassages about its reliability. They acknowledge its not perfect but say its \"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. The different installation types require meters with specific characteristics to suit the applications so we can be confident that the information provided in the table is correct for each meter type, including the quantities of single phase and multi-phase meters. ",null,"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. ","Meter number data is as at 30 June in each year. Meter T1-4 include both alternative control services meters (those installed for free before July 2005) and negotiated distribution 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","Meter Purchases","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 Types 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,null,"These costs are shown for indicative purposes only. 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","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 Types 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,null,"These volumes are shown for indicative purposes only. Meters purchased are included in also New Meter Installation and Meter Replacement volumes."]
[null,"4.2.2","Meter Testing","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: Customer 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.  Meter Services - Meter Services reviewed their Annual Meter Testing Log to determine volumes and meter services timesheets to identify order numbers related to meter testing. Volumes were converted from calendar year to regulatory year basis by dividing by two and summing relevant half year data. Calender year cost data was extracted from SAP by order number and converted to regulatory year basis by dividing by two and summing relevant half year data. 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. This apportionment was done by assuming a 50:50 split.Metering Services (M11) metering work from 01-07-2014 to 31-06-2015 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.\n"]
[null,"4.2.2","Meter Testing","Non-financial","SAP/Metering 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: Customer Connect - Detailed volume and meter type data was extracted from SAP at the service order level to ascertain the volumes of relevant services. Meter Services - Meter Services reviewed their Annual Meter Testing Log to determine volumes. Volumes were converted from calendar year to regulatory year basis by dividing by two and summing relevant half year data. 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. This apportionment was done by assuming a 50:50 split.Metering Services (M11) metering work from 01-07-2014 to 31-06-2015 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","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: Customer 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. Meter Services - Meter services identified order numbers related to meter advice and investigations and extracted calendar year cost data from SAP by these order numbers. The calendar year data was converted to a regulatory year basis by dividing by two and summing relevant half year data. The volumes and split between Types 4, 5 and 6 was estimated by reference to the analysis of meter test volumes from Meter Services’ Annual Meter Testing Log as there was no other reasonable basis to use.  For Meter Investigations Type 5 and Meter Investigations Type 6 the split was estimated. Tasks volumes are not recorded; the number of tasks was based on the allocated budget allocation per task divided by total cost. "]
[null,"4.2.2","Meter Investigations","Non-financial","SAP/Metering 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: Customer 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. Meter Services - Meter Services reviewed their Annual Meter Testing Log to determine volumes. Volumes were converted from calendar year to regulatory year basis by dividing by two and summing relevant half year data. 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. This apportionment was done by assuming a 50:50 split.For Meter Investigations Type 5 and Meter Investigations Type 6 the split was estimated. Tasks volumes are not recorded; the number of tasks was based on the allocated budget allocation per task divided by total cost. "]
[null,"4.2.2","Scheduled meter reading","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 base 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.",null,"T5/T6 split is based on the relevant volumes"]
[null,"4.2.2","Scheduled meter reading","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 base 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 MR","Financial","Not reported",null,"Special MRs are Negotiated Services"]
[null,"4.2.2","Special MR","Non-financial","Not reported",null,"Special MRs are Negotiated Services"]
[null,"4.2.2","New Meter Installations","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.",null,"All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","New Meter Installations","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.",null,"All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Replacements","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: Customer 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. Meter Services - Network Management maintains an Excel database showing the monthly volumes and costs of meter replacements by meter type. The cost data held in that database is extracted from SAP by relevant order number. The monthly cost data was allocated to relevant regulatory years.Metering Services (M11) metering work from 01-07-2014 to 31-06-2015 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,"All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Replacements","Non-financial","SAP/Metering 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: Customer Connect - Detailed volume data was extracted from SAP at the service order level to ascertain the volumes of relevant services. Meter Services - Network Management maintains an Excel database showing the monthly volumes and costs of meter replacements by meter type. The monthly volume data was allocated to relevant regulatory years.Metering Services (M11) metering work from 01-07-2014 to 31-06-2015 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,"All data includes installations/replacements of some meters where SA Power Networks is not the Meter Provider."]
[null,"4.2.2","Meter Maintenance","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 identifed 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-2014 to 31-06-2015 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.\n",null,"The calendar year to financial year adjustment assumes that work undertaken evenly throughout the year."]
[null,"4.2.2","Meter Maintenance","Non-financial","Metering Services' spreadsheet \"Meter Test Summary\"","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-2014 to 31-06-2015 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,"The calendar year to financial year adjustment assumes that work undertaken evenly throughout the year."]
[null,"4.2.2","Remote MR (T4)","Financial","N/A",null,null,null,null,null,"We are not a T4 MDA"]
[null,"4.2.2","Remote Meter Reconfig (T4)","Financial","N/A",null,null,null,null,null,"We are not a T4 MDA"]
[null,"4.2.2","Other Metering","Financial","N/A",null,null,null,null,null,"There are no \"other metering costs\""]
[null,"4.2.2","IT infrastructure cap/opex (T4)","Financial","N/A",null,null,null,null,null,"Minor amount only reported as IT cost in Non-Network template"]
[null,"4.2.2","Comms infrastructure cap/opex (T4)","Financial","N/A",null,null,null,null,null,"We are not a T4 MDA"]

{"sheet":"5.2 Asset Age","index":12,"n_rows":26,"n_cols":10,"rows_kept":26,"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.1000000000000001,4,5,6,8,9,10,11]
[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","\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,"General Assumpution, Applies to the whole 5.2 Tab","Non-financial",null,"Estimated",null,"For entry into the RIN, as division by financial year is required however asset installation year was recorded as calendar year, the sum of half of each calendar year was used to populated each financial year. \nFor the asset population for the 14/15 financial year, we extracted the functional location for Reclosers,Sectionalizer,Pole top and Kioskmounted transformer, Groundlevel Switchgear,from SAP and added the repacements on top of them.\nFor poles the inventory data was used i.e the total numbers of poles manufactured during the 14/15 financial year.\nFor OH_Conductor and UG_Cables, the new OH_Conductor and UG_Cable added to our network was taken from GIS and the replacements were added on top as in GIS we cant figure out the replacements.",null,"Applies to Poles, Transformers Pole top and Kiosk mounted,Groundlevel Switchgear,Recloser,Sectionalizer"]
[null,"5.2.1","Others - DNSP defined","Non-financial",null,"Estimated","Unable to define asset catergories due to protection of template sheet. Used previous version of Catergory Analysis template to assign asset catergories - Refer to snapshot of screen print."]
[null,"5.2.1","5.2 Asset Age Profile\nPOLES\nROWS: (<=11kV STOBIE; >11kV & <= 33kV STOBIE; \n>33kV & <=66kV STOBIE; \n>66kV & <=132kV STOBIE) \nPole Refurbished;STOBIE\n\nCOLUMNS: (2014/15 - 1997/98)","Non-financial","Inventory data","Estimated","An estimate is required as actual data does not exist. Stobie poles have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/highest operating voltage of all poles. Hence an estimation is required.This data was only used from (2014/15 - 1997/98).","The 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 Notofication data was used for the plated poles since 2006","It was assumed that a poles 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\nThe total number of poles which are 745860, is all estimated based on the OH_Conductor Circuit length of the Network provided by GIS Group and then calculating by factoring the span length based on different volatge levels and bushfire zones and also factoring the duplication factor i.e (when there are different volatages on the same pole)"]
[null,"5.2.1","5.2 Asset Age Profile \nPole Top Structures\n (<=1kV; \n>1kV & <=kV; \n>11kV & <=22kV ; \n>22kV & <=66kV)\nCOLUMNS: (2012/13 - 1910/11)","Non-financial","AMP 3.1.06 - Overhead Line Components\nHistorical Database\nSAP","Estimated","An estimate is required as actual data does not exist. Pole Top Structures have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age of all Pole Top Structures. Hence an estimation is required."," - The main part of Pole Top Structures (Crossarms, Insulators, Joints and Taps, and other minor assessories) were obtained from historical database\n- other part of Pole Top Structures (OH Load switches, Disconnect Fuses, Fuse Bases, Air Breaks, Load switch Fuses) were obtained from SAP\n- The AMP assists to get The ratio of Insulators of different voltage levels, then The ratio was applied to The total count to break all assets down to nominated voltage levels"," - Assume ratio of insulator of different voltage levels represents The ratios for other Pole Top Structure assets\n- It is assumed that The age profile of The known population provides a fair representation of The total population."]
[null,"5.2.1","5.2 Asset Age Profile\nPOLES\nROWS: (<=11kV STOBIE; \n>11kV & <= 33kV STOBIE; \n>33kV & <=66kV STOBIE; \n>66kV & <=132kV STOBIE) \nPole Refurbished;STOBIE\nCOLUMNS: (1996/97-1910/11)","Non-financial","CBRM data, Pole Production data,SAP Data","Estimated","An estimate is required as actual data does not exist. Stobie poles have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact number/age/highest operating voltage of all poles. Hence an estimation is required.","The population of stobie poles was estimated based on the route length of the network and the average span length based on the lowest operating voltage for that feeder. These calculations were performed based on information available in GIS. The estimated number of poles is 740856. From inventory data it was found that 26794 poles were produced between 1997 and 2013. The remaining 714062 poles were produced before 1997.\n\nPole production data was used to create an age profile and therefore obtain proportions of the pole population produced each year between 1932 and 1997. It was assumed that all poles produced after 1970 are still in service. A linearly decreasing replacement rate was then applied to poles produced from 1932 to 1970 (i.e. no poles replaced installed in 1970 have been replaced and highest percentage of poles installed in 1932 have been replaced).\n\nCBRM data were used to produce a voltage profile per year and hence obtain the proportions of each voltage poles produced each year.\n\nno data is available on Pole Refurbishment before 2006\n\nThese proportions were then scaled to meet the 694834 poles estimated to be produced between 1932 and 1997 based on the previously produced age profile from production data.","It was assumed that all poles installed before 1932 have been replaced.\n\nit was assumed all poles produced since 1970 are still in service.\n\nIt was assumed that the age profile obtained from pole production data is a fair representation of the current population.\n\nIt was assumed that the CBRM data provides a fair representation of the voltages for the pole population."]
[null,"5.2.1","5.2 Asset Age Profile\nOVERHEAD CONDUCTORS\nROWS: (<=1kV; \n>1kV & <=kV; \n>11kV & <=22kV SWER; \n>22kV & <=66kV)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","CBRM data\nSAP data\nProject data","Estimated","An estimate is required as actual data does not exist. OH conductor has been used extensively throughout the distribution network. Data 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.","The length reported for over head conductors is the conductor length.for 11kv,33kv,66kv and 7.6 kv the conductor length =3*route length,for 19kv SWER Conductor length= route length,for LV conductor length=4* route length\nThe data used for CBRM was complete for the vast majority of conductor sections. Some conductors were missing an age. The age of those conductors without an age was evenly distributed between 1954 and 1990 as this is when the majority of conductor was strung out.","It is assumed that the age profile of the known population provides a fair representation of the total population.\n\nFor 2008/2009 – 2012/2013, we assume the amount of overhead conductor got replaced is equal to the amount of conductor got installed.For 2013/14-2014/15 we have used figures from GIS Line Statistics that how much conductor was added for different voltages."]
[null,"5.2.1","5.2 Asset Age Profile\nUNDERGROUND CABLES\nROWS: (<=1kV)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","Accounting records and GIS","Estimated","An estimate is required as actual data does not exist. LV underground cables have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact length/age/highest operating voltage of all LV underground cables. Hence an estimation is required.","The primary source of information for this analysis was accounting records. Where accounting records was unavailable information from GIS was used. Where information from GIS was also unavailable then the average age of the feeder was used to estimate the age of the cable.","It is assumed that the year commissioned is equal to the year installed.For 2013/14-2014/15 we have used figures from GIS Line Statistics that how much cable was added for low voltages."]
[null,"5.2.1","5.2 Asset Age Profile\nUNDERGROUND CABLES\nROWS: (>1kV & <=11kV; \n>11kV & <22kV; \n>22kV & <=33kV; \n>33kV & <=66kV; \n>66kV & <=132kV)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","Accounting records and GIS","Estimated","An estimate is required as actual data does not exist. HV underground cables have been used extensively throughout the distribution network. Data capture programs have not yet been able to measure the exact length/age/highest operating voltage of all HV underground cables. Hence an estimation is required.","The most accurate source of information was determined to be the construction drawings available from GIS. For this reason where possible the date from drawings were used. For the majority of feeder sections no construction drawings were available. For these sections of feeder accounting records were used to determine the age of the cable. The age of the cable was determined by the year that section of feeder was commissioned. Accounting records contain all cables used on feeder sections however only underground cable types were considered. For several sections of cables, the average feeder age was used to determine the approximate year it was installed. One section of cable the average age of its feeder was unknown and hence the average age of surrounding feeders was used to estimate its age.","It is assumed that the year commissioned is equal to the year installed.For 2013/14-2014/15 we have used figures from GIS Line Statistics that how much cable was added for different voltages."]
[null,"5.2.1","5.2 Asset Age Profile\nSERVICE LINES\nROWS: (<= 1kV RESIDENTIAL SIMPLE TYPE; \n<= 1kV COMMERCIAL & INDUSTRIAL COMPLEX TYPE)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","CIS/OV and GIS","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 .","It is assumed every customer has a service line however all flats/units have only one service line for the group.\n\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.\n\nIt is assumed that all residential connections are of simple type.\n\nIt is assumed that all commercial and industrial connections are of complex type"]
[null,"5.2.1","5.2 Asset Age Profile\nSERVICE LINES\nROWS:\n? ? 11 KV ; RESIDENTIAL ; SIMPLE TYPE \n? ? 11 KV ; COMMERCIAL & INDUSTRIAL ; COMPLEX TYPE \n> 22 KV & < ? 33 KV ; COMMERCIAL & INDUSTRIAL  \n> 33 KV & < ? 66 KV ; COMMERCIAL & INDUSTRIAL  \n\nCOLUMNS: (2014/15 - 1910/11)","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/voltage of all service lines. Hence an estimation is required.","Customer information was extracted from CIS/OV and cross referenced with NES and filtered for HV customers only. The age of the service line was based on the minimum installation date.","It is assumed that HV customers are supplied at the feeder voltage.\n\nIt is assumed that all HV connections are of commercial and industrial type and are of complex connection complexity."]
[null,"5.2.1","5.2 Asset Age Profile\nTRANSFORMERS\nROWS: (POLE MOUNTED <?22kV <?60kVA SINGLE PHASE;\nPOLE MOUNTED <?22kV  >60kVA and <?600kVA SINGLE PHASE;\nPOLE MOUNTED <?22kV  >600kVA SINGLE PHASE;\nPOLE MOUNTED <?22kV  <?60kVA MULTIPLE PHASE;\nPOLE MOUNTED <?22kV  >60kVA and <?600kVA MULTIPLE PHASE;\nPOLE MOUNTED <?22kV  >600kVA MULTIPLE PHASE;\nPOLE MOUNTED >22kV  <?60kVA \nPOLE MOUNTED >22kV  >60kVA and <?600 kVA\nPOLE MOUNTED >22kV  >600 KVA \nPOLE MOUNTED >22kV  <?60 kVA\nPOLE MOUNTED >22kV  >60kVA and <?600KVA\nPOLE MOUNTED >22 kV  >600KVA\nKIOSK MOUNTED <?22kV  <?60kVA SINGLE PHASE;\nKIOSK MOUNTED <?22kV  >60kVA and <?600kVA SINGLE PHASE;\nKIOSK MOUNTED <?22kV  >600kVA SINGLE PHASE;\nKIOSK MOUNTED <?22kV  <?60kVA MULTIPLE PHASE;\nKIOSK MOUNTED <?22kV  >60kVA and <?600kVA MULTIPLE PHASE;\nKIOSK MOUNTED <?22kV  >600kVA MULTIPLE PHASE;\nKIOSK MOUNTED >22 kV  <?60kVA\nKIOSK MOUNTED >22kV  >60kVA and <?600kVA\nKIOSK MOUNTED >22kV  >600KVA\nKIOSK MOUNTED >22kV  <?60kVA\nKIOSK MOUNTED >22 kV  >60kVA and <?600KVA\nKIOSK MOUNTED >22 kV  >600 KVA\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ?22kV  <?60kVA SINGLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ?22kV  >60kVA  and <?600kVA SINGLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ?22kV  >600kVA SINGLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ?22kV  <?60kVA MULTIPLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED <22kV  >60kVA  and <?600kVa MULTIPLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED ?22 kV  >600kVA MULTIPLE PHASE;\nGROUND OUTDOOR / INDOOR CHAMBER MOUNTED >?22 kV & <?33kV  <?15MVA)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","SAP and Voltage Regulator AMP","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.\n\nPLEASE NOTE THAT:\nFor line 76-81, 88-93, due to the duplication of names, we have assumed the first 3 of duplications as SINGLE PHASE TF and the last 3 of duplications as MULTIPLE PHASE TF","Transformer data was extracted from SAP however was not complete as for the requirements for the RIN. Firstly transformer type was determined by the prefix of the functional location. Then information about transformer type was recorded in three different fields, this was condensed into one field, this information was used where a type could not be determined by FLOC prefix. \n\nSome records had their date labelled as inaccurate these were installed dates before 1930 and those after 2014.\n\nDustbin transformers with unknown phasing were labelled as 1PH. In addition, PH/E and SWER phasing was labelled as 1PH.\n\nDates of purchase were used where available in absence of installation date.\n\nFor MK7, MK6 and MK5 pad mount transformers with unknown age their vintage was used to estimate their age.\n\nFor feeders without an installation date their age was estimated to be that of the average feeder age.\n\nFor transformers on feeders with unknown average age the age of those transformers was estimated based on their equipment ID number and the ID of transformers with known age on the same feeder. \n\nFor transformers without equipment numbers their age was estimated based on the age of surrounding feeders.\n\nThe remaining transformers were the feeder was also unknown was allocated an installation date which represented the greater population, these transformers were evenly distributed between 1970 and 2005.\n\nSimilarly those transformers without a type, operating voltage or phasing were distributed to reflect the greater population.\n\nFor entry into the RIN, as division by financial year is required however asset installation year was recorded as calendar year, the sum of half of each calendar year was used to populated each financial year. ","It was assumed that any transformers recorded as being installed before 1930 were incorrect. Further assumptions were made to correctly label these.\n\nDustbin style transformers of unknown phasing were labelled as being 1PH as this was the majority phasing of dustbin transformers. Very few dustbin transformers are 3PH.\n\nPH/E and SWER phasing was categorised as 1PH.\n\nDate of purchase was approximately equal to the installation date.\n\nEquipment ID numbers were issued in approximate chronological order.\n\nFor transformers without a voltage it was assumed their maximum operating voltage was that of the feeder.\n\nIt was assumed the known population fairly represents the total population"]
[null,"5.2.1","5.2 Asset Age Profile\nSWITCH GEAR\nROWS: >= 11 kV & < ? 22 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical) \n> 22 kV & < ? 33 kV  ; LOAD BREAK SWITCH; GROUND LEVEL (Switching Cubical)\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","GIS, Switching diagrams, accounting records and  Various databases provided by Doug Lorimer (Ground Level switch gear asset expert)\n\nFor Databases provided follow link in comments column","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.","Databases provided, formed a starting point for the analysis. All switch gear was then confirmed by either GIS or switching diagrams. For new switch gear not available in the provided databases accounting records were used to provide number, age and voltage. \n\nFor English electric, South Wales, Statter, Yorkshire and GEC/AEI type switch gear the exact installation dates are unknown however it is known that those installed in Elizabeth were done so between 1956 and 1969 while those installed in the CBD were installed before 1974. Therefore these items of switch gear had their age distributed between 1956-1969 and 1956 and 1974 respectively.\n\nFor ETSA \"D\" type switches it is known that they were commissioned between 1973 and 1976. Therefore they were estimated to have been installed in 1976.\n\nFor Brown Boveri FN-12, Brown Boveri NL-12 and Brown Boveri RGB-12 did not have known installation dates therefore their age was estimated based on their vintage. It was estimated that FN-12 switch gear were installed in 1981, NL-12 switchgear was installed in 1986 and RGB switch gear was installed in 1981.\n\nFor Krone switch gear the installation date was readily available.\n\nF&G switch gear did not have readily available instillation dates hence their instillation date was estimated based on their vintage. F&G GA24 were estimated to be installed in 1992. F&G GAC were estimated to be installed in 2005. F&G GC10 were estimated to be installed in 1999. For unidentified F&G switches they were estimated to be installed in 2000.\n\nMerlin Gerin switch gear did not have readily available instillation dates hence their instillation date was estimated based on their vintage. Type 1 switches were estimated to be installed in 1997. Type 2 switches were estimated to be installed in 2006.\n\nFor the majority of ABB Safelink and Safering switches the installation year was known. For those without a installation date it was a estimated that they were installed in 2009.\n\nFor S&C Vista switches the exact installation date was unknown therefore the switch vintage was used to estimate its age. These switches were estimated to be installed in 2010.\n\nFor Holec Xiria switches their instillation date was readily available.\n\nFor MK6 and MK7 switch gear the majority of installation dates was readily available. For MK6 switches without an installation date it was assumed that they were installed in 2006. For MK7 switches without an installation date it was estimated that they were installed in 2012.","It is assumed that the vintage mean of a vintage for a switch type provides a fair representation of the actual age of that switch population.\n\nIt is assumed that the purchase date is approximately equal to the installation date."]
[null,"5.2.1","5.2 Asset Age Profile\nSWITCH GEAR\nROWS: (RECLOSER )\nCOLUMNS: (2014/15 - 1910/11)","Non-financial","SAP, PSS6 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","5.2 Asset Age Profile\nSWITCH GEAR\nROWS: (<=11kV SECTIONALISERS; \n>11KV & <=22kV SECTIONALISERS)\nCOLUMNS: (2014/15 - 1910/11)","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","5.2 Asset Age Profile \nEconomic Life  (MEAN & STANDARD DEVIATION)","Non-financial","2.2 Repex tab and 5.5 Asset age profile data ,SME Enginnering Judgment and manufacturers estimated standard life","Estimated",null,"As there can be so many different definitions for the asset economic/mean life i.e. the average inservice life of an asset .we calculated the economic /mean life based on the average number of replacements during the last 5 years and then calibrating the Repex Model using those average replacement volume to get the calibrated Economic/mean life.\nAs the repex model calibrated economic/mean life is based on historical replacement volumes so for the asset categories that have been historically just replaced on failure the calibrated repex model  would have a much higher economic/mean than what it is in reality, so therefore we have used the calibrated repex model mean/economic life where the mean/economic life makes sense for other assets we have used the life of asset upon SA Power Network actual experience and referring to SME's."]
[null,"5.2.1","SWITCHGEAR / CIRCUIT BREAKERS","Non-financial","SAP","Actual",null,"1. Start with Original CB-SAP-Working-Data-2015.07.21 Workbook to capture all changes in SAP from 7/2014 data (2509 entries)\n2. Remove equipment records against SSD992 & SSD991 FLOCs - scrap & stock CBs (2409 entries remaining)\n3. Remove LV breakers (0.4kV Primary Voltages (V)) (1973 entries remaining)\n4. Remove Unregulated Assets (1966 entries remaining)\n5. Remove duplicate equipment records (shown as duplicated FLOC Descriptions) - error introduced through SAP data changes (1943 entries)\n6. Combine '21.07.2015 SAP' records with '2014 RIN Age Profile' records and remove duplicate equipment numbers to show all changes between 2014 and current data (78 Records Remaining)\n7. Updated missing Data (voltage/purchase dates) from various sources (plant running sheets, design drawings, photos of nameplates etc)\n8. For each asset type, identify equipment record changes from 2014 to 2015:\n  -  new asset (new installation/equipment record) - to be added to 2014 age profile data\n  -  removed asset (decommissioned/removed equipment record) - to be removed from 2014 age profile data\n9. For each asset type, identify asset movements between 7/2014 and 7/2015 not captured in SAP:\n  - Collected Asset Movement Forms, capital projects recorded in SAP L14/L54/L13 work centres, SAP notifications and failure records\n  - Movement of HSS Horizon CBs and 11kV CB refurbishments not fully captured in processed data as they do not significantly affect the age profile\n  - Oil Disconnect and Air Disconnect devices have been excluded from 2015 data for consistency with 2014 data.\n10. For each asset movement, determine the corresponding RIN Category (based on operating voltage, normal rating etc) and financial year appropriate to the asset.\n11. Summarise net movements for each RIN category and financial year (i.e. 1 CB out & 1 CB in = 0 movements in that year)\n12. Update 5.2 Asset Age Profile (2013-14) data with net changes for each asset category. Summary Age profile as of 7/2015 presented in 5.2 Asset Age Profile (2014-15) tab.","Equipment purchased in any calendar year is recorded against the financial year beginning 1 July of that year (e.g. a purchase date of any month in 1966 will be recorded in the 1966/67 financial year)."]
[null,"5.2.1","SWITCHGEAR / SWITCHES","Non-financial","SAP","Actual",null,"1. Start with Original SW-SAP-Working-Data-2015.07.22.xlsx Workbook to capture all changes in SAP from 7/2014 data (5482 entries)\n2. Remove equipment in SSD992 & SSD991 FLOCs - scrap & stock SWs (4727 entries remaining)\n3. Remove LV switches (0.4kV & 0.23kV Operating voltages) (4688 entries remaining)\n4. Remove Unregulated 132kV Assets  (4684 entries remaining)\n5. Remove Fuses from List - assets with a  object type of \"SW_F\" (4289 entries remaining)\n6. Remove (integral) earth switches from List - assets with a  object type of \"SW_E\" (4075 entries remaining)\n7. Remove SAP equipment record errors from List (4068 entries remining)\n8. Combine '21.07.2015 SAP' records with '2014 RIN Age Profile' records and remove duplicate equipment numbers to show all changes between 2014 and current data (328 Records Remaining)\n9. Updated missing Data (voltage/purchase dates) where possible - from various sources (plant running sheets, design drawings, photos of nameplates etc)\n10. For each asset type, identify equipment record changes from 2014 to 2015:\n  -  new asset (new installation/equipment record) - to be added to 2014 age profile data\n  -  removed asset (decommissioned/removed equipment record) - to be removed from 2014 age profile data\n11. For each asset type, identify asset movements between 7/2014 and 7/2015 not captured in SAP:\n  - Collected Asset Movement Forms, capital projects recorded in SAP L14/L54/L13 work centres, SAP notifications and failure records\n  - Oil Disconnect and Air Disconnect devices have been excluded from 2015 data for consistency with 2014 data.\n12. For each asset movement, determine the corresponding RIN Category (based on operating voltage, normal rating etc) and financial year appropriate to the asset.\n13. Summarise net movements for each RIN category and financial year (i.e. 1 CB out & 1 CB in = 0 movements in that year)\n14. Update 5.2 Asset Age Profile (2013-14) data with net changes for each asset category. Summary Age profile as of 7/2015 presented in 5.2 Asset Age Profile (2014-15) tab.","Equipment purchased in any calendar year is recorded against the financial year beginning 1 July of that year (e.g. a purchase date of any month in 1966 will be recorded in the 1966/67 financial year)."]
[null,"5.2.1","TRANSFORMERS","Non-financial","SAP","Actual",null,"1. Start with Original TF SAP-Working-Data-2015.07.22.xlsx Workbook to capture all changes in SAP from 7/2014 data (1642 entries) \n2. Remove equipment records against SSD992 & SSD991 FLOCs - scrap & stock TFs & TFs not allocated to Sub FLOCS (1043 entries remaining)\n3. Remove station transformers - Sub-Class 'Transformer - Station/Aux' + FLOCs containing \"ST\" (778 entries remaining)\n4. Remove Single Phase Regulators - Sub-Class 'Regulator - Single Phase' (706 entries remaining)\n5. Remove Unregulated Assets  (696 entries remaining)\n6. Combine '21.07.2015 SAP' records with '2014 RIN Age Profile' records and remove duplicate equipment numbers to show all changes between 2014 and current SAP data (12 Records Remaining)\n7. Updated missing Data (voltage/purchase dates) from various sources (plant running sheets, design drawings, photos of nameplates etc)\n8. For each asset type, identify equipment record changes from 2014 to 2015:\n  -  new asset (new installation/equipment record) - to be added to 2014 age profile data\n  -  removed asset (decommissioned/removed equipment record) - to be removed from 2014 age profile data\n9. For each asset type, identify asset movements between 7/2014 and 7/2015 not captured in SAP:\n  - Collected Asset Movement Forms, capital projects recorded in SAP L14/L54/L13 work centres, SAP notifications and failure records\n  - Oil Disconnect and Air Disconnect devices have been excluded from 2015 data for consistency with 2014 data.\n10. For each asset movement, determine the corresponding RIN Category (based on operating voltage, normal rating etc) and financial year appropriate to the asset.\n11. Summarise net movements for each RIN category and financial year (i.e. 1 CB out & 1 CB in = 0 movements in that year)\n12. Update 5.2 Asset Age Profile (2013-14) data with net changes for each asset category. Summary Age profile as of 7/2015 presented in 5.2 Asset Age Profile (2014-15) tab.K15","Equipment purchased in any calendar year is recorded against the financial year beginning 1 July of that year (e.g. a purchase date of any month in 1966 will be recorded in the 1966/67 financial year)."]
[null,5.2,"Row SCADA, network control and protection systems - Communications 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 this current years entries are correct","Went through list of projects for the eyear and entered installed items for each project","Assumptions from old equipment, not for this years installations.All communication linear asset section  lengths are reported in KM"]
[null,5.2,"SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS - Field Device","Non-financial","2009-2015 Protection and Control AMP","Estimated","Actual installation date of every asset is not known.","Total number of each asset type and period of installation is known. The installation year of each relay model is averaged over the known period of installation.\n\nThe mean and standard deviation for protection relay economic life is calculated based on values for the three relay classes published in section 4.6 of the 2009-2015 Protection and Control AMP","AMP age profile reflects approximately the actual age profile"]
[null,"5.2.1","SCADA, NETWORK CONTROL AND PROTECTION SYSTEMS:\nSCADA ASSETS","Non-financial","SCADA configuration files and \nSCADA design/secondary drawings","Actual","N/A","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.","N/A","SCADA assets itemised to highlight the different types of assets and their proportions on the network.SCADA assets i.e. RTUs were listed in the 'Other' Asset Category (row 130), the listed fields such as Master Station and field devices do not meet the business definition of SCADA devices isuch as RTUs and TDUs. Because the section also covers protection, it is assumed that 'Field Devices' relate to protection devices, while master station refer to the office HMI i.e. control system which has been captured in 'non-network'. "]

{"sheet":"5.3 Max Demand Network Lvl","index":13,"n_rows":12,"n_cols":11,"rows_kept":12,"cut":false,"hidden":false,"merged":[[9,7,9,8],[10,7,10,8],[11,7,11,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[5,7,5,8],[5,10,8,10],[6,7,6,8],[7,7,7,8],[8,7,8,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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 Network coincident MD","Non-financial","Metered data stored in NESS","Actual",null,"Maximum demand observed in 12 month period of metered data",null,null,"SA Power Networks has prepared this data to comply with the RIN.  However, we have also prepared alternative data and basis of preparation (both shown in the next tab of this document) which we believe provides a better indication of MD trends on SA Power Networks' system."]
[null,"5.3.1","Date MD occurred","Non-financial","Metered data stored in NESS","Actual",null,"Date of day when maximum demand occuurred"]
[null,"5.3.1","Half-hour time period MD occurred","Non-financial","Metered data stored in NESS","Actual",null,"Half-hour when maximum demand occuurred"]
[null,"5.3.1","Winter/Summer peaking","Non-financial","Metered data stored in NESS","Actual",null,"Season when maximum demand occurred (always Summer)"]
[null,"5.3.1","Embedded Generation","Non-financial","Metered data stored in NESS","Actual",null,"Summated demand of all metered embedded generation that exports into SA Power Networks grid (Major Embedded and Gross PV Export)",null,"The embedded generators include:","Note: There is a one and a half-hour difference between the time of the system maximum demand recorded in tab 5.3 and the time of the coincident maximum demand recorded in tab 5.4.  There was an update to the PV data after tab 5.4 was prepared which altered the aggregate system maximum demand by only a few MW but shifted the time of the system maximum demand by one and a half-hours (from 4pm to 2.30pm local time). Tab 5.3 was revised to include the latest PV data and the system maximum demand, and the time it occurred, were updated accordingly. We have not revised all the substation coincident maximum demands in tab 5.4 for this one and a half-hour shift as it is not considered material at the spatial level."]
[null,null,null,null,null,null,null,null,null,"Canunda Wind Farm","Non-Scheduled"]
[null,null,null,null,null,null,null,null,null,"Kimberley Clark Australia","Exempt from registration"]

{"sheet":"5.3 MD Alternative","index":14,"n_rows":33,"n_cols":15,"rows_kept":33,"cut":false,"hidden":false,"merged":[[42,7,42,8],[43,7,43,8],[44,7,44,8],[45,7,45,8],[46,7,46,8],[41,7,41,8],[30,7,30,8],[31,7,31,8],[32,7,32,8],[33,7,33,8],[34,7,34,8],[35,7,35,8],[36,7,36,8],[37,7,37,8],[38,7,38,8],[39,7,39,8],[40,7,40,8],[22,1,22,3],[22,4,22,10],[23,7,23,8],[24,7,24,8],[25,7,25,8],[26,7,26,8],[26,10,32,10],[27,7,27,8],[28,7,28,8],[29,7,29,8]]}
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,null,null,null,null,"Alternative TABLE 5.3.1 - RAW AND WEATHER CORRECTED COINCIDENT MD AT NETWORK LEVEL (SUMMED AT TRANSMISSION CONNECTION POINT)"]
[]
[]
[null,null,null,null,null,null,null,"UNIT","2008/09","2009/10","2010/11","2011/12","2012/13","2013/14","2014/15"]
[null,null,null,null,null,null,"RAW NETWORK COINCIDENT MD","MW",2975,2802,2897,2577,2738,2986,2203]
[null,null,null,null,null,null,"DATE MD OCCURRED ",null,"2009-01-29","2010-01-11","2011-01-31","2012-01-23","2013-01-17","2014-01-16","2014-01-17"]
[null,null,null,null,null,null,"HALF HOUR TIME PERIOD MD OCCURRED",null,"1830 EST","1830 EST","1830 EST","1830 EST","1830 EST","1830 EST","1830 EST"]
[null,null,null,null,null,null,"WINTER/SUMMER PEAKING",null,"SUMMER","SUMMER","SUMMER","SUMMER","SUMMER","SUMMER","SUMMER"]
[null,null,null,null,null,null,"EMBEDDED GENERATION","MW",31.1,38.700000000000003,81.900000000000006,65.7,69.7,82,17]
[null,null,null,null,null,null,"WEATHER CORRECTED (10% POE) NETWORK COINCIDENT MD","MW",2819,2900,2843,2796,2858,2822,2617]
[null,null,null,null,null,null,"WEATHER CORRECTED (50% POE) NETWORK COINCIDENT MD","MW",2657,2718,2671,2625,2701,2657,2460]
[]
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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 Network coincident MD","Non-financial","1. ElectraNet metered TNI data\n2. Major customers NMI data (net out)\n3. Embedded Generation NMI data (net in)\n4. PV Gross output sample NMI meters \n5. Installed effective capacity of PV (by month)\n6. Kent Town Weather bureau","Estimated","While metered data and information from Kent Town weather bureau are actual data we only have a sample of actual metered PV data and need to scale this up to estimate total PV generation to then calculate what is the demand net of all generation (including the estimated PV generation).  ","Determine SAPN net demand at TCP by combining ElectraNet embedded generation and PV generation\nConsider the following two demands separately:-\n.  Major customers (because these are connected to the edge of our system and respond to price and not weather)\n.  All other demand (drives the use of the majority of network and is primarily weather sensitive)",null,"1. Schedule of installed PV systems (81% of approvals) reflects the effective installed capacity.\n2. A small sample of PV systems reflects the typical operation of all PV systems.\n3. Losses on PV systems are approximately 8%.\n4. No adjustment for losses on major customers or embedded generation as it is minimal.\n5. All quantities are effectively at TCP.","This information is non-complaint with the RIN but, we believe, provides a better indication of MD trends on the SA Power Networks' system."]
[null,"5.3.1","Date MD occurred","Non-financial","Metered data as above","Actual",null,"Date that highest work-day demand occurred"]
[null,"5.3.1","Half-hour time period MD occurred","Non-financial","Metered data as above","Actual",null,"Half-hour time period that highest work-day demand occurred"]
[null,"5.3.1","Winter/Summer peaking","Non-financial","Metered data as above","Actual",null,"Season that highest work-day demand occurred (always Summer)"]
[null,"5.3.1","Embedded Generation","Non-financial","1. Embedded generation NMI data\n2. The (entire) sample of PV systems with Type 4 metering and configured to record gross generation","Estimated","Only a small population of PV systems have Type 4 metering configured to record gross generation and these outputs are scaled to estimate total PV generation","Metered PV sample output is scaled up to the effective installed PV capacity\nPV generation lossses are subtracted.\nOther metered embedded generation is added"]
[null,"5.3.1","10%PoE coincident MD","Non-financial","Metered data as above","Estimated","While metered data and information from Kent Town weather bureau are actual data we only have a sample of actual metered PV data and need to scale this up to estimate total PV generation to then calculate what is the demand net of all generation (including the estimated PV generation).  ","Interpolate / extrapolate actual demands on severe weather days using a temperature index set to reflect 10% and 50% PoE.\nExclude the most extreme days (eg days more than 5% PoE) as the demand response to temperature is not linear at the extreme.",null,"1. Schedule of installed PV systems (81% of approvals) reflects the effective installed capacity.\n2. A small sample of PV systems reflects the typical operation of all PV systems.\n3. Losses on PV systems are approximately 8%.\n4. No adjustment for losses on major customers or embedded generation as it is minimal.\n5. All quantities are effectively at TCP.\n6. For major customers (no temperature involved) the maximum work day demand after diversity in February is the 10% PoE and the 50% PoE.  This load is <7% of MD"]
[null,"5.3.1","50%PoE coincident MD","Non-financial","Metered data as above","Estimated","While metered data and information from Kent Town weather bureau are actual data we only have a sample of actual metered PV data and need to scale this up to estimate total PV generation to then calculate what is the demand net of all generation (including the estimated PV generation).  ","Interpolate / extrapolate actual demands on severe weather days using a temperature index set to reflect 10% and 50% PoE.\nExclude the most extreme days (eg days more than 5% PoE) as the demand response to temperature is not linear at the extreme.",null,"1. Schedule of installed PV systems (81% of approvals) reflects the effective installed capacity.\n2. A small sample of PV systems reflects the typical operation of all PV systems.\n3. Losses on PV systems are approximately 8%.\n4. No adjustment for losses on major customers or embedded generation as it is minimal.\n5. All quantities are effectively at TCP.\n6. For major customers (no temperature involved) the maximum work day demand after diversity in February is the 10% PoE and the 50% PoE.  This load is <7% of MD"]

{"sheet":"5.4 Max Dem & Utilise - Spatial","index":15,"n_rows":8,"n_cols":10,"rows_kept":8,"cut":false,"hidden":false,"merged":[[5,1,5,9],[0,1,0,3],[0,4,0,9],[4,1,4,9],[7,8,8,8],[7,9,8,9],[7,1,8,1],[7,2,8,2],[7,3,8,3],[7,4,8,4],[7,5,8,5],[7,6,8,6]]}
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,10,11]
[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","\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 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 or 33kV). 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\nPoE: Probability of Exceedance\nPV: Photo Voltaic"]
[null,"5.4.1","All","Non-financial","Historical SA Power Networks Databases (10% PoE and 50% PoE  MASTER Load Forecasts 2014, MASTER Substation Transformer Ratings), Demand Forecast Tool Database established by ACIL Allen, PV Installed Capacity for March 2014 and March 2015 Databases, ACIL Allen created PV Calculator, National Electricity Forecasting Report 2015","Estimated","1. For continuous metered sites, weather corrected demand forecasts provided are statistically calculated from 2014/15 measured demand and temperatures in combination with a simulation approach to generate a long run distribution of maximum demands from which PoE demands are obtained. \n2. For non-continuous metered sites, very limited demand records are available and there is no ability to refer to retrospective “snapshot” of Zone Substation peak demand for the 2014/15 summer.\nDemand records are obtained by installing temporary demand loggers for approximately 6 weeks 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.\n3. 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.\n4. Other model adjustments (spot loads and transfers) are not metered values.\n","The following steps were undertaken to compile the data submitted:\n\n1. Starting with substation ratings, normal published cyclic ratings were extracted and collated from the following SA Power Networks’ databases:\n• Sub-transmission Substations – Connection Point Capacity V Moderate 2012/13 Load Forecast.\n• Zone Substations – MASTER Substation Transformer Ratings.\n\n2. 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 are used for forecasting purposes and determining the timing for site upgrades due to the lack of spare available capacity.\n\n3. For continuous metered sites please refer to Maximum Demand Forecast Tool (Methodology and Users Guide for SA Power Networks Maximum Demand Forecasting Tool) document for detailed explanation of the methodology used for SA Power Networks’ demand forecasts.\n\nCoincident reconciled and non-coincident reconciled 10 POE and 50 POE forecasts (MW and MVA) were extracted and collated from the Demand Forecast Tool Database.  The tabs of interest include Coincident Reconciled and Non-coincident.\n\n4. For non-continuous metered Zone Substations reported data was obtained and extrapolated simplistically from SA Power Networks historically produced 2013 Zone Substation Forecasts. \n\n• Assumed ratio measured peak and 10 POE is a factor of 0.95 (10 POE = 0.95 x peak).\n• Assumed ratio 50 POE and 10 POE is a factor of 0.9 (50 POE = 0.9 x 10 POE).\n\n5. Embedded Gens (PV) installed capacity per Substation for March 2014 and March 2015 was collated where available.  Using the ACIL Allen PV Calculator, an estimated amount of PV was calculated for each Sub-transmission and Zone Substation based on the time of day of the assigned peak. \n\nEmbedded Gens (other) were included only when the generator operation was consistent throughout the summer and was not operating due to market or weather conditions.  Sites include Seaford, Metro South Region, Port Adelaide North, Kilburn, Metro West Region, Prospect, Metro East Region, Bolivar and Metro North Region.  The amount of generation plus PV for these sites has been collated in the data submitted.\n\n","In compiling the data contained within this table, the following assumptions were made:\n1. Sub-transmission Substation Ratings are the ratings as provided by the transformer owner (ElectraNet).  Ratings for the following sites were not available to SA Power Networks, therefore nameplate ratings were used:  Dorrien, Hummocks, Waterloo and Whyalla Terminal.\n2. Coincident refers to the time of System Peak (SA Power Networks demand only, excludes ElectraNet direct connected customers).  \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.\n4. For non-continuous metered Zone Substations, the time of day peak is assumed to be when the System demand peaks (ie: coincident and non-coincident peaks are at the same time).\n5. For reconciliation purposes, Sub-transmission Substations were reconciled to the trend of the State demand (essentially flat) as per AEMO’s National Electricity Forecasting Report 2015.  Zone Substations were then reconciled to the corresponding reconciled Sub-transmission Substation trend value.\n6. Where actual demand data is only available in Amps, MW and MVA values have been determined assuming nominal voltage and the PF of the upstream Sub-transmission Substation.\n7. Model Parameters:\n• Major customers, spot loads and transfers – no adjustment factor between 10 POE and 50 POE forecasts.\n\n","Note: There is a one and a half-hour difference between the time of the system maximum demand recorded in tab 5.3 and the time of the coincident maximum demand recorded in tab 5.4.  There was an update to the PV data after tab 5.4 was prepared which altered the aggregate system maximum demand by only a few MW but shifted the time of the system maximum demand by one and a half-hours (from 4pm to 2.30pm local time). Tab 5.3 was revised to include the latest PV data and the system maximum demand, and the time it occurred, were updated accordingly. We have not revised all the substation coincident maximum demands in tab 5.4 for this one and a half-hour shift as it is not considered material at the spatial level."]
[null,"5.4.1","ALL","Non-financial","Historical SA Power Networks Databases (10% PoE and 50% PoE  MASTER Load Forecasts 2014, MASTER Substation Transformer Ratings), Demand Forecast Tool Database established by ACIL Allen, PV Installed Capacity for March 2014 and March 2015 Databases, ACIL Allen created PV Calculator, National Electricity Forecasting Report 2015","Actual",null,"The following steps were undertaken to compile the data below:\n1. For each Sub-transmission and Zone Substation, the peak MW day and time for the summer was identified along with associated MVA / MVAr loading.\n2. For each Sub-transmission and Zone Substation, the peak MVA day and time for the summer was identified.  This MVA value was directly compared to the MVA reading described in Step 1.\n\n\nSubstation DATE TIME MVA Difference to when MW peaked (MVA)\nEast Terrace 11kV 7/01/2015 1:00 PM 46.0 0.8\nHindley Street 11kV 7/01/2015 12:30 PM 41.0 0.9\n\nTable 1: Peak MVA at different time to Peak MW for continuous metered Zone Substations and Connection Points \n","In compiling the data contained within the table below, the following assumptions were made:\n1. Sub-transmission and Zone Substations were only included if the MVA margin was greater than 0.2MVA.\n2. Only continuous metered sites were considered with full MW, MVAr and MVA (measured actual data only).\n"]

{"sheet":"6.3 Sustained Intrp","index":16,"n_rows":6,"n_cols":11,"rows_kept":6,"cut":false,"hidden":false,"merged":[[6,7,6,8],[1,1,1,3],[1,4,1,10],[2,7,2,8],[3,7,3,8],[4,7,4,8],[5,7,5,8]]}
[]
[null,"SA Power Networks",null,null,"Basis of Preparation"]
[null,1,1.1000000000000001,4,5,6,8,9,null,10,11]
[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)",null,"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","\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.",null,"\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","Entire tab","Non-financial","OMS","Estimated","Some estimation of Customer numbers is required at the LV level","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.",null,"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."]

{"sheet":"Sheet1","index":17,"n_rows":0,"n_cols":0,"rows_kept":0,"cut":false,"hidden":false,"merged":[]}