News
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
As engineering professionals we should all be passionate about protecting our hard won designs and intellectual property from the pirates and less than scrupulous commercial denizens. There are many disturbing examples of ‘rip-offs’ occurring regularly around the globe – with some countries more guilty than others.
Despite what you think this is a topic relevant to us all. Whether an electrician or chief engineer, you work with intellectual property on a daily basis. And it is this intellectual property which is closely linked to your (and your firm’s) skills and expertise. It is, therefore, vital that you know when you are creating something worth patenting or copyrighting and, on the other hand, are aware of the possibility of infringing on someone else’s patent.
Patenting an idea gives you, the inventor, a 20-year monopoly, during which time you are free to maximise your intellectual property in the marketplace. This requires the publication of a full and honest account of how the new product, process or material works (so that everyone can see how “you did it”). Which, I hasten to add, is not necessarily to your advantage as you now raise the flag and disclose your soul to all your competitors and pirates out there (for what may be considered “your birthright in exchange for mess of pottage”).
In order to patent your invention, it must not only be novel, but also useful and ‘non-obvious’. It is impossible to patent magic, for example, or something which defies the Laws of Nature (such as perpetual motion). Furthermore, a working prototype must be provided to the US Patent and Trademark Office (USPTO) for the patent applications which may challenge the Laws of Nature.
The challenge, at present, for the patent offices (particularly in the US) is the deluge of frivolous applications. We have the famous case of the intermittent windshield wiper operation. Perhaps in days long gone, when the wiper was powered mechanically from a vacuum in the engine, there was something massively innovative here. But with today’s technology, where electrical motors and dedicated electronics are used, it is a trivial operation within the capabilities of entry level high school students in their Design and Technology classes. Another issue for the patent offices are the aggressive lawyers who represent firms making applications with little to show. An example of a legal stoush over a patent license was when Rockwell Automation’s clients were sued (by a legal firm that had accumulated well over $400m from similar actions in the past), some years ago, over a patent for real time communication between computers – something which is done as a matter of course these days. This is not very productive for society.
But this is not really the target for my spleen – patenting ‘business processes’ is. There are over 12,000 business processes patented annually in the USA alone (and considerably fewer elsewhere). Examples of silly business process patents include Amazon’s “one-click” and Priceline.com’s “name-your-price”. These are not stimulating innovations, but are about extracting money from innocent users and, possibly, competing firms with fairly obvious ideas.
What has become clear is that the ‘non-obvious’ part of the patent test hasn’t been applied as rigorously as before. As a result many shonky patents have been granted which act more to suppress commercial activity and competition. This may be as a result of US Patent Office understaffing, the Internet still a relatively new phenomena and other travails which have kept commercial patenting off the political radar.
Fortunately, with recent court cases, America’s Supreme Court is poised to rule for common sense - making it very difficult to get a patent for a business process. As a result, many business processes which are based around software algorithms will be affected - it will impact on software patents as well. This may encourage software programmers to seek solace in copyright which extends up to 70 years after the author’s death. Admittedly, copyright protection is very narrow in scope and can only protect against straight piracy.
Oddly enough, as an aside, very few inventions are worth patenting. My advice is to avoid the temptation to patent unless you believe you have something really worthwhile. Surveys of companies in Europe and North America constantly rate outstanding service, lead time and quality (and secrecy!) as significantly more beneficial than patents. The challenge behind a patent, other than the investment of time and the cost (they are relatively cheap actually) is the fact of disclosure. If it contains any commercial value you will immediately attract a robust horde of imitators and you will then need to defend your patent in court. This is where your real costs start. It would appear that, in the majority of cases, the cost of litigation far exceeds any revenue made from royalties or licensing fees as an inventor. In this situation the only winner, sadly enough, is your friendly lawyer who will be delighted to go to court for you.
I can clearly remember (doesn’t this age me?) when we had the plethora of competing and definitely non-interchangeable hardware and software computer operating systems in the early eighties. At that time IBM walked away from any patenting. It produced the open source concept (well, sort of) with their initial PC, set up a standard PC and created a new industry. IBM changed the world - allowing us to interchange software and hardware with a standard PC and the market expansion was breathtaking. (Despite this, I am sure there are some who claim that the standard PC is still riddled with inconsistencies and problems).
I love H.E.Martz’s take on it all: “He who builds a better mousetrap these days runs into material shortages, patent-infringement suites, work stoppages, collusive bidding, discount discrimination and ….taxes”
Thanks to the Economist and some of their correspondents for some interesting reading on this subject.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
I like to think I am one - an engineering entrepreneur that is. And vaguely successful. Although, I must confess that when I see the salaries earned by those uber successful engineers in oil and gas, for example, I know that it is arguable in terms of financial success (especially considering the risks I have taken). But I comfort myself with the great satisfaction I get (well, 90% of the time). I delight in engineers and technicians who have set up incredibly successful businesses (but am saddened by those – the majority – who have failed). In these tough times, I do believe that for our economies to grow we need far more entrepreneurs providing services and products that improve productivity (including safety). The spin-off will be the employment of more people and more opportunities for engineering professionals to practise their skills. Engineers, being highly creative (and making things that are ultimately useful), have an incredible role to play here (as opposed to other disciplines such as lawyers, doctors and accountants).
Becoming an engineering entrepreneur may seem a good idea if you have reached a crossroads or hit a brick wall in your engineering career. Otherwise you may have such a brilliant service or product which you reckon has great possibilities and which tempts you to head out on your own. Importantly, though, becoming an entrepreneur does not necessarily entail striking out solely on your own. You can often do it within your existing company structure – genuine owners of businesses delight in welcoming like-minded engineering professionals to extend their businesses with new products and services (and to weather the risk themselves). However, even here, you will have to take ownership of the risks and ensure your venture works, otherwise you will have your career and credibility seriously weakened.
Be ruthless about whether it is a feasible product you are proposing. Many companies have not been able to survive as their key products, whilst useful, have simply never been viable business ventures. Oddly enough, what you are contemplating doesn't have to be new or unique (is there such an animal?), but the overall business case has to really work.
Some personal lessons for me are:
As engineering professionals we tend to focus on the technical aspects of the product. This is what gets us excited. However, it is the ‘filthy’ business case on which we need to center our attention – “Can this product or service be sold to make money?” - the overwhelmingly important question before launching an idea. Engineers often neglect the business factors as they are less interesting to us. Sadly, the market will not beat a path to your door because ‘you have designed a better rat/mouse trap’. Ideas are a penny a dozen - it is the business strategy and plan that is critical. Most engineers and technicians can sketch out ideas with potential. 99.999%, however, won’t be able to put them into action. As a starting point you must ensure that your business is closely aligned to your engineering skills and passion. You will have built up a tremendous skill-base, knowledge and indeed contacts over your engineering years in a particular field – a great leverage.
It is also a myth that by setting up a business, you end up getting rid of your ghastly boss. In fact, you end up with many, many more bosses (also known as clients). And they may not be that pleasant to deal with either. So don’t use this as your motivation for setting up a new business.
It is good idea to take an idea which is red hot and let it boil for a few months. Kick it to death as many times as you can by getting other people’s opinions (these will often be disinterested or negative). If it survives 6 months of this and you remain enthusiastic about its strength as a business case it may mean it has “a 30% chance” of success.
A business plan defining your product and strategy is absolutely essential. And it should fit on a single sheet of paper with all the key thoughts worked through and built in here. I believe that the 150 page business plans have long since disappeared – your plan must be succinct, simple and convincing. If you can’t explain simply what you are doing in a few words to your grandmother, it is probably going to be difficult to make it work. Items to be included in your business plan include; those aspects of the product that are unique, why you will be able to sell it, who your competitors are, the costs and predicted revenue, the cash available to fund the venture, how long it will take to develop the product, the members of your team, an outline of the operations and admin issues and finally, a simple implementation check list with dates.
Initially, try to finance the product yourself and demonstrate that it is workable and bringing in a solid profitability before going to others for funding. Borrowing money from others or getting partners onboard, when the product hasn’t been proven, is fraught with danger. Having a proven business operating before you approach partners or venture capitalists (if there are any around these days), gives you considerable leverage in negotiations for more money or partners in selling it in other markets.
Put overwhelming effort into your marketing and sales. Persistent communication of your idea to prospects for your products are essential. Engineers often shy away from this. If you don’t have their interest and no partners who can take this role on; seriously reconsider the viability of setting up a business.
Once you have your product out in the marketplace, you have to listen carefully. You may find that you have to change your strategy considerably as the market might want something else. Unless you are superhuman and highly attuned to the market, it is unlikely your original idea will be what you eventually sell. Don’t be obsessed with your particular product or service - listen to the requirements of the market. And remember every day; re-assess what you are doing to ensure it is aligned with the needs of the marketplace. Be quick to re-invent yourself if necessary in order to match up with the changing needs in the marketplace.
It is an extremely lonely mission setting up your own business. Often you are confronted by severe indifference with no one to talk to (apart from your long suffering life-partner who may be a bit underwhelmed by your day-to-day problems). Make sure you have oodles of support from your life-partner and that she or he is absolutely committed.
Even when you have a highly successful business, it takes aeons to see the first dollars come in. Often you end up with two years of virtually no income as you build up the business. Can you cope with this and more importantly can your personal life cope with this? Cash flow is always a challenging animal to deal with, but it is always king in business.
And an issue I have tended to scorn in the past (to my detriment), is the operational and administrative side of running the business. You have to put in place systems to deliver your product or service easily and effectively, with a high and continuing level of quality and profitably. Oddly enough neglect of these issues can cripple your business. One of the frustrations of entrepreneurs comes with expansion. Employing more people costs more and with systems in place lacking effectiveness a reduction in product quality can result. You may find that your profitability is considerably less too, compared with when you were the sole employee.
You do need passion and persistence. Persistence is critical as you will get “kicked in the teeth” at least a dozen times a day in the course of running the business.
There is no doubt, that it is enormously satisfying as an engineer to run one’s own business, bring new products and services to the market and take control of one’s own destiny. I continue to see so many vibrant engineering businesses opening up that are absolutely inspirational. These range from consulting, to software and hardware development, to electronic product development, to education, to construction and shipbuilding.
When considering entrepreneurial ventures, as the famous General Patton counselled:
‘Take calculated risks. These are quite different from being rash.’
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Thanks for the flood of responses to the engineering quiz. Full answers are below and we would like to congratulate our winners:
Mr Patrick Richards
Mr Brett Dixon
Mr Mike Jones
(Drawn from all the correct submissions). All others with correct answers will be offered an e-book of their choice. Well done everyone.
Wanted: Green Engineers and Technicians
Some of you have tartly suggested over the past few years, that it would be gratifying to receive some convincing evidence that climate change is actually caused by man. Unfortunately I am not in the position to provide this (due to my lack of knowledge in the area), but what is becoming very clear is the need for more engineering practitioners focusing on the matter of climate change. Massive commitments have been made by the larger economies to address the issue, but there are now simply not enough engineering professionals to implement these radically new systems – many of which are completely different to those used in the past.
The use of coal is expected to double by 2030. In response some pretty serious carbon capture and storage technologies are required with enormously innovative geological surveying, mining, pipelining, automation and chemical engineering needed. There are obviously mixed feelings about the nuclear industry, but many governments have decided to go ahead here, and both outstanding engineering professionals and independent regulators (to ensure safety and to protect the public) are required. Renewable energy with solar and wind energy, is perhaps better understood (but whose need is perhaps not quite as pressing as carbon capture and nuclear technologies - with their enormous concentrated capital investments). Renewable energy, however, can provide an enormous number of jobs and can be extended on a vast scale (by retrofitting homes for greater energy efficiency, for example). And naturally, all engineering design and installation today requires deep thought given to the issues of sustainability, energy efficiency and minimisation of emissions.
For the first time that I can recall, engineering is in the unique position of being perfectly aligned with the environmental movement with its focus on “saving the world” and with engineers as the “good guys”. Technology will prove itself as one of the keys to dealing with the problem of climate change (otherwise we must return to subsistence living – an unlikely option).
What do we need to do?
* Drive your governments and bureaucrats to more aggressively fund research in energy engineering. This will ensure the emergence of practical, useful technologies which, as engineering professionals, we can apply.
* Convince laid off engineers and technicians or those in more somnolent areas (e.g. missile engineers) to take up green technology skills.
* Tell the world (particularly environmental campaigners and politicians), that engineers can actually “save the world”. Inform them that through the application of new technologies; emissions can be reduced, efficient energy systems designed and carbon captured effectively.
* Look at how you can skill yourself up in these new green areas to build your career and “help your world”
To rework a comment from The Economist a little:”…the best thing a bright young person can do to help fix the climate change problem is to get an education in engineering”.
Thanks to the Economist (The World in 2010) for their valuable references.
The Quiz
Q1. If the resistance of a circuit is 20 Ohms and the voltage across it is 100 Volts, what is the current?
A1. V= I * R; thus 5 amperes (or 5A)
Q2. What is the key feature of the HART protocol?
A2. It allows for bidirectional digital communications superimposed over a standard 4-20mA loop, thus providing for querying of data and diagnostic information and sending configuration data to the instrument.
Q3. Why is the 4-20mA instrumentation standard so useful?
A3. It is an internationally recognised standard. With at least 4mA always flowing in the loop (with ability to power instruments on the same pair of wires), simplified wiring is possible. Loop resistance does not make a major impact. In addition, with a minimum value of 4mA, it can indicate a broken link.
Q4. In terms of stability, what is the purpose of the derivative term in PID control?
A4. Particularly with loops with significant process lags (such as temperature loops), the addition of the derivative term provides for increased stability in the overall loop operation.
Q5. What is the difference between these two engineering instruments below?
(a) (b)
A5. (a) is a slide rule using for calculations (mainly used prior to the mid seventies) while (b) is a vernier caliper for measurement of internal and external distances and depths
Q6. A pump with a low initial cost and low maintenance cost is (select one):
Gear Pump / bucket pump / double acting piston pump / centrifugal pump
A6. Centrifugal pump.
Q7. A feeler gauge is used for measuring the (select one):
Thickness of plates / clearance between mating parts / pitch of screw threads / radius of curvature.
A7. Clearance between mating parts
Thanks for all your submissions.
Yours in engineering learning
Steve
The winners of the quiz were: Mr Patrick Richards, Mr Brett Dixon and Mr Mike Jones. Congratulations and thanks to all those who submitted answers. The suggested answers follow each question – please note that we accepted a wide range of answers provided they were reasonable.
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Although there is the inevitable hype about what an incredible economic year beckons us as we farewell the great recession, I have my reservations. I reckon things are going to remain challenging and that we are currently experiencing a paradigm shift which will effect how we work as engineering professionals. This is driven by a high level of unemployment, a shortage of capital, low profitability in companies, enormous debt weighing on all economies, China and India rapidly growing and the internet coming of age in all industries. In response we have to be flexible to maximise our career opportunities.
Over the past decade, I have observed some remarkable engineering career changes; Mike, an instrumentation engineer, had enormous experience in mining and alumina, but is now heading up a successful software design team for transport systems, Phil has moved from an advanced process control background to floating a top international mining company, John has set up a massively successful cell phone company after a successful data communications design career; Branden, a successful computer networking technician, has set up a company writing 3-d engineering software for mining applications and finally, Mike, who originally implemented electrical SCADA systems for an electrical utility is now designing and managing biomedical systems.
On the other hand, however, I have seen some remarkable career failures, especially with the dot com bomb in 2000 - some really good engineers and technicians got “wasted” by entering the web design and internet area where, at that time, there were no solid commercial benefits. In many cases their (often very interesting) jobs soon evaporated.
Suggestions:
* Look out for solid technology trends in your engineering area and investigate them
* Skill yourself up in these new areas by networking, reading, attending courses and getting on-the-job experience
* Look for areas which have solid commercial payoffs rather than blue sky opportunities
* Look at how you can add these new skills to your instruction set to benefit your firm
* If the job looks solid and there are real commercial benefits, then take it.
And in investigating new avenues for your career remember, Philip Crosby's injunction: ‘Very few of the great leaders ever get through their careers without failing, sometimes dramatically’.
Yours in engineering learning
Steve
- Details
- Written by: Quintus Potgieter
- Category: Industry
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear colleagues
There is so much to celebrate this week – Christmas, Hanukkah, Kwanzaa, Solstice or simply the imminent New Year. We, at IDC, would like to wish you everything of the best for the remainder of this year. We hope you find some time for a well-earned break before a prosperous 2010. (My wife and I kicked off the holiday season amongst the vines and alongside the surf in the south western corner of Western Australia - where the Great Southern and Indian Oceans meet).
I am very grateful for your wonderful support over the past four years. We now have 120,000 engineers and technicians throughout the world receiving this newsletter.
Here is one last, but brief comment for 2009, on a sometimes vexing, but very interesting topic.
Energize to Trip
Being from a traditional industrial automation background, I have always believed that de-energize to trip is the name of the game. One only needs to think of the emergency stop push button for a motor. The idea is that if the emergency push button is pressed or the associated control cable is broken, then the motor will be de-energized. No “if’s or buts”. Zero power! And thus safe!
But our Safety Controls guru (read his many books and articles), Dave Macdonald, gently chided me on Friday on the topic of de-energize to trip. His discussion below outlines another important option. From a simply intuitive point of view, as he pointed out patiently, when there is a failure, de-energize to trip is certainly not an option for a Jumbo 747, with 500 passengers on-board, 32,000 feet up in the sky.
Why, then, do we bother to learn about de-energize or energize to trip? Knowing the difference and their applications are vital, however, particularly with technology changes and the importance of keeping up with current best practice in the engineering world. So read on. What follows is a tight little tutorial which Dave has written with some vigour:
Safety instrumented systems protect a vast range of processes and machines against hazardous conditions. They perform safety instrumented functions (SIFs) intended to bring the operations to a safe state. The traditional and well proven approach to designing the circuits and device arrangements for any SIF is to adopt inherently fail-safe design principles which lead to a predominance of “safe failure” modes over the undesirable “dangerous failure” modes.
The principle of “de-energize to trip” (or DTT) ensures that for most devices the loss of circuit integrity through wire breaks or dry contacts or the loss of motive power in actuators should lead to the “safe state” of the process as soon as the fault occurs, even though the process itself was not in a hazardous condition at the time. For example, if you break the connection to a solenoid valve on an air-to-open spring loaded shut off valve it will snap shut; annoying the boss, but not risking any lives! These “spurious trips” are accepted as the price of fail-safe design unless the hazards or the financial losses created by spurious trips exceed the benefits to safety integrity. Then most designers will resort to redundancy for availability (“2 out of 2” or “2 out of 3” voting) if costs are justified for the application.
However, there are some cases where DTT principles are difficult to implement or justify. Energize-to-trip or ETT principles may then be more appropriate, despite their apparent risk of failure due to undetected circuit breaks or power failures. Fire and gas protection systems on offshore installations or in public buildings are one example where circuit breaks would lead to sudden deluges that would be just as hazardous as a fire. Situations where large numbers of Emergency Stops are used, such as for aircraft refueling points, may also justify ETT techniques because of the risk of frequent circuit breakages in the field, resulting in too many spurious trips.
Energize to trip is not as silly as it may seem because in modern SIS practice the two biggest drawbacks of ETT can be easily overcome. Line monitoring by low-power pulsing allows for continuous detection of circuit continuity on both input and output channels - giving alarm and response actions as soon as circuit failure occurs. No-break power systems have greater capacity than ever before and an important point to note about ETT systems is that they consume far less power if the inputs and outputs are de-energized most of the time. Hence battery back-up duration is greatly extended over continuously energized DTT designs; another reason for their use in fire and gas systems.
No-one would expect to build a relay-based logic solver stage on ETT principles, but this issue falls away as the majority of SIS logic solvers are now based on safety-certified PLCs which in turn bring greater diagnostic capabilities for sensing malfunctions and circuit breaks in the input and output field devices. IEC standard 61511 (Functional safety – Safety instrumented systems for the process industry sector) does not preclude the use of ETT principles where the user decides that this is justified, but does not offer any significant advice on the subject.
The technical obstacles to using ETT methods, therefore, have fallen away, but the basic principle of simplicity dictates that DTT principles are always going to be the first choice until a practical obstacle or a severe cost penalty arises.
Thanks very much, Dave, for an excellent article. Most appreciated. Any feedback will be published.
Preferably not, but as John Galbraith, the famous economist, remarked ruefully:
“If all else fails, immortality can always be assured by spectacular error”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
As the festive end of the year approaches – the season for giving, it is a great time to examine how we can use our engineering skills to do something for our fellow world citizens living in poverty. A billion people do not have safe drinking water, for example, and two billion do not have adequate sanitation. Outbreaks of avoidable disease and a high death rate result. An inspirational engineer in this regard is Amy Smith of MIT. She and her hundreds of mechanical engineering students work on real projects applying simple technology to help the rural poor. She is driven by the need to help the billions of people struggling without the basic requirements for survival; safe water, sanitation, enough food and a place to live – things we take for granted. Some of her recent projects have included a high pressure, hand-press for making charcoal briquettes from sugarcane waste, a vibrating compactor to make bricks from soil, a bicycle-powered, chlorine generator to purify water and batteries made from aluminium cans, charcoal and salt water (the last one sounds rather suspect, but there you go). She avoids foisting high flying advanced technology on the locals, but tries to give them an achievable skill base to enable them to create their own solutions.
As you well know, western-style technology is reaching out and touching all corners of the globe: In the poorest villages you will find an internet café somewhere. Afghanistan had 15,000 mobile phones in 2002, now that figure has grown 40-fold. And solar panels are stuck haphazardly onto the thatched roofs of huts in some Kenyan villages.
However, much of western technology and engineering is simply not appropriate for poor countries. Large western-style projects (infrastructure such as power stations and gigantic dams) have often not delivered to the poor, but instead caused further hardship including displacement. In fact many western technologies are simply bad news for the poor - highly sophisticated manufacturing plants, for example, can’t run without a sophisticated supporting infrastructure and skills base. And chemical pesticides on farms require strict health and safety rules which are ignored due to language and conceptual difficulties. I don’t think our focus should be on blame, however, or finding these failures convenient reasons to give up. We need to look aggressively for workable alternatives. Another consideration and challenge in developing countries is cheap and abundant labour - so western style, capital-intensive, automated manufacturing requiring minimal labour just doesn’t stack up.
I have listed some successful micro-projects in engineering to give you an idea:
• A machine to turn industrial waste into roof tiles
• Solar powered ovens
• Micro-hydroelectric plants on small rivers
• Solar water heating
• Machinery to turn weeds into paper
• An elephant pump – drawing water up from a deep well using plastic washers knotted to a loop of rope running through a pipe
• Eco-san toilet which doesn’t require conventional sewer systems
• Solar powered lanterns for lighting homes and villages
A few suggestions:
• Look for ways to apply your engineering skills appropriately in poorer countries
• Encourage your colleagues to do the same
• Transfer your engineering know-how freely to others
• Mentor students and people from less advantaged backgrounds - especially from poorer countries
• Encourage your universities and colleges to embark on projects in countries where people are disadvantaged
• Actively look at how you can simplify your high tech products and services to make them applicable in more rural, low-tech environments
• Support your local engineering association’s efforts in this regard (e.g. RedR)
And so, my fellow engineers, to modify John Kennedy’s famous request: Ask not what your engineering skills can do for you—ask how you can apply them in the service of your fellow citizens throughout the world.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Whilst on a ship a woman enquired of Herbert Hoover (who later became US president in 1929) what he did for a living. His reply; “I am an engineer”, to which she responded; “But I thought you were a gentleman”. Attitudes to this profession and the practice of engineering itself have, however, changed considerably over the past hundred years. Although the science of engineering remains in motion (some of these trends are outlined below) there is no doubt that there are some constants, such as the need for strong skills in maths and science (and the associated necessity to be meticulous and precise). The ability to troubleshoot and transform mere ideas into real and useful objects is also essential.
With the inevitability of change in our vocations it is clear why we need to be ‘obsessively’ multi-skilled and highly receptive to and embracing of new ideas and approaches. There has been a merging of professions including mechanical, electrical, IT and others that surface every so often. This constant state of flux is exceptionally challenging and merciless - where engineering professionals have been resistant to change they quickly find their skills redundant. A colleague of mine - a technician working in the industrial data communications area - refused to move beyond RS-232 and RS-485 and into the realms of Ethernet. He reluctantly retired.
Sujeet Chand, from Rockwell, remarked that the constraints and considerations when designing have become more complex. He was referring to issues such as energy efficiency, cost, climate change, safety and ergonomics. He pointed out that the need to be adroit in dealing with these was becoming more critical.
We must collaborate widely and communicate constantly and well. This is often essential in a virtual sense too (through email, the web, web and video conferencing), with different cultures located all over the world. Furthermore, there is a merging of collaboration with people and the resources on the web, as all information is available on the web in a searchable format. As a result very complex designs can be put together quickly.
The outsourcing of non-core functions has often seriously emasculated engineering companies with the loss of great engineering talent. These companies are reduced in their abilities – often only able to repackage old technologies. Eventually this limited scope fails in our highly competitive market.
A lot of the very satisfying hands-on experience is no longer with us. James Truchard, of National Instruments, remarked that in many cases the mathematics has isolated us from grounded reality - we have lost the need to and ability for intuition due to this high level of abstraction. Fortunately, with the new approaches to simulation and the realistic representation of simulated data, we can move back to the hands-on, intuitive approach again.
So, to weather these winds of change we need to:
• Strengthen our communication skills in collaboration with other cultures and engineers from around the globe.
• Strive to retain the hands-on, intuitive approach to engineering using the new
3-d simulation approaches.
• Embrace multi-skilling and regard engineering as one vast interlocking field.
• Be wary of outsourcing and losing core resources and functionality.
• And, at the risk of sounding obsessive, keep learning and absorbing
Thanks to Terry Cousins of TLC Software and Machine Design for giving me the incentive to write this.
Here is a brilliant quotation from Christina Baldwin (as in my stolen title):
“Change is the constant, the signal for rebirth, the egg of the phoenix”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear colleagues
In these rather challenging times, it is especially important to value yourself and to extract as much value from your engineering expertise as you can. It is also imperative, however, to continually assess yourself in terms of your ability to indeed deliver true value and improve your expertise. What follows are a few suggestions on how to build value into your engineering:
• Measure yourself honestly and objectively when you execute your day-to-day engineering tasks. This can be done whether you are simply doing maintenance work or engaged on a large project. Ask yourself whether you can improve on what you are doing – can you improve on quality, lower costs, deliver more quickly, and/or make safety upgrades?
• Look after your career. If the work you are doing is mundane and outdated and headed for a brick wall in terms of obsolescence, then actively look for ways to test and challenge yourself in another job or project.
• Leverage your abilities by working with professionals who complement your skills. A good controls engineer may find working with a great process or chemical engineer adds enormous value to what he/she is doing. Your knowledge base will naturally increase too.
• Avoid being declared mentally insane. The definition of insanity is doing the same thing over and over again. If you are facing the same project problems repeatedly (cost and time overruns, equipment failures, staffing issues etc); it is time to ask where the fault lies. Is it you, the project manager or the client causing the impasse? Respond honestly and fix it. Ensure you don’t get stuck again.
• Test and extend yourself in your work. Don’t be comfortable doing the same old thing and thinking in the same old ways .Move outside of the box. This can be positively uncomfortable, but will make you more valuable.
• Actively listen and learn from your peers. Don’t be afraid to seek their advice. Colleagues are a vast untapped resource of information and knowhow and can be enormously valuable. It is flattering to be asked and your colleagues will be more than happy to provide assistance and advise as a result.
• Thrive on failure. If you fail, honestly admit it and put forward viable solutions. You can only learn from this and even gain some respect (unless of course the failure is as a result of sheer incompetence). Carefully assess what went wrong and learn from the lesson. Build yourself up. You can’t be perfect at all time.
• Are you working too hard trying to accomplish something your colleagues do effortlessly? If this is the case, closely study what makes them successful and build up your expertise. “A bit of short term pain for long term gain” as the saying goes.
• Continuous improvement is the name of the career game. Constantly build value into your skill base. Be conscious of useful experience opportunities and knowledge that can be derived from your day to day work and from your peers. Be aware of training opportunities and books that you can read. Through this investment in yourself you can experiment with new approaches. No one else is going to.
• Complete an outstanding project loudly, but modestly. This is often awkward, but important and can be done, for example, through editorials. The result will initiate the building up of a “brand-you” so that others are aware of your success and expertise and will call on you to assist in future projects.
• Always maintain a strong ethical and principled approach. You may be tempted, at times, to take a short cut or ignore poor work; but above all stick to the highest standards of the profession.
Your engineering abilities are critical and will distinguish you in a team environment - as noted by Mitchell Caplan: “To succeed as a team is to hold all of the members accountable for their expertise”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear colleagues,
In 1902 CY O’Connor, one of Australia’s greatest engineers, constructed the longest pipeline in the world. It was designed to carry water from Perth to the desperately dry goldfields. During the final stages of its commissioning the project faced some problems. CY O’Connor suffered some vicious criticism before committing suicide – he rode his horse into the surf in Fremantle. Doubts were cast on whether the pipeline would work and there were unfounded rumours that he was receiving kickbacks from contractors. His only fault was that he was a perfectionist and brilliant. The pipeline opened shortly after his death and operated flawlessly. It is still operating as a lifeline to the region a hundred years later.
I am not suggesting that anyone will get this despondent. But let’s face it, we all enjoy ups and have to endure some enormous downs. Inevitably there are times, through an engineering career, when things can get extraordinarily difficult – a natural cycle. What we have to guard against, however, are feelings of being overwhelmed - when the cycle fails to move on and where work responsibility is taken too personally. The fallout includes engineering without rewards and a negative impact on our personal lives too. The likely manifestation at work (and at home) includes; procrastination, isolation, apathy, disinterest and bitterness.
Engineering is particularly tough: We are dealing with real equipment, which has a finite life time, and our designs can have unpredictable results because they take on the natural world. Furthermore, we have to deal with the financial and management types who insist on technical compromise. We often have to limp along “making do” with older or cheaper equipment.
Some suggestions to avoid self-sabotage:
1. Keep your mind on your goals – engineering career and personal ones.
2. Stay firmly focused on the task at hand and in getting it finished.
3. Stick to your guns (despite the naysayers) if your engineering research indicates that you are right with a design or project.
4. Associate with positive engineers and technicians at all times, whenever possible. Avoid those who are negative and delight in failure.
5. Celebrate your personal successes and those of your closest colleagues.
6. Build your personal support networks. They will be essential when things are tough.
7. Support your colleagues when they are having a bad run.
8. Persist through the tough engineering times – take one step at a time and keep a cool head when everyone else is losing theirs.
9. Watch out for the hidden impacts on your life and keep yourself healthy and fit.
There is a poem that travels with me wherever I am in the world. I picked it up at some bookshop in London in the early nineties and it still motivates me. An extract:
When things go wrong as they sometimes will
When the road you’re trudging seems all up hill
……
And you want to smile but you have to sigh
Rest if you must, but don’t you quit.
…..
So stick to the fight when you’re hardest hit
It’s when things seem worse that you mustn’t quit.
Richard Denny
yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
You’ve just won a great contract but have to work in a team. Great, a technical challenge, but in groups! As engineering professionals this is not our best scenario. You may be outgoing and extroverted, but it doesn’t necessarily follow that you have good team interaction skills. Engineering projects today, however, are increasingly complex and need a team to succeed.
Teams are brought together for specific projects, with some of the group often operating out of offices oceans apart. Once the project is completed the team breaks up. Web based collaborative techniques (such as web conferencing) are making the interface between different groups seamless - one of the new buzzwords is the ‘virtual team’. An outstanding engineering team, including skilled design engineers from around the world, has a higher probability of getting an innovative product, of a high quality, to the market quickly and successfully. It is rare today to see a single engineer developing a product and getting it to market on his/her own.
Operating in a team requires many soft skills such as consensus building and co-operation. The added difficulty is the successful use of these skills with men and women from different cultural backgrounds. This is challenging, but encourages diversity of thought. Some even believe that in the past, with the predominantly all white, male engineer, products were compromised through the lack of consideration of size, weight or strength differentials, for example in women and children.
Personally, I have been on many unsuccessful team projects. I now know that if one can harness the full power of the team effectively, from its inception, great results can be generated quickly. This sort of team becomes iconic – one that everyone talks about for years. Remember, you can’t simply tell everyone to work as a team and assume they will work happily and harmoniously together. Practices and objectives can differ quite significantly between different team members and cause problems. Cost overruns, poor quality products and services and significant delays often result when a project team crashes and burns.
A few suggested ways to make your engineering team really work well (please send me your suggestions so that I can publish them):
Ensure outstanding leadership of the team. This is surely the most important (and often neglected area). A traditional leader, perhaps, but someone who is also enthusiastic, ensures everyone in the team knows everyone else, glues everyone together, extracts every ounce of ability from the team members and gives an overall vision of where the team is heading. The leader should handle the frequent setbacks with a Churchillian resolve to keep “fighting on the beaches” until the job has reached completion. Mediation of the inevitable disputes is critical and manageable with a wise, long term approach. Finally, some careful management is required to help the team navigate the trade-off between: as a team “you sink or swim together” against “every team member must be held accountable for their tasks”.
Drive deadlines hard. Team members must be clear about deadlines well before they occur and understand the importance of meeting these. Support should be provided in order to meet the deadlines.
Plan practically and hard. Detailed, practical plans are essential. These need to be understood and agreed upon by all team members and the resource availability clarified (watch out for writing software!).
Prioritize and compromise. All plans for the individual groups must fit together. Where problems with resources arise, priorities must be quickly revised and compromises made and clearly communicated.
Educate, train and keep improving. Team members (and the leader) should identify the strengths and weaknesses of everyone and where necessary provide mutual support. Identify the skills each person brings to the team and use these. Keep improving the team members’ know-how.
Communicate aggressively. Ensure everyone across the group is aware of the status of the project at all times – no matter how painful. Break down the silo mentality and ensure everyone communicates openly and often about how his/her particular part of the project is developing. Interaction between team members is vital to success.
Involve the client. Whether an internal company member or an outside party, the client must be constantly updated regarding the project progress – particularly when design compromises are made. Due to contractual issues, the client may be less than enthused with giving any tacit support, but listen carefully - this can be helpful.
Don’t take short cuts which compromise quality. Looking for improved ways of doing a job is positive. In the drive to finish the job quickly, however, short cuts may seriously undermine the quality or final product performance. It is best to do the hard yards.
Think of the other person before yourself. Try and understand the difficulties and challenges the other team members have. Provide them with thoughtful and unsolicited support as in any good partnership. This should not be your intention, but the reverse is likely to occur if you need help.
Cut out the rot quickly. When things go wrong or a team member is not playing ball; face up to the particular problem and deal with it quickly. Without quick intervention problems often spread and can impact on everyone in the team. The leader needs to counsel the disaffected team member, get him/her back on track or moved to other activities.
Nurture your team. As both a leader and team member, look after your team. This can be done through education, support and training. Help with problem solving difficulties. And whilst avoiding the “jolly hockey sticks” mentality, build up the esprit de corps and morale with positive activities. A team is a delicate thing and needs constant attention.
Face up to contractual issues quickly. If there is a variation developing, because of some team development or a client requesting change; communicate this to everyone immediately. Watch for team irritation and provide counselling where necessary. Ensure the client is apprised of the costs or project changes as soon as possible.
Measure – measure – measure. Whether you are the leader or a team member, track your progress in the project in terms of costs and time and obviously the real progress of the product or project.
A positive team experience means that you will be in even better shape for the next team project.
Two great quotations this week:
“To succeed as a team is to hold all of the members accountable for their expertise.”
Mitchell Caplan, CEO, E*Trade Group Inc.
“Players win games, teams win championships.” Bill Taylor
Thanks to Catherine S. McGowan of the IEEE for her interesting article which served as a timely inspiration for me.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Murphy’s Law is especially quoted in engineering and as most of you would well know the gist of it is: ‘If anything can go wrong, it will’. Often, we add: ‘And at the most inopportune moment and in the most damnable way.’ (A little unfair - the assumption: A malevolent universe).
The Law’s (supposed) origin is from an engineering blunder. A Captain Ed Murphy, an engineer at Edwards Air Force Base, was dealing with a technician who incorrectly wired a strain gauge bridge – he wired it backwards! The bridge was intended for gravity tests, but as a result of the gaffe it gave an incorrect zero reading. There is vigorous debate as to whether the engineer’s wiring diagram was at fault or the technician’s wiring. Whatever happened, the law is now firmly linked with Captain Murphy. Aside from the debate, however, the set-up should have been meticulously tested before being put into service to avoid what ensued.
I reckon this is a reflection of a fundamental principle of engineering where the lack of precision results in measurement uncertainty. We can never know precisely the value of anything to any arbitrary level of precision. At the sub atomic level, Heisenberg’s principle makes this point; the more precisely you try and measure the location of a particle, the less precisely you will measure its momentum (and vice versa when trying to measure momentum). This doesn’t reflect on our ability to measure, but on the nature of the system itself.
In Safety engineering, we do what is called a risk analysis where we identify what types of harm could arise from what we are planning to make or do. We can then establish the probability of the occurrence and multiply this by the severity of the harm (broken finger, to amputated arm) and we end up with the Risk. If the Risk is great enough, we can then apply a $ value to it and determine how much time and money to spend in reducing it to a tolerable risk. It is impossible to make anything unequivocally safe. So as far as Murphy’s Law and risk management is concerned, if you have conducted your risk assessment correctly, then you must expect that the consequences it predicts will eventually come to pass.
And remember: “Absence of proof is not proof of absence”. For example, with the ill- fated space shuttle, a proper risk analysis would presumably have shown that the foam chunks falling off its booster and damaging its thermal tiles would have correctly predicted the deaths and destruction of the craft during re-entry due to the defective tiles. However, NASA believed that because they had not seen such problems so far, they would continue not to see them.
So please continue to embed Murphy’s Law in your daily engineering life and constantly seek to minimise the consequences of risk.
With our constant litany of woe with IT stuff, I think we are all familiar with Murphy’s Computer Laws (Finagles Rules) – well, I certainly am:
What Every Computer Consultant Needs to Know:
1) In case of doubt, make it sound convincing.
2) Do not believe in miracles. Rely on them.
Thanks to Keith Armstrong for his illuminating article
Yours in engineering learning
Steve Mackay
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear colleagues
Thanks to all +120,000 readers for your suggestions - please keep them coming.
As you know with your CAD design work, working in 3-d is almost upon us. You would have noticed the upsurge in 3-d movies recently. High definition images have already become established as a standard and it is very difficult to see much more improvements possible to 2-d images (As far as the human eye is concerned).3-d is now the focus area with cinemas replacing the boring old red-and-blue glasses for 3-d movies with newer and more realistic technologies. Cinemas are delighted with the 3-d technology as this gives them a great advantage over home cinemas which cannot yet match the technology.
By the end of the year, we will see the first few laptop or notebook computers which can display in 3-d; the first prototype 3-d televisions and associated consumer good are already bumping into the market. Despite the inevitable lack of agreement on standards, many firms will be releasing 3-d products in 2010. Creating 3-d images can be challenging; the stereoscopic approach requires scenes to be filmed from two perspectives. Special eyewear ensures that each eye only sees one of the scene perspectives and the brain is thus fooled into believing it is looking at a 3-d image. Another way is using an auto stereoscopic approach (no glasses required) where tiny lenses on the front of the display direct images for each eye in different directions. When your head is in the right place, you suddenly see a 3-d image.
Obviously to date, most content is 2 dimensional; thus creating some challenges in trying to use the vast amount of existing materials. New software (and firmware), now make it possible to convert images from 2-d to 3-d, by using object recognition software to analyse colours and shapes and to work out distances.
The other tried and tested approach to creating 3-d images is the use of holography. Producing a hologram of a fixed object is a tricky process. Essentially, a hologram is a special interference pattern created in a photosensitive medium (such as photographic film). When the light strikes this pattern it is scattered in such a way that it is identical to the real object, thus allowing you to see a 3-d image without glasses.
So what are some of the applications emerging?
A French company has devised a 3-d hologram image of their remotely operated submarine for oil exploration companies. This uses video and sonar data to create the image and the operator thus has a realistic 3-d image of what to control, which he does by moving a cursor around inside the hologram.
An improved approach to radiotherapy uses a 3-d hologram image of the patient showing where the beam of radiation is being directed to in the body allowing more pinpoint targeting of tumours.
Engineers working in different physical locations can now examine the same object using 3-d video conferencing, again using holograms.
So how do we apply this to your engineering?
* Consider everything you are doing and how you can migrate across to a more realistic 3-d form – from simple drawings to full realistic scenes
* Demand 3-d from your software vendors to improve your processes?
* Consider extending static 3-d into a dynamic 3-d image with live plant controls and automation systems
* Examine how or whether 3-d can improve process safety/quality of your processes and effectiveness of your systems.
As Oliver Wendell Holmes remarked: “Man's mind, once stretched by a new idea, never regains its original dimensions”
Thanks to the Economist and Solidworks for references.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Every now and again, one gets a handsome return for your tax dollars (thank you America). If you are working in renewable energy or energy systems, there is a complimentary and brilliant program (Homer) you have to add to your armoury (even if you are only mildly associated with energy systems). See the end of the newsletter for further details (no, I am not selling anything – courtesy of the US National Renewable Energy Laboratory).
I drank four coffees at midnight last night while contemplating an interesting article by Peggy Hutcheson of the IEEE (thanks Peggy) on keeping yourself competitive. Contemplate, for just two minutes, where you are going with your career and what you want out of life. Work is, after all, a large chunk of your life. In your contemplation consider the following 3 areas: Your market, your brand and your legacy.
Your market
Keep an eye on your skills. Unfortunately they (esp. in some IT areas) are being commoditised at an alarming rate and are being shipped off to lower cost countries. A hardened veteran at Cisco made the following comment regarding their strategy in developing new areas of business in response to increasing competition: “Where there’s mystery, there’s margin”. This applies to all of us. Where we fear to tread is where we have to go in terms of career development. Currently job markets which are growing strongly include; security (software/hardware/process), project management, green energy and other environmental markets, virtual communication products and processes, bio-engineering and biomedical, infrastructure development (the stimulus packages) and industrial automation. By comparison, traditional electronics design is only growing in niche areas (where it is going gangbusters mind you, but to find these areas and sustain them….).
Small and medium sized businesses (including units within large companies) offer the greatest opportunities for work. The more entrepreneurial ones can be risky due to funding constraints though.
Review the way you approach your job. Update yourself with fresh new approaches and technologies. Apparently the definition of insanity is doing the same thing again and again – so avoid this. To think outside the box requires you to continuously educate yourself by talking to your peers, reading, reviewing new technologies and approaches, attending courses and ultimately experimenting with new approaches (many may fail, but persist with others). This will keep you from doing the same old thing again and again.
Thy Brand
You are the product you offer your employer. Think about what you really enjoy doing at work. Ensure your deep rooted areas of satisfaction in your work are aligned with the work you are actually doing. And ensure you come across as someone who is outstanding and leading edge in your career, someone making a significant contribution. Show passion and enthusiasm (yes – I use this word with engineering professionals) in all that you do. And be a valuable mentor to your younger colleagues.
Thy Legacy
An odd comment (especially if you are only mid way through your career), but how do you want to be remembered in your career? How do others talk about your contribution to engineering and the firm now? And on this point, tempting as it is to get involved; always avoid the good old office politics and back-stabbing, “who stuffed what up when?”. Always focus on the positives. One of the top electrical and control engineers I have ever known would wander away when office gossip began, particularly when it involved the criticism of someone in relation to a disastrous project. He may have been within his rights to join in as he always did an outstanding design job, even uncomplainingly and successfully picking up and reworking failed projects. He showed enormous integrity by not partaking in the character assassinations. Even though he is now in his late sixties, he is still being pursued by a dozen firms to do projects for them. The engineering professionals that leave great legacies (and are still in demand) are those that show enormous enthusiasm, positive leadership, pioneer new approaches and technologies and are able to smoothly adapt to the daily challenges in engineering (these can range from: “Boss, I broke it – what do I do now?” to “Our key engineering supplier has gone bust – we need to urgently rework our production line today”) and business.
Remember, as Phil Crosby remarked: Very few of the great leaders ever get through their careers without failing, sometimes dramatically.
Homer software download
HOMER, the micropower and energy optimization model, helps you design off-grid and grid-connected systems. You can use HOMER to perform analyses to explore a wide range of design questions:
* Which technologies are most cost-effective?
* What size should components be?
* What happens to the project’s economics if costs or loads change?
* Is the renewable resource adequate?
HOMER’s optimization and sensitivity analysis capabilities help you answer these difficult questions.
Home page (for downloading): http://homerenergy.com/
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Over the past few years we have heard a lot about virtual reality – computer generated worlds in which one can be completely immersed. Interestingly it has never quite fired up the engineering world. Virtual reality is obviously very prevalent in video games, but has not become overly convincing elsewhere (exceptions exist in very specialised applications).
A new hype, however, has crept up vigorously over the past year - augmented reality or AR. This is a concept I can see generating great results for us in engineering. Rather than trying to create an entirely new reality, digital information is merely added on top of it. This is not only much easier, but is certainly more compelling for us cynical punters. Augmented reality can be as simple as taking the screen of a mobile phone (which takes a reasonably accurate picture of the world) and adding digital information (such as text and graphics) to each item in the picture. This can range from labelling the mountains visible within a photograph to superimposing historical images on a renovated building to show how it looked 200 years before. Phones can even be used to locate…. say, an Indian restaurant in a certain area (although it would only locate those restaurants participating on the GPS system). Augmented reality (AR) technology enables one to mesh in the barrage of online data with the real world. AR has been around for many years, but the sudden advent of mobile phones with the capability of the following five items has made it workable:
• GPS (satellite positioning – a bit ho hum these days)
• Tilt sensors (we know all about these with our kids wii’s)
• Cameras (rapidly jumping in quality)
• Fast internet (pretty expected these days with the photos being shot off into hyperspace)
• And a very recent innovation – a digital compass (it knows where you are pointing it)
Remember, this does not merely pertain to a mobile phone - a PDA or pocket superportable computer (or even desktop computer if it has these features) can also utilise AR.
A clever AR application which has enjoyed widespread interest recently is Wikitude. As a tourist you can walk through a city and view the landmarks. A Wikipedia entry for each landmark (providing a detailed description of its history and other attributes) is immediately pulled up onto your mobile phone display. Apparently there are 600,000 Wikipedia entries linked to their longitudes and latitudes and the program looks for a matching set, based on those your phone pulls out with its GPS.
“Mildly interesting” you may remark, “for a consumer in a shopping mall or a tourist, but what possible impact for us in the engineering world?” But I can see a stampede of applications bearing down on us. Just think:
• Hold your digital phone next to a piece of machinery - a help screen jumps out to tell you how to service or maintain it.
• Glance at your phone’s display as it buzzes when you get too close to some dangerous process – it tells you that you need to be careful and indicates exactly what could happen
• Listen to your phone as it relays an alarm to you from your plant - it tells you where to look to fix the problem. The screen includes a picture which directs you to the problem source.
• Look through your PDA camera to see all the electrical cables and water piping laid out below it. Problems can be more easily located and more quickly fixed.
• Scan a city area to be excavated through your head held camera. By superimposing a model of the proposed trench on the physical landscape, pipes and cables can be avoided.
• Leave messages virtually tagged to the bits of equipment on a plant during your operation shift. When others wander around the plant pointing their cameras at the specific pieces of equipment, a host of messages will be downloaded and superimposed onto the equipment detailing any issues that have been previously encountered.
The mind boggles with the possibilities…..
And as for my earlier comments regarding my preference for reality over the virtual world - I must confess, I do love Albert Einstein’s (attributed, admittedly) take on reality:
Reality is merely an illusion, albeit a very persistent one.
Thanks to the Economist and wikitude for some interesting thoughts.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We are flooded on a daily basis with too much data and because we are in such a hurry we often don’t verify the truth of an assertion. This was brought home to me yesterday with the following exchange about damage to an aircraft (shown in the photograph below). An expert confirmed that the damage was created by a lightning strike and then made some interesting comments about aircraft and lightning.
Apparently an American Airline pilot took the photograph after the plane had suffered a lightning strike. One can see significant damage – a large hole burnt into the cockpit. The associated article goes on to say that lightning regularly strikes aircraft – the odds are that every airplane will be hit once a year. Lightning, however, has not directly caused a crash (at least in the USA) in more than 40 years. When a plane is hit, the lightning bolt merely flows along the highly conductive aluminium skin of the plane. However, 40 years ago there was a crash due to lightning: A Boeing 707, carrying 81 passengers, was struck causing the fuel vapour in a tank to ignite and explode. Systems were put in place, as a result, to prevent this from happening. In addition, all aircrafts’ electrical and electronic systems protect electrical currents from lightning damage.
But the real story and the facts....
Although the picture does represent real damage (no photoshopping here), it occurred on the ground and had nothing to do with lightning. It resulted from a cockpit fire that burned through the skin of the aircraft after external power was applied in preparation for a flight. Having looked at the pictures, one engineer - working in the area of lightning - remarked, despite the lightning assertions, that he was dubious as only an unusually powerful lightning strike could melt that much aluminium alloy. Furthermore, there should have been some distortion around the hole due to the speed of travel through the air and lightning’s electromagnetic forces. (Other photographs can be found on the link below).
So a few suggestions in your engineering work:
1. Check out anecdotal information, otherwise file it away as untested.
2. Trace and audit any data which you suspect is second hand - it may have been copied from another source and contain inaccuracies.
3. Use the ‘common sense’ test – this will quickly eliminate the faulty data or statement (as the airplane story indicates).
4. Be suspicious of any data or assumptions which appear to be ‘too clean’, predictable, smooth, spherical - nature is unfortunately unpredictable, jagged and bumpy.
5. Apply some quick calculation tests to your newly acquired data to see if it does fit
In the worse case, where the system is ‘infected’ with faulty data or assumptions, ensure you own up quickly and let everyone know so it can be rectified - this is the sign of a true professional - being honest about your mistakes.
Remember that in nature, as the venerable Mark Twain once observed with some exasperation: “Truth is more of a stranger than fiction.”
Those of you who want to view the pictures in more detail should go to:
http://www.snopes.com/photos/airplane/lightning.asp (the source of my ideas for this blog, for which I am grateful)
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
My good sparring partner, Luke Hancock, who is our IT guru, has kindly made some comments on the new Windows 7 due to hit you shortly (thanks Luke). I initially thought Windows 7 was a wondrous new environment fixing the Vista problems, but his take (below) is somewhat more cautious. Read on.
Microsoft will be soon releasing Windows 7, a new version of the Windows operating system. Industrial users tend to be hesitant about adopting a new operating system (with often very good reason), as their products are often centred on a specific operating system (mostly Windows XP). Previous releases of Windows have often caused many headaches with early adopters (see Windows Vista and driver issues), and these problems cannot be tolerated by industry.
Windows 7 seems very similar to Windows Vista – however there are a number of structural changes to the operating system to try to enhance the performance of the system. The minimum hardware requirements have not changed too much from Windows Vista, so a reasonably new PC should be able to run Windows 7 without too many problems. The one area where Windows 7 has increased is in the space taken up on the system drive – the 32-bit version requires a minimum of 16Gb, while the 64-bit version requires 20Gb free space. Compare this to the 15Gb of space required by Vista, and the 1.5Gb of space required by Windows XP Professional. Independent testing of Windows 7 as compared to Vista has shown a slight speedup for most tasks – somewhere in the region of 3-5%. The one area where Windows 7 has the edge on Windows Vista is in boot times, but again this will depend on the hardware configuration of the host system. For full results, please see this link.
Most consumers will be mostly interested in the update of the Aero window system to include some flashy new effects. The brush has also been taken to the venerable Taskbar, which has been redesigned to be more application-centric rather than window-centric. Other users will be interested in the inclusion of multi-touch and improved handwriting and speech recognition features, and the inclusion of the Windows Powershell scripting environment.
Windows 7 will be released in a number of varieties depending on your requirements. There are 6 basic levels, however most industrial users will be looking directly at the Professional, Enterprise and Ultimate versions. Windows 7 is also providing the basis for Windows Embedded Standard, and is heavily tied in with the release of Windows Server 2008 R2.
Multiple Processor Support
The Professional, Enterprise and Ultimate versions will both support 2 processors installed on a single PC. This limit does not include the number of cores present on either processor.
32-bit vs. 64-bit versions
Each of the three versions mentioned earlier will come in both 32-bit and 64-bit versions. 64-bit computing offers significant benefits for those systems that are expressly designed around using 64-bit applications. The 64-bit versions will also run 32-bit programs, but with a speed cost due to the overheads involved in the 32-bit compatibility mode. Also, many installations still require mission-critical legacy 16-bit DOS applications – with the 64-bit versions these will not run.
The final problem that needs to be considered in moving to a 64-bit version is the requirement for specific 64-bit drivers for hardware. For those running legacy hardware (such as data acquisition cards), this may be a deal breaker.
Windows 7 XP mode
Microsoft has enabled a ‘XP Mode’ for those customers with Windows 7 Professional, Enterprise and Ultimate. The required software will not come ‘in the box’ with Windows 7, and will have to be downloaded. The software is a version of Virtual PC with a pre-installed, licensed Windows XP SP3 copy.
Also, you must have at least 2Gb of RAM and a processor with Intel’s VT or AMD’s AMD-V virtualisation extensions to run the XP virtual machine. These include most versions of Intel’s Core2Duo and up, and also most of the AMD range post-Phenom. However, the XP virtual machine does not have direct access to hardware, and is only intended to support legacy applications.
Solid State Disk (SSD) support
Finally, Microsoft has made some changes to natively support SSDs, and to optimise their performance given their unique characteristics. This is important for industrial customers given the increasing penetration of SSDs into the industrial panel PC and automation controller market. These include:
• Reducing the amount of disk writes and cache flushes
• Disabling disk defragmentation on SSDs
• Disabling prefetching and similar technologies on SSDs
In short, industrial users will display the usual reticence in using a brand new operating systems until all of the potential bugs are ironed out. Given the extended period of testing and wide distribution of the Release Candidate versions of Windows 7, this may be a short period of time. As always, any migration to a new OS should be managed carefully with stringent testing of the system to ensure that it meets your specific circumstances.
Thanks to Amplicon and CIO Magazine for some ideas for this article.
Yours in engineering learning
Steve and Luke
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues,
Networking is now a critical part of your career. And it shouldn’t be when you are urgently looking for a job before the “work” roof caves in. Networking is also not just about career development. It is about building successful companies and making your engineering career even more successful. It is about keeping in touch on a continuous basis, seeking new contacts and being generous with your information and know-how to a rapidly growing circle of friends and colleagues. Admittedly, it does require a bit more effort than sitting slumped in front of your computer contemplating the latest design quirk or the fact that the contractor has messed up on the installation of the Profibus industrial network. So just a few minutes of your time below on making your engineering career a bit more secure (and more beautiful) and indeed, your company more successful.
Many studies have confirmed what we pure engineering professionals dread to hear. Well, those of us looking for jobs. The number one source of jobs are not advertised or secured by online ads, recruiters but simply obtained by word-of-mouth and employee referrals. Company executives tap into the company rumour mills to find low risk known people to fill their jobs. Even with today’s collapsed job market; the hidden network fills more new jobs than the internet or other posted openings.
So, sadly (much to my chagrin): It’s not what you know, but who you know (and who knows your fit to a job or contract opportunity) that matters.
Some ideas for boosting your engineering career and firm:
1. Stretch yourself out today beyond your comfort zone to people you don’t know. I know this is horribly hard for an engineer or technician to do.
2. Choose your connections for reputations and results. Help other people with suggestions for their business and career challenges. And ensure they know who you are and why you can help them. Even if there is no fit now; they will remember that quirky engineer that called them to make a suggestion on fixing the frequent power outages at their site or the complex control problem.
3. Use third-party referrals to get you into the front office past the nay sayers and bureaucrats. Use connections shamelessly to get introduced to others. Avoid unsolicited calls (unless you are brave), as a warm fuzzy personal recommendation always does the trick.
4. Don’t abandon your network when you have secured a new contract for your company or a new job. Keep exchanging notes and views on what is happening in your work community.
5. Keep yourself highly visible with a location on a web site/ blog / Wiki site or one of the social networks. Demonstrate on your web site your strengths, achievements and skills.
6. Be the guru. Ensure that you play a role in professional associations/chapters. Make your whitepapers (a few pages written in simple English) freely available to your industry with your details clearly indicated. Keep track with online networking groups and contribute vigorously. Write letters to editors and comment to authors.
7. Be generous with your knowledge and help. Always contribute more than you receive. Help your contacts with their careers and work challenges. Send them valuable technical articles and remember their special days. You will undoubtedly get enormous payback from this generosity.
Bearing in mind the ease of communication today with email,web sites and mobile phones, being a top networker will more than guarantee you long term success and security in your engineering career. Remember it is “not what you know but….”.
Thanks to Debra Feldman of the IEEE for the inspiration to write this article.
And remember as Jane Howard so aptly put it:
Call it a clan, call it a network, call it a tribe, call it a family. Whatever you call it, whoever you are, you need one.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
When you have a permanent job in a company, your income is pretty certain. In the real, but cruel world of consultant, contractor and contract, however, life can be considerably more complex and fraught with danger. If the contracts are not handled correctly you could end up considerably poorer, despite putting in an enormous number of working hours. It may be worth re-considering the different options as outlined below. (And at the end of this newsletter is an extract from our Project Management course - a bonus chapter on costs.)
Crudely and simplistically put, as a consultant or contractor, you can bid for work in three ways.
1. Fixed Price Contracts.
These arrangements lock you into a price. Generally, come hell or high water, this is the price you, as the consultant or contractor, get paid.
2. Time and Materials
You get paid for both your hours spent on the job as well as the materials supplied to the client.
3. Two-Phase Contract
The first phase - you get paid on a time-and-materials basis, during which time you define the job to both your satisfaction and the client’s.
The second phase - you actually perform the contract on a fixed price (or sometimes time-and-materials basis).
Fixed Price is a Gamble
If you know exactly what has to be done and how long it will take (and the project is actually achievable); then this is a great option. But if the outcomes are uncertain and the project is badly defined, this is a dangerous option. Sadly enough, many clients know exactly how difficult and risky a particular job will be, but go for a fixed price so that the risk is removed from their bailiwick. They are simply after a rock bottom price.
Interestingly though, on the other side of the coin, I see that many contractors go for fixed price contracts knowing full well that they will be able to “drive a bus through the contract”. There was a particularly tough case recently involving underground tunneling, with a fixed price contract. The consistency of the earth and rock had not even been established! The contractor, however, actually ended up getting compensated for his risk as he incurred substantial additional costs. The client wasn’t too enthused with the thought of lengthy litigation and the inability to use the tunnel for an extended length of time so after jumping around for a while, the money was paid.
In a situation where you are forced into going for a fixed price contract and the definition of the job is still a bit uncertain do the following: Ensure that you define exactly what you are going to provide in the contract in terms of hours and materials and the rate of compensation for a situation where the project specifications change. You may find that if you do this precisely enough, you will end up making more money from the variations to the contract than the actual fixed price part of the contract! This is a popular strategy followed by some control system vendors who bid very low fixed prices. Against fierce competition the jobs were won with the full knowledge that the variations would compensate them handsomely. If you, as the client, take on these fixed price jobs; you will have to spend an inordinate amount of time on the contract. You will need to define all the terms and conditions and contemplate all eventualities otherwise you are up for considerably more money than originally anticipated.
Sometimes fixed price contracts fail to work well for unexpected reasons. One particularly acrimonious job comes to mind. It involved the provision of advice to a client on a project to build a Gas Turbine power station. We defined everything extraordinarily clearly and ended up with a fixed price job. Unfortunately the contractor omitted the risk for writing the control system software and the client had an awkward choice at the end. Either let the contractor go bankrupt, but have an incomplete power station or pay more money for the unexpected variations the contractor hadn’t factored in (and thus keep him in business). The client ended up paying well above the fixed price. Despite this, a few months later, the contractor still went bust. This resulted in the client having to complete the job with the attendant risk now shifted onto her.
Theoretically, you can claim on variations to the contract, but this is always fraught with some negotiation and angst as the client is not often enthused with having to pay more. Remember, however, when a variation to the contract comes up bring this to the client’s attention and bill him at the earliest possible opportunity (no matter how awkward and unpleasant this is). If you delay until the end of the contract, you may run the risk of not getting paid.
And at worse case, as a contractor/consultant, if you cannot see your way to getting paid for the additional work you are doing, and can’t get agreement from the client, simply “up stumps” (as we say in cricketing lore) and leave site. It generally never gets better. It is best to face up to the reality of the situation and avoid your losses getting worse. At this point, you may find that the client can see that you are serious and may become more accommodating
Sometimes it helps to compromise
Clients naturally worry that, with time-and-materials contracts, they may be “taken to the cleaners” as far as the end price goes. This is a valid concern. Unproven contractors can get lazy and simply bill for every hour. Naturally this is a short term win - they are unlikely to be invited back on site again.
I would suggest that if both client and contractor are unsure then a two phase approach is always the best. Develop and agree on a good specification where the unknowns are clarified and defined for the first phase. A fixed price or well considered time-and-materials proposal can then be agreed on for the second phase. Let’s face it. At the end of the day, in the specialized world of engineering, it is important that we build up long-term, trusting relationships between client and contractor and that both parties get a fair return on their investment: Not too much. Not too little. Just fair.
New Fangled approaches
I worry sometimes about these new fangled approaches which involve alliances and partnerships between clients and contractors. They are a little like a partnership between God and the Devil. With superb management on both sides they can work out. Unfortunately, though, they often end up costing one of the parties far more.
Always remember that it is better to lose a contract if you are going to lose money on it. Finally, as Samuel Goldwyn wryly remarked: “A verbal contract isn't worth the paper it's written on”. Make sure all agreements are in writing, signed by the correct parties and can cope with project modifications.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We are delighted to announce that this week we have become an IEEE Education Partner. As you probably know, the IEEE is the world's leading professional association for the advancement of technology and has over 360,000 members throughout the world.
We have also produced a number of complimentary books over the past few months, including; Greatest Engineering Disasters, Crazy Inventors, Engineering Careers for 2009, Crazy Inventions, Impossible Engineering Jobs, Job Interviews and Technical Writing. See the bottom of this newsletter for details.
Being a bit of a cynic, I don’t have many engineering heroes. The inspirational engineer, Andy Grove (former chief of Intel, the microchip maker), however, must surely be one of them. He wrote a well known book entitled; “Only the paranoid survive”, reflecting on the difficulties in surviving and growing in business.
Andy Grove was a poverty stricken refugee from Hungary. He attended New York’s City College and then gained his doctorate in engineering from the University of California, at Berkeley. A book he wrote at the time - on semiconductors - is still a standard text. He then joined Fairchild Semiconductor, where he became the protégé of Robert Noyce (co-inventor of the integrated circuit) and Gordon Moore (the proponent of the law which states that the amount of computing power available at a given price doubles every 18 months). He joined them after they founded Intel in 1968. He became CEO in 1987 and finished off as chairman in 2004. During Andy’s reign, Intel was considered, for a time, the most valuable company in the world.
Why should we bother about Andy Grove? Well; I believe no matter whether you are a manager, engineer, technician or tradesperson, he has some important lessons for our careers and businesses. Although he is an outstanding engineer, he will be remembered as a daring businessman who applied engineering to business with incredible success.
Andy felt that every firm would be confronted, at least once, with the perfect storm -where internal and external forces conspire to make the existing business unviable. In a word; if something isn’t done quickly with your business, you are “busted”. This is probably true of our careers as well as our businesses. In Intel’s case, their core business was in manufacturing memory chips. The prices, however, had fallen to such an extent (with Japanese competitors driving them down) that it was uneconomic to produce them. The entire company (and indeed the two key founders) couldn’t break from the memory chip business. But Andy Grove decided to ‘bet the company’ on microprocessors and change what they were doing. This not only saved the company, but transformed the industry, driving (amongst other things) the low cost ubiquitous PC.
His second critical decision was to sell microprocessors directly to consumers rather than through the computer makers, as Intel had been doing. You may vaguely recall the ‘Intel Inside’ campaign. This drove the computer makers into an unhappy frenzy, but the Pentium chip ended up being a best seller. Some of you may also recall the minor flaw in the Pentium for certain mathematical calculations. Downplaying the problem was a major PR disaster for Intel; costing them a half billion dollars. Andy Grove reckoned, though, that this episode actually ended up supporting Intel’s transformation. He believed it resulted in the dramatically improved quality of manufacturing and acted as ballast against a similar occurrence. But overall, when Intel turned from a component maker into a consumer brand, it was a stroke of genius.
Andy felt that his early experiences as an undergraduate student at City College shaped his ideas in life and business. Hard work was rewarded and students and professors were equally treated. Questioning everything was encouraged. He felt, however, that his first job at Fairchild was a disaster. He felt that the company’s corporate culture was dysfunctional, elitist, backstabbing and lax. Senior executives strolled into the office late; whereas blue collar workers were fired for the slightest transgression. At Intel, he created a highly disciplined environment which attracted the best and rewarded results - with no double standards.
(As an aside and somewhat controversially, he feels that today, companies should use the patents they are granted rather than sitting on them.)
So what are some of the lessons from Andy Grove?
* Ensure that you watch for the ‘point of inflection’ in your business and career. This is the time to change what you do – particularly if it is proving uneconomic. Research carefully what the market is doing and then ‘jump ship’ as far as your current product and service is concerned. This is certainly what we have done in moving holus bolus into online web conferencing and production of e-courses - supplementing our old traditional methods of course presentation.
* Hard work, discipline and rewarding results in business (and indeed life) still generate enormous satisfaction. (Although one would question this with the travails of Wall St over the past few years).
* Encouraging a culture of questioning everything and treating everyone fairly is still a key to success for business
* A high degree of intensive knowledge and expertise is so absolutely vital in building a great business.
* Never accept the status quo, but concentrate on being a maverick in industry doing things differently and always questioning what you are doing.
* When things go wrong, it is best to ‘come clean’ soonest and use this as an opportunity to improve your processes and business
In this massively information rich and confused world, surely William S. Burroughs comment is valid: “A paranoid is someone who knows a little of what's going on.”
Thanks to the Economist and Dr Andy Grove’s book: “Only the Paranoid survive” for reference sources.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Since the early seventies, I have watched as engineering careers have morphed into five distinct types: ‘corporate’, ‘learning’, ‘contract’, ‘skilled global’ and ‘manager’. I would be most interested to know what your type is and naturally, make suggestions on what you think of my categorisation. I will conclude by making some suggestions on how you can take advantage of these trends.
I believe each category still exists today, but the last two appear to be growing strongly.
The Corporate Engineer/Technician
During the sixties and early seventies, engineers set themselves up for life with one strong company with a solid career ladder. There were reasonably slow changes in technology so what know-how one gained at university or college was applicable for most of one’s career. Quality was a desirable (and required) attribute in all work and budgets weren’t fought over with such intensity. Competition was minimal. The company invested in the engineer’s career development and looked after him/her. Engineers were sought after and valued - even through the regular recessions. This type is still around, but has diminished over time.
Learning Engineer/Technician
In the seventies, new technologies started to move in, especially with developments such as; electronics, automation, computer technology and miniaturization of components, being typical examples. Competition started to increase and budgets were under some pressure. The engineer and technician had to learn these new technologies or face redundancy (or a dead end job sometimes in the guise of management). Engineering professionals started to move between companies with 4 to 8 employers being the norm before retirement.
Contract Engineer
Competition started to become more vigorous and, in the mid to late eighties, there were continual blasts of corporate downsizing. Management consultants were being called in to, “re-organise and re-engineer the already re-organised” - as one UK engineer expressed to me with some bitterness. Many engineers and technicians, who were dumped as a result of these restructurings, started working on hourly rates as contractors or consultants. Loyalty to the company was lost and instead remuneration levels became the focus. Temporary and often lucrative contracts were given by companies who only wanted to offer temporary jobs for the life of a single project. ‘Bodyshops’ began to emerge. Engineers and technicians began to be hired out - where they were often short-changed by the sweatshop owners. Guaranteed career ladders became more uncommon and continuing education for engineers and technicians more limited. Large companies were able to avoid negative publicity when contract engineers were sacked - they were not “true employees” – merely temporary guests of the company! As a result many were deterred from becoming engineers and technicians as they perceived it to be an unstable career. And many left the profession and moved into other areas, such as commerce.
The Skilled or Global Engineer
A severe shortage of engineering professionals started developing in the late nineties as a result of the downsizing in the eighties. Many with expertise had been sacked (and then retrained in other areas) and others were simply not interested in the profession due to the tough education process, limited income and a sense that there remained some instability. This shortage was exacerbated by a big jump in infrastructure, mining, oil and gas and manufacturing projects and an economic boom. Salaries started jumping in certain engineering professions and engineers and technicians were back in demand. Paradoxically, however, there appeared to be considerably more demand for specialists. Employers made (temporary) employment conditional on engineers and technicians having the precise skill set they were after, for a specific project (and often fired the engineers and technicians whose skills weren’t considered relevant any longer). Furthermore, engineering professionals in companies found that, due to the severe shortage of expertise, they were expected to multi-task, work longer hours and have a wide range of know-how. Technology change continued to accelerate and engineers /technicians began taking on work on a global basis - including work with virtual teams spread around the world. Due to the shortage of engineering expertise and downward pressure on costs, outsourcing of engineering work accelerated. Companies, however, found that the old adage; ‘Pay peanuts and you get monkeys’ remained true - under paying engineers and technicians, doing sophisticated design work in certain third world countries, just didn’t work (and actually cost more).
The Manager
Becoming a manager became a popular career choice. This was due in part to the uncertainties in engineering, but was also as a result of the perception that a career in management was the path to a quick buck and a relaxing career. University business schools perpetrated this myth through their misleading marketing. Many engineering students came to believe that they could be transformed in a mere 10 to 12 months. They thought they could break out of their technical shackles and join their more laid back and easy going peers in human resources, finance and administration by following this path. However, the salaries of the ‘Global Engineer’ often surpassed that of ‘The Manager’ - leading many ‘Managers’ to question what they were doing in the corporate environment. However, it must be said that the successful engineers with management ability (and perhaps an MBA), who set up their own businesses, were often extraordinarily successful - creating everything from industrial software to precision manufacturing and employing thousands of people.
So where do we go from here?
You need to become a professional career planner and take ownership of your career on a day-by-day basis. Watch the career trends and avoid being stuck in a dead end job. It sounds like a very lonely world, but no one – not your husband/wife/partner or business associate - is going to do this for you. In the fifties, as a corporate engineer, perhaps you were cared for. This is unlikely these days. If you fail to map your career out you may pay an enormous price in the years to come; with loss of earnings and even worse – loss of job satisfaction. Once you have identified who you are and where you are going, keep firmly to your course using a good compass.
You have to become an avid learner. Not only by absorbing information from your peers, on-the-job or from courses, but also by becoming adept at working with ‘meta-knowledge’ - managing information and knowledge. Know where to find it and have the ability to identify it when it is found. It is not always necessary to absorb and become skilled in the actual know-how, but it is important to ‘know where it is and what it consists of’.
And dare I say, plan for a time when you may be unable to work any longer, due to health reasons or a bad economy. Unpleasant scenarios, but realistic - I hope instead that you work happily at something which is fulfilling and financially satisfactory until you depart this ‘mortal coil’.
Thanks to Vern Johnson of the IEEE for inspiration for this article.
Jeff Foxworthy had an interesting take on his career, but is not my advice to you: “My whole career can be summed up with 'Ignorance is bliss.' When you do not know better, you do not really worry about failing”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
From: Kevin Kelly and Coleambally Irrigation Co-operative Limited
Some interesting comments from Kevin Kelly
Thanks very much for your thoughful commentary and insight here, Kev.
______________________________________________________________
We were involved at the leading edge and have spent a bit of time at the bleeding edge implementing irrigation open channel flow measurement. Thankfully the technology has been retained in Australia.
Regards,
Kevin.
Steve,
As always, interesting to read your latest thoughts.
The leading edge is where the creative juices flow, where ideas are created, where those who are a little eccentric imagine how things could be better for all of us. Where those who do not know that it can’t be done; go ahead and do it because they were not aware that it could not be done. Ideas are freely exchanged with those who share a passion for new knowledge.
Just a short distance behind the leading edge is the bleeding edge. This is where the practical, technical people try to do the things, that now can be done. Prototyping, product testing and development require clever people who enjoy their work. Tweaking, fiddling, adjusting and making things work. Lots of fun, lots of grief, lots of learning.
Back behind the bleeding edge is the “Feeding Edge”. Where the marketing consultants, lawyers, contract patent attorneys and others who feed off the innovators; accumulate and feed and grow big and fat. No new ideas created here. Lots of theft of intellectual property, industrial espionage and buying up struggling start-ups. There is lots of production of product by those at this level but also lots of secrecy and protection of turf. Many big USA companies inhabit the “Feeding Edge”.
Perhaps we should ask ourselves,
“Why is there a Bleeding Edge?”
Kevin
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
One of the joys of an engineer is the opportunity to work on cutting edge projects – particularly when you are leading the way. Another is working on a ‘greenfield’ site - starting something completely new (instead of salvaging a failing project begun by others). These opportunities, however, are very rare these days. More commonly we tend to be involved in either tacking on an additional facility to an existing site or simply doing some small improvement to an existing product design. Particularly now, with companies being somewhat risk-averse.
As engineers we dream of bringing something technically revolutionary to the market and changing the tide of human events - truly fulfilling our ambitions as engineering professionals. You only need to think of Marconi with radio or Steve Jobs with the Apple microcomputer to envy the satisfaction they must have felt when achieving these engineering wins. Another couple who come to mind are; Stephenson with the Rocket steam engine and Vint Cerf, the father of the internet (who co-developed TCP/IP).
But picking technical winners is an exceptionally brutal business. Technology forecasting is fraught with disaster. One only needs to think of some of the debacles for the dream bubble to burst. Remember the huge sun-reflecting satellites which were to bring light to the dark parts of the earth (NASA forecast that this would be achieved by the mid ‘70’s); or human cloning by 1985, or newspapers delivered by fax by 1978, or superconductors being a billion dollar business by 1975, and, interestingly, the internal combustion engine being dead as a dodo by 1980.
Why technical forecasts fail
Why most forecasts fail may be as a result of the tendency to get swamped by the sheer technology wizardry. We make the assumption that this must be the “next great thing”. This is particularly dangerous when we see people clamouring to adopt it. I shudder when I think how the media jumped onto the Internet with overwhelming enthusiasm in the late nineties with the truly spectacular juggernaut that formed here. We are all familiar with that crash. Often new forecasts are reruns of earlier ones. Or are simply fads which everyone eagerly adopts with no real economic or technical logic.
On the other hand, new technologies are often simply delayed because everyone has invested so much in the existing ones. This slows down new innovative products being introduced - think of Microsoft Windows, for example.
Unexpected “disruptive technologies” can shorten life cycles of numerous products. One only needs to think of solid-state technology which rapidly knocked out electronic valves in short order.
A market tipping one way or another is often difficult to predict – a great example here is Sony Betamax (surely, technically the superior product) being overtaken after a long 30 year war of attrition by VHS video tapes.
Thus - don’t be an engineering pioneer
My take on all this is this: It is extremely dangerous to be the pioneer in any field. If you look at the history of technology, there is no doubt that we admire the technology pioneers (and in many cases they are remembered) – whether it was for the first steam engine, automobile, radio, radar, microcomputer, internet or spreadsheet. However, most of these pioneers failed to have much commercial (and often outright technical) success with their products. They were often superseded by others who refined these pioneering efforts. You only need to look at the most recent example here (and I know you will groan when I mention his name); Steve Jobs and the iPod. For years there were hundreds of iPod equivalents before Jobs refined the concept and made it frighteningly successful. The same thing happened with spreadsheets (remember VisiCalc) invented by Dan Bricklin. These were replaced shortly afterwards by the Microsoft Excel as the de facto standard. Similarly, with the internet. The initial pioneers have been swamped by a flood of very successful companies ranging from Google to Microsoft who apply this technology so very successfully. The same applies to Dell Computers. Steve Dell tried the pioneering route, but after severe losses rapidly backed off allowing others to take this dangerous lead. He still does exceptionally well using this approach (being well behind the “bleeding edge”).
Some brave pioneers do reach the summit, with their perfect products; but mostly they arrive breathless at base camp and have to retreat, a little worse for wear.
In conclusion then
My thesis is this: Being a pioneer can be wonderfully satisfying, but, more often than not, the result is lonely and can be financially defeating. By all means watch the cutting edge developments. But come in later, with a great product which makes sound business sense and refines the pioneering technology. This will inevitably be after the pioneers have launched their products with all their foibles and problems and left the stage battered and bruised, There is so much inertia in the market place that you will have time in which to study the trends of the pioneering products and launch your success story (which may be a tiny refinement of the initial successful product). Doubtless, you won’t do as well as there will be a range of competitors coming in at the same time as you; but you will have a good solid venture which may last for many years. Until the next wave arrives, that is.
Above all, it is our duty as engineers and technicians to constantly innovate and improve. Otherwise we wouldn’t be true to our mission. So pick engineering winners, but keep well behind the leading edge so that you can optimise them with the best results for you and others.
Thanks to Donald Christiansen of the IEEE for his interesting article.
Remember as the Forbes journal once gloomily remarked: “When you get the urge to predict the future, better lie down until it goes away.”
Yours in engineering
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Some really great suggestions from the inimitable Ian McMillan on the 1st September 2009
Driving a good Engineering Presentation, but with or without Graphics?
Hi Steve
Me and my 2c-worth again. Good one, I quite agree. A picture is worth a thousand words, provided it's the right picture.
I use the gimp extensively for image manipulation - it's a Photoshop-type program, it's a free download, it's available for virtually every platform out there, it's unbelievably powerful, it's user-friendly and intuitive, and there's absolutely nothing shabby about it at all. gimp stands for "GNU's Image Manipulation Program". There have been many online debates about which is better, Photoshop or the gimp. I use the gimp on my Fedora Core 6 (Linux Box) for all my professional image creation and manipulation, from designing logos to developing security printing algorithms (I work in the packaging-printing industry). I think most of the guys that could really use it, don't know about it - maybe you could make a mention of it on your blog, even give it a road test if you want to? Just a thought.....
All the best
Ian McMillan
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We have all sat through interminably boring power point presentations, often riddled with the poor use of graphics. As engineering professionals we tend to stick to the technical side of things and avoid presentations full stop. However, there are times when they are unavoidable. Here are some really great tips that I have picked up (or stolen?), over the years, on how to use graphics/visuals, with panache, in engineering presentations.
There is no doubt that graphics are vital in a good presentation and can gain and retain attention from an audience of technical personnel. I get quite despondent, though, when I see graphics used wastefully and poorly and, more recently, the killer - the use of enormous tracks of video (which are often poorly explained or have very little relation to the actual presentation). Another dubious trick is to make extensive use of sound and animated graphics. Which, while initially entertaining, end up confusing (and ultimately boring) everyone. Unfortunately, there is no machine or software available to research, rehearse and make a dynamic presentation for you!
But there are a number of points regarding graphics which may be useful when you next have to get up and present. The keys to good graphics in presentations:
* Use them sparingly
* Make them big so that they can be clearly seen
* Make them simple so that they can be understood by everyone in the audience
* Avoid colours that can’t be differentiated from the back of the room
* Make them memorable, leaving a lasting impression
* And remember engineering professionals tend to prefer useful schematics rather than cute pictures of industrial plants and equipment
So why use Graphics in your Presentations?
* You simply can’t present slide after slide of text – this is too boring – graphics can be useful dividers of text and refreshers
* Graphics can be helpful when explaining difficult concepts where text is not up to the task
* Graphics are great for communicating symbolic points that you want remembered
* They provide useful prompts or props for talking around when discussing some concepts
* If used appropriately, graphics show your audience that you have gone to some trouble to create a really professional presentation to benefit them (rather than a bunch of text-ridden slides)
Cut out the Clutter (and noise)
Many graphics have an enormous amount of ‘clutter’ in them. One needs to apply the so called “three second rule” - if your audience can’t read and understand the graphic in this time; you need to simplify it further. Otherwise the graphic becomes a distraction – the audience focuses on the unraveling of the mysterious graphic rather than on the presentation content.
Ways of reducing clutter:
* Unnecessary detail should be removed, for example; grids and numbers
* The graphic should focus only on what you are discussing (this may mean that the remainder of the graphic needs to be eliminated).
* Numerical detail is confusing and too detailed - use a bar or line graph to get the point across
* Legends with graphs are difficult to read– label directly on the lines in the graph to minimize your audience flipping back and forth to the legend.
Give your Bulleted Sequences the Bullet
An endless stream of bullet points can be exhausting slide after slide. Be innovative – break them up with graphics. For example, draw a star and place the individual ideas at each point of the star - you still have text, but text which is visually represented. This is much more appealing.
Symbols and more Symbols
Symbols, to replace text, can make your message more memorable and at times more humorous.
Some examples:
* An electrical plug and socket for - “plugged into a concept or thought”
* An engineer swinging a bat for - “taking a swing at corruption/poor practices…”
* A rocket with the concept written on it for - “taking off like a rocket”
* A blindfolded person about to step down a manhole with no cover for - “blind to danger or safety issues”
* Kids building blocks for - “the basic building blocks in creating some new concept”
At the end of the day; however, ensure that an incredible graphic doesn’t take the focus from you and distract them from your message.
Thanks to Peter and Cheryl Reimold for some good ideas in writing this piece.
Always remember Alfred Montapert’s comment about the end game of visualization – you still need to do something : “To accomplish great things we must first dream, then visualize, then plan... believe... act”!
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear colleagues
There are many examples of products and companies developed during poor economic times - venerable companies such as HP, FedEx, CNN and products such as the iPod. Adversity spurred the creators on. However it is very rare to have a Eureka moment in design (the one when Archimedes purportedly ran down the street naked hollering, "I have found it!” – Similar to Steve Job’s comment at the end of this note). But innovation is a key element in driving any business or economy upwards and outwards, particularly in hard times. As Eric Starkloff remarked sagely, “Lean innovation occurs when times are tight and your resources are very thin and you need three items: Doing more with less; proving it fast and using your business, technical and social networks to the extreme.”
1. Do more with less. This requires using fewer engineering staff to achieve the same results. Perhaps by reducing your previous team of hardware designers, mechanical engineers and RF engineers to two electronic engineers and you. This does create significant hardship – the remaining few have to multitask and be multi-skilled or acquire new complex skills quickly. It may also require you to cobble bits of an existing design together, for example - not entirely optimum, but if it enables you to get a working system out there quickly then it’s brilliant.
2. Quick prototyping to prove the concept works. Once you can demonstrate a working prototype, your firm will be encouraged to support further work. This will require innovation – not only in your thinking, but also in your approach and in the tools you use. These may not reflect your ideal and may indeed compromise your standards; but if it enables you to get a demonstration product out quickly…...
3. Finally (and most importantly), I reckon it is something we as engineers and technicians don’t do enough of: Leverage and “work” our business, technical and social networks more. We like focusing on the technical side in the design and work. However, it is often the network that really builds value in very quickly. The ideal example is the iPod. It is a highly fashionable and clever engineering design, undoubtedly, but was created because of a network of linked-in hardware/software and content (the non-engineering bit) which was brought together brilliantly in such a way that the competitors were left gasping. Networks will also help you source the bits necessary to do item 1 above (“Do more with less”). This approach is cheaper and quicker than designing and building what is required yourself.
Other examples of engineering products built from networks must surely be the array of Microsoft products out there. Microsoft, with their software, have a great network with Intel’s hardware and firmware chips and an array (perhaps, reluctant?) of hardware and software partners producing interlocking products. They are all linked, but are being propelled along by the market, where the complete package is essential to the products’ success.
Another example of using networks and interlocking products must be the usual OEM story where a Gas Turbine manufacturer takes many of the components (PLC Control System/Vibration monitoring/SCADA system/mechanical components/electrical switchgear from a variety of partners) and provides a finished (but complex) product.
So my suggestions are;
* Actively build your business, technical and social networks. This seems a non-engineering thing to do particularly for shy engineers, but is essential to your career and your firm and indeed to your product.
* When you are designing anything and are looking to build enormous value think outside the box and use your network
* Think of building value as you would with Lego blocks. The more interlocking bits you can find which match an overall real need; the further you will be ahead of your competitors and the more resilient your product will be to change.
* Persist with your approach and networks.
I think this comment from Steve Jobs, CEO of Apple, is so true particularly the last bit which has been italicised:
Innovation has nothing to do with how many R&D dollars you have. When Apple came up with the Mac, IBM was spending at least 100 times more on R&D. It's not about money. It's about the people you have, how you're led, and how much you get it.
Thanks to Eric Starkloff of NI and Electronics News for your intriguing article from which I have gleaned my ideas.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We have created a few more short videos (in 5 min segments) and associated book chapters on PLC installation and Programming.
It is clear that we are not in a boom time at present. Many of the more entrepreneurial engineers amongst us have either been moved out or move out and set up as independent consultants. Or you may head up a division of a company where one of your many responsibilities is ensuring good cash flow. Or you are selling your much-in-demand skills after hours - moonlighting. You may think that working for large companies means you don’t have to worry about the issue of money. But sooner or later, “being paid” will confront you. In these circumstances, you will be exposed to the inevitable rogue clients who will use your good nature as an engineer or technician to take advantage of you. And as my old business lecturer used to tell us: “Remember – Cash is King”. Massive company profits, but no cash is far worse than company losses, but cash in the bank.
Essentially, your priorities are few in consultancy: Get business/do the work and get paid. Most books about consulting ignore the “getting paid” bit - as it is the most unpleasant part, the part we as engineers tend to avoid talking about. We have an inherent belief that our client is the ultimate “good guy or gal”. Getting the business is great, but getting paid is crucial. And let’s face it: most of us only charge moderately (and often discount massively) for our services; as we tend to focus on the technical aspects (“Do I like doing this work” is the key decider often for engineering professionals?). Incorrectly, I might add. But as engineering professionals we generally aren’t greedy. We are the archetypal good guys and gals focusing on a good quality design and project outcome; but not on payment issues. And this is where the problems start…..when you have a problem client. Read on….
Spot the problem child/client
A few suggestions on clients who may be problematic in terms of paying you for your honest work. Attempts at avoiding payment are likely from:
* Small or medium sized companies controlled by an owner who has a big stake in the profits
* A large company with the executive tied to the profitability of your project you have been working on
* A company which has cash flow problems (often due to poor management)
* An entrepreneurial company which lurches between largesse and large losses
* High risk projects where the business results are uncertain – but the client wants to hold you responsible for his decisions (and cash flow)
When payment is due; don’t dilly dally
We are always embarrassed as engineers and technicians when a client is late with payment. Should we call him/her? The answer is yes. Immediately. If you delay; you could end up in a far worse situation and set a precedent for slow future payments. Don’t let the amount owing to you build up to significant amounts. You may find it impossible to recover from this situation as you will now have joined the bank in financing the client’s day-to-day activities (his working capital), where he uses you. And if the no payment situation persists for a few weeks; deal with the situation head on. Perhaps (dare I say) get the debt collector onto the client as soon as possible and write off this fee (and client).
The check (or cheque) is in the mail
Watch out for the situation when the client chases you up at the end of the project to finish as soon as possible, but you haven’t been paid yet.
The client will assure you that you will be paid soon; the check is in the mail; they have lost your invoice – please resubmit; the manager who normally signs is ill or out of town. Don’t hesitate. Confront the client immediately and if nothing satisfactory is forthcoming - stop work immediately and remove all valuable supporting equipment / materials / software from site. Show the client that you are serious as you are in a difficult situation.
Watch out for exotic and faraway places
Your risk of not getting paid jumps significantly when doing work at remote locations. No matter how much money you are going to get paid; it is important to weigh up the risk. The client knows this and may decide to play games with payment if you are thousand of kms away. It is best to avoid doing this work unless you have payment guaranteed. Furthermore, the remote location may have a questionable legal system (if you are forced to protect your rights), let alone morals and ethics which may not align with your own.
Don’t give away the house for free
Sometimes you are tempted to do the preliminary work for free. So that you can get the job. Be very wary of this approach. It shows a distinct lack of respect for you as an engineering professional.. And often your design gets given to someone else to use as a starting point (for free) or you get treated poorly later on in the project.
Don’t persist with poor clients
As with personal relationships, if your partner (the client) treats you with disdain as far as payments are concerned or haggles about rates; don’t continue the relationship. Things never get better – they tend to worsen. Move onto others who respect you and want your skills. Your time is too valuable to waste on these issues and indeed life is too short to “drink bad wine”.
Variations are critical to deal with now
Many years ago I worked for a bunch of consultants who were always keen never to rock the boat with a tough mining client. Whenever a variation came along for the work he wanted done; they insisted I didn’t pester the client for a variation order (because he used to shout and scream and throw things around the office). Two years later, at the end of the job; when we confronted the client with the string of variations, he was horrified with the significant dollar value and only paid part of the total bill. The (competing) consultancy company, who worked with us on parts of the project, used to confront the client with the variations immediately and secured his signed assent. At the end of the project, they received the full amount for their work. We didn’t. They were hired by the client again for the next project as he respected their frankness and knew where he stood financially all the time. We weren’t.
So - if your client wants to make any changes to the project’s scope; make sure he signs off on the change the minute it occurs and knows exactly how much it will cost him.
It is your professional duty to protect yourself
When commencing any project, it is perfectly reasonable to insist on advance payment to cover your costs before you get paid. No worthy client will have a problem with this request. If a client does play games here; be very suspicious.
And remember; when you are wondering if you will get paid or not, Robert De Niro’s favourite dictum comes into play: “When there is any doubt, there is no doubt”.
Thanks to the IEEE and Nathan O. Sokal for the inspiration to write this article.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Let’s face it; if you haven’t got one; at least one of your colleagues has. As an engineer or technician, is it a worthwhile endeavour? - A year or two involving a potentially jaded professor providing you with potentially questionable concepts?
There is no doubt that currently, MBAs have an uncertain reputation with employers. And the quality of MBAs offered range dramatically from the outstanding to the ghastly – there is absolutely no comparison in worth between a Harvard MBA and one of these strange creatures cobbled together by one of the more provincial universities. But even with the Harvard MBAs you have all heard (to distraction) about the Wall Street MBA pack who have destroyed companies and economies with gleeful abandon (whilst protecting their own back pockets, of course).
At present, MBA programs take on huge numbers of …. Let’s call ‘em kids - with absolutely no work experience, but huge egos and ambitions, who then, on graduating, expect to command the Star Ship Endeavour in business enterprise. The result invariably, on taking strategic control of a company, is to plunge it into enormously destructive downward spirals. Or as a result of ineptitude get safely sidelined. Certainly, 30 years ago, achieving an MBA guaranteed you a massive salary increase. This was much to my bemusement as I could never work out how one or two years in a classroom could suddenly justify a 30% (or more) salary increase. One’s skills cannot be that much better after achieving an MBA. Today these massive salary increases are rare. Unless, however, you go to Harvard or Wharton and then become a Wall Street banker ( a beleaguered and somewhat destructive species as we have all come to know).
I am sounding horribly cynical, but I do have some personal experience having completed an MBA 30 years ago at a fairly prestigious university. Whilst most of my cohort was honest and ethical I notice that 3 have been jailed for fraud and two have bankrupted their companies. One has done exceptionally well, however, selling Hong Kong property – but even this is a questionable contribution to building an economy.
Part of the problem with MBAs is that it would appear that most of them have become increasingly oriented around the theory of management and its research and less on real world approaches such as leadership, accounting, ethics and business law. Harry Mintzberg, one of the current outstanding management thinkers, feels that MBA education is failing as the courses tend to focus on the so called “science of management” rather than on the real issue - that it is really an “art and craft”. He also expresses the concern that management training has focused erroneously on short term profits and ramping up share prices. Managers need to learn from their own experiences instead and realize that reducing management to a purely scientific endeavour is missing the point. Another concern is that many of the lecturers and professors populating the business schools have little or no experience in the real business world. At least with mature age students, their work experience is brought into the mix when studying for a MBA.
One aspect of the MBA which I did find useful was the case study approach. But there seems to be a trend away from the use of them and a move towards the scrutiny of hypothetical business situations. This is sad as I have always found real world case study discussions enormously useful and the resultant debate with students a great learning experience. (Incidentally, I often wonder why this approach cannot be applied more extensively to engineering).
On the other hand, there is no doubt that engineering professionals are often short changed when working for businesses. They often work long hours and put in significant creative effort in technical areas. Despite this they have little opportunity to move into more (even technical) managerial positions - often getting bypassed by smart kids with commerce or legal degrees (or even with human resources backgrounds). Some sort of management prowess is essential, therefore, to survive and grow careers - especially in businesses where the technical paths have dead-ends.
There are many examples of engineers who have done MBAs and who are enormously satisfied as they have gained a greater perspective of business and improved their careers (and even their personal lives). Before tackling their MBAs, however, substantial engineering experience is usually attained to derive greater career benefits. On their MBA programs another great benefit is their interaction with other outstanding engineers and professionals from law, commerce, marketing, HR, accountancy (and even medicine and divinity).
What should you do?
* If you feel an MBA is for you; ensure you go for an outstanding one which focuses on art and craft and is of a high quality with staff who have demonstrated real business experience
* Look at the MBA as providing you with the skills to deal with business and not necessarily providing you with a greater salary
* Ensure you get into an MBA where you can interact vigorously with your peers in the other disciplines such as Law/Accountancy/Business
* Ensure the MBA helps you break down the barriers and build up key competencies and confidence in the other disciplines such as accountancy/law/human resources/logistics
* Think about an MBA as giving you the skills to set up your own business
* Tie in the MBA closely to your technical skills to maximize your leverage
Unfortunately, I really believe that a lot of business experience and indeed, commentary is ‘reflected’ by Warren Buffet’s comment: “In the business world, the rear-view mirror is always clearer than the windshield”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Through my observation of engineers and technicians over the past 30 years I have discovered that certain traits or habits make them successful - very successful, in some cases. I believe that we can all become extraordinarily able through the adoption of these practices. Thanks to Buckbee and Covey for the inspiration to write this.
1. Know your Process, Operator and Client/Customer
Firstly, before you can commence engineering a project you need to have an in-depth understanding of all aspects and angles of the project that you are working with. If it is designing a better control and instrumentation system you need to understand the process intimately. If it is for the electric distribution system for an arc furnace; you had better understand the characteristics of the metal you are arcing and the resultant harmonics.
Secondly, naturally you have a client with a set of requirements to be considered and facilitated. For example, she may want you to build a wind turbine for renewable energy, but is also concerned about the plight of a particular breed of bird in the locality, on the verge of extinction, which may be hurt in the turbine blades.
Finally, if you're designing a wonderful engineering system you will probably require an operator to use it. You need to understand what his needs are. The operator generally knows far more about how the process behaves (esp. at 2am) normally, abnormally and during failures. Sometimes the operator and the client are the same – for example, Steve Jobs when designing the iPod had to consider an unpredictable teenager (client and operator) making peculiar demands on the hardware
This all takes an enormous amount of effort and time. But there are no short cuts here. Failure to adequately understand the process, operator and customer is effectively the same as building a house of straw (rather than with mortar and bricks); We all know what happened to the little pigs when the big bad wolf came calling.
2. Be Proactive with your Engineering
Unless you drive the engineering project and your team the project will never reach completion. It is essential to be constantly on the lookout for problems and their solutions. It always amazes me that even the tiniest issues can hold up an entire multi million dollar project - a screw or chip missing, or an unsecured wire.
Always apply the maxim - “when there is any doubt; there is no doubt” - when engineering something. If you suspect the HVAC design hasn’t taken into account the amount of dust in the air or the PLCs have a memory sizing problem, then check check check. You will no doubt find that your worst suspicions are correct. An apt quote from Andy Grove of Intel (the almost chemical engineering founder): “Only the paranoid survive in engineering”. (He actually referred to business in the original quote).
Being proactive means that you need to be committed and have a passion for what you are doing in engineering. (Our lives are too short to waste doing things we don’t want to do). So show your passion and take everyone along with you. Be precise and meticulous at all times and demand this from everyone on your team. A slight miscalculation or delay in ordering a critical item can be a disaster for a project.
3. Prioritize at all Times
As Covey says: “The main thing is to keep the main thing the main thing”. You will be inundated on a daily basis with fighting fires, including equipment failures, meetings and people demanding your time. Constantly clarify what the most important issues are and focus on them (filter out all other distractions). For example, Buckbee suggests that in a process manufacturing environment, the main things are probably:
- Unit Cost
- Production rate
- Quality
- Energy costs
- Reliability
- Environmental and safety
Note how (and engineers hate this) the emphasis is on $$$; not direct technical things to prioritize.
4. Document the beginning
Define the beginning of the project in business terms (i.e. $). You can certainly link in technical metrics, but the overriding aim has to be on improving a particular business metric with the proposed project. Ensure that everyone is in agreement with what you currently have in front of you and what you will be doing to improve this.
5. Communicate well and extensively
This is an area most engineers don’t like to get too involved with. Reading, writing and speaking in simple understandable language is not a preferred activity for most engineering professionals. But you have to communicate your requirements and successes in simple business terms. Long reports detailing exquisite technical accomplishments are never read. A short email with a provocative subject line: “$340,000 savings with flowmeter installation” followed by before and after pictures and some examples of how you have improved the quality (lower variability) of the process is far more powerful than a detailed 200 page account which includes the problems with the flow loop and the challenges in installation.
6.Use your Tools Effectively
As engineering professionals we all like to dig deeply and to investigate the technical issues; and we sometimes get sidetracked from the main game with these activities. Instead we need to use effective tools to get our results as quickly as possible without being sidetracked into minor issues.
And always ensure your tools are doing the right job. Compare their results with what you would intuitively expect – based on your past experience. Never trust a software program until it has proven itself in all circumstances.
7. Keep Sharpening your Skills and Know-how
Technology changes on a daily basis. You need to keep sharpening your skills by reading widely; exchanging views with your technical peers; attending outstanding training courses (which will be clearly beneficial) and drawing on your mentors to assist you with challenges. Keep a natural curiosity in everything you do. Keep questioning the ways you and your colleagues do things and examine ways to improve on these. Never accept a particular method of doing something without testing its assumptions. And never trust anecdotal information that something is superior. Always examine information gleaned from the web and magazines with a critical eye - look for the flaws - question everything. And remember that on-the-job training is probably the most powerful training you will ever receive.
Form these 7 habits and you will become a significant source of expertise. Encourage your peers to do the same. Sharing your know-how with others is one of the great traditions of the engineering profession.
Thanks to George Buckbee of Expertune and Stephen Covey for the inspiration and reference material to write this article.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues,
Steve is away from the office this week, so in his absence we have included a segment from one of our recent press releases for you. Obviously, these can be construed to be promoting our training (which they are) but we have had many case studies appearing over the past 12 months with this new form of learning from all walks of life (even one gentleman in Canada who is over 70 yo who is still working and updating his skills):
Online training via the internet really is coming of age when two generations of engineering professionals from one a South African company both enrol in the same e-learning course.
A father and son in a family owned business based in Johannesburg both enrolled earlier this year in IDC Technologies’ 18 month Advanced Diploma of Electrical Engineering. And both remain excited about the course several months down the road.
We asked son Chris Liebenberg for some comments about the course, his progress, and what it was like sharing the study with his father.
“Let me say I’m a big advocate for this e-learning approach,” states Chris. “If it had been this good when I was younger I probably would have studied at least as much as I should have done back then! It is more flexible than classroom based learning. For example, we can always review the recordings of the live sessions if we miss one. But the live sessions presented each week have been fantastic and with an excellent instructor such as we have it is hugely motivational to ‘attend’. I’ve been completely thrilled.”
Both father and son seem to be benefitting by doing the course together. They have developed some “healthy competition” over their assignment work but also compare notes and discuss some of the exercises and problems presented by the instructors. “My father occasionally needs some help with his computer connection, and in return it is good to have someone close by to discuss the material with,” reports Chris
Does Chris have any advice for someone contemplating enrolling in this course? He says “Yes, go for it.”
Have you had a positive or negative experience with e-Learning which you would like to share? Let us know!
F'REE Engineering & Technical Whitepapers
Every week, we are putting up at least 10 to 20 new engineering white papers in areas such as data communications & networking, electrical, instrumentation, industrial IT, mechanical and project management. Please send us any useful white papers you may have uncovered in these areas and we will place these up as well. You can locate these white papers at: https://www.idc-online.com/resources/technical-references.html
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We have this week placed up a selection of papers from a few of our conferences (see http://www.idc-online.com ). We all know the expression:" There is no such thing as a free lunch". But we have gone to considerable effort to collect these materials; so most assuredly they are good quality.
Engineering for quality, not longevity, is being brought home to us every day with loved ones who are often being sustained by machines. Now, I have no intention of engaging in debating the minefield of ethics in this area; well outside my competence and powers of persistence. As our technology improves in this area and we have a massive number of people who are aging, we are going to be increasingly confronted with this issue.
Our thrust as engineering professionals has always been on providing machines which will last forever (well, that is what we are often told in the marketing materials). I reckon a lot us intrinsically believe the human is yet another machine. There would be definitely mixed feelings if you designed an instrument which stopped working based on when the quality of output dropped off. We tend to be forced by the financial types and managers in our business to keep flogging that instrument to perform; despite poor quality data or performance; until it really does die. They then reluctantly allow us to upgrade to a new instrument.
When I did a medical electronics course, oh so many years ago, Prof. Chris Barnard, the eminent heart surgeon, remarked wryly when he dubiously looked at our early, primitive heart pacemakers: "The purpose of medicine is to improve the quality of human life; not to prolong it". There is no doubt that a heart pacemaker today can provide an incredibly high quality of life (as compared to those early ones in the sixties and seventies which were perhaps, brutal on the human body). We have an enormous growth in medical engineering technology (This seems to be reasonably recession proof ?) and growing associated costs and an aging western population increasingly needing access to this technology.
Despite the current economic travails, we find ourselves in, there are enormous engineering opportunities opening up with the aging of the population in terms of provision of improved quality in working comfort and health. We are all aware of the obvious ones such as vision degradation as you get older, to lower levels of endurance and powers of concentration. From providing engineering assistance at work, to the home and to leisure. I can think of a myriad of issues. For example, where a 65yo technician (as against a 21yo) may be highly skilled but is unable to physically get to examine an defective instrument but needs a remote method of accessing it; to inability to work in harsh freezing conditions for the same periods of time; to limited physical strength in lifting something up quickly and in controlling an instrument with the dexterity of a 22yo. Our safety guru, Dave MacDonald, will probably agree that there are many safety issues that need to be addressed with an older working population; which may not be such an issue when you were younger.
So what am I saying here in terms of action steps ?
- Think of an engineering professional who may be 65yo (not 21yo) working on your plant when it comes to providing easy access to instruments and equipment
- Seize the massively growing opportunities in medical technology and for older workers by taking your designs into this field
- When working with people in healthcare perhaps consider the focus on quality of life when engineering solutions
Yours in engineering learning,
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
A brief note today, as I have "crocodiles snapping at me" whilst working with the team here on finalising our accreditation application to present a Masters degree in Industrial Automation.
Engineering software and videos
We now have a two short videos (<5 mins) prepared by Terry Cousins on power quality issues. It is particularly challenging to compress everything into this short time; but useful educationally.
The power quality videos are:
* When the Lights Go Out
* When Voltage Dips, Your Profits Slip
And more are being added every week…
If you know of any other complimentary engineering videos or software that would be useful to your colleagues; please let us know by return and we shall highlight the list to everyone.
As Montaigne remarked: “It is good to rub and polish our brain against that of others” so any other contributions or ideas are most welcome.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
A short <5 minute video on Electrical Power Quality, presented by the inimitable Terry Cousins (of TLC software), is up for your perusal: http://www.youtube.com/watch?v=LZqkD4syAO8. There will be more going up over the next few weeks (emphatically non-sales).
In response to my blog last week I am grateful to Dave Macdonald, our safety control systems expert (and author of three highly praised books on the topic), who has kindly put together the item below on systematic errors. It is worth reading if you are involved in designing control systems - for instrumentation, mechanical or electrical systems.
Some thoughts (by Dave) on Systematic Errors in Control Systems
If you build any sort of process or machine control system there is a very good chance that, when you first put it into service or test it, you will be plagued by some kind of ‘bug’, either in the wiring or in the software. The proper term for such bugs is: ‘Systematic Error in Design’.
Most of us are familiar with the routine of version upgrades or specification revisions. These are not big problems for a control system on a production process: The control engineer says, “Sorry, just hold on a few minutes, I will make a few quick changes to remedy the problem - I didn’t quite understand what you wanted first time round”.
But it’s a different story if the bug is dormant in a functional safety system, better known as a safety instrumented system (SIS) or emergency shutdown system. We can’t afford to have a wrong response just when the plant is about to explode! So it’s not surprising that SIS projects involve some heavy duty quality assurance work to try to minimize the chances of systematic errors creeping into the design.
Some examples may help us to see the problem:
1 Faulty trip logic: An error in the trip logic diagram may not be revealed by testing the SIS as the faulty response will be built into the safety system. Testing the diagram with the (independent) process engineer might be a good idea here.
2 Failure to separate the safety sensor from the regular control sensor. Whatever goes wrong with the control loop will also afflict the safety function. We call this a common cause failure, but it originates from a systematic design error.
3 Incorrect installation of the trip sensor. The trip sensor will not correctly read the process condition.
4 Failure to consider all possibilities when scoping a safety function. See below for a notorious example from the London Underground.
Systematic Errors. When the mistake is built into the design through errors in understanding.
Train Safety…..?!!!
A London Underground train rolled backwards half a mile when the driver fell asleep, highlighting a serious flaw in signaling systems: they only work with trains going forward.
The Engineer: 14 July 2000
5 Safety controls often employ redundancy to ensure fault tolerance for random failures in the instruments. However, the benefits of doing this are significantly limited if the redundant instruments are identical - they may both suffer the same failure, for the same reason.
Here is a systematic failure example from my own experience: Two identical diaphragm seals, for pressure transmitters on a distillation column, failed at the same time when a severe vacuum occurred during a shutdown. The diaphragms were stretched leaving a 30% zero offset on both transmitters - not much help if one is for control and the other is for safety!
How can you avoid systematic errors?
• Be on the alert for common cause failure possibilities between control and safety instruments. Always look for diversity between instruments on the same application.
• Use the best quality assurance methods in hardware specification and in application software projects. Check back at each step forward in the project.
• Apply the safety life cycle guidelines of IEC 61511 and then find someone who is genuinely independent of your project to review the project stages for pitfalls.
• Strictly manage all design modifications and evaluate them for impact on the original safety requirements.
The more familiar you are with design projects, the more aware you will be of the potential for built in errors. Be alert!
Although the famous Economist, John Kenneth Galbraith, probably wasn’t thinking of systematic errors specifically, nonetheless this does apply: “If all else fails, immortality can always be assured by spectacular error”.
Thanks so much Dave Macdonald for your elegant dissertation above.
yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Don’t forget - we have a complimentary presentation on Transformer Failure in two weeks time. Details at the end of this newsletter.
As engineering professionals, we are surely closer to the driverless car than the paperless toilet
There is an old jibe amongst pilots regarding the basic requirements for flying a modern plane: The answer is a computer, a pilot and a dog. The computer flies the plane; the pilot’s sole task is to feed the dog and the dog’s job is to bite the pilot if he tries to touch anything. This is a fairly cynical attitude, yet most long haul flights are handled by auto pilot. I am a little twitchy about these modern planes, though, especially after the A330 which broke up over the Atlantic a few weeks ago; seemingly the computers (and presumably the pilots) were bamboozled by erroneous speed readings due to iced up pitot tubes. Most instrument engineers will sigh when they read this; as they would have been exposed to similar situations in plants of every description. But naturally, we must wait for the full airline disaster story before settling on this explanation.
Interestingly enough autopilots have been around since 1912. The modern autopilots still use the old Intel 80386 processor from 25 years ago (remember DOS and no odd operating system crashes). Trains are also highly automated (they only move backwards and forwards at the right speed and watch for red lights) without drivers - and people are comfortable with this. You only need to look at the London Dockyard trains, various world city monorails and the Malaysian Airport to see this in evidence.
What is mystifying, however, is the series of accidents with driver- led trains; this week, in the US, one drove into the back of another, and collisions at point crossings are not very rare.
But the big prize - to automate the car - has two obstacles; technical – obviously - and a harder one – psychological. Roads are enormously complex places compared with railway systems and the relatively empty skies in which planes fly (and then when landing they have massively human controlled airports and pilots on hand). Already the car is a massively digital and computerised animal with over 200 on-board sensors. The high end one possesses over 70 microprocessors and even the lowly Tata Nano has a dozen. Satnav is a key part of many drivers’ daily lives - allowing them to get around cheaply with satellite navigation in strange locations. Internet connectivity is achieved with smart phones allowing all sorts of interesting information to be gathered (such as real time traffic information and indeed even the location of speed traps). As we all know from personal experience; a driverless car has to deal with a myriad of issues – unexpected objects in the road, giving way to emergency vehicles; other accidents; drunken pedestrians; sudden road diversions.
But the payback could be enormous – a machine can react far more quickly than a human to a hazardous situation. And if the cars on the road could “chat” to each other via wireless they could minimise traffic jams and dangerous overtaking. As far back as 1994, a driverless car drove through the manic traffic-infested streets of Paris at speeds up to 120km/h for over 1000 kms. So the technology is almost here. Several cars (Mercedes and Volvo) will now brake automatically if they detect an imminent collision. And the Lexus (from Toyota) does its own parallel parking.
What to do:
• Read up on this new technology and talk about it with your peers
• Look for the business opportunities unfolding here – whether you are mechanical, electrical, IT or electronically oriented - with millions of cars on the road the re-engineering required is wide ranging and the huge opportunities evident
• Apply these new proven automobile technologies to your next project
• Ensure that whatever is done; all cars and support gear are super safe
• Think of the Law of Unintended Consequences and figure out unexpected results which may need to be dealt with – either from an opportunity or safety point of view
We engineers can improve on this safety zenith I am sure - a humorous remark by Dudley Moore: The best car safety device is a rear-view mirror with a cop in it.
Thanks to the Economist for references in writing this.
Case Studies of Transformer Failures
Listen in, ask questions or join in on our discussion during this free interactive webinar on Wednesday July 1st. It is to be presented by Dr Jerry Walker. During the 45 minute webinar we will review case studies of transformer failure, including; off circuit tap changer failure, sulphur contamination, and extreme conditions. We will summarise common reasons for failure by occurrence and severity, then look at preventive measures.
Yours in
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
I receive comments now and again querying why I spend an hour or two, per week, writing these musings. Well; apart from the PR for our engineering training, they keep me on my toes and interestingly I learn even more on the various topics from your responses. At the end of this blog are details regarding the recording of our latest webconference session on “Industrial Wireless Disasters” But now for my musings:
Buy or Roll thy own Engineering Software Tools
A decision we get confronted with regularly is whether to buy engineering software off the shelf or to write it in-house - or at least cobble it together from existing programs. In today’s market it is even more difficult to decide – there are more programmers available and the cost of the software off the shelf is exorbitant. I have been faced with this dilemma so many times and often made the wrong decision. Obviously, if it is a Word processing package or an engineering CAD package; it is unlikely that these will be rewritten. The difficulty is more prevalent, however, when software packages exist, for example, an industrial automation package - written for a particular plant or application. The vendor would have us believe that it can simply be ‘plugged in’. We have all had the nightmare of being trapped into buying something which has turned out to be a miserable and frustrating mistake – when in hindsight we should actually have gone down the hard road of writing it ourselves.
In essence, with Engineering Software what you are really after is:
* Availability – it should run and work smoothly with all your other tools
* Efficiency – it is quick to operate (minimal overhead)
* Reliability – it doesn’t crash in a different hardware/software environment, but runs without a hiccup
* Functionality – it should offer the functions you require – no more – no less
* Sustainability – it is constantly updated as new problems and situations arise with your systems
* Economy – it is not fiendishly expensive imposing an horrendous $ burden on your project or product It is virtually impossible for an in-house developed engineering software product to deliver consistently on all of the above. Only a commercially produced package, with tens or indeed thousands of iterations and many, many installations, can come up with this.
Why is an Engineering Software tool so hard to develop in-house? A few quick points on this score:
* Commercial packages are developed over a long period of time using many different clients and programmers – you are unlikely to have this luxury with software designed in-house.
* You are exposing yourself to significant commercial risk. You may be handicapped by a tool that should have been purchased off-the-shelf. Furthermore, designing it in-house can distract you from your core mission. You may only need a small increase in productivity to justify paying for a commercial software tool.
* Others have been there and done it – the commercial package – you could save a great deal of time and angst and ultimately money.
* You will achieve increased functionality due to the wider usage that a commercial package is designed for.
* What about the future? A software package requires ongoing development. At least with off-the-shelf software there is some degree of future proofing due to their support and R & D staff. (This is somewhat questionable in today’s gloomy business world, but is generally true if you purchase your product from a reputable organization).
* In-house software developers can simply walk out of the door when they decide to move on
* Training new staff on how to use your newly designed package can be difficult in-house.
* Ongoing maintenance for changes to your hardware and software environments, when done in-house, requires your design team’s time and time off the software – both a distraction from your project/s.
* And paradoxically – Customization. This is often quoted as the main reason to write the software in-house. But you may find the elements you require are already written for some other client in an off-the-shelf package. So the standard mantra of; “Our application is too different, special or customized for a commercial off-the-shelf tool,” is not necessarily always true.
Obviously in buying something off-the-shelf where millions of items are sold (as with a computer), one should bear in mind this sage advice: If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside. Robert X. Cringely, InfoWorld magazine
My grateful thanks to one of those enduring electronic design engineers, Steve Ciarcia, who wrote hands-on electronics projects for Byte Magazine. This is based on an article by him and CMX-Systems on real time operating systems.
Adapted to engineering software based on my mixed experiences.
IDC webinar recording now available.
Listen any time. Major Disasters in Industrial Wireless - and How to Avoid Them. This complimentary 45 minute recording of a recent IDC webinar is a discussion of disasters – both real and potential - that can occur in industrial wireless. Senior instructor Deon Reynders touches on the growth of wireless control in industry, recent trends, security issues and consequent disasters. We conclude with a simple checklist of basic preventive measures. Bear in mind that we have used our Electromeet software to do the recording to avoid having a massively large 100Mbyte (compressed) file.
You can listen to the recording of our latest session by following these simple steps.
1. If you already have Electromeet installed on your computer, skip to step 2. If not, you will need to download and install the latest version of the Electromeet software from http://electromeet.com/download/Default.aspx . (10MB approx download, 20MB hard disk space)
2. Now cut and paste the entire recording link ( http://www.electromeet.com/ssdownload.aspx?filename=session_356e62ae-11a... ) into your browser address bar then download the recording file (ends in .emss) and Save to a known location on your hard disk. (10MB file size)
3. Launch Electromeet from the desktop icon. Open File >Open Saved Session >[browse to saved session location] from the Electromeet menu.
4. Click on the file of the downloaded session. The recording will play back. Use the play, stop, fast forward and fast rewind controls from the “Recordings” section (bottom left of screen) as you would on a DVD player.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Contrary to my effusive praise for the USB (esp. compared to RS-232); I received a list of woes relating to its use from you dear readers. I have placed some of your comments up on the blog site. Thanks very much for your quick and often detailed responses.
As engineering professionals, do we save enough energy?
I have watched with interest the collapse of oil prices - and then, in the past month or so, their upward trajectory. The upward trend, in many cases, is as a result of our friendly speculators betting on the worldwide economy getting better more quickly. I have always believed that engineers and technicians are very conservative in their energy usage – always looking for ways of doing more with less. But even with a recession, we are still a long way from a time when oil was $7/barrel – back in 1971. Since then, there has been an impressive decoupling (yes – that economic term) of growth in energy consumption and “human activity” (or Gross domestic product). As most of you already know, some of the most publicized methods for energy conservation are to incorporate passive energy designs into a home (or office) using:
* Solar water heaters. This is where hot water is moved to where it is needed without the use of mechanical pumps
* Convective loop/double shell design. This involves the inclusion of a space between the inner and outer walls of a home allowing for convective circulation of (hot) air
* Efficient building components. These include efficient roof and wall insulation; multi pane windows and tight air sealing for both windows and doors
* Natural day lighting. This involves the avoidance of east and west facing windows so that the need for artificial lighting is reduced.
* Window glazing. When it is done well Goldilocks would remark, “Just right”. This is critical, as too much can prevent adequate daylight penetration while too little can result in the need for increased heating.
Active systems are also becoming increasingly attractive through either an open loop or closed loop system where pumps, powered by solar photovoltaics, are used to drive the water around the system.
Whatever conspiracy theorists say; you can bet your bottom dollar that the oil price will shoot up to high levels again - apart from anything else because there is a growing shortage of oil. So purely from a cost and strategic point of view, energy conservation is worth investigating and employing…….and you would be reducing pollution and CO2 gases in an effective manner.
What are the results to date?
Energy use per dollar of GDP has fallen more than 40% since the 1970’s. Oddly enough, energy per capita has remained relatively constant; but will be impacted by the employment of the measures outlined above. Other metrics (compared to the ‘70’s) include; new home fridges using a third less energy; fluorescent lighting using less than half the energy and the amount of energy needed to generate 1kWh of electricity dropping by 10%.
So where do we go from here (bearing in mind that high energy prices will return with a vengeance):
* Actively look for energy conservation options in your personal life and business
* Look to apply clever technologies to energy conservation
* Read up as much as possible and preach these technologies to your peers
Thanks to P.E. Meyer and G.F.McClure of the IEEE for their very commendable (although US-centric) article.
As William A. Smith remarked rather seriously in 1908:
As Engineering is the science of economy, of conserving the energy, kinetic and potential, provided and stored up by nature for the use of man. It is the business of engineering to utilize this energy to the best advantage, so that there may be the least possible waste.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Recently, when looking at our local electronics’ supermarket, the pile of 32 Gigabytes USB memory sticks, now costing less than $100, caught my attention. It made me ponder, yet again, the ubiquitous USB standard and its industrial usage. There is no doubt that Ethernet is a strong industrial standard used widely around the traps - but USB offers a real alternative. Spend a few minutes considering it as you read the following.
Over 2.5billion USB (Universal Serial Bus) devices were shipped last year and there are more than 6 million installed (according to the USB Implementers Forum). The brilliance of USB (well, USB 2.0) is that it is almost ‘plug and play’ (not ‘plug and pray’, as many jokers referred to the earlier incarnations of industrial networks and PCs). One can see the different USB speed benefits for a 25 GByte high definition movie. It ranges from; USB 1.0 (9.3 hours), to USB 2.0 (1.39 minutes), to USB 3.0 (70 seconds).
USB provides a medium bandwidth, non-proprietary port with multi-drop, half duplex twisted pair operation (similar to RS-485). Because of its differential nature, noise immunity for industrial environments is a positive consequence. Data rates are high and it can connect up to 127 devices. Although it is half the speed (480 Mbit/s) of Gigabit Ethernet (which incidentally, is not used overwhelmingly in industrial applications) it is the USB’s versatility and convenience, rather than its speed, which is magnificent for industrial applications. A data logger can be installed in a few seconds, up to 5m from the PC. It can be simply plugged into the PC to draw the necessary power from the USB connection. It is also easy to add and (hot) swap new modules. Many instrumentation companies are using USB for a range of applications including; data acquisition, digital multimeters (DMMs) and switching modules and sensors - such as proximity detectors. USB is also particularly useful as a power supply (where the DMM uses only 2W, for example).
The great benefit of a USB port is that a hub can be easily added and then onto this several devices attached with minimal software impact (some designers up to 12 devices). With a hub it is possible to cascade up to 5 levels. And another trusty old use is replacing old DOS based floppies with USB data storage, thus providing a new lease of life to old hardware. Although the main standard at present is USB 2.0; USB 1.1 is still around and being used for mice and keyboards. Many industrial users are relieved to find the arrival of a plethora of ‘ruggedized’ USB chip sets. These have wider temperature ranges and there is greater driver support for USB across most operating systems ranging from x86 chips to Linux.
On the negative side, however - the USB lacks a widely used industrial connector (Industrial Ethernet uses industrialised connectors now to replace the horrible RJ-45 connector). Furthermore, the challenges for USB, in an industrial context, include; connector strain relief and the maximum cable length of 5m (although with USB hubs (to 30 m) and extenders (to 500m) the distance is greatly increased). And finally, there is no provision for electrical isolation - a problem for industrial applications, surely.
Despite these detractors, in your next project don’t automatically assume that Ethernet is the name of the game - seriously consider USB.
And to those of you who poo-poo the idea of using USB for industrial purposes, may I be so bold as to quote Samuel Johnson:
“Nothing will ever be attempted if all objections must first be overcome.”
Thanks to Electronics Design, Wikipedia and B&B Electronics for references.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
My dream (well, one of ’em), when I was in my early twenties as a young engineer, was to travel and work extensively throughout the world. However, having done this (and being on an engineering business trip at present), I am a little more circumspect about travel and prefer the home turf. There is this belief, regarding work overseas, that it is not only exotic, but lucrative. Most often, though, this is not the case and one merely lands up elsewhere because the boss said so!
We all know about the cultural ambassadors such as Paul Gaugin, Pablo Picasso and Ernest Hemingway who have enriched our worlds enormously – when they worked at home and abroad. But engineers working creatively and contributing creatively to the world by working overseas? This is doubtful, surely? Research, however, by two psychologists; Drs Maddux and Galinsky, clearly shows enormously enhanced creativity as a result of working in different countries. Although the cause is somewhat unclear.
There is no doubt that engineering professionals travel extensively these days. As far as engineering is concerned we really live in a global village. Engineers travel for a whole gamut of reasons, ranging from the minor (like plugging an updated EPROM Chip into the PLC system in a remote power station location - a few hour assignment, but deemed worthwhile if risk is avoided) to the profound and extensive (like sending a team of engineers and technicians to construct a new petrochemical plant in the middle of North Africa – a project taking a good two years).
Some thoughts on what to consider when working overseas:
• As a young engineering professional travel extensively and embrace the world – it will enhance your career and creativity magnificently
• Make a grand effort to get on with your boss and management team in the foreign town
• Thrive and learn from the culture and way of working and thinking, as an engineer and technician, overseas – it will contribute to your ability to think laterally.
• Assess national standards and see how you can enhance them when compared with those in your home country.
• Add engineering value by sharing your know-how widely with the locals
• Look for opportunities to take concepts, products and services from your homeland to your new overseas workplace and vice versa
• Be careful to measure the personal price paid when working overseas
• Examine the impact on a young family (sending kids to a boarding school and having your wife/husband, with a PhD in nuclear physics, sitting around cooling her/his heels, is not always a happy option)
• Ensure you get paid in a currency that doesn’t depreciate after 6 months in your new location
• Keep professionally up to date with your peers back at home and don’t let your skills degrade
• Build professional relationships with people in overseas’ countries – these relationships often continue long after you have returned home and can be enormously valuable and satisfying
An interesting observation follows. It is made by Faith Popcorn about the Americans - but is certainly not exclusive to them. We can all ultimately fall into this humdrum routine.
“The trouble in corporate America is that too many people with too much power live in a box (their home), then travel the same road every day to another box (their office)”.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
No matter how good a proposed solution seems to be it will have some unintended consequences and as engineering professionals this directly impacts on us. A couple of weeks ago we discussed the great new low energy LED lights. These have been installed as traffic lights in Portland and are saving big $ in energy. BUT…. they are the cause of numerous accidents. With the older lighting technology, a great deal of energy was wasted as a result of the heat that was generated to produce the light. Now, however, without the heat, snow and ice build up on the signals and hide the bright red, yellow and green LEDs and drivers can’t see who has right of way. Thanks very much to Robert Zonis for pointing out this unintended consequence in response to my blog.
Crudely put, unintended consequences can be grouped into three types:
* A positive unexpected benefit (a windfall)
* A negative effective opposite to what was intended – generally always referred as an unintended consequence
* A potential source of problems (e.g. Murphy’s Law)
The classical example is a bypass built to relieve traffic congestion on a road. The new road, however, attracts new development which results in more traffic – the unintended consequence - two congested busy streets.
Simply put, the Law states that each solution will have more than one effect and one of these will be an unforeseen negative side effect (which indeed, can be considerably more significant than any of the designed or intended side effects).
Another example is the proliferation of the very quiet hybrid or electric vehicles. Pedestrians (esp. those who are sight impaired or pre-occupied with the latest rap music on their iPods) don’t hear them coming. Will this result in legislation requiring vehicles to have minimum sound levels to avoid potential accidents? Another example is the introduction of these new graphic chips that give ultra fast games brilliant graphics. With the parallel processing capability of the chips, the password hacker is using these chips for his “Password recovery” software and is achieving password cracks in 3 to 5 days instead of months. Other much quoted examples of unintended consequences (although often riddled with misinformation, I might add): Windfarms. Apparently they kill migratory birds with their turbine blades. Bio fuels. They have apparently resulted in price hikes of foodstuff, such as corn, due to the incredible demand for ethanol - a more environmentally friendly fuel – which they are used to produce. Censorship. An often amusing consequence is when authorities try to censor a photo or some information, but find the exact opposite results (The Streisand effect).
Herewith, some suggestions to avoid being stung by the Law of Unintended Consequences when engineering your next project:
* Take time to consider the outcomes. Try to predict both the long term and immediate effects. Think laterally to include even the wildly impossible outcomes and consider possible impacts three or more steps into the future. Do not be impulsive! Think carefully and extensively.
* Talk to others (esp. well outside of your discipline) and consult them. You are not omnipotent and other perspectives would cast new lights on the problem. Avoid ‘group-think’ where everyone is locked into one way of thinking. Encourage dissent in your design circle to ensure lateral thinking.
* Research the problem. Nothing under the sun is new; and you may well find someone else has experienced an unexpected consequence to the project you are working on.
* Apply a risk management program to identify the risks on a continuous basis. Use Failure Mode and Effects Analysis (FMEA), employing fault trees, to assess potential failures.
* And as, the Happy Curmudgeon, remarked: Avoid management fads.
As an anonymous author wryly observed: Results are what you expect, and consequences are what you get.
Acknowledgements to Robert Zonis, The Happy Curmudgeon and Wikipedia for references used above.
Yours in engineering learning Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
My mailbox buckled under the strain of responses from my discussion on lighting last week. Thank you all for your comments. I have put a selection up onto my blog site.
Don’t forget another in our series of complimentary 45 min. webinars (no sales spiel) entitled: “Major disasters in engineering and technical marketing (and how to avoid them)” on Wed 14th May (details at the bottom of this note).
1.0 Engineers and Techs – Rip up your power cables
You probably sigh, as I often do, when trying to move some piece of equipment which is festooned with cables. And some of us (including my dear wife, I might add), have cursed at 3am with the incessant beeping of the cell phone wanting to be charged. Fortunately the data communications and networking cables are no longer as evident with the advent of wireless, but the power cables and charger are still firmly in place - apart from one’s electric toothbrush which is cleverly charged by inductive coupling. There has been an explosion of cell phones, mp3 players, computers and even household robots (for some of the more daring amongst us), all demanding that we break that last umbilical power cable to make our lives that much more convenient.
The surprising thing in engineering is that, despite the incredible advances in communications and technology, electrical power still cannot be simply beamed through the air - at which point irritating adapters, cables and plugs could be dispensed with.
Transmitting power wirelessly has been used through the centuries - mainly electromagnetic radiation using radio waves. Unfortunately, even when radio waves are tightly focused, they still tend to disperse in all directions and undoubtedly have an adverse impact on humans. Directed electromagnetic radiation, such as with lasers, requires an uninterrupted line of sight and can cause harm to anything erroneously entering its path. As a result this is not viable either.
Initial commercial success, to date, has been in the use of electromagnetic induction; where a coil (contained in a pad) generates a magnetic field when a current flows through it. A mobile device containing a corresponding coil is brought close to the pad and the magnetic field generates a current in the second coil - charging the mobile device’s battery. This was the concept behind Splashpower - a British technology firm who attracted very strong interest from consumer electronic firms in 2004. They unfortunately went bust recently - illustrating that turning the theory into profitable products is somewhat elusive. In Dec. 2008, the Wireless Power Consortium (modeled on Blue Tooth), was formed to promote a common standard for inductive wireless charging; with some big hitter members such as Philips, Sanyo and TI. Although this technology is being commercialized with toothbrushes; commonality is required across different brands of mobile phones (unbelievably when you lose your charger, sometimes it is cheaper to buy a new phone) and digital cameras.
Strong competition between manufacturers of mobile devices is fuelling the introduction of wireless charging. With its latest phone, Palm introduced an optional charging pad - using induction to charge the device when it is placed on the pad. Another offering involves embedding charging pads into kitchen counters to charge wireless blenders and electric knives, for example. Another less whiz bang approach includes creating a charging pad with four small conductive metal studs on the back of the phone - allowing electrical contact at all times with a charging pad.
Other options, with faint hopes of success, include long range transmission of wireless power (similar to the passive power principle in crystal radios); which is reasonably successful over short distances. The intensity of radio waves needed to charge mobile phones, however, is likely to be hazardous to human health. Over distances of 7.5m, Powercast, has created products that can power wireless sensor networks at safe power levels (mW over meters). And there are inevitable “triers” with laser powered devices, although it is difficult to see these as safe options with humans floating around.
I must mention one innovative design from MIT - as I wonder why we didn’t think of this many years ago - called WiTricity (Wireless Electricity) based on using coupled resonant objects. As you may recall from your high school physics (or indeed radio theory – think of a tuned oscillator), two resonant objects exchange energy very efficiently. A great (mechanical) example is a child on a swing - a resonator. Only when she pumps her legs at the right frequency is she able to impart substantial energy. Or the well known example of an opera singer, singing at precisely the right note and shattering only one of 100 wine glasses in a room which has been tuned exactly to the same frequency and has accumulated sufficient energy. The WiTricity project equipment comprises two copper coils – each is a self resonant system. The sending coil "sends out" a magnetic field. This allows for strong interaction between the sending and receiving coils, whilst the interaction with the rest of the environment is weak. Do not mistake this with magnetic induction which is apparently almost a million times less efficient than this coupled resonant approach. They have demonstrated lighting a 60W bulb, from a power source 2meters away, with objects in between. It is exciting to see this coming to commercial fruition.
Some pundits reckon that mobile phone manufacturers use the proprietary power adaptors to lock customers into their products, as it is a hassle to change. But change is slowly coming and one can expect to see inductive power, at the least, but hopefully some more innovative technologies, such as that from MIT, coming to the fore.
Over the ages, the best example of wireless power has to be as William McDonough remarked at the Fortune Brainstorm Conference in 2006:
“Don't get me wrong: I love nuclear energy! It's just that I prefer fusion to fission. And it just so happens that there's an enormous fusion reactor safely banked a few million miles from us. It delivers more than we could ever use in just about 8 minutes. And it is wireless!”
Thanks to the Economist, MIT and ScienceDaily for the background information here.
2. Major Disasters in Engineering and Technical Marketing (and How to Avoid them) webinar on 14th May
This complimentary 45 minute webinar aims to illustrate the perils of marketing so that engineers and technicians can develop greater awareness of the potential for real product disasters. It is to be presented by Terry Cousins, a professional engineer who has set up a remarkable worldwide business designing and manufacturing electronic test equipment. We look at 5 different, but famous, marketing campaigns from recent history and consider the lessons that can be learnt from them. One of the crucial questions to be considered:- ‘Is innovation enough to guarantee market success?’ This live webinar will provide us with lots to think about in an entertaining format…….. and enable you to boost the sales of your products and services! The registration page is at http://www.idc-online.com/IDCwebinar.html
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Thanks for your comments on my blog, including those chastising me! I try to respond to everyone that mails me and where possible I put your comments up onto the site.
Don’t forget another in our series of complimentary 45 min. webinars (no sales spiel) entitled; “Major disasters in engineering and technical marketing (and how to avoid them)” on Wed 14th May (as detailed below).
1.0 The LED knocks out incandescence big time
If you’re like me; you’re probably a little irritated by the demise of incandescent bulbs. In search of lower energy consumption (lighting takes up 20% of the world’s electricity) they are being replaced with the expensive compact fluorescent lights (CFLs). Europe will phase out incandescents by 2012, America by 2014 and Australia has already given them the flick. Thomas Edison created the first incandescent bulb in 1879 using a wire filament encased in glass. They were initially hopelessly inefficient - (5% energy to light) and then needed replacing every 1000 hours or so. Back to today - the cheapest replacement is the compact fluorescent light (CFL) which uses 75% less power, lasts ten times longer, but costs a heck of a lot more (6 to ten times). CFLs use electricity to excite mercury vapour, which creates UV light causing the phosphor coating inside the bulb to glow. There are some safety concerns with the use of CFLs, however; the flickering effect of some CFLs, the leakage of UV from some of the poorly manufactured ones and the disposal of mercury. (I wonder; how many of us are hoarding incandescent bulbs)
There is a great alternative; Light Emitting Diodes (or LEDs). They have a lower energy usage, a longer lifetime, are smaller and more robust, but require more precise current and heat management. Energy savings are up to 80%, but they cost $US60 or more! They were invented by Oleg Losev in the 1920’s. You will no doubt recall them as dimly lit, simple red indicators on electronic panels. They have now morphed into torches and streetlights and more. As you may know; a LED is made up of two layers of semi-conductor – an n-type (lots of electrons) and a p-type (lots of holes – or an absence of electrons). When a voltage is applied across the junction, the holes and electrons meet up and release light – an effect called electroluminescence. Breakthroughs, such as the use of Gallium Nitride which creates bright-blue LEDs, promise to reduce costs significantly. At present these are deposited on sapphire wafers, but when these can be replaced with silicon, dramatically lower costs will result.
Some positive progress has been made - low cost LEDs can be applied to solar powered reading lights, in the poorer areas of the world, allowing children to do their homework in the evenings without using candles.
There is an enormous amount of development in this area; so tread cautiously as you sift through the emerging lighting information - and follow James Thurber’s exhortation: “There are two kinds of light--the glow that illuminates, and the glare that obscures”.
Thanks to Wikipedia, Cambridge University, The Economist and Philips for background reading.
2. Major Disasters in Engineering and Technical Marketing (and How to Avoid them) webinar on 14th May
This complimentary 45 minute webinar aims to illustrate the perils of marketing so that engineers and technicians can develop greater awareness of the potential for real product disasters. It is to be presented by Terry Cousins, a professional engineer who has set up a remarkable worldwide business designing and manufacturing electronic test equipment. We look at 5 different, but famous, marketing campaigns from recent history and consider the lessons that can be learnt from them. One of the crucial questions to be considered - Is innovation enough to guarantee market success? This live webinar will provide us with lots to think about in an entertaining format…….. and enable you to boost the sales of your products and services! Registration page at http://www.idc-online.com/IDCwebinar.html
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
We have yet another in our series of complimentary 45 min. webinars entitled; “Major disasters in engineering and technical marketing (and how to avoid them)” This one is running on Wed 14th May. At the end of the day, we are all selling something so if you are involved in the technical world; an engineer, technician electrician…. this should be of benefit. See below for details.
Over a hundred very interactive (and indeed chatty) participants attended the PLC webinar yesterday.
The convergence of engineering & biology is creating an enormous opportunity for you - Today
I am convinced one fast growing area of engineering, which is not unduly impacted by the economic crises, is in the medical area. And enormous growth is happening here now. It is time to look at what you are doing in engineering to determine how you can apply this to the medical and biological fields.
Oddly enough, over the years, the healthcare sector has been rather reluctant to grab the opportunities presented by engineering and even the more ubiquitous Information Technology (IT). For example, most doctors still work mainly with pen and paper, and shy away from any electronic record keeping (which would be useful to both doctors and patients). We all know engineering has been impacted by IT; advanced materials, imaging, nano technology and modelling and simulation. These technologies are about to be absorbed into the medical world on a large scale. As Menno Prins of Philips (big into medical technologies) explained: ‘like chemistry before it, biology is moving from a world of alchemy and ignorance to becoming a predictable, repeatable science’. And the biggest winners promise to be the consumers – patients will be more able to manage their own health affairs. To be perfectly frank (well, I am sure you are aware of this from your own experiences); doctors lack the knowledge to always make good decisions. The Institute of Medicine in the USA, estimated that over 100,000 Americans are killed each year by preventable mistakes such as medication errors and hospital infections. Patients now have the opportunity to take responsibility for their own health and stay out of hospital.
And as The Economist pointed out: “ Technology is making health care more portable, precise and personal”. For example - the million dollar machines being designed and sold now which morph the X-ray, ultrasound and magnetic resonance scanners to provide real images of your guts in real time Another example - micro-robotics which makes surgery far more precise than ever before (esp. for horrible diseases such as prostate cancer). In a decade from now, nano robots will operate in your body, at the molecular level, seeking out tumours and zapping them with radio waves.
Rapid diagnostic tools, with cheap testing kits, are being developed and released. Old fashioned pills, which often didn’t make it to their tumour targets, are being supplemented by silicon chips that are storing and releasing drugs on demand with a wireless signal.
Personalised medical devices, allowing health care at home, are really taking off due to three converging technologies:
* Telemedicine - built on improved data communications (and the Internet)
* Medical devices at home are becoming smaller and cheaper – (a welcome shift away from “clunky medical monitors and creepy lavatories” according to the Economist)
* Very low cost medical sensors and smart phones are allowing a move to real body computing.
Naturally, the Tsunami load of data generated by these devices still needs to be analysed and acted upon effectively by the experts…...
Telemedicine, though, is growing in leaps and bounds. One example involves remote medical consultations which are taking place from mainland USA to Hawaii for skin consultations. Another involves remote video links in India where eye-care clinics operate in remote villages. They are staffed by highly trained local women with the elusive and expensive supporting physicians at a faraway city hospital.
Obviously all this medical technology still comes at an enormous cost - we do need better economic health outcomes as we (and the public purse) don’t have unlimited funds. This is a discussion for another time.
But remember - this field is growing and offering enormous opportunities to you whether you are an electrician wiring up the new machines and installing home medical devices or a highly skilled mechanical or electronic design engineer contemplating a new medical engineering technology. Or even if you are a patient who would surely appreciate better quality medical care, at a lower cost and which involves staying at home rather than in an anonymous hospital.
Read up about it now to work out how you can leverage off these incredible new medical technologies – some of the fastest growing areas of engineering endeavour today. As the Old Testament remarked many years ago: “Physician heal thyself”. This couldn’t be truer with the incredible opportunities today to personalise medicine and indeed to take ownership of your own health. And this is where you and engineering can play a key role. Naturally, technology cannot substitute for personal responsibility – you still need to take control of your personal health and those you love and care for.
Thanks to The Economist for some inspiring words about engineering and technology moving into the medical fields.
The webinar: Major Disasters in Engineering and Technical Marketing (and How to Avoid them)
There are three session times on Thursday, May 14.
This complimentary 45 minute webinar aims to illustrate the perils of marketing so that engineers and technicians can develop greater awareness of the potential for real product disasters. It is to be presented by Terry Cousins, a professional engineer who has set up a remarkable worldwide business designing and manufacturing electronic test equipment. We look at 5 different, but famous, marketing campaigns from recent history and consider the lessons that can be learnt from them. One of the crucial questions to be considered - Is innovation enough to guarantee market success? This live webinar will provide us with lots to think about in an entertaining format…….. and enable you to boost the sales of your products!
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Don’t forget our Major Disasters in PLC Projects webinar on 21st April – details at the end.
1. Scavenging for Endless Energy – without Batteries
After initially being a doubting Thomas, I’ve become quite enthused with the new wireless networked instruments available (whether flow, temperature, pressure based or …….) which operate for up to ten years (or longer), in some cases, with a single battery. And now, I am astounded to find that the next generation to be released involves wireless instruments that need no batteries at all! Instead they “scavenge energy” from the environment to power the instruments. This is not some sci-fi gimmick, but are real commercial products emerging today. What follows are a few words on this incredible new technology.
As we all know, we are surrounded by energy, and recently (with climate change in the news) we have been harvesting this energy on a more “macro” scale with giant wind turbines and dazzling arrays of solar cells. We are thinking in terms of chunky MWs (rather than mere joules – see later). But what has become increasingly possible today, is to power electronic devices, scattered around your plant and home, by harvesting the ambient energy in the environment - thus eliminating the need for batteries forever (no more periodic battery replacements or other external power supplies!).
This has all resulted with the convergence of four separate technologies. Firstly, microcontrollers are demanding considerably less power than ever before. Secondly, wireless networking has increased data rates for an equivalent lower power (using bursts of transmission). Thirdly, protocols for operation have become far cleverer using less power. And finally, energy harvesting - or gathering energy from the environment - is vastly improved.
Technically there are three free energy types available:
* Radiant – the classical silicon-based photovoltaic (PV) cells – pretty stock standard, but obviously considerably smaller. These are now moving into organic PV cells to operate with ultraviolet and infra red. Some are even gathering energy from RF transmissions (off TV stations).
* Mechanical – the use of electromagnetic or piezo electric conversion to create energy. Vibration, using cyclic movement, is also popular.
* Thermal - which can leverage the Seebeck effect (remember our good old thermocouples from our high school days) by converting thermal into electrical energy.
A key component associated with energy harvesting hardware is a power management block. This is required to manage these disparate and disorganized bursts of energy by delivering the electrical voltage level required by the instrumentation. For example, with movement energy harvesting (eg. from a pushbutton) - the energy delivered ceases when motion is stopped. So it has to be managed to produce a consistent voltage.
Another key device, to address the energy uncertainty, is the incorporation of an energy storage area or reservoir in the system. These reserves result in continued and consistent operation even when there is no energy around. Interestingly, however, the most common uses for energy reservoirs are when the instantaneous power requirements are far more than the converter is able to supply - the device collects energy and then operates for a short burst consuming high levels of power (e.g. for a radio transmission of the instrument’s data).
A few suggestions when applying these technologies in your next system:
* Be energy aware and optimise the microcontroller’s various modes for minimum energy consumption (and naturally eliminate small voltage and energy losses in your circuit design).
* Keep RF transmissions to a minimum. These are very power hungry.
* Don’t think in terms of current draw (amps) in circuits, but in energy consumption (joules).
* Remember that in most applications there is not sufficient energy available to drive the electronics all the time. They can be driven in short bursts, so carefully assess standby requirements, peak current draw and average power needs.
A few years ago, these sorts of applications were impossible. Now we can implement wireless systems anywhere without tiresome cabling, external power and even batteries. With devices now using even less power and energy harvesting still in its infancy, we have incredible opportunities today in our designs. Seize these opportunities now.
Thanks to Richard Quinnell at Electronic Design (use these key words to google the article) for the background research and a very detailed article.
Using batteries with instruments was once considered an enormous problem, but as Lee Iacocca said:” We are continually faced by great opportunities brilliantly disguised as insoluble problems”.
2.Major disasters in PLC projects (and how to avoid them)
IDC Technologies proudly presents another live webinar in our popular series "Avoiding Engineering Failures".
When: Tuesday April 21
(Registrations close 24 hours before the first session). There’s a choice of 3 session times on the registration page at http://www.idc-online.com/IDCwebinar.html
.
Where: At your desk!
What will it cover: This complimentary 45 minute webinar will touch on the many considerations of PLCs, including; installations, planning, purchasing, hardware and software reviews, testing, commissioning, and operational aspects. We’ll also look briefly at good practice for safety PLCs and the documentation requirements. It will not be brand specific.
This is a live, interactive webinar. And it’s free!
Join us from anywhere - and bring our PLC expert to your desk! If you are involved in PLC selection, programming and operation you will benefit from the session. All you need to participate is a computer with adequate internet connection, speakers and (ideally) a microphone.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Good morning to you all
Three items today.
1. Sarah Montgomery, Our conference manager, has kindly made available some of our papers from our recent SCADA and Industrial Automation conferences. Click here to download these.
2. Don’t forget our Major disasters in PLC projects webinar on 21st April – details at the end.
3. Build your engineering technical reputation especially during these hard times
We have all noticed that certain engineering professionals in the firm develop into technical experts - becoming rapidly indispensable. During the last downturn I was rather awestruck to see assorted partners, in a firm of consulting engineers, being retrenched when the indispensable, technical boffin remained unscathed - he was critical to the firm’s wellbeing. The technical experts are the ones sought out to solve hard technical problems and guide the firm in decision making on future activities. They often end up leading the business as Technical Director or even CEO. An obvious example of a technical expert who rode the rising tide is the inimitable Steve Jobs at Apple. He engineered all the most breathtaking advances (e.g. iPhone and iPod). With his outstanding technical and business skills he is driving a multi billion dollar business. And interestingly enough, he has no (engineering) qualifications – but that is another issue for another time.
How does one become a technical expert? Here are twelve suggestions:
1. Pay supreme attention to (technical) detail. Ensure that design or commissioning is done to the highest level of precision and accuracy. Check, check and re-check for errors.
2. Stay hands-on at all time. You only learn by doing. Constantly attempt new approaches from hardware to software prototypes, testing new ideas.
3. Go deep technically when meeting others. Don’t gloss over the technical detail when analysing problems. Ask the awkward and penetrating questions that ensure a problem or opportunity are thoroughly assessed.
4. Don’t get swamped by personal trivia. As Hanks (below) suggests: “Read e-mail on Wednesday”. Focus on and commit furiously and unswervingly to your design task. Avoid other distractions - the usual business trivia or bureaucratic demands. Hard thought often requires you to be anti-social.
5. Keep teaching. Training others on concepts is often the best way to test your own knowledge and gauge that you have a clear understanding of them. Give your knowledge freely to others and ensure that you listen carefully to them. You will learn a great deal - even from those you are instructing.
6. Join the technical expert groups and run with the wizards and wolves. Groups of high flying technical wizards, from different companies (in different countries), tend to group together – partner with them and tap their know-how all the time. Bridge the gaps in your knowledge. Be clear about where your industry is heading and transfer this know-how to your outfit.
7. Don’t be afraid to fail. If you have researched a particular approach carefully and are confident this has value - go for it. If it fails due to some reason out of your control, so be it. Remember, however, to give it your best shot, don’t compromise with the negative people who inhabit all firms, but drive your approach forward persistently.
8. Reach for the stars with your vision. Being an engineer or technician means you are probably strongly quantitative and conservative (a reason for being good here). But try and imagine approaches which would stretch you well outside of your technical comfort zone but, which are still well-grounded.
9. Ensure your passion and hobbies are aligned with the company mission and vision. If you find technical things boring and would prefer to run a fishing boat chartering business, bail out immediately and cross over. But if you love engineering, electronic and software design and are always tinkering/talking or reading about these things; you are most likely going to grow with the business technically.
10. Lead by example - inspire others to follow you by constantly driving forward with new ideas, new approaches and continued enthusiasm (despite the inevitable setbacks).
11. Keep learning and suck in new information, ideas and know-how. Keep examining how you can apply new approaches and knowledge to your projects. Become known as the “technical ideas” man/woman, with refreshing new approaches based on your recent learning.
12. Be apolitical and modest. A colleague of mine - one of the most successful control engineers, I know (yes, you Mr Martin G.) works assiduously putting a new process or plant together and avoids blaming anyone (no matter how tempting) for the usual detritus of ‘stuff ups’ and badly engineered jobs. He concentrates on fixing these and incorporating them successfully into a smoothly running plant. Be opinionated on well researched technical issues, but avoid arrogance (which may be tempting and fairly natural given your superior knowledge) and general organisational gossip which doesn’t benefit the final project outcome one iota.
Remember to learn constantly. As William Shakespeare said: “The fool doth think he is wise, but the wise man knows himself to be a fool”.
My grateful thanks to John Hanks of National Instruments for the inspiration and some of the collateral to write this article.
3. Major disasters in PLC projects (and how to avoid them)
IDC Technologies proudly presents another live webinar in our popular series "Avoiding Engineering Failures"
When: Tuesday April 21
(Registrations close 24 hours before the first session). There’s a choice of 3 session times on the registration page at http://www.idc-online.com/IDCwebinar.html .
Where: At your desk!
What will it cover: This complimentary 45 minute webinar will touch on the many considerations of PLCs, including; installations, planning, purchasing, hardware and software reviews, testing, commissioning, and operational aspects. We’ll also look briefly at good practice for safety PLCs and the documentation requirements. It will not be brand specific.
This is a live, interactive webinar. And it’s free!
Join us from anywhere - and bring our PLC expert to your desk! If you are involved in PLC selection, programming and operation you will benefit from the session. All you need to participate is a computer with adequate internet connection, speakers and (ideally) a microphone.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Two items today. On this April Fool’s day I hope you are enjoying a laugh - with the economic storm clouds gathering we do need to retain a sense of humour.
1. Major disasters in PLC projects (and how to avoid them)
In this complimentary 45 minute webinar, we will look at the intrigues of PLC installations, the programming of their hardware and software and how to achieve good practice. It is running on the 21st April. More details can be found at the end.
2. Drawing and thinking inside the engineering box
Most experienced engineers and technical professionals love sketching out solutions to problems - drawing little boxes when explaining or detailing some particularly ‘curly’ problem. I do feel, however, that drawing is underutilized as a tool when explaining concepts to fellow professionals and to laypeople – whether you are an electrician or advanced computer design engineer – sketching out the concept is an enormously powerful way to communicate. There is an overemphasis on the necessity of good written and verbal communication, and to our cost, we forget the incredible resource we have in drawing freehand to communicate really well. For those of you muttering that you can’t draw - probably the most difficult artistic requirement is the simple box. Admittedly, various exotically shaped boxes may be necessary, but you don’t need to be a Picasso trying out your cubist abilities. Learning mechanical and electrical drawing techniques was useful, but we must not downplay the incredibly powerful and achievable free-hand sketches we can create to explain a technical concept. I remember, as a young engineer, being fascinated by an experienced design engineer quickly and skillfully sketching on the back of his cigarette box. He communicated, succinctly, the modified wiring for a radar installation of a ship and then handed it to the marine electrician to continue with. It was idiot proof and powerful. We still have a ‘helluva’ way to go to easily draw on a computer though. It will be a good day when we can do this with the same ease and speed as on a piece of paper.
Donald Christiansen, of the IEEE, has written a fascinating and succinct summary of the progress made in engineering drawing over the past century (largely from the electrical and electronic point of view). In 1884, the technical journals at the time showed electromechanical telephones, telegraph keys, motors and dynamos all connected together diagrammatically - the only element shown symbolically was the battery. This is understandable as the battery would have been around a lot longer than telephones and motors. A few years later, the famous Nikola Tesla (the name of the new electric hybrid car), used circuit drawings that were a mix of sketches of generators and switches, but with symbols for coils, transformers and capacitors. The first part of the twentieth century saw the arrival of the wiring diagram - but still very pictorial in content. And then from the twenties onwards, electronics (esp. the vacuum tube) drove the development of schematics with symbols for some of the components; such as a vacuum tube’s grid (yes – I can still vaguely remember this), alternating between squiggles and dashed lines (the latter the eventual winner). And then “the box arrived”. The various functions of the radio receiver were called stages (e.g. the first one being the detector stage) and each was represented in a block format, as it represented an entire subsystem available “off the shelf”. Systems engineering has inspired a plethora of graphics tools ranging from flowcharts and Pert charts to matrices. Block diagrams play a key role here. The theory of system design uses a variety of exotic box diagrams and circles with arrows looping between them. Perhaps I am a little slow, but I am always dismayed by the complexity of these diagrams. The IEC has now abandoned the traditional logic gate symbols and also uses simple boxes for the ubiquitous ‘AND’ and ‘NAND’ gates. And the new resistor symbol is a long rectangle. Where has the zigzag shaped resistor gone to? As you would be well aware the integrated circuit (the ic) is also represented as a rectangle – even showing how the wires are connected together has now been abandoned due to the high pin count.
As Donald concludes somewhat wryly: “…. call it what you will - ¬block, square, rectangle - ¬the box is here to stay. Long live the box!”
The most extreme artistic expertise required of you, as an engineer and technician, is a box, so I urge you to redouble your efforts to communicate graphically wherever possible.
As engineering professionals, we must assist our children guard against what Karl Buhler believes: “…... As an essentially verbal education gains control, the child abandons his graphic efforts and relies almost entirely on words. Language has first spoilt drawing and then swallowed it up completely.”
In conclusion: Go forth and sketch!
3. Major disasters in PLC projects (and how to avoid them)
IDC Technologies proudly presents another live webinar in our popular series "Avoiding Engineering Failures"
When: Tuesday April 21
(Registrations close 24 hours before the first session). There’s a choice of 3 session times on the registration page at http://www.idc-online.com/IDCwebinar.html .
Where: At your desk!
What will it cover: This complimentary 45 minute webinar will touch on the many considerations of PLCs, including; installations, planning, purchasing, hardware and software reviews, testing, commissioning, and operational aspects. We’ll also look briefly at good practice for safety PLCs and the documentation requirements. It will not be brand specific.
This is a live, interactive webinar. And it’s free!
Join us from anywhere - and bring our PLC expert to your desk! If you are involved in PLC selection, programming and operation you will benefit from the session which will be live, in real time. All you need to participate is a computer with adequate internet connection, speakers and (ideally) a microphone.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Engineering whitepapers
We are building up a great source of complimentary engineering information. Thousands of useful articles are available on topics ranging from data communications, instrumentation to electrical and mechanical engineering. These are located by clicking on downloads at www.idc-online.com.
Go for outstanding engineering designs by suppressing your subconscious
I have been reading through selected bits of what must be an outstanding book on engineering design (Pahl, Beitz and Wallace). It is written, not from an electrical, electronics or mechanical engineering perspective, but from a designer’s, - and this is quite different.
According to these guys, design commences with abstracting an idea in an effort to identify the essential problems. This is where we, as engineering professionals, should really come into our own. Often so-called solutions are already available, but are based on fixed ideas and constraints which often don’t even exist. As the book suggests; it is absolutely critical that we avoid focusing on conventional or perceived solutions which are lodged in our subconscious. An extremely difficult task, as this involves stepping right outside of our comfy zones and thinking laterally. It involves ‘ignoring the particular or incidental and emphasizing the general and essential’. In other words we have to identify what the “crux” of the problem is. For example, in designing a labyrinth seal, the “crux” of the task is designing a shaft seal without physical constraints. Further questions regarding the “crux” should be asked. For example should “it”:
-
Improve the technical functions e.g. the sealing quality or safety
-
Reduce weight or space
-
Significantly reduce costs
-
Significantly shorten delivery times
-
Improve production methods
Each of these goals may result in different design outcomes. Only once the “crux” of the task has been correctly identified, can we move onto formulating the overall task.
I would love feedback from you on design problems you have encountered and the novel solutions you employed to solve them.
I was intrigued by Freeman Dyson’s take on design: “A good scientist is a person with original ideas. A good engineer is a person who makes a design work with as few original ideas as possible.”
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Two things on this fine day:
1. Major Disasters in Power Quality (and how to prevent them)
Why not join us for another in our series of live, online webinars on 2nd April 2009? These are complimentary and are available to you to thank you for all your support over the past 20 yrs.
2. Fill your Engineering Gaps
As an engineering professional, have you ever worked outside your comfort zone? It is a challenging experience, but ultimately rewarding - learning to master a new skill set which fills in a few gaps in one’s engineering knowledge. Many engineers and technicians would suggest that it is crazy to expose oneself like this. Ultimately, however, I believe the benefits outweigh the ‘dangers’. I presented a course recently covering a few topics outside of my areas of experience - I was somewhat daunted, but with some intensive work and considerable coaching from my peers beforehand, I managed to do a reasonable job (according
to the reviews anyway). My anxiety peaked when I was exposed to delegates with real experience rather than simply book knowledge. As a result of the preparation and then interaction with the class I have improved my knowledge in a fairly new area (but I was naturally very nervous). One of the things we do regularly at work is focus on the areas we are comfortable in (especially on a Monday morning after a serendipitous weekend) - why take a cold show when you can mooch through the day, working with stuff you are comfortable with?
We don’t need to go on training courses to skill ourselves in new areas - this is perhaps an obvious starting point - but the best way is to talk to our peers (they will be delighted to share their knowledge). But then we must actually work in these unknown areas to gain real experience. Take industrial automation for example. If you are working on calibrating and installing instruments all day, learn to set up a Profibus or Foundation fieldbus network, or examine the PLC or DCS coding for that tricky analog problem. Size the variable speed drives your peers are planning to install on the plant or have a look at the process design and get involved with the flow of the materials. If you are an electrical engineer working on power distribution layouts, move across to calibrate instrumentation and perhaps look at the IT issues with the SCADA installation of your plant. Being a widely multiskilled engineer is hugely advantageous today (let alone enjoyable). We may find our skills are in demand now; but tomorrow may be a completely different story. Investment in some short term reskilling may bring enormous benefits in the future.
One of the surprising issues in surveys on this topic indicates that specialists are even more highly prized than before - this would appear to make what I have said above a nonsense. What is omitted, however, is that requirements for specialities disappear after a few years and then reskilling becomes imperative. So the safest course is to constantly reskill in new and allied areas. The advantage of a wider skill set is the ability to view and approach a project more holistically, thus avoiding the embarrassment when unforeseen and inevitable problems arise. An example of this was when new locomotives were commissioned recently (in a notable city in the western world) and were found lacking as the power distribution network failed to cope with the power demands of these newly purchased railway engines.
Now, if you are really energetic, walk into your accountant’s office and offer to do the management and cost accounting for your area…..you will be horrified to find out how easy it is.
A comment by Wilbur Wright about the importance of engineering know-how is intriguing (and surely prescient of the admirable Capt. Sully who safely landed the Boeing, with failed engines, in the Hudson River - some 100 years later):
“It is possible to fly without motors, but not without knowledge and skill.”
3. Major disasters in Power Quality and how to prevent them
Our next webinar is on Thursday 2nd April: Major Disasters in Power Quality (and How to Prevent Them). Join us for this session – one, in our series of live, online webinars?
They are complimentary, short and informative (no sales spiel – promise)
This Power Quality webinar will be presented by popular IDC senior instructor, Terry Cousins.
You can choose one out of the three session times on Thursday April 2nd . All you need is a computer with reliable internet access (preferably broadband speed).
This 45 minute webinar will commence by contrasting the “ideal” with “practical” power systems, then move on to consider typical problems, their consequences and preventative measures and costs.
You can join us from anywhere in the world. And you can choose to either observe and listen passively or roll up your “webinar sleeves” and participate in the discussion! We will send you joining instructions once you’ve registered.
You can choose your session times and register at http://www.idc-online.com/IDCwebinar.html.
Registrations close 24 hours before the first session.
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Two things today.
1. WA Industrial Roadshow next week in Perth/Bunbury/Karratha and Kalgoorlie
We are running complimentary seminars on Industrial Ethernet/Electrical wiring regs/hazardous areas. More info : http://www.processonline.com.au/events
2. Engineering the intelligent building
It’s 7.00am. You wake up to the gentle sounds of your favourite CD playing. The lights in your bedroom "fade up" and then follow you around your home as you walk into the kitchen to drink your coffee - which has been automatically made for you. This scenario is happening now. One of my greener and more energetic colleagues has his own solar panels and windmill wired into his home for power and water when required during the day. He sells the power back to the local utility when he is not using it (admittedly for a few pennies, at this stage) – all built into his intelligent home.
People are supposedly using this economic slowdown to retool and re orient their economies to smarter and more efficient technologies (apart from Australia, that is. Instead it is building up more debt by proffering cash to the punters to hit K-Mart and Target to buy Plasma TVs and hit the pub - but let’s not go into this).
You can clearly see this area of industry of intelligent buildings expanding rapidly as it makes positive impacts on people’s comfort and provides real $$ savings.
So whatever you call ‘em, they are ‘in’: Intelligent buildings, intelligent homes, automated buildings, smart homes or building management systems. Whether private, commercial or industrial these intelligent buildings include a range of technologies such as energy management systems and building controls. Services provided include: lighting, heating, security, CCTV and alarm systems (for the more nervous amongst us), access control, audio visual and entertainment systems, ventilation, climate control. And even time and attendance control. Whether we like it or not; these changes are becoming more popular and prevalent.
There are two main types of building control systems:
- Time – usage only when required
- "Optimiser Parameter" – for example, using temperature for space heating or level of lighting to control lights.
The origins of intelligent buildings come from the industrial automation and process control systems in the 70’s. The technology was cleverly adapted for usage in buildings with great results. - another example of how technical developments in one sector can be used effectively in another.
Optimising heating is an easy target for intelligent control. It involves time based off and on facilities and is triggered too when a temperature reaches a certain level. Savings of up to 10% can be accomplished on heating with these controls. Lighting too is so easily controllable. It is infuriating to witness massive buildings lit up at 4am in the morning and typical savings can be in the order of 75% of the original load.
Something which is not much discussed, but which worries me somewhat are the safety and failure issues with intelligent buildings. Systems are in place, I am sure, to overcome these, but, for example a person becoming trapped in a burning building because the exit doors were locked. Or smoke impeding vision, the lighting system failing and there is a problem reverting to the manual system. (the electronic control keypad has failed)!
Despite these little anxieties on my part - how can we exploit these marvelous new technologies ?
- Read and talk to your peers more about this rapidly growing field
- Look at how you can apply these technologies in your own facilities and at home
- Examine whether your current technologies can be applied to the intelligent buildings
Although he was probably not thinking of building automation systems; Winston Churchill remarked rather wisely: " We shape our buildings, thereafter they shape us"
Yours in engineering learning
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
Two items today:
1. Real life cases of motor failures and how they were solved
Late last year we presented brief complimentary webinars on the subject of Avoiding Disasters in Industrial Wireless. This was very popular – we had to add extra sessions to handle the demand. Now, in keeping with the theme of; Avoiding Engineering Failures, we invite you to join us for the next in this series, entitled: Real Life Cases of Motor Failures and How They Were Solved.
2. How to do outstanding engineering and technical presentations
I often writhe in my seat when I listen to engineering professionals presenting technical content to an audience. These are often boring, unprofessional and generally a complete waste of time for all involved. The engineer frequently sweats profusely and talks to the whiteboard or to some imaginary spot in the room. And is enormously anxious that he or she will be “found out” with an awkward question.
You may ask why engineers bother with presentations at all? Perhaps you are a technologist and feel our focus should be on engineering design or the commissioning of a plant - not on time-consuming presentations. Well; the truth of the matter is that it is through presentations that we get our “engineering world” exposed to a wider and perhaps more appreciative audience. This often results in our own career advancement and, of course, helps gain greater credibility and consequently more business for our firms.
So here you go; a ‘toolbox’ of 5 tips to use when preparing and executing your next engineering presentation. With these you will distinguish yourself.
1. Show real passion for your topic and smile.
In some respects you are engaged in a sales mission. You are trying to sell your audience on what you are presenting. Show enthusiasm and commitment to the topic and real passion. You will sweep them along with you. Smiling counters the normal feeling that this is yet another dull, technical presentation, instead, it suggests something interesting and full of life.
2. Edit ruthlessly.
Don’t swamp your audience with tonnes of material. Limit yourself to 4 or 5 points to a slide. Include a lot of visual information - simple graphics which clarify the material and are easy to interpret. Avoid glitzy sound effects and multimedia pizzaz - this is generally lost on an audience. ‘Talking around’ a slide with a simple graphic is often a very powerful method of communicating. Mix it up a little by scribbling simple messages and graphics onto the whiteboard or flipchart. One of our best instructors refuses to use powerpoint and sketches all his diagrams and text onto a flipchart. He then hangs these sheets of paper all around the room – hundreds by the end of a day. He is generally exhausted after doing this, so watch your energy levels.
3. Listen carefully to your audience and interact with them.
(You often learn far more from your audience than they do from you). Watch their reactions and get them to interact with you. Test their knowledge along the way – a good way of gauging whether or not you are imparting the material successfully. The more the audience interacts with you, and each other, the more memorable an experience it will be for them (and for you) and the more likely it is that they will absorb the content.
4. Use real life samples.
As an engineering professional you will create a far greater impact with real life samples (an old colleague of mine calls them “props”) to support your content – for example; scored valves, blown up circuit breakers, pitted centrifugal pump impellers etc. And use pictures of real equipment in your slides. A demonstration of real stuff operating is a brilliant presentation tool - despite the inconvenience of transporting and assembling the bits at the presentation venue. Simple animations of equipment operating in power point can also be effective; provided they are contained and clear.
5. Practise, practise and then practise again.
Actually this should be the number 1 item in any toolbox of presentation skills. Practise every slide for timing and articulation. Speak slowly and clearly. Don’t rush – you will if you are nervous so make a grand effort to slow down. The more you go over your materials loudly in front of the mirror (or indeed the dog); the more confident you will be in front of your audience. And then you can focus on other issues, such as introducing amusing or interesting anecdotes, rather than simply reading off your slides.
Best of luck with your next technical presentation.
And above all, as Dorothy Sarnoff noted: ‘Make sure you have finished speaking before your audience has finished listening’.
Thanks and acknowledgements to Susan de la Vergne of Alder Business Services for her inspirational article.
Yours in engineering learning,
Steve
- Details
- Written by: Steve Mackay
- Category: Blog - Steve Mackay
Dear Colleagues
The economic stimulus package that president Obama signed into life last week had an interesting side effect. Most of the jobs created (or protected) require some sort of qualification or degree. According to Higher Ed (2/23, Ledeman), “a minimum of 54% of the 3.7 million jobs created require at least a post secondary certificate”. And a large chunk of the rest, require some sort of specialized training. So even though many of these programs are designed to help the more lowly-skilled and poorly paid, they really end up helping skilled workers. With a little thinking it is easy to list a great many manual jobs that have been replaced by automated machines which are then controlled by skilled operators – generally there seems to be a reduction in demand for low skilled workers.
It follows then that you can bet your bottom dollar your investment in your own skills will pay off. I am rather cautious, though, about highly theoretical, academic skills being conducive to further employment. But putting effort into improving your practical know-how and skills is surely a powerful way of staying employed – particularly ‘on-the-job’ experiential type training. I was inspired today after talking to one of our highly experienced power system protection instructors. He is a professional engineer who still seeks to actively improve his skills by reading extensively on technical topics, talking to his peers, attending courses and walking the factory floor (from the UK to North America to Asia) in an effort to observe and understand new manufacturing techniques. And he is poised to turn 80 next month. He has to turn work away “as he hasn’t had time to work in his garden recently”!
Although, we are naturally enthused about education and learning, the inimitable Oscar Wilde does sound a warning note: ‘Education is an admirable thing, but it is well to remember from time to time that nothing that is worth knowing can be taught’.
Yours in engineering learning.
Steve
Blog - Steve Mackay
EIT's Technical Director, Steve Mackay, enjoys keeping his blog up-to-date with useful tips and current industry matters for his fellow colleagues. He has a loyal and expanding following base reaching over 300,000 people around the world.
Student Stories
In this section you have the opportunity to read and listen to EIT students talking about the reality of the programs. Discussions are wide-ranging and include information about the study commitment required, the value of the qualification in their careers, the relevance of the subject matter, future pathways, and more. They provide valuable feedback for you to take into account before you decide to join one of our programs.
Career Information
Latest career information including industry research, podcasts, blogs, life hacks and general information about how you can make the most out of your career.
Education
Here you will find out more about the latest trends and developments within education worldwide, along with some helpful articles regarding study tips and keeping on track with your studies.
Developments
The latest innovation and inventions from the world of engineering can be found here. Learn about advances in technology and how they can make a real difference within your industry.
Announcements
Keep up to date with the latest announcements from the Engineering Institute of Technology. In this section you can read more about new courses, new recognition from professional bodies, our Excellence in Teaching Award, upcoming free webinars and much more.
Monthly Update
We understand that you may not have time to read all the articles that we post, so our monthly update gives you access to some fascinating articles which cover the best of the months news in a compact format.
Engineering Resources
The key objective of the Engineering Institute of Technology is to provide outstanding practical engineering and technology education. Together with several industry and educational partners we gladly share the following resources and information to assist you along your professional development path. Please note that some of the articles will open a new internet browser tab and redirect you to other partner websites.