What does the Procurement AI Agent do? The Procurement AI Agent is an AI procurement agent for construction and project-based industries, part of DANAOS ProjectVIEW AI. It is designed to compare supplier quotations, check prices against the budget rate for each BoQ item and flag anomalies before an order is placed. The procurement officer approves every award and purchase order. Which ProjectVIEW ERP data does it use? The agent uses the data in the Procurement and Purchasing module of ProjectVIEW ERP, linked to the budget through BoQ, WBS and Cost Codes. Purchase requisitions and need dates from the WBS Supplier quotations and price history Budget rates by BoQ item and Cost Code Purchase orders, deliveries and supplier performance Committed cost against budget How does it work? The agent follows the ProjectVIEW AI agent cycle. Applied to procurement: Detect: flag a quotation above the budget rate, an unusual price change or a missing item in a supplier offer. Investigate: compare all quotations for the requisition with price history and the budget. Explain: state what is different and what it means for committed cost. Recommend: propose an award, a negotiation point or a request for a revised offer. Request approval: send the recommendation to the procurement officer. Execute: after approval, create or update the purchase order in ProjectVIEW ERP. Audit: record the comparison, the recommendation and the decision. The agent works within the approval limits set for each role. It does not place orders without a person’s approval. What goes in, what comes out and where does a person approve? Main inputs, outputs and decision points: Inputs Outputs Human approval point Requisition and need date Comparison sheet of quotations by item Procurement officer reviews the comparison Supplier quotations and price history Anomalies: prices above budget rate, missing items, unusual terms Procurement officer decides on clarification or negotiation Budget rates and committed cost Impact of the proposed award on the cost code Cost controller confirms where budget is exceeded Approved award Draft purchase order Authorised approver releases the order How is the agent governed? The Procurement AI Agent works inside ProjectVIEW ERP governance, following the chain Identity → Role → Permission → Data → AI → Action. It sees only the data the user’s role allows and proposes only actions that role could take. AI should operate inside enterprise governance, not around it. Consequential actions always need human approval. Every recommendation, approval and change is recorded for audit. Data stays in the client’s private environment and is not sent to public consumer AI services. Example: how could it work on a project? Illustrative example. A contractor needs reinforcement steel for Project D. Three quotations are entered against the requisition in ProjectVIEW ERP. The agent compares them and flags that the lowest offer excludes delivery to site and that all three are above the budget rate for the item. It explains the effect on committed cost for the concrete works cost code. It recommends asking the lowest bidder for a delivered price and alerting the cost controller to the budget gap. The procurement officer approves the request, the revised offer is compared, and the purchase order is released by the authorised approver. Each step is logged. Who uses it? The agent is designed for buyers and the people who control spend: Procurement officers who compare offers and issue purchase orders Cost controllers and project managers who need to see committed cost before invoices arrive It applies to construction, shipbuilding and repair and other project-based industries that buy against a BoQ. Frequently asked questions What does an AI procurement agent for construction check? It is designed to check each quotation against the budget rate, price history and the other offers, and to flag missing items or unusual terms. The aim is to see cost exposure before the order is placed. Can it place purchase orders? It can prepare a draft purchase order after an award is approved. Releasing the order stays with the authorised approver, within the limits set for each role. Does it work with need dates from the schedule? Requisitions in ProjectVIEW ERP are linked to the WBS, so the agent can take need dates into account when it flags late or at-risk purchases. How can you see it on your own data? See how the Procurement AI Agent is designed to work on your own requisitions and quotations. See all agents on the ProjectVIEW AI agents page. Related reading: Construction procurement planning: working backward from WBS need dates to site delivery. Book a Demo