kithpendragon

To: Local Management Team; Regional Management Team From: Jake Bleggslee Subject: RE: Inventory Discrepancies Attachment: Rolling Shutter Distortion Examples As you are all doubtless aware, the Inventory Check, like other components of the database control system it’s part of, is prone to certain biases and errors. Although the numbers displayed in BleggsUniversal® Report Processing Software may be the RealTruth™, that isn’t enough to cause them to actually be correct. This is a fact we collide with every so often, usually resulting in some minor frustration and a lot of excitement. Especially when we start to experience an edge case (such as when certain resources are more densely allocated at some facilities than others), the noisy nature of database management becomes more evident. Before I continue: My intention here is not to excuse suboptimal habits and practices; those should certainly be addressed. Rather, I aim to add a little context and a little detail to the discussion from last night's meeting in order to help calibrate expectations for working with a database that is being expected to track as many different entities, and handle as many different situations from as many input sources as this one is. Hopefully we can decrease the amount of surprise and stress that tends to spread around whenever these edge cases come up. Zooming Out: Lots of Access Points, Lots of Users So much is asked of any database system that must include components throughout the BleggsUniversal® Relocative Network, and that tracks the movements of everything from individual BleggsUniversal® Transport Trollies (which are treated as interchangable by almost every department, but tracked individually for Maintenance) to whole shipments riding in their interconnected (and individually trackable) BleggsUniversal® Linked Long External Transporters. Inventory Checks are one important process in the management of such a system. These real