30 August 2017

Use of PEARL in
Assessing TRL

Ashish Kumar Bhuriya, Scientist E

Basic Foundation Course in TM 2, 28-30 August 2017

 30 August 2017

DATE
Decision support tool
Framework for evaluation of different technologies
Availability in India and technical human resources
Depending upon number of factors
Factors were leading to lack of clarity on actual readiness level
Feature: Identification of technology gaps

PEARL attempts to simplify the process of DATE

 30 August 2017

Objectives of PEARL
PEARL is a highly modified version of DATE

To assess difficulty of development

To make realistic assessment of time of development

To provide expected levels of subsystem readiness level

during execution and completion of subsystem
Quantitative analysis technological content and the stage
of readiness of its subsystem
 30 August 2017

Objectives of PEARL
PEARL does not mark a project as non-feasible

Restrict to analysis of the readiness level of the technological

content
Support to take low module level readiness systems

Enhance the indigenisation of defence systems at component

level
Essential for technological growth of the country
To provide expected levels of MRL/PRI during project
progression and at completion
 30 August 2017

Terminology in PEARL
Technology Readiness Level (TRL)
Applicable for a subsystem, module, process, etc.
TRL of any project depends upon the stages of projects

Project Readiness Level

Single index to represent the readiness level of whole
project at any stage
Minimum value of TRL of various subsystems at any point
in time
 30 August 2017

PRI for a Programme

A Programme involves many projects and each project is
independent of each other e.g. NBC Defence Programme has
12 MM projects, 24 S&T projects.
Each system/product is an independent system with no
correlation to each other
Assigning a single PRI to the programme may not be justified
In such cases each individual project/systems should be
independently assigned a PRI based on TRL of its sub systems
 30 August 2017

Steps in PEARL
Draw block diagram subsystem/module

Identify the TRL of each subsystem

Go down to sub-subsystem level if TRL is <5 for that

particular module

Evolve PRI as lowest value of subsystem TRL

PRI = minimum of TRL of subsystem

Draw the anticipated roadmap of PRI with project timeline

 30 August 2017

DRDO TRL (Technology Readiness Level)

TRL Definition
Level
1 Abinitio research to start

2 Basic technologies assessed & report compiled

3 Similar module made earlier & proved at Lab level

4 Similar module made earlier and proved at actual environment

5 Finalization of Design of required module /Vetting by experts

6 Required module manufactured as prototype/ preliminary test in

lab/test rig
7 Required module proved as prototype in test bed & qualified

8 Required module integrated in system and proved in test bed

9 Required module integrated & proved in actual environment

10 Module in production/ COTS

 30 August 2017

TRL 1: Abinitio Research to Start

Level: Basic start of R&D first time by DRDO

Examples: Blue green lasers for underwater communication

(Only known agency Russia)

Supporting documents
Study of possible research partners
Published research papers
 30 August 2017

TRL 2: Basic Technologies Assessed and Reported

Level: Completion of initial feasibility study

Literature study of world wide trends

Possible development options based on functional and environmental specifications
Identification of final development model
How to test and validate the system
Possible technical risks

Examples: First Aerostat, first torpedo, etc.

Supporting documents
Feasibility study report
 30 August 2017

TRL 3: Similar Subsystem/Module made Earlier and

Proved at Lab Level
Level: Earlier work carried out and proved in the lab

Gives credit to the work

Required area of development
Assumed enhancement in the required specifications
Top-up not to exceed 50 percent of main functional specification, major changes
in design philosophy
If exceeds, technical justification to be provided
Details of Additional testing and validation

Examples: Development of a 120 W TWT and tested at laboratory level against a

requirement of 200 W TWT

Supporting documents
Report on similar system developed with test details of specification
Feasibility report outlining proposed approach to meet enhanced
specification for design, manufacturing and testing
 30 August 2017

TRL 4: Similar Subsystem/Module made Earlier and

Proved at Actual Environment
Level: Earlier work carried out in the lab and proved in the actual
environment
Gives credit to the work
Required area of development
Assumed enhancement in the required specifications
Top-up not to exceed 50 percent of main functional specification, major changes
in design philosophy
If exceeds, technical justification to be provided
Details of Additional testing and validation

Examples: Development of a 120 W TWT and proved in actual

environment, i.e. radar as against a requirement of 200 W
TWT to be integrated in a radar
Supporting documents
Report on similar system developed with test details of specification
Feasibility report outlining proposed approach to meet enhanced
specification for design, manufacturing and testing
 30 August 2017

TRL 5: Finalization of Design of Required Module/Vetting

by Experts
Level: Third level of ab-initio development project
Passed through level 1 and level 2 requirements
Preliminary design completed
Modeling and simulation studies carried out
Initial assessment of realisation and testing methodology completed

Examples: Completion of preliminary design of a subsystem with

simulation and modeling studies to support the design

Supporting documents
Design document cleared by Expert committee
 30 August 2017

TRL 6: Required Module made as Prototype with

Preliminary Test in Lab/Test Bed
Level: Assumes that the module has already passed through preliminary design
stage and the first prototype has been built

At this stage, limited tests of prototype be carried out in lab/test rig

To demonstrate basic functional parameters
Preliminary QA/inspection requirements should be formulated
Test schedules are frozen and put for approval

Examples: First engineering model of SDR tested in simulator and

functional parameters

Supporting documents
Manufacturing document of first prototype
QA plan + test report of completed tests
 30 August 2017

TRL 7: Required Module proved as Prototype in Test bed

& Qualified
Level: Implies that the module has been built as a prototype and tested in test
bed for all functional requirements as per approved ATP/QT plan

The test should be carried out/vetted by QA reps

Testing should be documented
Ideally CDR should be carried out at this stage

Examples: First prototype of SDR qualified through cycle of tests as per ATP

Supporting documents
Test report of system in test bed
Design specifications Vs specification achieved + approved CDR report (optional)
 30 August 2017

TRL 8: Required Module integrated in System and Proved

in Test Bed
Level: Integration of prototype module

System has equipped with this prototype module

Tested for its functional performance in a test rig

Examples: Qualified gearbox integrated with engine and tested on the

Engine test rig

Supporting documents
Test report of sub systems integrated in system
Desired specification Vs achieved specification
 30 August 2017

TRL 9: Required Module Integrated & Proved in Actual

Environment

Level: Implies that the prototype module is integrated within the system and
tested for its functional performance in the actual environment

Examples: Gearbox integrated with engine and mounted/tested in flight in

the aircraft

Supporting documents
Test report of system integrated in actual environment
Design specifications Vs specification achieved
 30 August 2017

TRL 10: Module in Production/COTS

Level: Implies that the module is readily available as a system in ready production
or as Bought Out Item (BOI) commercially

Supporting documents
Plan of procurement with cost, source, procurement /delivery schedule
 30 August 2017

Role of PEARL at Different Stages

At Project Sanction
Shelf evaluation tool for PD

Evaluation guidelines for sanctioning authority

PBS in term of TRL, at least two levels of PBS

Present level of expertise/capability and quantum of work involved

in
the project execution

After subsystem TRL determination, collection of necessary

documents as supporting evidence

Followed by a self-analysis and time estimation by the project team

of the level that will be reached at each subsequent year right up to
the estimated PDC
 30 August 2017

Role of PEARL at Different Stages

During Project Execution

TRL tracks progress and support development

Basic research (TRL 1) to actual system development (TRL 10)
TRL assessment before PDR and CDR processes and during Executive
Board meeting annually
EB should ensure target maturity (TRL 5 toward TRL 10) before start
of manufacturing, testing and operational readiness review
Project Director is responsible for presenting the current status of TRL
in various meetings and ensure planned transition to every higher
stages
Apart from PRC, PMRC and EB Reviews, Cost Reviews and Technical
Reviews in DMC
Use of these review processes may overlap with assessment of TRL
and gives awareness
 30 August 2017

Role of PEARL at Different Stages

At Project Closure

Certificate of achieved project scope

Analysing module/subsystem at the completion of project activities

Assessment of TRL at the project closure

At final TRL, Verifying Authority issue certificate no and will be part of

Technical Closure Report

If not achieving planned stage of completion as per TRL, justification

and explanation is required
 30 August 2017

Verifying Authority

Technology Council of lab first level of verification of the proposed

PRI by checking out the required documentation

PRC will carry out thorough vetting of the proposed TRLs/PRI

PRC will recommend the final PRI and category of project

For projects within DGs power, Director PM of concerned DG will

ensure presentation/assessment of TRL/PRI during PRC and will
obtain certificate from PRC Chairman

Projects above DGs power, this task will be performed by DP&C

during PRC
 30 August 2017

Example Module A

Module A has achieved MRL 10 that has been

incorporated fully into a larger system. It has been proven
to work smoothly during earlier developmental phases of
the project and is considered operational and mature
enough to be incorporated into a system.

In this example, if one considers an improvement in the

module, the new idea would be considered to be at TRL 4. It
would again make its way through the development
process, while the original module remains at MRL 10
 30 August 2017

Example Module B

Module B has achieved MRL 6 and developments are

going in the prototype to integrate the
technology/subsystem. A parallel work which is being done
to improve the product specifications (Mk II of the system)
is also going on due to technological advancements

Due to simultaneous development in Mk II of the

product, even though the first technology has attained MRL
6 during the due course of time, its actual TRL will be lower
(say TRL 4) at start of new development cycle
 30 August 2017

Case Study: Development of SONAR

25
 30 August 2017
MRL/PRI of Sonar System
Sub-Sub- Sub- PRC 12 months / 24 months / After 36 After 48
System (SSS) System (sanction) PDR CDR months months
(SS) SSS SS SSS SS SSS SS SSS SS SSS SS
Power 2 4 3 5 5 6 10
amplifier Transmitt
2 6 10
Projector er 2 3 5 7 10
Array
Hydrophone 2 4 3 5 5 6 10
Array
Receiver 2 6 10
Front End 2 3 5 7 10
Electronics
Mechanical 2 3 3 5 5 7 10
U/W
Systems 2 7 10
Enclosure
Cable 2 4 5 7 10
Mechanical 2 4 4 5 5 7 10
Systems Deployme
2 7 10
Electrical nt System 2 4 5 8 10
Systems
Hardware Signal 2 4 4 5 5 7 10
2 7 10
Software Processor 2 4 5 7 10
Hardware Display 2 5 5 5 5 8 10
Software and 2 2 5 5 8 8 10 10
Control
PRI 2 3 5 6 10
 30 August 2017

Case Study - SONAR

Project will move from PRI of 2 to PRI of 10 in 4

years

Realistic projections? Possibly requires 5 years

Should it be taken in TD or MM project

PRC to decide if PDC is realistic; PRC to

recommend parallel path of development for
subsystem of TRC 2
Thanks