Civil Engineering Reference
In-Depth Information
eTendering/eEvaluation
Dos
Don'ts
Consider the quantity/complexity of the
purchasing requirement when preparing the
specifi cation for the system(s) and standard
electronic procurement documentation
Ignore the existence of the client's
existing systems and check for
compatibility/ease of adoption
Prepare a Business Case for using the
eProcurement systems for client approval
Underestimate the support arrangements
required when developing resourcing
profi les for the procurement function
Consider the type of goods, works and
services to be purchased and the marketplace
when deciding the type of eProcurement tool
to implement, e.g. is reverse auctioning likely
to be required?
Forget to consider the marketplace and
its ability to use an e-tendering system,
e.g. are suppliers mainly SMEs without
access to IT?
Develop a suite of standard 'non-editable'
procurement documents to instruct suppliers
on the use of the system and the procurement
process
Limit access for publishing procurement
documentation
Centrally control the development and update/
upload of standard procurement
documentation
Consider reporting requirements pre- and post-
contract, e.g. the ability to agree performance
measurement criteria at pre-contract stage for
eReporting post contract
Ensure comprehensive training for all users.
Make sure that whatever e-sourcing system is
used is free for suppliers to use and they have
access to free support in the use of the
system
Carefully consider what is expected from
suppliers and then make sure the questions
clearly defi ne the fi le names of the responses
required, e.g. 'Please respond with a fi le
named B01_experience'
Think carefully about mandatory questions.
Ensure that you mandate only what is
necessary
Make everything mandatory
Take time to agree with all stakeholders the
evaluation model and then test and prove it
before live application
