labs@atheron:~/industries/epc/completions$ complete --systems --punch --handover

EPC completions

Offline tablets, check sheets, punch lists and certificates.

Completions decide when a plant can be handed over, and on most remote sites they still run on paper. We build completions systems on tablets that work offline, generate certificates when their prerequisites are met, and give everyone one view of what is left.

Start a project See the example projects

// what matters here

What is different in this industry.

Built from the engineering data

Systems, subsystems and tags imported from the engineering data, so check sheets attach to the right things from day one.

Offline by design

Check sheets, punch items, photos and signatures captured on tablets with no signal, synced to a server on site and on to head office.

Certificates that issue themselves

MC, RFC and RFSU certificates are generated when every prerequisite check sheet and punch item is closed, never before.

One view of what is left

Completion by system, area and contractor, so the handover meeting starts from the same numbers.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Completions and commissioning app

Hypothetical. Not a client, not a result.

// The problem

Mechanical completion and commissioning on a remote site run on paper check sheets and punch lists, and certificates wait for someone to reconcile them in a spreadsheet.

// What we would build

A completions system on tablets that works offline: systems and subsystems, A, B and C check sheets, punch lists with photos, and handover certificates (MC, RFC, RFSU) signed on the device, synced to a server on site and to head office when the link allows.

// What is in it

Systems and subsystems, with tags and check sheets imported from the engineering data
A, B and C check sheets completed offline, with photos and signatures
Punch lists by category, with ownership and clear-out tracking
MC, RFC and RFSU certificates generated when their prerequisites are met
A server on site for areas with poor connectivity, synced to head office
Dashboards of completion by system, area and contractor

// Stack

React Native
Next.js
PostgreSQL
Rack server on site
Offline sync

// estimate

Build: ≈ US$199,000 to US$304,000, delivered within 42 weeksCAD 283,600 to 432,400
Hosting: ≈ US$25 a monthCAD 35 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month
Hardware: ≈ US$10,700 to US$20,900CAD 15,170 to 29,770

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 3.5 to 4 weeks
Design approved: 9.5 to 16 weeks
Core features: 3 to 5.5 weeks
Full build: 2 to 3.5 weeks
First build on devices: 6.5 to 10.5 weeks
Testing and fixes: 0.5 to 1.5 weeks
Store submission: 1.5 to 2 weeks
Certificates issued in a trial handover: 1.5 to 2.5 weeks
Launch: 1.5 to 2 weeks

Outside our hands, and added to the calendar

Hardware delivery, after it is ordered: 2 to 6 weeks
App store review: 1 week
Client IT security review and vendor onboarding: 4 to 8 weeks

How it is paid

Deposit 20%: CAD 56,720 to 86,480
Discovery 8.1%: CAD 22,971.60 to 35,024.40
Design approved 8.1%: CAD 22,971.60 to 35,024.40
Core features 6.6%: CAD 18,717.60 to 28,538.40
Full build 4.4%: CAD 12,478.40 to 19,025.60
First build on devices 17.6%: CAD 49,913.60 to 76,102.40
Testing and fixes 2.2%: CAD 6,239.20 to 9,512.80
Store submission 5.8%: CAD 16,448.80 to 25,079.20
Certificates issued in a trial handover 8.7%: CAD 24,673.20 to 37,618.80
Launch 8.5%: CAD 24,106 to 36,754
Holdback, 30 days after launch (10%): CAD 28,360 to 43,240
Rack server x 1: CAD 14,200 to 28,800. Billed up front, at cost, outside the milestones
Cellular edge gateway x 2: CAD 970. Billed up front, at cost, outside the milestones

Start from this example

// questions

Questions we get about this.

Can it work with our completions database?

Yes. It can be the field tool feeding your database through its API, or the system of record itself; we decide that with your completions lead.

Can check sheet templates be our own?

Yes. Templates are data, edited by your team, not code.

What if two people edit the same item offline?

Changes are merged item by item, and real conflicts are shown to a supervisor to resolve, never silently overwritten.

Back to the industry: Engineering and construction (EPC/EPCM)About the service: Web and mobile apps

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call