.

Generate cement program documentation

Generating a job program and reports is an obvious statement but so important that it deserves
a section in this chapter. Engineers often perform many
simulations and sensitivity analysis when designing a cement job for a specific casing string.
For traceability, it is imperative that a final program is generated, or a file saved, that includes
all of the assumptions that contributed to
the design. This cement program may be referred to during the performance
of the cement job, and may also be referred to throughout the life as the well
.for insights into the cement that is placed in the well
Cement program and design files range from very simple one-page programs to complex
100+ page programs. The length and complexity of the
,cement program depends on the complexity of the well and the regulatory
reporting and design requirements for the well operator, the driller, and the
service provider. While difficult to propose a “standard” program, the operator, driller, and
service provider should agree what type of summary, hard
.copy and digital files will be in the cement program
The cement program, together with the cement job data and the laboratory tests define the
cement system and how it has been installed in
the well
Perform postjob simulations to compare wellsite observations to
.simulations
.RWF 10. Perform postjob simulations for job evaluation
Comparison of well site data with simulation data are recognized as one
method for determining that the cement job has met the objectives. This
is a logical step after performing all the prejob simulations. Comparing
job data with simulation is not the only way, however, to evaluate a cement
job. Please also refer to Chapter 11, Job Evaluation, for more details on
.cement job evaluation
There are several significant components in the workflow for comparing
job data to the simulations. First the data must be collected and entered into
the simulator. The fluid sequence needs to be set, and then the simulated