The dependencies for this was our phone lines, which were used to receive the "broadcast" from Jeep, our corporate WAN/LAN, a local Oracle database and a few other local servers. Our custom application had various processes built-in for emergency situations like losing connectivity, the database failing etc... Over the years, we had a few outages where the database was corrupted or our phone lines were down and it was a mess but we survived.
I wanted to learn programming and decided to write a Perl script that we could use to print labels and manually sequence parts with nothing but the "broadcast" file from Jeep. No WAN, LAN, phone lines, database or custom application required. Basically replacing a multi-million dollar system with a Perl script in case of a catastrophic failure that would likely never occur. This was not in my job description and definitely wasn't supported by corporate.
So, one day while we were in the middle of a problem with the database, unbeknownst to us, the local utility company was doing some work outside of our offices and severed our data lines with a backhoe. No WAN. No LAN because all traffic was routed through remote corporate servers. No "broadcast" from Jeep. And the Oracle database was still down.
We ran production for 17 hours using the first program I ever wrote, a floppy disk hand-delivered from Jeep containing the broadcast data, a Dell laptop and a single Zebra printer. This theoretically saved my company $10.2 million.