Understand Ennea
Ennea connects manufacturing information and daily work in one platform. Konnie, Ennea's AI employee, helps you find information, prepare changes, and carry out authorized tasks. Your organization decides which sites, environments, Apps, connections, and permissions you can use.
Three ways to work
| Perspective | Where | What you do |
|---|---|---|
| Build | Operations Studio | Define materials, work centers, routings, reports, Apps, workflows, and connections. |
| Operate | Apps and operational areas | Submit information, execute production, plan capacity, handle material, and review results. |
| Understand | Nexus | Find records, explore relationships, inspect activity and documents, and trace information to its sources. |
Konnie works across these perspectives. Give it a concrete goal, the relevant records, and the boundaries of the task. Review its evidence and proposed changes when review is required.
The building blocks
Master data describes reusable materials, work centers, reasons, and other definitions. A bill of materials describes required components. A routing describes manufacturing steps and resources. A recipe supplies instructions or parameters for performing work.
An App's input screen collects structured values; its source owns questions and validation. A report template defines a document's layout and data; a generated report is created from a particular context. An App brings tools together in a tailored screen. An automation or workflow connects triggers and actions so that an event can lead to subsequent work.
A production order is a specific manufacturing job. Operations and execution records describe actual work. A customer order captures demand and can be connected to production. An integration connects an external system; it does not make every external field authoritative inside Ennea.
Definitions and records have different lifecycles
Editing an App or routing changes its definition. Running an App, submitting its inputs or reporting production creates or changes operational records. Saving a checkpoint, publishing a definition, approving a proposal, and applying a change are separate actions. Read the confirmation and verify the resulting status.
Production is the operational workspace. Test is used to try configuration and workflows with the permissions and connections assigned to it. Check the scope in the header before making changes. A Test label alone does not prove that an external connection points to a test system.
Two connected examples
For a material request, a builder defines a Table and an App that saves requests directly. A separate Automation is added only when follow-up processing is needed. Operators use the published App; supervisors inspect the resulting records and follow-up. Follow the data collection tutorial.
For manufacturing, an engineer defines the material, routing, recipe, and work centers. A planner creates and schedules an order against the Factory Calendar. Operators report progress on the shop floor. Planners and Konnie use that evidence to understand the job.
Start with your task
- New users: Getting started.
- Orientation: Platform tour.
- Access: Roles and permissions.
- Help: Konnie or Troubleshooting and support.
Screens and available actions depend on your permissions, selected scope, and organization configuration. Each guide explains prerequisites that affect the workflow.