---
alias: user-guide-create-data-silo
description: "This documentation outlines the process for creating a new data silo within the system"
---

# Create Data Silo

:lock: DataSilo.**Create**

## Overview

This operation is used to create a **Data Silo**.

## Setup

No specific setup is required other than to meet the preconditions of the transaction.

## Preconditions

* The **Data Silo** does not currently exist in the system.

## Sequence of Steps

1. Provide a name for the **Data Silo**.
2. Optionally, provide a description for the **Data Silo**.
3. Select the **Data Silo** type. The list of possible values is taken from the [[datasilotype-lt]] Lookup table.
4. Optionally, select the Data Version of the **Data Silo**, which should include the major, minor and patch number of the system. This field serves as a reference only. Its value is automatically maintained by the replication process and does not require manual updates.
5. Provide an Enterprise Name for the **Data Silo**.
6. Optionally, provide a Facility Name for the **Data Silo**.
7. Optionally, select whether the **Data Silo** Is External.

    !!! info "Is External Behavior"
        - When the Is External flag is disabled, the data originates from a Critical Manufacturing MES and is ingested into the Critical Manufacturing EDP instance through the standard replication flow.
        - When the Is External flag is enabled, the data originates from a third-party MES or external system and is ingested into the Critical Manufacturing EDP instance exclusively via the [[user-guide-automation-task-core-apipostevent|Post Event API]].

8. Optionally, select whether the **Data Silo** Is System. When enabled, it indicates that the **Data Silo** is system-managed.
9. Optionally, provide Keywords, which are used as metadata to support filtering, categorization, and discoverability in environments with multiple **Data Silos**.
10. Provide a Site Name for the **Data Silo**.

    !!! info "Enterprise and Site Recommended Configuration"
        In line with the ISA-95 model, Enterprise and Site should always be defined, even if the MES treats them as optional. If no value is defined, EDP will use the Enterprise and Site values provided in the incoming data.  
        When defined in the Data Silo, these identifiers are logical values used by the [[tutorials-edp|Enterprise Data Platform]] only, are not linked to MES entities, and override the values received from the MES. Defining them explicitly is strongly recommended to ensure data segregation and prevent conflicts when consolidating data from multiple MES installations.

11. Select the User associated with the **Data Silo**.

    !!! warning "One User, One Data Silo"
        A User must be associated with only one Data Silo. Associating the same User with multiple Data Silos can cause incoming data to be routed to the wrong database.

12. Select **Create** to complete the operation.

![Create Data Silo](images/create_data_silo_01.png)