1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[5824],{99071:function(e,t,r){(window.__NEXT_P=window.__NEXT_P||[]).push(["/products/supista-epc-erp/features/[slug]",function(){return r(60125)}])},85805:function(e,t,r){"use strict";r.d(t,{Z:function(){return i}});var o=r(85893),a=r(67294),n=r(26692);function i(e){let{children:t,eventName:r,...i}=e,[s,c]=(0,a.useState)(!1),l=()=>{{let e=window;e.dataLayer=e.dataLayer||[],e.dataLayer.push({event:r,product:"supista_epc_erp"})}c(!0)};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)("button",{...i,type:"button",onClick:l,children:t}),(0,o.jsx)(n.default,{isOpen:s,onClose:()=>c(!1)})]})}},60125:function(e,t,r){"use strict";r.r(t),r.d(t,{__N_SSG:function(){return y},default:function(){return b}});var o=r(85893),a=r(25675),n=r.n(a),i=r(41664),s=r.n(i),c=r(13767),l=r(85805),d=r(5197),p=r(11572);let u=function(e,t,r,o,a){let n=arguments.length>5&&void 0!==arguments[5]?arguments[5]:720,i=arguments.length>6&&void 0!==arguments[6]?arguments[6]:420;return{src:e,alt:t,width:n,height:i,title:r,caption:o,annotations:a}},m={"project-management":{slug:"project-management",seoTitle:"EPC Project Management Software | Supista ERP",meta:"Control EPC schedules, site progress, procurement, materials and project costs from one connected, role-based project management system across sites.",eyebrow:"EPC project management software",h1:"Keep every EPC project on schedule and within budget",hero:"Built for project directors, project managers and EPC business leaders. Connect planning, site execution, procurement, cost and billing around the same project so teams see risk, ownership and next actions early.",definition:"EPC project management software connects the work breakdown structure (WBS), activities, site progress, materials, procurement, costs and billing in one project record. It gives delivery teams a current view of planned work, actual progress, blockers and commercial exposure without replacing engineering or project leadership judgement.",problemHeading:"When the plan and site reality stop matching",problems:[{title:"Progress arrives too late",copy:"Site updates sit in calls, messages and separate Daily Project Reports. The baseline remains unchanged, so leaders discover slippage after a milestone is missed."},{title:"Workfronts look ready",copy:"An activity has dates and an owner, but drawings, approvals, materials or subcontractors are unavailable. Crews wait and corrective action starts late."},{title:"Cost lacks execution context",copy:"Purchase orders, expenses and bills move without a clear work-package view. Management sees an overrun but cannot quickly locate its operational cause."}],connectionHeading:"Connect every control around the project",connectionIntro:"The project record provides common context for the plan, daily site facts and commercial transactions. Teams can move from a delayed milestone to the activity, material requirement, purchase status, expense or bill behind it.",connections:["Project and WBS","Work package and activity","Milestone and owner","DPR and blocker","BOQ and budget","Procurement and material","Expense and subcontract","Billing and collection"],capabilities:[{title:"Project structures",copy:"Organise phases, WBS elements, work packages and activities with accountable owners. Prevent teams from reporting against inconsistent project structures.",icon:"building"},{title:"Milestone control",copy:"Record planned dates, dependencies and responsible roles. Review what changed before a downstream milestone is affected.",icon:"calendar"},{title:"Planned versus actual",copy:"Compare baseline progress with approved site updates and quantities. Focus reviews on the packages where actual execution is falling behind.",icon:"chart"}
1,{title:"Daily site evidence",copy:"Relate DPR entries, photos, manpower, equipment and blockers to current work. Keep a usable record behind each reported update.",icon:"file"},{title:"Readiness checks",copy:"View material requirements, purchase status and site availability beside upcoming work. Identify workfronts that need action before crews mobilise.",icon:"box"},{title:"Cost visibility",copy:"Review BOQ, budget, commitments, expenses and billing in project context. Trace an exception to the source record instead of rebuilding a spreadsheet.",icon:"wallet"},{title:"Corrective actions",copy:"Record blockers, owners, target dates and follow-ups. Make unresolved constraints visible in the next project review.",icon:"alert"},{title:"Role dashboards",copy:"Give leaders, project teams, procurement and finance views suited to their responsibilities. Preserve role-based access to underlying records.",icon:"eye"}],visual:u("/assets/img/screenshots/epc/project-dashboard.png","Supista project workspace showing project status, WBS records and accountable owners","From portfolio signal to project record","Review status, ownership and project records in one workspace, then open the source information requiring action.",["Project status remains visible","WBS records retain ownership","Teams can open the underlying record"],1672,941),workflowHeading:"Move from WBS setup to controlled execution",workflow:[{title:"Structure the project",trigger:"Awarded project and control plan",role:"Project controls team",record:"Project, WBS and work packages",control:"Approved structure and ownership",handoff:"Budget and planning baselines"},{title:"Set the baseline",trigger:"Approved WBS",role:"Project manager and planner",record:"Activities, dates, milestones and dependencies",control:"Baseline review",handoff:"Site execution and material planning"},{title:"Report execution",trigger:"Daily site work",role:"Site engineer",record:"DPR, quantities, evidence and blockers",control:"Project review or approval",handoff:"Updated progress and actions"},{title:"Connect supply and cost",trigger:"Upcoming work and approved demand",role:"Procurement and commercial teams",record:"Requirements, orders, receipts and commitments",control:"Budget and approval checks",handoff:"Material readiness and cost view"},{title:"Review and correct",trigger:"Variance or unresolved blocker",role:"Project director",record:"Corrective action and owner",control:"Management review",handoff:"Revised action plan and billing readiness"}],roleHeading:"Give each project role the view needed to act",roles:[{title:"Project director",copy:"Compare schedule, cost, material and billing exposure across active projects."},{title:"Project manager",copy:"Control milestones, work packages, dependencies, blockers and accountable actions."},{title:"Site engineer",copy:"Report progress and evidence against the correct activity from site."},{title:"Commercial head",copy:"Relate physical progress to commitments, cost, billing and collections."}],loisHeading:"Ask Lois about the project work needing attention",lois:[{ask:"Which activities may miss this weekâs milestones?",checks:"Activities, dates, dependencies, progress and open blockers",prepares:"A risk summary linked to available records",review:"The project manager validates causes and corrective actions"},{ask:"Show workfronts waiting for materials or approvals.",checks:"Upcoming activities, requirements, orders, receipts and approval status",prepares:"A readiness list with owners and pending items",review:"Responsible teams confirm availability and priorities"},{ask:"Prepare todayâs management project summary.",checks:"Permitted progress, cost, procurement, blocker and billing records",prepares:"A concise draft with source context",review:"The project director reviews interpretation before sharing"}],lifecycleFocus:["project plan","site execution","analytics"],related:[{slug:"planning-scheduling",label:"Planning and scheduling"},{slug:"daily-project-report",label:"Daily Project Reports"},{slug:"boq-budget-cost-control",label:"BOQ and cost control"}],assuranceHeading:"Configure project control around your operating model",assuranceCopy:"Start with one live project, its WBS, reporting formats, roles and approvals. Supista supports configurable workflows, role-based access, mobile-friendly reporting and ISO/IEC 27001-certified information-security controls.",faqs:[{question:"What is EPC project management software?",answer:"EPC project management software connects WBS planning, site execution, procurement, materials, costs and billing so delivery teams can control schedule and budget from one project record."},{question:"Can teams manage WBS, work packages and milestones?",answer:"Yes. Teams can structure projects into WBS elements, work packages and activities, assign owners, set dates and maintain milestone and dependency context."},{question:"Can project managers see material and approval blockers?",answer:"Yes. Project views can relate upcoming activities to available requirement, approval, purchase, receipt and blocker records so managers can identify workfronts needing action."},{question:"Does Supista replace specialist planning software or judgement?",answer:"No. Supista connects planning context with operational records. Planners, engineers and authorised project leaders remain responsible for baselines, forecasts and professional decisions."},{question:"Can site teams report progress from mobile devices?",answer:"Mobile-friendly workflows can let authorised site users record progress, quantities, blockers, expenses and supporting evidence, subject to the configured implementation."}
1,{question:"How does Lois support project management?",answer:"Lois can summarise permitted project records and prepare supported drafts. Users review the result, while configured validations, permissions and approvals continue to apply."}],finalHeading:"See how one active EPC project can run in Supista",finalCopy:"Bring your WBS, progress format or current project-control challenge. Weâll show how planning, site execution, procurement, cost and billing can share controlled project context."},"boq-budget-cost-control":{slug:"boq-budget-cost-control",seoTitle:"BOQ, Budget and Cost Control Software for EPC Projects",meta:"Control EPC BOQ revisions, approved budgets, commitments, actual cost and forecasts with package-level variance and source-record drill-down.",eyebrow:"EPC BOQ and project cost control software",h1:"Control BOQ, budget, commitments and actual project cost",hero:"Built for commercial heads, quantity surveyors and project directors. Keep approved quantities, budget allocations, purchase commitments, subcontract bills and site expenses connected so cost exposure is visible before final accounts.",definition:"EPC BOQ and project cost control software organises the Bill of Quantities (BOQ), approved budget, commitments, actual costs and forecasts by project, cost code and work package. BOQ value represents priced scope; budget is the approved spending limit; commitments are contracted amounts; actual cost is recorded expenditure; forecast cost estimates the expected final position.",problemHeading:"Why project cost reports arrive after the decision window",problems:[{title:"Revisions lose their history",copy:"BOQ quantities change, but teams circulate renamed spreadsheets. Buyers and commercial teams may work from different versions, creating incorrect package limits."},{title:"Commitments stay hidden",copy:"Management reviews posted costs while approved purchase orders and work orders sit elsewhere. The apparent budget headroom disappears when invoices arrive."},{title:"Variance has no source",copy:"A package is over budget, but the report cannot show which order, bill, expense or quantity caused it. Corrective action becomes slow and disputed."}],connectionHeading:"Follow value from BOQ line to final cost",connectionIntro:"Cost control works when each commercial record retains project, WBS, package and cost-code context. A variance can then be traced from summary to purchase order, subcontract bill or site expense.",connections:["BOQ version","Approved estimate","Budget allocation","Cost code","Purchase commitment","Subcontract commitment","Actual expense","Forecast and margin"],capabilities:[{title:"BOQ revisions",copy:"Maintain controlled BOQ versions and revision context. Prevent teams from treating an obsolete quantity schedule as the current commercial baseline.",icon:"file"},{title:"Approved budgets",copy:"Allocate approved budgets by package, cost code or configured dimension. Give approvers the correct control limit before a commitment is made.",icon:"shield"},{title:"Commitment view",copy:"Bring approved purchase and subcontract commitments into cost reviews. Show exposure that has not yet become an invoice or paid cost.",icon:"cart"},{title:"Actual cost",copy:"Relate recorded invoices, subcontract bills and expenses to their cost context. Reduce manual reconciliation between accounts and project reports.",icon:"wallet"},{title:"Package variance",copy:"Compare budget, commitment and actual cost at a useful project level. Direct commercial reviews toward exceptions with material impact.",icon:"chart"},{title:"Forecast context",copy:"Combine available cost and progress records to support forecast reviews. Authorised teams retain responsibility for estimate-to-complete assumptions.",icon:"eye"},{title:"Source drill-down",copy:"Open the orders, bills and expenses behind a number. Give reviewers evidence without distributing parallel spreadsheets.",icon:"link"}],visual:u("/assets/img/screenshots/epc/cost-control.svg","EPC cost-control workflow graphic comparing BOQ, budget, committed cost and actual cost","Understand the five cost positions","A controlled cost review separates priced scope, spending authority, contractual exposure, recorded cost and expected final cost.",["BOQ defines priced scope","Commitments expose future cost","Drill-down explains variance"]),workflowHeading:"Control cost from baseline through forecast",workflow:[{title:"Ap
1prove scope",trigger:"Contract BOQ or approved revision",role:"Quantity surveyor",record:"Versioned BOQ",control:"Revision approval",handoff:"Estimate and budget preparation"},{title:"Set cost limits",trigger:"Approved estimate",role:"Commercial head",record:"Budget by package and cost code",control:"Management approval",handoff:"Procurement and work-order controls"},{title:"Capture commitments",trigger:"Approved PO or subcontract work order",role:"Procurement and commercial teams",record:"Committed cost",control:"Budget availability and approval",handoff:"Cost exposure reporting"},{title:"Record actual cost",trigger:"Invoice, bill or supported expense",role:"Finance team",record:"Actual cost entry",control:"Validation and financial approval",handoff:"Project cost report"},{title:"Review forecast",trigger:"Progress or cost variance",role:"Project director",record:"Forecast and corrective action",control:"Professional commercial review",handoff:"Management margin outlook"}],roleHeading:"Make cost exposure useful to commercial decisions",roles:[{title:"Commercial head",copy:"See package commitments, actuals, forecasts and margin pressure before closeout."},{title:"Quantity surveyor",copy:"Keep BOQ revisions, measured quantities and cost codes in controlled context."},{title:"Project director",copy:"Relate cost variance to progress, procurement and accountable work packages."},{title:"Finance team",copy:"Trace project reports to the approved transaction or expense behind each value."}],loisHeading:"Ask Lois to explain cost records, not invent forecasts",lois:[{ask:"Why is the civil package above budget?",checks:"Budget allocations, approved orders, bills and expenses",prepares:"A variance breakdown with linked source records",review:"Commercial owners assess causes and corrective action"},{ask:"Show commitments not yet billed.",checks:"Approved purchase orders, work orders and recorded invoices",prepares:"An open-commitment list by package",review:"Finance confirms accounting treatment and status"},{ask:"Summarise cost exposure for this project.",checks:"Permitted BOQ, budget, commitment, actual and progress data",prepares:"A review draft identifying exceptions",review:"The project director approves assumptions and interpretation"}],lifecycleFocus:["BOQ and budget","purchase orders","expenses and subcontract work"],related:[{slug:"project-management",label:"Project management"},{slug:"procure-to-pay",label:"Procure-to-pay"},{slug:"subcontractor-management",label:"Subcontractor management"}],assuranceHeading:"Keep your cost structure and approval limits",assuranceCopy:"Implementation maps current BOQ structures, cost codes, budget ownership and approval paths before transactions move. Configurable fields and role-based access support control without turning every change into uncontrolled custom development.",faqs:[{question:"What is EPC BOQ and project cost control software?",answer:"It connects BOQ scope, approved budgets, purchase and subcontract commitments, actual project costs and forecasts by project and work package."},{question:"How are BOQ value and budget different?",answer:"BOQ value represents priced contractual scope or an estimate basis. Budget is the internally approved amount available for controlled spending against that scope."},{question:"What is the difference between committed and actual cost?",answer:"Committed cost is covered by an approved order or contract but may not yet be billed. Actual cost is expenditure recorded through accepted invoices, bills or expenses under the configured accounting process."},{question:"Can users trace a variance to its source?",answer:"Where connected records are available, authorised users can move from a package variance to relevant purchase orders, subcontract bills, invoices or expenses."},{question:"Does the system calculate the final forecast without judgement?",answer:"No. Available records can support forecast reviews, but authorised commercial and project professionals remain responsible for assumptions, estimate-to-complete and margin judgement."},{question:"Can our existing cost codes and approval limits be configured?",answer:"Yes. Cost dimensions, fields, roles, validations and approval paths can be mapped during implementation, subject to the agreed design."}],finalHeading:"Review one live project cost structure in Supista",finalCopy:"Bring a BOQ, budget and current cost report. Weâll show how commitments, actuals and source records can be controlled without losing your package structure."},"procure-to-pay":{slug:"procure-to-pay",seoTitle:"EPC Procurement and Procure-to-Pay Software | Supista",meta:"Control EPC purchase requirements, PRs, RFQs, quotations, POs, GRNs, invoices and payments with complete project, budget and material context.",eyebrow:"EPC procurement management software",h1:"Control every project purchase from requirement to payment",hero:"Built for procurement leaders, project teams and commercial approvers. Carry project, BOQ, budget, work-package and required-at-site context through sourcing, receipt, invoice and payment.",definition:"EPC procurement management software controls project buying from purchase requirement and purchase requisition (PR) through request for quotation (RFQ), quotation comparison, purchase order (PO), goods receipt note (GRN), invoice and payment. Each step retains the project need, approval status, vendor and material-delivery context.",problemHeading:"Where EPC purchases lose time and control",problems:[{title:"Requirements arrive incomplete",copy:"A site request lacks specifications, quantity, budget context or required-at-site date. Procurement spends critical days clarifying a need that should be purchase-ready."}
1,{title:"Comparisons lack one basis",copy:"Quotes arrive through email and messaging with different taxes, freight, delivery terms and exclusions. Approvers cannot see whether evaluated costs are comparable."},{title:"Order status stops at PO",copy:"The purchase order is issued, but dispatch, receipt, invoice and payment status live in separate registers. Site teams chase material without a reliable answer."}],connectionHeading:"Keep the requirement attached to every transaction",connectionIntro:"A purchase should never become a detached finance document. Project, BOQ, budget, work package, material, required-at-site date and vendor context follow it from demand through payment.",connections:["Purchase requirement","PR and approval","RFQ","Vendor quotation","Commercial comparison","PO","GRN and receipt","Invoice and payment"],capabilities:[{title:"Project requirements",copy:"Record what the project needs, where and by when. Reduce avoidable clarification before procurement can begin.",icon:"file"},{title:"Controlled PRs",copy:"Prepare PRs with project, BOQ, budget and work-package context. Route them through configured roles and approval limits.",icon:"shield"},{title:"RFQ management",copy:"Issue and track RFQs against a defined requirement. Keep invited vendors and response status visible to buyers.",icon:"cart"},{title:"Quotation records",copy:"Capture comparable commercial fields and supporting documents. Preserve what each vendor offered without relying on inbox searches.",icon:"users"},{title:"Commercial comparison",copy:"Compare evaluated price, taxes, freight, delivery and configured terms. Flag missing information for professional review.",icon:"chart"},{title:"PO control",copy:"Create approved purchase orders and retain amendment context. Prevent unapproved changes from becoming an informal buying commitment.",icon:"invoice"},{title:"Receipt to payment",copy:"Connect PO quantities with GRNs, invoices and payment status. Give project and finance teams one traceable transaction chain.",icon:"link"}],visual:u("/assets/img/screenshots/epc/procurement-flow.svg","EPC procurement workflow graphic from project requirement through PR, RFQ, PO, GRN, invoice and payment","One controlled chain from need to payment","Each procurement record passes approved project, commercial and delivery context to the next team.",["Required-at-site date starts the clock","Quotation terms stay comparable","GRN links receipt to invoice control"]),workflowHeading:"Run the complete project procurement workflow",workflow:[{title:"Define the requirement",trigger:"Project need or material plan",role:"Site or project engineer",record:"Purchase requirement",control:"Specification and need-date completeness",handoff:"Purchase requisition"},{title:"Approve the PR",trigger:"Complete requirement",role:"Project and commercial approvers",record:"Approved PR",control:"Budget, authority and scope checks",handoff:"RFQ sourcing"},{title:"Source and compare",trigger:"Approved PR",role:"Procurement manager",record:"RFQ, quotations and comparison",control:"Comparable terms and approval",handoff:"Purchase order"},{title:"Order and receive",trigger:"Approved vendor selection",role:"Buyer and store manager",record:"PO, dispatch context and GRN",control:"Order and receipt validation",handoff:"Invoice review"},{title:"Invoice and pay",trigger:"Vendor invoice",role:"Finance team",record:"Invoice and payment status",control:"Configured matching and approval",handoff:"Actual project cost"}],roleHeading:"Give every buying stakeholder reliable status",roles:[{title:"Procurement manager",copy:"Control PR queues, sourcing, comparisons, orders and supplier follow-up."},{title:"Project manager",copy:"See whether critical material will reach site before planned execution."},{title:"Store manager",copy:"Receive ordered material and record quantities against the correct PO."},{title:"Finance team",copy:"Review invoice and payment context against approved orders and receipts."}],loisHeading:"Use Lois to prepare procurement work with review built in",lois:[{ask:"Prepare a PR for 500 metres of cable for Site B.",checks:"User access, project, material, quantity, cost context and required date",prepares:"A purchase-requisition preview and missing-field questions",review:"The user confirms; configured PR approval follows"},{ask:"Record these three vendor quotations.",checks:"RFQ, vendors, supplied quote documents and required commercial fields",prepares:"Structured quotation drafts with flagged gaps",review:"The buyer verifies captured terms before saving"},{ask:"Compare the quotations for evaluated cost and delivery.",checks:"Permitted quotation values, taxes, freight, lead times and terms",prepares:"A comparison using available captured data",review:"Procurement and approvers make the selection decision"}],lifecycleFocus:["purchase requirements","vendor sourcing","purchase orders","material receipt"],related:[{slug:"boq-budget-cost-control",label:"BOQ and cost control"},{slug:"vendor-management",label:"Vendor management"},{slug:"inventory-material-management",label:"Material management"}],assuranceHeading:"Map procurement controls before moving transactions",assuranceCopy:"Configure requisition fields, approval limits, quotation parameters, purchase-order controls and receipt workflows around the companyâs operating policy. Roles and traceable records remain in place when Lois assists users.",faqs:[{question:"What is EPC procurement management software?",answer:"It manages project purchases from requirement and PR through RFQ, quotation comparison, PO, GRN, invoice and payment while retaining project and budget context."},{question:"Can a PR be linked to project and BOQ context?",answer:"Yes. Supported configurations can retain the project, work package, BOQ or c
1ost context, material details and required-at-site date on the requisition workflow."},{question:"Can Supista compare vendor quotations?",answer:"Yes. It can compare captured commercial fields such as price, taxes, freight, delivery and configured terms. Missing or unclear details remain subject to buyer review."},{question:"Does Supista approve vendors or purchases automatically?",answer:"No automatic commercial decision is implied. Authorised users evaluate vendors and purchases, and configured validations, permissions and approval paths remain in force."},{question:"How do receipts connect with invoices?",answer:"PO and GRN records can provide ordered and received quantity context for invoice review, subject to the organisationâs configured matching and finance controls."},{question:"Can Lois prepare procurement records?",answer:"For supported workflows, Lois can ask for missing information and prepare PR, quotation or comparison drafts. The user reviews them and normal approvals continue."}],finalHeading:"See how your current procurement workflow can run in Supista",finalCopy:"Bring one active requirement, comparison format or delayed material case. Weâll map the same handoffs from project need through receipt and payment."},"client-billing-approvals":{slug:"client-billing-approvals",seoTitle:"EPC Client Billing and Approval Software | Supista",meta:"Connect completed EPC work, measurements, supporting documents, approvals, invoices, due dates and collections to reduce unbilled project work.",eyebrow:"EPC client billing software",h1:"Convert completed project work into approved bills faster",hero:"Built for quantity surveyors, commercial managers and project directors. Connect billable quantities and milestones with measurement references, documents, approvals, invoices and collections without treating software records as engineering certification.",definition:"EPC client billing software connects completed quantities or milestones with measurement references, supporting documents, approval status, invoice submission, due dates and collections. It helps commercial teams identify billable and unbilled work, while authorised engineers, clients and commercial reviewers remain responsible for measurements and certification.",problemHeading:"Why completed work remains unbilled",problems:[{title:"Evidence arrives after completion",copy:"Site work is reported complete, but measurements, photographs or supporting documents are not assembled. Commercial teams cannot prepare a defensible bill pack."},{title:"Approval ownership is unclear",copy:"A running account bill or milestone submission moves through email with no current owner. Follow-up begins only when cash planning is affected."},{title:"Collections lose project context",copy:"Invoices and due dates sit in finance records while project teams track certification separately. Leaders cannot distinguish unbilled work from billed-but-uncollected value."}],connectionHeading:"Carry approved progress into billing and collection",connectionIntro:"The billing record links the agreed BOQ or milestone with completed work, measurement references, documents and reviewer status. Once authorised, the invoice and collection position remain visible beside the project.",connections:["BOQ or milestone","Completed work","Measurement reference","Supporting documents","Approval status","Invoice submission","Due date","Collection"],capabilities:[{title:"Billable work",copy:"Compare available completed quantities or milestones with the billing plan. Show commercial teams where a billing review should begin.",icon:"eye"},{title:"Measurement context",copy:"Attach or reference measurements behind claimed work. Keep professional verification with authorised project and client teams.",icon:"file"},{title:"Document readiness",copy:"Track the supporting documents required for a submission. Prevent an avoidable missing attachment from holding the entire bill.",icon:"check"},{title:"RA bill records",copy:"Where configured, organise running account bill periods, prior values and current claims. Preserve the agreed commercial structure across submissions.",icon:"invoice"}
1,{title:"Approval status",copy:"Show who holds the next review and what remains pending. Give project leaders a practical follow-up list.",icon:"users"},{title:"Unbilled visibility",copy:"Separate completed-but-unbilled work from submitted, approved and invoiced value. Improve cash-flow discussions with traceable status.",icon:"chart"},{title:"Collections view",copy:"Retain invoice dates, due dates and collection status in project context. Help commercial and finance teams coordinate follow-up.",icon:"wallet"}],visual:u("/assets/img/screenshots/epc/cost-control.svg","EPC client billing workflow graphic showing completed work, measurement support, approval, invoice and collection","From completed work to collected value","The billing workflow makes readiness, certification status and cash follow-up visible without automating professional approval.",["Completed work starts the review","Evidence supports the submission","Approval and collection remain distinct"]),workflowHeading:"Move a billing item through controlled review",workflow:[{title:"Identify billable work",trigger:"Reported quantity or achieved milestone",role:"Quantity surveyor",record:"Billing candidate",control:"Contract and progress review",handoff:"Measurement and document pack"},{title:"Assemble evidence",trigger:"Candidate accepted for preparation",role:"Site and commercial teams",record:"Measurements and supporting documents",control:"Completeness check",handoff:"Bill draft"},{title:"Review the bill",trigger:"Complete draft",role:"Commercial manager",record:"RA bill or milestone claim",control:"Internal approval",handoff:"Client submission"},{title:"Track certification",trigger:"Submitted bill",role:"Project commercial team",record:"Client review and approval status",control:"Authorised certification",handoff:"Invoice"},{title:"Invoice and collect",trigger:"Approved amount",role:"Finance team",record:"Invoice, due date and receipt",control:"Finance validation",handoff:"Project cash and analytics"}],roleHeading:"Turn site progress into commercial follow-through",roles:[{title:"Quantity surveyor",copy:"Relate quantities, measurements and prior claims to the current bill period."},{title:"Commercial manager",copy:"See unbilled work, missing evidence, pending approvals and deductions."},{title:"Project director",copy:"Review billing readiness and collection exposure alongside project progress."},{title:"Finance team",copy:"Follow approved invoices, due dates and collections with project context."}],loisHeading:"Ask Lois to organise available billing evidence",lois:[{ask:"What completed work may be billable this week?",checks:"Permitted progress, BOQ, milestone and prior-billing records",prepares:"A candidate list with available evidence and gaps",review:"The quantity surveyor validates measurement and eligibility"},{ask:"Which bill packs are waiting for documents?",checks:"Draft bills, required-document fields and attachment status",prepares:"A missing-document follow-up list",review:"Commercial owners confirm what the contract requires"},{ask:"Summarise overdue client approvals and invoices.",checks:"Submission, approval, invoice, due-date and collection records",prepares:"A status summary with responsible owners",review:"Commercial and finance teams verify follow-up actions"}],lifecycleFocus:["site execution","client billing","analytics"],related:[{slug:"daily-project-report",label:"Daily Project Reports"},{slug:"subcontractor-management",label:"Subcontractor management"},{slug:"analytics",label:"Project analytics"}],assuranceHeading:"Keep certification and financial controls with authorised people",assuranceCopy:"Supista can configure billing fields, supporting-document requirements, role access and approval paths. The system records workflow status; it does not independently certify engineering quantities or replace contract administration judgement.",faqs:[{question:"What is EPC client billing software?",answer:"It connects completed quantities or milestones with measurement references, supporting documents, approvals, invoices, due dates and collections for c
1ontrolled project billing."},{question:"Can it show completed but unbilled work?",answer:"Where progress and billing records share project context, authorised teams can identify work reported complete that has not yet moved into a bill or approved invoice."},{question:"Does Supista certify engineering measurements?",answer:"No. Authorised engineers, quantity surveyors, clients and commercial reviewers remain responsible for measurement, certification and contractual approval."},{question:"Can running account bills be managed?",answer:"Running account bill periods, previous values, current claims and supporting records can be configured where that workflow is included in the agreed implementation."},{question:"Can teams track approval and collection separately?",answer:"Yes. Submission, certification, invoice and collection are separate states, helping teams distinguish operational billing delays from overdue receivables."},{question:"How can Lois help with client billing?",answer:"Lois can find available billable-work records, identify missing information and prepare summaries. Users review its output and all permissions and approvals remain in place."}],finalHeading:"See how completed work can reach billing sooner",finalCopy:"Bring one active BOQ, billing format or pending bill pack. Weâll show how measurements, documents, approvals, invoices and collections can stay connected."},"vendor-management":{slug:"vendor-management",seoTitle:"Vendor Management Software for EPC and Construction",meta:"Manage EPC vendor onboarding, qualification, compliance documents, expiry dates, categories, RFQ history, orders, deliveries and open issues.",eyebrow:"EPC vendor management software",h1:"Choose and manage vendors using complete project history",hero:"Built for procurement managers and commercial approvers. Maintain governed vendor master records, documents and categories, then review sourcing, order and delivery history without confusing vendor data with procurement transactions.",definition:"EPC vendor management software maintains the governed vendor master: identity, categories, qualification fields, compliance documents, expiry dates and role-restricted records. It connects that master with RFQs, quotations, purchase orders, pending deliveries and recorded performance inputs, while each procurement transaction remains a separate controlled record.",problemHeading:"Why a vendor name is not enough for a buying decision",problems:[{title:"Qualification is scattered",copy:"Registrations, tax records and technical documents sit in folders or inboxes. Buyers cannot quickly confirm what is current, missing or expired."},{title:"History disappears between projects",copy:"A new package starts with a fresh spreadsheet. Teams overlook previous quotations, late deliveries or unresolved issues already recorded elsewhere."},{title:"Access is too broad",copy:"Sensitive bank, commercial or compliance information is shared outside the roles that need it. Governance weakens even when buying steps are approved."}],connectionHeading:"Separate vendor governance from each purchase",connectionIntro:"The vendor master supplies approved identity, category and document context. RFQs, quotations, orders, receipts and issues then build transaction history without changing the underlying master informally.",connections:["Vendor master","Category","Qualification field","Compliance document","RFQ history","Quotation history","PO history","Delivery and issue record"],capabilities:[{title:"Vendor onboarding",copy:"Capture defined identity, contact and registration details. Give master-data owners a consistent record to review.",icon:"users"},{title:"Qualification fields",copy:"Configure commercial or technical information required by category. Keep qualification decisions with authorised reviewers.",icon:"check"},{title:"Document validity",copy:"Record document references and expiry dates where required. Make missing or expiring records visible for follow-up.",icon:"file"},{title:"Vendor categories",copy:"Organise vendors by supplied material, service or project need. Help buyers find relevant records without treating category as automatic approval.",icon:"box"},{title:"Sourcing history",copy:"View RFQ invitations, captured quotations and comparison context. Understand prior participation before starting the next event.",icon:"cart"},{title:"Order history",copy:"Review purchase-order and pending-delivery context linked to the vendor. Give follow-up conversations an evidence base.",icon:"invoice"},{title:"Restricted records",copy:"Apply role permissions to sensitive vendor information and actions. Prevent convenience from overriding data governance.",icon:"shield"}],visual:u("/assets/img/screenshots/epc/partner-control.svg","EPC vend
1or management workflow graphic with qualification documents, RFQs, purchase orders and delivery issues","A governed vendor record with transactional history","Master data stays controlled while sourcing and delivery records provide context for authorised decisions.",["Qualifications belong to the master","Transactions build project history","Permissions limit sensitive access"]),workflowHeading:"Govern the vendor record throughout procurement",workflow:[{title:"Register the vendor",trigger:"Onboarding request",role:"Vendor master owner",record:"Draft vendor profile",control:"Required-field validation",handoff:"Qualification review"},{title:"Review qualification",trigger:"Submitted information",role:"Authorised technical or commercial reviewer",record:"Qualification status",control:"Human assessment",handoff:"Approved category access"},{title:"Maintain documents",trigger:"New or expiring document",role:"Vendor coordinator",record:"Document and validity status",control:"Configured review",handoff:"Buying visibility"},{title:"Build history",trigger:"RFQ, quotation, PO or receipt",role:"Procurement and stores",record:"Linked transaction history",control:"Transaction approvals",handoff:"Vendor review"},{title:"Review issues",trigger:"Delivery or performance input",role:"Procurement manager",record:"Issue and follow-up",control:"Evidence and responsible review",handoff:"Future sourcing context"}],roleHeading:"Use vendor history where it changes the decision",roles:[{title:"Procurement manager",copy:"Review qualifications, open deliveries and prior sourcing context before inviting vendors."},{title:"Commercial approver",copy:"See controlled vendor and quotation evidence behind a proposed award."},{title:"Store manager",copy:"Relate delivery issues and pending quantities to the correct vendor and PO."},{title:"Vendor master owner",copy:"Control duplicates, documents, categories and access to sensitive fields."}],loisHeading:"Ask Lois about authorised vendor records",lois:[{ask:"Show electrical vendors with current required documents.",checks:"Permitted vendor categories, qualification and document-validity fields",prepares:"A filtered record list with visible gaps",review:"The buyer confirms suitability for the specific RFQ"},{ask:"Which vendors have open deliveries for Site B?",checks:"Purchase orders, receipt records and pending quantities",prepares:"A vendor follow-up list by order",review:"Procurement verifies current delivery commitments"},{ask:"Summarise this vendorâs recorded project history.",checks:"Accessible RFQs, quotations, orders, receipts and logged issues",prepares:"A source-linked history summary",review:"Authorised reviewers apply professional judgement"}],lifecycleFocus:["vendor sourcing","purchase orders","material receipt"],related:[{slug:"procure-to-pay",label:"Procure-to-pay"},{slug:"inventory-material-management",label:"Material management"},{slug:"analytics",label:"Project analytics"}],assuranceHeading:"Protect master data while keeping it useful",assuranceCopy:"Configure vendor fields, categories, document requirements and role permissions around the approved onboarding policy. ISO/IEC 27001-certified controls support information security; commercial qualification remains an authorised business decision.",faqs:[{question:"What is EPC vendor management software?",answer:"It maintains vendor master, qualification, category and document records and connects them with authorised procurement and delivery history."},{question:"How is vendor management different from procurement?",answer:"Vendor management governs who the vendor is and what master information is approved. Procurement records each RFQ, quotation, order, receipt, invoice and approval separately."},{question:"Can document expiry dates be tracked?",answer:"Document references, required fields and validity dates can be configured so authorised teams can identify missing or expiring records."},{question:"Does recorded history automatically qualify a vendor?",answer:"No. History informs authorised reviewers. Technical suitability, commercial evaluation and approval remain professional and organisational decisions."},{question:"Can sensitive vendor records be restricted?",answer:"Yes. Role-based permissions can control which users see or change vendor information and which actions they may perform."},{question:"Does Lois search public sources for vendors?",answer:"No public-vendor discovery is claimed. Lois works with permitted Supista records and does not bypass configured validations, permissions or approvals."}],finalHeading:"Review one vendor category and its buying history",finalCopy:"Bring your onboarding checklist, category structure or current vendor register. Weâll show how master governance and procurement history can work together."},"subcontractor-management":{slug:"subcontractor-management",seoTitle:"Subcontractor Management Software for EPC Projects",meta:"Control EPC subcontract work orders, scope limits, measured progress, advances, deductions, retention, bills, reconciliation and liabilities.",eyebrow:"Construction subcontractor management software",h1:"Control subcontract scope, progress, measurements and bills",hero:"Built for project commercial teams, quantity surveyors and project managers. Connect the subcontract work order with measured progress, prior payments, deductions and retention before establishing the payable amount.",definition:"Construction subcontractor management software links onboarding, work orders, scope and quantity limits, progress records, measurement references, advances, deductions, retention, bills and reconciliation. It helps authorised commercial teams establish liabilities from recorded evidence; it does not independently measure, certify or approve completed work.",problemHeading:"Where subcontract liability becomes unclear",problems:[{title:"Scope changes informally",copy:"Site instructions extend work beyond the work order, but quantity and rate limits are not updated. The dispute appears when the subcontractor submits a bill."},{title:"Progress and bills diverge",copy:"Measurements sit with site teams while prior bills sit with finance. Reviewers cannot see what was certified, paid or carried forward."},{title:"Recoveries are missed",copy:"Advances, material recovery, deductions and retention live in separate registers. The payable amount is overstated or takes days to reconcile."}],connectionHeading:"Keep scope, measurement and payment in one chain",connectionIntro:"The subcontract record ties the work order to the project package. Progress and measurement references support the current bill, while prior payments, recoveries and retention explain the net payable and outstanding liability.",connections:["Subcontractor master","Work order","Scope and quantity limit","Measured progress","Previous payments","Advance recovery","Deductions and retention","Net payable"],capabilities:[{title:"Work-order scope",copy:"Record package scope, quantities, rates and configured limits. Give reviewers a controlled basis for bill assessment.",icon:"file"},{title:"Progress records",copy:"Connect reported work with the relevant project and package. Avoid billing against progress held only in a site spreadsheet.",icon:"building"},{title:"Measurement context",copy:"Reference the measurements and evidence used by authorised certifiers. Preserve professional judgement and approval.",icon:"check"},{title:"Advances",copy:"Track recorded advances and their recovery status. Prevent outstanding amounts from disappearing between b
1ill periods.",icon:"wallet"},{title:"Deductions",copy:"Apply configured recovery and deduction records with visible reasons. Make the net position explainable to commercial reviewers.",icon:"chart"},{title:"Retention",copy:"Calculate or record retention under configured commercial terms. Keep retained value distinct from current payment and released amounts.",icon:"shield"},{title:"Liability view",copy:"Reconcile certified value, prior payments and current payable amounts. Give finance a traceable project liability.",icon:"eye"}],visual:u("/assets/img/screenshots/epc/partner-control.svg","EPC subcontractor billing workflow graphic showing work order, measured progress, advances, deductions and retention","Explain the current subcontract payable","For example, a certified value of 100 less 20 previously paid, 10 advance recovery, 5 deductions and 5 retention leaves 60 payable, subject to authorised review.",["Start with certified progress","Subtract prior payments and recoveries","Retain the approval trail"]),workflowHeading:"Move from work order to reconciled liability",workflow:[{title:"Approve the work order",trigger:"Awarded subcontract package",role:"Commercial manager",record:"Work order and scope limits",control:"Commercial approval",handoff:"Site execution"},{title:"Record progress",trigger:"Completed site work",role:"Site engineer",record:"Progress and measurement reference",control:"Technical review",handoff:"Bill preparation"},{title:"Prepare the bill",trigger:"Reviewed measurement",role:"Quantity surveyor",record:"Subcontract bill",control:"Scope, rate and quantity checks",handoff:"Recovery calculation"},{title:"Apply recoveries",trigger:"Bill under review",role:"Commercial team",record:"Advances, deductions and retention",control:"Contract-term validation",handoff:"Net payable"},{title:"Approve and reconcile",trigger:"Complete bill assessment",role:"Authorised approver and finance",record:"Approved liability and payment status",control:"Approval matrix",handoff:"Project actual cost"}],roleHeading:"Give site, commercial and finance one liability view",roles:[{title:"Quantity surveyor",copy:"Compare measured quantities with work-order limits and prior certified values."},{title:"Commercial manager",copy:"Review rates, advances, deductions, retention and outstanding obligations."},{title:"Project manager",copy:"See package progress and unresolved subcontract issues affecting delivery."},{title:"Finance team",copy:"Pay approved net liability with traceable recoveries and project allocation."}],loisHeading:"Ask Lois to prepare a subcontract review",lois:[{ask:"Compare this bill with measured progress and work-order limits.",checks:"Permitted work order, progress, measurements and current bill",prepares:"An exception list and calculation context",review:"The quantity surveyor validates measurement and entitlement"},{ask:"Show unrecovered subcontract advances.",checks:"Advance, prior bill and recovery records",prepares:"An outstanding-recovery list by subcontract",review:"Commercial and finance confirm balances"},{ask:"Explain the proposed payable amount.",checks:"Certified value, previous payments, deductions and retention",prepares:"A transparent reconciliation draft",review:"Authorised approvers confirm the bill"}],lifecycleFocus:["site execution","expenses and subcontract work","client billing"],related:[{slug:"project-management",label:"Project management"},{slug:"boq-budget-cost-control",label:"BOQ and cost control"},{slug:"client-billing-approvals",label:"Client billing"}],assuranceHeading:"Configure commercial terms without automating certification",assuranceCopy:"Work-order fields, measurement references, recovery types, retention rules and approvals can reflect the agreed process. Authorised professionals remain responsible for scope interpretation, measured progress, entitlement and certification.",faqs:[{question:"What is construction subcontractor management software?",answer:"It connects subcontract scope, progress, measurements, advances, deductions, retention, bills, payments and outstanding liability in project context."},{question:"Can bills be checked against work-order limits?",answer:"Where scope, rate and quantity records are configured, authorised users can compare a bill with those limits and review exceptions."},{question:"How is the net payable amount established?",answer:"The reviewed value is reconciled with prior payments, applicable advance recovery, deductions and retention under configured terms, then routed for authorised approval."},{question:"Does Supista certify subcontractor measurements?",answer:"No. Engineers, quantity surveyors and authorised commercial reviewers remain responsible for measurement, entitlement and certification."},{question:"Can outstanding advances and retention be viewed?",answer:"Yes. Available advance, recovery, retention and release records can be shown by subcontract and project to authorised users."},{question:"Can Lois approve a subcontract bill?",answer:"No. Lois may prepare a comparison or reconciliation from permitted records, but configured validations, permissions and approval workflows remain in control."}],finalHeading:"See one subcontract bill reconciled in project context",finalCopy:"Bring a work order, measurement format or sample bill. Weâll show how scope, recoveries, retention and payable value can remain traceable."},"inventory-material-management":{slug:"inventory-material-management",seoTitle:"Construction Material and Inventory Management Software",meta:"Track EPC materials from PO-linked receipt and GRN through location stock, transfers, issues, consumption, returns and project reconciliation.",eyebrow:"Construction material inventory management software",h1:"Track project materials from receipt to site consumption",hero:"Built for store managers, project managers and procurement teams. Maintain stock by warehouse and site, then connect receipts, transfers, issues, consumption and returns to project and BOQ context.",definition:"Construction material inventory management software tracks materials across warehouses and site stores. Purchased quantity is ordered; received quantity is accepted through a goods receipt note (GRN); available quantity remains in stock; issued quantity leaves the store; consumed quantity is recorded against work; returned quantity comes back for reuse or reconciliation.",problemHeading:"Why system stock and site reality diverge",problems:[{title:"Receipt is treated as availability",copy:"A PO shows material purchased, but part remains in transit or at another location. Site planning assumes stock that cannot support todayâs work."},{title:"Issues lack work context",copy:"Stores record material leav
1ing, but not the activity, package or responsible team. Excess consumption cannot be explained against planned quantities."},{title:"Transfers disappear",copy:"One site sends surplus to another through calls and paper notes. Both locations report unreliable balances and procurement may buy again."}],connectionHeading:"Preserve quantity meaning across every movement",connectionIntro:"Each movement retains the material, project, location and source document. Teams can distinguish ordered, received, available, issued, consumed and returned quantities instead of using one ambiguous stock figure.",connections:["Material request","Purchase order","GRN","Warehouse stock","Site-store stock","Transfer","Issue and consumption","Return and reconciliation"],capabilities:[{title:"Location stock",copy:"View recorded balances by warehouse, project or site store. Prevent central stock from being mistaken for site-ready material.",icon:"box"},{title:"PO-linked receipts",copy:"Record receipts against the authorised purchase order and material. Retain ordered-versus-received quantity context.",icon:"cart"},{title:"Controlled GRNs",copy:"Create a GRN with receipt details and configured checks. Pass accepted quantity into the right stock location.",icon:"file"},{title:"Inter-site transfers",copy:"Track dispatch and receipt between controlled locations. Keep the sending and receiving balances accountable.",icon:"link"},{title:"Issues and returns",copy:"Record material issued to work and returned to store. Reduce unexplained movement in reconciliation.",icon:"check"},{title:"Consumption context",copy:"Relate supported consumption records to project, BOQ or activity context. Help project teams review excess or shortage signals.",icon:"chart"},{title:"Shortage visibility",copy:"Compare available stock, planned need and pending receipts. Give procurement a clearer replenishment priority.",icon:"alert"}],visual:u("/assets/img/screenshots/epc/material-control.svg","Construction material flow graphic from purchase order and GRN to store, transfer, issue, consumption and return","Follow each material quantity through the site","Ordered, received, available, issued, consumed and returned quantities answer different operational questions.",["PO quantity is not site stock","Every transfer changes two locations","Consumption needs project context"]),workflowHeading:"Move material through controlled locations",workflow:[{title:"Request material",trigger:"Planned activity or site need",role:"Site engineer",record:"Material request",control:"Project and requirement review",handoff:"Procurement or stock allocation"},{title:"Receive against PO",trigger:"Vendor delivery",role:"Store manager",record:"GRN and accepted quantity",control:"Order and receipt checks",handoff:"Available location stock"},{title:"Transfer if needed",trigger:"Approved inter-site demand",role:"Sending and receiving stores",record:"Transfer dispatch and receipt",control:"Location confirmation",handoff:"Receiving-site availability"},{title:"Issue to work",trigger:"Authorised site request",role:"Store keeper",record:"Material issue",control:"Quantity and responsibility check",handoff:"Site use"},{title:"Consume or return",trigger:"Work completion or unused material",role:"Site team",record:"Consumption, return and reconciliation",control:"Project review",handoff:"Cost and material analytics"}],roleHeading:"Give stores and project teams the same material position",roles:[{title:"Store manager",copy:"Control receipts, location balances, transfers, issues and returns."},{title:"Project manager",copy:"See material readiness and consumption exceptions against upcoming work."},{title:"Procurement manager",copy:"Prioritise orders using shortages, pending receipts and required-at-site dates."},{title:"Commercial team",copy:"Relate material movement and consumption to project and BOQ context."}],loisHeading:"Ask Lois what material records show",lois:[{ask:"Do we have enough cable for next weekâs work?",checks:"Permitted stock, planned demand, open transfers and pending receipts",prepares:"A readiness summary with quantity gaps",review:"Stores and project teams verify physical and planning assumptions"},{ask:"Prepare a transfer request from Central Store to Site B.",checks:"User access, location stock, material, quantity and project need",prepares:"A transfer-request preview",review:"The user confirms and configured approval continues"},{ask:"Show material issues above recorded consumption.",checks:"Issue, consumption and return records by project context",prepares:"A reconciliation exception list",review:"Site and commercial owners investigate the cause"}],lifecycleFocus:["purchase orders","material receipt","site execution"],related:[{slug:"procure-to-pay",label:"Procure-to-pay"},{slug:"planning-scheduling",label:"Planning and scheduling"},{slug:"daily-project-report",label:"Daily Project Reports"}],assuranceHeading:"Configure locations, units and material controls first",assuranceCopy:"Implementation maps warehouses, site stores, materials, units, document types and responsible roles. Mobile-friendly access and configurable workflows support site use, while physical verification remains an operational responsibility.",faqs:[{question:"What is construction material inventory management software?",answer:"It tracks material requests, PO-linked receipts, GRNs, location stock, transfers, issues, consumption, returns and reconciliation across EPC projects."},{question:"How do purchased and received quantities differ?",answer:"Purchased quantity is covered by a purchase order. Received quantity is material recorded as delivered and accepted through the configured receipt process."},{question:"How do issued and consumed quantities differ?",answer:"Issued quantity has left the store for a responsible workfront. Consumed quantity is recorded as used against work;
1 unused material may remain at site or return to store."},{question:"Can stock be viewed by warehouse or project?",answer:"Yes. Authorised users can view recorded balances and movements by configured warehouse, site store and project context."},{question:"Can inter-site transfers be controlled?",answer:"Yes. Supported transfers can record dispatch from one location and receipt at another with responsible roles and configured approvals."},{question:"Can Lois confirm physical stock?",answer:"No. Lois can summarise permitted inventory records and prepare supported requests, but teams must verify physical stock and normal controls still apply."}],finalHeading:"Trace one critical material from order to consumption",finalCopy:"Bring a material register, store structure or current shortage. Weâll show how receipts, transfers, issues and reconciliation can stay project-linked."},"planning-scheduling":{slug:"planning-scheduling",seoTitle:"EPC Project Planning and Scheduling Software | Supista",meta:"Connect EPC WBS activities and milestones with owners, site progress, materials, approvals, subcontract dependencies, delay reasons and actions.",eyebrow:"EPC project planning and scheduling software",h1:"Connect the project schedule with live site dependencies",hero:"Built for planning engineers, project managers and project directors. Relate the WBS baseline to current progress, materials, approvals, subcontract dependencies and corrective actions while retaining professional scheduling judgement.",definition:"EPC project planning and scheduling software connects the work breakdown structure (WBS), activities, milestones, owners and dependencies with live execution records. It helps teams compare planned and actual progress and expose material, approval or subcontract constraints; specialist planning logic and forecasts remain the plannerâs responsibility.",problemHeading:"A valid schedule can still describe an unready site",problems:[{title:"Dependencies live outside the plan",copy:"Material, drawing and client approvals sit in separate trackers. An activity reaches its planned start date without a workable front."},{title:"Progress has no consistent basis",copy:"Teams report percentages through calls and presentations without activity-level quantities or evidence. Planned-versus-actual views become difficult to trust."},{title:"Delay reasons are not assigned",copy:"Slippage is visible, but the cause, responsible owner and recovery action are absent. The same blocker returns in the next review."}],connectionHeading:"Connect schedule dates with execution readiness",connectionIntro:"Activities retain their owners and dependencies while current records show whether materials, approvals, subcontractors and site progress support the plan. The result is an operating view besideânot a substitute forâthe specialist schedule.",connections:["WBS","Activity","Milestone","Owner","Logical dependency","Material dependency","Approval dependency","Delay and action"],capabilities:[{title:"WBS planning",copy:"Structure activities under controlled project and work-package context. Keep reporting aligned to how delivery responsibility is organised.",icon:"building"},{title:"Dates and owners",copy:"Record planned start, finish and accountable roles. Make late handoffs and unowned work visible.",icon:"calendar"},{title:"Dependencies",copy:"Relate predecessor work and configured operational dependencies. Explain why a workfront is not ready beyond a date alone.",icon:"link"},{title:"Progress updates",copy:"Connect approved activity updates with quantities, DPRs or supporting records. Improve the basis for planned-versus-actual review.",icon:"chart"},{title:"Delay reasons",copy:"Record the stated reason, impact and responsible follow-up. Preserve context for later management and claim review.",icon:"alert"},{title:"Corrective actions",copy:"Assign actions and target dates against identified constraints. Keep recovery work visible until resolved.",icon:"check"},{title:"Schedule-risk views",copy:"Bring delayed activities and missing readiness records into focused views. Let planners investigate before updating forecasts.",icon:"eye"}],visual:u("/assets/img/screenshots/epc/planned-vs-actual.png","Supista project dashboard comparing planned and actual project activity progress","Review planned and actual progress with context","The dashboard highlights variance; planners still validate logic, causes and forecast impact using professional judgement.",["Baseline dates anchor comparison","Actual updates need evidence","Depen
1dencies explain readiness"],1792,878),workflowHeading:"Turn the baseline into an operating control",workflow:[{title:"Structure the WBS",trigger:"Approved project controls plan",role:"Planning engineer",record:"WBS and activities",control:"Project baseline review",handoff:"Dates and dependencies"},{title:"Set the baseline",trigger:"Defined activities",role:"Planner and project manager",record:"Milestones, dates, owners and logic",control:"Authorised baseline approval",handoff:"Execution plan"},{title:"Connect readiness",trigger:"Upcoming activities",role:"Project coordination team",record:"Material, approval and subcontract dependencies",control:"Readiness review",handoff:"Workfront release"},{title:"Update progress",trigger:"Site execution",role:"Site engineer",record:"Actual progress and evidence",control:"Progress review",handoff:"Variance view"},{title:"Respond to variance",trigger:"Delay or blocked dependency",role:"Planner and project manager",record:"Reason and corrective action",control:"Professional schedule review",handoff:"Revised forecast or action plan"}],roleHeading:"Give planners evidence and owners a clear next action",roles:[{title:"Planning engineer",copy:"Review activity progress, dependencies, delay reasons and available execution evidence."},{title:"Project manager",copy:"See which near-term milestones lack material, approval or subcontract readiness."},{title:"Site engineer",copy:"Update actual work against the correct activity and report blockers."},{title:"Project director",copy:"Focus reviews on schedule exposure, accountable owners and recovery actions."}],loisHeading:"Ask Lois to surface schedule context",lois:[{ask:"Which activities could delay next monthâs milestones?",checks:"Permitted activities, dates, dependencies, progress and blockers",prepares:"An at-risk list with available reasons",review:"The planning engineer validates logic and forecast impact"},{ask:"Show activities waiting for materials or approvals.",checks:"Upcoming activities and linked readiness records",prepares:"A dependency follow-up list",review:"Responsible owners confirm current status"},{ask:"Draft the weekly schedule-risk summary.",checks:"Variance, delay-reason and corrective-action records",prepares:"A management summary linked to sources",review:"The project manager reviews conclusions"}],lifecycleFocus:["project plan","material receipt","site execution"],related:[{slug:"project-management",label:"Project management"},{slug:"inventory-material-management",label:"Material management"},{slug:"daily-project-report",label:"Daily Project Reports"}],assuranceHeading:"Support the planner without replacing planning judgement",assuranceCopy:"Supista connects schedule context with project records and configurable reviews. Specialist scheduling tools, baseline governance, critical-path interpretation and recovery forecasts remain with qualified project professionals.",faqs:[{question:"What is EPC project planning and scheduling software?",answer:"It connects WBS activities, milestones, owners and dependencies with progress and operational readiness records for planned-versus-actual control."},{question:"Does Supista replace specialist scheduling software?",answer:"No. It provides connected operational context. Detailed scheduling logic, critical-path analysis and professional forecasts remain with the projectâs planning approach and qualified users."},{question:"Can activities show material and approval dependencies?",answer:"Yes. Supported configurations can relate upcoming activities to available material, purchase, approval and subcontract readiness records."},{question:"Can actual progress be linked to DPRs?",answer:"Where configured, activity progress can reference Daily Project Report entries, quantities and evidence so reviewers can inspect the reporting basis."},{question:"Can delay reasons and corrective actions be tracked?",answer:"Yes. Teams can record delay context, responsible owners, target dates and follow-up actions within the project workflow."},{question:"How does Lois assess schedule risk?",answer:"Lois summarises permitted dates, progress and dependency records. A planner must review the result; Lois does not bypass controls or make professional scheduling decisions."}],finalHeading:"See your near-term schedule with live dependencies",finalCopy:"Bring a WBS, milestone plan or delayed workfront. Weâll show how progress, materials, approvals and accountable actions can sit beside the schedule."},"daily-project-report":{slug:"daily-project-report",seoTitle:"Construction Daily Project Report Software | Supista",meta:"Capture structured construction DPRs with work quantities, manpower, equipment, material use, weather, delays, photo evidence and review status.",eyebrow:"Construction Daily Project Report software",h1:"Capture complete site progress with a structured DPR",hero:"Built for site engineers, project managers and planning teams. Record the dayâs work, resources, material, conditions, blockers and evidence in a consistent mobile-friendly Daily Project Report (DPR).",definition:"Construction Daily Project Report software captures structured site facts for each reporting day: completed work, planned and actual quantities, manpower, equipment, material use, weather, delays, photographs, documents and review status. It creates consistent progress evidence for project reporting without inventing missing site information.",problemHeading:"Why daily reporting fails to support project control",problems:[{title:"Updates arrive in fragments",copy:"Quantities are in a spreadsheet, photographs are in messaging groups and manpower comes by phone. The project manager cannot review one complete daily record."},{title:"Progress lacks a basis",copy:"A team reports an activity complete without planned quantity, actual quantity or measurement context. Planning cannot use the update confidently."},{title:"Blockers disappear overnight",copy:"Weather, access, drawing or material delays are mentioned informally. No owner or review status carries the issue into tomorrowâs action list."}],connectionHeading:"Turn the site day into reusable project evidence",connectionIntro:"A DPR links its date and location with activities, quantities, manpower, equipment, material use, weather, delays and attachments. Reviewed facts then support planning, cost, material and management reporting.",connections:["Project and date","Activity","Planned quantity","Actual quantity","Manpower and equipment","Material use","Delay and blocker","Photo and document"],capabilities:[{title:"Mobile reporting",copy:"Give authorised site users a practical form for field entry. Reduce dependence on end-of-week spreadsheet compilation.",icon:"mobile"},{title:"Work quantities",copy:"Record planned and actual quantities against relevant work. Give progress reviewers a clearer reporting basis.",icon:"chart"},{title:"Resource records",copy:"Capture manpower and equipment deployed during the shift. Relate resource context to achieved work.",icon:"users"},{title:"Material use",copy:"Record supported material-use information in the project day. Help reconcile site reporting with store and cost records.",icon:"box"},{title:"Conditions and delays",copy:"Capture weather, access constraints and delay reasons. Preserve facts that may matter in later reviews.",icon:"alert"},{title:"Photos and documents",copy:"Attach evidence to the relevant DPR instead of an unsearchable message thread. Improve traceability for authorised reviewers.",icon:"file"},{title:"Review status",copy:"Route the report through the configured review process. Show missing days and pending DPRs in consolidated reporting.",icon:"check"}],visual:u("/assets/img/screenshots/epc/dpr-expense.svg","Structured construction Daily Project Report layout with work, quantities, manpower, equipment, weather and blockers","What a useful DPR records","A complete daily record answers what happened, what resources were used, what blocked progress and what evidence supports the update.",["Activity: cable tray installation","Plan 280 m \xb7 actual 240 m","18 people \xb7 4 equipment \xb7 permit delay"]),workflowHeading:"Capture, review and reuse the site day",workflow:[{title:"Open the reporting day",trigger:"End of shift or configured reporting time",role:"Site engineer",record:"Draft DPR",control:"Project, date and location validation",handoff:"Work and resource entry"},{title:"Record work",trigger:"Activities performed",role:"Site team",record:"Quantities and progress details",control:"Required-field checks",handoff:"Resource and material context"},{title:"Add conditions",trigger:"Site observations",role:"Site engineer",record:"Manpower, equipment, material, weather and delays",control:"Completeness review",handoff:"Evidence"},{title:"Attach evidence",trigger:"Supporting photos or documents",role:"Authorised reporter",record:"DPR attachments",control:"File and access controls",handoff:"Reviewer"},{title:"Review and consolidate",trigger:"Submitted DPR",role:"Project manager",record:"Reviewed DPR and action items",control:"Configured approval",handoff:"Progress, planning and analytics"}],roleHeading:"Make the DPR useful beyond the site",roles:[{title:"Site engineer",copy:"Submit one structured record for work, resources, conditions and evidence."},{title:"Project manager",copy:"Review daily variance, blockers and accountable actions without chasing updates."},{title:"Planning engineer",copy:"Use reviewed quantity and delay records when assessing actual progress."},{title:"Commercial manager",copy:"Access supporting site context for cost, subcontract and billing reviews."}],loisHeading:"Let Lois guide the DPR draft",lois:[{ask:"Start todayâs DPR for Site B.",checks:"User access, project, reporting date and configured required fields",prepares:"A structured draft and questions for missing facts",review:"The site user confirms every reported fact"},{ask:"Add 240 metres completed and 18 technicians.",checks:"Draft DPR, activity, unit and resource fields",prepares:"Updated entries in the preview",review:"The reporter validates quantities and allocation"},{ask:"Summarise this weekâs site blockers.",checks:"Permitted reviewed DPRs and blocker records",prepares:"A source-linked trend summary",review:"The project manager confirms causes and actions"}],lifecycleFocus:["project plan","site execution","analytics"],related:[{slug:"planning-scheduling",label:"Planning and scheduling"},{slug:"inventory-material-management",label:"Material management"},{slug:"project-expense-monitor",label:"Site expenses"}],assuranceHeading:"Configure the DPR around your site controls",assuranceCopy:"Fields, units, required evidence, review roles and reporting schedules can reflect the agreed project process. Mobile access helps capture facts close to the work; authorised teams remain responsible for accuracy and approval.",faqs:[{question:"What is construction Daily Project Report software?",answer:"It captures structured daily site records for work, quantities, manpower, equipment, material, weather, delays, evidence and review status."},{question:"What information should a DPR include?",answer:"A useful DPR includes the project and date, activities, planned and actual quantities, resources, material use, site conditions, blockers, remarks and supporting evidence."},{question:"Can DPRs be submitted from mobile devices?",answer:"Mobile-friendly workflows can support authorised site reporting, subject to the configured forms, permissions and available connectivity."},{question:"Can DPR progress update the project view?",answer:"Where configured and reviewed, DPR activity and quantity records can provide current progress context for project and planning views."},{question:"Can missing reporting days be identified?",answer:"Yes. Consolidated views can compare expected reporting with available DPR records and show missing or pending reports."},{question:"Will Lois fill in unknown site facts?",answer:"No. Lois can ask for missing information and prepare a draft from supplied and permitted data. The site user reviews it and normal validations and approvals apply."}],finalHeading:"See your current DPR become a controlled site record",finalCopy:"Bring a daily report format or recent site update. Weâll show how work, resources, blockers and evidence can feed the wider project workflow."},"project-expense-monitor":{slug:"project-expense-monitor",seoTitle:"Construction Site Expense Management Software",meta:"Capture construction petty cash, fuel, transport, site purchases and advances with receipts, cost heads, approvals and project-budget reporting.",eyebrow:"Construction site expense management software",h1:"Record and control project expenses before month-end",hero:"Built for site teams, project managers and finance. Capture petty cash, fuel, transport, equipment and urgent site purchases with receipts, advances, cost allocation and configured approval.",definition:"Construction site expense management software records field expenses and employee or site advances against the correct project and cost head. It c
1aptures receipts, routes claims through configured approvals, tracks settlements and exceptions, and passes approved values into project-cost reporting before month-end reconciliation.",problemHeading:"Small site costs create large reporting gaps",problems:[{title:"Receipts arrive late",copy:"Fuel, transport and urgent purchases stay in wallets or chat messages. Finance learns the project cost weeks after cash was spent."},{title:"Allocation is guessed",copy:"A receipt has an amount but no project, work package or cost head. Accounts must chase the site or post the cost to a broad bucket."},{title:"Advances remain open",copy:"New cash is issued while prior advances lack supporting expenses or returns. The true employee and site balance becomes unclear."}],connectionHeading:"Move each expense from evidence to project cost",connectionIntro:"The expense record connects the spender, receipt, project, cost head and advance. Approval establishes whether it can enter the controlled cost view; rejected or incomplete claims remain visible as exceptions.",connections:["Mobile capture","Receipt","Employee or site","Project","Cost head","Advance","Approval","Project cost report"],capabilities:[{title:"Field capture",copy:"Record expenses close to when they happen from a mobile-friendly workflow. Reduce month-end memory and document gaps.",icon:"mobile"},{title:"Receipt evidence",copy:"Attach the available receipt or supporting document. Keep the evidence beside the claim for review.",icon:"file"},{title:"Cost allocation",copy:"Assign project and configured cost-head context. Improve the usefulness of approved expenses in project reporting.",icon:"building"},{title:"Advance tracking",copy:"Relate claims and returned balances to the relevant advance. Give employees, sites and finance a common settlement position.",icon:"wallet"},{title:"Approval routing",copy:"Apply role, limit and exception controls before posting approved cost. Prevent assisted capture from becoming automatic approval.",icon:"shield"},{title:"Exception review",copy:"Show missing evidence, duplicate-looking details or incomplete allocation for user review. Keep judgement with authorised approvers.",icon:"alert"},{title:"Budget reporting",copy:"Bring approved site expenses into project and cost-head analysis. Show spend earlier than a month-end spreadsheet.",icon:"chart"}],visual:u("/assets/img/screenshots/epc/dpr-expense.svg","Construction site expense workflow from mobile receipt capture to project allocation, approval and cost reporting","From a site receipt to controlled project cost","A captured receipt becomes a project cost only after required context, user confirmation and configured approval.",["Capture amount and evidence","Allocate project and cost head","Approve, settle and report"]),workflowHeading:"Control an expense before it reaches reporting",workflow:[{title:"Capture the spend",trigger:"Petty cash, fuel, transport or site purchase",role:"Employee or site user",record:"Draft expense and receipt",control:"Required evidence",handoff:"Allocation"},{title:"Add cost context",trigger:"Draft claim",role:"Claimant",record:"Project, cost head and advance reference",control:"Field validation",handoff:"Manager review"},{title:"Review the claim",trigger:"Complete submission",role:"Project manager",record:"Reviewed expense",control:"Purpose and limit checks",handoff:"Finance approval"},{title:"Approve or return",trigger:"Manager-reviewed claim",role:"Finance team",record:"Approved, rejected or returned status",control:"Configured approval workflow",handoff:"Settlement"},{title:"Settle and report",trigger:"Approved expense",role:"Finance team",record:"Advance settlement and project cost",control:"Financial posting controls",handoff:"Budget and analytics"}],roleHeading:"Give site and finance one expense trail",roles:[{title:"Site engineer",copy:"Capture supported costs before receipts and purpose are forgotten."},{title:"Project manager",copy:"Review necessity, project allocation and exceptions while context is current."},{title:"Finance team",copy:"Control evidence, approvals, advance settlement and reporting status."},{title:"Commercial head",copy:"See approved site expenses against package or cost-head budgets."}],loisHeading:"Ask Lois to prepare, not approve, an expense",lois:[{ask:"Record this diesel receipt for Site B.",checks:"Supplied receipt, user permission and configured expense fields",prepares:"An expense draft and questions for project or cost head",review:"The claimant verifies extracted details"},{ask:"Show my unsettled advances.",checks:"Permitted advance, claim and settlement records",prepares:"An outstanding-balance list",review:"The employee and finance confirm settlement action"},{ask:"Which site expenses are waiting for approval?",checks:"Submitted expense status and responsible approval roles",prepares:"A pending queue with visible exceptions",review:"Authorised approvers decide each claim"}],lifecycleFocus:["site execution","expenses and subcontract work","analytics"],related:[{slug:"daily-project-report",label:"Daily Project Reports"},{slug:"boq-budget-cost-control",label:"BOQ and cost control"},{slug:"analytics",label:"Project analytics"}],assuranceHeading:"Keep expense limits and financial approval in place",assuranceCopy:"Configure expense types, required fields, cost heads, advance references and approval limits around policy. Lois can assist capture from supplied information, but claimants and approvers remain accountable.",faqs:[{question:"What is construction site expense management software?",answer:"It records site expenses, receipts, project and cost-head allocation, advances, approvals, settlements and approved cost reporting."},{question:"Which expenses can be recorded?",answer:"Configured categories may include petty cash, fuel, transport, equipment running costs and urgent site purchases, according to the organisationâs policy."},{question:"Can advances be reconciled with expense claims?",answer:"Yes. Supported records can relate expenses and returned balances to an employee or site advance and show outstanding settlement status."},{question:"Does mobile capture automatically approve a cost?",answer:"No. Capture creates or prepares a record. Required evidence, permissions, validations and configured managerial or finance approval still apply."},{question:"When does an expense enter project-cost reporting?",answer:"That depends on the configured finance process. Approved expense status can feed project and cost-head reporting while posting controls remain with finance."},{question:"Can Lois read a receipt?",answer:"Where enabled, Lois can extract supplied receipt details and ask for missing context. The user must verify the draft and configured approvals continue."}],finalHeading:"See a site expense reach project cost with control",finalCopy:"Bring an expense form, advance process or sample receipt. Weâll show the path from mobile capture through approval, settlement and reporting."},analytics:{slug:"analytics",seoTitle:"EPC Project Analytics and Management Dashboards",meta:"Review EPC portfolio health, schedule and cost variance, procurement, materials, DPRs, blockers, billing and collections with source drill-down.",eyebrow:"EPC project analytics and dashboards",h1:"See project risks, delays and cost exposure in one review",hero:"Built for CEOs, project directors and functional leaders. Compare portfolio and project health, then drill from a schedule, cost, procurement, material or billing signal to the permitted source record.",definition:"EPC project analytics and dashboards combine approved operational records into role-based portfolio and project views. Leaders can review schedule variance, budget and cost exposure, procurement status, material availability, missing DPRs, blockers, billing and collections, then trace an exception to its source instead of relying on disconnected presentations.",problemHeading:"Why management reviews spend more time collecting than deciding",problems:[{title:"Every function brings a version",copy:"Planning, procurement, site and finance use different cut-off dates and structures. The meeting debates numbers before reaching the project issue."},{title:"Portfolio averages hide exposure",copy:"Overall progress appears acceptable while one work package lacks material or exceeds budget. Leaders need exceptions, not another high-level percentage."},{title:"Charts stop at the signal",copy:"A red KPI cannot open the delayed PO, missing DPR or unpaid invoice behind it. Teams leave the review with more reconciliation work."}],connectionHeading:"Use one project context across every dashboard",connectionIntro:"Analytics becomes actionable when WBS, cost, purchase, material, DPR, blocker and billing records retain shared project dimensions. Role views can then answer different questions while drawing from governed source records.",connections:["Portfolio","Project health","Schedule variance","Cost variance","Procurement status","Material readiness","DPR and blockers","Billing and collection"],capabilities:[{title:"Portfolio overview",copy:"Compare active projects using consistent configured measures. Direct executive attention to material exceptions rather than report preparation.",icon:"building"},{title:"Schedule variance",copy:"Review baseline and actual progress signals with delay context. Open the affected project or activity for investigation.",icon:"calendar"},{title:"Cost exposure",copy:"Compare budget, commitments and recorded actuals by project or package. Trace variance to available source transactions.",icon:"wallet"},{title:"Procurement status",copy:"See requisitions, sourcing, orders and pending delivery positions. Identify purchases threatening required-at-site dates.",icon:"cart"},{title:"Material readiness",copy:"Relate location stock and pending receipts to current project demand. Surface shortages requiring operational confirmation.",icon:"box"},{title:"Reporting discipline",copy:"Show missing DPRs, open blockers and pending actions. Make data gaps visible instead of hiding them in the dashboard.",icon:"alert"},{title:"Custom reports",copy:"Configure dimensions, filters and role views for the agreed review process. Preserve permission controls on underlying records.",icon:"chart"}],visual:u("/assets/img/screenshots/epc/analytics-builder.png","Supista analytics workspace with configurable EPC project charts, filters and role-based dashboard access","Build the review around the decision","Role dashboards present relevant exceptions and preserve drill-down to the permitted records behind each measure.",["Portfolio filters focus the review","Charts expose schedule and cost variance","Source access follows user permissions"],1917,1078),workflowHeading:"Move from governed records to accountable action",workflow:[{title:"Define the review",trigger:"Management question or review cadence",role:"Process owner",record:"Measures, filters and role view",control:"Definition and access approval",handoff:"Dashboard configuration"},{title:"Collect source status",trigger:"Approved operational records",role:"System workflows",record:"Current project measures",control:"Record permissions and status",handoff:"Portfolio view"},{title:"Identify exceptions",trigger:"Variance or missing record",role:"Functional leader",record:"Exception list",control:"Threshold and context review",handoff:"Source drill-down"},{title:"Investigate the source",trigger:"Selected exception",role:"Responsible manager",record:"Underlying activity, order, cost or bill",control:"Role-based access",handoff:"Corrective action"},{title:"Track the response",trigger:"Confirmed issue",role:"Project director",record:"Owner and action",control:"Management follow-up",handoff:"Next review cycle"}],roleHeading:"Answer the question each leader owns",roles:[{title:"CEO or managing director",copy:"Compare project health, cash exposure and the exceptions requiring executive intervention."},{title:"Project manager",copy:"Review schedule, blockers, DPR compliance and material readiness for one project."},{title:"Commercial and finance",copy:"Track budget exposure, billing readiness, due invoices and collections."},{title:"Procurement manager",copy:"See sourcing queues, pending orders, late receipts and vendor follow-up."}],loisHeading:"Ask Lois to move from dashboard signal to source context",lois:[{ask:"Show the five largest risks across active projects.",checks:"Permitted schedule, cost, procurement, blocker and billing records",prepares:"A prioritised summary with source links",review:"Leaders validate materiality and action"},{ask:"Why did Project B move to amber?",checks:"Current configured measures and contributing records",prepares:"An explanation based on available data",review:"The project owner confirms causes"},{ask:"Prepare tomorrowâs portfolio review.",checks:"Role-permitted exceptions, actions and reporting gaps",prepares:"A concise agenda and follow-up draft",review:"The meeting owner approves the review pack"}],lifecycleFocus:["BOQ and budget","site execution","client billing","analytics"],related:[{slug:"project-management",label:"Project management"},{slug:"boq-budget-cost-control",label:"BOQ and cost control"},{slug:"client-billing-approvals",label:"Client billing"}],assuranceHeading:"Build dashboards from governed operational definitions",assuranceCopy:"Configure measures, dimensions, filters and access with process owners before rollout. Dashboards display available records and should expose data gaps; they do not convert incomplete inputs into verified business facts.",faqs:[{question:"What are EPC project analytics and dashboards?",answer:"They combine project, schedule, cost, procurement, material, site-reporting and billing records into role-based views with source drill-down."},{question:"What should a CEO see?",answer:"A CEO view should focus on portfolio health, major schedule and cost exposure, cash position and issues needing executive intervention rather than operational detail."},{question:"Can users drill into the source record?",answer:"Where the source is connected and the user has permission, dashboard exceptions can link to the relevant activity, transaction, material record, DPR or bill."},{question:"Can different teams have different dashboards?",answer:"Yes. Configurable role views can present the measures and filters relevant to project, procurement, commercial, finance and executive responsibilities."},{question:"Are dashboard figures professional forecasts?",answer:"Not automatically. Dashboards show available records and configured calculations. Qualified users remain responsible for forecast assumptions and management interpretation."},{question:"Can Lois answer questions about dashboards?",answer:"Lois can summarise permitted records and explain available context. Users must review the answer, and permissions, validations and approvals remain in place."}],finalHeading:"Build the next project review around live source records",finalCopy:"Bring your current management report or review agenda. Weâll show how each exception can connect to an owner and the record behind it."},"lois-ai":{slug:"lois-ai",seoTitle:"AI ERP for EPC and Construction Companies | Lois AI",meta:"Use Lois AI to find permitted EPC records, prepare PRs, capture quotations, draft DPRs and supported expenses with preview and human approval.",eyebrow:"AI ERP for EPC and construction",h1:"Ask AI to complete everyday EPC ERP work",hero:"Built for EPC teams who need answers and actions without navigating every screen. Lois uses permitted ERP context, asks for missing information and prepares a preview before the normal workflow continues.",definition:"AI
1ERP for EPC and construction combines a conversational interface with governed project records and workflows. Lois can retrieve permitted information, prepare supported ERP records and summarise operational risks. It requests missing facts, shows a preview for human confirmation and never bypasses configured permissions, validations or approvals.",problemHeading:"Why ERP work remains incomplete even when the system exists",problems:[{title:"Users cannot find the right path",copy:"A site user knows the required outcome but not the correct module, form or field. The update waits for an experienced ERP operator."},{title:"Questions require manual joins",copy:"A project manager must open activities, orders, receipts and approvals to explain one delay. The answer is slow and difficult to reproduce."},{title:"Automation creates control anxiety",copy:"Leaders worry that AI may invent values, expose restricted records or submit transactions without review. Adoption stalls unless the control flow is explicit."}],connectionHeading:"Use conversation as a governed ERP interface",connectionIntro:"The control flow is simple: ask, understand context, request missing information, prepare a preview, obtain user confirmation, then continue through the configured workflow and approval. Access is limited to the userâs permitted Supista data.",connections:["Ask","Understand context","Request missing facts","Prepare preview","User confirms","Validate","Route for approval","Retain traceability"],capabilities:[{title:"ERP questions",copy:"Ask about projects, activities, materials, costs or bills within current permissions. Receive an answer grounded in available Supista records.",icon:"spark"},{title:"Guided PR drafts",copy:"Describe a project requirement in plain language. Lois asks for missing fields and prepares a requisition preview.",icon:"cart"},{title:"Quotation capture",copy:"Use supplied quotation information to prepare structured records. Buyers verify values and terms before saving.",icon:"file"},{title:"Comparison drafts",copy:"Compare captured commercial fields using available data. Leave vendor selection and professional evaluation to authorised users.",icon:"chart"},{title:"DPR assistance",copy:"Guide a site user through required daily-report fields. Never invent missing quantities, conditions or events.",icon:"mobile"},{title:"Expense capture",copy:"Read a supplied receipt and request missing project context. Prepare the claim for confirmation and normal approval.",icon:"wallet"},{title:"Permission enforcement",copy:"Respect the userâs roles and record access throughout the conversation. Keep validation and approval steps in the workflow.",icon:"shield"}],visual:u("/assets/img/screenshots/epc/lois-workflow.svg","Lois AI governed ERP workflow from user request to context check, preview, confirmation and approval","An operational assistant inside the ERP","Lois can prepare supported work, but the user sees the proposed record before configured controls and approvals continue.",["Context comes from permitted ERP data","Missing information becomes a question","Human confirmation precedes workflow submission"]),workflowHeading:"From plain-language request to controlled ERP action",workflow:[{title:"Ask",trigger:"User describes an outcome or question",role:"Authorised ERP user",record:"Conversation request",control:"Identity and permission context",handoff:"Intent and record lookup"},{title:"Understand context",trigger:"Recognised supported task",role:"Lois",record:"Relevant permitted context",control:"Access boundaries",handoff:"Completeness check"},{title:"Request missing facts",trigger:"Required information is absent",role:"Lois and user",record:"Supplied task details",control:"Configured required fields",handoff:"Draft preparation"},{title:"Preview",trigger:"Complete supported input",role:"Lois",record:"Answer, comparison or draft record",control:"Validation checks",handoff:"Human review"},{title:"Confirm and continue",trigger:"User confirmation",role:"Authorised user and approvers",record:"Submitted workflow record",control:"Permissions and approval matrix",handoff:"Traceable ERP workflow"}],roleHeading:"Reduce navigation without reducing accountability",roles:[{title:"Project manager",copy:"Ask for delayed work, material blockers and concise project-risk summaries."},{title:"Procurement manager",copy:"Prepare PRs, capture supplied quotes and compare recorded commercial terms."},{title:"Site engineer",copy:"Draft DPRs and supported expenses through guided questions."},{title:"Commercial leader",copy:"Find cost exposure and billable-work context across permitted project records."}],loisHeading:"Practical Lois requests across the EPC day",lois:[{ask:"Prepare a PR for 500 metres of 4-core cable.",checks:"Project, material, quantity, required date, cost context and access",prepares:"A PR preview with unresolved fields highlighted",review:"The user confirms; the approval matrix continues"},{ask:"Find completed work that may be ready to bill.",checks:"Permitted progress, BOQ, milestone and billing records",prepares:"A candidate list with evidence gaps",review:"Commercial professionals validate eligibility"},{ask:"Draft todayâs DPR from these site facts.",checks:"Project, activity, quantities, resources, conditions and attachments",prepares:"A structured DPR draft",review:"The site reporter confirms accuracy before submission"}],lifecycleFocus:["project plan","purchase requirements","site execution","analytics"],related:[{slug:"project-management",label:"Project management"},{slug:"procure-to-pay",label:"Procure-to-pay"},{slug:"daily-project-report",label:"Daily Project Reports"}],assuranceHeading:"Keep AI inside enterprise controls",assuranceCopy:"Lois works with permitted Supista data and does not bypass configured validations, permissions or approvals. Customer prompts and outputs are not used to train foundation models, and Supista states that enterprise models are accessed through Microsoft Foundry.",faqs:[{question:"What is AI ERP for EPC and construction?",answer:"It combines governed EPC records and workflows with conversational retrieval and supported record preparation, while keeping permissions, validation and human approval."},{question:"Is Lois a generic chatbot?",answer:"No. Lois is positioned as an operational interface to permitted Supista ERP data and supported workflows, not an open-ended public chatbot."},{question:"Can Lois create records without confirmation?",answer:"Important supported actions follow a preview and user confirmation, then continue through configured validation and approval. Lois does not bypass those controls."},{question:"Can Lois make engineering or commercial decisions?",answer:"No. Lois can organise available information and prepare supported drafts. Qualified and authorised people retain responsibility for engineering, planning, vendor, cost and certification decisions."},{question:"What happens when information is missing?",answer:"Lois asks the user for required facts or flags the gap. It should not invent a project quantity, commercial term or site event."},{question:"Can Lois access every company record?",answer:"No. Lois works within the authenticated userâs permitted Supista data and role access."},{question:"Is customer data used to train foundation models?",answer:"Supista states that customer prompts and outputs are not used to train foundation models and that Lois uses enterprise models through Microsoft Foundry."}],finalHeading:"Test Lois against a real EPC task",finalCopy:"Bring one purchase request, reporting task or management question. Weâll show what Lois can prepare, what it asks, and where human review remains mandatory."},"custom-epc-erp":{slug:"custom-epc-erp",seoTitle:"Customisable EPC ERP and Construction Management Software",meta:"Configure EPC ERP modules, forms, fields, record relationships, terminology, roles, approvals, validations, notifications, dashboards and reports.",eyebrow:"Customisable EPC ERP software",h1:"Adapt the ERP to your projects, controls and terminology",hero:"Built for EPC owners, process leaders and implementation teams. Configure modules, forms, fields, relationships, roles and approvals around the governed operating model instead of maintaining uncontrolled code forks.",definition:"Customisable EPC ERP software lets an organisation configure modules, forms, fields, terminology, record relationships, roles, permissions, approval paths, validations, notifications, dashboards and reports. Configuration changes governed product behaviour through managed tools; uncontrolled custom development creates separate code that is harder to maintain and audit.",problemHeading:"Why rigid ERP and uncontrolled custom code both fail",problems:[{title:"Users work around the ERP",copy:"Required EPC fields, terms or approvals are missing, so teams recreate the real process in spreadsheets. System records become incomplete."},{title:"Every exception becomes code",copy:"Small form or routing changes require development and deployment. The process cannot adapt at the pace of active projects."},{title:"Customisation loses governance",copy:"Fields and workflows are added without ownership, validation or access review. Different c
1ompanies and projects use conflicting definitions."}],connectionHeading:"Configure the record model and its controls together",connectionIntro:"A useful configuration defines the module, fields and relationships alongside roles, validation, approval, notification and reporting. This keeps project terminology flexible while preserving a governed source of truth.",connections:["Module","Form and field","Record relationship","Company terminology","Role and permission","Approval path","Validation and notification","Dashboard and report"],capabilities:[{title:"Configurable modules",copy:"Shape supported modules around the agreed project process. Avoid forcing every team into unrelated generic records.",icon:"settings"},{title:"Forms and fields",copy:"Add controlled fields, labels and required information. Keep definitions owned and documented during implementation.",icon:"file"},{title:"Record relationships",copy:"Connect project, BOQ, activity, material, vendor and transaction records. Preserve context across team handoffs.",icon:"link"},{title:"Company terminology",copy:"Use familiar names for approved process concepts. Improve adoption without changing the underlying governance informally.",icon:"users"},{title:"Roles and permissions",copy:"Define who may view, create, change or approve records. Keep sensitive commercial and project data restricted.",icon:"shield"},{title:"Approval and validation",copy:"Configure routing, required fields and business checks. Make changes through controlled design rather than hidden workarounds.",icon:"check"},{title:"Dashboards and reports",copy:"Build role-focused views from configured records and dimensions. Let each function review the information it owns.",icon:"chart"},{title:"Adaptable workflows",copy:"Revise approved configuration as the operating model changes. Retain governance over who requests, tests and releases each change.",icon:"bolt"}],visual:u("/assets/img/screenshots/epc/custom-workflow.svg","Configurable EPC ERP workflow graphic showing custom fields, validation, role permissions and approval routing","Configuration with governance built in","Process owners define what changes, authorised implementers configure it, and users receive tested forms, controls and reports.",["Relationships preserve project context","Permissions control each action","Approved changes remain maintainable"]),workflowHeading:"Move a process change through managed configuration",workflow:[{title:"Map the process",trigger:"Implementation or approved change request",role:"Process owner",record:"Current and target workflow",control:"Scope and ownership review",handoff:"Configuration design"},{title:"Design the model",trigger:"Approved process map",role:"Implementation team",record:"Modules, fields and relationships",control:"Data-definition review",handoff:"Control design"},{title:"Set governance",trigger:"Configured record model",role:"Process and security owners",record:"Roles, validations and approvals",control:"Access and authority review",handoff:"Testing"},{title:"Test the workflow",trigger:"Configured environment",role:"Business users",record:"Test cases and accepted results",control:"User acceptance",handoff:"Controlled rollout"},{title:"Adapt responsibly",trigger:"Future approved process change",role:"Configuration owner",record:"Versioned change",control:"Impact review and approval",handoff:"Updated forms, dashboards and training"}],roleHeading:"Let process owners shape the ERP without losing control",roles:[{title:"Business owner",copy:"Approve which project and commercial outcomes the configuration must support."},{title:"Process leader",copy:"Define forms, terminology, validations and handoffs used by the team."},{title:"System administrator",copy:"Manage approved roles, fields, workflows and reporting configuration."},{title:"End user",copy:"Work with familiar project terms and only the actions relevant to the role."}],loisHeading:"Use Lois within the configured operating model",lois:[{ask:"Which fields are required before this PR can move?",checks:"Permitted form configuration and current record",prepares:"A missing-field explanation",review:"The user supplies accurate information"},{ask:"Prepare this supported record using our project terminology.",checks:"User role, configured module, fields and relationships",prepares:"A preview using the approved form",review:"The user confirms; validations and approvals continue"},{ask:"Show records waiting at this approval step.",checks:"Permitted workflow status and responsible roles",prepares:"A governed work queue",review:"Authorised users take the configured action"}],lifecycleFocus:["BOQ and budget","project plan","purchase requirements","analytics"],related:[{slug:"project-management",label:"Project management"},{slug:"lois-ai",label:"Lois AI"},{slug:"analytics",label:"Project analytics"}],assuranceHeading:"Differentiate managed configuration from a code fork",assuranceCopy:"No-code and low-code configuration uses supported controls for forms, relationships, roles and workflows. Requirements outside verified product capability should be confirmed during solution design rather than published or promised as available functionality.",faqs:[{question:"What is customisable EPC ERP software?",answer:"It lets organisations configure supported modules, fields, relationships, terminology, roles, approvals, validations, dashboards and reports around their governed EPC process."},{question:"How is configuration different from custom development?",answer:"Configuration changes supported product behaviour through managed controls. Custom development creates or changes code and requires separate design, testing, maintenance and product-team confirmation."},{question:"Can we keep our terminology and forms?",answer:"Company terminology, supported forms and fields can be mapped during solution design, subject to the agreed configuration and product capability."},{question:"Can approval paths and permissions be configured?",answer:"Yes. Roles, permissions, required fields and approval routing are supported configuration areas and should be tested against the organisationâs authority matrix."},{question:"Does configurability remove governance?",answer:"No. Process owners should approve definitions, access, validations and releases. Configuration should encode governance rather than let every user alter controls."}
1,{question:"Can multi-company processes be configured?",answer:"Multi-company requirements should be confirmed against the proposed design and supported deployment before commitment; terminology, roles and reporting boundaries may differ."},{question:"Will future process changes require a new ERP?",answer:"Many supported form, field, role and workflow changes can be handled through configuration. Requirements beyond current capability need product-team assessment."}],finalHeading:"Map one of your EPC workflows into Supista",finalCopy:"Bring a form, approval matrix or process map. Weâll separate supported configuration from requirements that need product-team confirmation before commitment."}},h=e=>m[e];var g=r(31918),v=r.n(g);let f=[{key:"BOQ and budget",label:"BOQ & budget",slug:"boq-budget-cost-control"},{key:"project plan",label:"Project plan",slug:"planning-scheduling"},{key:"purchase requirements",label:"Purchase requirements",slug:"procure-to-pay"},{key:"vendor sourcing",label:"Vendor sourcing",slug:"vendor-management"},{key:"purchase orders",label:"Purchase orders",slug:"procure-to-pay"},{key:"material receipt",label:"Material receipt",slug:"inventory-material-management"},{key:"site execution",label:"Site execution",slug:"daily-project-report"},{key:"expenses and subcontract work",label:"Expenses & subcontract work",slug:"subcontractor-management"},{key:"client billing",label:"Client billing",slug:"client-billing-approvals"},{key:"analytics",label:"Analytics",slug:"analytics"}];function w(e){let{feature:t}=e,r=h(t.slug);if(!r)return null;let a="https://supista.com".concat(p.Vd,"/features/").concat(r.slug),i={"@context":"https://schema.org","@type":"FAQPage",mainEntity:r.faqs.map(e=>({"@type":"Question",name:e.question,acceptedAnswer:{"@type":"Answer",text:e.answer}}))},u={"@context":"https://schema.org","@type":"BreadcrumbList",itemListElement:[{"@type":"ListItem",position:1,name:"Supista EPC ERP",item:"https://supista.com".concat(p.Vd)},{"@type":"ListItem",position:2,name:"Features",item:"https://supista.com".concat(p.Vd,"#features")},{"@type":"ListItem",position:3,name:r.eyebrow,item:a}]},m={"@context":"https://schema.org","@type":"SoftwareApplication",name:"".concat(r.eyebrow," | Supista"),applicationCategory:"BusinessApplication",operatingSystem:"Web",description:r.meta,url:a,featureList:r.capabilities.map(e=>e.title),isPartOf:{"@type":"SoftwareApplication",name:"Supista EPC ERP",url:"https://supista.com".concat(p.Vd)}};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsxs)(c.Z,{title:r.seoTitle,description:r.meta,canonical:a,children:[(0,o.jsx)("script",{type:"application/ld+json",dangerouslySetInnerHTML:{__html:JSON.stringify(m)}}),(0,o.jsx)("script",{type:"application/ld+json",dangerouslySetInnerHTML:{__html:JSON.stringify(u)}}),(0,o.jsx)("script",{type:"application/ld+json",dangerouslySetInnerHTML:{__html:JSON.stringify(i)}})]}),(0,o.jsxs)("main",{className:v().page,children:[(0,o.jsx)("section",{className:v().featureHero,children:(0,o.jsxs)("div",{className:"".concat(v().container," ").concat(v().featureHeroGrid),children:[(0,o.jsxs)("div",{children:[(0,o.jsxs)("nav",{className:v().breadcrumbs,"aria-label":"Breadcrumb",children:[(0,o.jsx)(s(),{href:p.Vd,children:"Supista EPC ERP"}),(0,o.jsx)("span",{children:"â"}),(0,o.jsx)(s(),{href:"".concat(p.Vd,"#features"),children:"Features"}),(0,o.jsx)("span",{children:"â"}),(0,o.jsx)("span",{children:t.eyebrow})]}),(0,o.jsx)("p",{className:v().eyebrow,children:r.eyebrow}),(0,o.jsx)("h1",{children:r.h1}),(0,o.jsx)("p",{className:v().lead,children:r.hero}),(0,o.jsxs)("div",{className:v().actions,children:[(0,o.jsx)(l.Z,{eventName:"epc_feature_demo",className:v().primary,children:"Book a Project Workflow Demo"}),(0,o.jsx)(s(),{className:v().secondary,href:p.Vd,children:"Explore the Live ERP"})]}),(0,o.jsxs)("div",{className:v().heroAssurance,children:[(0,o.jsx)("span",{children:"Role-based access"}),(0,o.jsx)("span",{children:"Configurable workflows"}),(0,o.jsx)("span",{children:"Mobile access"})]})]}),(0,o.jsxs)("figure",{className:v().heroVisual,children:[(0,o.jsx)(n(),{src:r.visual.src,alt:r.visual.alt,width:r.visual.width,height:r.visual.height,priority:!0,sizes:"(max-width: 900px) 100v
1w, 540px"}),(0,o.jsxs)("figcaption",{children:[(0,o.jsx)("strong",{children:r.visual.title}),(0,o.jsx)("span",{children:r.visual.caption})]})]})]})}),(0,o.jsx)("section",{className:v().definition,children:(0,o.jsx)("div",{className:v().container,children:(0,o.jsxs)("p",{children:[(0,o.jsxs)("strong",{children:["What is ",r.eyebrow.toLowerCase(),"?"]})," ",r.definition]})})}),(0,o.jsx)("section",{className:v().section,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"The operational problem"}),(0,o.jsx)("h2",{children:r.problemHeading}),(0,o.jsx)("div",{className:v().problemGrid,children:r.problems.map(e=>(0,o.jsxs)("article",{children:[(0,o.jsx)(d.Z,{name:"alert"}),(0,o.jsx)("h3",{children:e.title}),(0,o.jsx)("p",{children:e.copy})]},e.title))})]})}),(0,o.jsx)("section",{className:v().sectionAlt,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Connected EPC records"}),(0,o.jsx)("h2",{children:r.connectionHeading}),(0,o.jsx)("p",{className:v().sectionIntro,children:r.connectionIntro}),(0,o.jsx)("div",{className:v().connectionFlow,children:r.connections.map((e,t)=>(0,o.jsxs)("div",{children:[(0,o.jsx)("span",{children:String(t+1).padStart(2,"0")}),(0,o.jsx)("strong",{children:e})]},e))})]})}),(0,o.jsx)("section",{className:v().section,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Core capabilities"}),(0,o.jsx)("h2",{children:"Controls your team can evaluate in a demo"}),(0,o.jsx)("div",{className:"".concat(v().capGrid," ").concat(v().detailCapGrid),children:r.capabilities.map(e=>(0,o.jsxs)("article",{children:[(0,o.jsx)(d.Z,{name:e.icon}),(0,o.jsx)("h3",{children:e.title}),(0,o.jsx)("p",{children:e.copy})]},e.title))})]})}),(0,o.jsx)("section",{className:v().walkthrough,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsxs)("div",{className:v().walkthroughHead,children:[(0,o.jsxs)("div",{children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Product walkthrough"}),(0,o.jsx)("h2",{children:r.visual.title}),(0,o.jsx)("p",{children:r.visual.caption})]}),(0,o.jsx)("ol",{children:r.visual.annotations.map((e,t)=>(0,o.jsxs)("li",{children:[(0,o.jsx)("span",{children:t+1}),e]},e))})]}),(0,o.jsxs)("figure",{className:v().walkthroughVisual,children:[(0,o.jsx)(n(),{src:r.visual.src,alt:r.visual.alt,width:r.visual.width,height:r.visual.height,sizes:"(max-width: 1120px) 100vw, 1120px"}),(0,o.jsx)("figcaption",{children:r.visual.caption})]}),(0,o.jsxs)("p",{className:v().takeaway,children:[(0,o.jsx)("strong",{children:"Operational takeaway"}),(0,o.jsx)("span",{children:"The view gives authorised teams a shared record for the next decision; it does not replace physical verification or professional judgement."})]})]})}),(0,o.jsx)("section",{className:v().sectionAlt,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Feature workflow"}),(0,o.jsx)("h2",{children:r.workflowHeading}),(0,o.jsx)("div",{className:v().detailedWorkflow,children:r.workflow.map((e,t)=>(0,o.jsxs)("article",{children:[(0,o.jsx)("span",{children:t+1}),(0,o.jsx)("h3",{children:e.title}),(0,o.jsxs)("dl",{children:[(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Trigger"}),(0,o.jsx)("dd",{children:e.trigger})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Responsible role"}),(0,o.jsx)("dd",{children:e.role})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Record produced"}),(0,o.jsx)("dd",{children:e.record})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Control point"}),(0,o.jsx)("dd",{children:e.control})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Next handoff"}),(0,o.jsx)("dd",{children:e.handoff})]})]})]},e.title))})]})}),(0,o.jsx)("section",{className:v().section,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Role-based value"}),(0,o.jsx)("h2",{children:r.roleHeading}),(0,o.jsx)("div",{className:v().roleGrid,children:r.roles.map(e=>(0,o.jsxs)("article",{children:[(0,o.jsx)("h3",{children:e.title}),(0,o.jsx)("p",{children:e.copy})]},e.title))})]})}),(0,o.jsx)("section",{className:v().loisAssist,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsxs)("div",{className:v().loisSectionHead,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Lois AI in this workflow"}),(0,o.jsx)("h2",{children:r.loisHeading}),(0,o.jsx)("p",{children:"Lois works with permitted Supista data and does not bypass configured validations, permissions or approvals."})]}),(0,o.jsx)("div",{className:v().loisExamples,children:r.lois.map(e=>(0,o.jsxs)("article",{children:[(0,o.jsxs)("blockquote",{children:["â",e.ask,"â"]}
1),(0,o.jsxs)("dl",{children:[(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Checks"}),(0,o.jsx)("dd",{children:e.checks})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"Prepares"}),(0,o.jsx)("dd",{children:e.prepares})]}),(0,o.jsxs)("div",{children:[(0,o.jsx)("dt",{children:"You review"}),(0,o.jsx)("dd",{children:e.review})]})]})]},e.ask))}),(0,o.jsx)(s(),{href:"".concat(p.Vd,"/features/lois-ai"),children:"See how Lois AI works â"})]})}),(0,o.jsx)("section",{className:v().lifecycleSection,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Connected EPC lifecycle"}),(0,o.jsx)("h2",{children:"See where this feature passes work next"}),(0,o.jsx)("div",{className:v().lifecycleFlow,children:f.map(e=>(0,o.jsx)(s(),{href:"".concat(p.Vd,"/features/").concat(e.slug),className:r.lifecycleFocus.includes(e.key)?v().lifecycleActive:"",children:e.label},e.key))}),(0,o.jsx)("nav",{className:v().relatedLinks,"aria-label":"Immediately related EPC features",children:r.related.map(e=>(0,o.jsxs)(s(),{href:"".concat(p.Vd,"/features/").concat(e.slug),children:["Explore ",e.label," â"]},e.slug))})]})}),(0,o.jsx)("section",{className:v().implementationSection,children:(0,o.jsxs)("div",{className:"".concat(v().container," ").concat(v().implementationGrid),children:[(0,o.jsxs)("div",{children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Proof and deployment confidence"}),(0,o.jsx)("h2",{children:r.assuranceHeading}),(0,o.jsx)("p",{children:r.assuranceCopy})]}),(0,o.jsxs)("ul",{className:v().checklist,children:[(0,o.jsx)("li",{children:"ISO/IEC 27001-certified controls"}),(0,o.jsx)("li",{children:"Role-based record access"}),(0,o.jsx)("li",{children:"Configurable forms and workflows"}),(0,o.jsx)("li",{children:"Mobile-friendly operational access"}),(0,o.jsx)("li",{children:"Human review for professional decisions"})]})]})}),(0,o.jsx)("section",{className:v().sectionAlt,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Buyer questions"}),(0,o.jsxs)("h2",{children:[r.eyebrow," FAQs"]}),(0,o.jsx)("div",{className:v().faq,children:r.faqs.map(e=>(0,o.jsxs)("details",{children:[(0,o.jsx)("summary",{children:e.question}),(0,o.jsx)("p",{children:e.answer})]},e.question))}),(0,o.jsxs)("nav",{className:v().articleNav,"aria-label":"Related EPC resources",children:[(0,o.jsx)(s(),{href:"".concat(p.Vd,"/guides"),children:"Read EPC implementation guides"}),(0,o.jsx)(s(),{href:"".concat(p.Vd,"/use-cases/epc-contractors"),children:"See the EPC contractor use case"}),(0,o.jsx)(s(),{href:"".concat(p.Vd,"/pricing"),children:"Review EPC ERP pricing"}),(0,o.jsx)(s(),{href:"/contact",children:"Talk to an EPC workflow expert"})]})]})}),(0,o.jsx)("section",{className:v().final,children:(0,o.jsxs)("div",{className:v().container,children:[(0,o.jsx)("p",{className:v().eyebrow,children:"Use a real workflow"}),(0,o.jsx)("h2",{children:r.finalHeading}),(0,o.jsx)("p",{children:r.finalCopy}),(0,o.jsxs)("div",{className:v().actions,children:[(0,o.jsx)(l.Z,{eventName:"epc_final_demo",className:v().primary,children:"Book a Project Workflow Demo"}),(0,o.jsx)(s(),{className:v().secondary,href:"".concat(p.Vd,"/pricing"),children:"View EPC ERP Pricing"})]})]})})]})]})}var y=!0;function b(e){let{feature:t}=e;return(0,o.jsx)(w,{feature:t})}},31918:function(e){e.exports={page:"EpcContentPage_page__y6sJi",container:"EpcContentPage_container__Xt5_z",hero:"EpcContentPage_hero__Qx5QJ",breadcrumbs:"EpcContentPage_breadcrumbs__1Xhvx",eyebrow:"EpcContentPage_eyebrow__POIgA",lead:"EpcContentPage_lead__6_i1w",actions:"EpcContentPage_actions__1BUo8",primary:"EpcContentPage_primary__GXELa",secondary:"EpcContentPage_secondary__NriwS",section:"EpcContentPage_section__MEHKl",sectionAlt:"EpcContentPage_sectionAlt__Xnii4",final:"EpcContentPage_final___1c7_",split:"EpcContentPage_split__H8sHH",copy:"EpcContentPage_copy__7OQT7",answer:"EpcContentPage_answer__zdaka",capGrid:"EpcContentPage_capGrid__JYF1D",workflow:"EpcContentPage_workflow__FAH6f",roleGrid:"EpcContentPage_roleGrid__LMfVG",linkGrid:"EpcContentPage_linkGrid__VpFd4",outcome:"EpcContentPage_outcome__eq_fF",faq:"EpcContentPage_faq___aq8r",checklist:"EpcContentPage_checklist__2kQUI",metaLine
1:"EpcContentPage_metaLine__VG_Id",tableWrap:"EpcContentPage_tableWrap__rnLsH",table:"EpcContentPage_table__BuAaM",notice:"EpcContentPage_notice__Jvc4S",article:"EpcContentPage_article__KR9CI",articleNav:"EpcContentPage_articleNav__C66Pq",visualSection:"EpcContentPage_visualSection__vVfE5",productVisual:"EpcContentPage_productVisual__m7Fkf",visualActions:"EpcContentPage_visualActions__huMQo",articleHeroImage:"EpcContentPage_articleHeroImage__9YRM_",guidesHero:"EpcContentPage_guidesHero__MSIWv",guideArticleHero:"EpcContentPage_guideArticleHero__hpzec",guidesHeroGrid:"EpcContentPage_guidesHeroGrid__u8hZv",articleHeroGrid:"EpcContentPage_articleHeroGrid__s3eM4",guidesHeroImage:"EpcContentPage_guidesHeroImage__bzW69",guideGrid:"EpcContentPage_guideGrid__QVsjF",guideCard:"EpcContentPage_guideCard__WT7on",guideCardImage:"EpcContentPage_guideCardImage__H_V4E",guideCardCopy:"EpcContentPage_guideCardCopy__Q_MsY",loisAssist:"EpcContentPage_loisAssist__JoTe_",loisAssistGrid:"EpcContentPage_loisAssistGrid__p2nev",loisHeading:"EpcContentPage_loisHeading__diX8X",loisPrompt:"EpcContentPage_loisPrompt__DOgDi",projectHero:"EpcContentPage_projectHero__y7uUC",trustStrip:"EpcContentPage_trustStrip__CVE8d",definition:"EpcContentPage_definition__0Q5Dj",problemGrid:"EpcContentPage_problemGrid__ws6LA",sectionIntro:"EpcContentPage_sectionIntro__48_Cg",sectionClosing:"EpcContentPage_sectionClosing__0VPYr",productViewGrid:"EpcContentPage_productViewGrid__uWulB",productViewWide:"EpcContentPage_productViewWide__aTYG3",viewLabel:"EpcContentPage_viewLabel__T8L78",projectCapGrid:"EpcContentPage_projectCapGrid__s4875",projectWorkflow:"EpcContentPage_projectWorkflow__P7PM8",promptList:"EpcContentPage_promptList__OOFWW",safetyLine:"EpcContentPage_safetyLine__sa4G7",projectRoleGrid:"EpcContentPage_projectRoleGrid__Zi7w8",implementationSection:"EpcContentPage_implementationSection__3Pmf1",implementationGrid:"EpcContentPage_implementationGrid__EC11B",featureHero:"EpcContentPage_featureHero__IGtz8",featureHeroGrid:"EpcContentPage_featureHeroGrid__M3_YX",heroVisual:"EpcContentPage_heroVisual__piwM9",heroAssurance:"EpcContentPage_heroAssurance__BjWOR",connectionFlow:"EpcContentPage_connectionFlow__F2of6",detailCapGrid:"EpcContentPage_detailCapGrid__ZqLg6",walkthrough:"EpcContentPage_walkthrough__GkjKe",walkthroughHead:"EpcContentPage_walkthroughHead__wKpIb",walkthroughVisual:"EpcContentPage_walkthroughVisual__VqcR2",takeaway:"EpcContentPage_takeaway__k5Pwl",detailedWorkflow:"EpcContentPage_detailedWorkflow__ek5V4",loisExamples:"EpcContentPage_loisExamples__Gvvhk",loisSectionHead:"EpcContentPage_loisSectionHead__DGsie",lifecycleSection:"EpcContentPage_lifecycleSection__5piJ4",lifecycleFlow:"EpcContentPage_lifecycleFlow__sVhOZ",lifecycleActive:"EpcContentPage_lifecycleActive__quVL7",relatedLinks:"EpcContentPage_relatedLinks__ZXOUC"}}},function(e){e.O(0,[6692,9029,9774,2888,179],function(){return e(e.s=99071)}),_N_E=e.O()}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.