Guides for procurement & sourcing.

When Predictive Monitoring raises an alert, ticket, or inspection finding on an asset, it can be turned into a purchase requisition with the failing asset and its site already attached. The requisition keeps a link back to the originating fault, so the whole chain — alert → requisition → RFQ → PO → receipt → payment — stays traceable as one document trail.

The asset reference, site, and category flow from the alert or inspection into the requisition line. Where a catalog item matches, description, unit of measure, and preferred-supplier pricing autofill. This removes re-keying and keeps requisitions clean and consistent across O&M teams.

Yes. Requisitions can be raised directly for planned spend — spares for preventive maintenance, EPC scope, or O&M consumables — with priority, estimated total, and site/cost-center allocations. The alert path is an accelerator, not a requirement.

Create an RFQ from a requisition or from scratch, add lines, and invite suppliers from your organisation's vendor list. Suppliers submit quotes through the vendor portal. Responses are compared side by side on a scored comparative statement, and the award is recorded against that statement rather than an ad-hoc decision.

A reverse auction lets invited suppliers competitively lower their bids within a live window, with a starting price and minimum decrement. Use it for commoditised, well-specified line items where multiple qualified suppliers can compete purely on price. Technical qualification can gate who is allowed to bid.

When an RFQ requires technical evaluation, assigned evaluators record a verdict per quote. A quote is technically accepted only when every currently-assigned evaluator has accepted it; any rejection blocks award. This keeps commercial award separate from — and downstream of — technical qualification.

An RFQ can require an NDA before line detail is visible. Until the invited supplier's matching agreement is in place, the vendor portal hides line detail and blocks quote submission for that supplier.

Approvals are matched by amount, category, site, and department. Beyond a specific user or the requester's manager, routing supports approval groups, manager chains (walking a reports-to hierarchy by authority amount), and an authority matrix matched on site/category/department/amount range. Requisitions, POs, awards, contracts, and payments each flow through the policy that matches them.

Behaviour is configurable per organisation. The default is to auto-approve (legacy behaviour); organisations that require gating set no-match to block, so an unrouted document is stopped rather than sailing through ungated. An RFQ award, for example, will not complete if a required policy is missing and the org blocks unapproved awards.

A user can delegate their pending approvals to another user for a date range, optionally scoped to specific document types. Per-step reminders and escalation timers keep approvals moving, and parallel approval groups let several approvers act at the same step.

Yes. A policy can be simulated against live documents to show exactly who would approve what, so a matrix edit never silently re-routes spend the wrong way.

The procurement command center surfaces critical insights such as a possible duplicate invoice from the same supplier within a short window, or a possible split PO — several orders to one supplier that each land just under the approval threshold. These are highlighted for review before they clear.

Insights are shown on the buyer's command center alongside approvals, spend snapshot, and the requisition/PO/invoice/payment KPI row, so the person who can act on them sees them in context.

Receive against the purchase order (and, where used, the vendor's advance shipment notice). The platform matches PO, goods receipt, and invoice, holding exceptions for review before payment. A goods receipt can be linked back to the ASN that fulfilled it.

Payments run through an approval lifecycle and support scheduled payments, retention release, early-payment requests (a vendor offers a discount for early settlement), and credit notes that can net off a payment. Payment-blocking compliance requirements must be accepted before a payment is released.

Through the vendor portal, suppliers raise invoices, request early payment against an approved unpaid invoice, and submit credit notes with supporting documents. Finance sees each against the matched PO and goods receipt.

Compliance requirements — bank guarantees, insurance, warranty, and other evidence — are tracked per purchase order with vendor- or buyer-submitted evidence. Requirements flagged as payment-blocking must reach accepted before a payment or tranche release is allowed, and a daily expiry sweep flags evidence that is lapsing.

Configurable tax handling travels with the transaction — tax registers, withholding, and invoice reconciliation — and adapts to the jurisdiction you operate in, so tax compliance rides along with each document instead of living in a separate spreadsheet.

Contracts (MSA, NDA, framework, AMC, service agreements) have a draft→active approval gate, document storage with checksums, due-date obligation tracking, and a renewal chain. A daily lifecycle sweep flags expiring or expired contracts and overdue obligations.

The vendor portal gives suppliers a ranked to-do: confirm purchase-order lines (promise a date and quantity), keep compliance evidence current, respond to RFQs before the deadline, upload requested documents, mark shipments in transit, and sign issued agreements. It removes the email back-and-forth from day-to-day collaboration.

One real vendor company gets a single platform-wide identity (a shareable vendor code) instead of a separate account per buying organisation. Buyers invite vendors by code or email; vendor members see a unified cross-company inbox and a company switcher rather than juggling separate logins.

Two-sided messaging is scoped to a PO, RFQ, or invoice, with in-app and email notifications routed by each vendor user's preference (immediate, daily digest, or off). RFQ clarifications let a vendor ask a question privately until the buyer publishes the answer to all invited suppliers.

The catalog is an organisation-scoped internal item master with per-supplier pricing. A preferred supplier resolves the default unit price. Requisition and RFQ lines can reference a catalog item to autofill price, unit of measure, and description.

Yes. Vendors can propose a price update to an existing catalog item or submit a brand-new item; buyer approval upserts the per-supplier pricing (with minimum order quantity and validity dates).