FS 311753 New Info Tab Fields - Revision history

Anw: v0.3 - New field naming in XML configuration

2013-10-04T10:41:30Z

v0.3 - New field naming in XML configuration

← Older revision		Revision as of 12:41, 4 October 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' eSERV}}		{{#vardefine:System\|''CALIDUS'' eSERV}}
	{{#vardefine:Doc_Title\|New Info Tab Fields}}		{{#vardefine:Doc_Title\|New Info Tab Fields}}
	{{#vardefine:Version\|0.2}}		{{#vardefine:Version\|0.3}}
	{{#vardefine:Date\|~~11th September~~ 2013}}		{{#vardefine:Date\|4th October 2013}}
	{{#vardefine:Reference\|311753 309371-3}}		{{#vardefine:Reference\|311753 309371-3}}
	{{#vardefine:Year\|2013}}		{{#vardefine:Year\|2013}}
Line 294:		Line 294:
	==DB Range==		==DB Range==
	<FORM NAME="INFO UDF FILE" REQUIRED="Y">		<FORM NAME="INFO UDF FILE" REQUIRED="Y">
	<FIELD ID="~~0001~~">		<FIELD ID="APPLICATION">
	<TEXT>Application</TEXT>		<TEXT>Application</TEXT>
	<FORMAT>DDL</FORMAT>		<FORMAT>DDL</FORMAT>
Line 304:		Line 304:
	</ITEMS>		</ITEMS>
	</FIELD>		</FIELD>
	<FIELD ID="~~0002~~">		<FIELD ID="LOCATION">
	<TEXT>Location on Site</TEXT>		<TEXT>Location on Site</TEXT>
	<FORMAT>T</FORMAT>		<FORMAT>T</FORMAT>
Line 314:		Line 314:
	<FORM NAME="INFO UDF FILE" REQUIRED="Y">		<FORM NAME="INFO UDF FILE" REQUIRED="Y">
	<FIELD ID="0001">		<FIELD ID="0001">
	<TEXT>~~Application~~</TEXT>		<TEXT>APPLICATION</TEXT>
	<FORMAT>DDL</FORMAT>		<FORMAT>DDL</FORMAT>
	<SKIPABLE>N</SKIPABLE>		<SKIPABLE>N</SKIPABLE>
Line 323:		Line 323:
	</ITEMS>		</ITEMS>
	</FIELD>		</FIELD>
	<FIELD ID="~~0002~~">		<FIELD ID="LOCATION">
	<TEXT>Location on Site</TEXT>		<TEXT>Location on Site</TEXT>
	<FORMAT>T</FORMAT>		<FORMAT>T</FORMAT>
Line 333:		Line 333:
	<FORM NAME="INFO UDF FILE" REQUIRED="Y">		<FORM NAME="INFO UDF FILE" REQUIRED="Y">
	<FIELD ID="0001">		<FIELD ID="0001">
	<TEXT>~~Application~~</TEXT>		<TEXT>APPLICATION</TEXT>
	<FORMAT>DDL</FORMAT>		<FORMAT>DDL</FORMAT>
	<SKIPABLE>N</SKIPABLE>		<SKIPABLE>N</SKIPABLE>
Line 342:		Line 342:
	</ITEMS>		</ITEMS>
	</FIELD>		</FIELD>
	<FIELD ID="~~0002~~">		<FIELD ID="LOCATION">
	<TEXT>Location on Site</TEXT>		<TEXT>Location on Site</TEXT>
	<FORMAT>T</FORMAT>		<FORMAT>T</FORMAT>

Anw at 08:06, 11 September 2013

2013-09-11T08:06:27Z

← Older revision		Revision as of 10:06, 11 September 2013
Line 371:		Line 371:
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0
	\|FS=0.5		\|FS=0.75
	\|TS=0.0		\|TS=0.0
	\|DEV=4.0		\|DEV=4.0

Anw: v0.2 - Additional detail on how Infor fields will be populated and entered; Changed estimate.

2013-09-11T07:51:08Z

v0.2 - Additional detail on how Infor fields will be populated and entered; Changed estimate.

← Older revision		Revision as of 09:51, 11 September 2013
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' eSERV}}		{{#vardefine:System\|''CALIDUS'' eSERV}}
	{{#vardefine:Doc_Title\|New Info Tab Fields}}		{{#vardefine:Doc_Title\|New Info Tab Fields}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.2}}
	{{#vardefine:Date\|~~5th~~ September 2013}}		{{#vardefine:Date\|11th September 2013}}
	{{#vardefine:Reference\|311753 309371-3}}		{{#vardefine:Reference\|311753 309371-3}}
	{{#vardefine:Year\|2013}}		{{#vardefine:Year\|2013}}
Line 43:		Line 43:
	Both of these will be maintained at Job Group and Site level.		Both of these will be maintained at Job Group and Site level.

	The ~~Admin~~ PDA Services process will be modified to allow entry of these new fields and to validate them.		The PDA Services process will be modified to allow entry of these new fields and to validate them.

			The Admin system will be modified to allow entry of certain PDA codes (formerly Reason Codes) for use in the drop-down lists on the PDA for key data such as Service Type.

	== Scope ==		== Scope ==
Line 76:		Line 78:
	** EPL_UDF_FIELDS - see [[#Appendix_B:_INFO_UDF_FILE\|Appendix B: INFO UDF FILE]]		** EPL_UDF_FIELDS - see [[#Appendix_B:_INFO_UDF_FILE\|Appendix B: INFO UDF FILE]]
	{{Note}} There is a fourth, generic Lanemark setting yet to be confirmed, which will require another UDF configuration record to be set up.		{{Note}} There is a fourth, generic Lanemark setting yet to be confirmed, which will require another UDF configuration record to be set up.


			Table EPOD_REASON_CODES will have the following records added to it, as part of the implementation of the changes:
			* For reason type SERVTYPE, the following will be added (Reason Code-Description):
			** C-Commissioning
			** S-Service
			** SU-Survey
			** B-Breakdown
			** O-Other

	<!-- NEW PAGE -->		<!-- NEW PAGE -->
Line 207:		Line 218:

	If PDA_JOB_GROUP.EPL_SERVICE_INFO = "L", the following fields will be made available for editing on the Info tab of SM_Service.js:		If PDA_JOB_GROUP.EPL_SERVICE_INFO = "L", the following fields will be made available for editing on the Info tab of SM_Service.js:
	* EPL_SERVICE_GROUP - labelled as "Range" for the Lanemark style, and "Group" for others.		* EPL_SERVICE_GROUP - labelled as "Range" for the Lanemark style, and "Group" for others. This will be a drop-down list populated by the Product Groups available in the system. A new function will be created in PDA_SERVICE_PRODUCT_MASTER, based on SelectAllSystemTypes, called SelectAllGroups, will be created - this will return a distinct list of all available Product Groups. The Group selected by the Admin user will be defaulted in the DDL.
	* EPL_SYSTEM_TYPE - Labelled as "Model" for the all (except where other styles apply).		* EPL_SYSTEM_TYPE - Labelled as "Model" for the all (except where other styles apply). This will be a drop-down list populated by the Product Models available in the system, as now, through SelectAllSystemTypes. The model selected by the Admin user will be defaulted in the DDL.
	* EPL_VIN_NUMBER - Labelled as "Serial No" for the Lanemark style, and "VIN Number" for others.		* EPL_VIN_NUMBER - Labelled as "Serial No" for the Lanemark style, and "VIN Number" for others.
	* EPL_SERVICE_TYPE - Labelled as "Reason for Site Visit" for the Lanemark style, and "Service Type" for others.		* EPL_SERVICE_TYPE - Labelled as "Reason for Site Visit" for the Lanemark style, and "Service Type" for others. This will be a drop-down list and will be populated by the available service types in the system, using the existing function SelectAllReasonCodes, passing the Site and an EPL_REASON_TYPE of "SERVTYPE". The Service Type selected by the Admin user will be defaulted in the DDL.

	{{Note}} The existing UDF developments should also create a scrolling view for the user-defined information - see [[#Appendix_C:_Quote_.26_Document_References\|Appendix C]] for details. Section [[#Appendix_B:_INFO_UDF_FILE\|Appendix B: INFO UDF FILE]] shows the configurations that must be made at Product Group level for the correct fields to be entered.		{{Note}} The existing UDF developments should also create a scrolling view for the user-defined information - see [[#Appendix_C:_Quote_.26_Document_References\|Appendix C]] for details. Section [[#Appendix_B:_INFO_UDF_FILE\|Appendix B: INFO UDF FILE]] shows the configurations that must be made at Product Group level for the correct fields to be entered.
Line 362:		Line 373:
	\|FS=0.5		\|FS=0.5
	\|TS=0.0		\|TS=0.0
	\|DEV=2.75		\|DEV=4.0
	\|ST=0.5		\|ST=0.5
	\|IMP=0		\|IMP=0

Anw: Addition of soem changes to Services screen

2013-09-10T14:47:00Z

Addition of soem changes to Services screen

← Older revision		Revision as of 16:47, 10 September 2013
Line 124:		Line 124:
	* EPL_SYSTEM_TYPE - labelled as "Model".		* EPL_SYSTEM_TYPE - labelled as "Model".

	The Services screen (service_job.aspx) will be modified ~~so that the~~ label against VIN number when entering search criteria is "Serial No", if EPL_SERVICE_INFO = "L".		The Services screen (service_job.aspx) will be modified as follows:
			* The label against VIN number when entering search criteria is "Serial No", if EPL_SERVICE_INFO = "L".
			* The Service Type will be displayed from the variable values, in the Search criteria, Edit/Add pop-up and the Grid.

	The Service Details screen (service_detail.aspx) will be modified as follows:		The Service Details screen (service_detail.aspx) will be modified as follows:

Anw: /* DB Range */

2013-09-09T15:15:09Z

DB Range

← Older revision		Revision as of 17:15, 9 September 2013
Line 298:		Line 298:
	</FORM>		</FORM>

	==TX/TRX/MTX Ranges==		==TX/TRX/MTX Ranges==
	<FORM NAME="INFO UDF FILE" REQUIRED="Y">		<FORM NAME="INFO UDF FILE" REQUIRED="Y">
	<FIELD ID="0001">		<FIELD ID="0001">

Anw: Added EPOD_SERVICE XML export structure

2013-09-06T08:46:35Z

Added EPOD_SERVICE XML export structure

@@ Line 143: / Line 143: @@
 * Existing field EPL_SIM_NUMBER will become EPL_CODE_3.
 All code that references these fields in all modules will be globally replaced.
 If PDA_JOB_GROUP.EPL_SERVICE_INFO = "L", the following fields will be made available for editing on the Info tab of SM_Service.js:
@@ Line 157: / Line 217: @@
 <!-- MEDIA LANDSCAPE YES -->
 = Appendix A: TEST PLAN  =
 {{TestPlan_Header

Anw: v0.1 - Initial Creation

2013-09-05T15:18:54Z

v0.1 - Initial Creation

New page

<div class="noprint">
{{#vardefine:Client|LANE}}
{{#vardefine:ClientName|Lanemark}}
{{#vardefine:System|''CALIDUS'' eSERV}}
{{#vardefine:Doc_Title|New Info Tab Fields}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|5th September 2013}}
{{#vardefine:Reference|311753 309371-3}}
{{#vardefine:Year|2013}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Info will show:
* Range - Service Group - drop-down list entry of:
** TX/TRX/MTX
** DB
** FD/FDB
** Non-Lanemark
* Model - text entry
* S/No - text entry
* Lanemark Service Item Number - Service ID. Entered by Admin, displayed here.
* Application - User-defined Field.
* Location On Site - User-defined Field.
* Reason For Site Visit - Service Type

== Solution Overview ==
Configuration within Admin will control what fields are to be entered in the Info tab of the Services process through:
* A new "Lanemark" configuration against the Info tab
* A UDF configuration against the Info tab
Both of these will be maintained at Job Group and Site level.

The Admin PDA Services process will be modified to allow entry of these new fields and to validate them.

== Scope ==
* These changes will be made in the latest version of the {{#var:System}} product only.
* The changes will be made to the Android eSERV client only.
* {{Warning}} This change requires that the UDF modifications are complete first - see [[#Appendix_C:_Quote_.26_Document_References|Appendix C]] for details.



= Set-up =

== Pre-requisites ==

== Menu Structure ==

== Data ==
Table EPOD_UDF_CONFIG must have new records created for the product groups:
* EPL_DESCRIPTION = "DB Product Group Info Fields"
** EPL_KEY_TYPE = "P"
** EPL_KEY_VAL = "{EPL_SITE_ID}|DB"
** EPL_CONFIG_TYPE = "INFO"
** EPL_UDF_FIELDS - see [[#Appendix_B:_INFO_UDF_FILE|Appendix B: INFO UDF FILE]]
* EPL_DESCRIPTION = "TX/TRX/MTX Product Group Info Fields"
** EPL_KEY_TYPE = "P"
** EPL_KEY_VAL = "{EPL_SITE_ID}|TX/TRX/MTX"
** EPL_CONFIG_TYPE = "INFO"
** EPL_UDF_FIELDS - see [[#Appendix_B:_INFO_UDF_FILE|Appendix B: INFO UDF FILE]]
* EPL_DESCRIPTION = "FD/FDB Product Group Info Fields"
** EPL_KEY_TYPE = "P"
** EPL_KEY_VAL = "{EPL_SITE_ID}|FD/FDB"
** EPL_CONFIG_TYPE = "INFO"
** EPL_UDF_FIELDS - see [[#Appendix_B:_INFO_UDF_FILE|Appendix B: INFO UDF FILE]]
{{Note}} There is a fourth, generic Lanemark setting yet to be confirmed, which will require another UDF configuration record to be set up.


= Functional Description =
== Database and DAL ==
The table EPOD_SERVICE will be modified as follows:
* Existing field EPL_VIN_NUMBER will become EPL_CODE_1.
* Existing field EPL_REG_NUMBER will become EPL_CODE_2 and will extend to 50 characters in length.
* Existing field EPL_SIM_NUMBER will become EPL_CODE_3.
All references to these EPOD_SERVICE fields in the following projects and areas will be changed for the new field names:
* All XSDs
* All .NET projects
* All database packages.

== Server ==
All XSDs within the Server will be modified to remove any value restriction from EPL_SERVICE_TYPE. These include but are not limited to:
* EPOD_EXPORT_JOB.XSD
* EPOD_EXPORT_JOB_RESPONSE.XSD
* EPOD_EXPORT_LOAD.XSD
* EPOD_EXPORT_LOAD_RESPONSE.XSD
* XMLUpload.XSD

== Admin ==
The Info and Diagnosis drop-down lists will be modified to allow the user to choose a new value of "Enabled (Lanemark)", value "L". This will apply to the Job Group (job_group.aspx) and Site (site_header.aspx) maintenance screens.

{{Note}} If these drop-down lists have not already been modified to allow configurable data items on the list, this change should be made now.

{{Note}} Although it is only necessary to change one of DDLs at this time, the full requirements from the client need both to be changed. These may already have been changed under another change - see [[#Appendix_C:_Quote_.26_Document_References|Appendix C]] for details.

The Job and Service Screens will require modification when creating a new job. Those screens affected are:
* ConfigurableJob.aspx
* job_details.aspx
* service_job.aspx

When creating or editing a new Service job, different fields will be prompted for, depending on the new Info configuration (EPL_SERVICE_INFO):

Service Type will be modified to offer a selection of different types, as follows:
* C-Commissioning
* S-Service
* SU-Survey
* B-Breakdown
* O-Other
These will be controlled by changing the Service Type DDL to accept data from the configurable data items.

The following fields will also be prompted for, if EPL_SERVICE_INFO = "L":
* EPL_SERVICE_GROUP - labelled as "Range"
* EPL_CODE_1 (formerly EPL_VIN_NUMBER) - labelled as "Serial No"
* EPL_SYSTEM_TYPE - labelled as "Model".

The Services screen (service_job.aspx) will be modified so that the label against VIN number when entering search criteria is "Serial No", if EPL_SERVICE_INFO = "L".

The Service Details screen (service_detail.aspx) will be modified as follows:
* Service Details:
** Service Type will be looked up from variable data rather than fixed.
* Information section:
** EPL_SERVICE_GROUP - labelled as "Range"
** EPL_SYSTEM_TYPE - labelled as "Model".
** EPL_CODE_1 (formerly EPL_VIN_NUMBER) - labelled as "Serial No"
** A translation of each of the User-defined fields from within EPL_UDF_INFO. The extraction of these fields will be similar to the extraction of T&Cs for reports, whereby the screen will iterate through the contained XML and create fields in this section. See TDLPOD.aspx.cs.generateFooter() for an example. The format of the fields will be similar to those already on this Service Details screen.

== Android Client ==
{{Note}} A Lanemark-specific Style change should already have been made under change [[FS_311581_Diagnosis_Narrative_Extended_Length]] - if this has not been completed, please check this specification for details.

The table EPOD_SERVICE will be modified as follows:
* Existing field EPL_VIN_NUMBER will become EPL_CODE_1.
* Existing field EPL_REG_NUMBER will become EPL_CODE_2 and will extend to 50 characters in length.
* Existing field EPL_SIM_NUMBER will become EPL_CODE_3.
All code that references these fields in all modules will be globally replaced.

If PDA_JOB_GROUP.EPL_SERVICE_INFO = "L", the following fields will be made available for editing on the Info tab of SM_Service.js:
* EPL_SERVICE_GROUP - labelled as "Range" for the Lanemark style, and "Group" for others.
* EPL_SYSTEM_TYPE - Labelled as "Model" for the all (except where other styles apply).
* EPL_VIN_NUMBER - Labelled as "Serial No" for the Lanemark style, and "VIN Number" for others.
* EPL_SERVICE_TYPE - Labelled as "Reason for Site Visit" for the Lanemark style, and "Service Type" for others.

{{Note}} The existing UDF developments should also create a scrolling view for the user-defined information - see [[#Appendix_C:_Quote_.26_Document_References|Appendix C]] for details. Section [[#Appendix_B:_INFO_UDF_FILE|Appendix B: INFO UDF FILE]] shows the configurations that must be made at Product Group level for the correct fields to be entered.

SM_Service.validateService() will be modified to check that the above listed fields have been entered and that the entries are valid, if PDA_JOB_GROUP.EPL_SERVICE_INFO = "L".

SM_Service.saveService() will be modified to save the above listed fields to the Services job, if PDA_JOB_GROUP.EPL_SERVICE_INFO = "L".


= Appendix A: TEST PLAN =
{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=To test the entry of new Info fields in the Service process.
|MenuAccess=Services
|Prerequisites=The Services module must be configured for Info fields in the Lanemark style, and configurable fields are set up for each of the available product groups.
|Objective=To test that: Services can be created and edited with the new fields configured; the Services process requests the correct fields, labelled correctly; the system is updated correctly when a Service is completed and; services can be viewed correctly.
}}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Create a new Service Job using the Jobs, Configurable Jobs and Service Jobs screen
|Result=The screen should prompt for the correct items, validate them correctly, offer the correct options and save correctly.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Find a Service Job through the Services screen using Serial No.
|Result=
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Edit an existing Service Job using the Jobs, Configurable Jobs and Service Jobs screen
|Result=The screen should prompt for the correct items, validate them correctly, offer the correct options and save correctly.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=View the details of a completed service {{Note}} Do this after the PDA tests following.
|Result=The New Key and Configurable fields are displayed on the screen, with the correct labels.
|Remarks= |PassFail= }} {{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA
|Notes=
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start a Service Job and click on the Info tab.
|Result=The correct Key and Configurable fields are displayed for entry.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Change the Range.
|Result=The screen should refresh to display the correct Configurable fields for the Product Group selected.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Do not enter any data - just click '''Done''' on the diagnosis screen.
|Result=Validation errors should be displayed, forcing the user to enter the correct data.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Correct any errors, complete any required entry on other tabs and click '''Done'''.
|Result=The unit should prompt for Signature Entry.
|Remarks= |PassFail= }} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Complete the Service Job.
|Result=All data should be updated and passed back to the server, where it should be stored in the correct fields.
|Remarks= |PassFail= }} {{TestPlan_CycleFooter}}


= Appendix B: INFO UDF FILES =
{{Note}} There is a fourth, generic Lanemark setting yet to be confirmed, which will require a different UDF configuration.
==DB Range==
<FORM NAME="INFO UDF FILE" REQUIRED="Y">
<FIELD ID="0001">
<TEXT>Application</TEXT>
<FORMAT>DDL</FORMAT>
<SKIPABLE>N</SKIPABLE>
<ITEMS>
<ITEM CODE="Spray Booth">Spray Booth</ITEM>
<ITEM CODE="Low Bake">Low Bake</ITEM>
<ITEM CODE="Dryer">Dryer</ITEM>
</ITEMS>
</FIELD>
<FIELD ID="0002">
<TEXT>Location on Site</TEXT>
<FORMAT>T</FORMAT>
<SKIPABLE>N</SKIPABLE>
</FIELD>
</FORM>

==TX/TRX/MTX Ranges==
<FORM NAME="INFO UDF FILE" REQUIRED="Y">
<FIELD ID="0001">
<TEXT>Application</TEXT>
<FORMAT>DDL</FORMAT>
<SKIPABLE>N</SKIPABLE>
<ITEMS>
<ITEM CODE="Tray Washer">Tray Washer</ITEM>
<ITEM CODE="Micro Brewery">Micro Brewery</ITEM>
<ITEM CODE="Process Tank">Process Tank</ITEM>
</ITEMS>
</FIELD>
<FIELD ID="0002">
<TEXT>Location on Site</TEXT>
<FORMAT>T</FORMAT>
<SKIPABLE>N</SKIPABLE>
</FIELD>
</FORM>

==FD/FDB Ranges==
<FORM NAME="INFO UDF FILE" REQUIRED="Y">
<FIELD ID="0001">
<TEXT>Application</TEXT>
<FORMAT>DDL</FORMAT>
<SKIPABLE>N</SKIPABLE>
<ITEMS>
<ITEM CODE="Drying Oven">Drying Oven</ITEM>
<ITEM CODE="Curing Oven">Curing Oven</ITEM>
<ITEM CODE="Rotamoulding">Rotamoulding</ITEM>
</ITEMS>
</FIELD>
<FIELD ID="0002">
<TEXT>Location on Site</TEXT>
<FORMAT>T</FORMAT>
<SKIPABLE>N</SKIPABLE>
</FIELD>
</FORM>


{{Doc_Appendix
|Appendix=C
|Estimate=Y
|Glossary=EPOD
|Ref1=[http://{{SERVERNAME}}/calidus-assist/EPOD/index.php/UG_291094_EPOD_Admin_User_Guide UG 291094 EPOD Admin User Guide]
|RefV1=2.0
|RefDate1=4/4/2012
|Ref2=[http://{{SERVERNAME}}/calidus-assist/EPOD/index.php/UG_291097_EPOD_Client_User_Guide UG 291097 EPOD Client User Guide]
|RefV2=3.0
|RefDate2=23/4/2013
|Ref3=[[REQ_309371_Lanemark_eSERV_Requirements]]
|RefV3=0.4
|RefDate3=29/08/2013
|Ref4=[[FS_311636_UDF_Modifications]]
|RefV4=0.3
|RefDate4=05/09/2013
|Ref5=[[FS_311577_Additional_Diagnosis_Check_Fields]]
|RefV5=0.1
|RefDate5=29/08/2013
|REQ=0
|EST=0
|FS=0.5
|TS=0.0
|DEV=2.75
|ST=0.5
|IMP=0
|FOC=Y
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Julie Taylor
|Rev1Title=OBS Project Manager
|Rev2=Jeff Foster
|Rev2Title=Client Representative
|Rev3=Alan Thompson
|Rev3Title=Client Representative
}}</div>
[[Category:{{#var:Client}} FS]]