HSEC Engg Procedures Manual

ENGINEERING Doc.
No: HSEC/QSP/ENG/01
PROCEDURES MANUAL Date: 20.05.2009
Table of Contents
1 TENDER PROPOSAL/PREPARATION 3
1.1 Projects 3
1.1.1 Proposal format 3
1.1.1.1 Background 3
1.1.1.2 Objective 3
1.1.1.3 Scope of Work 3
1.1.1.4 Resources 4
1.1.1.5 Timescale 4
1.1.1.6 Price 3
1.1.1.7 Terms and Conditions 3
1.2 Start up 7
1.2.1 Objective 7
1.2.2 Administration 7
1.2.3 Project planning 7
1.2.4 Delegation 8
1.3 Ongoing work 9

1.3.1 Quality control 9
1.3.2 Progress and cost monitoring 9
1.3.3 Reporting 9
1.3.4 Billing 9
1.4 Job completion 10
2 INVESTIGATIONS GENERAL 11
2.1 General 11
2.1.1 Introduction 11
2.1.2 Field records 11
2.1.3 After the field trip 11
3 DESIGN 12
3.1 Design process 12
3.2 Calculations 13
3.3 Planning of drawings 15

3.3.1 General 15
3.3.2 Drawing titles 15
3.3.3 Drawing numbers 15
3.3.4 Scales 18
3.3.5 Layout of drawings 18
3.3.6 Sections and details 19
3.3.7 Blocks 19
3.4 Drawing standards 20

3.4.1 Material 20
3.4.2 Drawing sizes 20
3.4.3 Title blocks 20
3.4.4 LAYER DEFINITION 21
3.4.4.1 CIVIL DRAWINGS 21
3.4.4.2 ADDITIONAL LAYER DEFINITION 23
3.4.5 Plot Style Table 24
3.4.6 Dimensioning 25
3.4.7 Text Style 26
3.4.8 Hatch 26
3.4.9 LINE TYPE 27
3.4.10 Care of Backup 27
3.5 RC detailing 28
3.5.1 General 28
3.5.2 References 28
3.5.3 Design considerations 28
3.5.4 Detailing 29
3.5.5 Drawings 29
3.5.6 Bar schedules 30
3.6 Approval and issue 32

3.6.1 Designer's check 32
3.6.2 Independent check 32
3.6.3 Recommendation for approval 32
3.6.4 Approval 32
3.6.5 Drawing issue 33
3.6.6 Preliminary prints 33
3.6.7 Revisions 34
3.6.7.1 Revision Index 34
3.7 Registration and storage 41

3.7.1 Drawing registration 41
3.7.2 Drawing storage 41
3.7.3 Calculations 42
3.8 Quantities 41
4 REPORTS 41
4.1 Introduction 41
4.2 Layout 41
4.2.1 Overall structure 41
4.2.2 Headings and numbering system 43
4.3 Writing 41
4.3.1 Preparing to write 41
4.3.2 Good English 41
4.3.3 Spelling and punctuation 42
4.3.3.1 Spelling 42
4.3.3.2 Abbreviations 42
4.3.3.3 Capitals 43
4.3.3.4 Numbers 43
4.3.4 Dates 43
4.4 Illustrations 41
4.5 Format 41
4.5.1 Typing 41
4.5.2 Production 42
4.6 Review and issue 41

4.6.1 Checklist 41
4.6.2 Approval 41
4.6.3 Issue 41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/PMP/00
PROJECT MANAGEMENT Prepared Approved
Date: April 24, 2019
PROPOSALS
1 TENDER PROPOSAL/PREPARATION
The form that a particular tender/proposal takes will depend on the nature of the request and on the
potential nature and value of the proposed project. The following sections provide outlines for
tender/proposals for potential projects of different size. The outlines should be used for the sizes of
project indicated and may be adapted to meet particular project or client requirements. In each case,
the general format should be followed.
1.1 Projects
Project is an undertaking job by Hydro Solution. Projects may be small or of a large scale.
1.1.1 Proposal format

A sample front cover for a tender/proposal is given onHSEC/F/PPC/00: the approval box should only
be on the inside front cover.HSEC/F/PMPCP/00 illustrates sample contents page for a project
proposal. The following sections describe the standard proposal format.
1.1.1.1 Background
This section should clarify the intent of writing a proposal to the client clearly. It should include the
details of all the communication between the client and Hydro Solutions up to the point of writing
the proposal. Client’s requests for the proposal preparation should be particularly referenced along
with the date and the nature of that request.
The Background section should also show the client that his requirements are clearly understood by
Hydro Solutions. Appropriate reference should be made to the context of the proposed project.This
section should reflect the client’s requirement clearly that there is a clear need for the services and
Hydro Solutions can oblige with those requirements. Hydro Solutions shall use any materials
provided by client at the time of the preparation of the proposal request.The proposal documents
should include the same terms and phrases as used by the client.
A complete background section should clearly indicate to the client that his proposal requirements
have been understood by Hydro Solutions with whom he has requested a proposal.
1.1.1.2 Objective
The objective of the project should be clearly stated in terms that reflect the client’s objective for the
study. The objective shall always be to meet the client’s requirement, not to complete the scope of
work. There should only be one objective. The objective should be written as per the “SMART”
acronym (Specific, Measurable, Achievable, Realistic, Time bound). When required, sub-objectives
may be set for specific tasks but they must fit with the main objective and must also be “SMART”.
1.1.1.3 Scope of Work

This section explains to the client what he will receive in return for placing a contract with Hydro
Solutions and paying the contract price. The scope of work must relate clearly to the objective and
sub-objectives.
The scope should be detailed as tasks where there is a logical progression between the tasks in
pursuit of the objective. There should be sufficient detail to convince the client that he is getting
3
PROPOSALS
value for money. Only the nature of each task should be given. The manpower requirements,
duration and price will be given in later sections of the proposal.
Within the “Scope of Work” section, there should be a sub-section which outlines the reporting tasks
for the project. These will tell the client which reports he will receive, when he will receive them and
the nature and timescale of actions expected of him in response to the reports.
1.1.1.4 Resources
This section tells the client, the resources which Hydro Solutions will mobilise to meet his
requirement. The main resources to be detailed in this section are people, equipment and office
facilities. The names of the key people should be included and reference should be made to their
CV’s in an appendix.
Standard lists of equipment and office and site facilities should be used and adapted to be relevant
to each proposal.
The client should be given the impression that Hydro Solutions is well staffed and well equipped and
that he will benefit from such staff and equipment if he places an order. This section should impart
and impression to the client that Hydro Solutions is well equipped and well staffed to comply with
the clients need and that the clients will benefit from hiring Hydro Solutions for their order
1.1.1.5 Timescale
This section should explain the appropriate time scale for the above scope of work to be completed
with above resources to the client.
For numerous tasks, Microsoft Project should be used to produce project planning chart. For a
smaller number of tasks (<10), GANNT charts or any other charts produced in Word or Excel can be
used.
The chart should clearly show individual task start and finish dates as well as those for the overall
project. Key reporting dates and/or project milestones should also be marked.
4
PROPOSALS
1.1.1.6 Price
This section should clarify the client on what he will have to pay for the above scope of works.
The total value of the project should be stated clearly, as should the nature of the price; fixed price
or cost plus. For small projects the price should be lump sum with no breakdown given. For cost plus
projects the price should be stated to be an estimate of the total price payable and the standard
Hydro Solutions schedule of rates should be included and referred to as an appendix.
N.B. Always refers to price, not cost. The price is what the client pays. The cost is what Hydro
Solutions pays to complete the project. Price includes cost and the profit margin for Hydro Solutions.
1.1.1.7 Terms and Conditions

Each proposal must be accompanied by a standard set of terms and conditions.These are given
below.
1.1.1.7.1 Price
For fixed price proposals the following clause should be included.
The above price is fixed and relates to the above Scope of Work, based on Hydro Solution’s current
understanding of the Client’s requirement. Should that requirement or the scope of work change the
above price will be void and a new price based on a revised scope of work will be submitted to the
Client for review and approval.
For cost plus proposals the following clause should be included.
The above price is an estimate of the total price payable and relates to the above Scope of Work,
based on Hydro Solution’s current understanding of the Client’s requirement.The actual amount to
be charged to the client will be determined by the man hours expended and costs incurred by Hydro
Solution, based on the schedule of rates given on Annex *, in completing the above scope of work.
3
PROPOSALS
1.1.1.7.2 Payment
For fixed price proposals, following clause should be included.
The above fixed price is payable in two lump sum instalments. Fifty percent of the Project Price shall
be included with the written instruction from the Client to proceed with project. The remaining fifty
percent shall be paid upon receipt by the Client of the project final report.
For cost plus proposals,following clause should be included.
The above price is payable as an advance followed by payment of monthly invoices submitted in
arrears. An advance to the value of fifty percent of the Project Price shall be included with the
written instruction from the Client to proceed with the project. Thereafter Hydro Solutions will
submit monthly invoices based on the man hours and costs incurred by Hydro Solutions in executing
the project during the previous month.
For both, fixed price and cost plus proposals, following clause should be included.
Payment is to be made within thirty days of the date of each invoice submitted. Delay in payment
beyond thirty days may result in an interest charge at the annual rate of four percent above the
prevailing Nepal Rastra Bank Base Lending Rate.
1.1.1.7.3 Contract
The above proposal is not a contract between Hydro Solutions and the Client to undertake the scope
of works detailed herein. Prior to the initiation of the project, a project contract based on the FIDIC
Client/Consultant Agreement shall be entered into by the Client and Hydro Solutions.
1.1.1.7.4 Validity
The price and timescale given in the above proposal shall be valid for a period of forty five days from
the date on the front cover of the proposal. Following expiry of that date and if requested by the
Client a new proposal with new price and timescale will be submitted to the Client by Hydro
Solutions.
1.1.1.7.5 Confidentiality
This proposal and its contents are to remain confidential to the Client and Hydro Solutions. The
contents of this proposal document are in no way whatsoever to be divulged to any third party
outside the Client and Hydro Solutions. Failure to observe the confidentiality of the proposal will be
deemed sufficient for Hydro Solutions to withdraw the proposal and decline to enter into a project
contract with the Client.
4
PROPOSALS COVER
XXX Hydropower Project
Proposal No:
Submitted to:
Name Initials Date
Prepared
Checked
Approved
Note: The signature table not to be included on the cover page of the proposal. Instead, use the
same cover page with the table right after the cover page for signatory purposes.
Proposal date
Submitted by:
Hydro Solutions P. Ltd

Engineering Department
Thulo Bharayang, Shoyambhu -15
Kathmandu, Nepal
Tel: +977 01 4672598, 4672599
Fax: +977 01 5527901
Email: info@hydro-solutions.org.
Website: www.hydro-solutions.com
5
PROPOSALS CONTENT PAGE
Proposal Format
Background
Objective
Scope of Work
Resources
Timescale
Price
Terms and Conditions
Price
Payment
Contract
Validity
Confidentiality
6
START UP
1.2 Start up
1.2.1 Objective
The objective for a job completion should always be within the allocated time frame, allocated
budget and in par with appropriate applicable standards meeting the requirements of the client. It is
therefore essential that the client's requirements be understood and clarified where necessary, so
that there is no doubt about the scope of work or quality of output expected.
It is the responsibility of the Project Engineer/Team Leader to ensure that the client's requirements
are agreed and documented, and that any changes as the work proceeds are likewise agreed and
documented.
1.2.2 Administration
At the start of a new job the Director, Technical will assign a Project Engineer/Team Leader to take
responsibility. The Project Engineer/Team Leader shall select a suitable brief job name, in
consultation with the Director and advise the Hydro Solutions Administration Officer, who will
allocate a job number when required. The Administration Officer shall advise Hydro Solutions
Accounts Dept of new job names and numbers.
The job name is used as a prefix to drawing numbers and correspondence file numbers (a 3 to 5letter
job code).
Proper guidelines for correspondence system and other administrative utilities involved with a
project are still in the pipe line. It is advised that regular system of correspondence should carry on
until new guidelines are established. A written record of every correspondence incoming and
outgoing is expected for now.
1.2.3 Project planning

From the start of the job there should be a programme and budget and an estimate of the resources
needed to complete the job. These may be refined as the job proceeds, but are essential tools for
project management.
Systems for monitoring progress and costs, reporting, review, document control and quality control
should also be set up at the start of the job.(See HSEC/QSP/PMOGW/00).
7
START UP
1.2.4 Delegation
On all but the smallest jobs, the Project Engineer/Team Leader will normally delegate responsibility
for part of the job to someone else. It is the responsibility of the Project Engineer/Team leader to
ensure that work is only delegated to suitably qualified personnel equipped with adequate resources.
The Project Engineer/Team Leader shall provide such persons with written instructions defining the
extent of responsibility delegated, the time when the work is to be completed, a time budget, job
number and procedures for review: for design work this shall be by means of theDesign and
Development Input Output form (Form HSEC/F/DDIO/00).
8
ONGOING WORK
1.3 Ongoing work
1.3.1 Quality control

The Project Engineer must ensure that all members of the project team understand their own
responsibilities and adhere to the quality control procedures.
1.3.2 Progress and cost monitoring

The job shall be broken down into the principal activities, against each of which is entered the
estimated time, quality specification, cost and completion date. Actual progress, time and expenses
should be calculated each month for comparison with the earlier estimates.
The Manager should be informed about any forecast delays or cost overruns, and appropriate action
agreed with him. The client and other affected parties may also need to be informed.
1.3.3 Reporting
Written reports from the Project Engineer should be used to inform concerned parties about
progress of the job, and to highlight any problems. The file copy should be circulated to the Manager
before filing.
1.3.4 Billing
Clients should be billed regularly and promptly as set out in the project agreement. Billing will be
undertaken by Hydro Solutions accounts staff at the request of the Project Engineer.
9
JOB COMPLETION
1.4 Job completion
Before completion of a job the Project Engineer is responsible for ensuring that:
the client's requirements have been satisfied (refer to Terms of Reference,

Contract and subsequent changes)
as-built drawings have been made where relevant
final reports have been written, checked and submitted (eg design report,
operation and maintenance manual, completion report, as necessary)
all accounts have been finalized
all calculations, files, drawings and reports have been finalized, indexed and
stored properly, after discarding superseded and obsolete material.
any material likely to be of use in future jobs has been suitably written up and
lodged in the library
all books and references have been returned to the library
10
GENERAL
2 Investigations General
2.1 General
2.1.1 Introduction
Field investigations may be required for a variety of reasons, such as:-
 Geological investigations
 Hydrological gauging
 Community and environmental studies
 Engineering planning and assessment
 Operation studies
2.1.2 Field records

Information gathered during field investigations must be recorded directly into a field notebook or
appropriate data form, and should be checked while at site.
Photographs should be used to aid note taking and for record purposes. Also consider taking
photographs for report illustrations and for the firm's publicity. Cameras with a data-back should be
set to record the date on each photograph, except on photographs intended for publicity.
2.1.3 After the field trip

After the field trip the records should be appropriately filed and written up while the memory is still
fresh.
Photographs taken should be promptly stored in the corresponding project file in the computer
under separate Images folder.
11
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DADDP/00
DESIGN PROCESS
3 DESIGN
3.1 Design process
The design process for a structure will generally be as follows:
a) Assemble all relevant data
b) Set out design assumptions and criteria
c) Prepare outline design proposal
d) Independent review
e) Detailed design and drawings prepared for tracing
f) Independent review
g) Drawings traced by draftsman and signed by him/her after checking
h) Drawings checked by designer and signed by him/her after checking
i) Drawings and calculations checked by another engineer and signed by him/her after
checking. N.B calculations must be checked and signed before drawings are signed by
checker
j) Drawings recommended by Project Engineer for approval
k) Drawings approved by Technical Director
l) Drawings issued
The independent reviews at Stages (d) and (f) are helpful in avoiding abortive work, but one
or other may be omitted in some cases. They may be carried out by the Team Leader,
Project Engineer or Technical Director, and sometimes also by the client at Stage (d). The
detailed check of the calculations may be carried out before the drawings have been traced
if that is more convenient.
The design process is controlled by aDesign and Development Input and Output form
HSEC/F/DDIO/00, which should be issued by the Team Leader to the design engineer before
work starts, and should be completed (in ink) at each stage. It should be filed at the front
of the calculations. Any non-conformance with requirements should be noted by the
checker or reviewer on the design control form: if there is insufficient room, notes should
be written on a subsequent page which is referred to on Page 1.
12
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDC/00
DESIGN AND DRAWING
CALCULTAIONS
3.2 Calculations
All designs shall be prepared in SI units (see HSEC/QSP/DDU/00). Calculations may either be done on
paper or using excel spread sheet. If done on paper, the left margin should be kept clear for filing.
All calculations must be written up in such a way that they can be followed easily by another
engineer, even after the original designer has left the office. This means that they should be neat
and tidy, in logical order, and complete with explanations, cross-references etc.
The following design calculation procedures are recommended:
(a) All sources of data should be referenced and, where appropriate, attached to the calculations.
(b) Where methods are taken from manuals or text books, these should be referenced (including
the relevant editions and page numbers).
(c) All assumptions should be labelled as assumptions and clearly stated.
(d) Sketches should be incorporated into the design calculations so that the checker has a clear
idea of the designer's intentions.
(e) Do not use more significant figures than justified. The results of the calculations should reflect
the level of data available, the assumptions and the methods used. Where appropriate, an
indication of the level of accuracy should be given.
f) Results of calculations should be summarized and presented in a simple format. Where
possible, graphs should be prepared, since they provide a simple and visual check of results.
Before handing their work over for checking, designers should check their own calculations and
assemble them into logical order, omitting superseded or irrelevant material.
The calculations shall be tied into a folder on which is written the job name; work area and
calculation file number. The calculation file number shall comprise:
a) Job name
b) /CF/ (for calculation file)
c) Number related to drawing numbering system (see HSEC/QSP/DDPOD/00)
For example, the calculation file for Ankhu Khola Hydropower Project penstock is numbered
AKHP/CF/305, and could be sub-divided into AKHP/CF/305 C, M and R if necessary.
13
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDU/00
DESIGN AND DRAWING Prepared Approved
PREFERRED SI UNITS
Quantity Preferred units Conversions
Length mm, m, km
Area mm2, m2, ha, km2 1 ha = 10,000 m2
Volume ml, l, m3 1 m3 = 1000 litres

1 litre= 1000 ml
Mass g, kg, t 1 t = 1000 kg
Force N, kN 1 kg f = 9.80 N
1 t f = 9.80 kN
Unit weight kN/m3 1 kN/m3 = 102 kg f/m3 = 1 N/dm3
Pressure, stress N/mm2 (= MPa) 1 N/mm2 = 10.2 kg f/cm2

loading kN/m2 (= kPa) 1 m head = 9.80 kN/m2
1 bar = 100 kN/m2
Time s (second), h (hour), d (day)

Velocity m/s
Flow l/s, m3/s, Ml/d 1 m3/s = 86.4 Ml/d
Power kW, MW
Energy kWh, GWh 1 GWh = 106 kWh
14
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDPOD/00
DESIGN AND DRAWINGS Prepared Approved
PLANNING OF DRAWINGS
3.3 Planning of drawings
3.3.1 General
Planning of drawing shall be done by design engineers before actual drafting starts. Care should be
taken to reduce ambiguity in reading drawings by any third party. Drawings shall be complete, users
friendly, simple and clear. All the references relevant to design and drawings are stored in
Engineering/Admin/Formats/Drafting.
3.3.2 Drafting
In general, topographical, general layout, general arrangement drawings of major structures shall be
drawn in 1 meter. All other minor structures and details shall be drawn as 1 unit of AUTOCAD
equivalent to 1 mm.
3.3.3 Drawing titles

Drawing titles should be kept as brief as possible, and should be consistent within a set of drawings.
Where two drawings are required to be read together as part of a set, the designations "SHEET 1 OF
2", "SHEET 2 OF 2" may be written in smaller letters under the main title (which must be identical in
this case), with supplementary information if required. For example:
SETTLING BASIN BASE SLAB
RC DETAILS
SHEET 1 OF 2, BOTTOM MAT
SETTLING BASIN BASE SLAB

RC DETAILS
SHEET 2 OF 2, TOP MAT
If multiple sets are used, it is always wise to provide an inset diagram with that individual set hatched
along with the total component drawing.
3.3.4 Drawing numbers

Drawing numbers should be coded in 14 letters, but 1 letter will be added for any revision made as in
Table 3-1.
Table 3-1: Drawing number format
1 2 3 4 5 / 7 8 / 10 11 12 13 14 15
5 letters for 2 letters for 2 letters for 1 letter 2 letters for 1 letter for
project code indicating stage component for type sequential revision code
of the drawing code code number (if any)
a) Project Code:
Start of numbering will always be the project name initials. The code will be five project
name initials. For an example: For Ankhu Khola Hydropower Project, it will be coded as
ANKHP.
15
b) Stage Code:
2 letter stage codesindicate the stage/phases of the project. It is shown inTable 3-3.
c) Component Code:
Individual components of the proposed project will be numbered by two digit (00-99)
categorisedas in Table 3-2:
Table 3-2 : Drawing Component Code s

DCN Descriptions DCN Descriptions
00 General 50 Powerhouse/Tailrace/Switchyard
Project Location, District Map & Catchment Area Powerhouse (Below ground level)
Project Layout, Plan and Profiles Powerhouse Electrical Drawing
Land Requirement Powerhouse superstructure
10 Headworks Tailrace outlet structure
Spillway Service Building
Intake Switchgear Building, Control Room
Reservoir Switchyard Foundation/structure
Desander Switchyard Electrical Drawing
Rock fill Dam Earthing System
Adit 1 Electrical System
Diversion works 60 Transmission System
Wing walls Foundation Civil Drawing
Buildings Electrical and mechanical Drawing
20 Headrace LV & HV TL for construction power
Headrace tunnel Transmission/Distribution Line
Headrace pipe Substation
Headrace Canal Foundation Drawing
30 Forebay/Surge Tank Electrical Drawing
Forebay Tank 70 Infrastructure
Reservoir Road/Bridge
Surge Tank Water Supply
Spillway Sewage System
Buildings 80 Camp Area
40 Penstock Staff building
Penstock Pipe Office Building/Workshop
Power Tunnel 90 Miscellaneous
Adit
Valve Chamber
Bifurcation, Anchor Blocks
Discharge Measuring Chamber
16
d) Type Code:
1 letter is indicated to identify the type of drawing as inTable 3-4 :
Table 3-3 : Drawing Stage Code

CODE DEFINITION
00 Desk Study
01 Feasibility Study
02 Topographic, cadastral&geological maps
03 Tender Drawings
04 Construction Drawings
05 As built Drawings
Table 3-4 : Drawing Type Code
CODE DEFINITION
A General
C Civil
E Electrical
G Geological mapping
H Health/Sanitary
L Cadastral (legal) survey
M Mechanical
N Environment
R Reinforcement
T Topographical survey map
e) Drawing No:
Two digits from 00 to 99 is indicated for drawing sequential number.
f) Revision Code:
One letter is coded for any type of revision in the drawing as in Table 3-5:
Table 3-5: Drawing Revision Code
CODE DEFINITION
1 letter digit (1-9 ) For In-house revision made
1 letter alphabet (A-Z) For Client revision made
17
For example:
ANKHP/03/50E01-2Ankhu/Tender/Powerhouse Electrical 1st drawing – 2ndin house revision
NYSHP/01/20C03-A Nyasim/Feasibility/Headworks Civil 3rd drawing – 1st Client revision
UMCHP/04/20R05 Upper Mai C/Construction/H/W Reinforcement 5th drawing-no revision
With this type of system it is necessary to have clear instructions about the filing of drawings, so that
they can be retrieved without difficulty, and to provide documentation to all users so that the system
can be understood.
3.3.5 Digital Documentation

Drawings shall be prepared in AutoCAD. AutoCAD version shall be used for HSEC documentation
purposes. Drawing files shall be saved in AutoCAD 2000 for transmittal purposes.
Drawings shall be saved so that the file names resemble the drawing titles as in Table 3-6.
Table 3-6 : Digital Documentation
Drawing Titles Saved File name
ANKHP/03/50E01-3 ANKHP-03-50E01-3.dwg
NYSHP/01/20C03-A NYSHP-01-20C03-A.dwg
UMCHP/04/20R05 UMCHP-04-20R05.dwg
Additional description of drawings after the drawing shall be stored in the drawing description
properties box through save as or properties.
3.3.6 Scales
Recommended scales are 1:1, 1:2, 1:5 and multiples of 10 of these. However, 1:25 etc may be used,
but never on the same drawing as 1:20. The use of too many different scales on the same drawing
should be avoided. Where more than one scale is used, the scale should be written below each title:
all scales used should be noted in the title block and shown as a graphic scale on the drawing, to
avoid confusion when drawings are photo-reduced.
3.3.7 Layout of drawings

The following general rules apply where possible:
a) The plan is placed in the bottom left hand corner, with the main section or elevation in
projection above it, and end elevations and additional cross sections placed in projection to
the right of the main section.
b) Further sections or minor details occupy the area to the right of the main plan. Location
plans and tables are placed in the top right hand corner.
c) The space above the title block is reserved for notes and the amendment
d) Additional notes and graphical scale bars, if required, may be placed to the left of the title
block.
e) The direction of flow of water should be from left to right or from top to bottom. River and
canal cross sections should always be drawn looking downstream. The direction of flow
should always be marked.
f) Location plans should be oriented with north towards the top. Always show a north point.
18
Figure 3-1 : Drawing layout
Left Bank Right Bank NORTH, KEY

PLAN
Water flow TABLES

Water flow Additional Section
(Elevation)
MAIN SECTION/ELEVATION LEGEND/NOTES
Text
GRAPHICAL
Text SCALE
Water flow
DETAILS/MINOR REVISIONS
SECTIONS
Water flow
TITLE BOX
PLAN
ADD NOTES
3.3.8 Sections and details

Where possible, sections should be positioned in the direction of viewing, in projection, and should
be drawn at the same scale as the view on which they are marked.
Sections are designated 'A-A', 'B-B' etc, and are arranged in alphabetical sequence on the drawings;
do not use 'I - I' nor '0-0'. Where two or more drawings form part of a set, the section letters should
be in continuous alphabetical sequence.
Where miscellaneous details are shown on a drawing each detail should have at least two views
which should be grouped together under their main heading. Each group should be placed in an
orderly sequence within the drawing. Details may be numbered '1', '2' etc.
3.3.9 Blocks
The use of blocks is recommended for common objects. Some blocks are listed in Sample Drawing.
Figure 3-2 : Sample Drawing in AutoCAD
19
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDDS/00
DRAWING STANDARDS
3.4 Drawing standards

3.5 Material
Use of computer software to be used and normal paper could be used to produce drawings.
Computer back up of calculation is extremely important and should be kept as an archive.
3.5.1 Drawing sizes

Standard drawings are A1 size, with 10 mm margins. Drawings to be bound into reports should be A3
or A4 size, and incorporate a 25 mm filing margin on the left-hand side. A2 size drawings should only
be used where specified by the client.
Table 3-7 : Paper Size
NAME OF PAPER SIZE DRAWINGS MARGINS
Uses
FORMAT (mm) AREA (mm) LEFT RIGHT ABOVE BELOW
DIN A0 1189 X 841
DIN A1 841 X 594 791 X 574 40 10 10 10 Standard
DIN A2 594 X 420
20 5 5 5 A3 reports
DIN A3 420X 297 395 X 287
5 5 20 5 A4 reports
DIN A4 297 X 210 272 X 200 20 5 5 5 Reports
3.5.2 Title blocks

Title blocks should be a standard for every drawing sheet. A standard title block is shown here for
illustrative purpose.
Figure 3-3: Title Block
20
DRAWING STANDARDS
3.5.3 LAYER DEFINITION

The layer definition depends on the subject of drawing. The list below shows a layer definition for
CIVIL DRAWINGS. In other kind of drawings, e.g. containing geological, topographical, mechanical,
electrical information a.s.o., it may necessary to replace or add several layer names. The use of the
layer names shall be guided by the following layer definition.
The idea of layer names is to group layers that belong together by using a prefix (e.g. TOPO-.. REINF-
… or ROAD-)
User- defined layer names are allowed to isolate a specific element or structure (e.g. ACCESS ROAD,
EMBANKMENT, JOINT, SHOTCRETE, ANCHOR, EXISTINGS-BUILDING a.s.o.) but shall be reduced to a
useful number and shall anyway be fixed in a list by the design engineer.
Basically all layers are thawn or turned on when the drawing is being plotted. Layers that shall not be
printed in the drawing shall have a hint on that in their name (e.g. “HATCH-OUT-OFF”: outline of
hatch symbol, layer usually turned off). This is important because a third person usually does not
know which layer has to be turned on or off.
As far as possible use the BY LAYER property.
Table 3-8 : CIVIL DRAWINGS

NO.OF
LAYER NAME DESCRIPTION COLOR LINE TYPE
COLOR
0 (zero) General layer 7 White Cont.

AXIS Axis 4 Cyan Center2
BOULDER Boulder 8 Gray Cont.
BREAK LINE Symbol of Continue 4 Cyan Cont.
BRIDGE Bridge 1 Red Cont.
CONCRETE_BL Blinding Concrete 1 Red Cont.
CO- ORDINATE Co- Ordinate 4 Cyan Cont.
CONTOUR MAJOR Major Contour 4 Cyan Cont.
CONTOUR MINOR Minor Contour 8 Gray Cont.
CONTOUR VALUE Contour Value 4 Cyan Cont.
DEFPOINTS General layer 7 White Cont.
DIM Dimensions and Elevations 1 Red Cont.
DRAIN Drain 1 Red Cont.
EL Electrical equipment 3 Green Cont.
EXCAVATION LINE Excavation Line 1 Red Cont.
FINISHED LVL. Finished Level 3 Green Cont.
FRAME Borders of drawing 3 Green Cont.
21
DRAWING STANDARDS
Information according to the frame, that

FRAME OUTER 4 Cyan Cont.
can turned off before final plot
GEOLOGY Geological information 3 Green Cont.
GEOLOGY Geological hatch 32 Brown Cont.
GEOLOGY Hatch boundary 210 Magenta Dash
GRID Grid Lines 8 D Grey Cont.
HATCH General Layer for hatches 4 Cyan Cont.
KHOSI Kholsi 140 Blue Cont.
LOGO HSL Logo 7 White Cont.
LEGEND Legend 1 Red Cont.
O.G.L. Original Ground Profile 4 Cyan Originan_GL
Excavated
ROCK LINE_EX Excavated Rock Line 4 Cyan
Rock
ROCK LINE_NA Natural Rock Line 4 Cyan Natural Rock
REINFORCEMENT Reinforcement Bar 255 White Cont.
RIVER River 140 Blue Cont.
ROAD Roads (if no separate drawing) 1 Red Cont.
SCALE BAR Scale bar 4 Cyan Cont.
SECTION LINE SECTION LINE 4 Cyan Dashdot
SLOPE Symbols of slopes 1 Cyan Cont.
SLOPE-UPPER-EDGE Upper edge of a slope 4 Cyan Hsl Slope
STRUCTURE_BG Background Structure (Elevation View) 1 Red Cont.
STRUCTURE_SL Steel structure 10 Red Cont.
STRUCTURE PLAN Structures at plan 3 Green Cont.
STRUCTURE SECTION Structures at section 7 White Cont.
TABLE Table 4 Cyan Cont.
TEXT General text 1 Red Cont.
TEXT TITLE TITLE TEXT 7 White Cont.
TITLE BLOCK Title block 3 Green Cont.
10-meter contour line in topographical
TOPO-CL10 3 Green Cont.
plans
22
DRAWING STANDARDS
TOPO-CL5 5-meter contour line in topographical plans 4 Cyan Cont.

TOPO-CL-TEXT Text of contour lines 4 Cyan Cont.
TOPO-TEXT Text in topographical plans 1 Red Cont.
VIEWPORT View port (in paper mode, layer always
6 Magenta Cont.
turned off when plotted)
WL Water Level 160 Blue Cont.
3.5.3.1 ADDITIONAL LAYER DEFINITION

3.5.3.1.1 Drawings Containing Topography
Table 3-9 : Prefix: TOPO
NO. OF
LAYER NAME DESCRIPTION COLOR LINE TYPE
COLOR
TOPO-BUILDING Existing Building 1 Red Cont.

TOPO-CUTTING-LINE- Polyline to which contour lines are 2 Yellow Cont.
OFF trimmed
TOPO-CL-TEXT Text of contour lines 1 Red Cont.
TOPO-CL 1 1-m-contour line 8 Grey Cont.
TOPO-CL5 5-m-contour line 4 Cyan Cont.
TOPO-CL10 10-m-contour line 3 Grey Cont.
TOPO-GRIG 8 D. Grey Cont.
TOPO-GRIG-TEXT Coordinates 4 Cyan Cont.
TOPO-HATCH 4 Cyan Cont.
TOPO-RIVER 1 Red Cont.
TOPO-ROAD 1 Red Cont.
TOPO-SYMBOL Symbols 4 Cyan Cont.
TOPO-SYMBOL-TEXT Symbols related text 4 Cyan Cont.
TOPO-TEXT Text in general 1 Red Cont.
23
DRAWING STANDARDS
3.5.4 Plot Style Table

Specific plot style table has been developed for A1 and A3 plotting of the drawings.
The available plot style tables are:
For A1 paper =>HSEC-A1.ctb
For A3 paper =>HSEC-A3.ctb
Default line specifications used in these plot styles are presented in Table 3-10 : Plot StyleTable 3-10.
Table 3-10 : Plot Style
NO. OF
COLOR WIDTH WIDTH OCCURRANCE
COLOR
A1 A3
1 Red 0.25 0.20
2 Yellow 0.30 0.25
3 Green 0.35 0.30
4 Cyan 0.20 0.18
5 Blue 0.70 0.50
6 Magenta 1.40 1.40
7 White/ Black 0.50 0.35
8 Dark Grey 0.15 0.10
9 Bright Grey 0.15 0.10
10 Red 0.30 0.25
20 Red 0.30 0.25 “Hydro-solutions Symbol” in title block
160 Blue 0.15 0.13 “Hydro-solutions Symbol” in title block
44 Brown 0.18 0.18 “Hydro-solutions Symbol “ in title block
250 Black 0.25 0.25 “Hydro-solutions Symbol “ in title block
140 Blue 0.25 0.20 For River, Kholsi
32 Brown 0.20 0.18 For Geology hatch
210 Magenta 0.25 0.25 For Geology hatch boundary (not printable)
130 Blue 0.18 0.15
255 White 0.60 0.50 For Reinforcement
24
DRAWING STANDARDS
3.5.5 Dimensioning
All dimensions should be in metres or millimetres, depending on the type of drawing: the relevant
unit is defined in the notes. All dimensions in metres should be shown to at least one decimal place:
the number of decimal places on a drawing should be consistent, according to the required accuracy.
All levels should be in metres. The level datum (i.e sea level, local or arbitrary) should be stated in the
notes. Levels should be quoted to a consistent number of decimal places which reflects the expected
accuracy.
Table 3-11 : Dimension Style

STYLE NAME A3 PAPER A1 PAPER
Overall Scale Annotative Annotative
Dimension Line / Spacing 1.25 2.50
Dimension Line / color Cyan Cyan
Extension Line / Extension 1.25 2.50
Extension Line / Original Off Set 1.25 2.50
Extension Line / Color Cyan Cyan
Arrowhead / Size 1.25 2.50
Text / Style Simplex-08 Simplex-08
Text / Height 1.25 2.50
Text / Gap 1.25 2.50
Text / Color Red Red
Units / Decimals 0 0
As far as possible, dimensions and levels should be written outside the structure. Sufficient
dimensions to define the structure without ambiguity, but avoid showing too many - they clutter the
drawing shall be shown.
25
DRAWING STANDARDS
3.5.6 Text Style

Text shall be created as far as possible with the MULTILINE EDITOR. This facilitates text wrapping. Text
shall be written to be red from the bottom or the left hand side of a drawing. Exception: Contour
values, chainages and grid co-ordinates. They shall always be written to be red from the lower level
to the upper level.
Section letters shall be placed between the arrowheads, to be readable in its normal orientation
(Whatever the orientation of the section is).
If a drawing or view port has another original scale, adjust the size of letters or numbers following
the list as presented in Table 3-12.
Table 3-12 : Text Styles
STYLE HEIGHT
DESCRIPTION TEXT STYLE LAYER COLOR
NAME A3 A1
Text in general, e.g. 1.25 1.25 2.50
Notes, elevations, SIMPLEX-8 Text Red
2.5
inscriptions, legend
2.5 5.0
Title, main, inscriptions Sec. Title ROMAND SectionText White
Subtitle SIMPLEX-8 SIMPLEX-8 Text Red 1.25 2.5
Dimensions (width
SIMPLEX-8 SIMPLEX-8 Dim By Layer 1.25 2.5
factor 1.0)
3.5.7 Hatch
Hatches shall not be exploded.The outlines of hatch,that shall not be printed on paper, shall be stored in
a separate layers and hidden. Typical set of hatches are presented inTable 3-13.
Table 3-13 : Typical hatch

DESCRIPTION HATCH NAME ANGLE LINE TYPE
Concrete, reinforced AR-CONC 0 Cont.
Concrete, not reinforced AR-CONC 0 Cont.
Soil EARTH 45 Cont.
Backfill AR-SAND 0 Cont.
Brickwork BRICK 0 Cont.
Metal ANSI31 0 Cont.
Gabion HONEY 0 Cont.
Stone Masonry ANSI33 0 Cont.
26
DRAWING STANDARDS
3.5.8 Line Type
The line type is preferably chosen as By Layer. In AutoCAD, by selecting Linetype in Layer Manager
and clicking in Load, the different types of line type can be found. The typical line types and their
application descriptions are presented in Table 3-14.
Table 3-14 : Line Types
WIDTH
LINE TYPE DESCRIPTION
(Approx.)
CONTINUOUS Construction lines in general

HIDDEN Invisible lines beyond section plane
CENTER Axis
PHANTOM Borders, rock lines
DOT Foot trail,
DASHDOT 0.18 Invisible lines in front of section plane
DASHDOT 0.5-0.7 Alignment of section
FENCE For Boundary
DASH
DIVIDE For dividing equally parts
3.5.9 Care of Backup

All data stored in computer shall be backed up at regular intervals in an external hard disk
(preferable daily) and should be placed in the safest places.
27
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDRD/00
RC DETAILING
3.6 RC detailing
3.6.1 General
This section covers only the most common mistakes made in RC detailing. Reference should be made
to the publications listed below when necessary.
3.6.2 References
Reinforced concrete design is to be carried out to British Standards:
BS 8110 (1985) Structural use of concrete
BS 8007 (1987) Design of reinforced concrete structures for retaining aqueous liquids
Reinforced concrete detailing is to be consistent with:
BS 4466 (1987) Specification for bending dimensions and scheduling of
reinforcement for concrete
There are a number of Indian publications giving typical RC details which should be treated with
suspicion. Many details are for mild steel bars with hook anchorages, not generally used with
torsteel.
3.6.3 Design considerations
Bar type Mild steel bars are not readily available in Nepal, so should not be specified. Designs
should normally be based on Grade 415 high yield steel, but Grade 500 may be used
where that is more economical. Bar types should not be mixed at the same site.
Note that these bar strengths are not as given in BS 8110, therefore some
interpolation is necessary.
Concrete grade Minimum grades to be used are:

C15 Blinding and mass concrete
C25 Reinforced concrete
C35 Water retaining structures
Only specify higher grades where required for strength or durability.
Cover As per BS 8110 Section 3.3 according to degree of exposure. Nominal cover for Grade C25
concrete, which is not specified in BS8110, should be not less than the following:
Mild exposure 25 mm
Moderate exposure 40 mm
Severe exposure 50 mm
For foundations using Grade C25 concrete, the nominal cover should be not less than 75 mm when
the concrete is cast against the ground, or less than 50 mm when the concrete is cast against rock or
a layer of blinding concrete.
28
RC DETAILING
Bar spacing Keep to standard spacing, in multiples of 25 mm only

ie 100/125/150/175/200/225/250/300 ..........
Size of members Bear in mind the practical problems of pouring concrete. It is not possible to
make doubly reinforced water retaining walls less than 250 thick. (250 - 2 x
50 - 4 x 12 = 100 approx: just enough for vibrator)
3.6.4 Detailing
Pour sequence Consider how the contractor may cast the structure dividing it into pours
and detail the reinforcement accordingly. There will usually be construction
joints:
• 75 mm above the bottom of a wall or column (kicker)

• at a change in section
• at the underside of a slab
Unsupported reinforcement up to a great height is difficult to deal with and level accurately. It is
better to put a hairpin on the top of a high wall which can be levelled accurately just before the last
pour than to use the vertical reinforcement bent over at the top.
Complexity A large number of bar marks may save money in theory but a
complex arrangement may be difficult to assemble and a costly
mistake may be made.
Congestion Allow plenty of space between bars for concrete or it will be difficult
to assemble the mat and pour concrete. Pay attention to corners,
particularly if there is an acute or oblique angle and at junctions of
walls/slabs. There can be congestion of reinforcement if some bars
are not curtailed.
Bend radius Take into account the bending radius of shear links when considering
the position of main steel.
Water bar At movement joints on slab/wall junctions allowance needs to be
made for reinforcement which may intersect a water bar of 250 mm
width.
3.6.5 Drawings
General Unless details are very simple the reinforcement should be shown on a
separate RC detail drawing not on the general arrangement or
outline drawings.
Layout Plan the drawing before drafting starts, making it easy to understand.
Generally:
• put the plan in the bottom left
• put related views together, ideally in projection
• arrange section and elevation letters sequentially
Organize drawings according to concrete pour so that all information needed at one time is
available on one or two drawings. Do not show shear reinforcement on one drawing and
main reinforcement on another for the same beam or column.
29
RC DETAILING
Notes A standard set of notes is shownonHSEC/F/RCTN/00.Make sure all

relevant things are included and only include the notes on one of a
set of drawings to make it easier for changes.
Lap lengths "Lap length to be according to specification" is not a helpful note
when nothing is written in the specification. Specify minimum lap
length on the drawing.
Dimensions The dimensions of concrete should not be shown but they must be
the same as on the general arrangement drawings.
Sections andelevation
Show viewed from the correct side, eg not from inside the rock
where a wall is cast against rock. Show the full concrete section,
including slab and beam where beams are integral with the slab; but don't show slab
reinforcement on beam sections.
Calling off Follow the standard notation shown onHSEC/F/RCTN/00.Only call
reinforcement off bars once: on plan for slabs; on elevation for walls,
beams and columns.
3.6.6 Bar schedules

Dimensions Measure as shown on Tables 4 and 5 of BS 4466. The length of each bar is rounded to
nearest 25 mm, dimension to 5 mm.
Tolerances Make sure allowance is made in dimensions for tolerances in:
• cutting and bending reinforcement
• Form works erection
Otherwise the reinforcement cage may not fit into the formwork, cover will be reduced or there will
be additional work in cutting and bending steel.
Bar marks Bar marks should be numbered and scheduled sequentially usually starting from 01
for a given set of RC detail drawings. It may be decided to use 01-100 for base
slab, 101 - 200 for walls etc.
The bar mark must be different for bars varying in type, diameter, length or
shape.
Varying lengths Bars of varying length may be given bar marks: 13a, 13b, 13c etc (but not using i or
o). Avoid this for small increments of say 25 mm by using a varying lap length
with a constant length of bar. Keep it simple.
Numbering There should be one set of sequentially numbered sheets for each of set
of sheets RC detail drawings.
Revisions Note that the bar schedule contains a revision letter which is unrelated to any
revision letter on the drawing: the schedule may be revised but without a revision
to the related drawing. The schedule revision letter should be written in the right
hand margin of the schedule in line with the bar marks affected.
30
HSEC ENGINEERING PROCEDURES Doc. HSEC/F/RCTN/00
RC DETAILING: TYPICAL NOTES
LEGEND
24 T 12 - 17 - 200 T1
T1 top outer layer N1 near outer layer
Bar layer: T2 top second layer N2 near second layer
B2 bottom second layer F2 far second layer
B1 bottom outer layer F1 far outer layer
Bar spacing (mm)
Bar mark
Bar diameter (mm)
Bar type: X= Grade 500 high yield type 2 deformed
T= Grade 415 high yield type 2 deformed
Number of bars
NOTES
A. Reinforced concrete to be Grade C30 (20 mm max. aggregate).
B. Nominal cover to reinforcement:
a. Foundations 75 mm
b. Above ground 40 mm
C. Minimum lap to reinforcement to be:
a. T12 500 mm
b. T16 620 mm
D. Kicker height to be 75 mm.
E. This drawing to be read in conjunction with:
a. Bar Bending Schedule
b. General arrangement drawings
c. RC detail drawings
31
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDAI/00
APPROVAL AND ISSUE
3.7 Approval and issue

The stages of drawing production are included in the design process outlined on
HSEC/QSP/DADDP/00, and include checks by the draftsman, the designer and an independent
checker before approval. The Title block must be initialled by individual checker after the corrections
have been made.
3.7.1 Designer's check

A final copy must be provided to the designer by draftsman after he is done with the corrections for a
final correction within the team. Any errors or omissions must be marked on the check print, which
should be signed and dated (above the title block) by the designer and returned for corrections.
3.7.2 Independent check

After the designer has checked the drafting, the drawing or set of drawings must be checked by an
independent engineer (the design Team Leader, or someone assigned by the Team Leader), who
should ensure that:
• the relevant calculations have been checked
• the drawings are consistent with the calculations
• drawing standards and symbols are consistent with this chapter
• cross-references to other drawings are correct
• all necessary information is shown
Any errors or omissions should be marked on the check print, which should be signed and dated by
the checker (above the title block) and returned for corrections.
3.7.3 Recommendation for approval

The Project Engineer/Team Leader shall check that the drawing meets the job requirements, then
sign in the title block his recommendation for approval. Note, that this stage is only a brief overview,
and does not relieve the designer and checker of responsibility for their work.
3.7.4 Approval
Drawings may only be approved by the Technical Director; furthermore, the design, check and
approval of a drawing must be by three different people.
A clean print should be made for approval purposes, unless the check print had very few corrections
made on it. This print should be submitted for approval along with the relevant Design Control Form
and calculations. The approval engineer will mark any required changes on the approval print, then
sign and date it. After all required changes have been made, he will sign the tracing.
If no significant changes are required, the approval print may subsequently be used as the office
copy.
32
APPROVAL AND ISSUE
3.7.5 Drawing issue

Drawings may not be issued prior to any approval.
Normal procedure is that after drawing approval prints shall be made as follows:
Record copy 1 print
Office copy 1 print
Resident engineer 1 or more prints, as agreed
Contractor 1 or more prints, as agreed
Others As necessary
A drawing register is maintained for each job in which is recorded the drawing number, title, revision
letter, revision date (approval date), to whom issued, when, and number of copies to each
recipient.This information is also recorded on the Document Transmittal Form which is to be sent
with all drawings. (See HSEC/F/DTF/00).
The record copy is to be filed for the duration of the job, as a record of every issue of every drawing
sent out of the office.
The office copy is retained as a working copy of the current issue of each drawing. Any amendments
required shall be marked onto the office copy.
Prints for the contractor should normally be issued via the resident engineer, who will first stamp the
'Issued for construction' near the title block. (Note: The stamping needs to be done right above the
title block of the drawings.)
3.7.6 Preliminary prints

On occasion a drawing needs to be issued for discussion or planning purposes before full approval.
In this case 'P1' should be written in the revision box of the title block, and the amendment box
should describe the nature of the issue, eg 'Preliminary, for land purchase only'. A preliminary issue
must still be approved in the amendment box, however. If amendments are required before full
approval they should be designated 'P2', 'P3' etc.
33
APPROVAL AND ISSUE
3.7.7 Revisions
No amendment shall be made to an approved drawing or to an approved revised issue without first
changing the revision letter.
Except where a preliminary issue has been made, the first issue of a drawing will be blank in the
revision box. Subsequent issues should be given revision letters 'A', 'B' etc, and the amendment box
must be completed with a brief description of the change. Even if no changes are made to a
preliminary issue, it should still be given revision letter 'A' and 'Approved drawing' should be entered
in the amendment box before approval.
Following approval of a revised drawing, the old office copy should be discarded and replaced with a
current print.
3.7.7.1 Revision Index

The revision index of a drawing shows that there are amendments compared to the previous state of
the drawing ( lower index). All necessary information shall be given in the revision box of the title
block.
In Detailed Design the following fixing shall be used:
Drawings not yet handed over to Drawings already handed over to

the client/contractor/supplier the client/contractor/supplier
Remarks Internal design phase
Revision index Number Letter
Example 1, 2, 3 … A, B, C….
Example for electronic file UMCHP/04/20C01-2 UMCHP/04/20C01A
Note:
 Mind the hyphen(-) left of the number in the internal drawing file name.
34
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDRS/00
REGISTRATION AND STORAGE
3.8 Registration and storage
3.8.1 Drawing registration

Overall drawing registry system will be handled by Team leader or his/her designee as per the criteria’s
outlined in the following sections. If the drafting is done by the team itself, the responsibility to properly
register, number and store the drawings falls under the whole team. However, if the drafting
responsibility is delegated to the drafting team in-house, the appropriate team leader must delegate the
proper instructions as per this manual to the drafting team for proper recording and filing system for
individual drawings. It will be a normal practice for a team to register and store the drawings developed
under them in their separate cabinet, but the individual sheet, its title and its number must be
registered under the format file “Drawing Reference Record” HSEC/F/DRR/00. A copy of the format will
be available for easy access in the central server after the server is set up.
Drawing records register
The Team Leader and his/her designee or Drafting-in-Charge shall maintain a drawing records register
for each job. It is advised that the records register is updated regularly with each additional drawing
made. A standard drawing records register is available as HSEC/F/DRR/00. The drawing numbers
assigned should be as per HSEC/QSP/DDPOD/00 under section 3.3.3.
Document transmittal form
Drawings being sent out of the office must have been approved and must be accompanied by a
Document Transmittal Form (Form HSEC/F/DTF/00) signed by the Team Leader. Individual team is
responsible to keep a record of this form in a separate file. The drawing record register must be
updated under the remarks section after a drawing document is sent out from the office accompanied
by a copy of the document transmittal form (HSEC/F/DTF/00).
Incoming drawings
The date of receipt and register number shall be written on the drawing using the registration stamp
available at the front desk. The format of the stamp is shown here for illustrative purposes
(HSEC/F/IDS/00)
3.8.2 Drawing storage

Drawings are to be stored properly by individual design team in the proper cabinets with proper name
tags labelled on them. The drafting team is responsible to deliver the drawings to the individual project
team in case the drafting team is involved. Please note that it is also a standard practice for a design
team to prepare their own drawings. Any obsolete drawings should be clearly marked suspended and
thrown out for disposal (Burning method of disposal is recommended for obsolete copies of drawings.)
Record copy and office copy should be clearly stamped on each drawing booklet and should be used
accordingly. Incoming drawings which are not given a Hydro Solutions drawing number shall be stored in
box files in the drafting store, in numerical order by the incoming drawing register number. The
Drafting-in-Charge shall label the box file with the job name and incoming drawing registernumbers of
the drawings within. Drawings shall not be removed from the incoming drawings box file, except to
make copies to work with.
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/DDRS/00
REGISTRATION AND STORAGE
3.8.3 Calculations
Calculations shall be written up and tied into numbered folders, as described in HSEC/QSP/DDC/00 section
3.2.These folders shall be stored in numerical order.
The design Team Leader shall maintain a register of the calculation files, listing:
file number
subject
name of designer
date of design
name of checker
date of approval
42
HSEC ENGINEERING PROCEDURES Doc. HSEC/F/DTF/00
DOCUMENTS TRANSMITTAL
FORM
HSEC/D/DTF/00
Date:
Dear XYZ,
Please receive the following Items.
S.N Details Quantity
Sent From Received By
Name: Name:
Designation: Designation:
Date: Date:
Stamp: Stamp:
Signature: Signature:
------------------ -----------------
Prepared by: Approved by:
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/F/IDS/00
INCOMING DRAWING STAMPS
HYDRO SOLUTIONS, KTM.
Incoming No…………………………
Received Date……………………….
Signature……………………………...
Incoming Registration stamp, Available at the front desk.
Name Initial Date

Checked
Recommended
Approved
Issued for construction
HSEC Engg. Consultant Drawing No. Revision
Approval Stamp
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/Q/00
QUANTITIES
3.9 Quantities
On most jobs it will be necessary to calculate construction quantities from the design drawings. This
should be done using Form HSEC/F/BOM/00 (Bill of quantity measurement). This form will illustrate the
material quantity and the costs at one place. Standard practise should be as follows. Material quantities
must be defined for a project under design phase. Projects under construction should reflect the total
costs for the materials as well in the form HSEC/F/BOM/00.
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QSP/Q/00
QUANTITIES
This page is left blank intentionally!
This page is left blank intentionally!!
42
HSEC ENGINEERING PROCEDURES Doc. HSEC/QMS/RI/00
REPORTS Prepared Approved
INTRODUCTION
4 REPORTS
4.1 Introduction
The intention of a report shall always be to convey the required information as simply and clearly as
possible. Often, we being engineers having a technical mind frame, fail to excel in the art of report writing.
This chapter of the Hydro Solutions HSEC ENGINEERING PROCEDURES manual closely resembles the style
of a report that needs to be written and it may be used as a model for report writing and presentation.
The chapter is divided into the following sections:
4.1 Introduction
4.2 Layout
4.2.1 Overall structure
4.2.2 Headings and numbering system
4.3 Writing
4.3.1 Preparing to write
4.3.2 Good English
4.3.3 Spelling and punctuation
4.4.3 Dates
4.4 Illustrations
4.5 Format
4.5.1 Typing
4.5.2 Production
4.6 Review and issue
4.6.1 Checklist
4.6.2 Approval
4.6.3 Issue
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QMS/RL/00
REPORTS LAYOUT Prepared Approved
4.2 Layout
4.2.1 Overall structure

Reports can be short or long. Irrespective of its length, a report must include the following:
 Title, heading or subject
 Introduction
 Main text
 Conclusions and/or recommendations
In addition, longer reports may include the following:
 Title page
 Transmittal letter
 Synopsis (see below)
 Table of contents
 Summary (executive summary)
 Appendices/annexes
 References
Title, heading or subject
A brief title is always good for illustrating the general idea of what report is about. Shorter reports can be
headed with the project name before the report title. A short report may be defined as a report having 10
or less pages as its content. Longer reports should have a title page that includes:
 Client name
 Project name
 Title of report
 Volume number and description, if there is more than one volume
 Date
 Author's name and address (Hydro Solutions with any associated company)
 Approval signature in the second page
Title page illustration will be presented later on in this manual. (HSEC/F/RTP/00)
Transmittal letter
A copy of the letter of transmittal may be bound into the front of the report to identify the main recipient
and give information about the following wherever applicable.
 report distribution
 outline contents of separate volumes, if used
 acknowledgement of help received (alternatively this could be a separate section in the report)
 Hydro Solutions file reference
Table of contents
This should be included in all longer reports, giving the main headings, section numbering and page
numbers. Lists of appendices, tables, figures and drawings normally follow the table of contents: they
should indicate where each illustration can be found in the report.
Summary
A long report should normally include a summary (sometimes called an executive summary) which outlines
the principal features of the report and highlights the conclusions and recommendations. The summary
41
should be one to five pages plus a table of salient features. A reader should be able to get a handle on the
overall presentation through this section of the report.
Introduction
The introduction must include explanation of the aim and scope of the report, the back ground to it and
the methodology used in the report. By thus setting the context in which the report was written, the
introduction gives the reader guidance in how to interpret what he/she reads.
One paragraph of the introduction should state the reason and purpose of the report with absolute clarity.
It should refer to any terms of reference, which should normally be included as an appendix to the main
report.
Main text
The main part of the report should be organized logically under a series of chapter and section headings.
These chapters should contain all the information, ideas, factors, arguments and deductions relevant to
the subject. Facts should stand out and conclusions should be drawn on the same basis. Please avoid any
opinions.
Conclusions and recommendations

Conclusions may have been spread throughout the report, but should be brought together in a final
section or chapter which summarizes the arguments and deductions. No new information should be put
into the conclusions. Make sure that there are no ambiguous postulations in the conclusions chapter.
Recommendations will be governed by the purpose of a report, but whenever a recommendation is

included, they must be backed up logically based on engineering findings of the study. The reader must be
persuaded that the recommendations are technically and economically feasible, acceptable, and better
than the alternatives
Appendices and annexes

Appendices may be used in the shorter reports. For longer reports, annexes are the best way to go. These
words tend to be used interchangeably, although their meaning is slightly different. An appendix is used to
remove data from the main text which would otherwise interrupt the reader from the main line of
thought. An annex is a self-standing report, usually written by a specialist, which is summarized in the
main report. (An annex may contain one or more appendices).
References
Referred texts from peer reviewed journals, books and other publications must be referenced accordingly
at the end of the report. The following paragraph outlines the way to present the reference books,
journals or any other publications.
Within the text, references are identified by author and date of publication, eg WECS/DHM (1990), whilst
the list of references should be arranged alphabetically by author in the following style:
WECS/DHM. 1990. Methodologies for estimating hydrologic characteristics of unguaged locations in Nepal
(2 volumes). HMGN Ministry of Water Resources, Water and Energy Commission Secretariat and
Department of Hydrology and Meteorology. July 1990.
Sometimes it may be appropriate to expand the list of references to include relevant publications which
have not been directly referred to in the text. In this case the same style is used, but it should be called a
Bibliography, not a list of references.
42
It is always better to hang the second line of reference by about half an inch from the original indent. (As
shown above) In case of peer reviewed journals and books, starting the reference line with the author
names ( Abbreviated), the date of publication, title of book or the journal and then the reference of
publisher always looks good in a report.
4.2.2 Headings and numbering system

The text should be divided into chapters, sections and sub-sections, each of which is given both a heading
and number. Headings should be as brief as possible.
The decimal system of section numbering should be used, as in this chapter of the Hydro Solutions Office
Manual. A maximum of three tiers should be used eg:
Chapter 4. REPORTS
Section 4.2 Layout
Sub-section 4.2.2 Headings and numbering system
For short reports, a two tier system will be enough:

Section 2. Layout
Sub-section 2.2 Headings and numbering system
Minor headings should not be numbered. Items in lists are normally marked by a bullet ( ), but may be
identified by letters (a,b,c, etc.). Further sub-divisions, if required, can be made using Roman numerals (i,
ii, iii, etc).
Appendices should be lettered 'A', 'B', 'C', etc. Material within the appendix may be divided into sections
using a numbering system as above, except that the chapter number is replaced by the appendix letter.
43
HSEC ENGINEERING PROCEDURES Doc. HSEC/F/RTP/00
REPORTS TITLE PAGE Prepared Approved
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/F/RSP/00
REPORTS SIGNATURE PAGE Prepared Approved
ANKHU KHOLA HYDROPOWER PROJECT

(42.9 MW)
Dhading District, Nepal
FEASIBILITY STUDY REPORT

(Updated)
Prepared by: Approved by:
-------------------------- ---------------------------------
Mr. Sanjay K. Sharma, Mr. Pushpa Chitrakar
Project Manager General Manager
Ankhu Khola Hydropower Project Hydro Solutions Engg. Consultant Pvt. Ltd.
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QMS/RW/00
REPORT WRITING Prepared Approved
4.3 Writing
4.3.1 Preparing to write

There are three essential steps before starting to write the report text:
a) The author should be aware of the purpose of the report and to whom it is intended to.
b) A draft table of content with proper headings and sub headings should be outlined first.
c) Jot down the information you have under each heading or sub-heading, and then
assemble it into logical order before starting to write that section.
4.3.2 Good English
General
We, being engineers often lack with linguistic skills in the English language for a better writing. That’s why
it is always wise to express clear, concise and short sentences in a report.
Technical report writing obeys the rules of good English. Other basic rules are: be accurate; be brief; be
clear. Cut out any word, sentence or paragraph which is not necessary, or the reader is liable to become
bored and not bother with the report. Avoid generalizations and quote actual examples of figures where
possible.
Paragraphs
A paragraph consists of one or more sentences (usually more) all bearing on the same aspect of the
subject. A common mistake is to write a number of short paragraphs each containing only one or two
sentences. This makes the report jerky. A properly constructed paragraph should deal with only one
topic: each sentence in the paragraph should be relevant to that topic and to the preceding sentence.
Sentences
The rules of sentence construction are:
a) Keep sentences reasonably short.
b) Be prepared to substitute a full stop for 'and'.
c) Arrange sentences so that each leads naturally and logically to the next. It is unnecessary to tie
each sentence to its neighbour by connecting links such as 'since', 'because', 'therefore' or
'consequently'. If the order of sentences is right the reader will himself see the connection of
ideas.
d) Never forget that a sentence must have a verb.
e) Use direct construction without too many dependent or relative clauses.
f) Never start to write a sentence until you can 'hear' the end and it sounds well when read aloud.
Language
a) Write simple English, using short and familiar words in preference to long or obscure ones.
b) Avoid using too many adjectives. Only use words such as 'essential', 'vital' and ‘unique’ in their
true meaning.
41
c) Do not use technical jargon which may not be understood by readers. Explain technical
expressions if necessary.
d) Do not use slang.
e) Do not use cliches or platitudes.
4.3.3 Spelling and punctuation

4.3.3.1 Spelling
Use the WORD spellchecker English (UK) dictionary to check the spelling of English words. Be consistent in
the spelling of technical terms not found in the dictionary. For example, 'power house', 'power-house' or
'powerhouse' would all be acceptable, but one form should be used throughout a report. The preferred
form for commonly used compound terms is a single un-hyphenated word, eg crossflow, flashboard,
powerhouse, stoplog.
Check that Nepali names are transliterated consistently throughout the report. Eg do not mix 'Tama Koshi'
with 'Tama Kosi' or 'Tamakoshi'.
4.3.3.2 Abbreviations
Abbreviations should be avoided wherever possible. It is always wise to list out the abbreviations used
after the table of contents page in case many abbreviations are used. Care should be taken that by using
abbreviations, the reader may get confused on what is being expressed in that particular report when a lot
of abbreviations are used Except for comm.
-+on abbreviations (such as ie, eg) all abbreviations should be written out in full the first time they are used
in a report. Avoid using etcetera: it is better to be specific.
Abbreviations of a single word are normally written in lower case letters, and may be given a full stop to
make it clear that an abbreviation is being used. Abbreviations formed from the initial letters of a phrase
or names are normally written in capitals without the use of full stops (but there are exceptions, eg cif for
cost, insurance freight: refer to the dictionary). Abbreviations for units are always written in lower case
letters without full stops, except that:
i) tera- (1012, T), giga- (109, G) and mega- (106, M) are written in capitals to distinguish them from
the abbreviations for tonne, gram and milli- or metre;
ii) units named after a person are abbreviated with a capital letter, eg newton (N), volt (V), watt
(W).
Examples are given below:
max maximum
no. number
nos numbers
cif cost, insurance, freight
NPV net present value
kg kilogram
kW kilowatt
MW megawatt
GWh gigawatt-hour
42
4.3.3.3 Capitals
Capital letters should only be used at the start of a sentence and for:
 proper nouns, eg Mr Gadtaula, Kathmandu, Ankhu Khola, Monday, April
 some abbreviations (see above)
 words which have been given a defined meaning in a contract document, eg Works, Contract,
Site
 titles, eg the Ministry of Water Resources, the Baramchi Hydropower Project, Chief District
Officer
 headings (first letter of first word only)
 specific references, eg Figure 2, Table 5.3, Appendix A, Adit 3, Alternative B
4.3.3.4 Numbers
In text, numbers involving more than four figures before the decimal point should be written in blocks of
three, for ease of reading. In columns, all figures should be in blocks of three, so that figures line up. Use
Decimal tabs to ensure figures are aligned. Decimal fractions are indicated by the use of a point, and
thousands are separated by a comma. If a number is less than one, always add a zero before the decimal
point.
Always leave a space between a number and its associated unit, except for degrees. No space is required
between degrees, minutes and seconds when writing angles, latitude and longitude.
Examples of numbers:
In text In text In columns
0.000567 1358 km2 203

0.0004 1.7 m 1,567
1.23 12.7% 4,783
1234 45° C 27
10,500 27°38'05"N 15,345
5600,000 Rs 50,000 6,432
65,400,000 Rs 5.50/kWh 28,357
Do not write 'approximately' or 'about' followed by a number which implies an accurate measurement.
For example, a distance might be 'approximately 25 km' or '25.7 km' (implying that it has been measured
to the nearest 0.1 km) but it cannot be 'approximately 25.7 km'.
4.3.4 Dates
All reports must use the Western calendar. If it is necessary or helpful to use the Bikram Sambat calendar,
this should be in addition to the Western calendar.
43
HSEC ENGINEERING PROCEDURES Doc. HSEC/QMS/RI/00
REPORTS ILLUSTRATION Prepared Approved
4.4 Illustrations
Illustrations such as tables, graphs and figures should be used wherever they clarify the text or save on
words. They must be chosen to serve their intended purpose, eg statistics are normally best given in a
table, but a graph would be more appropriate for showing a trend. Every illustration must be titled,
numbered and referred to in the text.
Tables are the most common illustration. They are ideally suited to presenting numerical data, but can
also be used to present other information, as for example Table 6.1 below:
Table 4.1 Use of illustrations
Type of illustration Suitability Typical size Maximum size
Table Numerical data A4 A3

Other information
Graphs
Figures Key plans A4 A3
Maps
Diagrams
Drawings Maps A2, A1, or photo-reduced A1
Engineering plans to A3
Photographs Many purposes < A4 A4
Graphs, key plans, maps, diagrams and sketches are all referred to as figures, and given a figure number.
They should be no larger than A3 size, for binding into the report, but A4 size is preferable.
Tables and figures should normally appear in the report at the place where they are referred to, or at the
end of that chapter. In short reports they should be numbered sequentially straight through the report
(Table 1, Table 2, etc) but for longer reports it is helpful to use a two-part numbering system, with the first
part being the chapter number or appendix letter: this means that a change in one chapter does not affect
the numbering in subsequent chapters.
Drawings should be avoided if possible, because they are too large to bind into a report. A limited number
of drawings may be folded into pockets at the back of the report, however. If more than three or four
drawings are required, it is better to photo-reduce them to A3 size so that they can be bound into the
report.
As it is said, pictures speak a thousand words on its own. Good photographs are much more effective than
words for describing a site, and should be used wherever appropriate. They are normally included in the
text at the `appropriate point, but large numbers of photographs should be put into an appendix.
41
HSEC ENGINEERING PROCEDURES Doc. HSEC/QMS/RF/00
REPORT FORMAT Prepared Approved
4.5 Format
4.5.1 Typing
Lettering should be Aerial 11 scalable font, varied as given in Table 6.2 below.
Table 4.2 Lettering
Application Font size Style
CHAPTER HEADINGS 16 Bold capitals

Section headings 14 Bold
Sub-headings 13 Bold
Table headings 11 Bold
Minor headings 12 Italic
Normal text 11 Normal
Footers 6 Italic, Capitals
Page numbers 11 Normal
Margins and indents

Margins should be set according to Table 6.3 below. Text and tables should be indented 1.5 cm to leave a
clear space for section numbering. Further indents of 0.5 or 1.0 cm should be used for lists, quotations,
etc.
Bullets marking items in a list should normally be indented 1.0 cm, with the text indented a further 0.5 cm.
Where items in a list are identified by letters or Roman numerals, however, no indent is required for the
identifying letter, but the text should be indented 1.0 cm.
Table 4.3 Margins
Margin Setting (Inch)
Top 1.05
Bottom 0.8
Left 1.1
Right 0.9
41
REPORT FORMAT Prepared Approved
Letter spacing
Use a double space after the full stop at the end of each sentence. Use a triple space between a table
number and title. Refer to Section 4.3.3 for instructions on typing numbers. There should be no space
between a punctuation mark and the word it follows.
Text should be fully (left and right) justified.]
Line spacing and pages

Single line spacing (autospacing, which is 6 lines per inch) should be used generally. Double line spacing
(i.e one blank line) should be used:
under headings
between paragraphs
above and below tables
above and below lists like this
Triple line spacing (i.e. two blank lines) should be used between the bottom of one section and the next
section heading.
Try to avoid having less than two lines of a paragraph at the top or bottom of a page, eg by using the
'widows and orphans' feature. Never put a heading at the bottom of a page.
Every chapter and appendix should start on a new page.
Footers and page numbers
At the bottom of every page should be:
a) a left footer giving the computer file name for the document, using the MS Word 'Insert
field' feature;
b) a right footer giving the date of printing, using the MS Word 'insert field' feature;
c) a page number, printed centrally.
Page numbers for the preliminary pages (table of contents, etc) should be lower case Roman numerals (i,
ii, iii, iv etc). The main part of the report should normally be numbered straight through (1, 2, 3 etc), but
the summary and appendix pages may be given a prefix letter (S1, S2; A1, A2; B1, B2 etc). Two-part page
numbers may be used for long reports, with the first part being the chapter number, eg the third page of
Chapter 8 would be Page 8-3.
4.5.2 Production
Short reports (less than five pages) are normally photocopied within the office onto one side of the paper,
so that they can be read after being inserted into a file.
Longer reports normally include a title page and are sent out for photocopying and binding. Bound reports
should :
a) use single side of the paper
b) include coloured (preferably blue) interleave pages to enable readers to find the start of
each chapter or appendix;
c) Have a plastic cover on both sides of the report.
d) Use a high quality photo print paper for the cover page which includes a picture;
e) Use spiral bindings with a black spiral.
42
REPORT REVIEW AND ISSUE Prepared Approved
4.6 Review and issue
4.6.1 Checklist
Every report should be reviewed by the author, preferably at least 24 hours after first writing. At this
review stage the writer should put himself into the position of the reader and check the following:
 Is the purpose and content of the report clear?
 Does the report satisfy the requirements set out in the terms of reference or
elsewhere?
 Is there enough background information for the intended readers? Is it clear and easy for
them to understand?
 Is everything in the report relevant to its purpose?
 Is the report structure logical?
 Have illustrations and appendices been used appropriately? Are they referred to in the text?
 Are the conclusions and recommendations clearly reasoned from the information given in
the report?
 Is spelling and punctuation correct?
 Does the table of contents exactly match the headings and sub-headings used? Are all cross-
references correct?
 Is the report written in good English? Is it accurate, brief and clear?

4.6.2 Approval
Every report which will be sent out of the Hydro Solutions office must be checked and approved before
issue. For this reason every report except the ones that will be submitted to DOED (Department of
Electricity Development) should be signed as per HSEC/F/RSP/00.
4.6.3 Issue
No report may be issued before approval. After approval the report should be printed in sufficient copies
for the client, internal use and others as appropriate. For internal use there should always be at least one
office copy, for day to day use within the project team, and one record copy which is filed. A library copy
should also be made for final reports or other significant reports.
Reports should be issued with a letter of transmittal, see Section HSEC/F/DTF/00. This will be signed by the
Team Leader and approved by the Technical Director. The Team Leader must ensure that the collation of
all reports has been checked before despatch.
41
REPORT REVIEW AND ISSUE Prepared Approved
This page is left blank intentionally!
This page is left blank intentionally!!
42
43

HSEC Engg Procedures Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HSEC Engg Procedures Manual

Uploaded by

Copyright:

Available Formats

ENGINEERING Doc.

1.3 Ongoing work 9

1.4 Job completion 10

3.1 Design process 12

3.3 Planning of drawings 15

3.4 Drawing standards 20

3.6 Approval and issue 32

3.7 Registration and storage 41

4.6 Review and issue 41

1.1.1 Proposal format

1.1.1.3 Scope of Work

1.1.1.7 Terms and Conditions

For cost plus proposals the following clause should be included.

XXX Hydropower Project

Name Initials Date

Hydro Solutions P. Ltd

Terms and Conditions

1.2.3 Project planning

1.3 Ongoing work

1.3.1 Quality control

1.3.2 Progress and cost monitoring

1.4 Job completion

the client's requirements have been satisfied (refer to Terms of Reference,

as-built drawings have been made where relevant

all accounts have been finalized

all books and references have been returned to the library

2.1.2 Field records

2.1.3 After the field trip

Quantity Preferred units Conversions

Area mm2, m2, ha, km2 1 ha = 10,000 m2

Volume ml, l, m3 1 m3 = 1000 litres

Mass g, kg, t 1 t = 1000 kg

Unit weight kN/m3 1 kN/m3 = 102 kg f/m3 = 1 N/dm3

Pressure, stress N/mm2 (= MPa) 1 N/mm2 = 10.2 kg f/cm2

Time s (second), h (hour), d (day)

3.3 Planning of drawings

3.3.3 Drawing titles

SETTLING BASIN BASE SLAB

3.3.4 Drawing numbers

Table 3-2 : Drawing Component Code s

Table 3-3 : Drawing Stage Code

Table 3-4 : Drawing Type Code

1 letter digit (1-9 ) For In-house revision made

1 letter alphabet (A-Z) For Client revision made

3.3.5 Digital Documentation

Table 3-6 : Digital Documentation

Drawing Titles Saved File name

3.3.7 Layout of drawings

Figure 3-1 : Drawing layout

Left Bank Right Bank NORTH, KEY

Water flow TABLES

3.3.8 Sections and details

Figure 3-2 : Sample Drawing in AutoCAD

3.4 Drawing standards

3.5.1 Drawing sizes

3.5.2 Title blocks

3.5.3 LAYER DEFINITION

Table 3-8 : CIVIL DRAWINGS

0 (zero) General layer 7 White Cont.

Information according to the frame, that

TOPO-CL5 5-meter contour line in topographical plans 4 Cyan Cont.

WL Water Level 160 Blue Cont.