100%(1)1 out of 1 people found this document helpful
This preview shows page 15 - 17 out of 43 pages.
Figure2.19assumes that, generally, a givenpart can be stored in different ways (i.e., differentstorageforms),forexample,onpalettesorstacked on a shelf. Storage locations are usuallybroken up into storage places that allow certaintypes of storage forms.2.1.4Dealing with Missing DataIn describing the MRP master data, we haveassumed that either these data already exist ortheorganizationpossessesallinformationPart(1,)(0,)is aorInhouse partPurchased partSupplystructureConditionsSupplier(0,)(0,)Fig. 2.18ERMconnecting parts andsuppliers2.1Master Data for MRP33
needed to create the data. This assumption isusually satisfied when the organization is similarto the type described in the beginning of thechapter: producing a standard production pro-gram in mass or large-series production basedon well-defined product structures and well-known demand curves and stocking the products.Whenever customers are directly involved,the situation can be very different. Inmake-to-order production, the end products are often notpredefined, but specified by the customer. Forthese products, the company will usually nothave master data, unless the product has beenbuilt in the same way before. Inindividualmake-to-orderproduction,andespeciallyinindividual one-time production, the part andproduct structure data often have to be createdjust for the specific customer order.This does not necessarily mean that everysingle part going into a customer-specific endproduct has to be designed from scratch. Make-to-order manufacturers also strive to use standardparts as much as possible, because it is moreeconomical. A typical situation is therefore thatthe higher levels of a product structure exhibitnew (i.e., customer-specific) parts, whereas onthe lower levels, standard parts are found. Forstandardparts,masterdataexist,butforcustomer-specific parts, this is not the case.Normally, an ERP system will require thecompany to create complete master data beforeany planning based on these data can be done.However, many make-to-order manufacturers arereluctant to make the effort of establishing newparts and product structures because their organi-zation requires elaborate administrative processesfor introducing (and approving) new parts.On the other hand, an ERP system cannot doanyplanningwithouttheunderlyingdatastructures. Therefore, at least some of the datahave to be entered in one way or another. TheERP system can support this work effectively byproviding adequate assisting features, including:•Powerful copying and editing functions allow-ing existing part or product structure data to becopied and modified to suit the present needs•Temporary parts and product structures whichdo not have to meet the same requirements asother database objects•Product structures which reference incompletepart master data•Planning features that exploit similarity (i.e.,planninginanalogytoprevioussimilarorders)PartAssigned to(1,)Storage formStorage placeStorage location(0,)Assigned to(1,)(1,)