Finite-Scheduling

Document Sample
Finite-Scheduling Powered By Docstoc
					VENDOR :

Printed on : 11/27/2009

Basic Requirements for a Finite Capacity Scheduling Package
Issue Activity Yes / No Alternative Solution

Operation

Operation

Should consider committed production jobs in ERP system in generating finite scheduling. Be able to regenerate total schedule or perform net change of frozen planned orders. All jobs identified by job number, lot number and reference tags. This is to enable to users to retrieve info. as to the status of specific jobs by the combination of one or more of these fields. Eg. if lot number 11063 has been inquired, system should bring all the information starting with this lot number, such as 11063A, 11063B etc., similarly with job numbers and reference tags.

Be able to move jobs on line and instantly display resource loading. (Graphically and numerically.) This is an essential feature to allow users to be able to peg into resources to analyze to load jobs and move selected jobs to balance the loads. Be able to interactively change demand, capacity or constraints to Operation test various business scenarios. For selected jobs and its respective stages, user be able to lock Operation start or completion dates and the system work around this in rescheduling. Ability to finite schedule jobs where operations are performed in Modeling more than one physical location, i.e. jobs floating in and out of / more than one location. Algorithm Operation Features to incorporate prioritized multiple routings for given Modeling product and finite schedule accordingly in the event of capacity contention. System should suggest possible solutions in case of contention. Modeling System scheduling and optimization should be able to incorporate batch production and discrete production.

8cfdac60-826a-4efd-8e8e-9c661a431658.xls / Finite Scheduling : ALL TRANSACTIONS AND SPECIAL ERROR LOGS ARE TO BE MAINTAINED IN AUDIT TRAIL AND BE RETRIEVABLE. NOTE Page 1 of 4

VENDOR :

Printed on : 11/27/2009

Basic Requirements for a Finite Capacity Scheduling Package
Issue Activity Yes / No Alternative Solution

This will have the functionality to work with standard (minimum and multiple) batch sizes and maximum batch sizes (to estimate change over / clean up /set up times etc.) If necessary, should be able to solve for lot size, sequence, Modeling coordination of multiple operational steps and sourcing simultaneously. If necessary should be able to represent inventory storage Modeling capacity as a constraint in a time-phased manner. Either dedicated or warehouse storage should be available. If necessary should be able to represent labor as a constraint in a time-phased manner. If necessary should be able to represent raw materials or Modeling purchased components as a constraints in a time-phased manner. Modeling System should recognize different setup and clean up (changeover) times depending on the product mix. Ability to attach priority codes to jobs and/or reference tags and Modeling applied to finite scheduling in prioritizing job schedules. System should be able to lock a particular manufacturing room/area as a resource center. That is if there are more than one Modeling machine in one room, it might have to be defined that more than one job cannot utilize that room at any given time. If more than one machinery is located in one room, system should recognize this as a capacity restriction and should not allow to allocate that room for more than one job at any given time. Modeling System to provide optimized schedule based on the criteria defined by the user. User defined criteria, e.g.. Cost, customer priority, job priority etc. Modeling Prompt material shortages in a time phased manner. Modeling

Generate schedule in ASAP or JIT modes.

Arbitrary criteria may require some customization

8cfdac60-826a-4efd-8e8e-9c661a431658.xls / Finite Scheduling : ALL TRANSACTIONS AND SPECIAL ERROR LOGS ARE TO BE MAINTAINED IN AUDIT TRAIL AND BE RETRIEVABLE. NOTE Page 2 of 4

VENDOR :

Printed on : 11/27/2009

Basic Requirements for a Finite Capacity Scheduling Package
Issue Activity Yes / No Alternative Solution

For all categories of jobs the system be able to prompt any material shortages respective to the process. Ensure expiry dating are considered by the lot numbers for the material, and therefore appropriately included in the material availability/shortages. Similarly, the material being released into stock be included in the calculations in time phased manner. Modeling Default calendar feature for work centers/machine centers. Modeling Multiple calendars for work centers/machine centers. This is to enable different machines to have different work shifts potentially. Ability to lock specified jobs/stages to expected start or completion Modeling dates. Display and print Gantt chart of all the process steps for selected Interface products/jobs and/or work centers/machine centers. Ability to "click on" job and display other pertinent information Interface such as description, quantity etc. Simulations for viewing and listing with introduction of new jobs, Interface changes to expected dates etc. Simulations should be stored with different (file name/retrieval codes) name and can be available for modifications. On viewing, users should not lock each other out, i.e. multi-user viewing capability. Interface Inquiries and reports to include and not be limited to: Detail load by work center/machine center either as for specified, range or globally. Detail job status for selection by product range and/or date range by stages/operation. Exception reporting/display, of loads, for machine/work centers for specified ranges of load values. Scheduling periods and ranges should be defined by users for Interface generation and inquires. Interface
8cfdac60-826a-4efd-8e8e-9c661a431658.xls / Finite Scheduling : ALL TRANSACTIONS AND SPECIAL ERROR LOGS ARE TO BE MAINTAINED IN AUDIT TRAIL AND BE RETRIEVABLE. NOTE Page 3 of 4

VENDOR :

Printed on : 11/27/2009

Basic Requirements for a Finite Capacity Scheduling Package
Issue Activity Yes / No Alternative Solution

Users should be able to inquiry online (or print) for periods defined such as on daily, weekly buckets etc.

8cfdac60-826a-4efd-8e8e-9c661a431658.xls / Finite Scheduling : ALL TRANSACTIONS AND SPECIAL ERROR LOGS ARE TO BE MAINTAINED IN AUDIT TRAIL AND BE RETRIEVABLE. NOTE Page 4 of 4


				
DOCUMENT INFO
Shared By:
Tags: Finit, e-Sch
Stats:
views:47
posted:11/28/2009
language:English
pages:4
Description: Finite-Scheduling