This Asset Management Framework (AMF) Journal entry is the next in a series on SAMPs. Prior entries are listed below:
This entry is a pre-culmination installment providing good examples of a SAMP. This is a good news story and there is a lot to be happy about. This entry will:
Set the stage for what a SAMP is and is supposed to do,
Summarize, as an example, US Federal requirements for a SAMP for built infrastructure,
Highlight key features and benefits of effective SAMPs, and
Highlight excellent leading examples of SAMPs for built infrastructure in the US Federal government.
The concluding entry in this AMF SAMP miniseries will be released next month titled: SAMP Development Playbook.
What is a SAMP and What it Needs to Do
A SAMP is the wheelhouse, the command-and-control center for how an organization manages its built infrastructure portfolio. It defines what is covered, what is important, and what needs to be done to built infrastructure for the organization to be successful. It justifies budgets and establishes the business case and strategy for coordinating capital, maintenance and repair (M&R), and operations and maintenance (O&M) programs. The SAMP is also the principal means of communicating plans of action and providing stakeholder assurances that built infrastructure will be ready to support operations and production when, where, and how needed.
What the SAMP needs to do is organize this information so that it is understandable to many different constituents, stakeholders, and decision makers.