KOMBOLCHA POLYTECHNIC COLLEGE

Department Of Metal Manufacturing

 MODULE TITLE: - Develop and Document

Specifications and Procedures.
 NOMINAL DURATION = 90 hours.
By Muluneh N 1
Learning Outcomes (Objectives):-
At the end of the module the Trainees will be
able to:
LO1. Identify requirements
LO2. Prepare specifications
LO3. Prepare technical procedures

By Muluneh N 2
 Unit One :-

1. LO1. Identify requirements

By Muluneh N 3
Defin.
 The document specification defines the
document templates, data sources, and the
output formats to be used to create a report.
 Before documents can be generated,
templates and data sources must be
accessible from the location of the document
specification.

By Muluneh N 4
 .
 The term requirement has been in use in the software
engineering community since at least the 1960s
 Requirements can be said to relate to two main fields:
 Product requirements prescribe properties of a system
or product.
 Process requirements prescribe activities to be
performed by the developing organization.
 For instance, process requirements could specify the
methodologies that must be followed, and constraints that
the organization must obey.

By Muluneh N 5
 .
 Product and process requirements are closely linked;
 a product requirement could be said to specify the
automation required to support a process requirement
 while a process requirement could be said to specify the
activities required to support a product requirement.
 For example, a maximum development cost requirement
(a process requirement) may be imposed to help achieve
a maximum sales price requirement (a product
requirement);

By Muluneh N 6
.
A requirement that the product be
maintainable (a product requirement) often is
addressed by imposing requirements to
follow particular development styles
 (e.g., object-oriented programming), style-
guides, or a review/inspection process
(process requirements).

By Muluneh N 7
 1.1 Identifying and assembling Information required
for technical specifications and procedures

 Specification
 A detailed description of the dimensions, construction,
workmanship, materials etc., of work done or to be
done, prepared by an architect, engineer etc."
 a detailed description of the design and materials used
to make something. "one of the telescope's mirrors had
been manufactured to incorrect specifications"
 A specification is a requirement which is clearly stated,
for example about the necessary features in the design
of something.

By Muluneh N 8
.
 Specifications can be divided into three types:
1. functional,
2. technical, and
3. administrative.
 Functional specifications are the most
general and cover all aspects of the product.
 Technical specifications cover the features
and performance of the product.

By Muluneh N 9
 .
 Specification (often abbreviated as spec) may refer to
an explicit set of requirements to be satisfied by a
material, design, product, or service.
 Should a material, product, or service fail to meet one or
more of the applicable specifications, it may be referred
to as being out of specification; the abbreviation OOS
may also be used.
 In casual usage, underspec or overspec are used when
something is worse or better than specified (compare
overengineering), though in general (such as for sizes)
there is only a notion of "in spec" or "out of spec", not
"better" or "worse".
 A specification is a type ofBy technical
Muluneh N
standard. 10
 .

1. A technical specification may be developed by any of various

kinds of organizations, both public and private. Example
organization types include
 A corporation, a consortium (a small group of corporations),
 A trade association (an industry-wide group of corporations),

 A national government (including its military, regulatory

agencies, and
 National laboratories and institutes),
By Muluneh N 11
.
 a professional association (society),
 a purpose-made standards organization such as ISO, or
 vendor-neutral developed generic requirements.

It is common for one organization to refer to (reference, call

out, cite) the standards of another.
Voluntary standards may become mandatory if adopted by a
government or business contract.

By Muluneh N 12
 .
 A Design or Product Specification describes the
features of the solutions for the Requirement
Specification.
 Sometimes the term specification is here used in
connection with a data sheet (or spec sheet). This may be
confusing.
 A data sheet describes the technical characteristics of an
item or product as designed and/or produced.
 It can be published by a manufacturer to help people
choose products or to help use the products.
 A data sheet is not a technical specification as described
in this article. By Muluneh N 13
 2. Establishing and confirming Specifications and
procedures requirements and formats where necessary

For Example :-
A Welding Procedure Specification (WPS) is a formal
written document describing welding procedures, which
provides direction to the welder or welding operators for
making sound and quality production welds as per the code
requirements .
The purpose of the document is to guide welders to the
accepted procedures so that repeatable and trusted
welding techniques are used.
 A WPS is developed for each material alloy and for each
welding type used. Specific codes and/or engineering
societies are often the driving force behind the
development of a company'sByWPS.Muluneh N 14
. Product Specifications
 Perform Benchmarking
 Establish target specifications
 Finalize specifications

By Muluneh N 15
Benchmarking
 The continuous process of measuring
products against the competitors or those
recognized as industry leaders.
 Step 1: Make a list of design issues

example – coffee mill

 Identify design issues: price, grind time,
fineness of grind, noise level, size

By Muluneh N 16
 Step 2: Make a list of competitive products
example: coffee mill
 Krups, Braun, Cuisinar, Bosch, ….
Step 3: Conduct an information search
Gather as much information about the product as
possible (functions they perform and targeted market)
 Sources: Internet, Trade Mag., Consumer
Reports Mag., Thomas Register of Comp., Moody’s
Industry Review, National Bureau of Standards,
Patents.

By Muluneh N 17
 Step 4: Teardown the competitor’s
product
 select competitive products that are
leaders on some aspect, disassemble
and make a list of all components.

By Muluneh N 18
Teardown method – Subtract and
Operate Procedure (SOP
 Disassemble (subtract) one component of the
assembly or subassembly
 Operate the product, if possible, through its
full range.
 Analyze and document the effect.
 SOP determines the functionality and/or
redundancies in an assembly.

By Muluneh N 19
 Step 5: Compare competitive products
Summarize the comparison by
component function and /or by
customer needs importance.
 Step 6: Establish best-in-class competitor
For each function, determine the
highest performance solution. Also,
determine the least expensive solution.
Step 7: Manufacturing and Assembly cost
Analysis. Coffee mill example
By Muluneh N 20
Step 7: Manufacturing and Assembly cost
Analysis. Coffee mill example
 Generally speaking, benchmarking can be effective
for understanding the market.
 It can identify key innovations and technologies.
 It will not uncover new innovations being developed
by competition., provides lagging information.
 Do not benchmark all competitive products, stay
away from loser products.
 If a company is a clear market leader,
benchmarking may not offer much insight.
 Benchmarking requires wisdom and judgment.

By Muluneh N 21
Quality Function Deployment,
QFD
 QFD is a methodology for defining the
customer’s desires in the customer’s own
voice, prioritizing these desires, translating
them into engineering requirements, and
establishing targets for meeting the
requirements.
 QFD was developed in 1972 at Mitsubishi,
introduced into US by the Xerox Corp. and
has been adopted by a number of industries,
automobile, electronics,….
By Muluneh N 22
QFD
 Identifying the Customer(s)
1 Goal: Determine who will use the product
 Determining Customer Requirements
2 Goal: Develop a complete list of all
requirements
 Determining Relative Importance of the
Requirements
3. Goal: Evaluate importance of each
requirements
By Muluneh N 23
QFD
 Competition Benchmarking
4 Goal: Determine how the customer perceives the
 competition’s ability to meet the requirements
 Translating Customer Requirements into
 Measurable Engineering Requirements
5. Goal: Develop set of engineering requirements (design
 specifications) that are measurable
 Setting Engineering Targets for the Design
6. Goal: Determine target values for each engineering
 requirements

By Muluneh N 24
And
 Goal :- “provide excellent customer service.
 Objective: “reduce customer wait time to one
minute

By Muluneh N 25
 Unit -2

LO2. Prepare specifications

By Muluneh N 26
.
The specifications define the required
characteristics of the supplies including:
The quality levels
Environmental performance
Design for all requirements (including
accessibility for disabled people)
The levels and procedures of conformity
assessment
Fitness for use
By Muluneh N 27
.
 Safety or dimensions, including, for supplies,
the sales name and user instructions, and, for
all contracts, terminology, symbols, testing
and test methods, packaging, marking and
labelling, production procedures and
methods.
 The purpose of the specifications is to give
instructions and guidance to contractors at
the tendering stage about the nature of the
tender they will need to submit and to serve
as the contractor's mandate during project
implementation. By Muluneh N 28
.
 The Technical Specifications will be included in
the tender dossier and will become an annex of
the eventual contract awarded as a result of the
tender.
• All information or documents must be held
in confidence and used only for the purposes of
preparing the Technical Specifications and not
disclosed to any third party unless that person
has also signed a Declaration of Objectivity and
Confidentiality
•
By Muluneh N 29
.
 All working documents must be shredded
• All contributions to preparing Technical
Specifications must be objective and must
fully respect the principles of fair competition
and impartiality, in particular by avoiding
terms or conditions favouring any one
product, manufacturer or service provider.

By Muluneh N 30
 OVER-SPECIFICATION
1.Unnecessarily high specification
There is a temptation to specify items to a very high level,
offering complex functionality which may not be necessary for
the beneficiary and which they are unlikely to use.
2.Redundant specification
Another fault is where part of the technical
requirement is redundant.
3. Unnecessary items
All the items in the Technical Specifications should contribute
to meeting the overall purpose of the procurement. Items that do
not contribute to achieving the purpose should not be included.
By Muluneh N 31
 Unit Three
LO3. Prepare technical procedures

By Muluneh N 32
definition
 Technical procedures systematically describe
a series of steps for the operation,
maintenance, or testing of systems or
components. They are widely used as a
method for ensuring consistency, reducing
human error, and improving the quality of the
end-product.

By Muluneh N 33
The technical procedures shall
include:
 A clear definition of the scope of the
procedure.
 A technical description of the theoretical (or
implicit) principles on which the procedure is
based on.
 The main steps to be followed and the
sequence of tasks to be performed.
 The format to report the achieved results

By Muluneh N 34
.
 Here are some of the common steps that
you can follow:
1) Conduct research. All technical
documentation begins with conducting
research. ...
2) Create a plan. ...
3) Design a structure. ...
4) Add content. ...
5) Proofread and edit.
By Muluneh N 35
Thanks
So Much
By Muluneh N 36