Question 1

What does Helmspur monitor across an EPCI project?

Accepted Answer

Helmspur watches 3D models and FEM analyses across process, structural, mechanical, piping, electrical, and integrity. It compares incoming revisions with the last accepted state, surfaces cross-discipline clashes, and tracks expected supplier deliverables such as IFC, STEP, PDMS/E3D, and FEM-neutral files.

Question 2

How does Helmspur sit alongside AVEVA, Bentley, Siemens, Hexagon, Autodesk, Ansys, and Dassault?

Accepted Answer

Helmspur is an oversight layer, not a replacement. The current product story is designed to sit over the AVEVA, Bentley, Siemens, Hexagon, Autodesk, Ansys, and Dassault stacks your team already runs, using open or neutral outputs and revision signals. Specific connectors and pilot scope are confirmed with engineering; we do not claim a native integration for every product.

Question 3

Which input formats and EPCI disciplines are in scope?

Accepted Answer

The current documented inputs include IFC, STEP, PDMS/E3D, and FEM-neutral files. The EPCI scope is process, structural, mechanical, piping, electrical, and integrity. The exact discipline mapping, units, and acceptance rules are set against the project package rather than assumed from a generic template.

Question 4

Who owns the supplier chases and escalation?

Accepted Answer

The project team defines the package, owner, and escalation path. Helmspur starts the chase when an expected delivery slips and routes it by contract package and accountable owner; it does not take contractual ownership or replace the supplier's agreed workflow.

Question 5

What data leaves the project boundary?

Accepted Answer

The documented upload path is same-origin multipart/form-data, with no external upload URL in the application flow. For IFC, raw bytes are parsed in memory and dropped; the app keeps derived metadata and geometry JSON in the platform-provisioned Postgres store. Helmspur does not promise that project data never crosses a platform boundary, so procurement can use the security documentation and an engineering review to confirm platform-mediated processing and subprocessors for a pilot.

Question 6

How are FEM tolerances configured?

Accepted Answer

Helmspur's evaluation model treats FEM tolerance as a discipline and package setting, not one global number. A pilot should agree the threshold, units, baseline, and escalation behavior for each discipline before results are treated as procurement evidence. Where a value is not documented for your package, it remains project-specific rather than an assumed default.

Question 7

How is the daily brief generated and delivered?

Accepted Answer

The brief summarizes overnight revision changes, clashes, missing deliverables, and items that need a decision, so the technical lead gets a concise morning control-room readout. The current product copy promises a daily status brief before the working day; the exact delivery channel and timing are pilot-specific and should be confirmed with engineering rather than assumed to be email or Slack.

Question 8

How are project, revision, clash, and reviewer boundaries handled?

Accepted Answer

Project records, revisions, and clashes remain tied to their project and revision context, while the installed auth model scopes access to signed-in users and roles. The security page documents per-project scan isolation and the deletion path. Package-specific reviewer access and sharing should still be confirmed for the pilot; the product is not presented as a public data directory.

Question 9

How do pilots, procurement, DPA, and sub-processor questions work?

Accepted Answer

A pilot is scoped around a real package and the evidence a technical lead needs to review. Procurement questions can be taken through the security overview, security FAQ, sub-processor page, and security contact; engineering can then confirm the project-specific data path, DPA needs, and any connector or acceptance-rule assumptions. No blanket certification or integration guarantee is implied by this FAQ.

Question 10

How can a buyer request project-specific evidence?

Accepted Answer

Use the engineering contact path with the package, disciplines, target review, or procurement clause you need to test. Helmspur can use that context to propose a contained pilot and identify the evidence that should be reviewed; the contact route is the right place to confirm claims that depend on your project rather than this general FAQ.

The questions that surface before a watchtower goes live.

Ten answers for the technical lead, buyer, and security reviewer.

Ten answers for the technical lead, buyer, and security reviewer.

01What does Helmspur monitor across an EPCI project?

02How does Helmspur sit alongside AVEVA, Bentley, Siemens, Hexagon, Autodesk, Ansys, and Dassault?

03Which input formats and EPCI disciplines are in scope?

04Who owns the supplier chases and escalation?

05What data leaves the project boundary?

06How are FEM tolerances configured?

07How is the daily brief generated and delivered?

08How are project, revision, clash, and reviewer boundaries handled?

09How do pilots, procurement, DPA, and sub-processor questions work?

10How can a buyer request project-specific evidence?