A SAMP (strategic asset management plan) is a high-level plan that turns organizational goals into asset management objectives. It also sets the approach for meeting those objectives. An asset management plan (AMP) is different. It is the detailed plan for a specific group of assets, covering what work is done, when and at what cost.
The two names sound alike, so teams often treat them as one document. A simple way to separate them is by job. The SAMP explains why and how you make asset decisions, and each AMP spells out what you will do with a given asset group. Below, you'll find both definitions, a side-by-side comparison and six steps to write your own plan.
Key Takeaways
A SAMP is the document that links organizational goals to the way you manage physical assets. ISO 55000 describes it as documented information. It explains how organizational objectives become asset management objectives, how plans are developed, and what role the asset management system plays in delivering results. Many organizations call the same document an asset management strategy.
The ISO 55000 family treats it as the bridge between the asset management policy and the plans that follow it. The policy states your commitment, the SAMP turns that commitment into objectives and an approach, and the AMPs carry out the work.
Most maintenance teams only see the plan if someone shares it on purpose. A plan that crews understand leads to better choices in the field.
A strategic asset management plan usually contains eight parts. Exact headings vary between organizations, but these items appear in most well-built plans.
An asset management objective is a measurable result that asset management must deliver. Writing clear objectives is the hardest part of the job, and most teams rush it.
An asset management plan is a detailed plan for operating, maintaining and funding a group of assets. It turns the strategic direction into actions, schedules and budgets that planners and crews can follow.
An AMP usually covers one asset class, site or service. A water utility might write separate AMPs for pumps, pipes and treatment buildings. A factory might write one for each production line and another for site utilities.
Most maintenance teams already hold much of this information in spreadsheets, PM schedules and work history. An AMP pulls it together in one document for each asset group.
To keep the asset records behind every AMP accurate, see how asset tracking gives each asset a live digital record.
The main difference is level of detail. A SAMP sets direction for the whole organization, while an AMP sets actions for one asset group. The table shows seven differences side by side.
| Area | SAMP | Asset Management Plan (AMP) |
|---|---|---|
| Purpose | Turns organizational goals into asset management objectives and decision rules | Sets the work, timing and budget for a specific asset group |
| Scope | Whole organization and all asset classes | One asset class, site or service |
| Time horizon | Long term, reviewed every few years or when strategy changes | Medium to long term, with detailed near-term actions and forecast outer years |
| Main audience | Executives, asset owners, board and regulators | Planners, engineers, maintenance managers and finance |
| Typical owner | Head of asset management or a senior leader | Asset class or site manager |
| Key content | Objectives, decision criteria, governance and lifecycle approach | Asset register, condition, levels of service, tasks, risks and costs |
| Review cycle | On a set cycle and when strategy or risk changes | Often yearly, and after major failures or budget changes |
One document does not replace the other. A SAMP without AMPs stays theory, and AMPs without a SAMP drift apart into local plans that pull in different directions.
A common mistake is to write one long AMP and call it a SAMP. If a document lists tasks and frequencies for each pump, it is an AMP. If it explains how you rank work across every asset class, it is the strategic plan.
A SAMP and its AMPs work together through line of sight. Line of sight is the traceable link from an organizational goal to the daily task that supports it. Every task in an AMP should trace back to an objective in the strategy, and every objective should trace back to a goal.
The SAMP Line-of-Sight Framework:
If a task has no line back to an objective, it is a candidate to stop or rethink. That simple test often exposes low-value work that nobody has questioned.
Say a packaging plant's goal is to ship every order on time. The plan sets an objective to raise availability on the three lines that limit output. Its decision criteria rank assets by the cost of a stoppage.
The AMP for those lines then sets weekly inspections, condition checks and a critical spares list. Each month, work order data shows whether availability is moving, and the next review adjusts the objective if demand changes. That loop is what makes the plan more than a document.
You write a SAMP by moving from goals to objectives to decision rules, and then naming the plans that will deliver them. Bring operations, finance and maintenance into the room, because each group sees different risks.
Keep the finished document short enough that executives will read it. If a section needs pages of detail, move that detail into the relevant AMP.
Choose the few KPIs that directly measure your objectives, and leave the rest out.
Most SAMP problems come from habits, not from a lack of effort. These six mistakes are easy to make and easy to fix.
Most operations that struggle with asset management have a plan on paper but no data flowing back into it. Fixing the feedback loop usually matters more than polishing the document.
A Computerized Maintenance Management System (CMMS) helps you deliver a SAMP by capturing the daily asset data that shows whether objectives are being met. It holds the asset register, work history and KPIs that every review depends on.
Maintenance teams using Cryotos have reported up to 30% reduction in unplanned downtime and 25% faster repair turnaround. Fewer emergency repairs means more of the plan runs as designed, and more availability objectives are met.
SAMP stands for strategic asset management plan. It is the high-level document that shows how an organization's goals shape its asset management objectives, decision rules and plans. Some organizations call it an asset management strategy.
A SAMP sets direction for the whole organization, while an AMP sets detailed actions for one asset group. The strategic plan covers objectives, decision criteria and governance. The AMP covers the asset register, tasks, risks and budgets that deliver those objectives.
Check the current text of ISO 55001 and speak with your certification body, because requirements depend on how you document your system. In practice, ISO 55001 expects documented asset management objectives, plans to achieve them and a clear link to organizational goals. Most organizations use a strategic plan like this to hold that information.
A SAMP should be long enough to cover objectives, decision criteria, lifecycle approach and governance, and short enough for senior leaders to read. Asset-class detail belongs in the AMPs, not in the strategy.
Most organizations review the plan on a fixed cycle and again when strategy, regulation or risk changes. AMPs are usually reviewed more often, because asset condition and budgets change faster than strategy.
A small facility rarely needs a long document. It still benefits from writing down its objectives, decision rules and ownership on a page or two. That short document does the same job and makes later AMPs easier to write.
Yes. A CMMS holds the asset register, work history and KPIs that show whether your objectives are being met. It does not write the plan for you, but it supplies the evidence for every review.
A clear SAMP gives every asset decision a purpose, and the right data keeps it honest. Schedule a free demo to see how Cryotos connects asset records, planned maintenance and live KPIs to your asset management objectives.
Cryotos AI predicts failures, automates work orders, and simplifies maintenance—before problems slow you down.
