    <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
     <channel>
        <title>CoalSync :: The CoalSync Advantage</title>
        <link>http://coalsync.com/public/</link>
        <description>Synchronising the Coal Supply Chain in Partnership with Coal Producers</description>
        <dc:language>en-us</dc:language> 
        <dc:creator>Administrator</dc:creator> 
        <admin:generatorAgent rdf:resource="http://www.xaraya.org" /> 
        <admin:errorReportsTo rdf:resource="mailto:site.admin@coalsync.com" /> 
       <sy:updatePeriod>hourly</sy:updatePeriod> 
       <sy:updateFrequency>1</sy:updateFrequency> 
       <docs>http://backend.userland.com/rss</docs>

<div>
You are here:            &gt;&gt; <a href="http://coalsync.com/public/index.php/xarpages/home" title="Welcome to CoalSync">home</a>
            &gt;&gt; <a href="http://coalsync.com/public/index.php/platform" title="The Platform">platform</a>
            &gt;&gt; <span title="The CoalSync Advantage">advantage</span>
</div>

<div>
Pages in this section:                <a href="http://coalsync.com/public/index.php/platform/challenges" title="Coal Chain Challenges">challenges</a>
                <a href="http://coalsync.com/public/index.php/platform/solution" title="The CoalSync Solution">solution</a>
                <span title="The CoalSync Advantage">advantage</span>
</div>


    <div style="margin: 1em; padding: 1em; border: 1px solid #aaaaaa;"><h2>CoalSync Advantage</h2> 
<table border="0" cellspacing="1" cellpadding="3" style="border-width: 0px">
	<thead>
		<tr>
			<th scope="col"> </th><th scope="col">
			<h3> Pros</h3></th><th scope="col">
			<h3>Cons </h3></th>
		</tr>
	</thead>
	<tbody>
		<tr valign="top">
			<td>
			<h4>Simple  Quota System</h4>
			<p>
			(Spreadsheet or manual process - e.g. DBCT Queue Management System)
			</p>
			</td>
			<td>
			<p>
			<strong>Simple, quick to implement</strong><br />
			Can be implemented relatively quickly, through something as simple as a spreadsheet.
			</p>
			<p>
			<strong>Reduces congestion<br />
			</strong>Limiting access can provide quick gains in reducing queues.  
			</p>
			</td>
			<td>
			<p>
			<strong>Reduces Throughput</strong><br />
			Quotas only limit peaks in demand, they don&#39;t provide a mechanism to make up lost capacity when a producer doesn&#39;t fully utilise their allocation. The actual throughput will always be lower than the reduced quota.
			</p>
			<p>
			<strong>Reduces Flexibility</strong><br />
			Fixed quota periods &quot;partition&quot; capacity, and limit the ability of exporters to follow natural peaks and troughs in production (e.g. can&#39;t carry over allocations from one period to the next after maintenance periods etc.).
			</p>
			</td>
		</tr>
		<tr class="xar-alt" valign="top">
			<td>
			<h4> Logistics Executive</h4>
			<p>
			(e.g. Hunter Valley Coal Chain)
			</p>
			</td>
			<td>
			<p>
			<strong>Can take a &quot;whole of chain&quot; view</strong><br />
			An executive team can operate the coal chain with visibility of the whole chain.
			</p>
			<p>
			<strong>Increase throughput</strong><br />
			Logistics team increases chain throughput by executive decision making at an operational level.
			</p>
			<p>
			<strong>Reduce demurrage</strong><br />
			Logistics team decreases demurrage,  through direct operational management of the chain.
			</p>
			</td>
			<td>
			<p>
			<strong>Slow to implement<br />
			</strong>A logistics executive needs to have representation or trust of all stakeholders. Issues such as independence, governance, and ownership can draw out the initial change process. 
			</p>
			<p>
			<strong>Costly to set up<br />
			</strong>The executive needs to be housed, staffed and provisioned with support tools, making it costly to establish.
			</p>
			<p>
			<strong>Reduced transparency</strong><br />
			Operational decision-making is carried out by the executive, on behalf of stakeholders. Stakeholders have to trust in the decisions being made - less transparent.<br />
			</p>
			<p>
			<strong>Does not cover long term ship scheduling activities</strong>
			</p>
			</td>
		</tr>
		<tr valign="top">
			<td>
			<h4> CoalSync</h4>
			<p>
			(Hosted Solution) 
			</p>
			</td>
			<td>
			<p>
			<strong>Increases throughput<br />
			</strong>Provides a framework that allows throughput to be maximised, without the constraints of a simple spreadsheet based quota scheme.<br />
			</p>
			<p>
			<strong>Reduces Congestion<br />
			</strong>Manages achievable throughput, and provides the visibility to avoid &quot;peaks and troughs&quot; in demand.
			</p>
			<p>
			<strong>Quick to implement</strong><br />
			Online solution, can be rolled out quickly. The CoalSync Solution includes a framework to facilitate agreement on operational protocols and rules.
			</p>
			<p>
			<strong>Increases flexibility<br />
			</strong>Individual Coal exporters are able to take advantage of natural peaks and troughs in production, and dovetail with other producers. Maintenance can be planned with the confidence that access given up now can be reclaimed later.
			</p>
			<p>
			<strong>Transparent and auditable<br />
			</strong>The CoalSync Solution implements operational rules and protocols agreed by the stakeholders. The rules are defined in a graphical flowchart, and are executed automatically by the system. This is a fully auditable process, that allows any stakeholder to see what factors contributed to a particular allocation or decision made. 
			</p>
			</td>
			<td> </td>
		</tr>
	</tbody>
</table>
  
<br />
<table border="0" cellspacing="0" cellpadding="0" style="border-width: 0px; width: 100%">
	<tbody>
		<tr>
			<td style="text-align: left">  <a href="index.php/platform/solution/6" title="The CoalSync Solution (6/6)"> <img src="static-content/images/rewind16.jpg" alt="Next" /> Previous</a> </td>
			<td style="text-align: right">&nbsp;</td>
		</tr>
	</tbody>
</table>
</div>

    <div>(2464 Reads)</div>
   </channel>
</rss>
