ARKcelerateARKcelerate
Project List

One Project ID the whole ERP follows.

One project list that every module reads from — a won deal becomes a project, and CRM, manufacturing, purchase, quality and finance all work off it.

Project List — one row per engagement, the lookup key every module uses.
Project List — one row per engagement, the lookup key every module uses.

What makes it unique

The features that set Project List apart from a generic ERP.

Built for projects-based manufacturing — not retrofitted to it. These are the workflows big ERPs either skip or get wrong.

One Project ID, fourteen modules

Every PO, MO, BOM, drawing revision, GRN, invoice, payslip and time entry carries the same Project ID by design. No copy-pasting, no spreadsheet bridge — the project is the join key everywhere.

Won deal → project

When a CRM opportunity is won, convert it into a project in one step. Promised lead time, quoted scope, customer contacts and approved drawings all carry across — manufacturing knows what to build, by when, and against which spec.

Customer Approvals tied to the project

Drawings, revisions, customer sign-offs and the audit trail all live under the project. Manufacturing Clearance Date stamps the moment the customer approves the critical doc — and the Dispatch Deadline computes itself from there.

Cost tracking — committed, actual, real-time

POs hit committed cost on approval; GRNs flip them to actual; payroll time-entries add labour cost; invoices update billed value. Open the project, see the live margin — no month-end reconciliation needed.

Auto-task board on creation

Creating a project spawns a Tasks board pre-built from a template — stages, sections, tasks and milestones — so the team has somewhere to work from day one, without setting it up by hand.

P1 priority cascades downstream

Mark a project P1 and it bumps to the top of the manufacturing queue, the purchase-approval inbox, the engineering revision board and the QC schedule — all in one flag. Priority is set once, respected everywhere.

Feature 01

A central registry — one row per engagement, the lookup key every module uses.

The Project List is the master record for every engagement: project code, customer, stage, owner, budget, start + end dates, status, on-time indicator. Search, filter, group, bulk-edit. From this one screen you can drill into the project and reach every MO, PO, invoice, drawing and time entry that’s ever been logged against it. Nobody else needs to maintain their own copy of "the project" — the rest of the org reads from this one.

Project detail — stage, budget, team, linked MOs, POs, invoices, documents.
Project detail — stage, budget, team, linked MOs, POs, invoices, documents.
  • Custom project stages per org (e.g. Awarded → Engineering → Production → Pre-Despatch → Closed)
  • Multiple owners per project: PM, engineering lead, commercial lead, site lead
  • Customer + project-site fields (separate from billing address)
  • Budget capture with revision tracking, scope-change flags
  • Filter by customer, KAM, status, priority — bulk-edit when scope shifts
  • On-time indicator computed from the Dispatch Deadline, visible at a glance

Feature 02

Live production status — for every component, on every tag.

Open any project and the Manufacturing tab shows you exactly where things stand on the shop floor. Component-level progress per tag (one project, three vessels, twelve components — each at its own stage), shopfloor areas and workers assigned to this project, and an overall percent-complete that’s computed from the actual stage on each piece. No status-update meeting required — the data is the status.

Project → Manufacturing tab — components, progress, areas and workers.
Project → Manufacturing tab — components, progress, areas and workers.
  • Per-tag progress bars + a 12-row component status table, each showing its current stage of fabrication
  • Shopfloor areas (Plate Shop, Fabrication Bay 1, Hydrotest Bay, Paint Booth) booked against the project for the duration of the build
  • Individual workers + production teams assigned with from/until dates — capacity stays honest
  • Stages defined per product type (Plate / Shell, Tube Bundle, Machined Component, Bought-Out)
  • Overall percent-complete is derived, not entered — managers can’t “round up”

Feature 03

Committed spend — per PO, per line, per supplier — in real time.

Procurement happens in Purchase, but the project owner doesn’t want to live there. The Purchase & Inventory tab on the project page shows every PO raised against this project: committed spend (basic + tax + total) by currency, status of each PO (received / partial / pending), and per-line received-vs-pending counts. The numbers update the instant a PO gets approved or a GRN gets posted — same ledger, just lensed against this one project.

Project → Purchase & Inventory tab — committed spend + per-PO line items.
Project → Purchase & Inventory tab — committed spend + per-PO line items.
  • Committed-spend table by currency — basic, tax, total — for projects that buy in USD + INR + EUR
  • Per-PO summary: supplier, status, order date, expected delivery, totals
  • Line-level received / pending split, so you can see *which* item is holding the build up
  • Statuses (Received / Partial / Pending) refresh as soon as the GRN is posted in Purchase
  • Click any PO number to jump straight into the Purchase module with full context

Feature 04

Every document the project ever touched — filed against the Project ID, forever.

The customer’s RFQ. The first GA Rev. 0 and every revision after it. MTCs from the plate mill. Weld maps. Radiography reports. ITPs. Hydrotest certificates. Internal MoMs. Weekly progress decks. As-built drawings. All of it lives in one place — the project itself — tagged with the same Project ID that Manufacturing, Purchase, Quality and Finance already use. Three years from now, when the customer calls about a leak and asks for the heat-lot certificate of the dished end, you don’t have to dig through old emails or chase someone’s laptop. Open the project, open Documents, find it.

Project → Documents tab — every doc the project ever touched, filed against the same Project ID.
Project → Documents tab — every doc the project ever touched, filed against the same Project ID.
  • Single Project ID is the join key — every document is queryable against it for the life of the project (and well beyond)
  • Pre-organised folders: Customer Inputs · Engineering Drawings · Material Test Certificates · QC & NDE Reports · Customer Submittals · Project Reports
  • Full revision history per document — every uploaded version is preserved; supersedes-chain shows the lineage at a glance
  • Customer + supplier docs filed alongside your own work, so traceability is end-to-end (mill heat lot → MTC → GA → ITP → hydrotest report — all on one page)
  • Recent uploads feed surfaces what just landed; folder counts show what’s still pending
  • Department-based access control — Engineering sees calc files, QA sees NDE reports, Sales sees what they need, no more

The projects-based manufacturing angle

One Project ID, one source of truth — across every module.

In a generic ERP, "projects" is a tag you can attach to records if someone remembers to. In ARKcelerate the Project ID is the join key the entire data model is built around — created when the deal is won, present on every PO, MO, BOM, drawing, GRN, invoice, payslip and task that follows. The result: profitability matches reality, deadlines are computed not estimated, and nobody has to keep a side spreadsheet to know what’s actually going on with project X.

Everything in the module

The full Project List feature list.

Grouped by functional area. Every feature below is included in every plan — no paywalled tiers, no “enterprise edition” unlocks.

53 featuresacross 10 areas
AreaFeatures
One project page, every signal in one place
  • Open a project once and see everything tagged to it: drawings, BOMs, MOs, POs, GRNs, inspections, punch points, invoices, time entries, documents, comments, audit log
  • Each tab queries the same Project ID off the same database every other module already writes to — no copy-paste, no spreadsheet bridge, no “which version is current?”
  • Open it today, open it in three years — the data is still there, still linked, still queryable
  • Scope-change banner surfaces at the top of every tab when an alert has been raised against the project
  • P1 priority set on the header propagates to every module’s queue automatically
Overview tab — the project at a glance
  • Project code, name, customer, current status, owner — the header line everyone knows
  • Linked CRM opportunity with quoted value, lead time and key contacts inherited from the win
  • Manufacturing orders surfaced inline with status pill + click-through to the MO
  • Upcoming maintenance alerts on shopfloor areas booked against the project
  • Custom-field values (org-defined: contract reference, BOM authority, regulatory class, …) editable inline
  • Multiple owners per project — PM, engineering lead, commercial lead, QC lead, site lead — each with their own role on the project
Customer Approvals tab — what the customer has seen and signed off
  • Engineering project stage (Drawing Preparation → Comments Received → Internal Approval → Submitted to Customer → Customer Approved → Manufacturing Drawing → Under Manufacturing)
  • Per-document submission/approval timeline with revision codes (Rev. 0 → Rev. A → Rev. B)
  • Clearance flag + date stamp — has manufacturing been cleared on this project? When?
  • Customer comments + responses logged inline against the drawing they refer to
  • Overdue indicator when a revision has been waiting on the customer past the SLA
Manufacturing tab — live shop-floor state, per component
  • KPI strip: total components / completed / shopfloor areas booked / workers assigned
  • Per-tag progress bars — derived from the actual stage on each component, not entered by hand
  • Component status table: section, tag, component, current stage, percent-complete bar
  • Shopfloor areas (Plate Shop, Fab Bay 1, Hydrotest Bay, Paint Booth …) booked for the build duration
  • Individual workers + production teams assigned with from/until dates — capacity stays honest
  • Stage template per product type (Plate / Shell, Tube Bundle, Machined Component, Bought-Out)
Quality tab — every inspection and punch point on the project
  • Inspection checks per tag: total / completed / failed / pending
  • Component-level inspection status (which tag, which component, which check, which inspector)
  • Customer inspection events (FAT, witness inspection, source inspection) with outcome
  • Punch points raised against the project + their current status (Open / Closed / Verified)
  • CAPA records tied to the project, with root-cause, owner and due date
Purchase & Inventory tab — every commitment and movement, real time
  • KPI strip: total POs / fully received / pending — at the project level
  • Committed spend table by currency (basic + tax + total) — projects that buy in USD + INR + EUR all reconcile
  • Per-PO breakdown: supplier, status, order date, expected delivery, totals
  • Line-level received / pending split — see which item is holding the build up
  • Click any PO number to jump into Purchase with the project filter pre-applied
  • Stock issues + reservations against the project — what was pulled from inventory, when, by whom
Schedule tab — promised vs computed dispatch deadline
  • Promised lead time pulled directly from the CRM opportunity at the moment of win
  • Engineering clearance date — stamped automatically when drawings get released to manufacturing
  • Computed dispatch deadline = clearance + lead time, recomputed every page load
  • On-Track / At-Risk (last 14 days) / Overdue badge — visible at a glance
  • Milestone timeline: Won → Started → Engineering Cleared → Manufacturing in Progress → Dispatch / Delivery
  • Days-to-dispatch counter visible on the project list view too — no drill-down required
Documents tab — every file the project has ever touched
  • KPI strip: total files / storage used / folder count
  • Pre-organised folders: Customer Inputs · Engineering Drawings · MTCs · QC & NDE Reports · Customer Submittals · Project Reports
  • Recent uploads feed with file name, folder, size, date and uploader
  • Every document carries its full revision history; supersedes-chain walks back through revisions
  • Customer + supplier docs filed alongside your own work — heat-lot certificates, supplier QAPs, customer-stamped ITPs all in one place
  • Department-based access control: Engineering sees calc files, QA sees NDE reports, Sales sees what they need
Team & Hierarchy tabs — who owns it, what sits under it
  • Project team roster surfaced on the Team tab with a role per member
  • Hierarchy tab: umbrella projects (PV1014A-B-C) with child projects per tag (PV1014A / PV1014B / PV1014C)
  • CRM opportunity links live on the umbrella; MOs, tasks, drawings can attach at any level — child or parent
  • Drill from the umbrella project straight into each tag’s child project
Activity tab — every event the project has ever seen, in one timeline
  • Cross-module audit feed: who did what, when, in which module — including opportunity wins, drawing approvals, MO releases, PO approvals, GRN posts, invoice issues, scope changes
  • Filter by module, user or date range
  • Source of truth for after-the-fact “what actually happened?” investigations — invaluable when a customer queries something months or years later
  • Audit-grade — every entry timestamped + user-stamped, no edit, no delete

Try Project List alongside every other module.

One signup. Full feature access during your trial.