<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02997ntm a2200289 a 4500</leader>
  <controlfield tag="001">vtls000098148</controlfield>
  <controlfield tag="003">KUKTEM</controlfield>
  <controlfield tag="005">20251117113437.0</controlfield>
  <controlfield tag="008">161123t2016    my a   f m    000 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">THE0007812(Local)</subfield>
  </datafield>
  <datafield tag="039" ind1=" " ind2="9">
    <subfield code="a">201906131130</subfield>
    <subfield code="b">nadia</subfield>
    <subfield code="c">201712141637</subfield>
    <subfield code="d">saini</subfield>
    <subfield code="y">201611231125</subfield>
    <subfield code="z">fateeha</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">UMP</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">FKASA .A35 2016 r Bc.</subfield>
  </datafield>
  <datafield tag="100" ind1="0" ind2=" ">
    <subfield code="a">Muhammad Afiq Hasmi</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Building information modeling (clash detection and analysis for architecture &amp; structure discipline in BIM) /</subfield>
    <subfield code="c">Muhammad Afiq Hasmi</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Kuantan, Pahang :</subfield>
    <subfield code="b">UMP,</subfield>
    <subfield code="c">2016</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xii, 42 p. :</subfield>
    <subfield code="b">col. ill. ;</subfield>
    <subfield code="c">30 cm. +</subfield>
    <subfield code="e">1 CD-ROM</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Faculty of Civil Engineering and Earth Resources</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Project Paper (Bachelors of Civil Engineering) -- Universiti Malaysia Pahang &#x2013; 2016</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Bibliography : p. 41-42</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Building information modelling (BIM) is one of the most promising recent developments in the AEC industry. With BIM technology, an accurate virtual model of a building is digitally constructed. This model, known as a building information model, can be used for planning, design, construction, and operation of the facility. In construction industry, one of the key that lead to the successfully of a project is a good and effective coordination of the time and the cost of the project that can be made during the pre-construction phases where it is called as design phase. In this phases, clash detection in 3D coordination are the most important step that need to be done in this BIM implementation to save an expansive cost of changing construction at site and to avoid the delay of time consuming in construction project. Nowadays, coordinator in Malaysia still rely with 2D construction drawings for all disciplines. This 2D construction drawing generally is been generated by CAD software which are lack of information that are requirement for the coordinator. In clash detection, the processes take a time of finding where the model clash. It means that elements of separate models occupying the same space, or with parameters that are incompatible, or in 4D BIM modelling, a time sequence that is out of order. Finding this inconsistence is vital, as they would severely impact the construction process, causing delays, design changes, materials costs and a cascade of headaches and budget overruns. The methodology of this research are beginning from the collection of raw data of a 2D CAD drawing until it finishes to the last that is the output of the research. The output of this research is the report of clash detection that will run through this research.</subfield>
  </datafield>
  <datafield tag="610" ind1="2" ind2="0">
    <subfield code="a">Faculty of Civil Engineering and Earth Resources</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Universities and Colleges</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Theses</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">http://ecollib.ump.edu.my/id/eprint/25581</subfield>
    <subfield code="z">Access in library only</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="8">REF</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">FKASA .A35 2016 r Bc.</subfield>
    <subfield code="p">0000115037</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="8">REF</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD 10242 | FKASA .A35 2016 r Bc.</subfield>
    <subfield code="p">0000115038</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VIRTUA40</subfield>
    <subfield code="c">8750</subfield>
    <subfield code="d">8756</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VTLSSORT0080*0200*0400*0900*1000*2450*2600*3000*5000*5020*5040*5200*6100*6500*6501*8560*9992</subfield>
  </datafield>
</record>
