The
most common processing of the Noah system works in
three simple stages:
Default
& System Definition
The first stage consists of default definition., including:
Global daily defaults, Holidays, Workcenters defined,
and exceptions list (for automatic reporting on delays
at workcenters).
Build
& Schedule Jobs
Then
Jobs are 'Built' with Customer name, Job Number, start
date, and a super easy method for sequencing workcenters.
Next, the newly built Jobs are sequenced and schedules
are created.
The
user has the freedom to try various quantities, with
alternate start dates, and view the resultant summaries
of resource requirements and schedule dates. It is
in this phase that capacity constraints are revealed
-- as well as when labor and machine resources should
be scheduled.
Each
schedule can either be viewed on screen or printed.
The result of this second phase is an accurate production
plan start and stop dates, and critical time path
to successfully meet due dates.
Execution
The third and final stage consists of using and reporting
on the schedules created in stage two.
By
design, Noah does not require updates to actual schedule
- but allows you 'by exception' to flag jobs that
are delayed and report on the cumulative effects of
all delays.
When
the exceptions (or any other event) warrant that some
Jobs need to be rescheduled, Noah features an easy
single click method to remove one or more Jobs from
existing schedule, arrange new priority, and reschedule.
Easy shipping and comprehensive reporting round out
the Noah system.