01 / Plan the work

Project Setup & BOQ Control

Connect project hierarchy, work packages, BOQ references, milestones, and accountable owners before field execution begins.

Designed for operational control

Visible ownership

Configurable workflows

Connected reporting

Role-based governance

Business challenge

Operational work needs more than another isolated tool.

Site reports and commercial claims become difficult to reconcile when teams use different zone names, item codes, units, and baseline revisions.

Solution overview

Control project & boq in the same operating model.

Organize infrastructure work by company, department, agency, project, corridor, and zone. Link work packages to approved scope and document references. BOQ imports, rate libraries, quantity limits, and schedule baselines form a configurable project-controls extension.

Capability note

Availability depends on tenant configuration, licensed applications, user rights, and the approved implementation scope.

Key capabilities

Structure the work. Preserve the context.

01

Project, corridor, zone, and work-package hierarchy

Use common identifiers across permits, tasks, documents, effort, and reporting.

02

BOQ item codes, units, quantities, and contract-rate references

Validate units and approved revisions before connecting quantities to valuation. BOQ import and rate handling are scoped with commercial teams.

03

Approved baseline and change ownership

Preserve the approved baseline and route scope changes for review; specialized version controls are agreed during implementation.

04

Milestone and contractor responsibility matrix

Assign package owners and planned dates so field records remain connected to delivery responsibility.

Business outcomes

Move from follow-up to managed execution.

Create a clearer operating rhythm by connecting responsibility, action, evidence, and reporting.

Consistent project records
Clear scope ownership
Comparable planned and actual work
A traceable basis for measurement
Process workflow

A controlled path from request to result.

1

Define hierarchy

2

Map scope and BOQ

3

Assign owners

4

Review baseline

5

Approve release

6

Monitor changes

Screens and dashboards

See the work and the exceptions around it.

Illustrative views show how acSys can bring operational records, ownership, filters, exceptions, and trends into one management workspace.

  • Work-package readiness
  • Unapproved baseline changes
  • Unmapped BOQ items
  • Milestones due
aOperations overview
Today · All companies
Present86
+4
On leave12
2 due back
Effort pending18
-6
Expiring docs9
3 urgent
Workforce availability30 days
Week 1Week 2Week 3Week 4
Needs attentionLive
Effort not posted18
Leave return pending5
Document expiry9
Unassigned tickets7
Role-wise value

One record, different decisions.

Project director

Review package readiness and baseline ownership.

Planner

Align zones, work packages, milestones, and schedule references.

Quantity surveyor

Validate item codes, units, quantities, and rates.

Contractor

Execute against consistent approved scope.

Integration opportunities

Connect the context that improves the decision.

Integrations are confirmed during discovery and designed around security, data ownership, error handling, and reconciliation requirements.

Project and resource managementDMS and workflow approvalsScheduling tools and ERP as scoped
Discuss your process

See how Project Setup & BOQ Control fits your operating model.

Book a Demo