Are you sick of hearing about the “cloud” and how its the future? Lots and lots of skepticism with a sprinkle of panic, it seems, about running software as a service. People seem to be worried about some valid points, such as, security, cost, “who owns the data” and a variety of other “things”. Seems to me, that many of the concerns absolutely have to be addressed and are being addressed but why are people still skeptical? Change! The engineering circle is always slow to change. Things must be laid out in a crystal clear fashion or at least have the data to backup the claims.
What’s the benefit to us as a user?
- Pay as you go/pay for what you need model. Allows for flexibility on making a capital investment for a piece of technology that is yet to be proven valuable and that is used only some of the time.
- Near instant fixes to “problems”. No need to update software or download anymore, its just there and it works.
- Access to software from anywhere, from any device on any platform. Freedom to choose what you want, not being dictated what to use by others.
I could go on forever, but even the short list above seems valuable. But the interesting concept is the name “Software as a Service (SaaS)”. I have been thinking about this one lately, what is the “service”? Access to the software? The fact that the software is more accessible, is that really a service?
What if vendors truly provided a “service” along with the software? Instant chatting, file sharing, file storage, project work, implementation, training, additional computing power, real engineering help all via the web? Now things could get interesting. Imagine having the “platinum” package and you have access to a support infrastructure “on-demand”.
Suppose you are in the midst of an engineering project and you want to create a really slick rendering for a proposal, but you never quite got the rendering stuff or better yet, you don’t have access to it with your license. You could log into “the site”, your model is already there and chat with the “service” team and you guys spec it out really quickly what I want. The turn around time could be anywhere from minutes, to hours to over night. Why? The web enables and promotes efficiency. The vendors will have to think this through well enough to be able to support it, but their “services” company can easily be around the clock, around the world. The models are already “up there”. Now its just getting the specifics. Especially if you have a “services” contract built into the cost of the well, service?
Think of how this scales out to automation of processes, SIMULATION, design help, the list is endless. I’d be interested to hear people talk about the service side of it and worry less about the software. At the end of the day, do we want to engineer or do we want to drive software?






















