<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-26T01:30:15Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/8309" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/8309</identifier><datestamp>2022-01-13T07:54:23Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Feniosky Peña-Mora.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">McCone, D. Sean</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Civil and Environmental Engineering.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Civil and Environmental Engineering</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-08-23T19:04:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-08-23T19:04:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2002</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2002</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/8309</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">50445583</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 2002.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Page 168 blank.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 160-167).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">One of the most important, but often overlooked steps in developing a project is a plan to prevent and handle conflict, a Conflict Management Plan. Leading construction experts have identified Productivity, Innovation, Cost Control, Safety, and Litigation Expenses as critical areas in need of improvement in the construction industry of this next century. In the United States alone, $60 billion are spent every year on lawsuits, of which the construction industry accounts for nearly $5 billion. Various dispute avoidance and resolutions techniques are presented that aim to prevent disputes before they arise and minimize the impacts if they do. These techniques are the tools then used in the Conflict Management Plan. A Conflict Mitigation Plan looks at each project individually to establish a set of criteria for controlling conflicts. It assesses how much conflict you will encounter, how severe each conflict might be, then presents cost effective ways to avoid conflict and curb these disputes. Similar to the contract documents it should be complete, unbiased, understood, and accepted by all the parties involved. All of the project participants such as the owners, the owner's representatives, designers, lawyers, and contractors are responsible for designing, reviewing and revising it accordingly. No one person or field should be responsible for developing this plan. Designing a conflict mitigation plan compels the owner to contemplate the conflict that might arise. This will allow the owner to allocate these risks and develop a plan to handle discrepancies. By doing this upfront and with each subsequent review, everyone involved has agreed to follow this plan, reducing the push for lengthy, costly court proceedings. To implement a Conflict Management Plan one must assess the project situation by identifying the sources of conflict that might occur, then analyze the severity and impact each of these conflicts might have. Match the conflict with a corresponding DART, to reduce or avoid the conflict. Draft the plan. Review and revise it as needed.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by D. Sean McCone.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">168 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">15289100 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">15288857 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Civil and Environmental Engineering.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Dispute resolution strategies for construction projects</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="de0efd8b-b62f-4892-b052-764f14f1dec4">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>Dispute resolution strategies for construction projects&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2002&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName&gt;McCone, D. Sean&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Civil and Environmental Engineering.&lt;/Keyword>
   	&lt;Abstract>One of the most important, but often overlooked steps in developing a project is a plan to prevent and handle conflict, a Conflict Management Plan. Leading construction experts have identified Productivity, Innovation, Cost Control, Safety, and Litigation Expenses as critical areas in need of improvement in the construction industry of this next century. In the United States alone, $60 billion are spent every year on lawsuits, of which the construction industry accounts for nearly $5 billion. Various dispute avoidance and resolutions techniques are presented that aim to prevent disputes before they arise and minimize the impacts if they do. These techniques are the tools then used in the Conflict Management Plan. A Conflict Mitigation Plan looks at each project individually to establish a set of criteria for controlling conflicts. It assesses how much conflict you will encounter, how severe each conflict might be, then presents cost effective ways to avoid conflict and curb these disputes. Similar to the contract documents it should be complete, unbiased, understood, and accepted by all the parties involved. All of the project participants such as the owners, the owner&amp;apos;s representatives, designers, lawyers, and contractors are responsible for designing, reviewing and revising it accordingly. No one person or field should be responsible for developing this plan. Designing a conflict mitigation plan compels the owner to contemplate the conflict that might arise. This will allow the owner to allocate these risks and develop a plan to handle discrepancies. By doing this upfront and with each subsequent review, everyone involved has agreed to follow this plan, reducing the push for lengthy, costly court proceedings. To implement a Conflict Management Plan one must assess the project situation by identifying the sources of conflict that might occur, then analyze the severity and impact each of these conflicts might have. Match the conflict with a corresponding DART, to reduce or avoid the conflict. Draft the plan. Review and revise it as needed.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>