Jan 27 2010
Reflections
I know from the server logs that quite a few more people visit this site than just those whom I know personally and it’s always quite interesting for me to follow things from my side of these pages. Although this has been a great way to communicate with family & friends and attract readers from around the globe, when you look at the format in addition to the content, you might think that the posts all these years have just been an excuse for being able to make a website in the first place.
About the same time we were running FlyingMelons.com out of our NJ basement (see: Welcome message), I was working as a Facilities Operations Scheduler for South Jersey Hospital System using Datastreams proprietary CMMS, MP2. The computer at work was just another tool for a job as far as I was concerned, a usable extension of the mind & hands for the person using it, and the licensed software product fit the bill as well as any other canned, off-the-shelf product would… more or less. (Less and less, if you’re into what you’re doing.)
We all have a learning curve and MP2 was really my first exposure to Database Management Systems (DBMS). Since it was the late 80′s / early ’90s, all of my server pages on the home machine were still static coded html. I really learned a lot because of what that program couldn’t do for me on the job.
The problems started to surface as we corporately merged and grew from a single hospital with a couple of O.R.’s and an ER; to two facilities with Maternity, various secured lock-down units and separate physicians offices; to three with out-reach clinics and more buildings; to, at the time of my employment, a four hospital, full-blown, Regional Healthcare System. What fit us early on, just wasn’t keeping pace with our growth.
We’d pay to add user licenses after user licenses and when we needed something not off-the-rack, we could either “wait for the next update” or call the company to have someone “customize” their product for us – for T&M + travel + per diem of course. But the customization repeatedly amounted to little more than a guy trying to tweak some boiler-plated addon from a job they did somewhere else – always with the problems, delays, and “We’ll have someone get back to you” excuses.
All the time I had been working on my stuff at home, little things like getting “persistence” commands to keep me connected to the ‘net after my welcome was wore out or creating our own email domain, and developing a DBMS from open source (read: free) materials that – in my vision – anyone with authorized access would be able to adapt to suit the corporation’s growing needs long after I was gone.
I soon had my regular departmental duties down to a routine and was also able to implement a system-wide Asset Management System that anyone with access to the company’s intranet could access with any browser – all run on a “stolen” I.P. from a single retired server converted to a Linux box on the floor alongside my desk. Ultimately it was the stolen IP address that enabled me to spend half of my time at work alongside some really great people in the IT department, but that’s another story.
The Work Order Request part of the system was immediately effective since previously, only Maintenance & Plant Operations personnel were granted access to this Work Order System. Nursing had their own system. Radiology, usually being contracted, had their own. Everyone was their own entity and as you can imagine, people in each facility were still vehemently clutching to the system they had grown accustomed to before mergers. But now, anyone could easily log on and have a database backed, time-stamped & logged Work Order Request literally within minutes – all with no EULA, travel fees, or the headaches.
Things were really starting to take off with this and I was spending more and more of my time collaborating with I.T. to seamlessly incorporate the Linux box with the Novell NetWare, expand to full corporate asset management instead of just the equipment I.D.’s I had previously been assigned and generally brain-storming with them on other improvements and to phase-out the proprietary system; all while completely fulfilling my previously agreed-to obligations within our department.
It was ultimately the short-sightedness of my immediate and 2nd level superiors, their need for control and a major motivation to “not make waves” by changing things that severed interdepartmental budgetary negotiations and is one of the reasons that I actively started looking for work elsewhere. That “elsewhere” eventually became Colorado.
No one can pay me enough to do little with my life and now I’m in a place where computers are used to control processes. It’s the coolest thing! Read about that move here…










