Last month I wrote about selecting an integrator [System Integrators Bring Value, Oct. 06]. This month I have an additional chance to offer some guidelines for creating the best outcome from the integrator relationship. Theres no one correct path to follow when working with an integrator, but this might give you some idea of things to aim for and avoid.
DoCommunicate properly. Meet with the integrator early and often to define your system requirements. Identify a contact person for each aspect of the project who can provide or direct support. Hold brief, regular, top-level status meetings to assess progress and risk.
DoDevelop a realistic schedule. Many times a machine builder will put together a schedule based on external demands rather than real project requirements. Cost and schedule are mortal enemies. Take those realistic time schedules, and add time to handle unexpected issues.
DontAssume your integrator will be ready for you anytime you call. If its a good firm, itll be busy. Try to give advanced notice of when youll need their services. This will save you time and money in the long run.
DoCreate detailed, complete specifications. If you cant create them yourself, expect to pay someoneprobably the integratorto create them for you.
DoConsult the integrator before specifying hardware. An unbiased integrator, i.e., one that doesnt sell the recommended hardware, can be an excellent resource for hardware selection. Extremely important: make sure the hardware can handle the system requirements. The time required to make a workaround with improper hardware can be extremely expensive.
DoMake sure the system is as fully wired and mechanically functional as possible before engaging the integrator on the shop floor. One approach is to have the integrator develop a simple I/O screen, so lower-cost personnel can verify that subsystems are functioning and sensors are adjusted before the higher-priced engineer starts. Use less-expensive resources for legwork, both in preparation and execution of your project. Keep your integrator focused on development.
DontExpect a new program to fix machine issues or vice-versa.
DoLearn from the integrator and ask questions about the inner workings of their development. Learn what you need to know so you can better support the system yourself, if you so desire.
DoAdd your own expertise. Expect integrators to bring their knowledge into your project, but your specific domain expertise is invaluable. Bring your knowledge to the table to avoid reinvention or, even worse, repeats of past mistakes.
DontIgnore an over-budget situation while it continues to grow. Deal with estimate discrepancies while there is time to rectify the causes.
DontShip a machine early. I wrote an entire column on this topic called "The Perils of Shipping too Soon," Sept. 06.
DoUnderstand the tradeoffs between fixed-bid and hourly projects. Biggest drawbacks with fixed bid contracts are lack of flexibility with the design and inherent problems dealing with change-orders for every specification change. Be careful when selecting a low bidder. As the saying goes, you get what you pay for.
With hourly contracts, integrators are more likely to underestimate the time required for projects. This is human nature. People are more conservative when the risk falls on them, and more optimistic when its you who assumes the risk. A benefit (and drawback) with hourly projects is that the integrator will be more accommodating to changes along the way. This flexibility can increase project costs quickly.
DoEnsure that your company owns or has an unlimited license for any software written for the project. Some integrators retain full control over the code created. This gives them some job security. It does nothing for you.
DoAppreciate that the integrators must make a profit. Its in your best interest that they dont lose their shirts on your project. This is true especially if you plan to rely on them for long-term support. However, you should negotiate for a lower rate. Integrators often will agree to a lower rate in exchange for a guaranteed volume of work. It never hurts to ask.
DoAccept some responsibility when things go wrong. If there are scope changes, hardware issues that cause delays, or lack of material, personnel, etc., this will result in additional charges.
|About the Author|