Case Studies

Rivers Field Project (Burlington)

This was the first CMS project and formed the basis of the model used today by Rowden Software Solutions.

The initial phase was to conduct a requirements capture and agreed a solution using software prototypes. The client’s contractors had specific MC forms that were read only word documents. We added a unit to auto populate the word documents, once the forms were mapped (so that the CMS knows what data to print and where to print it on the form) then the salient data (tag, Area, location, etc.) could be auto populated and the form printed as and when required by the commissioning engineers. The work was specified on an ‘as needed basis’, so once the basic status engine and data base components were in place the import module was written. Finally reports module was completed.
Despite a very tight schedule, we delivered the CMS solution on time and on budget.

Rivers Field Project Steam Drum (Burlington)

This was a ‘brown field’ project to replace a component. It brought out extra requirements in the work-packs and job-packs of the MC phase. This led to a ‘diamond’ hierarchy in which a Tag now has two parents: it’s MCPack and its Job-pack; both of which will receive progress events from the Tag when its forms are completed.

Chevron GACE

The Chevron GACE project identified the need to be able to import most, if not all of the setup data. By this time the CMS model had been refined and has evolved somewhat ‘under the bonnet’ making it more configurable to the actual changes between projects. Import data is created by the team as Excel Spreadsheets. These sheets can be dragged and dropped onto the CMS. Almost all the CMS configuration data can be imported in this way. This provides a set of archive-able source documents – if these documents are version managed then an audit trail is possible.
Improvements to the reference data model mean that more things can be handled automatically and in a configurable fashion. This version added some 60,000 lines of source code.