SMETS1 Migration A Guide For DCC Users - SMS Plc
SMETS1 MigrationA guide for DCC UsersVersion:V1.0Date:25 March 2019Author:DCCClassification:Public
DCC SMETS1 Device Migration Guide for IndustryTable of Contents12Introduction/background . 61.1Objectives of this document .61.2SMETS1 Migration Objectives.61.3Intended Audience .71.3.1‘Active Suppliers’ .71.3.2‘Dormant Suppliers’ . 71.3.3Network Operators . 71.3.4Registered Supplier Agents (RSAs) and Other Users (OUs) .71.3.5Geeks.81.4Structure of Document .81.5Precedence .81.6Notation .91.6.1Reference box .91.6.2Tip box .9Some background information for everyone . 102.1Why do we have SMETS1 meters? .102.2Why migrate SMETS1 meters to DCC? .102.3Some essential terminology .112.42.3.1SMETS1 Installations .112.3.2Active Meters and Dormant Meters .112.3.3Migration, Enrolment and Commissioning . 122.3.4Active Suppliers and Dormant Suppliers. 122.3.5Split Supply SMETS1 Installations.13What are the timescales for the SMETS1 migration? .142.4.1Operating Capabilities .142.4.2Migration of Dormant SMETS1 Installations before ActiveSMETS1 Installations .152.5What if I’m not a Supplier? .152.6Who are the key players involved in the SMETS1 migration?.152.6.1DCC .162.6.2DCC Migration Control Centre Service Desk (MCC) .16Page 2 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry2.6.3Data Service Provider (DSP) .172.6.4SMETS1 Smart Meter System Operators (SMSOs).172.6.5SMETS1 Communication Service Providers .172.6.6Requesting Party (RP).182.6.7SMETS1 Service Providers (S1SPs) .182.6.8Dual Control Organisation (DCO) .182.6.9Commissioning Party (CP) .192.7The Migration Process .192.8What’s the difference between SMETS1 and SMETS2? .192.8.1Secondary Elements . 202.8.2Block Tariffs .202.8.3Maximum Demand . 212.8.4Daily Logs .212.8.5Configuring Alert/Event Behaviour .212.8.6Auxiliary Load Control .212.8.7Device Security Credentials.212.8.8Local Commands . 212.8.9Installing/replacing Comms Hubs .212.8.10 Dual Band Comms Hubs .222.8.11 Network Data (Gas). 222.8.12 Miscellaneous.222.93Where should I go for more information .23Information relevant to Dormant Suppliers . 243.1Introduction .243.2What do I need to do ahead of the migration? .243.33.2.1DUIS3 Compatibility . 243.2.2Passing SMETS1 UEPT .253.2.3Getting your business SMETS1 ready .263.2.4Sorting out your Service Request forecasts .263.2.5Setting your Anomaly Detection Thresholds .27How do I know when migration is going to happen? .273.3.1Page 3 of 7425/03/2019DCC PUBLICIndicative Migration Forecast Aggregate Report .27
DCC SMETS1 Device Migration Guide for Industry3.43.543.3.2Notification of intention to upgrade/configure a SMETS1Installation .283.3.3Notification of intention to migrate a SMETS1 Installation .283.3.4Notification of successful migration.30What do I need to do once a SMETS1 Installation has successfullymigrated? .313.4.1Associating Network Operator SMKI Security Credentials withmigrated SMETS1 Installations .313.4.2Finding out about migrated SMETS1 Installations after theevent .323.4.3Testing of migrated SMETS1 Installation . 323.4.4What if something goes wrong? .33Where should I go for more information?.33Information relevant to Active Suppliers . 344.1Introduction .344.2Getting yourself ready for migration.344.3Getting your SMETS1 Installations ready for migration .344.3.1Introduction .344.3.2Device Model/Firmware Combinations . 344.3.3Device Model Combinations (DMCs) .354.3.4DCC Device Testing . 354.3.5EPC and PPC Lists . 364.3.6Updating SMETS1 Device firmware .374.3.7Updating SMETS1 Device configurations . 384.3.8Preparing Prepayment SMETS1 Installations .384.4Submitting Indicative Migration Forecasts .394.5The 6 week migration cycle .404.5.1Introduction .404.5.2Week 1: Migration Demand .424.5.3Week 2: Demand Commitment .434.5.4Week 3: Hiatus .444.5.5Week 4: Migration Authorisation .444.5.6Week 5: Migration . 464.5.6.1 Introduction .46Page 4 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry4.5.6.2 Suppliers electing for DCC to commission Devices .474.5.6.3 Suppliers electing to commission their own Devices .474.5.6.4 Post-Commissioning Testing .4854.5.7Week 6: Outcome Reporting .484.5.8The start of and end of an Operating Capability.49Information relevant to Network Operators. 515.1Introduction .515.2Getting yourself eligible for SMETS1 .515.3Planning for the arrival of SMETS1 Installations on your network .515.4Detecting the arrival of SMETS1 Installations on your network .525.5What you can do with SMETS1 Installations once they’ve migrated .526Information relevant to Registered Supplier Agents and OtherUsers5476.1Introduction .546.2Getting yourself eligible for SMETS1 .546.3Monitoring the progress of the SMETS1 migration .546.4Identifying migrated SMETS1 Installations .556.5What you can do with SMETS1 Installations once they’ve migrated .55Behind the scenes . 567.1Introduction .567.2The end-to-end migration process .567.37.2.1The end-to-end migration process (commissioning byCommissioning Party) .577.2.2The end-to-end migration process (commissioning by ActiveSupplier) .64Migration Files .67Appendix A: References. 69Appendix B: Jargon Buster. 70Page 5 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry1Introduction/background1.1Objectives of this documentWelcome to SMETS1 Migration: A Guide for DCC Users. The primary purpose ofthis document is to provide a plain English guide that helps DCC Users gain anunderstanding of SMETS1 smart meters and their migration to DCC. Whilst ofparticular interest to Suppliers, this guide recognises that the SMETS1 migration alsoimpacts Network Operators, Registered Supplier Agents (RSAs) and Other Users(OUs).Once you’ve read this Guide, you should (hopefully) be better informed as to: what the SMETS1 migration means to your business; how you should prepare for it; when it’s going to happen; how the migration process will work and what part you will play in it; where you should go for additional information.1.2SMETS1 Migration ObjectivesSMETS1 Migration will help achieve important objectives in support of Governmentpolicy so that: consumers with SMETS1 meters still operating as smart meters will be able toswitch Suppliers without losing their smart functionality; consumers whose SMETS1 meters have ‘gone dumb’ due to a change ofSupplier will regain their smart functionality; Industry investments will be protected by delaying the need to replace ‘dumb’SMETS1 meters.For Suppliers, migrated SMETS1 meters reduce the number of SMETS2 meterinstallations they’re required to complete by the end of 2020 and allow all smartmeters to be accessed via DCC’s systems which can simplify things in the backoffice.Page 6 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry1.3Intended Audience1.3.1‘Active Suppliers’The term, ‘Active Supplier’, is used in this document to describe ResponsibleSuppliers currently operating, or able to operate, a SMETS1 smart meter as a smartmeter through the services of a SMETS1 Smart Metering System Operator (SMSO).It’s important to note that the Responsible Supplier doesn’t have to be operating thesmart meter for the meter (and the Supplier) to be considered ‘Active’. If the Supplierhas a contract with the SMSO enabling it to operate the meter, it is considered to bean Active Meter regardless of whether or not the Supplier chooses to operate it.This is important since, Active Suppliers play an active role in the migration of themeters to DCC, taking responsibility for ensuring that the SMETS1 Devices meet thepre-requisites for migration, scheduling when the migrations occur and, optionally,commissioning the SMETS1 Devices as part of the migration process (as describedin section 4).1.3.2‘Dormant Suppliers’The term, ‘Dormant Supplier’, is used in this document to describe ResponsibleSuppliers with SMETS1 meters who have no contract with the SMSO and, as such,the SMETS1 meters have ‘gone dumb’. As their name suggests, Dormant Suppliersplay a relatively dormant role in the whole migration process; DCC takingresponsibility for the majority of migration activity. DCC keeps Dormant Suppliersabreast of these activities; both prior to, and on completion of, the migration, at whichpoint the Dormant Supplier can start operating the migrated SMETS1 Device(s) viaDCC (assuming the Dormant Supplier has met the required pre-requisites – seesection 3.2).1.3.3Network OperatorsLike Dormant Suppliers, Network Operators have a largely dormant role in the wholemigration process. They are kept abreast of progress of the overall migration but, aswith SMETS2 Devices, they must wait for a SMETS1 Device to appear in DCC andthen wait for someone else to associate their SMKI Security Credentials with theSMETS1 Device before being able to operate it.1.3.4Registered Supplier Agents (RSAs) and Other Users (OUs)Like Network Operators, RSAs and OUs only become involved once the migrationprocess has completed successfully, at which time, they are able to accesspreviously inaccessible SMETS1 Installations via DCC. Unlike Network Operators,they are not notified of the arrival of a SMETS1 Device in DCC but, on the plus side,they’re also not obliged to wait for SMKI Security Credentials to be associated withthe SMETS1 Devices prior to communicating with them.Page 7 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry1.3.5GeeksFor those with a morbid interest in the workings of DCC, section 7 provides a highlevel overview of the entire end-to-end migration process, flagging those parts whichfeature in the previous sections describing Dormant Suppliers, Active Suppliers,Network Operators and RSAs/OUs. It’s not essential that you know any of this sofeel free to skip it.1.4Structure of DocumentThis document has been largely structured according to its readership: Section 2 is intended for everyone. Section 3 is aimed specifically at Dormant Suppliers (i.e. those who haveinherited a SMETS1 meter through a change of Supplier but are not currentlyoperating it as a smart meter). Section 4 will be of interest to Active Suppliers (i.e. those currently operatingSMETS1 meters as smart meters through the services of a SMETS1 SMSO). Section 5 should be read by Network Operators (who will see migratedSMETS1 meters appearing on their networks following migration). Section 6 contains information relevant to Registered Supplier Agents (RSAs)and Other Users (OUs) who will now be able to access SMETS1 meters oncethey’ve migrated to DCC. Section 7 is a high-level description of what goes on behind the scenes tomake all this happen.1.5PrecedenceThis document aims to be a relatively friendly, accessible guide to the complex worldof SMETS1 migration but it’s not intended to be a substitute for the definitive tomeson the subject in the form of the Transition and Migration Approach Document(TMAD) and other associated Smart Energy Code (SEC) documents.In the event of any discrepancies between this document and the SEC documents onwhich it draws, it goes without saying that the SEC documents take precedence.We’ve worked hard to ensure this Guide is aligned with the TMAD version 0.3. Wedon’t plan to update this guide although we may consider should TMAD requiresubstantive changes in the future. Hopefully this guide will rapidly lose its value asSMETS1 Migration progresses and people become more familiar with the migrationprocess.Page 8 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry1.6NotationWe’ve tried to use capitalisation of terms consistently in this document. If a term iscapitalised, it has a specific meaning. Usually, it will be a term from TMAD, anotherSEC Subsidiary Document or the SEC, itself. Occasionally, it will be a term definedin the Guide (as is the case with ‘Active Supplier’ and ‘Dormant Supplier’).Acronyms abound in smart metering and not more so than in the SMETS1 Migration.We’ve tried hard to expand any acronym on its first use and again if it hasn’t beenused for a while. We’ve also included a ‘Jargon Buster’ in Appendix A as a go-tosection for the befuddled.And to make things a little easier to read, we’ve also included two additional forms ofnotation to signpost external references and take away points.1.6.1Reference boxBlue boxes contain references to external documents (where possible includinghyperlinks). We’ve also tried to include references to specific clauses withinexternal documents as footnotes where relevant to the text.For convenience, we’ve also gathered together all of the externally referenceddocuments in Appendix A.Please bear in mind that this document has been written during a particularlybusy stage of preparation for the SMETS1 Migration and many of thedocuments referenced in the Guide have yet to be finalised. It’s likely,therefore, that many of these references may soon become redundant.1.6.2Tip boxRed boxes contain some more detailed points of information we hope you’ll findparticularly useful.Page 9 of 7425/03/2019DCC PUBLIC
DCC SMETS1 Device Migration Guide for Industry2Some background information foreveryone2.1Why do we have SMETS1 meters?A key element in the Government’s mandated rollout of smart meters is theestablishment of DCC as a single gateway for those wishing to communicate withSMETS2 Devices. Indeed, due to the nature of the security model used to supportthem, DCC’s infrastructure is the only mechanism for communicating with SMETS2Devices.However, some Suppliers chose to start installing smart meters prior to DCCbecoming available. Some of these pre-DCC smart meters aren’t particularly smartand don’t count against a Supplier’s obligation to offer every customer a smart meterby 2020. These will need to be replaced along with traditional meters. SMETS1meters, on the other hand, are deemed sufficiently smart to count towards aSupplier’s quota of smart meters and do not need to be replaced.Prior to DCC coming into existence, Suppliers were required to procure the meansfor communicating with smart meters, themselves. DCC equivalent for pre-SMETS2smart meters is a Smart Metering System Operator (SMSO). Some Sup
Welcome to SMETS1 Migration: A Guide for DCC Users. The primary purpose of this document is to provide a plain English guide that helps DCC Users gain an understanding of SMETS1 smart meters and their migration to DCC. Whilst of particular interest to Suppliers, this guide recognises that the SMETS1 migration also
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Data Migration Planning Analysis, Solution Design and Development Mock Migration Pilot Migration Released Data Migration Active Data and User Migration Inactive Data Migration Post Migration Activities Small Bang The details for each step include: Data Migration Planing - Develop the migration strategy and approach, and define the scope,
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
LÄS NOGGRANT FÖLJANDE VILLKOR FÖR APPLE DEVELOPER PROGRAM LICENCE . Apple Developer Program License Agreement Syfte Du vill använda Apple-mjukvara (enligt definitionen nedan) för att utveckla en eller flera Applikationer (enligt definitionen nedan) för Apple-märkta produkter. . Applikationer som utvecklas för iOS-produkter, Apple .
Migration overview In the context of Migration Manager, migration is the process of promoting . A migration group can be either internal or user-defined. Internal migration groups are included with the product and are linked to other logically related migration groups called dependencies. You cannot modify internal migration
2. AngularJS looks in the template for the ngApp directive which designates our application root. 3. Loads the module associated with the directive. 4. Creates the application injector 5. Compiles the DOM treating the ngApp directive as the root of the compilation AngularJS: beginner's Guide - part 1
