View source for REQ 298608 Selby Container Yard Requirements

<div class="noprint">
{{#vardefine:Client|POT}}
{{#vardefine:ClientName|Potter Group}}
{{#vardefine:System|''CALIDUS'' WMS}}
{{#vardefine:SystemCode|TCM}}
{{#vardefine:Doc_Title|Selby Container Yard Requirements}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|10th January 2013}}
{{#vardefine:Reference|298608}}
{{#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}}
}} 

<!-- TOC --> 
<div class="noprint">
= Introduction  =
<!-- The introduction will detail the initial requirements supplied by the client -->
This document is the {{#var:Doc_Title}}.

== Objective  ==
The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}}, at Selby Container Yard, on 24th May 2012.

== Scope and Limitations ==
* The system will be a new build, with Administration and Mobile Device functionality, written in Visual C#.NET.
* The database will be the standard WMS database, with some new tables added for the specific container yard functionality described below.
* Invoicing requirements have not been included as part of this system and will be costed separately as required.
* The existing Oracle Form for maintaining Locations will be modified slightly to allow for Container Yard locations.

<!-- NEW PAGE --> 
=Requirements=
The system will be a new build, with Administration and Mobile Device functionality, written in a Web-based client-server language (e.g. .NET, JSP).

The database will be the standard WMS Oracle database, with some new tables added for the specific container yard functionality described below.

The general Company and Warehouse will be set up through the standard WMS Warehouse screens.

The EDI will be controlled and set up through the standard WMS EDI configuration screens.

Users will be created and set up through the standard WMS User maintenance screens.

= Menus =
The following menu items will be available within the new system. The menus will be offered to the user based on the setup of the user itself. There are 3 main menus, as shown below.

==Admin User Menu==

* Processes
** Container Control
** Inbound Rail
** Outbound Rail
** Location Administration
** Container Task Maintenance
* Enquiries
** Location Enquiry
** Task Enquiry
* Maintenance
** Container Maintenance
** Container Type Maintenance
** Location Maintenance

==Customer Menu==
* Customer Container Enquiry screen
* Latest Audit Records

==PDA Menu==
* Work In Progress
* Relocate Container
* Change Container Status

= Screens =
Each screen listed above is described in detail in this section.

In all screens, the basic warehousing fields of Company Code and Warehouse ID will not be displayed as part of the working screen panel, but will be defaulted to ensure that they are set up against the user when they log in. They will be displayed in a standard header or footer on the Administration screens.

During this section, several input types will be mentioned, defined below:
* Drop-down List or DDL - this allows the user to select from several fields, all shown in a list that drops down below the entry field. typically the user is not allowed to enter any value other than those in the list.
* Auto-complete - this is similar to a DDL, in that the user is typically only allowed to choose items from a list. The user will type part of the required information, and the system will search for matching results and display them in a list below the entry field. The user clicks one of the provided samples to enter the data.
* Check-box - this is used to define a simple Yes/No field, and is displayed graphically as a small box. If the value is Yes, a tick appears in the box. the user can tick or un-tick the box by clicking on the field.
* Button - a button to click to complete a specific action, usually labelled on the button itself.
* List Button or Menu Button - a button combined with a DDL - the user chooses the action to be taken, then presses the button. This is useful when space is limited.
* Grid - tabulated data, usually used for several rows of data entry or display.

==Container Control Screen==
This screen is used to enter a new task, a combination of Inbound and/or outbound tasks.

General fields entered:
* Registration - The vehicle registration; Required Entry.
* Account - DDL, defaulted to the user's default account (MED01) 
* Haulier - Auto-complete. If the Haulier does not exist, it will be automatically added when saving the data.
* Date/Time - Defaulted to the current date and time.

Inbound fields:

These will be displayed in a grid. There can be up to 2 containers entered here.
* Order # - This will not validated by the system - it will manually checked by the users; Required Entry.
* Container ID - Required Entry; Validated to the standard Container pattern with Mod 11 Check Digit calculation.
* Type - DDL; Defaulted if the Container ID has already been known in the system.
* Weight (Limit Max) - DDL; Prompted only and Required Field if the Container Type is 20Ft; From a choice of 24/27/30. Defaulted if Container ID has already been known in the system.
* Full/Damaged - DDL; System-maintained values from (currently) , E/F/ED/FD/U.
* Hazardous - Check-box; Defaults to unchecked.
* UN No - Auto-complete; Values are taken from the preloaded UN Numbers with in the WMS tables; Entered only if the Container is marked as Hazardous. 

Outbound fields:

These will be displayed in a grid. There can be up to 2 containers entered here.
* Order # - This will not validated by the system - it will manually checked by the users; Required Entry.
* Container ID - Validated to the standard Container pattern with Mod 11 Check Digit calculation. Optional Entry - if entered, the information below will be displayed from the Container record found.
* Type - If the container is unknown or no Container has been entered; DDL; Defaulted if the Container ID has already been known in the system.
* Weight (Limit Max) - If the container is unknown or no Container has been entered; DDL; Prompted only and Required Field if the Container Type is 20Ft; From a choice of 24/27/30; Defaulted if Container ID has already been known in the system.
* Full/Damaged - If the container is unknown or no Container has been entered; DDL; System-maintained values from (currently) , E/F/ED/FD/U; Defaulted if Container ID has already been known in the system.
* Hazardous - If the container is unknown or no Container has been entered; Check-box; Defaults to unchecked; Defaulted if Container ID has already been known in the system.
* UN No - If the container is unknown or no Container has been entered; Auto-complete; Values are taken from the preloaded UN Numbers with in the WMS tables; Entered only if the Container is marked as Hazardous; Defaulted if Container ID has already been known in the system.

A '''Save''' button is provided to save the data entered. On pressing: 
* The data will be validated and the user prompted to confirm the entry or correct problems. If everything passes validation, the system will:
** Create records on the Moves table. The Inbound records will always be written first, to ensure that the tasks appear in the correct sequence. {{Note}} Created Date and Time should be set to Now, whereas Date and Time should be set to the entered values. Created By will be populated by the User ID creating the task.
** Create Containers if they were previously unknown.
** Create a Haulier if it was previously unknown.

Once saved, the screen will blank all entered fields, ready for next entry.

== Inbound Rail ==
The inbound rail screen allows the user to set up the preadvice of tasks arriving through the rail network. On entry to the screen, the system will prompt for the following data.

General Fields:
* Account - DDL; defaulted to the user's default account (MED01) 
* Date/Time - Validated as a date/time; not defaulted.
* Registration - Default to IMP{Date:YYMMDD}(Time:HHNN} after the date and time have been entered.
* Service - Required free text entry
* Carrier - Required free text entry

Container Fields:

These will be displayed in a grid. There is no limit to the number of records that can be entered. Entering a row of data will automatically show the data above and extend the grid by another line. 
* Container ID - Required Entry; Validated to the standard Container pattern with Mod 11 Check Digit calculation.
* Type - DDL; Defaulted if the Container ID has already been known in the system.
* Weight (Limit Max) - DDL; Prompted only and Required Field if the Container Type is 20Ft; From a choice of 24/27/30. Defaulted if Container ID has already been known in the system.
* Full/Damaged - DDL; System-maintained values from (currently) , E/F/ED/FD/U; Defaulted to Full (F)
* Hazardous - Check-box; Defaults to unchecked.
* UN No - Auto-complete; Values are taken from the preloaded UN Numbers with in the WMS tables; Entered only if the Container is marked as Hazardous. 

A '''Save''' button is provided to save the Inbound Rail advice.
* The data will be validated and the user prompted to confirm the entry or correct problems. If everything passes validation, the system will:
** Create records on the Moves table. {{Note}} Created Date and Time should be set to Now, whereas Date and Time should be set to the entered values. Created By will be populated by the User ID creating the task.
** Create Containers if they were previously unknown.

A '''Search''' button will be provided for the user to search by Registration (auto-complete) for a saved Inbound Rail Advice, choosing whether to look for confirmed or unconfirmed (defaulted to unconfirmed) and display all the details.

A '''Confirm''' button will be provided for the user to confirm that the Inbound Rail Advice is completed, and present it to the drivers for completion.

If an item in the grid is clicked, the user is allowed to edit it (if the task is unconfirmed).

Once the Inbound Rail Advice is confirmed, an '''Export''' button will be available to export the advice to CSV, so the user can print this if required.


== Outbound Rail ==

This screen is similar to the Inbound Rail screen, except for:
* Registration is defaulted to EXP rather than IMP
* The user is allowed to link an Outbound Rail advice to an Inbound Rail advice.
* The user is allowed to specify the position in the train.

On entry to the screen, the system will prompt for the following data.

General Fields:
* Account - DDL; defaulted to the user's default account (MED01) 
* Date/Time - Validated as a date/time; not defaulted.
* Registration - Default to EXP{Date:YYMMDD}(Time:HHNN} after the date and time have been entered.
* Linked Inbound - Optional Entry; DDL of unconfirmed inbounds on same day up to day -3.
* Service - Required free text entry; defaulted to the value from the Linked Inbound
* Carrier - Required free text entry; defaulted to the value from the Linked Inbound

Container Fields:

These will be displayed in a grid. There is no limit to the number of records that can be entered. Entering a row of data will automatically show the data above and extend the grid by another line. 
* Container ID - Required Entry; Validated to the standard Container pattern with Mod 11 Check Digit calculation.
* Type - DDL; Defaulted if the Container ID has already been known in the system.
* Weight (Limit Max) - DDL; Prompted only and Required Field if the Container Type is 20Ft; From a choice of 24/27/30. Defaulted if Container ID has already been known in the system.
* Full/Damaged - DDL; System-maintained values from (currently) , E/F/ED/FD/U; Defaulted to Full (F)
* Hazardous - Check-box; Defaults to unchecked.
* UN No - Auto-complete; Values are taken from the preloaded UN Numbers with in the WMS tables; Entered only if the Container is marked as Hazardous. 
* Position code - Numeric; Required Entry.

A '''Save''' button is provided to save the Inbound Rail advice.
* The data will be validated and the user prompted to confirm the entry or correct problems. If everything passes validation, the system will:
** Create records on the Moves table. {{Note}} Created Date and Time should be set to Now, whereas Date and Time should be set to the entered values. Created By will be populated by the User ID creating the task.
** Create Containers if they were previously unknown.

A '''Search''' button will be provided for the user to search by Registration (auto-complete) for a saved Inbound Rail Advice, choosing whether to look for confirmed or unconfirmed (defaulted to unconfirmed) and display all the details.

A '''Confirm''' button will be provided for the user to confirm that the Inbound Rail Advice is completed, and present it to the drivers for completion.

If an item in the grid is clicked, the user is allowed to edit it (if the task is unconfirmed).

Once the Inbound Rail Advice is confirmed, an '''Export''' button will be available to export the advice to CSV, so the user can print this if required.


== Location Administration ==
This screen allows the user to find a location and see all of the containers in FIFO sequence. The user will be able to change the sequence of containers in the location and save the results.

The user will also be able to select a second location and move containers into or out of that location by clicking buttons to move the top-most containers from one location to another.


== Container Task Maintenance ==
This screen allows the user to select the jobs and;
* edit the details
* cancel/delete the job
* complete the job manually

The screen will allow the user to find tasks by any or all of the following:
* Date or Date Range
* Account
* Type (IR/IG/OR/OG)
* Registration

The results will be displayed in a grid showing:
* Date/Time
* Container ID 
* Order # 
* Type 
* Weight
* Full/Damaged 
* Hazardous 
* UN No
Only jobs that have not been completed will be shown.

The screen will allow the user to select a task. A popup will show:
* All the container details
* A '''Delete''' button, to remove the job completely.
* A '''Complete''' button, to complete the task
* An '''Edit''' button, to allow the user to change the details.

The '''Delete''' button will ask the user to confirm the request and, if confirmed, will remove the task. 

The '''Complete''' button will allow the user to complete the task. Depending on the task type, the system will prompt for a location in which to place the container (Inbound) or just confirm the outbound.
 
Saving the changes will mark the task as complete by the Admin user.

The '''Edit''' button will allow the user to change the details against the task. A '''Save''' button will save the changes.

After completing any of these actions, the search results grid will be refreshed.


== Location Enquiry ==
This screen allows the user to view container information through the entry of Location or Container.

The user will be able to filter data through:
* Location code 
* Container ID

The results matching will be displayed in a grid showing:
* Date/Time
* Container ID 
* Order # 
* Type 
* Weight
* Full/Damaged 
* Hazardous
* # Days on site 

The grid will be sorted by clicking on a column header, and can be exported to CSV. The existing format can be seen in the document referenced as item 3 in Appendix A.

Clicking on a container will show a screen showing the container and all historical transactions for the container.


== Task Audit Enquiry ==
This screen allows the user to view the historical tasks that have happened to a container through the entry of Date, Location or Container.

Filter data through:
* Date or Date Range (required)
* Location code 
* Container ID

The results will be displayed in a grid showing
* Date/Time
* Container ID 
* Order # 
* Type 
* Weight
* Full/Damaged 
* Hazardous 

The grid will be sorted by clicking on a column header, and can be exported to CSV.


== Container Maintenance ==
This screen allows the user to see the stored details of a container.

Filter data through:
* Account ID
* Container ID

The results will be displayed in a grid showing
* Date/Time
* Account ID
* Container ID 
* Type 
* Weight

Clicking on a container will display a popup which will display the full details of the container and allow the user to edit the details, saving the data with a '''Save''' button provided. A new container can be added through the use of a '''New''' button.


== Container Type Maintenance ==
This screen allows the user to maintain container types used by the system.

The screen will display all container types in a paginated grid immediately.

The grid will show:
* Container Type
* Description

Clicking the '''Select''' button will display a popup showing the details, allowing the user to '''Edit''' or '''Delete''' the container type (deleting requesting confirmation). The user can add a container type through the use of a '''New''' button.


== Location Maintenance ==
This screen allows the user to maintain the locations visible to the system.
The user is allowed to filter data through:
* Location Code

The results will be displayed in a grid showing
* Location Code
* A '''Delete''' button.

Clicking on the '''Delete''' button will allow the Location to be deleted, if there are no Containers in the location, pending confirmation from the user. A New location can be added by clicking a '''New''' button.


== Customer Container Enquiry Screen ==
This screen is linked to directly from a web-site page, for customers to view the status of their containers.

This screen will display a filter of Container code.

Under this will be the last 20 transactions for that customer (Account)
The Account will be passed into the screen as a parameter.

When a container is entered and the '''Search''' button is displayed, the screen will call the existing Container Enquiry Results screen, as shown above in the Location Enquiry screen.


== PDA Work In Progress ==
This is a series of screens to allow the drivers to move containers in and out of the yard.

Initially, the process shows a Vehicle List.

Each item shown is the Registration (or train), plus the type. e.g. AB123 BVC (IG/OG)
Types are:
* IG - Inbound Gate
* OG - Outbound Gate
* IR - Inbound Rail
* OR - Outbound Rail
If there are multiple tasks for a Gate task (Inbound and Outbound) they are shown here as IG/OG.

If there are more tasks than can be shown on the screen, '''Prev''' and '''Next''' buttons will be shown.

Unlinked IR and OR Rail tasks are always shown separately. e.g. INP120525 (IR), EXP120525 (OR)

Linked IR and OR Rail tasks will be shown as one e.g. I/E120525 (IR/OR)

This screen shows all the outstanding tasks, with a date less-than or equal to today's date, with the eldest shown first.

The user clicks the registration.

* If the type is IG/OG:
** The unit shows the containers associated to the registration, with an indication of Full or Empty. e.g. ALCU1234567 (F), ALCU1234567 (ED).
** All IG types will be shown first, followed by all OG types.
* If the type is IR or IR/OR:
** The unit shows the containers associated to the registration, with an indication of Full or Empty e.g. ALCU1234567 (F), ALCU1234567 (ED).
** All IR containers  are shown if they exist, in Container ID sequence.
** A '''Switch''' button on the top will allow the user to switch to the linked OR type, if there is one.
* If the type is IR or IR/OR:
** All OR containers are shown in Position sequence, with an indication of the position e.g. ALCU1234567 (Pos 1), ALCU1234567 (Pos 49).
** A '''Switch''' button on the top will allow the user to switch to the linked IR type, if there is one.

A Container marked as Hazardous is identified as Red text with an 'X' icon in the top right hand corner.

The user then clicks a container to complete this task.

If the type is IG or IR:

The device shows the container details and a suggestion of where to take container.

Location is suggested by listing all locations available. They are ordered as:
* Suitability
** If damaged status then DAMAGES Location.
** Contains the same Container Type already or is Empty
** Contains a different Container Type
* Type:
** PREP if IG Full only else BAY
** BAY if not IG Full else PREP
** YARD
** TRAIN (if IR only)
** DAMAGES (If not already shown)
* Partially Full
** Already has containers of that type (Green Tick)
** Empty (Orange Tick)
** Else (No formatting)
The user then clicks the chosen location, and then clicks the '''Confirm''' button.

The Task is marked as completed in the system, marked with the current date and time, and the user that completed it.

If the type is OG Full or OR:

The device shows the container details and shown the location to get the container.

The user clicks a location to see the containers in the location.

At this point the user has the option to click '''Relocate''' and a container to be offered a list of locations in which to relocate the container specified.

Once the container is found, the user clicks '''Confirm'''.

The Task is marked as completed in the system, marked with the current date and time, and the user that completed it.

If the type is OG Empty:

The device shows the container details required, and the locations that contain that type.

The user clicks a location to see the containers available in the location (sorted in LIFO sequence), indicating which containers are empty.

At this point the user has the option to click '''Relocate''' and a container to be offered a list of locations in which to relocate the container specified.

Once the container is found, the user clicks '''Confirm'''.

The Task is marked as completed in the system, marked with the current date and time, and the user that completed it.

For type IG/OG:

Once confirm is clicked, the Containers moved are shown (all IG and OG types).

The Terms & Conditions required are displayed on the screen.

The driver clicks '''Confirm'''.

The driver is required to enter their signature.

Once confirm is clicked, the system saves the data.
* The Driver Signature is saved, stamped with the Date and Time and a unique ID.
* The Signature ID is marked against the completed tasks.

{{Note}} Although this screen is created for use on the mobile devices, this screen will also work and be accessible by logging on as a PDA user on a normal browser. This functionality can be achieved through the standard Admin Container Task Maintenance screen.

Samples of the existing screen layouts are available in the file referenced as item 4 in Appendix A.


== PDA Relocate Container ==
This screen allows the user to manually relocate containers.

The user is shown a list of locations, sequenced as follows:
* BAY
* PREP
* YARD
* DAMAGES
* TRAIN. 
The user selects one.

The device then displays a list of the containers in this location. The user can then click one of the containers in the list.

The device displays the container information a lists a series of new locations.

The user can click a new location (or a '''Back''' button)

Once a new location is chosen, the user can click a '''Confirm''' button to confirm the changes and exit to the menu, or '''Confirm...''' to confirm the changes and start another relocation.

{{Note}} Although this screen is created for use on the mobile devices, this screen will also work and be accessible by logging on as a PDA user on a normal browser. This functionality can be achieved through the standard Admin Location Administration screen.

Samples of the existing screen layouts are available in the file referenced as item 4 in Appendix A.


== PDA Change Container Status ==
This screen allows the user to change the status of a specific container.

The user is shown a list of locations, sequenced as follows:
* BAY
* PREP
* YARD
* DAMAGES
* TRAIN. 
The user selects one.

The device then displays a list of the containers in this location. The user can then click one of the containers in the list.

The device displays the current status of the container and buttons for each of the available statuses to change to.

The user can then hit the '''Confirm''' button to confirm the changes and exit, or '''Confirm...''' to confirm the changes and start another change of container status.

{{Note}} Although this screen is created for use on the mobile devices, this screen will also work and be accessible by logging on as a PDA user on a normal browser. This functionality can be achieved through the standard Admin Container Maintenance screen.

Samples of the existing screen layouts are available in the file referenced as item 4 in Appendix A.


= Database =
The following tables will be used.

==CY_CONTAINERS (NEW)==
This is a new table, to store the information about containers that have been seen in the system before.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* CONTAINER_ID
* ACCOUNT_ID
* TYPE_CODE
* WEIGHT_CODE
* LOCATION_CODE
* LOCATION_SEQ

Indexes:
# COMPANY_CODE/WAREHOUSE_ID/CONTAINER_ID
# COMPANY_CODE/WAREHOUSE_ID/ACCOUNT_ID/CONTAINER_ID
# COMPANY_CODE/WAREHOUSE_ID/LOCATION_CODE/LOCATION_SEQ

==CY_MOVES (NEW)==
This is a new table, to store the information about every container move that has happenend within the container yard.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* REGISTRATION
* TYPE_CODE
* CONTAINER_ID
* ACCOUNT_ID
* HAULIER_CODE
* ORDER_NO
* STATUS_CODE
* HAZARDOUS_FLAG
* UN_NO
* CREATED_DATE
* CREATED_TIME
* COMPLETE_DATE
* COMPLETE_TIME
* FROM_LOCATION
* TO_LOCATION
* STATUS
* LINKED_REGISTRATION
* USER_ID
* SIGNATURE_ID
* OUR_REF
* SERVICE
* CARRIER
* CREATED_BY

Indexes:
# COMPANY_CODE/WAREHOUSE_ID/REGISTRATION/TYPE_CODE/CONTAINER_ID
# COMPANY_CODE/WAREHOUSE_ID/CONTAINER_ID/DATE/TIME
# COMPANY_CODE/WAREHOUSE_ID/ACCOUNT_ID/DATE/TIME
# COMPANY_CODE/WAREHOUSE_ID/STATUS/TYPE_CODE

==CY_SIGNATURES (NEW)==
This table stores the signatures of the drivers. As a separate table, this can be cleared independently of the Moves tables.

Fields:
* SIGNATURE_ID
* SIGNATURE

Index:
# SIGNATURE_ID

==WARE_LOCATION==
This tables stores the locations used in the container yard.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* LOCATION_CODE
* LOCATION_TYPE set to "Y"

Index:
# COMPANY_CODE/WAREHOUSE_ID/LOCATION_CODE/LOCATION_TYPE

==CONTAINER_TYPE==
This is a lookup table for the container types.

Fields:
* CONTAINER_TYPE
* DESCRIPTION

Index:
# CONTAINER_TYPE

==STK_STOCKIST==
This table is used to store the Accounts

Fields:
* STOCKIST_CODE
* STOCKIST_SUB_CODE (001)
* NAME

Index:
# STOCKIST_CODE/STOCKIST_SUB_CODE

==HAULIERS==
This table stores the Hauliers.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* HAULIER_CODE
* NAME
* STOCKIST_CODE
* STOCKIST_SUB_CODE (001)

Index:
# COMPANY_CODE/WAREHOUSE_ID/HAULIER_CODE

==CONTAINER_STATUS==
This is a lookup table for the container status.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* CONTAINER_STATUS_CODE
* DESCRIPTION

Index:
# COMPANY_CODE/WAREHOUSE_ID/CONTAINER_STATUS_CODE

==TRANSLATION_TABLE==
This generic lookup table is used to store the weights for 20ft containers.
* COMPANY_CODE
* WAREHOUSE_ID
* TRANSLATION_ID = "CWGHT"
* CODE
* DESCRIPTION
* CODE2 = the CONTAINER TYPE used to identify a 20ft container.

Index:
# COMPANY_CODE/WAREHOUSE_ID/TRANSLATION_ID/CODE

==FXM_USERS==
A generic table to store the basic user information

Fields:
* FXM_USERNAME
* FXM_DESCRIPTION
* FXM_PASSWORD

==FLEX_USER_COMP_WAREHOUSES==
A generic table to store the users' default warehouse.

Fields:
* COMPANY_CODE
* WAREHOUSE_ID
* LOGON_ID

==FLEX_USER_COMP_OWNERS==
A generic table to store the users' default account.

Fields:
* COMPANY_CODE
* LOGON_ID
* STOCKIST_CODE
* STOCKIST_SUB_CODE (001)


= EDI =
Each import and export of data can be created to work through the existing EDI capabilities of ''CALIDUS'' WMS, removing the need to have specific screens created within the Container Yard system to maintain them.

It is expected that a process will be created to sweep the system every 5 minutes for transactions that have completed but have not yet been sent via EDI.

If found, an email message will be sent per container.

The format of this message is defined in the document referenced as item 1 in Appendix A.

It is currently being investigated as to whether this process is going to change as part of this system refresh.

<!-- NEW PAGE --> 
= Appendix A: Sample Admin Screen Layouts =
'''A1: Login Screen'''

[[File:298608_CY_Login_1.png|border|Login Screen]]

'''A2: Main Screen and Menu'''

[[File:298608_CY_Main_1.png|border|600px|Main Screen and Menu]]

<!-- NEW PAGE --> 
'''A3: Container Control Screen'''

[[File:298608_CY_Cont_Cont_1.png|border|600px|Container Control Screen]]

'''A4: Containers Screen'''

[[File:298608_CY_Cont_Task_1.png|border|600px|Containers Screen]]

<!-- NEW PAGE --> 
'''A5: Containers Screen - Details Popup'''

[[File:298608_CY_Cont_Task_2.png|border|600px|Containers Screen - Details Popup]]

'''A6: Containers Screen - Edit Container'''

[[File:298608_CY_Cont_Task_3.png|border|Containers Screen - Edit Container]]

<!-- NEW PAGE --> 
'''A7: Location Maintenance Screen'''

[[File:298608_CY_Location_1.png|border|600px|Location Maintenance Screen]]

<!-- NEW PAGE --> 
{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=WMS
|Ref1=MSC CODECO EDI.zip
|RefV1=N/A
|RefDate1=N/A
|Ref2=2007 to 2012.xls
|RefV2=N/A
|RefDate2=N/A
|Ref3=Stock Holding Report.xlsx
|RefV3=N/A
|RefDate3=N/A
|Ref4=Container screen shots.docx
|RefV4=N/A
|RefDate4=N/A
|REQ=0
|EST=0
|FS=3
|TS=0
|DEV=35
|ST=10
|IMP=5
|PM=5
|Client=PROD
|Year=2012
|FSEST=N
|Rev1=Phil Harding
|Rev1Title=OBS Project Manager
}}</div> 
[[Category:{{#var:Client}} REQ]]
[[Category:{{#var:SystemCode}}]]