Frequently asked questions

Acatian is a browser-based process engineering workspace for chemical, biotechnology and food processes. Define a production question, build its model, calculate alternatives and export the results with their inputs and limitations.

Process development uses it to design and scale routes; MSAT and manufacturing use it for tech transfer, scheduling and capacity; plant engineering uses it for equipment, utilities and facility concepts; TEA and LCA teams use the same process basis for cost and environmental decisions.

The model library spans chemical production, biotechnology, food, water and related process industries. Available calculations include bounded chemical-reaction models, separation and heating calculations, and biological dynamics. Each calculation states its own required inputs and limits. Source-derived diagrams need reviewed connections and parameters before they become executable models.

Yes. Use a customer-owned reference process, define acceptance tolerances, reconstruct the authorized process basis, and compare balances, schedules, economics, exports, and collaboration workflows before migrating any validated work.

The package identifies the decision, process basis, selected scenario, calculated results, sources and unresolved inputs. Depending on the executed study, it can include flowsheets, equipment and stream tables, profiles, schedules, costs and environmental inventories. Uncalculated sections remain visibly unavailable.

Available tools include model-structure checks, dynamic calculations, supported parameter fitting, uncertainty propagation and constrained scenario studies. State-estimation and surrogate demonstrations use synthetic data; they do not establish online plant prediction or a trained neural model.

Our development direction is to accelerate process-model evaluation with learned approximations, connect molecular and formulation data to measured process responses, and evaluate control recommendations against plant measurements. These learned prediction and live control capabilities are development goals. Engineering calculations and experimental calibration are available today.

Accuracy depends on model structure, inputs, calibration, and evidence. Acatian records low, base, and high values, units, sources, confidence, and validation state so screening results are not presented as validated plant predictions.

The in-app view is an interactive engineering screen for geometry, boundary conditions, transport risks, and external job preparation. Validated three-dimensional CFD requires a verified mesh, numerical settings, material models, convergence evidence, and an external CFD worker such as OpenFOAM.

No. It makes assumptions, dependencies, consequences, and missing evidence visible. Qualified engineers remain responsible for safety, GMP, regulatory, equipment, validation, and investment decisions.

Yes. Projects accept company-owned CSV and JSON data such as historian series, batch records, assays, recipes, schedules, utilities, TEA/LCA inventories, and supplier quotes. Mapping and preview steps show what changes before data is applied.

Team plans support projects, collaborators, invitations, branches, saved versions, comparisons, and audit records so changes can be reviewed and earlier states reopened.

Activated monthly subscriptions use Stripe-hosted Checkout. Stripe handles payment credentials; Acatian stores the customer, contract, plan, entitlement, and verified subscription status required to control access. When self-service checkout is unavailable, plan actions open a technical-pilot request instead.

Request a technical pilot for one process and one decision. The pilot defines inputs, model scope, outputs, acceptance criteria, and remaining validation work before a subscription or enterprise deployment.