For outsourced engineering, maintenance or inspection, e-procurement begins with a service brief that explains what the plant will accept. A purchasing platform can route requests and retain approvals; the service owner still has to define the deliverable, judge the evidence and resolve exceptions.
Turn the need into an inspectable deliverable
Replace “improve the pump system” with an outcome that can be reviewed: inspect the listed pumps during an agreed shutdown, provide identified measurements and findings, and submit a prioritized repair report in the required format. Include asset identifiers, available drawings, site conditions and the boundary between investigation and repair. State who supplies access, isolation arrangements, escorts, tools and supporting data through the plant's approved procedures.
Attach a scope revision to the request for quotation. List required deliverables, dates, assumptions and acceptance criteria. If the work includes an uncertain discovery phase, define its output and an approval point before additional work. This gives suppliers a common basis for estimating and gives the plant a way to control changes.
Microsoft's procurement and sourcing overview illustrates the path from purchasing needs through supplier selection, orders and invoices. Actual roles and document flows depend on the organization's configuration and purchasing policy.
Compare scope before comparing totals
Ask each bidder to identify inclusions, exclusions, dependencies and deviations against the same brief. Resolve a missing test or report as a clarification, then record whether it changes price or schedule. Keep mandatory qualification requirements separate from scored preferences so an attractive price cannot conceal a missing essential capability.
On a narrow screen, scroll the table horizontally. Keyboard users can focus it and use the arrow keys.
| Question | Evidence to request | How it affects the decision |
|---|---|---|
| Is the scope complete? | Response against every deliverable and exclusion | Normalize required work before comparing totals |
| Can the team do it? | Relevant experience, named roles, required qualifications | Resolve mandatory requirements before award |
| Can the plant support it? | Access needs, shutdown dates, supplied information | Check dependencies with operations |
| How will it be accepted? | Report samples, test evidence and review milestones | Assign an acceptance owner and response time |
Publish the evaluation method internally before scoring. Define what each score means and retain a short evidence-based explanation. Microsoft documents RFQ scoring methods and criteria; a configured score is most useful when the underlying evidence remains visible to the reviewer.
Fictional comparison: Offer A is $9,000, excluding $1,000 of required testing and $1,500 of travel. Its comparable scope total is $11,500. Offer B includes the same work for $11,000, making B $500 lower on these inputs.
These invented amounts illustrate scope normalization. Confirm currency, taxes, timing and remaining exclusions separately, then consider capability and delivery risk under the agreed evaluation method.
Connect the order to accepted work
Carry the selected scope revision, milestones and commercial assumptions into the approved purchasing record. Identify who can request a change, who assesses its effect and who approves the revised commitment. A supplier's extra-work email should lead to a recorded decision with scope, cost and schedule consequences.
At each milestone, the service owner checks the actual deliverable against the agreed criteria. Record accepted, accepted with specifically authorized outstanding items, or returned for correction, according to local policy. Link the decision to the report or test record and preserve the reviewer and date.
Service receipt and invoice controls vary. Microsoft's overview explicitly describes service cases in which product receipt can be skipped or registered directly. Configure the appropriate service-acceptance evidence with procurement and finance; do not assume every service purchase follows the same physical-goods receipt process.
Resolve exceptions where they arise
If an invoice references an unapproved change, reconcile the request and authorization before processing it under the plant's rules. If a report arrives on time but lacks required measurements, return the missing-evidence list to the service owner. If access delays the work, record who owns the dependency and whether the milestone must change.
Close the project with the final scope, accepted deliverables, open warranty or follow-up items, and a supplier-performance note based on observed results. For the controlled drawings and product revisions supplied to a contractor, use the related product lifecycle management guide.
Use the working record
Download the editable service bid comparison. Save a copy, complete the actual requirements and evidence fields, and review open issues with the responsible owner. The plain-text record includes instructions, units where needed, the fictional example, and source references.