I am currently in the infancy of exploring Knowledge Management as a research topic using design thinking, specifically the problem relating to imminent retirements of many experienced contract & commercial managers coupled with the new gig economy and the different ways gen y & z embrace learning and governance.
Ie How do you capture this experience before it is gone and then bottle it for transmission in such a way that the new generations will utilise it to the fullest to ensure good governance and business efficiencies are maintained.
For IT services agreements I generally rely on the framework of ITIL ( Information Technology Infrastructure Library) - this informs on the various processes within IT and will give you a starting point to understand what needs to go into your playbook. It deals with both the vendor/customer aspect as well as for procurement.
Hi Mary Jo - great question. We've tried to take a lot out of the workload by investing up front in standard templates as much as possible. If you're only then putting in place objectives and milestones and special conditions to deal with unique risks whilst keeping the rest as identical as possible, we found that we've saved a lot of time and effort out of the process. Our former solicitors / lawyers were a little bit upset though !
Where possible, we've also tried to align legal manager to a procurement category. That helps balance things out but that way, they also see that there are themes or risk that might resonate within that area or require a new standard contract term.
Hope this helps
Hi Darren, Thank you for your response. Can you clarify what you mean by "we've also tried to align legal manager to a procurement category"? Would a procurement category be a business segment?
• Fire and Emergency NZ
Hi Mary Jo - sure. Business segment, category or team - by whatever name, we're talking the same.
Hope that this helped, and would love to hear any comments as to how others have done this as well ! b
I would expand to the inclusion of customer name/logo use in marketing material as there would typically be some sort of agreement prior to such marketing material being used. Maybe strike the language or amend to clarify?
• Philips India Limited
I have had experience when we signed non-binding MoU for JVs. The most likely scenario would be that the JV partner may like to advertise to the greater world that they have signed on a path breaking MOU etc., especially if these partners are listed entities. So its advisable to make it explicit that disclosing the existence of agreement covers not just "verbatim" disclosures, but other modes as well - including social media...unless explicitly agreed between the parties.
I agree with the other replies here, the NDA should cover marketing material. It's common courtesy to check the other party is ok with this being shared and customers I have had have explicitly blocked this as a company policy.
Whilst it's the way that a lot more suppliers seem to be going, if you think about this in with your procurement hat on - and that is what's going to happen at the end of 3-5 years - it's tough to see you doing anything but just rolling this over (and over and over again) as someone else has all of your data on their server.
At the risk of being awfully contentious, my own experience is that in a lot of circumstances, there's little consideration of whole of life costs - especially with that thinking about what's to happen in 3-5 years. Right now, many of these purchases done right now are flying under the radar of procurement teams because they're below procurement limits or just being called operational expenditure within business delegated authorities.
That said, one of the benefits that I've also seen is that upgrades happen automatically on the server of the host without the business having to create teams to do this, especially where there was a major upgrade - which were previously a big financial impact on many businesses.
Hope that this is useful.
New International Technology Co.
I suppose this depends on what you mean by a Contract Agreement. If you have a Master Services Agreement in place that contains agreed legal terms and conditions, signed off by both parties, then the RFP process could proceed. However, depending on the types of good or service being sought, i.e a major construction project, then the terms and conditions within the Master Services Agreement may not be appropriate, its always best to consult a legal professional before you issue the RFP to ensure all legal provisions are either sufficient or addressed.
• AJA Global Consultancy Services, LLC
Pallab, I may be missing something from your description of the issue; or what you describe as "execute a Contract Agreement (signed by both parties)..." could be the reason of my confusion.
It is not clear to me if your organization represents the buyer or purchaser side (who is the party making pressure to move ahead). But anyway, the practice you are describing seems to me as the typical recipe for potential claims. As Gary says in his reply: seek in-house legal advice.
Sorry I can not be of much help.
• Bahrain National Gas Co. (B.S.C)
What I mean by the Contract Agreement is the Form of Agreement which is generally the first covering pages of any standard Contact wherein it is stated..
This Agreement is entered into on the xth day of ... by and between ......
followed by the list of documents that together constitute the Contract and showing the precedence of documents in the event of conflict between the documents.
A blank Form of Agreement is provided as a format along with the tender documents which is finally filled up and signed by us and the successful tenderer. The format when filled up and signed, we call it the 'Contract Agreement'. This document is used for tenders (for services, construction works, etc.) having reasonably high estimates where full tender package is used to invite bids.
On the other hand, for small supply orders ( spare parts, plant consumables, etc.) a system generated RFP document is used to invite bids and eventually a system generated PO is issued referring to RFP document and supplier's quotation.
Now let me rephrase my question as - is there any thumb rule ( example- bid estimate) that could be followed as a criterion to determine
• when a full fledged tender document to be used to invite bids and finally a Form of Agreement is signed off to conclude a Contract, and
• when a simple RFP document to be used to invite bids and and just a system generated Purchase Order is issued to the winning bidder, and no Contract Agreement is executed.