Procurement Module

1. Module Overview & Purpose

Procurement Foundations

Warehouse Management

Office

Procurement & Purchasing

🏗️ Site Applications

• Site Item Request (SIR)

Addons

• Connectors

• Suppliers Portal and eAuctioning

The Procurement & Purchasing module (PV‑04) manages the entire procurement life‑cycle in ProjectVIEW ERP, from the initial material request through purchase order issuance and delivery tracking. Its purpose is to give project teams a controlled, auditable way to obtain materials and subcontracted services while ensuring that every purchase is justified, budgeted and properly documented. The module serves as the interface between project budgets, suppliers and onsite operations.

Why it exists – Construction projects often have large, complex procurement needs. PV‑04 centralizes this process to improve cost control, maintain visibility over spending, enforce budget and cost‑code constraints and enable competitive sourcing. By integrating procurement with cost control, budgeting and accounting modules, it prevents unapproved purchases and reduces manual data entry.

Who uses it? PV‑04 supports multiple roles:

• Site Managers/Supervisors – initiate material request forms (MRF) when on‑site materials or services are needed.

• Procurement Officers/Managers – convert MRFs to purchase requisitions (PR), send request‑for‑quotation (RFQ) packages, evaluate supplier quotations and issue purchase orders (PO).

• Materials Managers – oversee material planning, coordinate with inventory and update cost databases.

• Subcontractors Managers – manage procurement for subcontracted work, conduct RFQs and evaluate bids.

• Warehouse/Inventory Managers – record goods receipt, inspect deliveries and update stock.

• Finance/CFO – approve high‑value purchase orders, monitor budget compliance and integrate procurement with accounts payable.

Business domains supported – PV‑04 underpins supply chain management, purchasing, materials management and vendor management within construction projects. It ensures that procurement spending aligns with estimates, budgets and the project’s cost structure.

Position in the system architecture – PV‑04 sits on top of the Core module (PV‑00) and relies heavily on data from Cost Control & Budgeting (PV‑02) for cost codes, budgets and financial limits. It feeds data into Materials & Production (PV‑05) for inventory and consumption, Accounts Payable (PV‑09) for invoice matching, and interacts with Subcontractors Management (PV‑03) and other modules to track subcontracting orders. It also supports add‑ons such as the Suppliers Portal and e‑Auctioning for enhanced collaboration and competition.

2. Conceptual Foundation & Theoretical Background

PV‑04 embodies procurement best practices tailored for construction projects. Its conceptual foundation rests on these principles:

• Controlled, budget‑driven procurement – Every request must be linked to a cost code and checked against remaining budget. The system shows available budget for selected cost codes and requires adjustments or reallocations if funds are insufficient.

• End‑to‑end supply chain visibility – Procurement is treated as a continuous process: MRF → Purchase Requisition → RFQ → Quotation Evaluation → Purchase Order → Goods Receipt → Invoice. Keeping the lifecycle in one module reduces data fragmentation.

• Competitive and transparent sourcing – RFQs are sent to multiple approved suppliers, quotes are compared using multi‑criteria evaluation (price, quality, delivery, service), and decisions are documented. This supports ethical procurement and ensures best value.

• Integration with cost control and budgeting – Procurement spending is controlled by linking every line item to cost codes, budgets and the BoQ structure. Approval workflows enforce authorization limits, ensuring that only users with the right authority can commit funds.

• Auditability & Compliance – Each procurement document (MRF, PR, RFQ, PO, goods receipt) has a full audit trail capturing status changes, approvals, amendments and user actions. This supports compliance with internal policies and external regulations.

3. Core Architectural Components

PV‑04 is structured around several core functional areas and data entities:

• Material Request Form (MRF) – Initiated by site personnel to request materials or services. Captures project, requester, required delivery date, and line items (material codes, quantities, specifications). MRFs are the starting point of the procurement workflow.

• Purchase Requisition (PR) – Created by converting an approved MRF. PRs formalize the request, allocate cost codes and budgets, and must be reviewed and approved before suppliers are contacted.

• Request for Quotation (RFQ) – RFQs are generated from approved PRs and sent to multiple suppliers. They include line item details, delivery dates and terms.

• Supplier Quotations – Suppliers respond to RFQs with offers. Procurement staff enter these quotations into PV‑04, capturing prices, lead times, payment terms and other conditions.

• Quotation Evaluation & Award – An evaluation matrix allows comparison of supplier quotes using weighted criteria such as price, quality, delivery and service. The winning supplier is selected and approved for PO creation.

• Purchase Order (PO) – A formal commitment to purchase; created from the winning quotation or manually. POs include supplier information, delivery schedules, payment terms and line items.

• Goods Receipt (GRN) – When goods arrive, warehouse personnel record receipt, document quantities and any discrepancies, and update inventory. This step links procurement with stock control.

• Amendments & Change Management – PV‑04 supports formal PO amendments for changes in quantity, price, delivery dates or scope, each requiring justification and approval.

Additional automation mechanisms include supplier auto‑selection based on category and performance, RFQ distribution with document attachments, quotation import from Excel and electronic auctions for competitive bidding.

4. Interconnectivity Within the Platform

Procurement does not operate in isolation. PV‑04 connects with other modules to ensure consistency and data flow:

• Input from PV‑00 (Core & Master Data) – MRFs and PRs rely on master data such as projects, suppliers, cost codes, currencies, payment terms and procurement categories configured in the core module. Without these, procurement requests cannot be created.

• Budget & Cost Control (PV‑02) – When converting MRFs to PRs and assigning cost codes, the system checks the budget availability. If insufficient funds remain, users must reduce quantities, split across cost codes or request budget reallocation; this integration prevents overspending.

• Subcontractors Management (PV‑03) – For procurement of subcontracted work, PV‑04 sends RFQs and POs to subcontractors. Evaluation results feed into subcontract performance metrics.

• Materials & Production (PV‑05) – Goods receipts update inventory and feed into materials consumption tracking. Returned or damaged goods trigger adjustments in PV‑05.

• Human Resources & Payroll (PV‑07) – Procurement of labor services may interface with HRMS for rates and supplier time sheets.

• Accounting & AP (PV‑08 & PV‑09) – POs and goods receipts feed into accounts payable and accounting. Invoice matching occurs after goods receipt, linking procurement documents to vendor invoices.

• Site Operations (PV‑11) – Site operations rely on timely delivery of materials; PO delivery schedules feed into project timeline management.

Shared master data ensures consistent supplier lists, cost categories and currency rates. Cross‑module workflows are triggered at key stages: PR approval triggers RFQ creation; PO approval triggers issuance; goods receipt triggers inventory updates and invoice matching; PO amendments may trigger budget revalidation.

5. Data Flow & Governance Model

Data Ownership & Access

• Procurement Team – Owns MRFs, PRs, RFQs and POs. They can create, edit and approve within authorization limits.

• Site Personnel – Can submit MRFs and view status but cannot approve POs.

• Finance/CFO – Have read access to all procurement documents and approval rights for high‑value POs.

• Warehouse Managers – Can access PO and goods receipt information to record deliveries.

Validation Mechanisms

• Budget & Cost‑Code Validation – During PR creation, the system displays available budget for selected cost codes and prevents approval if the PR exceeds the budget.

• Supplier Approval – Only suppliers marked as active and approved in master data can receive RFQs or POs; this ensures due diligence and compliance.

• Document Completeness Checks – Mandatory fields (project, material codes, quantities, delivery dates) must be filled before saving.

Approval Hierarchies

• PR Approvals – Based on cost code and budget; low‑value PRs may be approved by the Procurement Manager, whereas high‑value PRs require Project Manager or Finance Manager approval.

• PO Approvals – Authorization limits are defined (e.g., < 50 000 EGP approved by Procurement Manager, higher values routed to CFO).

Role‑Based Access Control (RBAC)

Each user is assigned a role with defined privileges. Access layers ensure that only authorized users can view or modify procurement documents. Sensitive financial information (pricing, supplier terms) may be restricted to procurement and finance roles.

Audit Logging

PV‑04 maintains a complete audit trail of all status changes, approvals, rejections and amendments. Users can view the Activity tab on PRs or POs to see who made changes and when, supporting accountability.

6. Dashboards & Decision‑Support Philosophy

PV‑04 provides dashboards that help executives and operational staff monitor procurement performance:

• Operational Dashboards – Show active MRFs, PRs, RFQs and POs, highlighting pending approvals, overdue quotations and upcoming deliveries. Real‑time status updates enable quick intervention.

• Analytical Dashboards – Provide spend analysis by project, supplier performance metrics, price trends and budget vs actual tracking. KPIs include average lead time, RFQ response rate, supplier quality and cost savings achieved through evaluation.

• Executive Dashboards – Summarize procurement spend across projects, highlight top suppliers, track compliance with budget and show savings achieved via competitive bidding.

Dashboards offer drill‑down capabilities from high‑level KPIs to individual documents and allow filters by project, supplier or date. Access is role‑based: site managers see only their project’s procurement status; finance managers see all projects; executives get consolidated views. Detailed configuration and usage of each dashboard is described in the Dashboard Manual (PV‑04 dashboards section).

7. User Roles & Interaction Model

Primary User Personas

Role	Responsibilities	Key Activities
Site Manager / Supervisor	Initiates procurement requests for materials and services.	Creates MRFs, tracks requisition status, checks delivery schedules.
Procurement Officer / Manager	Manages requisitions, RFQs, evaluations and orders.	Converts MRFs to PRs, assigns cost codes, sends RFQs, enters quotations, evaluates suppliers, creates POs.
Materials Manager	Plans material requirements, manages supply chain and cost databases.	Reviews requisitions, updates materials catalogs, tracks inventory integration.
Subcontractors Manager	Oversees subcontractor procurement.	Sends eRFQs to subcontractors, evaluates bids, issues subcontract purchase orders.
Warehouse / Inventory Manager	Receives and inspects goods.	Records goods receipt, notes discrepancies, updates stock levels.
Finance Manager / CFO	Controls spending, approves high‑value orders.	Reviews PO terms, verifies budget compliance, approves or rejects POs, ensures integration with AP.

Access Layers & Workflow Participation

• Initiators – Can create MRFs and view status but cannot edit after submission.

• Reviewers – Procurement officers and project managers review and edit PRs, assign cost codes and budgets.

• Approvers – Project managers, finance managers and CFOs approve PRs and POs based on authorization limits.

• Recipients – Warehouse managers record deliveries; they cannot edit procurement documents.

Responsibility segregation ensures that no single user can request, approve and receive goods, preserving internal controls.

8. Integration & External Connectivity

• ERP Integration – PV‑04 is natively integrated with other ProjectVIEW modules. It uses a single database for master data and cross‑module workflows. No separate data mapping is needed.

• BI Tools – Procurement data can be exported to Business Intelligence tools via built‑in reporting APIs. Data feeds support real‑time analytics and custom dashboards.

• APIs – Standard REST APIs allow external systems (e.g., vendor portals, e‑procurement platforms) to submit quotes, track POs, and receive purchase documents.

• Data Import/Export – Users can import supplier quotations from Excel and export procurement lists or reports to Excel or PDF. Integration with e‑mail enables automatic RFQ and PO distribution to suppliers.

9. Compliance & Security Considerations

Procurement affects financial commitments, so PV‑04 incorporates compliance controls:

• Regulatory alignment – Procurement processes align with corporate governance policies, local procurement regulations and international standards such as ISO 9001 for quality management.

• Budget & Authorization Control – The system enforces approval hierarchies and authorization limits, ensuring compliance with delegation of authority policies.

• Audit Trails – All actions, approvals and changes are logged for audit purposes.

• Data Retention & Privacy – Procurement records (MRFs, PRs, POs, quotes) are retained per corporate retention policies. Sensitive supplier data is protected with role‑based access, and connections to external portals use encrypted channels.

• Security Architecture – The module leverages ProjectVIEW’s underlying security framework, including user authentication, password policies and optional multi‑factor authentication. Data encryption is applied at rest and in transit; integration APIs support OAuth for secure external connections.

10. Documentation & Manuals Structure

To support users, PV‑04 is accompanied by a set of manuals and guides:

• Functional User Manual – Step‑by‑step instructions for creating MRFs, converting to PRs, sending RFQs, evaluating quotations, issuing POs, recording goods receipt and handling amendments.

• Administrator Guide – Details configuration of procurement categories, cost codes, approval matrices, supplier master data and integration settings.

• Dashboard Manual – Explains procurement dashboards, KPIs and how to customize analytical views for different roles.

• Workflow Configuration Guide – Describes how to tailor approval workflows, authorization limits and multi‑level approvals for PRs and POs.

• API & Integration Guide – Documents the procurement APIs for connecting external systems, vendor portals and BI tools.

• Release Notes – Provide information on new features, enhancements and bug fixes for each PV‑04 version.

• Best Practices – Summarizes recommended procurement practices, tips for RFQ distribution, supplier evaluation strategies and budget control guidance.

These documents provide deeper operational guidance and should be referred to after gaining an overview from this wiki page.