2.7.6
General
General · 21 fields · 21 with a value
- Altnamealtname
- Master Production Scheduling (Finite Scheduling)
- Baserecordtypebaserecordtype
- customrecord_ns_imp_req_module
- Customformcustomform
- Module Form
- Isinactiveisinactive
- No
- Lastmodifiedlastmodified
- 8/2/2018 11:38 am
- Linenumberlinenumber
- 25
- Module descriptioncustrecord_ns_imp_module_description
- Master production and finite scheduling applies business rules and scheduling logic (defined relative to assigned assembly items and manufacturing routings) to determine the production schedule start date of each modeled operation of the manufacturing process. A scheduling engine is designed to resolve constraints and maximize capacity utilization, but a Planner may also review and edit its output to further optimize the production schedule. The Master Production Schedule optimizes each Work Order's scheduled start date based on the available Work Center capacity in relation to each operation of the manufacturing routing. Alternate assets may be assigned for any operation allowing for concurrent execution across multiple Work Orders. Assets will be scheduled according to their order of assignment to the operation. Work Order and Operation dependencies are evaluated using lead times that can be defined as either "fixed" (i.e. a predefined time offset) or "relative to production output" (i.e. a specified number of units having been completed in the prior operation). Previously scheduled Work Orders can be held firm as a pre-existing capacity constraint or can be rescheduled. Scheduling priority is assigned to Work Orders based upon their order when submitted to the scheduling engine. This order can be controlled by a number of sorting mechanisms including: ¥ Age ¥ Planned Date ¥ Schedule Code - a code that can be used to set scheduling priority to an assembly item ¥ Production Calls - see above ¥ Planning Code - a code available to planners for ad-hoc grouping (e.g. Build-to-Stock, Rush Order, etc.) ¥ Quantity Schedules may be previewed using several representations for evaluation prior to adopting the new start and end dates for Work Orders. The views include: ¥ Group by Work Order ¥ Group by Work Center ¥ Group by Asset ¥ Operation Task List ¥ Asset Utilization List ¥ Annotated Timeline ¥ Machine Hours Calendar Once reviewed the Work Orders may be "scheduled" which will record each Work Order's start and end dates as well as recording the scheduled start and end dates of all Operations. Optionally, the NetSuite start and end dates for the Work Order may be updated to influence Demand Planning.
- Module processcustrecord_ns_imp_module_process
- 2 Design to Build
- Namename
- 2.7.6
- Ownerowner
- Mihir Bhatnagar
- Owneridownerid
- 7
- Parent modulecustrecord_ns_imp_parent_module
- 2.7 Advanced Manufacturing
- Recordidrecordid
- 75
- Rectyperectype
- Module
- Rectype 242 1695 maxnkeyrectype_242_1695_maxnkey
- 258
- Scriptidscriptid
- value_54221_t1247005_742
- Submitnext tsubmitnext_t
- customrecordentry
- Submitnext ysubmitnext_y
- 242
- Templatestoredtemplatestored
- No
- Typetype
- custrecordentry
- Versionversion
- 3
System & IDs
System & IDs · 12 fields · 8 with a value · 4 empty
- Customform refidcustomform_refid
- 102
- Entryformquerystringentryformquerystring
- rectype=242&e=T&id=75
- Idid
- 75
- InternalIdInternalId
- 75
- Module process refidcustrecord_ns_imp_module_process_refid
- 2
- Owner refidowner_refid
- 7
- Parent module refidcustrecord_ns_imp_parent_module_refid
- 69
- Rectype refidrectype_refid
- 242
No value 4
- Customwhencecustomwhence
- —
- Externalidexternalid
- —
- Nsbrowserenvnsbrowserenv
- —
- Selectedtabselectedtab
- —
No field matches your search.
Fields without a value are shown as “—”.