Model it. Require it. Plan it. De-risk it.

LOGOS Systema LOGOS.exe

Draw the machine on a canvas — masses, springs, shafts, volumes, orifices, pumps, turbines, heat exchangers, motors, electrical, and control parts — and integrate it in time with a stiff DAE solver.

• Real-gas and liquid property tables, pump and motor maps, missions (time histories)
• Every part checked against exact answers: analytic, energy balances, CoolProp
• Run from the command line too; compare any two runs by CSV

Detailed design, inside Systema. Design a component in depth without leaving the system model: double-click a part, size it for its duty points, check it against its limits, and apply the result — the design then drives that part in the system. A part runs at one of three levels:

• Simple — the part’s own few parameters: the quickest to run, for laying a system out. A new compressor or turbine is a diameter and a pressure ratio, with its efficiency from LOGOS’s own charts
• Detailed — its parameters come from its detailed design: geometry, analyses, checks
• Calibrated — fitted to test data: a measured map, or the design’s loss coefficients fitted to the measured points

What can be designed today:

• Centrifugal compressors, with the map and its efficiency islands; radial inflow turbines; centrifugal and Barske (partial emission) pumps
• A synchronous reluctance machine; ball and hydrostatic bearings; labyrinth, face, leaf, Halo, and annular seals
• Printed circuit and finned-tube heat exchangers
• A rotor tool for the whole shaft: critical speeds, stability, the thrust balance, and the secondary flows

Each kind has the same pages and the same three buttons — automatic design, design, calibrate to test data — and drawings whose dimensions change with a double-click. The pump, leaf seal, and Halo seal models are first cuts; the help says how each kind is worked out and what it was checked against.

Working with an AI tool. LOGOS installs a folder of read-only context files — the model file, every part, the command line, worked models that run — so that an AI tool of your own choosing can build, run, and check a model with you. A first cut. LOGOS itself contains no AI and sends nothing anywhere.

LOGOS Kanon LOGOSKanon.exe

Read the customer’s Word, PDF, or Excel specification on the PC, split it into requirements, and trace each one to its source and to the model parameter that satisfies it.

• Trace, trace table, trace chart, and VCRM views
• Verify a requirement by running the LOGOS model behind it
• No cloud, no AI service: its own document readers, on your machine

LOGOS Hodos LOGOSHodos.exe

The plan, the money, and the parts: tasks and a Gantt chart with the driving path, resources and rates, earned value, milestones with risk gates, and a bill of material built from the model.

• Export the plan to Excel, laid out like MS Project
• A board for the team; the BoM with routings and orders
• Stakeholders see hours and dates, never labour rates

LOGOS Kindynos LOGOSKindynos.exe

The risk register, the risk cube, and the burndown — with each mitigation step tied to a task in the plan, so a late task shows up as a risk that is not burning down.

• Likelihood and consequence scales your way
• Risk gates on the plan’s milestones
• Export the risk log to Excel

LOGOS Agora LOGOSAgora.exe

The window on your data pools: every model, plan, requirement, and risk versioned, with check-out and check-in, baselines, links, and a hash-chained audit log. An organisation view rolls up every project’s schedule, cost, and risk.

• A pool is one file on your own storage — no server to run
• Classification banners that can only be raised
• Verify the audit chain: it names the first row changed outside LOGOS