Anw: v0.2 - Modifications to Last 3 Jobs and Grain POD

2019-03-05T10:13:20Z

v0.2 - Modifications to Last 3 Jobs and Grain POD

← Older revision		Revision as of 12:13, 5 March 2019
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|Rory Holbrook POD Notes}}		{{#vardefine:Doc_Title\|Rory Holbrook POD Notes}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.2}}
	{{#vardefine:Date\|~~4th~~ March 2019}}		{{#vardefine:Date\|5th March 2019}}
	{{#vardefine:Reference\|355526}}		{{#vardefine:Reference\|355526}}
	{{#vardefine:Year\|2019}}		{{#vardefine:Year\|2019}}
Line 193:		Line 193:
	* As only 2 telephone numbers may be defined against a customer, the telephones numbers are largely hard-coded.		* As only 2 telephone numbers may be defined against a customer, the telephones numbers are largely hard-coded.
	* "Consignment Note" is taken from the Job Code.		* "Consignment Note" is taken from the Job Code.
	* "Date Raised" is taken from the ~~actual~~ start date.		* "Date Raised" is taken from the planned start date of the collection job.
	* "Weighbridge Ticket No." is taken from the delivery job UDF field.		* "Weighbridge Ticket No." is taken from the delivery job UDF field.

Line 387:		Line 387:
	* LXJ_PRODUCT_2 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].		* LXJ_PRODUCT_2 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].
	* LXJ_PRODUCT_3 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].		* LXJ_PRODUCT_3 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].

			{{Note}} When setting LXJ_PRODUCT DAL objects, check that the job associated to the products is not null - if it is null, set the DAL object to null. This will prevent issues where last 3 jobs does not exist for the trailer.

Anw: Minor correction

2019-03-04T16:12:37Z

Minor correction

← Older revision		Revision as of 18:12, 4 March 2019
Line 456:		Line 456:
	\|Year={{#var:Year}}		\|Year={{#var:Year}}
	\|FSEST=Y		\|FSEST=Y
	\|Rev1=~~Rev1~~		\|Rev1=Murray Middleton
	\|Rev1Title=~~Murray Middleton~~		\|Rev1Title=OBSL Project Manager
	\|Rev2=Rev2		\|Rev2=Rev2
	\|Rev2Title=Customer Representative		\|Rev2Title=Customer Representative
	}}</div>		}}</div>
	[[Category:{{#var:Client}} FS]]		[[Category:{{#var:Client}} FS]]

Anw: Minor formatting changes

2019-03-04T16:11:10Z

Minor formatting changes

← Older revision		Revision as of 18:11, 4 March 2019
Line 35:		Line 35:
	Sample TASCC Grain Note:		Sample TASCC Grain Note:

	[[File: FS_355526_POD_Grain_Sample.PNG\|border\|~~800px~~]]		[[File: FS_355526_POD_Grain_Sample.PNG\|border\|600px]]

	Sample Conveyance Note:		Sample Conveyance Note:

	[[File: FS_355526_POD_Conveyance_Sample.PNG\|border\|~~800px~~]]		[[File: FS_355526_POD_Conveyance_Sample.PNG\|border\|600px]]

	Sample General Delivery Note:		Sample General Delivery Note:

	[[File: FS_355526_POD_General_Sample.PNG\|border\|~~800px~~]]		[[File: FS_355526_POD_General_Sample.PNG\|border\|600px]]


Line 176:		Line 176:
	The POD note has been prototyped as below:		The POD note has been prototyped as below:

	[[File: FS_355526_POD_Grain.PNG\|border\|~~800px~~]]		[[File: FS_355526_POD_Grain.PNG\|border\|600px]]

	POD Notes:		POD Notes:
Line 255:		Line 255:
	The POD note has been prototyped as below:		The POD note has been prototyped as below:

	[[File: FS_355526_POD_Conveyance.PNG\|border\|~~800px~~]]		[[File: FS_355526_POD_Conveyance.PNG\|border\|600px]]

	POD Notes:		POD Notes:

Anw: v0.1 - Initial Draft

2019-03-04T16:09:04Z

v0.1 - Initial Draft

New page

<div class="noprint">
{{#vardefine:Client|RJH}}
{{#vardefine:ClientName|Rory J Holbrook}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Rory Holbrook POD Notes}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|4th March 2019}}
{{#vardefine:Reference|355526}}
{{#vardefine:Year|2019}}
{{ #vardefine: Figure | 0 }}{{ #vardefine: Example | 0 }}

</div>
{{Doc_TitleNew
|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 ==
Ben provides samples of the 3 Delivery Notes currently in use. Depending on analysis of Job Groups we are expecting to consolidate this to 2 POD notes, one with Last Load information - one without - and the use of an OBS standard format. Potential changes to update Configurable POC Note to include UDF weighbridge reference data.

Sample TASCC Grain Note:

[[File: FS_355526_POD_Grain_Sample.PNG|border|800px]]

Sample Conveyance Note:

[[File: FS_355526_POD_Conveyance_Sample.PNG|border|800px]]

Sample General Delivery Note:

[[File: FS_355526_POD_General_Sample.PNG|border|800px]]

== Solution Overview ==
It has been since discussed and decided that general deliveries will continue off-system at this time.

2 new reports will be created:
* RJH Grain
* RJH Conveyance

When assigned to the appropriate job groups and with the correct user-defined forms (UDF) configuration, this will produce the correct output from the jobs.

In order to achieve these reports, developments are required to the ''CALIDUS'' ePOD configurable report format and to the Admin console to support:
* Last 3 Jobs reporting, including details from the jobs and products.
* Customer Parameters.

Customer Parameters development has been specified elsewhere.

Last 3 jobs functionality is specified as part of this change, although this has been determined to be product development.

== Scope ==
{{Warning}}

{{Note}} In both cases, the reports have used the FORS Silver logo, not the bronze logo (as seen in the samples), as the FORS website confirms that RJ Holbrook is now at the silver level.

== Impact ==
{{Warning}} Outstanding questions:
* Does the EWC Code directly match to the waste check-boxes? I have assumed so.
* If not, then I can change the collection to request EWC code separately.
* EWC code for Utilities/Unsegregated waste?
* Multiple EWC codes may be captured per collection?
* In both PODs, I have used the FORS Silver logo, not the bronze logo, as the FORS website confirmed that RJH is now at the silver level. Confirmation required.
* Confirm whether grain collection customer signature is required


= CONFIGURATION SET-UP =
== Pre-requisites ==
None.

== Menu Structure ==
None.

== Data ==
Jobs are defined by the job group:
* GRAIN
* GRAIN-DEL
* CONVEYANCE
* CONVEYANCE-DEL

The jobs groups must include the following configuration:
* GRAIN
** POD Note Format: "RJH Grain".
** POC Note Format: "RJH Grain".
* GRAIN-DEL
** Customer Signature enabled.
** POD Note Format: "RJH Grain".
** POC Note Format: "RJH Grain".
* CONVEYANCE
** Driver Signature enabled.
** Customer Signature enabled.
** POD Note Format: "RJH Conveyance".
** POC Note Format: "RJH Conveyance".
* CONVEYANCE-DEL
** Customer Signature enabled.
** POD Note Format: "RJH Conveyance".
** POC Note Format: "RJH Conveyance".

Terms and Conditions must be created for Grain Deliveries. These can be defined against the GRAIN-DEL job group or created as UDF.

Grain Delivery jobs request the following job UDF:
* Weighbridge Number - a required numeric entry box.
* Weighbridge Weight - a required numeric entry box.
* Cleaning - a drop-down list defaulting to "Swept"

Load Start metrics will be required to request
* Trailer ID - a required data-bound field that will update the Load and Job trailer IDs.
* Vehicle Type - a required drop-down list of whatever vehicle types are required.

Conveyance Collection jobs request the following job UDF:
* WAF No - a required text entry box
* Waste Description, comprising:
** A multi-check box
** An "Other" text entry box.

Customer Parameters must be configured and entered against the customers to appear on the report.
The following 3 customer parameters are required:
* CARRIER_LICENSE
* SIC_CODE
* OPERATOR
These are required on the following customer records.
* CARRIER_LICENSE - entered against the Site customer record as the carrier license, and entered against the delivery customer as the disposal license number.
* SIC_CODE - entered against the collection customer.
* OPERATOR - entered against the delivery customer.

UDF has been prototyped for all of these and must be assigned to the appropriate job group.

== Implementation Advice ==
{{Warning}}


= FUNCTIONAL DESCRIPTION =
== Grain Process and POD Note ==
The process for grain collections/deliveries is as follows:
* Jobs created in pairs - select the job group for the task.
* Each job must have a product and quantity.
* When jobs are assigned to the loads, the trailer id is entered if known. Multiple pairs of jobs can be assigned to the same load.
* At Load Start the driver will confirm or enter the trailer ID and vehicle type - each job completed will be stamped with this trailer ID. If the vehicle is fixed (not tractor), enter the vehicle reg instead.
* Start the collection job, navigate and arrive.
* Collect the product and confirm the product on the collection to full quantity (in tonnes).
* Obtain signature (if required?)
* Start the delivery job, navigate and arrive.
* Deliver the product and confirm the quantity (in tonnes).
* Clean the vehicle and capture the cleaning information.
* Capture the weighbridge ticket number and weight.
* Complete the job.
* Capture the signature.

When jobs are created and completed following these processes, the POD report may be produced.

The POD note has been prototyped as below:

[[File: FS_355526_POD_Grain.PNG|border|800px]]

POD Notes:

General:
* One line (the first found) of products will be shown, showing the description.
* The quantity of product is as entered/confirmed by the user, whilst the weight is as captured from the weighbridge weight.
* The POD note will be generated showing the last 3 products based on the trailer that was entered. This has required product development to achieve.

Page Header:
* RHS, FORS and FTA logos are embedded in the report.
* A site address (a customer record with the Site ID as the customer code) must be created for each site.
* Title "RORY J. HOLBROOK" is taken from the site customer name.
* "HAULAGE, TIPPER & PLANT HIRE" is fixed text in the report.
* The site address is taken from the site customer address
* As only 2 telephone numbers may be defined against a customer, the telephones numbers are largely hard-coded.
* "Consignment Note" is taken from the Job Code.
* "Date Raised" is taken from the actual start date.
* "Weighbridge Ticket No." is taken from the delivery job UDF field.

Initial Header:
* Collect From will utilise the Job Address of the collection job, if there is one, otherwise use the address of the Collection Customer.
* Deliver To will utilise the Job Address of the delivery job, if there is one, otherwise use the address of the Delivery Customer.
* Charge To will utilise the address of the Delivery Customer address.
* "COLLECT FROM"/"TIME/DATE IN" is taken from the collection job actual start date and time.
* "COLLECT FROM"/"TIME/DATE OUT" is taken from the collection job actual end date and time.
* "DELIVER TO"/"TIME/DATE IN" is taken from the delivery job actual start date and time.
* "DELIVER TO"/"TIME/DATE OUT" is taken from the delivery job actual end date and time.
* "VEHICLE REG. NO." is taken from the load's assigned vehicle.
* "DESCRIPTION OF GOODS" is taken from the description of the first product found on the job.
* "QUANTITY" is taken from the actual quantity of the first product found on the job.
* "WEIGHT" is taken from the delivery job UDF field.

Detail section: None (included in Initial Header section above).

Final Footer:
* "LAST 3 LOADS"/"1" is taken from the description of the first product found on the last collection job completed on this trailer.
* "CLEANED"/"1" is taken from the UDF field description of the last delivery job completed on this trailer.
* "LAST 3 LOADS"/"2" is taken from the description of the first product found on the next to last collection job completed on this trailer.
* "CLEANED"/"2" is taken from the UDF field description of the next to last delivery job completed on this trailer.
* "LAST 3 LOADS"/"3" is taken from the description of the first product found on the third last collection job completed on this trailer.
* "CLEANED"/"3" is taken from the UDF field description of the third last delivery job completed on this trailer.

Page Footer:
* "The above goods..." is taken from the terms and conditions configured against the delivery job.
* "Print Name" is taken from the customer signatory of the delivery job.
* "Signature" is taken from the signature of the delivery job.
* "Date" is taken from the actual end date of the delivery job.
* "Goods are accepted..." is fixed text in the report.

== Conveyance Process and POD Note ==
The process for Conveyance collections/deliveries is as follows:
* Jobs created in pairs - select the job group for the task.
* Each job will have no products.
* When jobs are assigned to the loads, the trailer id is entered if known. Multiple pairs of jobs can be assigned to the same load.
* At Load Start the driver will confirm or enter the trailer ID and vehicle type - each job completed will be stamped with this trailer ID. If the vehicle is fixed (not tractor), enter the vehicle reg instead.
* Start the collection job, navigate and arrive.
* Enter the WAF No, tick the Waste boxes to record what was collected or enter other (including the EWC code).
* Obtain customer signature.
* Driver sign for collection.
* Start the delivery job, navigate and arrive.
* Complete the job.
* Capture the customer signature.

{{Note}} This conveyance process does not use products - it uses UDF on the collection ONLY to capture what was picked up.

{{Note}} It is possible that we could change that to assign the UDF against a product, and ask the driver to confirm the product collected, then enter the UDF against the product.

{{Warning}} The real issue here is that UDF is NOT passed forward to a linked job, so the delivery will not be updated showing the driver what has been collected.
There is no other way of achieving this however.

{{Warning}} Confirmation required of "Utilities/Unsegregated Waste" EWC code.

When jobs are created and completed following these processes, the POD report may be produced.

The POD note has been prototyped as below:

[[File: FS_355526_POD_Conveyance.PNG|border|800px]]

POD Notes:
* SIC code, Carrier License/License No and Operator are required to be defined as customer parameters.
* The final section of the header (comprising the Driver Signature, Vehicle Reg No, Vehicle Type, EWC Code, Customer Signature and Name has been redesigned to make the best use of the available space.
* The Waste Description section has been redesigned to include the EWC Code.

Page Header:
* "TICKET No" is taken from the Job Code.
* RHS and FORS logos are embedded in the report.
* A site address (a customer record with the Site ID as the customer code) must be created for each site.
* Title "RORY J. HOLBROOK" is taken from the site customer name.
* "HAULAGE, TIPPER & PLANT HIRE" is fixed text in the report.
* "Registered Office" is taken from the site customer address.
* "Carrier License" is taken from the Site Customer parameter "CARRIER_LICENSE".
* "Issued By" is fixed text in the report.
* "WAF No" is taken from the collection job UDF field.
* As only 2 telephone numbers may be defined against a customer, the telephones numbers are largely hard-coded.
* "Email" is taken from the site customer email address.
* "www.roryholbrook.com" is taken from the site customer contact.
* "Date" is taken from the actual start date of the collection job.
* "Time" is taken from the actual start time of the collection job.

Initial Header:
* "Customer Name"/"Customer Address" will utilise the address of the Delivery Customer address.
* "SIC Code" is taken from the Collection customer parameter "SIC_CODE".
* "Driver's Name" is taken from the load's assigned driver.
* "Collection Address" will utilise the Job Address of the collection job, if there is one, otherwise use the address of the Collection Customer.
* "Driver Signature" is taken from the collection job's driver signature.
* "Vehicle Reg No" is taken from the load's assigned vehicle.
* "Vehicle Type" is taken from the Load Metrics UDF field.
* "Customer Signature" is taken from the customer signature of the collection job.
* "Print Name" is taken from customer signatory of the collection job.
* "Waste Description" is taken from the collection job's UDF field "WASTE".

Detail section: None (included in Initial Header section above).

Final Footer:
* "Site Name"/"Site Address" will utilise the Job Address of the delivery job, if there is one, otherwise use the address of the Delivery Customer.
* "Operator" is taken from the delivery customer parameter "OPERATOR".
* "License No" is taken from the delivery customer parameter "CARRIER_LICENSE".
* "Issued By" is fixed text in the report.
* "Print Name" is taken from customer signatory of the delivery job.
* "Signature" is taken from the customer signature of the delivery job.
* {{Note}} colour copy footer information is not required or printed.


= TECHNICAL NOTES =
== Modules Changed ==

{| class="wikitable" border="1" width="100%"
|-bgcolor="#FFFF99"
! width="20%" | Module Name || width="40%" | Module Type || width="40%" | Notes
|-
| 1 || 2 || 3
|}

== Table Updates ==

{| class="wikitable" border="1" width="100%"
|-bgcolor="#FFFF99"
! width="20%" | Name || width="10%" | Type || width="10%" | Nullable || width="10%" | Default || width="10%" | Storage || width="40%" | Comments
|-
| 1 || 2 || 3 || 4 || 5 || 6
|}

== Developer Notes ==
=== Last X Jobs ===
Information for the last jobs completed on the trailer are available through the following 'table' names:
* LXJ_JOB_1 - the collection job object for the first job (nearest to date that this job was completed). This object includes all details {containers, products, etc)
* LXJ_JOB_2
* LXJ_JOB_3 - the collection job object for the third job (furthest of the 3 away from the date this job was completed).
* LXJ_DELIVERY_JOB_1 - the delivery job linked to LXJ_JOB_1 by Job Code
* LXJ_DELIVERY_JOB_2
* LXJ_DELIVERY_JOB_3
* LXJ_PRODUCT_1 - the first product on LXJ_JOB_1
* LXJ_PRODUCT_2
* LXJ_PRODUCT_3
In order for this to be used, the jobs MUST have trailer ID entered against them, either set in Admin, or entered by the user against e load (through Load Start Metrics) and inherited onto the jobs.

The data can be accessed in exactly the same way as any other field on any other table. For example, accessing a UDF Field on the 2nd delivery job is as follows:
* [LXJ_DELIVERY_JOB_2.EPOD_UDF_JOBDETS.CLEANING]

A list will be created of the last 3 jobs for that trailer, consisting of a class (LinkedJobs) of:
* The collection job EPOD_JOB_LXJ_COLLECTION.
* The associated delivery job EPOD_JOB_LXJ_DELIVERY.

A LastJob class will be created to store the results of the last 3 collection jobs found for that trailer, storing:
* The Load ID EPL_LOAD_ID.
* The Job ID EPL_JOB_ID.
* The Job Code EPL_JOB_CODE.

A GetLastXJobs method will be created, to get the last 3 collection jobs run on this trailer.

The method will be passed the job ID and a database connection.

The process will run the stored procedure EPOD_JOB_SELECT_LAST_3_COLLECTIONS2 passing parameters:
* EPL_SITE_ID
* EPL_JOB_ID

This will return (up to) the last 3 jobs for the trailer set on that job.

The method will loop through the result and store the load, job ID and job code in a LastJob class object and add this to a LastXCollections list.

The method will loop through this list and for each will retrieve:
* the collection job DAL object, through the Site ID and Job ID.
* the associated delivery job DAL object, through the Site ID, Job Code, Job Type (Delivery) and load ID.
These will be stored in a new LinkedJobs object, and added to the list lstLastXJobs

The process will fill this to exactly 3 rows if there are less than 3 returned.

The existing method GetDataForReport will be modified to call GetLastXJobs after getting all other data.

The existing method replaceDataTags will be modified to recognise the following data table names and translate them to an existing DAL object:
* LXJ_JOB_1 - the collection job object for the first job (nearest to date that this job was completed). This object includes all details )containers, products, etc). In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.
* LXJ_JOB_2 - In this case, the data object oDalObj will be populated with lstLastXJobs[1].EPOD_JOB_LXJ_COLLECTION.
* LXJ_JOB_3 - the collection job object for the third job (furthest of the 3 away from the date this job was completed). In this case, the data object oDalObj will be populated with lstLastXJobs[2].EPOD_JOB_LXJ_COLLECTION.
* LXJ_DELIVERY_JOB_1 - the delivery job linked to LXJ_JOB_1 by Job Code. In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_DELIVERY.
* LXJ_DELIVERY_JOB_2 - In this case, the data object oDalObj will be populated with lstLastXJobs[1].EPOD_JOB_LXJ_DELIVERY.
* LXJ_DELIVERY_JOB_3 - In this case, the data object oDalObj will be populated with lstLastXJobs[2].EPOD_JOB_LXJ_DELIVERY.
* LXJ_PRODUCT_1 - the first product on LXJ_JOB_1. In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].
* LXJ_PRODUCT_2 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].
* LXJ_PRODUCT_3 - In this case, the data object oDalObj will be populated with lstLastXJobs[0].EPOD_JOB_LXJ_COLLECTION.EPOD_CONTAINERS[0].EPOD_PRODUCTS[0].

=== POD Design Notes ===
When accessing Last 3 Jobs information, they should be accessed as per the following example:
* [LXJ_DELIVERY_JOB_2.EPOD_UDF_JOBDETS.CLEANING]

When utilising customer parameters, they should be accessed as per the following example:
* [EPOD_COLLECTION_CUSTOMER.EPOD_ADM_PARAMETER_VALUES.SIC_CODE]
The actual parameter accessed depends on the parameter data configured as available for a customer and the parameters entered per customer.

The Waste Description section must be styled through the new UDF Fields classes.


= TEST PLAN =
{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=description of what is to be achieved
|MenuAccess=Where on the menus the item can be found
|Prerequisites=The prerequisites of the test
|Objective=The details of what each group of tests is to achieve
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Area being tested in this cycle
|Notes=Any notes or prerequisites for the tests following.
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}}


{{Doc_AppendixNew
|Appendix=A
|Estimate=Y
|Glossary=EPOD2
|Ref1=Reference1
|RefV1=0.1
|RefDate1=26/02/2019
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|PM=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Rev1
|Rev1Title=Murray Middleton
|Rev2=Rev2
|Rev2Title=Customer Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 355526 Rory Holbrook POD Notes - Revision history

Anw: v0.2 - Modifications to Last 3 Jobs and Grain POD

Anw: Minor correction

Anw: Minor formatting changes

Anw: v0.1 - Initial Draft