Mechanical Engineer | E.I.T | 4+ Years in Asset Integrity, Preventive and Risk-Based Maintenance, Equipment Procurement and Integration | 1 year away from P.Eng | Seeking Wisdom in Every Aspect of Life
One issue that some engineering procurement programs have, especially when both parties are under contract or working towards a contract, is the lack of clarity on what is expected of both parties. Sometimes this lack of clarity comes in the most simplest thing such as how the procurement artefacts are to be written, what technical information they will contain, and the format of such documentation. Such misalignment between the purchaser and the vendor comes at the cost of valuable company resources such as money, productive hours, and trust between both parties, as they try to gain clarity on expectations. This would slow down the execution of any program. Enter a document known as a Data Item Description, or DID. It is a type of contractual artefact that outlines how different technical documents required under contract from the vendor are to be written. They detail the format of the contents, the specific information required, and any supplementary documentation is required under contract. A DID is commonly used in military contracts, but it can be useful for all types of engineering contracts involving the procurement of valuable assets. I am not sure if the EPCM utilizes such types of contract documents (feel free to advise if you work in this space), but the DID, or the like, is a key tool to ensure all procurement packages are compliant to contract and that the execution of any procurement program runs as smoothly as possible. (Source: https://lnkd.in/g6sS-G5w) #DataItemDescription #TechnicalSpecification #EngineeringContracts #Procurement #ProcurementPackage #ProjectEngineering #AssetEngineering #Calgary #OilandGas #EnergySector #MechanicalEngineering
Marketing Specialist | Communications Strategy | Digital Marketing
2moInsightful