EG55F8/G8 Flow Assurance (2016)

Continuous assessment marking scheme and report tips

Dr Dominic van der A, Dr Yukie Tanino,
Dr Stuart Cameron, Dr Mark Stewart

Marking Scheme:
Dear Colleagues of EG55F8/G8, these general rules will be followed for marking your reports.
Marks reported below are out of a total of 100.

Introduction and Base data: 15 Marks. Description of main aspects of flow assurance
applied to this particular case will be appreciated. Base data used in the report given in
tables, with right format and units.

Methodology: 15 Marks. Coherent and clear description of the challenges and applied
methodologies to handle them.

Results: 30 Marks. Main results, detailed calculations should be listed in appendices.

Use correct format in tables, graphs and equations (see tips on this below - these will also
come in handy for your thesis).

Discussion and conclusions: 40 Marks. Discussion of the task outcomes and solutions
methods, conclusion should include an overall evaluation of the design and further recom-
mendations.

General comments:
A good Engineering report should follow a consistent structure and demonstrate understanding
of the main issues. Attempts to show critical awareness, i.e. thinking by you, are fundamental
characteristics of a good engineer and scientist. Good logic, sensible imagination and attempts
to extend the objectives of this assessment will always be rewarded.

- Every report should have a good introduction. Its good to bear in mind that this is
a technical report for readers with some technical knowledge, but the reader might not
necessarily be familiar with the details of flow assurance. Therefore, clarity and depth
should go together.

- Equations should be formatted by your selves (e.g. using Equation Editor), and where
required should be properly acknowledged and correctly referenced. Variables should be
consistent throughout your report, ie. dont use u for velocity in one section and v in the
next.

- The simulation requires to be clearly described, but avoiding software details. PIPESIM
is a tool, not a goal itself. When using software it is always good to address limitations
of the software and discuss how these might affect your design.

1
EG55F8/G8 Flow Assurance (2016)

- An important aspect of your report will be the care on the format of tables and graphs.
The axes are labelled using symbols ( rather viscosity) and units; ticks and marks
should go inside the graph, not outside; a figure is always followed by a caption where the
set of data is described, avoiding legend boxes and labels inside a graph. In general,
the default Excel format is always awful, really unclear, and requires changing. Variables
should also be reported in italic ( rather than ). Units should be quoted in roman
(Pa s rather than P a s). Do not copy-paste/Print Screen graphs from PIPESIM output
(theyre awful by default as well!), either modify the graphs following these comments or
plot the data using Excel, Matlab etc.

- Use tables to represent results of repeating calculations, there is no need to write down
the same calculation changing numbers. You could explain the methodology followed in
the calculations, and report the data in a table. Titles on the table should be clear, using
symbols and units (see below for an example)

- Every number should be followed by its unit (unless its dimensionless) and be sensible
with your decimal digits. Reporting viscosities, for instance, with 8 decimal digits is
as meaningless as answering the question What time is it? saying it is 20 hours 43
minutes, 3.898989890 seconds. Understanding uncertainties is a science by itself.

- Figures should be complemented with a description and discussion/analysis of the results

that are presented.

- Provide references for material that is not your own.

Example of a Figure:

Figure 1: Comparison of the literature data for solubility of CO2 in water at T = 373.15 K with
the experimental values obtained in this work. x0 is mole fraction of CO2 in water
Symbols: , this work; #, Kiepe et al. [11]; 2, Wiebe et al [29]; 4 Prutton et al [14];
Dashed line is computed from the model of Duan et al. [31]. Solid lines are fitted
values to a Krichevsky-Kasarnovski model.

2
EG55F8/G8 Flow Assurance (2016)

Example of a Table:

T (K) cp (JK1 kg1 ) T (K) cp (JK1 kg1 )

293.15 1690 373.15 2001
313.15 1766 393.15 2047
333.15 1828 423.15 2197
353.15 1908

Table 1: Isobaric specific heat capacity cp of DIDP at p = 0.1 MPa and temperatures T .

- The font style for variables is italic. Units, constants and text use Roman font style. This
rule applies to text, captions, axes titles....

- Use a standard format throughout the report. If you use Arial or Times New Roman or
Calibri, dont mix them. The University typically recommends a font size 11 with 1.5
lines line spacing for reports, but it is up to you.

- The X-axis always goes on the bottom of your plot, even when y is not equal to zero 0. In
this case, you force your x-axis to pass through the lowest y-value, and if zero is a value
on your y-axis, you generate a horizontal line at zero (generate a set of two values in the
x-axis with zero value in y, plot them and join then by a line without markers)

- A figure should not have external line borders (ie a frame).

- Information about the data should be included in the caption: avoid boxes with text in
the figure, except when you fit and equation.

- The tick marks one the axis go always inside

- Scales on the axes must display all the data in the plot centering these data in both axes.