<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000051" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To use calendars in service</Title>
		<Keyword><Level1>Calendars in service</Level1>
			<Level2>use</Level2>
		</Keyword>
		<Keyword><Level1>Use calendars in service</Level1>
		</Keyword>
	</Header>
	<GeneralSection><List><ListIntro>You can use a calendar in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, to define the availability of:</ListIntro>
			<ListItem>An Serialized Item</ListItem>
			<ListItem>A Cluster</ListItem>
			<ListItem>A service engineer</ListItem>
			<ListItem>A service center</ListItem>
			<ListItem>A response time</ListItem>
		</List>
		<GeneralSection><SectionTitle>Availability type</SectionTitle>
			<List><ListIntro>The functionality of the usage of availability type is very useful for calendars that are related to service engineers. The availability type gives the user the possibility to dedicate some engineers for a specific type of work or to define availability schemes for call solution outside normal working hours. In these availability schemes you can define if:</ListIntro>
				<ListItem>During the normal working day an engineer is available for all types of work (availability type = normal service)</ListItem>
				<ListItem>During the evening from 17.00 to 24.00 hrs the engineer can be called for call solution (availability type = call solution).</ListItem>
			</List>
			<Paragraph>In the calendars of the serialized item and the cluster, the availability type must be used to define the periods that the objects or the configuration is available for service. Because the objects or the configuration for call solution is normally always available, the user must define free periods for maintenance with the help of availability types in the objects or the configuration calendar.</Paragraph>
			<Paragraph>Blank availability type, which is mainly used for Order Management and Warehousing, can also be used within service. If the availability of a resource is not that important, service types with a blank availability type (empty field) can be used. The benefit is that only once the standard calendar template needs to be defined with blank availability, linked to an appropriate time interval type. So for example, 'blank' can be used for the company, service center and response code when the availability is more important (service engineer) then separate availability types regarding certain service types can be defined and linked to the company.</Paragraph>
			<Paragraph>In service the blank availability type is seen as a normal availability type, which needs to be defined. As a result, the system does a check if the blank availability type on the used service type is linked to the involved calendar.</Paragraph>
			<Paragraph>To use the blank availability type on the service type, select also the blank availability check-box for the concerned calendar and make sure the standard template is defined with the "blank availability", or in a more specific way by defining the availability types in calendar lines.</Paragraph>
		</GeneralSection>
		<List><ListIntro>In the specified modules of <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, the search sequences for calendars are as follows:</ListIntro>
			<ListItem><GUIRef href="/baanerp/ts/spc" role="module">Service Planning &amp; Concepts</GUIRef> module: Serialized item - Cluster - Service Center- Company.</ListItem>
			<ListItem><GUIRef href="/baanerp/ts/clm" role="module">Call Management</GUIRef> module: Response Time</ListItem>
			<ListItem><GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef> module: Serialized item - Cluster - Service engineer - Service Center - Company.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>If no calendar is defined for the response time, the calls are planned immediately.</Paragraph>
		</Note>
	</GeneralSection>
</ManualTopic>
