Requirements for a successful automation project.
Requirements for a successful automation project.
(OP)
Success of an automation project is defined in many ways. Two major definitions exist:
1) Machine XYZ completes all its logic functions and physical movements. The movements were defined by a combination of the automation engineer and process manager.
2) Machine XYZ produces product to specification. Often this specification is on the overall product which can be affected by both the incoming and subsequent processes. For example a failure by this definition may include a project where the machine moves exactly as specified but due to an incoming product the outgoing product fails to meet specification.
Which do you consider correct and why?
What would you like to see from an automation company? How should the initial project be approached? Should the automation company include development time to better understand the customers process? How would you like to see an automation company handle pricing and delivery when an automation project is often a development project where the path to solution is often not well understood beforehand?
Thanks in advance for your input.........MSCHWALM





RE: Requirements for a successful automation project.
The customers I work for look at it this way.
OK lets say "A" is process into XYZ "B" is process out.
The bottom line is A+XYZ+B=PROFIT "The Real Boss"
Many designers are given 100% to 150% flow rates to design
machine XYZ.
Define where you fit in the equation "Scope of work".
You need this very well defined with the customer.
In the real world an average process line runs 86% to 95% annual product depending how good the automation is. XYZ is most likely oversized for A or B or both. My feeling on the matter is you need a clear understanding of A&B to automate
XYZ to a customers satisfaction.
Bid yourself enough hours at a flat rate to set a "scope of work" Meet with your customer and set a direction of work.
RE: Requirements for a successful automation project.
With this in mind, if an automation project produces junk because the input is bad and not because the automation failed the result is still junk. The operation was a success, but the patient died! It is hard to call a project a success if the bottom line is a loss.
RE: Requirements for a successful automation project.
On a slightly different but related subject I would like to make an observation. When consideraing a product which has to be assembled designers automatically envisage one part in each hand. Hands are difficult to replicate. If component designers thought more in terms of the ability of simple machine mechansisms then the whole process of automated assembly would be very much easier to achieve, more reliable and more economic.
RE: Requirements for a successful automation project.
In regard to your last observation:
I learned what I know about tooling design from old-guard machine shop guys. That will teach you to consider what the tools can do, what they can't, and maybe more importantly - what the shop machines can do. One more reason young engineers should co-op.
RE: Requirements for a successful automation project.
1.study of the process
2.ergonomic aspects
3.budget available
4.technological environment in the organisation asking for automation
5.Manpower who is going to support the project.
6.Type of idiot moves expected.
7.disaster considerations in case of failure of any automated sub system.
8.reliability requiremrents of the process being automated.
power available at the site the project is being implemented.
9.educational and social environment around the project site and of the manpower likely to handle the project
vinod
vksingh_15@yahoo.com
RE: Requirements for a successful automation project.
I find that its easy to over complicate stuff. Mostly the customer wants the end result and doesnt really need the painful bit in the middle. Get the solution and work backwards. Dont invent solutions for solutions to solutions to problems. Sort out the basis for your project. Always consider the manual process too , how can we use it ? what should we learn from it. On line help apart from this site is poor. Check out
http://www.roboknowlege.com.
Its a bit specialized but if post the question and check out the site content you might provoke a response.
regards