<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Bill of materials generation in ERP environment</title>
  </titleInfo>
  <name type="personal">
    <namePart>Tin Zaw Moe</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Hasin, M.A.A.</namePart>
    <role>
      <roleTerm type="text">Chairperson</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Bohez, Erik L.J.</namePart>
    <role>
      <roleTerm type="text">Examination Committee</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Naber, Helmut</namePart>
    <role>
      <roleTerm type="text">Examination committee</roleTerm>
    </role>
  </name>
  <name type="corporate">
    <namePart>AIT Partial Scholarship</namePart>
    <role>
      <roleTerm type="text">Scholarship donor</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="marc">series</genre>
  <genre authority="marc">technical report</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">th</placeTerm>
    </place>
    <place>
      <placeTerm type="text">Bangkok</placeTerm>
    </place>
    <publisher>Asian Institute of Technology</publisher>
    <dateIssued>1999</dateIssued>
    <issuance>continuing</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>98 p.: ill.</extent>
  </physicalDescription>
  <abstract>Developing a bill of material for a product having many optional features is certainly a cumbersome task. If a separate BOM were used for each unique end product, the file size would be too big and difficult to maintain. The solution to this problem is the modular bill of materials. This study concerns about modular bill of materials and process bill of materials. Modular bill of material, which is used for improvement of material planning, as the result the demand for modules can be forecasted separately with much more accuracy than the final configurations. Process bill of materials, which is used for delivery of components to the process in order to supply right components to the right production point, as the result, reduce the complexity and lessen the production time of the production department. Computer aided design (CAD) and manufacturing resource planning (MRP II) are two major basic paiis, which exist in manufacturing. The Part Master Record (PMR) and the Bill of Materials (BOM) information, which are common to CAD and MRP II systems. This information is entered into the MRP II system manually. The entire process is extremely time consuming and error prone. This study aims to solve the problem through integration between CAD-MRP II systems, to achieve accurate and timely exchange of information between CAD and MRP II. The use of paper for information transfer could be virtually eliminated.</abstract>
  <note>A thesis submitted in partial fulfillment of the requirements for the degree of Master of Engineering, School of Advanced Technologies</note>
  <note>Thesis (M.Eng.) - Asian Institute of Technology</note>
  <subject authority="lcsh">
    <topic>Material requirements planning</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Enterprise resource planning</topic>
  </subject>
  <relatedItem type="series">
    <titleInfo>
      <title>Thesis ; no. ISE-99-22</title>
    </titleInfo>
    <name type="corporate">
      <namePart>Asian Institute of Technology.</namePart>
      <namePart/>
    </name>
  </relatedItem>
  <identifier type="uri">http://203.159.5.9/ait-thesis/detail.php?q=B12274</identifier>
  <location>
    <url displayLabel="Full-Text">http://203.159.5.9/ait-thesis/detail.php?q=B12274</url>
  </location>
  <recordInfo>
    <recordCreationDate encoding="marc">210400</recordCreationDate>
    <recordChangeDate encoding="iso8601">20260817171405.0</recordChangeDate>
  </recordInfo>
</mods>
