- 3D configuratorauthoring works
- Generatorin development
- Monitorin development
- adapterERPexisting
- adapterCRMexisting
- adapterMESexisting
- adapterWMSexisting
- adapterAccountingexisting
- adapterMissing systemadded via contract
Systems, kept or replaced
A system the company runs may stay or be replaced by a better one, the ERP included; the engagement decides this per role. A system that stays gets an adapter that translates its data to the role's contract and back, and people keep working in it as before. When the company lacks a system of some kind, one is added through the same contract, from whichever vendor suits the company.
Phenome itself is not an ERP. An engagement may keep the company's ERP, replace it or build a new one, and the chosen ERP connects through an adapter like any other system.
Handbook of contracts
The contracts between modules are described in an open handbook, currently draft 0.2. It maps 32 responsibilities and 24 boundaries between the modules of a manufacturing company to existing standards such as ISA-95 and OPC UA. The handbook is to be published under the MIT licence and has no public address until then.
Public code
The geometry kernel is written in C# for .NET 10 and has 571 automated tests. It runs on servers and in the browser as WebAssembly. The code is on GitHub under the MIT licence: https://github.com/theObjectCo/PhenomeKernel.
Phenome Link pairs an AI agent with the live Grasshopper canvas on which configurator prototypes are sketched. Its code is public under the MIT licence as well: https://github.com/theObjectCo/Phenome.