Thread by @Skitt0608

As promised, I will try to relay the different things and why for Transporter 1. Please buckle in; this will be long and tedious.

As you well know, there are over 100 payloads associated with this launch. Our primary system, which I will lovingly call OG, was developed in the 90's. Many of our Airmen/Guardians are younger than OG. OG was not developed for multiple payload launches 2/

Realizing this, many years ago we created a secondary system, who I will lovingly call YP, to assist with OG in updating the satellite catalog. YP does probably 80 percent of the catalog updates. However, YP does have its own limitations. 3/

YP cannot independently create new objects to transmit to the network. While it can now building 9 digit numbers, the 5 digit number (analyst or catalog) must be built on OG. So, tomorrow's catalog is going to show 100 catalog numbers already built. 4/

We built them on OG and have them available for YP to assign obs and transmit TLEs. The data you will see on space-track MAY be identical. This is due to initial mass and sorting of observations. No TLEs will be transmitted to space-track UNTIL.... 5/

They have been updated by the T1 team, made up by 18 SPCS civiliians/Airmen/Guardians and OMITRON contractors. This team are also updating the 1.16 Starlinks and prepping for 1.17 (and 1.18). 6/

Because OG cannot easily process multiple payloads and YP cannot create numbers, for Starlink launches, we have built 65 analysts on OG for YP, and have used those numbers for obs association. 7/

Only when the MEGA team (also known as T1 but with fewer numbers until now), do we catalog the launch. Analyst numbers are great to use, except in this case. While we can reserve 65 numbers for the MEGA team, we cannot sustain this 8/

Normally analyst numbers are used for breakups and other inhouse work and for Starlinks, we can build them days in advance. Not so for catalog numbers. We MUST wait until launch for catalog numbers. 9/

We are evaluating this process for future use on the multiple payload launches in the future. We knew who could not create enough analysts for this launch and the 1.16/1.17/1.18 Starlinks. We don't have enough numbers. 10/

Well, that's it for now. I appreciate the patience while we get the network to track these pieces. Owner operators, I'll try to relay via twitter which numbers have been updated. If any one has questions, I'll try to answer. Semper Supra! 11/11