I got hired by a company about a year ago that doesn't normally do software development. They had contracted out to a firm to get some software written for them. Later, they hired me to help maintain it. What this software does is gather data locally at a rig site, stores it in a local SQL database, and periodically uploads the data to a remote database that is maintained by my company. This allows people who are not at the local rig site(say, the clients CEO) to use a remote version of the software to login, and see what is going on. Each rig site has a name associated with it: Rig 1, Rig 5, etc. The main problem is that the client can create a username/pw each time they run the software. This leads to many logins all associated with new rig sites created with the same names. There are numerous reasons why this happens, the least of which is that the software doesn't check to see if a username already exists. And quite frankly, my company and all the clients all appear to not care about any of this.
The most difficult part of it all is if something goes wrong, I don't hear about it for almost 4-6 hours later. And when I do hear about it, I get the very vague "It's not working". When I try to prod them for more information, no one is ever doing anything when it "broke", or no one remembers. This is frustrating to no end, and I get yelled at when I can't successfully fix the issue in a timely manner. I've informed my boss about this issue, and again, no one really seems to care.
So that brings about my question: How do I make them care? How do I get them to impose some semblance of standards that will not only make my life easier, but benefit them as well?
Standards I'd like implemented:
- 1 username/pw per client (makes it easier for the client to see all the rigs they own in one place).
- Faster response time to issues.
- Detailed reports of what was going on when issues occurred. (Both these get the site up and running faster.)