Self-applicable, high level, finite capacity , multi-constraints based scheduling software for industry

Process Features

Standard process

Standard Process describes all operations (activities) habitually needed to achieve the production of a product set.

Note: Sched expects the set of activities to be known before scheduling starts .

Each process operation defines the time needed for one set (declined in start-up, production and end-up time) and describes the resources allocation needed to achieve operations.

Globally for the process or separately for each operation a lot of constraints are defined

According to the process classification , resources allocation combinations could be defined for the entire process (in-line resources) . For each operation, resources allocation could be defined in association or independently of the in-line resources allocation.

Defining a Standard Process help in the creation of further Orders Processes .

Order Process

The scheduling phase doesn’t work on standard process but on order process.

Orders are created when needed with specific data (product, quantity, due date, ... and a lot more see section 10.2).

To each order is attached a specific Order Process, to create the order process easily; the operators could generate it from an existing standard process and adapt it . This operation is called PLANNED PROCESS (see 10.2).

After 'planned operation' there is a copy of a standard process with times adapted to the order demand.

The first version of the order process could be entirely modified by operators.

Note that operators could create Order Process from nothing thus entirely manually.


  1. 1) The same standard process could be used for several orders.
  2. 2) The same process could be used for several products
  3. 3) Several standard processes can be created for the same product
  4. 4) Order Process generated by Standard Process are modifiable without altering Standard Process; when created , the order process is in


Basic Process : Operations are considered as single entities, without resource transition constraint.

In production Center Process : Activities are processed sequentially in the same workshop . Introducing the transition constraint sched will examine several combinations

In-Line production Process : Activities are processed sequentially or at the same time on the same production line.. Sched will examine all the lines available and retain one.


Process Time Bound constraint (PTBC)
Entire Process must be achieved within time borders. Generally times boundaries are defined for the entire process by fixing earliest starting date/time and latest ending date/time.
The earliest starting date could be fixed or variable, depending on another process (starting after the last operation, ...).
Sched gives a way to chain several processes together.

Applied by sched.
see earliest/latest date and chaining process

- the order must be achieved to respect due date.
- the process can not start before all components are available
- the order must start after another one is completely achieved
- the process could not start before the engine maintenance achievement
OperationTime Bound constraint (PTBC)
A single operation must be achieved within time borders by fixing earliest starting date/time and latest ending date/time.
The earliest starting date could be fixed or variable, depending on another operation within the same process (starting at the' same time as another operation, ...).
Applied by sched.
see earliest/latest operation date, overlapping operations
- the operation could not be started before all components are available
- the operation could not start if production surface is made free
- the operation could start at the same time as another one, start imperatively just after, simply after,
Resource constraint (REC)
A single activity requires time capacity from predefined resources . Description is named the resources allocation.

The resource constraint describes the limits of resources in each single time cell for one operation
Resources could be common to all processes or specific to one operation in the process.
Resources are defined nominally or by defining skills.
Resources are retained according they own capacity for the considered time cell. One Resource is not retained if absent or occupied on another process according to the individual time line,(defined in the time line of each individual resource )(see chapter 3)

The resources allocation description resource has its own grammar.

Applied by sched.
see resources allocation grammar

- which engine could operate
-which tool put up on one engine could operate
- number of 'skilled' operators which could handle setting-up, production and ending-up
- how many chassis could be assembles at the same time in one workshop
- could one operator be retained with another one
Operation Time Constraint (TIC)
The time constraint describes the times needed to achieve one operation .
For one operation sched declines set-up, production-time and end-up time (each needing particular resources).
Applied by sched.
see times description
how long to set numeric command (nc), produce set of pieces and unset engine
- how long to burnish a metal piece
-how long to control a test sample
Transition Constraint (TRC)
The transition constraint binds the resources from different time cells.

Resources allocation for downstream operations must take care of resources allocation choice in upstream operations.

Apply by sched.
see 'in-line' resources and no "in-line resources

- in the case of production with several similar workshop centers. The total multi-operation production must be achieved on the same center
- in the case of production in-line (several engines are produced at the same time or not).
If one line is chosen all downstream operations are using the same line
- in the case several operations in one process use the same resource (engine or operator)
Dependency constraint (DEC)
The dependency constraint binds an activity to another one (for the same order or not).

Apply by sched.
see overlapping operations and chaining process

- the earliest beginning time for one operation is conditioned to the ending time of another one in the same process
- - the earliest beginning time for the first operation of one process is conditioned to the achievement of another process
- several operations could start at the same time
- an operation could be started before the end of the previous one


There is no limit to the operation number.

For each operation sched retain 3 time (set-up, production and end-up), non-limited no-in-line resources allocation combination, ...and a lot more

The process flow with alternatives is well described for each process classic, .

If process operations needed it you could mix basic processes type with in-line and 'production center' processes in the same standard process, but not in-line process with 'production process' type ; if you want to do so, split the single process into several ones and chain the two processes together.

Chaining order ,Overlapping process,Overlapping Operations,Splitting Operations are permitted.

Chaining order: Sched opens a way to create a chain of orders , in single files.

Overlapping process: start a process after either a specified delay or after another one is achieved

Overlapping Operations: Inside the same process operations are beginning after the precedent one is completely achieved; sched provides the way for operations to overlap. In this case operations could start in parallel id if resources are available.

Splitting Operations: By default operations are not split, single operations are done in single phases;: however certain operations could be split in several ones.

Resource allocation grammar with sched

Scheduling features

  • Resources Features : Resources - Generic Calendars - Special Events - Resource Time Line - Skills - Fictive Resources - Ratio - -
  • Processes Features : Process categorization - Constraints - Operation - Combinations - Import
  • Process Description : Combinations - Resources allocation - Grammar - Example
  • Orders Features : Production Planner - Order Process - Order Constraints - Priorities - Status - Management - Flow Choice
  • Scheduling Features : Orders Main Board - Single Scheduling - Global Scheduling - Scheduling Engine - Auto/Manual Choice - Examining Results - Scheduling Reports - Scheduling Time
  • Reports and graphics : Chained reports - Customizable reports - Graph by Resource - Gantt by Resource - Gantt by Order
  • Orders Managing : Import - Cleaning - Fixing - Updating - Export