Explorer

• What is Through Life Management?
• Is Through Life Management Mandatory?
• How TLM relates to TLCM?
• What is a Through Life Management Plan?
• Framework for a TLMP
  • Section 1 - Mission and Objectives
  •     Section 1 - Further Advice
  • Section 2 - Stakeholders
  •     Section 2 - Further Advice
  • Section 3 - Strategies
  •     Section 3 - Further Advice
  • Section 4 - Plans and Processes
  •     Section 4 - Further Advice
  • Section 5 - Resources
  •     Section 5 - Further Advice
  • Section 6 - Evaluation of Success
  •     Section 6 - Further Advice
• Producing the TLMP – Process Overview
• Who Should use a TLMP
• The TLMP across an Acquisition Lifecycle
  • The TLMP in the Concept Phase
  • The TLMP in the Assessment Phase
  • The TLMP in the Demonstration and Manufacture Phase
  • The TLMP in the In-Service Phase
  • The TLMP in the Disposal Phase
• The TLMP and Other Acquisition Processes
• Measuring TLM Maturity
• Applying the TLMP Process
  • System and Platform TLMPs
  • TLMPs for In-Service Projects
  • TLMPs in Cluster IPTs
  • TLMPs for Small Projects
    • TLMP Templates for small projects
  • TLM Support Tools
  • Electronic and Web-based TLMPs
• TLM Frequently Asked Questions
  • TLM General
  • Producing a TLMP
  • Stakeholder Issues
  • Costing the TLMP
• TLM Common Terms
• Contacts

Content

Through Life Management Plans (TLMPs) in Cluster IPTs

When to use a single TLMP for managing multiple projects?

This approach can be considered when an IPT is managing a large number of small, low value projects which can be logically grouped under a single ‘umbrella’ TLMP. It is most suitable where the projects are similar in terms of equipment type, common customers/users and common procurement and support arrangements. It has been successfully applied to in-service ‘commodity’ IPTs who manage large inventories or many discrete low value projects.

Where projects exceed a ‘critical mass’ in respect of cost, complexity and risk then a separate, full TLMP is likely to be more appropriate.

There are examples of Cat D projects that have needed TLMPs of similar length and detail to those in much higher value projects.

For example, a Cat D training system in the Assessment phase that has complex interfaces with a platform and equipments managed by other IPTs.

There are other examples of TLMPs that are a single page - for example an in-service munition that is approaching its OSD.

The selected approach should be set out in the IPTs TLM strategy and be determined in consultation with customers and other key stakeholders.

What are the options for multiple project TLMPs?

There are two basic models which can be deployed.

The IPT might choose to have a single high level TLMP (as in Model 1 in the diagram below) for the IPT as a whole, or multiple TLMPs covering different equipment or commodity groupings that are managed by different sub-teams (as in Model 2). In the latter case a common format for the higher level TLMPs should be adopted.

Model 1: Single TLMP for multiple small projects

Model 2: Single TLMP for multiple small projects

In both models the main body of the TLMP is structured around the six sections of the TLMP Framework and expresses the overall business objectives and common stakeholders, strategies and processes of the team.

Each individual ‘project’ has a separate Annex in the TLMP. For low value or legacy projects the Annexes might be no more than one page of the key information, laid out in a common format.

Desk officers own and maintain the annexes for their projects. Section heads, the Business Manager or a nominated TLMP manager should own and maintain the main body of the TLMP and co-ordinate the incorporation of the Annexes.

Writing a TLMP for a new project then becomes a simple matter of raising a new Annex and linking it into the main TLMP.

What are the advantages of using single TLMPs for multiple projects?

• It facilitates strategic business planning, programme coherency and control across many small projects.
• It avoids having to write many detailed TLMPs for many small projects, It maximises the multiple use of common and pre-existing data.
• It can be valuable for flushing out and resolving mismatched assumptions between the IPT and stakeholders, particularly in old legacy projects where assumptions may not have been formally visible until the TLMP was written.
• TLMP information is communicated to senior management and stakeholders in a common and consistent format.
• It facilitates the development of common processes and plans within the IPT and builds them into all project TLMPs.

What are the issues with using single TLMPs for multiple projects?

• It is difficult to apply unless the projects fall into easy, logical groupings with common characteristics.
• It is best suited to groupings of In-service projects in steady state. Less suitable where projects are running across earlier CADMID stages.
• It can be resource intensive to set up in the first place. And maintaining good configuration control is crucial – this requires efficient processes. But the long term business benefits should far outweigh this overhead once the TLMP is operational.
• There is a danger of taking a ‘checklist’ approach to the TLMP – simply plugging historical information into the blanks and not applying forward, Through Life thinking to the project.

Change History

Change History