Pvos Ruc 037 Eta Calculation
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Pvos Ruc 037 Eta Calculation as PDF for free.
More details
- Words: 3,648
- Pages: 14
Port Vehicle Operating System Use Case Specification ETA Calculation RUC_037 Version No. 56.0
Copyright © 2001-2004 Ford Motor Company (U.S. and international notice, and original material was added in each indicated year.)
Originator: 9235618.doc Proprietary Record Type: Official
Page 1 of 14
Date Issued: <01/08/2007> Date Revised: <04/17/2007> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
Project Document Revision History Version Number
Date
Revision Author
1.0
05/08/2007
Umesh Bhatia
2.0
05/14/2007
Umesh Bhatia
Description Initial version 1. 2. 3.
3.0
05/14/2007
Umesh Bhatia
1. 2. 3. 4.
ETA calculation based on LOL and DPOE status added. Setting up Pre-defined number of days for LOL status added in Main Flow (ETA Calculation: Actual). Following Business Rules added : a. ETA recalculated at every status change b. Definition of Business Days c. ETA calculation will end at CDD status. Clear demarcation of start and end under Port Activity. Use of standard value when VIN is in LOL status incorporated in "Standard" ETA calculations. Use of pre-defined value when VIN is in LOL status incorporated in "Actual" ETA calculation table. Business Rule indicating scenarios when ETA will be re-calculated.
5.
4.0
05/15/2007
Umesh Bhatia
Business Rule mentioning Inland Transit Time (Actual) is summation of Leg 1 + Leg 2 movements. Business Rule added : The trigger for Offline Unranked and Offline Ranked vehicles are identified at the Occurrence Level in the Vehicle Setup Use Case (RUC_045)
5.0
05/16/2007
Umesh Bhatia
Issue Id 5039163: Following business rule added : When a VIN has multiple holds consider the hold with no end date as vehicle 'not available' and produce the ETA as not available. If the VIN has multiple holds with multiple end dates take the end date with the greatest value and use that as the start for the new ETA calculation. E-tracker Issue Id 5048472: Business rule pertaining to calculation of Transit Time in a multi leg move appended.
6.0
10/31/2007
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Umesh Bhatia
ETA Calculation table: Offline – Ranked: Calculation for Inland Transit changed from "Actual" to "Standard"
Page 2 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
1
Table of Contents 2 INTRODUCTION......................................................................................................................................................4 2.1 Purpose..................................................................................................................................................................4 2.2 Instructions............................................................................................................................................................4 3 USE CASE INFORMATION ...................................................................................................................................4 2.1 RUC_037..............................................................................................................................................................4 2.2 Actors ..................................................................................................................................................................4 2.3 Summary of Use Case...........................................................................................................................................5 4 TRIGGER...................................................................................................................................................................5 5 PRE-CONDITIONS...................................................................................................................................................5 6 POST-CONDITIONS.................................................................................................................................................5 7 FLOW OF EVENTS..................................................................................................................................................6 7.1 Main Flow.............................................................................................................................................................6 7.2 Customer Acceptance Test Cases........................................................................................................................10 7.3 Alternate/Exception Flows..................................................................................................................................10 8 BUSINESS RULES..................................................................................................................................................12 9 USE CASE SPECIFICATION APPROVAL.........................................................................................................14 .....................................................................................................................................................................................14
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 3 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
2
Introduction
This document captures detailed functional requirements. Technical or application architecture should not be detailed here. Technical details are recorded in the System Architecture Documents and Supplementary Specifications. High level data and business process is documented in the Business Owner View. Overall risk and project time constraints as well as a summary of the business case are documented in the Project Charter. 2.1
Purpose
Each use case discovered during the creation of the Use Case Model will generally need to be detailed with a Use Case Specification. This use case captures the details of maintaining the employee portfolio. 2.2
Instructions
Optimally, a small team of 2 or 3 people including at least one customer or customer representative should write the use cases. If more stakeholders desire input consider a secondary approval process with a larger audience. Before creating individual Use Case specifications, first create the Use Case Model. This document should be shared with all project stakeholders before proceeding to detailed use case specifications.
3
•
Iteratively increase the detail in the use cases.
•
Create a multi-layer use case hierarchy to provide the correct level of detail to the development team while retaining the bigger picture point of view.
•
Move long complex sections of use cases to a subordinate use case.
•
Merge short trivial use cases into the super use case to achieve two or three levels of uniform description.
•
If all the actors associated with this use case are system actors, define the Interface Specifications (e.g. Transaction Layout, Message Format, etc.) in the Business Rules section of this document.
Use Case Information 2.1 RUC_037 2.2
Actors
An actor is someone or something outside the system or business that interacts with the system or business.
Actor Name
Role
Description
Brand Personnel
Primary
Brand Personnel will set up the parameters for PVOS to ETA calculation
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 4 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
2.3 Summary of Use Case
4
•
PVOS will calculate & maintain the ETA from vehicle loaded at origin port (SEA status) till vehicle is delivered to the dealer (CDD status)
•
This ETA will be calculated considering the pre-defined activity & transit time (Port process, LOL, Inland road & rail transit time).
•
PVOS shall update the actual ETA value to the destination systems identified in Vehicle Setup Use case.
•
All mentioned process needs to have alternate / exception flow
Trigger •
5
6
VIN's are loaded on the vessel at the Port of Origin and VIN's are in "SEA" status.
Pre-conditions •
Port Pairs (Start and End Point) are defined with standard transit times.
•
Time required to carry out the pre-defined activities at the port is defined.
•
Standard off set value in number of days defined when VIN will be in LOL status.
•
Transit Times from Port to respective Dealer location(s) is defined.
Post-conditions •
Updated ETA for VIN(s) available and destination systems updated with the same.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 5 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
7
Flow of Events
7.1 7.1.1
Main Flow Setting up of Port Pairs: Standard Brand Personnel sets up a combination of port pairs in PVOS. The port pairs will consist of combination of Starting Port (Port of Origin) and Destination Port populated via the Ocean feed.
7.1.2
7.1.3
7.1.1.1
Brand Personnel will select "Port Pairs Setup" option under the ETA tab.
7.1.1.2
Brand Personnel will select the Port of Origin and Destination Port with the Port ID.
7.1.1.3
Brand Personnel will add the estimated time of travel between the port pairs.
7.1.1.4
Brand Personnel saves this combination of Port Pairs with the transit time in PVOS.
Setting up timelines for port activities (From FPR to Monroney Complete): Standard Based on the activities (from FPR to Monroney complete) to be undertaken at the Port; Brand Personnel sets up the standard off set value in terms of number of days. 7.1.2.1
Brand Personnel selects the "Port Activity" option under the ETA tab.
7.1.2.2
Brand Personnel selects the Port ID, Brand, Model and Year and enters the standard off set value in number of days and saves the same in PVOS.
7.1.2.3
This value will be used by PVOS with LOL and Inland Transportation standard off set values for calculating the ETA.
Setting up timelines for VIN(s) in a Load Line (LOL) status: Standard 7.1.3.1
Brand Personnel selects "LOL" option under the "ETA" tab and the default Occurrence Code (6200) will be displayed.
7.1.3.2
Brand Personnel selects the Port ID, Brand, Model, Year,
7.1.3.3
Brand Personnel enters the "Y" number of days and saves the combination in PVOS.
7.1.3.4
This value will indicate the number of days a VIN will be in Load Line (LOL) status and will be used for calculating an ETA.
7.1.3.5
This value will be used by PVOS with Port Activity and Inland Transportation standard off set values for calculating the ETA.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 6 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.1.4
Setting up of transit times for Inland Transportation: Standard Brand Personnel sets up transit times (time on road only) for Inland Transportation as a part of the Cost Set Up – Freight Billing (Use case RUC_039). This will consist of Dealer Location, Mileage and the transit time in number of days.
7.1.5
7.1.4.1
Brand Personnel will select the "Inland Transportation" option under the ETA tab.
7.1.4.2
Brand Personnel selects the Port ID, Brand, Model and Year and enters the standard off set value in number of days and saves the same in PVOS.
7.1.4.3
This value will be used by PVOS with Port Activities and LOL standard off set values for calculating the ETA.
ETA calculation Report: Standard Brand Personnel can view a combined total of standard offset values using Port, Brands, Model, Year combinations. 7.1.5.1
Brand Personnel will select the "ETA Calculation Report" option under the ETA tab.
7.1.5.2
Brand Personnel selects the Port ID, Brand, Model and Year and submits the selection using the Report tab.
7.1.5.3
Based on the selection(s) PVOS will populate the individual standard off set values for Ocean, Port Activities, LOL and Inland Transportation and also their summation for display.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 7 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
7.1.6
ETA calculation: Actual 7.1.6.1
PVOS will receive the vessel details from the Ocean Carrier System (RUC_001) this will also include the ETA of the Ocean Carrier to the Port of Discharge. Based on the standard off set values defined for Port Activities, LOL and Inland Transportation PVOS will calculate the ETA at a VIN level by adding the standard off sets to the vessel ETA.
7.1.6.2
Brand Personnel will have to set a pre-defined value which will be used for calculating ETA for Offline & Ranked VIN's: o Brand Personnel selects "Pre-defined Offline & Ranked" option under the "ETA" tab. o Brand Personnel selects Offline & Ranked option and the default Occurrence Code (4000) will be displayed. o Brand Personnel selects the Port ID, Brand, Model, Year, o Brand Personnel enters the "X" number of days and saves the combination in PVOS. This value will indicate the number of days a VIN will be in Offline and Ranked status and will be used for calculating an ETA.
7.1.6.3
Brand Personnel will have to pre-define the number days a VIN will be in Load Line (LOL) status. o
Brand Personnel selects "LOL" option under the "ETA" tab and the default Occurrence Code (6200) will be displayed.
o
Brand Personnel selects the Port ID, Brand, Model, Year,
o
Brand Personnel enters the "Y" number of days and saves the combination in PVOS.
o
This value will indicate the number of days a VIN will be in Load Line (LOL) status and will be used for calculating an ETA.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 8 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.1.6.4
ETA calculation in PVOS will take into account the Respective VIN status i.e. SEA, FPR, STO – Ranked / Unranked, OFL – Ranked / Unranked, LOL, DPOE Whether the VIN has any Holds and if they are Dealer Assigned (Ship to Dealer) or Dealer Unassigned (No Ship to Dealer found) Based on the above PVOS will calculate the ETA as follows:
VIN Status O C E A N
Dealer Assigned (Ship to Dealer)
Vehicle ETA = Vessel ETA + Standard Offset value for Port Activities + Y Days (LOL) + Inland Transit time (Actual)
SEA
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual) If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available".
Unranked
Ranked
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". ETA = Rank Process Date + Y Days (LOL) ETA = Rank Process Date + Transit + Y + Transit Time (Actual) Days (LOL) + Time (Standard) If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". Unranked
OFL
Ranked
L O L
ETA = Current Date + Y Days (LOL) + Transit Time (Standard)
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available".
ETA = Current Date + Y Days (LOL) + Transit Time (Actual)
STO
A C T I V I T Y
Holds*
If the hold category doesn’t have any end date. Vehicle ETA = Vessel ETA + Standard PVOS will populate ETA Value as "Not Available". Offset value for Port Activities + Y Days (LOL) + Standard Offset value for Inland If the hold category indicates an end date: ETA = Transit time Hold Release Date + Transit Time (Standard / Actual)
ETA = Rank Process Date + Y Days (LOL) ETA = Rank Process Date + Y Days + Transit Time (Actual) (LOL) + Transit Time (Standard)
FPR
P O R T
Dealer Unassigned (No Ship to Dealer)
LOL
INTRANSIT DPOE
ETA = Not Available
ETA = Not Available
ETA = OFL Date (Occ Code: OFFLNE 4000) + X Days + Y Days (LOL) + Transit Time (Actual) If Calculated ETA < Current Date: ETA = Current Date + Y Days + Transit Time (Actual) + 1 Day ETA = LOL Occurrence Date (Occ Code: MLCOM 6200) + Y Days (LOL) + Transit Time If Calculated ETA < Current Date: ETA = LOL Occurrence Date + Transit Time + 1 ETA = DPOE Occurrence Date (Occ Code: DPOE 7000) + Transit Time If Calculated ETA < Current Date ETA = DPOE Occurrence Date (Occ Code: DPOE 7000) + Transit Time + 1
ETA = OFL Date (Occ Code: OFFLNE 4000) + X Days + Y Days (LOL) + Transit Time (Standard) If Calculated ETA < Current Date : ETA = Current Date + Y Days + Transit Time (Standard) + 1 Day
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual) If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
Not Applicable
Not Applicable
Not Applicable
Not Applicable
* - PVOS will always give priority to "Hold Release Date" when calculating ETA value
7.1.6.5
PVOS populates the ETA value and updates the Destination systems with an ETA date (MM/DD/YYYY) or "Not Available" on a real time basis.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 9 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.2
7.3 7.3.1
7.3.2
Customer Acceptance Test Cases 7.2.1
Check if PVOS is able to display the correct Port Pairs with standard off set values for the Port Pairs.
7.2.2
Check if PVOS is able to populate standard off set values for LOL status for a given Port ID.
7.2.3
Check if PVOS is able to populate standard off set transit values for Inland transportation from a given Port ID.
7.2.4
Check if PVOS is able to populate ETA based on standard off set values set for Ocean, Port, LOL and Inland Transit.
7.2.5
Check if PVOS is able to populate ETA values on a real time basis based on the feed received from Ocean Carrier systems.
7.2.6
Check if PVOS updates destination systems on a real time basis.
Alternate/Exception Flows. Brand Personnel wants to delete / edit information pertaining to standard off set values for Port Pairs set up in PVOS 7.3.1.1
Brand Personnel selects the combination of Port Pairs which has to be deleted / edited.
7.3.1.2
Brand Personnel changes the data as required in the fields / deletes the selected Port Pair.
7.3.1.3
Brand Personnel saves the changes.
7.3.1.4
Use case ends.
Brand Personnel wants to edit information pertaining to standard off set values entered for Port Activities 7.3.2.1
Brand Personnel selects the Port ID data for which has to be edited.
7.3.2.2
Brand Personnel changes the data as required in the field for the given Port.
7.3.2.3
Brand Personnel saves the changes.
7.3.2.4
Use case ends.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 10 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.3.3
7.3.4
Brand Personnel wants to edit information pertaining to standard off set values entered for Load Line status (LOL) 7.3.3.1
Brand Personnel selects the Port ID and Brand for which the data has to be edited.
7.3.3.2
Brand Personnel changes the data as required in the field for the given Port.
7.3.3.3
Brand Personnel saves the changes.
7.3.3.4
Use case ends.
Brand Personnel wants to delete / edit information pertaining to standard off set values entered for Inland Transit 7.3.4.1
Brand Personnel selects the Port ID and Brand.
7.3.4.2
PVOS displays the data with the standard transit time (off set value) for the given combination which has to be deleted / edited
7.3.4.3
Brand Personnel changes the standard transit time (off set value) as required in the fields or deletes the given record.
7.3.4.4
Brand Personnel saves the changes.
7.3.4.5
Use case ends.
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 11 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
8
Business Rules •
PVOS will always give priority to "Hold Release Date" when calculating ETA value.
•
When a VIN has multiple holds consider the hold with no end date as vehicle 'not available' and produce the ETA as not available. If the VIN has multiple holds with multiple end dates take the end date with the greatest value and use that as the start for the new ETA calculation
•
When calculating ETA for VIN's with Hold Release Date, PVOS will always look for the greater value (date) between Hold Release Date and Rank Process Date. For example: If the Rank Process Date is May 11, 2007 and Hold Release Date is May 16. PVOS will consider May 16 (date) for calculating the ETA.
•
To calculate the ETA for online ranked VIN's PVOS will use the "Rank Process Date" calculated in the Rank Vehicles by Plan / production Sort use case (RUC_011)
•
PVOS will re-calculate ETA when there is :
•
A change in a VIN Status.
•
Any change in Ocean ETA
•
Any change in "Hold Release Date"
•
Any change in Rank Process Date
•
Any change in VIN condition from Offline Waiting to Active or vice –versa
•
Changes made to the standard off set values will effect the ETA values on a real time basis and this will also be updated in the Destination system
•
Separate standard off set value for VIN's requiring additional days will be defined at a Model and Year level. For calculating ETA, wherever this is defined PVOS will add the value defined at a Model & Year level to the standard off set value defined at Port ID and Brand level. For Example: Port ID
Brand
Model
Year
Standard Off Set Value
ETA
A
BAL
JAG
--
--
15 Days
15 Days
B
BAL
JAG
XJ
2007
03 Days
18 Days
A. BAL + JAG = 15 Days B. BAL + JAG + XJ + 2007 = 3 Days
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 12 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification ETA (Model & Year Level) = A + B = 15 + 3 = 18 Days •
For calculating ETA for a Model and Year specific defined VIN requiring additional days. PVOS will add the standard off set value (additional days) defined for that Model and Year to the standard off set value defined for that Port ID and Brand.
•
PVOS will stop calculating ETA at CDD status.
•
"Days" referenced and defined in the use case are business days defined in Supplier Setup Calendar (RUC_039: Cost Setup Use Case)
•
Inland Transit Time (Actual) will always be a summation of Leg 1 and Leg 2 (tied via a Route ID setup in RUC_039 Cost Setup – Freight Billing Flow – 6.1.2), wherever applicable.
•
Standard value set up for LOL status will also be applicable when PVOS calculates ETA on Actual basis.
•
The trigger for Offline Unranked and Offline Ranked vehicles are identified at the Occurrence Level in the Vehicle Setup Use Case (RUC_045)
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 13 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
9
Use Case Specification Approval
Approval of the Use Case Specification
By signing this Control Sheet, I confirm that I approve Version.5.0. Of the Use Case Specification RUC_037, ETA Calculation PVOS Project Name
Project Team Role
Signature
Conditions
Date
N / Y (See below) James Harrington
Business Project Manager
Conditions Acceptance is conditional on the following:
Originator: <SCSL>/ 9235618.doc Proprietary Record Type: Official
Page 14 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Copyright © 2001-2004 Ford Motor Company (U.S. and international notice, and original material was added in each indicated year.)
Originator:
Page 1 of 14
Date Issued: <01/08/2007> Date Revised: <04/17/2007> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
Project Document Revision History Version Number
Date
Revision Author
1.0
05/08/2007
Umesh Bhatia
2.0
05/14/2007
Umesh Bhatia
Description Initial version 1. 2. 3.
3.0
05/14/2007
Umesh Bhatia
1. 2. 3. 4.
ETA calculation based on LOL and DPOE status added. Setting up Pre-defined number of days for LOL status added in Main Flow (ETA Calculation: Actual). Following Business Rules added : a. ETA recalculated at every status change b. Definition of Business Days c. ETA calculation will end at CDD status. Clear demarcation of start and end under Port Activity. Use of standard value when VIN is in LOL status incorporated in "Standard" ETA calculations. Use of pre-defined value when VIN is in LOL status incorporated in "Actual" ETA calculation table. Business Rule indicating scenarios when ETA will be re-calculated.
5.
4.0
05/15/2007
Umesh Bhatia
Business Rule mentioning Inland Transit Time (Actual) is summation of Leg 1 + Leg 2 movements. Business Rule added : The trigger for Offline Unranked and Offline Ranked vehicles are identified at the Occurrence Level in the Vehicle Setup Use Case (RUC_045)
5.0
05/16/2007
Umesh Bhatia
Issue Id 5039163: Following business rule added : When a VIN has multiple holds consider the hold with no end date as vehicle 'not available' and produce the ETA as not available. If the VIN has multiple holds with multiple end dates take the end date with the greatest value and use that as the start for the new ETA calculation. E-tracker Issue Id 5048472: Business rule pertaining to calculation of Transit Time in a multi leg move appended.
6.0
10/31/2007
Originator: <SCSL>/
Umesh Bhatia
ETA Calculation table: Offline – Ranked: Calculation for Inland Transit changed from "Actual" to "Standard"
Page 2 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
1
Table of Contents 2 INTRODUCTION......................................................................................................................................................4 2.1 Purpose..................................................................................................................................................................4 2.2 Instructions............................................................................................................................................................4 3 USE CASE INFORMATION ...................................................................................................................................4 2.1 RUC_037..............................................................................................................................................................4 2.2 Actors ..................................................................................................................................................................4 2.3 Summary of Use Case...........................................................................................................................................5 4 TRIGGER...................................................................................................................................................................5 5 PRE-CONDITIONS...................................................................................................................................................5 6 POST-CONDITIONS.................................................................................................................................................5 7 FLOW OF EVENTS..................................................................................................................................................6 7.1 Main Flow.............................................................................................................................................................6 7.2 Customer Acceptance Test Cases........................................................................................................................10 7.3 Alternate/Exception Flows..................................................................................................................................10 8 BUSINESS RULES..................................................................................................................................................12 9 USE CASE SPECIFICATION APPROVAL.........................................................................................................14 .....................................................................................................................................................................................14
Originator: <SCSL>/
Page 3 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
2
Introduction
This document captures detailed functional requirements. Technical or application architecture should not be detailed here. Technical details are recorded in the System Architecture Documents and Supplementary Specifications. High level data and business process is documented in the Business Owner View. Overall risk and project time constraints as well as a summary of the business case are documented in the Project Charter. 2.1
Purpose
Each use case discovered during the creation of the Use Case Model will generally need to be detailed with a Use Case Specification. This use case captures the details of maintaining the employee portfolio. 2.2
Instructions
Optimally, a small team of 2 or 3 people including at least one customer or customer representative should write the use cases. If more stakeholders desire input consider a secondary approval process with a larger audience. Before creating individual Use Case specifications, first create the Use Case Model. This document should be shared with all project stakeholders before proceeding to detailed use case specifications.
3
•
Iteratively increase the detail in the use cases.
•
Create a multi-layer use case hierarchy to provide the correct level of detail to the development team while retaining the bigger picture point of view.
•
Move long complex sections of use cases to a subordinate use case.
•
Merge short trivial use cases into the super use case to achieve two or three levels of uniform description.
•
If all the actors associated with this use case are system actors, define the Interface Specifications (e.g. Transaction Layout, Message Format, etc.) in the Business Rules section of this document.
Use Case Information 2.1 RUC_037 2.2
Actors
An actor is someone or something outside the system or business that interacts with the system or business.
Actor Name
Role
Description
Brand Personnel
Primary
Brand Personnel will set up the parameters for PVOS to ETA calculation
Originator: <SCSL>/
Page 4 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
2.3 Summary of Use Case
4
•
PVOS will calculate & maintain the ETA from vehicle loaded at origin port (SEA status) till vehicle is delivered to the dealer (CDD status)
•
This ETA will be calculated considering the pre-defined activity & transit time (Port process, LOL, Inland road & rail transit time).
•
PVOS shall update the actual ETA value to the destination systems identified in Vehicle Setup Use case.
•
All mentioned process needs to have alternate / exception flow
Trigger •
5
6
VIN's are loaded on the vessel at the Port of Origin and VIN's are in "SEA" status.
Pre-conditions •
Port Pairs (Start and End Point) are defined with standard transit times.
•
Time required to carry out the pre-defined activities at the port is defined.
•
Standard off set value in number of days defined when VIN will be in LOL status.
•
Transit Times from Port to respective Dealer location(s) is defined.
Post-conditions •
Updated ETA for VIN(s) available and destination systems updated with the same.
Originator: <SCSL>/
Page 5 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
7
Flow of Events
7.1 7.1.1
Main Flow Setting up of Port Pairs: Standard Brand Personnel sets up a combination of port pairs in PVOS. The port pairs will consist of combination of Starting Port (Port of Origin) and Destination Port populated via the Ocean feed.
7.1.2
7.1.3
7.1.1.1
Brand Personnel will select "Port Pairs Setup" option under the ETA tab.
7.1.1.2
Brand Personnel will select the Port of Origin and Destination Port with the Port ID.
7.1.1.3
Brand Personnel will add the estimated time of travel between the port pairs.
7.1.1.4
Brand Personnel saves this combination of Port Pairs with the transit time in PVOS.
Setting up timelines for port activities (From FPR to Monroney Complete): Standard Based on the activities (from FPR to Monroney complete) to be undertaken at the Port; Brand Personnel sets up the standard off set value in terms of number of days. 7.1.2.1
Brand Personnel selects the "Port Activity" option under the ETA tab.
7.1.2.2
Brand Personnel selects the Port ID, Brand, Model and Year and enters the standard off set value in number of days and saves the same in PVOS.
7.1.2.3
This value will be used by PVOS with LOL and Inland Transportation standard off set values for calculating the ETA.
Setting up timelines for VIN(s) in a Load Line (LOL) status: Standard 7.1.3.1
Brand Personnel selects "LOL" option under the "ETA" tab and the default Occurrence Code (6200) will be displayed.
7.1.3.2
Brand Personnel selects the Port ID, Brand, Model, Year,
7.1.3.3
Brand Personnel enters the "Y" number of days and saves the combination in PVOS.
7.1.3.4
This value will indicate the number of days a VIN will be in Load Line (LOL) status and will be used for calculating an ETA.
7.1.3.5
This value will be used by PVOS with Port Activity and Inland Transportation standard off set values for calculating the ETA.
Originator: <SCSL>/
Page 6 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.1.4
Setting up of transit times for Inland Transportation: Standard Brand Personnel sets up transit times (time on road only) for Inland Transportation as a part of the Cost Set Up – Freight Billing (Use case RUC_039). This will consist of Dealer Location, Mileage and the transit time in number of days.
7.1.5
7.1.4.1
Brand Personnel will select the "Inland Transportation" option under the ETA tab.
7.1.4.2
Brand Personnel selects the Port ID, Brand, Model and Year and enters the standard off set value in number of days and saves the same in PVOS.
7.1.4.3
This value will be used by PVOS with Port Activities and LOL standard off set values for calculating the ETA.
ETA calculation Report: Standard Brand Personnel can view a combined total of standard offset values using Port, Brands, Model, Year combinations. 7.1.5.1
Brand Personnel will select the "ETA Calculation Report" option under the ETA tab.
7.1.5.2
Brand Personnel selects the Port ID, Brand, Model and Year and submits the selection using the Report tab.
7.1.5.3
Based on the selection(s) PVOS will populate the individual standard off set values for Ocean, Port Activities, LOL and Inland Transportation and also their summation for display.
Originator: <SCSL>/
Page 7 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
7.1.6
ETA calculation: Actual 7.1.6.1
PVOS will receive the vessel details from the Ocean Carrier System (RUC_001) this will also include the ETA of the Ocean Carrier to the Port of Discharge. Based on the standard off set values defined for Port Activities, LOL and Inland Transportation PVOS will calculate the ETA at a VIN level by adding the standard off sets to the vessel ETA.
7.1.6.2
Brand Personnel will have to set a pre-defined value which will be used for calculating ETA for Offline & Ranked VIN's: o Brand Personnel selects "Pre-defined Offline & Ranked" option under the "ETA" tab. o Brand Personnel selects Offline & Ranked option and the default Occurrence Code (4000) will be displayed. o Brand Personnel selects the Port ID, Brand, Model, Year, o Brand Personnel enters the "X" number of days and saves the combination in PVOS. This value will indicate the number of days a VIN will be in Offline and Ranked status and will be used for calculating an ETA.
7.1.6.3
Brand Personnel will have to pre-define the number days a VIN will be in Load Line (LOL) status. o
Brand Personnel selects "LOL" option under the "ETA" tab and the default Occurrence Code (6200) will be displayed.
o
Brand Personnel selects the Port ID, Brand, Model, Year,
o
Brand Personnel enters the "Y" number of days and saves the combination in PVOS.
o
This value will indicate the number of days a VIN will be in Load Line (LOL) status and will be used for calculating an ETA.
Originator: <SCSL>/
Page 8 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.1.6.4
ETA calculation in PVOS will take into account the Respective VIN status i.e. SEA, FPR, STO – Ranked / Unranked, OFL – Ranked / Unranked, LOL, DPOE Whether the VIN has any Holds and if they are Dealer Assigned (Ship to Dealer) or Dealer Unassigned (No Ship to Dealer found) Based on the above PVOS will calculate the ETA as follows:
VIN Status O C E A N
Dealer Assigned (Ship to Dealer)
Vehicle ETA = Vessel ETA + Standard Offset value for Port Activities + Y Days (LOL) + Inland Transit time (Actual)
SEA
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual) If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available".
Unranked
Ranked
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". ETA = Rank Process Date + Y Days (LOL) ETA = Rank Process Date + Transit + Y + Transit Time (Actual) Days (LOL) + Time (Standard) If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". Unranked
OFL
Ranked
L O L
ETA = Current Date + Y Days (LOL) + Transit Time (Standard)
If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available".
ETA = Current Date + Y Days (LOL) + Transit Time (Actual)
STO
A C T I V I T Y
Holds*
If the hold category doesn’t have any end date. Vehicle ETA = Vessel ETA + Standard PVOS will populate ETA Value as "Not Available". Offset value for Port Activities + Y Days (LOL) + Standard Offset value for Inland If the hold category indicates an end date: ETA = Transit time Hold Release Date + Transit Time (Standard / Actual)
ETA = Rank Process Date + Y Days (LOL) ETA = Rank Process Date + Y Days + Transit Time (Actual) (LOL) + Transit Time (Standard)
FPR
P O R T
Dealer Unassigned (No Ship to Dealer)
LOL
INTRANSIT DPOE
ETA = Not Available
ETA = Not Available
ETA = OFL Date (Occ Code: OFFLNE 4000) + X Days + Y Days (LOL) + Transit Time (Actual) If Calculated ETA < Current Date: ETA = Current Date + Y Days + Transit Time (Actual) + 1 Day ETA = LOL Occurrence Date (Occ Code: MLCOM 6200) + Y Days (LOL) + Transit Time If Calculated ETA < Current Date: ETA = LOL Occurrence Date + Transit Time + 1 ETA = DPOE Occurrence Date (Occ Code: DPOE 7000) + Transit Time If Calculated ETA < Current Date ETA = DPOE Occurrence Date (Occ Code: DPOE 7000) + Transit Time + 1
ETA = OFL Date (Occ Code: OFFLNE 4000) + X Days + Y Days (LOL) + Transit Time (Standard) If Calculated ETA < Current Date : ETA = Current Date + Y Days + Transit Time (Standard) + 1 Day
If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual) If the hold category doesn’t have any end date. PVOS will populate ETA Value as "Not Available". If the hold category indicates an end date: ETA = Hold Release Date + Transit Time (Standard / Actual)
Not Applicable
Not Applicable
Not Applicable
Not Applicable
* - PVOS will always give priority to "Hold Release Date" when calculating ETA value
7.1.6.5
PVOS populates the ETA value and updates the Destination systems with an ETA date (MM/DD/YYYY) or "Not Available" on a real time basis.
Originator: <SCSL>/
Page 9 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.2
7.3 7.3.1
7.3.2
Customer Acceptance Test Cases 7.2.1
Check if PVOS is able to display the correct Port Pairs with standard off set values for the Port Pairs.
7.2.2
Check if PVOS is able to populate standard off set values for LOL status for a given Port ID.
7.2.3
Check if PVOS is able to populate standard off set transit values for Inland transportation from a given Port ID.
7.2.4
Check if PVOS is able to populate ETA based on standard off set values set for Ocean, Port, LOL and Inland Transit.
7.2.5
Check if PVOS is able to populate ETA values on a real time basis based on the feed received from Ocean Carrier systems.
7.2.6
Check if PVOS updates destination systems on a real time basis.
Alternate/Exception Flows. Brand Personnel wants to delete / edit information pertaining to standard off set values for Port Pairs set up in PVOS 7.3.1.1
Brand Personnel selects the combination of Port Pairs which has to be deleted / edited.
7.3.1.2
Brand Personnel changes the data as required in the fields / deletes the selected Port Pair.
7.3.1.3
Brand Personnel saves the changes.
7.3.1.4
Use case ends.
Brand Personnel wants to edit information pertaining to standard off set values entered for Port Activities 7.3.2.1
Brand Personnel selects the Port ID data for which has to be edited.
7.3.2.2
Brand Personnel changes the data as required in the field for the given Port.
7.3.2.3
Brand Personnel saves the changes.
7.3.2.4
Use case ends.
Originator: <SCSL>/
Page 10 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification 7.3.3
7.3.4
Brand Personnel wants to edit information pertaining to standard off set values entered for Load Line status (LOL) 7.3.3.1
Brand Personnel selects the Port ID and Brand for which the data has to be edited.
7.3.3.2
Brand Personnel changes the data as required in the field for the given Port.
7.3.3.3
Brand Personnel saves the changes.
7.3.3.4
Use case ends.
Brand Personnel wants to delete / edit information pertaining to standard off set values entered for Inland Transit 7.3.4.1
Brand Personnel selects the Port ID and Brand.
7.3.4.2
PVOS displays the data with the standard transit time (off set value) for the given combination which has to be deleted / edited
7.3.4.3
Brand Personnel changes the standard transit time (off set value) as required in the fields or deletes the given record.
7.3.4.4
Brand Personnel saves the changes.
7.3.4.5
Use case ends.
Originator: <SCSL>/
Page 11 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
8
Business Rules •
PVOS will always give priority to "Hold Release Date" when calculating ETA value.
•
When a VIN has multiple holds consider the hold with no end date as vehicle 'not available' and produce the ETA as not available. If the VIN has multiple holds with multiple end dates take the end date with the greatest value and use that as the start for the new ETA calculation
•
When calculating ETA for VIN's with Hold Release Date, PVOS will always look for the greater value (date) between Hold Release Date and Rank Process Date. For example: If the Rank Process Date is May 11, 2007 and Hold Release Date is May 16. PVOS will consider May 16 (date) for calculating the ETA.
•
To calculate the ETA for online ranked VIN's PVOS will use the "Rank Process Date" calculated in the Rank Vehicles by Plan / production Sort use case (RUC_011)
•
PVOS will re-calculate ETA when there is :
•
A change in a VIN Status.
•
Any change in Ocean ETA
•
Any change in "Hold Release Date"
•
Any change in Rank Process Date
•
Any change in VIN condition from Offline Waiting to Active or vice –versa
•
Changes made to the standard off set values will effect the ETA values on a real time basis and this will also be updated in the Destination system
•
Separate standard off set value for VIN's requiring additional days will be defined at a Model and Year level. For calculating ETA, wherever this is defined PVOS will add the value defined at a Model & Year level to the standard off set value defined at Port ID and Brand level. For Example: Port ID
Brand
Model
Year
Standard Off Set Value
ETA
A
BAL
JAG
--
--
15 Days
15 Days
B
BAL
JAG
XJ
2007
03 Days
18 Days
A. BAL + JAG = 15 Days B. BAL + JAG + XJ + 2007 = 3 Days
Originator: <SCSL>/
Page 12 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification ETA (Model & Year Level) = A + B = 15 + 3 = 18 Days •
For calculating ETA for a Model and Year specific defined VIN requiring additional days. PVOS will add the standard off set value (additional days) defined for that Model and Year to the standard off set value defined for that Port ID and Brand.
•
PVOS will stop calculating ETA at CDD status.
•
"Days" referenced and defined in the use case are business days defined in Supplier Setup Calendar (RUC_039: Cost Setup Use Case)
•
Inland Transit Time (Actual) will always be a summation of Leg 1 and Leg 2 (tied via a Route ID setup in RUC_039 Cost Setup – Freight Billing Flow – 6.1.2), wherever applicable.
•
Standard value set up for LOL status will also be applicable when PVOS calculates ETA on Actual basis.
•
The trigger for Offline Unranked and Offline Ranked vehicles are identified at the Occurrence Level in the Vehicle Setup Use Case (RUC_045)
Originator: <SCSL>/
Page 13 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
Port Vehicle Operating System ( PVOS) Use Case Specification
9
Use Case Specification Approval
Approval of the Use Case Specification
By signing this Control Sheet, I confirm that I approve Version.5.0. Of the Use Case Specification RUC_037, ETA Calculation PVOS Project Name
Project Team Role
Signature
Conditions
Date
N / Y (See below) James Harrington
Business Project Manager
Conditions Acceptance is conditional on the following:
Originator: <SCSL>/
Page 14 of 14
Date Issued: <03/29/2007> Date Revised: <> Record Series: 17.01 Retention Period: C+3,T
