24Flow Data structure

Overview

1. Green: Represents master data typically sourced from the ERP system. This includes foundational data such as products.

2. Purple: Indicates master data maintained directly within 24Flow. This data is specific to the workflow and optimizations managed within the 24Flow platform, such as specific production configurations or custom routings tailored to the manufacturing process.

3. Grey: depends on project setup decisions, determining whether Production Type and Operation Type and assigments reside in the ERP system, 24Flow, or a combination of both. This flexibility allows for configuration based on the specific needs of the manufacturer and the system integration approach.

Master data

Refers to the essential, static information that forms the backbone of efficient production management for high-mix, low-volume manufacturing. In 24Flow, master data includes critical details such as products (materials and components), production types (operation sequences), and teams (work centers).

This data ensures seamless integration across processes like scheduling, execution, and tracking within 24Flow’s environment. By maintaining accurate and consistent master data, 24Flow enables manufacturers to optimize workflows, improve decision-making, and ensure compliance with quality and production standards, empowering them to operate more effectively and efficiently.

For a complete list of object fields we refer to the 24Flow API documentation: https://api-docs.24flow.eu/#/

Account

Account fields

Salesforce entity: account fields

Product

Product fields

Salesforce entity: product fields

Team

Team fields

Employee

Employee fields

Employee Team

The Employee Team link enables an employee to be associated with one or more teams, allowing flexibility in assigning employees to multiple teams based on their roles, skills, or responsibilities.

Employee Team fields

Equipment

Operation type

Operation types define how a task is performed, the resources involved (e.g., machines, teams), and the outputs expected.

Common Operation Types:

1. Machining Operations: Processes that remove material to shape a part, such as drilling, milling, or turning.

2. Assembly Operations: Tasks where components are joined together, such as welding, screwing, or fastening.

3. Fabrication Operations: Methods that transform raw materials, like cutting, bending, or forming.

4. Inspection Operations: Steps to verify quality, measurements, or conformance to standards.

5. Finishing Operations: Processes that enhance the surface or appearance of a product, such as painting, coating, or polishing.

6. Packaging Operations: Preparing products for shipment or distribution.

Operation type fields

Operation Type Example

Production type

Acts as a production blueprint for one or more products. A production type represent the workflow, collection, of operation types.

Production Type Example

The MTO vessel production type describes the production process of a simpel vessel, this wil be extended in the next section.

Operation type assignment

This relationship ensures that operation type follow the correct sequence for the associated production types while allowing for specific overrides to adapt to unique product requirements.

Operation type assignment fields

Operation type assignment contains the same fields as operation type.

Operation Type Assignment Example

In the example above, multiple operation types are linked to a production type via an Operation Type Assignment. This assignment allows you to override the default settings of an operation type for specific production scenarios.

For instance, when a MTO Vessel production type is used in a production order, the touch time for the sawing operation is adjusted to 40 minutes, overriding the default setting of 60 minutes. The default team of the milling operation is adjusted to M2.

Operational data

Production Order

A Production Order is the operational execution of a specific Production Type, representing a real-time instance where the defined processes, resources, and materials are applied to manufacture a product.

Production Order Fields

Fields listed above are the key fields which are often used, see API documentation for the complete list.

Operation

Is an instance of an operation type assignment configuration. It is possible to directly retrieve operations for a specific production order from an ERP system without the need of the operation type assignment blueprint.

Operation Fields

Operation Product

A component within a production order that defines the specific product or material being processed during an operation. It links the operation to the item being manufactured or transformed, ensuring accurate tracking and alignment with production requirements.

Operation Product Fields

Operation Routing

A production order consists of multiple operations. Each operation has a sequence number and is assigned to a specific team. To optimize the workflow, operations that are assigned to the same team and are sequentially connected can be grouped together into an "operation routing."

For example:

• Operation 1: Sequence 10, assigned to Team 1

• Operation 2: Sequence 20, assigned to Team 1

• Operation 3: Sequence 30, assigned to Team 2

In this case:

1. Routing 1: Groups Operations 1 and 2 under Team 1 because they share the same team and are sequential.

2. Routing 2: Starts with Team 2, containing Operation 3, and has no subsequent team assignment.

This approach ensures operations are logically organized based on team responsibility and sequence, streamlining production processes.

Operation Routing Fields

Time Activity

A Time Activity describes the specific type of work performed during a time entry. It categorizes labor or machine time such as ‘Setup,' 'Production,' or 'Training’.

Time Activity Fields

Time Sheet & Time Entry

A time sheet is a collection of related time entries. It typically aggregates the entries of a specific employee on a specific day, or compiles all entries for a complete production order to facilitate cost calculation. Time sheets can be linked to status approval processes. A Time Entry is linked to a Time Sheet via a Time Sheet Entry. This intermediate object resolves the many-to-many relationship between the two entities.

For example, workers John and Andy each work 4 hours on Production Order A on Monday. On Tuesday, only John works 2 hours on Order A.

Time Sheet Fields

Time Entry Fields

Time Sheet Entry Fields

Operation Output Trace

When detailed output registration is required, output traces are used to track individual entries of produced goods at the production order and operation level. When time tracking is enabled, these traces include a reference to the associated employee time entry.

For example, an operator starts time tracking on Production Order A from 8:00 AM to 11:00 AM. During that period, they produce one piece every 30 minutes, resulting in detailed tracking information.

Operation Output Fields

Operation Input Trace

When detailed input registration is required, input traces are used to track individual entries of consumed goods at the production order , operation and operation product level.

As an example, an operator consumes a sensor during the assembly of an electrical module on a specific production order.