EAM.7 - Generate Ways to Supply an Asset-Dependent Service
Type: Method Status: Stable
EAM.7:1 - Problem frame
Use this pattern when a needed service contribution has become a proposal to acquire or modify an asset. A team has a preferred machine, supplier or design, but materially different ways of obtaining the contribution could change cost, risk or feasibility.
Distinguish the required service contribution from the asset or provider first proposed to supply it. Return technically meaningful alternatives and the conditions needed to realize each one.
EAM.7:2 - Problem
Searching only within the familiar equipment category can exclude sharing, leasing, reconfiguration or demand change. The opposite mistake lists attractive concepts without showing how their contributions could be realized. A vendor’s availability claim then substitutes for an applicable engineering answer.
EAM.7:3 - Forces
Ownership can provide control while creating continuing support and exit burdens. Shared or leased service can reduce initial capital while adding dependency and recurring cost. A technically novel arrangement can improve value but require evidence and integration work that the decision window cannot support.
EAM.7:4 - Solution
Recover the required outside contribution, recipients, conditions and horizon from EAM.1 and EAM.2. Identify which feature of the incumbent arrangement is an assumption rather than a requirement.
Form materially different ways to supply the contribution. Depending on the problem, these can include changing an existing asset, acquiring a new one, redistributing capability, sharing a provider, leasing a service or changing demand. A renamed supplier offering with the same relevant behavior is not a distinct architectural alternative.
Describe how each option could work. Identify the asset or provider, integration with the present arrangement, interfaces, access, support and changes to operation. Use an applicable SYSE.5 result when functional organization and bearer allocation determine the option. Obtain subject-specific engineering where physics or other specialist constraints decide feasibility.
State the realization conditions and consequences for the same required service. Include procurement and integration time, interruption, continuing cost, dependency, reversal and exit. Identify what remains uncertain, including whether a proposed interface is compatible.
Compare the set with the incumbent or a no-build response. Explain why withdrawal, demand change or another contribution is included or excluded in this case. If an option requires amending a service commitment, identify the separate decision on the amendment and whether the competent authority has made it.
Return enough materially different alternatives to support comparison under EAM.9. Stop adding options when further generation is unlikely to improve the requested answer at a worthwhile burden. For a promising option that cannot yet be used, identify the dependency that still lacks support.
EAM.7:5 - Archetypal Grounding
CityWater’s wet-season North requirement exceeds the present 1,000 m³/h capability by 100. The shortlisted C modification and leased service each add a qualified 200. The modification requires €3 million initial capital and €0.20 million annually; the leased service requires no initial capital and €1.20 million annually, under the supplied five-year terms.
The alternatives differ in funding, continuing cost, realization time and dependence on the service provider. The lease can free capital for D replacement, while its recurring cost changes the whole portfolio comparison.
If the proposed leased service has no applicable evidence for the required connection and delivery conditions, it remains conditional. A quotation and a nominal pump rating do not establish that service. The practitioner asks for the needed engineering result.
EAM.7:6 - Bias-Annotation
A procurement channel can narrow the set before the asset question is answered. Supplier information can favor purchase or service contracts according to commercial interest. Preserve the costs and dependencies borne by the utility and service users.
EAM.7:7 - Conformance Checklist
Are the alternatives materially different ways to provide the same needed contribution? Are their realization conditions and continuing consequences visible? Can the recipient distinguish a supported candidate from a concept awaiting a decisive result?
EAM.7:8 - Common Anti-Patterns and How to Avoid Them
Three bids for effectively the same arrangement can conceal a missing service alternative. Challenge the bearer assumption before counting options.
Treating a service contract as removal of engineering dependence hides the provider and interface conditions. State the contribution the provider must deliver and the evidence needed to support reliance on the provider and the interface.
EAM.7:9 - Consequences
The comparison can reveal a lower-capital, more reversible or otherwise valuable alternative. Some concepts remain conditional, and more engineering may be required for a consequential choice.
EAM.7:10 - Architectural Rationale
The pattern separates desired contribution from physical or contractual form. This lets the decision maker compare engineering and financial consequences across alternatives. It complements EAM.8’s policies for existing assets. Acquisition is one possible starting point.
EAM.7:11 - SoTA-Echoing
For finding materially different ways to obtain an asset’s required contribution, adopt SYSE.5:4.1’s joint development of functional organization, bearers, interfaces and realization conditions. Adapt it to the receiving asset comparison by retaining the alternatives whose capital, continuing burden, service or dependency differences can change the choice. In CityWater, modification and qualified leased service provide the same additional flow but compete differently for capital and continuing expenditure. The Solution therefore establishes the contribution before fixing ownership or a particular construction.
In specification-led acquisition, hold an already justified asset arrangement fixed and compare designs or suppliers able to realize it. GFMAM’s Asset Management Landscape, third edition, June 2024, section 6.2 (pp. 72–73), provides the acquisition and integration comparator; its section 3.4 also keeps new, existing and non-asset responses available at planning scope. Retain specification-led comparison when the bearer decision is already supported. Where ownership is only an initial assumption, selecting it first could exclude C’s service option before its funding consequence is examined. The broader contribution comparison costs some additional provider/interface analysis, accepted because it can change the feasible asset programme; it stops short of detailed engineering for every conceivable option. The sources describe the methods. To rely on the lease, obtain evidence that the provider is available and that the service is compatible with the required connection. Reopen the choice when a required interface cannot be realized, a provider qualification changes, an incumbent assumption becomes an actual requirement, or a newly supported arrangement could improve the decision enough to justify examining it.
EAM.7:12 - Relations
EAM.2 and EAM.4 supply the need; EAM.3 and EAM.6 supply configuration and capability conditions. SYSE.5 supports bearer and interface alternatives. EAM.8 supplies existing-asset policies, EAM.9 compares value and EAM.11 tests realization timing.