<?xml version="1.0" encoding="iso-8859-1"?>
<?xml-stylesheet href="topics.xsl" type="text/xsl"?>
<topics>
	<heading>Project Management and Training</heading>
	<return>intro</return>
	<topic id="1">
		<title></title>
		<general>Caliach Vision helps you through the delicate and often sizeable task of implementation. On-site training and consultancy can be provided to get you up and running, sometimes in just a few days. </general>
		<trailingnote></trailingnote>
		<bullet id="1">
		  <text>The program comes with an extensive illustrated reference book, which is packed with ideas and suggestions as well as full functional details of the program.</text>
		</bullet>
		<bullet id="2">
		  <text>The integrated data transfer utility can import your data from standard file formats. This means you can transfer data from an old system into Caliach Vision without re-keying. As it imports, it checks data validity and rejects illogical records. There is even a test function so you can make absolutely sure things are right before you load the data.</text>
		</bullet>
	</topic>
	<topic id="2">
		<title></title>
		<general>Caliach Vision can be implemented in stages with benefits accruing right from the start. Typically successful implementation strategies have fallen into three broad approaches: </general>
		<trailingnote></trailingnote>
		<bullet id="1">
		  <text>The Big-Bang approach in which every facet and detail is prepared beforehand, all training completed, and a Go-Live date set for the change-over from existing systems.</text>
		</bullet>
		<bullet id="2">
		  <text>The Mini-Big-Bang approach, in which all facets except the accounts package are implemented on the Go-Live date. </text>
		</bullet>
		<bullet id="3">
		  <text>The Phased Introduction approach in which the main elements are introduced progressively over time. </text>
		</bullet>
	</topic>
	<topic id="3">
		<title></title>
		<general>The approach you choose will need to accommodate the particular situation of your business, taking into account any time and resource constraints. There are some general rules to follow: </general>
		<trailingnote></trailingnote>
		<bullet id="1">
		  <text>Parts must be defined prior to BoMs, process routes, customer parts, purchase parts, engineering data and any processing data such as sales orders.</text>
		</bullet>
		<bullet id="2">
		  <text>Customers must be defined before customer parts and sales orders can be created. </text>
		</bullet>
		<bullet id="3">
		  <text>Suppliers must be defined before purchase parts and purchase orders can be created.</text>
		</bullet>
		<bullet id="4">
		  <text>Work centres must be defined before process routes can be created.</text>
		</bullet>
		<bullet id="5">
		  <text>Work orders need parts to be defined but have minimal use unless BoMs are available.</text>
		</bullet>
		<bullet id="6">
		  <text>A physical stock take is generally needed at the point of going live.</text>
		</bullet>
		<graphic id="1">
			<file>project</file>
		</graphic>	
	</topic>
</topics>
