Industries · Engineering and design
Every project your firm has delivered, behind the next pursuit.
Niska reads your proposals, specifications and project records, builds a model of your firm, and runs pursuits and delivery on it.
Answer · 1 source
Approved with comments on September 12. The closer finish needs a resubmittal.1
Win with your own record.
Find the projects closest to a new pursuit, with the documents that prove it.
Keep specifications and submittals straight.
Requirements in your contracts and specifications become tracked work.
Know who has done it.
See which people delivered which projects, from the record.
What Taju learns here
Your projects, clients, disciplines, specifications, submittals, people and deadlines.
- project
- Riverside Clinic, Building B
- p. 1
- company
- Carver Builders
- p. 1
- status
- Approved with comments, Sep 12
- p. 1
- deadline
- Resubmittal due Sep 26
- p. 2
- person
- Dana Ruiz, project manager
- p. 2
Permissions before retrieval.
Access rules apply before the model sees anything, so each person sees only what they’re allowed to see.
Documents it reads
- Proposals
- Specifications
- Submittals
- Requests for information
- Contracts
- Drawing registers
- Meeting minutes
Modules firms start with
- Document management
- Data and opportunity sourcing
- Task management
- Customer relationship management
Questions
Can it read our project archive?
Yes. It reads documents in full, tables and scans included, and links each one to its project.
Can we keep the systems we use now?
Yes. Niska reads the systems you keep and runs the rest on its own modules. One model of your firm works across both, and you move each process over when you’re ready.
Where does our data live?
In the deployment you choose: your own cloud account, a Niska-managed cloud, or your own servers. Each firm gets its own database and search index.