Another kind of integration
Say the word "integration" to a control engineer and you may quickly find yourself ensconced in the realm of DCS and SCADA. But there is another type of integration that can be equally important to the success or failure of a project—contract integration. What is contract integration? It is, quite simply, knowing the boundaries of the "deal.
Say the word "integration" to a control engineer and you may quickly find yourself ensconced in the realm of DCS and SCADA. But there is another type of integration that can be equally important to the success or failure of a project—contract integration.
What is contract integration? It is, quite simply, knowing the boundaries of the "deal." Take it from a lawyer who spends considerable time navigating within the automation world: it is amazing how many companies neglect this most basic of legal principles—to the point where the process may be integrated but the legal requirements are not.
There are two typical ways in which contract integration can get off track.
The first is the lack of an "integration clause" in the project documents. This is the paragraph of the contract where it says (and I am colloquially paraphrasing): "This document that we have just signed is the only document that matters. None of the other documents that we previously exchanged or oral promises that we previously made mean a darn thing. In fact, please feel free to take any other documents (including both the RFP and accepted proposal) to your backyard and burn them. They are empty promises."
In case you are wondering, such a paragraph (even as overblown as I have made it) is binding throughout North America. But the larger point is that if there is not such a paragraph, it can be exceedingly unclear which terms apply to the project and which do not.
The other typical way that a contract's integration becomes unraveled is through what lawyers call "incorporation by reference."
Like Russian nesting dolls
You know those Russian nesting dolls where one painted wooden doll can be pulled apart to reveal another figure of the same sort inside—which itself can then be pulled apart to reveal yet another—and so on? That image probably is a pretty decent stand-in for this legal concept.
Let's say that before you sign a contract or a purchase order, you check it quickly for any problematic terms. Nothing jumps out at first glance, except there does seem to be a list of items identified as other contract documents. You pass that by and sign.
Check other obligations
Guess what? You may think you have reviewed the whole agreement, but you have not. Every one of those other listed items—each likely with its own "nested" terms— are also a part of what governs your company's performance. Better get your hands on each and every one of them and figure out how they relate. Otherwise, you may be on the hook for obligations that you have never even talked about—let alone reviewed ahead of time in written form. (In perhaps the most common version of this, a related contract to which your company is not a party, with all of its specs, is incorporated by reference.)
Now for a surprise ending: There are those situations (quite a few of them actually) where a lack of integration—in the legal sense of the word—can be advantageous. The essential question to ask is "in whose interest is clarity—ours, theirs, or everyone's?" While I would argue that in most cases the answer is "everyone's," there are exceptions. And if that is the lay of the land, you are hereby granted permission to go forth and make the contract less integrated—and more confusing.
Mark Voigtmann is a lawyer with Baker & Daniels, LLP (Indianapolis, Chicago, Washington DC and China). His group assists the automation and process industry in structuring projects and resolving disputes. Reach him at Mark.Voigtmann@bakerd.com or 317-237-1265.
Case Study Database
Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.
2012 Salary Survey
In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.
Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.