The Acquisition Handbook

More documents

Recommendations

Info

The Requirement SetConceptually, the set of individual user and system requirements are in the form illustrated in thefollowing figure, noting that each individual system requirement is underpinned by one or morelinked user requirements, and that each individual user requirement will be satisfied by one ormore linked system requirements.Key:Statement of Mission Needs"SingleUser RequirementKey User RequirementSystem RequirementKey System RequirementThe Anatomy of the Requirement Set"Statement of Mission NeedsUser RequirementsNote: ‘Many to Many’ linksexist between atomised userand system requirementsSystem RequirementsSystem DesignSmall Project PointSmart RequirementsSmall projects need to follow the same URD and SRD process as large projects,although the length of the documents and databases involved will beconsiderably less.10
TLMPs:• demonstrate that projectsThrough Life Management PlanThe Through-Life Management Plan (TLMP)To achieve Smart Acquisition it is vital that there is an integrated through life approach tomanaging acquisition. This starts as soon as the ECC has identified the capability gap, andcontinues up to the point of final disposal.TLMP AimTo plan how to take a project through its life, across the CADMID cycle,meeting Customer needs and providing visibility to all stakeholders ofthe through life management planning process.# have a clear customer focus# have been ‘whole life’ planned# have been ‘whole life’ costed# are realistic•enable stakeholders to inform and visualise the projectrecord commitments madeensure completeness, robustness and relevanceA TLMP is maintained and refined as the project progresses, improving in accuracy at eachstage, thereby increasing confidence in the IPT’s time, cost and performance targets. Mostimportantly it states the objectives, assumptions and resources that comprise the through lifeplanning process, and should inform all project-related decisions. A TLMP is not an end in itself,but a means to an end.The TLMP guidance is as much an underpinning concept as a detailed document structure.Each TLMP will have common features but the final solution may differ, depending on the natureof the project. A TLMP has a product focus, so IPTs that manage more than one product shouldhave a TLMP appropriate to each one.The TLMP may be likened to a route map taking the project through its lifecycle — a route thatis driven by outputs and decisions, that draws out inter-dependencies between different parts ofthe project, and with other projects. Essentially, it is an articulation by the IPT Leader (and eachproject manager in an IPT that manages more than one project) to their customers and keystakeholders of how they will manage their project through its life — their response to the taskset in their CSA.11
Page 1: The Acquisition HandbookEdition 4 -
Page 4 and 5: ContentsWhat is this handbook for?
Page 6 and 7: The aim of Smart AcquisitionWhat is
Page 8 and 9: The Acquisition CycleWhat are the m
Page 10 and 11: Smart RequirementsSmart Requirement
Page 12 and 13: Smart Requirementsupgrade, and prog
Page 16 and 17: Through Life Management Plan (TLMP)
Page 18 and 19: Whole Life Costs and Cost Of Owners
Page 20 and 21: ApprovalsEquipment projects are div
Page 22 and 23: Acceptance and ISDendorse. Thereaft
Page 24 and 25: Measures and Targets and Indicators
Page 26 and 27: Public/Private PartnershipPublic/Pr
Page 28 and 29: Team Working with IndustryPFI will
Page 30 and 31: Team Working with IndustryMOD beyon
Page 32 and 33: Business Tools for AcquisitionIPT/P
Page 34: The Customers and the IPT• Requir
Page 37 and 38: Who is in the IPT?(“dotted lines
Page 39 and 40: Core, Associate and Attached IPT Me
Page 41 and 42: The Acquisition Stream (AS)The AS w
Page 43 and 44: Acquisition Competence Framework (A
Page 45 and 46: Performance ManagementSmall Project
Page 47 and 48: Acquisition Training CellAcquisitio
Page 49 and 50: Electronic VersionThis handbook is
Page 51 and 52: Jargon BusterAssociate IPT MemberAn
Page 53 and 54: Jargon BusterDemonstration StageThe
Page 55 and 56: Jargon BusterKey User Requirements
Page 57: Jargon BusterSystem AcceptanceThe f

The Acquisition Handbook

Create successful ePaper yourself

Delete template?

Save as template?