Swap and Go BA cylinders

I agree that this is important for those who manage the lifecycle of the cylinder in the CFA. For cylinders that are always assigned for a single brigade, it's probably a good idea to uniquely identify each cylinder. But with the introduction of Swap and Go, one day the cylinder can be at one brigade, and the next day in other brigade. The brigade that runs the Swap and Go system, manages the lifecycle of the cylinder (they use ServiceNow). For them, I believe, it's important to know the serial #, so they know where the cylinder has been, how many times it has been used, etc. But for all the other brigades that just use the system, it's not important to know the serial number of each cylinder anymore. The cylinder becomes a commodity and we just need to ensure we have fresh cylinders stocked on the trucks.

If the system requires serial numbers for each cylinder, we will end up with a LOT more cylinders in our register than we actually have in the brigade at any point in time.

The system is designed to prevent any duplicate cylinders and it doesn't matter if the user enters BRKD1265, BRKD-⁠1265 or BRKD 1265 they will all get matched to the same cylinder. The primary difference in StationOne vs Swap and Go is that we do not have the entire cylinder database available. As brigades scan a cylinder, if it does not exist in our system you are given the option to add it, once it is added, it now belongs to the parent organisation. If you dispose of that cylinder from your brigade and another brigade scans it or you have not disposed of it in the app but another brigade scans it, it will move the cylinder to their brigade. Using this process, as brigades use our BA module, eventually a large proportion of the cylinder database will be built, noting it can not physically create duplicates of cylinders. So if you are scanning a cylinder and get the request to add it and enter the cylinder number in the asset field, that is now added forever, wherever it ends up in the future.