Rich, I am not sure of the statement made by Grillo regarding the storage of information. In the end, all persistent data is stored in files. The organization and interpretation of the data is through the program, but that is transparent to the user. Cloud systems typically have storage integrated, but the location is transparent to the programmer and user. There are bulk storage clouds, such as Amazon's Simple Storage Service (S3). On the other hand, it is important to distinguish between a design software vendor that uses a private cloud or one that is hosted on a service such as the Amazon Elastic Compute Cloud (EC2). I am using Amazon just as an example because they are well known. Other companies, such as IBM, Gooble, Oracle and others are now offering substantial compute resources in a cloud format.
Grillo's comment about saving often is interesting. It makes sense, since you do not have decicated hardware locally. That might be something the vendors might want to work on.
In day jobs at larger companies, expensive cloud collaboration software is a must. Too many people, to many version.
But what can the individual or small business use? The extent if cloud use I have ever used for jobs was a centralized storage location. IE: Google drive, network drives. Do these people have other options?
Similar to a response I made just last week, when Richard wrote about "PLM in the cloud" – (same basic idea) – I see the "The Cloud" as just a gimmicky marketing Buzz Word.
For decades, managers have been asking Engineers for the latest & greatest WIP data. You either get a "real-time" report (where the data resides on the server) or you get a "Snap-shot in time" (where the data resides on my home drive).
Its simply a matter of where the data resides. Pros & Cons are obvious; it's about unrestricted control of the data therein. The concept is as old as "Apple-Share" from the 1980's, but it's been re-packaged as "The Cloud".
Richer, Grillo explained about the security and access mechanisms for cloud. But the basic concept of Design in the cloud is yet to be addressed. To my knowledge, it's something like keeping the design tools and design works in a common repository in cloud. Since cloud is scalable, it can be access from anywhere and peoples can work on its image from their own device and finally updating the changes with its original version in cloud. So the changes will get reflect to all its images in a real time scenario.
Jim, eventhough marketing peoples are using “CLOUD” as a buzz word, in real working environment it has many advantages. Especially when it comes under the preview of BYOD or work at home, cloud will help the employees to access the resources or repository, irrespective of device, location, time etc.
IMO, the cloud is nothing more than a means to offload mass data storage to a 3rd party. So, if you design in the cloud your data is stored there and anyone with credentials has access to it. The innovation, if we want to call it that, is the use of todays faster internet connections to make it workable.
I think it's a natural evolution of internet business, and what makes it a good thing is smaller companies (like the one I work for) can keep resources more concentrated on core, value added tasks and less on overhead.
To me, the "Cloud" looks suspiciously like how we used to do things thirty or more years ago- one would punch up a deck of cards, then transmit the data via a telephone modem to a centralized computer, then wait for the computer to spit back the results. (this was way before Al Gore invented the internet). Granted, communications speeds have improved by several orders of magnitude, and data entry methods have become a bit more user friendly, but the process is essentially the same- the real design work is done by the operator at the terminal, not by whatever processor is chosen to assimilate the data into human-readable form (i.e., graphics renderings of lists of points, edges, volumes, etc.). And with the power of today's PC workstations, I don't see any compelling need to offload the work to a remote server, unless you are designing a large, intricate system. Even with large, intricate systems, I venture that the design process begins at the same point my much simpler design projects begin- hand sketches on paper. The tools have improved significantly over the years, but the process is the same...
Now, as to "renting" software rather than buying it: design software, and analysis software such as FAE, CFD, multi-physics simulations, etc., are all very complicated, and one does not gain expertise in a few minutes at a terminal. It takes months to become profecient with a particular software package, and, usually, several days to re-aclimatize oneself to the latest "required" upgrade from the typical software developer. this issue is especially important for the "casual" user...
If one relies on a third party to maintain the software, one loses control over the upgrade cycle, and may find that one must spend time relearning becasue the software package has changed. Then, there is the issue of version compatibility (I still maintain a Win 98SE system becasue I need access to "ancient" work that was created with software in a format that newer packages cannot access). Will you be able to access your data five years from now?
And, of course, the Internet is not always available when you need your data. Just ask the victims of Sandy how long it took to regain access to their cloud-stored data...
Overall, I see "cloud computing" as a marketing scheme for generating new revenue streams for products that are generally over-priced in the first place.
Engineers at Fuel Cell Energy have found a way to take advantage of a side reaction, unique to their carbonate fuel cell that has nothing to do with energy production, as a potential, cost-effective solution to capturing carbon from fossil fuel power plants.
To get to a trillion sensors in the IoT that we all look forward to, there are many challenges to commercialization that still remain, including interoperability, the lack of standards, and the issue of security, to name a few.
This is part one of an article discussing the University of Washington’s nationally ranked FSAE electric car (eCar) and combustible car (cCar). Stay tuned for part two, tomorrow, which will discuss the four unique PCBs used in both the eCar and cCars.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.