Changes of customer in the transmission queue

A change of customer is a project’s customer name in one register different from the last one given before it, capitals, spaces and punctuation aside; a blank is never a change. A change that a later register undoes, the old name back, is taken out with the change that undid it. Two names are the same company where they differ only in a legal form or in “&” for “and”, or where an approved alias joins them, and a pair can be put right in those aliases later. The register names the company that holds the agreement, so a sale of that company leaves its name as it was: these are transfers of the agreement and renamings, not every sale of a project.

A company is its name as the register writes it most recently, taking together names that differ only in a legal form or in “&” for “and”, or that an approved alias joins. Each change counts once, in the technology and status the project had in the register that first showed the new name, with the MW it still had to connect there.

A change counts as before the project connected where it still had MW to connect in the register before the change. A stage has connected when the register first shows its MW connected.

For each full year we take the projects with MW to connect and a connection date at the start and the end of the year, as Delays and exits does. A project is similar to another where both are in the same year, their connection dates were the same distance ahead at the start of it (due that year, the year after, two years on, three or four, five or more, or past already) and both had the same status. What is expected is how often the rest of the queue in the same group was pushed back, left or connected, added up over the projects that changed customer. Where they are now is read from the latest register; we give how many have connected since only where it differs from the number expected by more than 15%.