FASTREACT
All MM Executive _M
* Means All
Only Incomplete Event
without time table Date
Unknown
M
in
us
on
ly
1p
co
rd
er
qt
y
Minus/Reduce
visio rm
nal
nfi
Min only Co
P ro
,
us
de r
Or
Load List Job
Scrolling Tab
Job Search
Save
Capacity Blank
[Link] Time Table
Stri
p
Ev
en
t
ate
1.A
a rget D
dd
nt t
Eve
ow
Or
le & Sh
de
imetab
rR
dT
r Ad
ef.
Afte
against Single Job
There is various Strip
Low Level Planning Board :
Allowing detailed line level planning taking into account product type efficiencies,
learning curve efficiencies, order and strip efficiencies.
Generates schedules for pre and post sewing secondary operations including the ability to
monitor the load vs. capacity of these secondary operations, which are linked to the sewing
plan
Plan Row
Refers to a production line or any low level entity planned by the factory
Primary Operation (Planned Operation)
Refers to the production (process) which is planned and considered as the main capacity
constraint in the factory, commonly Sewing
Strip
Refers to planned orders. This can be a full order or part of an order as bigger quantities are
split into multiple plan rows.
Secondary Operation
Refers to “other” supporting operations planned within FR e.g. cutting, embroidery, etc.
Standing Time
Amount of time (in days) required between different production processes.
Throughput Time
Days between Sewing feed on and production end
Timetable Templates
List of events that need to take place before production of an Order can commence. Unlimited
timetables templates can be created considering customer, responsible person and order lead
time etc.0
Offset Days
Number of days required to completed an event based on pre-defined logic. Example: Fabric
needs to receive 5 days earlier of cut start date. Here 5 is the
offset days.
Order Event base Date
Order Event base Date means OPD Date.
Target Date
An event’s required complete date based on critical path / T&A template.
Example: Fabric need to receive 5 days earlier of cut start date. If Cut start date is
10 January, then fabric receive target will be 5 January based on template.
Expected Date
When event target date is not achievable, possible completion date can be entered. Example:
Fabric receive target date is 5 January. However, due to supplier delay fabric will be received
on 7 January. This date need to enter on Expected date so that all relevant personnel get the
latest update.
Retained Date:
Agreed target date. This date is manually saved once target dates are agreed with relevant
stakeholders. Retained date is required when target date is generated based on production
plan. “All Retain target date are target date, but all target are not retain.” Retain target date
means, target date which are save for fixed plan.
Launch Date : FastReact you have to manually enter the "Launch date" against each
product, by using this option FastReact will automatically set the launch date to the earliest
planned strip for the product.
On Time Delivery Performance (OTDP)
Cut To Ship (CTS) ratio,
Overall Lead Time (OLT)
Work in Progress (WiP)
Critical Path
Event Flow Process is called Critical path
Order Event Base Date
Order Event Base Date means OPD date
Order and Products Details
Products-Means Job-FFL-23-01452
Order Number-00000-4519-23-01452::09-090[A]::1
Item-3PACK
Style-BRN TSHIRTS
Pre-Production Plan Board
• This Planning Board shows the critical path activities driven by the application of a
Critical Path Timetable to Orders and Products.
• Planning Board
• Sorting
• This can be further re-orientated based on the User selections from the menu bar at the top
of the dialog, thus:
• By Order, Event, Due Date
• By Event, Due Date
• By Exec, Due Date
• By Customer, Exec, Event, Due Date
• By Supplier, Order, Event, Due Date
• Further refinements based on the following options are possible:
• All events
• All incomplete events
• Late incomplete events
• All complete events
High Level Plan Board
The High Level planning board allows the Planner to plan their orders into groups such as Factories or
Subcontractors.
1. Load list
2. Grid Style Load List
3. Planning board
4. Drop Down Planning Board
5. Traditional Planning Board
6. Moving Orders
7. Loading charts
8. Tool bar
9. Find function
10. High Level Right Click Functionality
1. Load list
The load list will show orders still to be planned. If the user does not have
rights to plan orders they will still be able to view the load list.
The Load list contains a list of orders that have still to be planned on the High
level planning board. The list contains the following columns of information
• The Load list contains a list of orders that have still to be planned on the
High level planning board. The list contains the following columns of
information
Order Code
The order reference is preced
colour (if any) associated with
reference itself. There may b
order if that order has multipl
of this entry will your normal
However, in systems which
reference will show you that
level planning board, but that
Product
A rectangle showing the colo
this product, followed by the P
Product type
The product type associated w
Customer
A rectangle showing the c
followed by the Customer refe
Delivery
The delivery date for this part
Note:
An order can have multiple de
Quantity
The balance to make of this
can be in the load list even if p
Description
This is the description of the
which you want to show in the
The Load List can be sorted b
columns, except quantity, are
delivery quantity is sorted so
the table.
• High Level Planning Board
• The planning board occupies the top half of the High level plan and shows individual
orders represented by coloured strips running across the screen. The left hand side of the
screen shows information about each order whilst the body of the planning board shows
where each order is planned.
• High level board display types
• There are two ways in which the High Level Planning Board can be visualised.
• Traditional High Level view.
• Drop Down High Level view.
• A description of each of these views can be found by following the links above.
UDF-User Define Field
Strip Color Codes
[Link] colour
[Link] colour
[Link] colour
Capacity Blank
TNA Fail,Planning Delay
Holiday OT
No Problems –on time
TNA Fail
That need to be planned first
late for delivery, delivery tolerance
Low Level Planning Board
Capacity Blank
Early planned
Learning Curve Applied
Strip not Added
Monthly_Weekly Breakdown