Career Questions and Answers
A day in the life of a Systems Engineer (automation)?
Asked by Foggy
Hi,
I'm an electrical apprentice at one of three car manufacturing plants in Australia. Since I started my trade I realised I need more of a challenge and regret not going to university. I enjoy PLC programming and robot programming, and the complicated automation which I have to troubleshoot on a daily basis.
I figure the logical career progression for me is to Electrical Engineer. I know this means 4 years and a degree at Uni.
Before I do this, I'm just wondering if anybody in this career can compare it to what a maintenace electrician experiences, and basically 'A Day In The Life Of a Systems Engineer'. Do these engineers play a part in PLC programming (software), or are they the ones that come up with the 'hardware' design for a production line, like control wiring cabinets, locations of proximity devices etc.
I just don't want to jump before I know what I'm in for! :P
Thanks everyone!!
A:
Best Answer:
Electrical Engineering is a very broad degree that doesn't directly relate to automation. They design anything electronic, from the circuits in children's toys to cell phone towers all the way up to power plants.
If you are interested in automation, you will probably need an engineering degree, but it can generally be Electrical or Mechanical and in some cases I have seen Computer Science majors as well (though "real" engineers tend to get hired much easier than a CS would). What is more important is that you need to take classes in Mechatronics (this may be called something else outside of the US). You will need to learn how to program in Ladder Logic, Structured Text, and ANCI C or their equivalents.
I work for a company that does automation for machine builders (EOMs). For a typical project, I work with the EOM to get a detailed Specification together first, so I know how the machine is supposed to work and how it should react to different situations. That can take anywhere from a few days to weeks, depending on if the EOM knows what they want or just has a general idea (in many cases they haven't finished designing the mechanics of the machine). Then I write the program at my office, using smaller motors to test what I can before going on site; this can take a week or 6 months, depending on the complexity. While I'm doing that, someone (sometimes me) wires up a panel which connects all the electronics together and will go in the machine's electrical cabinet. The motors and panel are normally installed and wired up by the EOM and I spend a week or so on site testing and revising the program.
Most of my time is spent thinking of ways for a machine operator to screw everything up or hurt themselves, then thinking of how to prevent them from being able to do that. I typically program in Structured Text, though some OEMs will insist on Ladder because it was the standard for so long and a few will request ANSI C for various reasons. I also end up going out to fix other people's programs which could be written in any IEC standard language.
I'm a Mechanical Engineer working in automation and close friends with Electrical Engineers and Computer Science guys in and outside of the automation industry.
Answered by themcnasty
Best Answers are selected by the person who asked the question or other Yahoo! users.
Find out more at
Yahoo! Answers