In the process of validating Customer A’s algorithm we used only two options as this was sufficient to demonstrate functionality.
Customer A decided to keep the structure of their plans simple (see below) as it met all of their requirements.
For Customer A, focusing on “what needs to be done” and “what is needed to do it” covered the necessary and sufficient elements to inform action. Monitoring “track, budget and time” was similarly considered adequate.
Customer A chose to retain all fields for reporting – on the basis that reports can be adequately tailored by deselecting appropriate information fields.
Disclaimer: This website is provided for general information and as such, should not be relied upon for any particular matter. John Salter provides this information as a general reference source only and has taken all reasonable measures to ensure that the material contained on this site is as accurate as possible at the time of publication. However, John Salter makes no representation and gives no warranty about the accuracy, reliability, completeness or suitability for any particular purpose of the information. To the full extent that he is able to do so in law, John Salter disclaims all liability, (including liability in negligence), for losses and damages, (including indirect and consequential loss and damage), caused by or arising from anyone using or relying on the information for any purpose whatsoever.