Call-off is usually best for short projects with an existing client who has specific local training and implementation issues to be addressed with a small group of competent users. Typically these projects last for so many days, maybe a week or two over a period of a month or two, and act as a major catalyst for the site to establish better procedures and greater understanding of Athene. Thus it is a pointer towards how to do things, with typically just a few pilot nodes set up and initial reports and models generated. The site then has enough expertise to take the implementation forward. For this investment of say 5 - 10 consultancy days, a site can go forward with much greater confidence in the expertise of its own staff and the procedures they have established.
The specified requirement will be typically one page of text outlining the understanding of what the client needs the consultancy to address. This will include useful background information e.g. hardware details, software environment, packages/application of concern.
This will be typically one page of text outlining the approach. Logically the paragraphs of this section mirror the stages in the work involved such as:
- Data capture and collection – by Metron or client
- Data analysis - on site or at Metron, how the data will get to Metron
- Performance reporting – describe briefly the level and frequency of reporting envisaged
- Planning - describe briefly the build, calibrate and describe ‘what if’ process
- Recommendation and formal reporting - written report, presentation on site
A short and sharp set of bullet points that outline what Metron will provide. A clear definition of what Metron will do and provide so that any new requirements that the client subsequently raises can be agreed as additional. This should make it clear specifically what questions are being answered, what effort is involved at the client site etc.
Typical areas covered include:
- Who will implement Acquire and collect the data
- Any on-site facilities needed (e.g. printing, copying)
- Pre-requisites for machine access
- Access to relevant staff for information, e.g. about current system; ‘what if’ information
|
