High- Level Specification

Functional Overview

A Constraint is an identified limitation on the production process or supply source. This is important as they must be applied to a PartSource. Examples include equipment (such as a WorkCentre or Line, where maximum production per day would be represented), labor or people (such as staff shortages), and agreements (for example, restrictions on purchasing more than a specified amount during a calendar month).

Constraints can be expressed in any UOM (hours, kg, etc.), with conversion handled through Constraint.UnitOfMeasure and PartSource.SupplierUOM via SourceConstraint.ConstraintFactor.

Scope and Objectives

The scope of this interface is between Global Integration Suite and Maestro. This document includes details of the Constraint.tab object. 

The objective is to populate the Constraint and it's referenced tables based on the file provided by Global Integration Suite.

Process Flow Diagram

Assumptions

• Data will only come from Global Integration Suite into the Global Data Source, set up in Maestro.

Dependencies

• (SFTP) SFTP credentials needs to be set up, along with the file transfer mechanism.
• Integration suites should provide data in the format described by the Data Sources and Mapping section of this document. 

Security, Integrity and Controls

See Application Architecture Kinaxis Maestro for security requirements for SFTP/REST based authentication and security. 

Configuration Requirements

The Data Sources and Mapping for this interface should be configured once, according to the structure in the Data Structure section below. 

The Data Model needs to be configured with the Syway-specific fields shown in the Data Model Custom Fields section below.

Special Requirements

None

Design Rationale

The base of this design has been taken from the existing Maestro implementation, as designed during the Advanced Planning System (APS) Project. 

A fit-gap analysis was undertaken within Syway, and changes were identified which have been incorporated into the Syway spec as shown.

API Use

The data object provided by either Integration Suite will be consumed by Maestro.

For more information see the Data Integration Document.

Data Structure

 The following Maestro fields will be populated by the file provided by Integration Suite:

File Formats 

See File Formats - SFTP section in the Data Integration Document.

Data Model Constraint table settings:

Data Model Constraint custom fields:

Processing Logic

See Processing Logic - SFTP section in the Data Integration Document.

Delta or Full Load Requirements

The preference is to do a full load. 

For more information on the difference between Full and Delta loads, see the  Full Loads and Delta Loads - SFTP section in the Data Integration Document.

Interface Alert & Monitoring

See the Interface Alert & Monitoring - SFTP section in the Data Integration Document,

Language Requirements

None

User Interface Requirements

Not required.
 

Sequencing

Reference tables to support Constraint table data have to be either loaded manually before loading the Constraint table or at the same time as the Constraint table is loaded or set to be created automatically in data model or in DSM.

Below tables need to be taken into account before Constraint table data load:

Volumetrics

Current APS Volume of Constraint records is 85. Because APS makes up approximately 60% of Syway projected records, an expected estimate for Syway is therefore 140

This value is expected to grow by 1-2% per year. 

Performance Consideration

N/A

Error Handling

See Interface Alert & Monitoring section. 

Testing

How to Test

Testing of the interface consists of executing the data load into Maestro and validating the results using standard monitoring and validation tools. After each load, the Data Import and Update log is reviewed to confirm successful execution and to identify any errors or warnings generated during the load process.

Loaded data is then validated using a Data Validation workbook to ensure data completeness and correctness. Validation checks include confirming that required fields are populated, values are displayed in the correct format, and that data quality issues such as blank fields, incorrect quantities, or zero or invalid unit costs are not present. Additional checks may be performed to ensure consistency across key attributes such as part, location, and quantity.

Any errors or data issues identified during testing are documented in the agreed issue tracking mechanism (for example, in Jira or an action log). Most common error types  are duplicate errors, missing references, junk values in input fields. 

Duplicate errors need further investigation, in case valid data is flagged as duplicate by Maestro during data load and key field combinations have to be looked into for data uniqueness.

Missing references are to be resolved by either providing the missing data that is required to support the file upload (this could be in the form of a file or Maestro settings to allow for the data to be created automatically) or removing the references from the file.

Required corrections are implemented in the middleware (Integration Suite), and the data is reloaded. Validation steps are repeated until no errors are present (or reasons are fully understood).

Test Conditions and Expected Results 

There are no Constraint-specific test conditions.

Test Considerations/Dependencies

Dependent files should already be loaded into Maestro for these tests to complete. See Sequencing section above. 

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

Change log