Not Visible to Public

Should buyers require providers to use equipment that are owned by the buyers, the list of equipment should be provided in the tender documents. Buyers could also specify in the tender documents, any operating systems or technology that they want the providers to use.

Information on existing security systems can be made known to the tenderers for them to consider the usefulness and possible integration as part of the offered solution.

Define the baseline and ad-hoc or surge service items for price submissions. Forecast possible events that may require the deployment of additional manpower.

As a guide, buyers can consider a contract period of at least three years. Buyers can extend this to cover the nature of contract extension (e.g. lead time to notify contract extensions) and how it will affect pricing components (e.g. schedule rates and optional services).

Definition of the area of deployment which falls under the scope of the contract. It can include projections of peak or low activity volume at different locations. Sensitive or inaccessible areas which require increased surveillance or higher security classification should be flagged out in the requirements.

Definition of the type of security services to be rendered, the operating parameters which needs to be considered, with corresponding explanations and performance measurements on the outcomes to be achieved.

To determine clear, measurable performance metrics (both quantitative and qualitative) that are linked to security outcomes in the tender documents for subsequent evaluation of contractual performance

To track the performance of the providers’ performance based on a performance evaluation matrix/demerit points model

To encourage providers to meet or exceed performance standards on a regular basis, buyers are encouraged to adopt some form of reward system to incentivise providers.

Buyers can choose to adopt a Fixed Price Model or Price Review Model for the contract.