Every established engineering firm is sitting on twenty years of project directories: drawings, proposals, specifications, manuals, PLC and controls programs, bills of material, site photographs, and the email thread where somebody explained why a decision was made. It is the most valuable asset in the business and the least usable, because finding anything in it depends on the person who remembers where it is.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
Project Genesis is designed to turn those directories into institutional memory you can query — deployed on-premises or in a private cloud, because this material is not going into anyone else’s system.
What It Is Designed To Do
- Project-directory ingestion — point it at the archive as it actually exists, rather than requiring a migration project first.
- Drawing, document and code extraction — read the content, not just the filenames.
- Entity and relationship indexing — connect projects, equipment, customers and components to each other.
- Engineering semantic search — ask in engineering terms rather than guessing folder names.
- Project similarity and reuse analysis — find the job you already did that resembles the one being quoted.
- Component obsolescence tracking — know which installed base depends on a part going end-of-life.
- Commissioning lessons and issue history — surface what went wrong last time, before it goes wrong again.
- Cited answers and provenance graph — every answer points back to the document it came from.
Why Citations Are the Whole Point
An engineering answer you cannot trace is not usable. If the system says a previous installation used a particular controller, an engineer needs the drawing that says so — not a confident paragraph. Provenance is what makes this a reference tool rather than a plausible-sounding risk, and it is the same retrieval-grounded approach we apply to enterprise knowledge generally.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.