Explorer

Content

Project Management using Technology Readiness Levels (TRLs)

In order for TRLs to be of use to a project it is essential that they become embedded as a Technology Management tool within daily project management. They shouldn’t be seen as an isolated ‘obstacle’ to achieving an objective such as Initial Gate or Main Gate. TRLs add value when projects use them routinely.

Timely TRL assessments allow the project to focus effort on areas of immature technology, reducing the overall project risk, and monitor the project progress. Communications is essential - discussions between stakeholders to defining and then agreeing the TRLs can add value to their use.

Using TRLs for hardware and software projects

TRLs are applicable to both the hardware and software that forms a component of a project.

A project that is software intensive or entirely software based should make use of specific processes used for the development and maturation of software. The customisation of the software TRLs will show the increasing maturity of programming languages and real-time operation as the TRL increases.

Using TRLs for PFI and PPP projects

All projects, including Private Finance Initiative (PFI) and Public Private Partnership (PPP) projects are required to undertake an assessment of technology readiness.

Although the lead project may be contracting out the service provision to an external company, the ultimate risk of non availability of technology to MOD lies with the project team. The team needs confidence in the ability of the contractor to manage technical risk and their contractor should use TRLs - appropriately customised and agreed - to provide this.

Using TRLs on international collaborative programmes

When undertaking a TRL assessment on international collaborative programmes, additional time needs to be allowed for discussion with overseas agencies and companies on how the MOD applies TRLs and to gain access to the information required for evidence of TRL achievement.

It may also be necessary to agree a joint approach to applying them.

Using TRLs with incremental acquisition and technology insertion

Project teams using incremental acquisition or technology insertion need to ensure that the TRL assessment clearly shows which technologies are in each delivery package to avoid a low top level TRL that is not representative of the in-service maturity.

The assessment should take into account the integration aspects for the receiving platform or system that could have an effect on the overall TRL.

Using Modeling and Simulation to mature technology

The use of a model or simulation can be a cost effective and timely way of increasing the TRL of a system.

Modeling and simulation can be used throughout the life of a programme to test system concepts, model potential solutions and reduce the amount of physical test and evaluation required to prove a system. The re-use of models and simulations, within and between programmes, can further reduce the overheads associated with traditional trials.

Modeling and simulation should be used in conjunction with real operational trials and scenarios, when required, particularly when evidence of achievement of a higher TRL is needed.

Using TRLs with COTS and MOTS Projects

For Commercial off the Shelf (COTS) or Military off the Shelf (MOTS) equipment, it is essential that the difference between existing operational requirements and the actual operating environment in which the capability will be used is understood when assessing the TRL.

Differences may include the operating hours and additional certifications.

Change History

1 September 2010: Minor amendments made.