TABLE OF CONTENTS

• Introduction
• What Can SchedEx transfer
• SchedEx Conceptual Overview
  • Connector 
  • Template
  • Config
  • SchedEx Exchange Agreement
• Key Roles and Terms in EA

Introduction

This article introduces the core building blocks of the SchedEx and explains how they work together to enable seamless schedule and planning data transfers between systems. Together, the connector, template, config, and exchange agreement form an integrated system that drives the entire process. By understanding these elements, users can better navigate and implement data transfers with accuracy and confidence.

What Can SchedEx transfer

SchedEx transfers not only the essential schedule data—referred to as Core Terms—but also additional, customizable information known as SchedEx Terms.

Core Terms

Core Terms are the foundational data fields like ActivityID, Description, Start Date, Finish Date, and % Complete. Since these values are fundamental to any schedule, they are automatically part of every transfer—regardless of how the rest of the transfer is set up.

SchedEx Terms  

SchedEx Terms provide additional flexibility by allowing the inclusion of extra schedule-related data tailored to specific project or organizational needs. Examples include Area, Discipline, Phase, and other user-defined fields.

Unlike Core Terms, SchedEx Terms are optional and fully configurable. They are managed by System Admins (the Global list of SchedEx Terms) or Tenant Admins (for tenant specific ones), and are also subject to content control rules. This helps enforce consistency, validate field values, and ensure that only acceptable data is transferred between systems.

SchedEx Conceptual Overview

Connector 

A Connector is responsible for linking SchedEx to data systems, such as a Safran Database. It retrieves schedules and user field definitions necessary for data transfer. It defines the location where a host system stores its data, including authentication information. Connectors use APIs to access planning data stored in databases or file locations. Read here to find out more about connector.

Template

Template acts as a blueprint outlining the data elements to be transferred. It includes a list of information that is included in transfers and defines what will be transferred in addition to Core Terms. Users can choose from the defined SchedEx Terms (e.g., Area, Discipline, Phase). The principle of "create once, use many times" ensures that Templates are created once and can be used multiple times. Core Terms (e.g., Description, Start, Finish) are always transferred. Additionally, Templates are shared between tenants, allowing for consistent data transfer across different system. Checkout this to learn more about templates.

Config

Config connects template to the appropriate schedules in the connector, detailing where the requested schedule information is located. If the schedules (e.g. Safran Schedules) have uniform user fields, one Config suffices; otherwise, multiple configurations may be necessary. It designates whether the configuration is for sending or receiving and applies direct mapping wherever possible (e.g., mapping Discipline to R3). More about configs click here.

SchedEx Exchange Agreement

A SchedEx Exchange Agreement (EA) enables the scheduled transfer of planning data between actors and across different scheduling systems. It is created by the Owner, who invites a Partner and determines the roles of Sender and Receiver. The Owner selects the appropriate Connector and Template, specifies the Schedule ID, Start/Finish parameters, and transfer Frequency. The agreement is finalized with signatures from both parties, triggering the automated creation of transfer events in the executing component. Learn more about EA from click here. 

Key Roles and Terms in EA

• Owner: Has the necessary privileges to create an EA. They invite the Partner for schedule data exchange.
• Partner: Participates in the EA when invited, regardless of also holding Owner privileges.
• Sender: Responsible for sending schedule data when the EA is executed. This role is assigned by the Owner.
• Receiver: Responsible for receiving data upon execution of the EA. Owner of EA decides this role
• Upload: The Sender's executing component uploads schedule data from the scheduling system to SchedEx. 
• Download: The Receiver's executing component downloads the data from SchedEx to the host system, ensuring complete importation of schedule and data.
• More definitions can be found from Glossary.