The application provisions its packaged source datasets automatically on startup. The Library is therefore ready before you begin normal estimating.
Build estimates with a clear source, quantity and calculation trail.
This guide describes the application as it works today. It focuses on the engineer's workflow rather than reproducing every screen control: source libraries are available automatically, projects define context, headings define Civil/E&M work type, measurements define quantity, Named Variables and measurement references reduce repeated entry, and the shared calculation engine drives analysis, reports and Excel.
1. Quick start
Enter project name, Work/Sanction Number, Department/Sub-division and Place of Work. Do not look for a project-wide Work Type; classification belongs to headings.
Create Civil or E&M headings, add source items, enter measurements, use references or Named Variables where useful, then inspect Data Analysis.
2. Dashboard
The Dashboard is the project starting point. Use it to create a project, open an existing project, duplicate a project or manage supporting library areas.
Open the project you want to continue. Project state is persisted locally and is independent from the source library.
Browse standard resources and schedule items, import additional source data, or inspect Observed Data databases.
Use Local MR, Cost Index and Rate Analysis Profiles for their respective engineering configuration tasks.
This guide is a conceptual and operational reference. The application itself remains the authority for current field values and available actions.
3. Complete estimating workflow
Create or open the project. Confirm project identity, Place of Work and project defaults.
Create the heading. Assign Civil or E&M. A single project can contain both work types.
Add an item. Use the heading-aware picker to choose the appropriate source/database/chapter or search for an item, preview it and insert it.
Take off quantity. Enter measurement rows and use measurement references or Named Variables when a value is deliberately reused.
Audit the rate. Inspect resource/MR lines, source provenance, Civil/E&M additions, P&OH and Cost Index in Data Analysis.
Produce output. Review the estimate and export the required Abstract, Detailed Report or formula-driven Excel workbook.
4. Projects and headings
Project context
A project contains common identity and defaults such as name, Work/Sanction Number, Department/Sub-division, Place of Work, tax and applicable calculation defaults.
Heading Work Type
There is no project-wide Work Type. Each heading explicitly stores Civil or E&M. That classification controls source filtering, Cost Index resolution and rate-analysis policy.
| Context | Scope | Meaning |
|---|---|---|
| Place of Work | Project | Shared geographic context used for Cost Index resolution. |
| Work Type | Heading | Authoritative Civil/E&M classification. |
| Estimate item | Heading | Source-backed or custom item with its own measurement and rate-analysis state. |
5. Items and the Item Picker
The picker is heading-aware. Standard catalogue records, approved PRICE Observed Data and Personal Library results are restricted to the active heading's work type where that classification applies.
- Do not browse the entire catalogue at once. Search is used deliberately and displayed results are bounded for performance.
- Choose source context first when browsing. Database/chapter selection reduces ambiguity between similarly named source records.
- Preview before insertion. Confirm the specification, unit and source context.
- Standard and approved source records are protected. If you need an independent editable item, use the Create OD workflow.
6. Measurements
The Measurement workspace is the quantity take-off surface. It is designed to behave like an engineering spreadsheet while preserving explicit row state and calculation semantics.
| Field | Purpose |
|---|---|
Description | Meaningful location, member, room, drawing reference or other engineering description. |
Nos | Number of repetitions. |
Length | Length dimension. |
Width | Width/breadth dimension. |
Height | Height/depth dimension. |
Coefficient | Controlled multiplier or factor. |
Qty | Calculated result, not normally a manually entered total. |
Keyboard workflow
| Shortcut | Action |
|---|---|
Tab / Shift+Tab | Move to the next/previous editable field. |
Enter / Shift+Enter | Move vertically within the same field. |
Ctrl/Cmd + Enter | Insert a row below the active row. |
Ctrl/Cmd + Shift + Backspace | Delete the active row through the normal deletion path. |
Ctrl/Cmd + D | Reuse the value from the row above in the same field. |
Shift + Space | Select or clear the active row. |
Shift + ↑ / ↓ | Extend a contiguous row selection. |
7. Measurement references
Measurement references allow a formula to reuse an existing measurement value from the estimate instead of manually retyping the number.
- Start a formula with
=. - Open the Measurement Reference Manager.
- Select the project item/context and the required measurement field.
- Insert the reference into the active formula.
- Complete any required arithmetic and verify the result.
The Reference Manager keeps the measurement targets No, Length, Width, Height, Coefficient and Qty available for insertion. These are reference targets, not replacement measurement inputs.
8. Named Variables — reusable engineering values
Typical examples
A Named Variable can be a constant or a derived formula. Derived variables can use other Named Variables recursively.
Where Named Variables live
Named Variables are project-scoped. They are stored with the existing Project object, not in a separate parallel database. Changing the active project changes the variable context, preventing variables from leaking between projects.
Reference Manager integration
The Measurement Reference Manager provides three working areas plus the active formula: Project Items, Measurement References and Named Variables. Measurement references cover No, Length, Width, Height, Coefficient and Qty. The Named Variables pane searches reusable variables, inserts their symbolic names and provides a compact Add action for a constant.
Full Named Variables Manager
- Create, edit and delete project variables.
- Search by name, unit, description or formula.
- Store optional unit and description for engineering clarity.
- Use Excel-style identifiers: a letter or underscore first, followed by letters, numbers or underscores.
- Names are unique within the project and resolved case-insensitively.
- Dependency checks prevent deleting a variable that another variable still uses.
- Invalid formulas, missing names and circular dependencies are rejected safely.
Formula rules
Named Variables extend the existing safe measurement-formula evaluator. Supported arithmetic remains +, -, *, /, unary signs and parentheses. There is no arbitrary JavaScript execution.
Excel export
Formula-driven Excel export includes a Named Variables worksheet with the project's definitions. Valid names are also emitted as Excel Defined Names, so exported formulas can continue to use names such as =length*width.
9. Rate Analysis
Rate Analysis explains the composition of an item's unit rate. Line types matter because the calculation policy depends on the meaning of the line.
| Line type | Role |
|---|---|
Material | Material resource; also the basis for E&M carriage. |
Labour | Labour resource. |
ToolsPlant | Tools/plant component according to the applicable source/profile. |
Carriage | Transport/cartage component. |
MR | Local Market Rate; included in the complete rate but excluded from Cost Index base. |
SubItem | Nested or source-defined line. |
Note | Informational line without an independent priced resource basis. |
Resource-rate hydration
Standard PRICE/CPWD schedule lines can persist a resource code while the authoritative rate is held in the Resource Library. A stored rate of zero is therefore not automatically a genuine zero rate.
10. Civil vs E&M
| Work Type | Current PRICE source context | Policy |
|---|---|---|
| Civil | 2021 · Databook 1 · typical Civil chapter 50 · worknatureid=8 | Water Charge → Contractor P&OH → Cost Index. |
| E&M | 2022 · Databook 2 · typical E&M chapter 90 · worknatureid=9 | Carriage = 1% of Material Cost → Contractor P&OH → E&M Cost Index; no Civil Water Charge. |
Civil sequence
E&M sequence
The E&M carriage basis is the typed Material subtotal. It is not the final item total and is not Water Charge.
MR is included in the complete rate basis but excluded from the Cost Index base for both Civil and E&M.
11. Library — source data is ready by default
Packaged datasets
| Dataset | Type | Work Type |
|---|---|---|
| CPWD DSR 2021 | .eproj standard catalogue | Civil |
| CPWD DSR 2022 | .eproj standard catalogue | E&M |
| PRICE Observed Data (Civil) | .oddb approved PRICE OD source | Civil |
| PRICE Observed Data (E&M) | .oddb approved PRICE OD source | E&M |
The application also checks bundled data health and can rehydrate managed bundled datasets when a stored copy is incomplete.
Library areas
Browse resource categories and resource master rates.
Browse standard schedule records by database, then chapter, then search.
Bring in additional local source files through one unified import entry point.
Manage imported Observed Data databases and their OD records.
12. Observed Data and custom OD
Observed Data is a separate imported database class. A PRICE Observed Data database can be an approved source, while a custom OD is an independently authored reusable estimate item.
Unified Import Data workflow
| File | Handling |
|---|---|
.eproj | Existing master-data parser and confirmation flow. |
.oddb / .edb | Existing Observed Data importer. |
.sqlite / .db | Neutral SQLite extension; the UI asks whether to use the Master or Observed importer. |
Add source data vs Create OD
| Action | Use when | Result |
|---|---|---|
| Add source data | The required standard or approved source item already exists. | Source-backed, protected estimate item. |
| Create OD | A new independent custom item is required. | Editable custom OD; the original source is not modified. |
Three Create OD paths
- Entirely new — start a blank custom OD.
- Create from existing OD — copy an observed/personal source into an independent draft.
- Create from Standard Data — copy a standard/approved source into an independent draft.
Custom ODs use their own identity, technical specification, billed unit, header quantity/unit and analysis. Resource/MR rates are sourced from the libraries rather than turning the OD editor into a second uncontrolled price master.
13. Local Market Rate (MR) Library
The MR Library stores reusable market-rate records independently from source databases. MR can be entered manually, imported from Excel or extracted from source analysis data.
- Manual create/edit/delete.
- Excel import with common headings such as Code/MR Code, Description, Unit and Rate.
- Extraction from PRICE/Observed Data analysis lines.
- Extraction from imported master PRICE/CPWD/DSR analysis templates.
- Classification by Work Type and source provenance where available.
14. Resource Library
The Resource Library is the local master for resource code, description, unit, category, source and authoritative rate. Standard schedule analysis may reference a resource by code.
- Code — lookup identity.
- Description / Unit — engineering presentation and unit consistency.
- Category — resource organisation.
- Rate — authoritative rate used by standard resource hydration.
- Source — provenance.
15. Cost Index
Civil and E&M Cost Index profiles are independent. A mixed project can share one location while each heading resolves its own work-type profile.
MR remains in the complete rate but is excluded from the Cost Index base.
16. Data Analysis — audit the result
When a number looks wrong, trace it backwards instead of applying a display correction.
Audit checklist
- Confirm the item source and specification.
- Confirm header quantity and unit basis.
- Confirm analysis line types.
- Confirm Resource/MR rates.
- Confirm MR is excluded from Cost Index base.
- Confirm Civil/E&M policy matches the heading.
- Save and reopen after analysis edits to verify persistence.
17. Reports and Excel
Reports and Excel consume the shared calculation authority. They should not silently implement a second version of the estimator's rules.
- Review project metadata and Place of Work.
- Review heading Work Type.
- Verify item specification and unit.
- Verify measurement quantity.
- Verify rate-analysis composition.
- Verify Cost Index and P&OH.
- For formula exports, verify the Named Variables worksheet and Defined Names when the project uses them.
Named Variables in Excel
The canonical formula-driven workbook includes the project's Named Variables as a dedicated worksheet and exposes valid names as Excel Defined Names. This keeps reusable formula semantics visible in the exported workbook.
Rounding
Civil PRICE monetary stages are rounded at the defined calculation stages so UI and Excel remain aligned. GST/Cess source sequence rows are provenance for the final tax stage rather than rate-analysis components.
18. Storage and sync
The browser-local working store contains projects, estimate entities, measurements, analysis lines and library data.
Cloud synchronization is an explicit cloud layer. It does not replace the local working database.
Source removal is not estimate deletion
Removing an imported library source removes that source's local library records. Estimate items already copied into a project are independent and are not automatically removed.
Project portability
Project export/import and duplication operate on the project bundle. Project-scoped Named Variables travel with that project because they are part of the existing Project object.
19. Offline-first PWA
The hosted estimator is an installable PWA. The application shell can be cached for offline use, while IndexedDB remains the working data store.
- Bundled source data is provisioned into local storage for normal use.
- Imported source data is stored locally in the appropriate source stores.
- Cloud synchronization is separate from local persistence.
- Hosted access remains subject to the application's authentication boundary.
20. Source and provenance rules
Source metadata is part of the calculation context. Do not infer Civil/E&M classification from a filename when explicit metadata or heading context exists.
| Rule | Current contract |
|---|---|
| Civil PRICE provenance | Databook 1 · SOR 2021 · relevant Civil chapter · worknatureid=8. |
| E&M PRICE provenance | Databook 2 · SOR 2022 · relevant E&M chapter · worknatureid=9. |
| Observed specification | od_items.description is the authoritative technical specification. |
| Synthetic source rows | Do not sum a source-derived calculation row again when the shared calculation policy already represents it. |
| Work Type | Active heading is the authoritative estimate classification; source metadata supports source validation. |
21. Troubleshooting by root cause
| Symptom | Check first |
|---|---|
| Library looks empty after first load | Allow startup provisioning to finish, then revisit Library. Bundled data is provisioned automatically; it is not a manual import step. |
| Schedule chapter list is ambiguous | Use Library → Schedule Items and select the database first, then the chapter. |
| Item missing from picker | Heading Work Type, source metadata, database/chapter and search term. |
| Standard resource rate is zero | Resource code and Resource Library authoritative rate. |
| E&M shows Water Charge | Heading Work Type and shared E&M policy. E&M uses 1% Material Cost carriage instead. |
| Named Variable will not save | Check identifier format, duplicate name, missing references and circular dependencies. |
| Named Variable cannot be deleted | Another Named Variable depends on it. Remove or edit the dependent formula first. |
| Measurement formula gives an invalid result | Check reference target, Named Variable name, arithmetic syntax and circular dependencies. |
| MR receives Cost Index | Inspect MR classification and Cost Index base construction. |
| Excel differs from UI | Compare staged calculation values and rounding points in Data Analysis. |
| Edited analysis returns after reload | Verify the save path and persisted IndexedDB state. |