User Requirement Specification

User Requirement Specification
Workshop E – Job Planner

Integration
Reference No. :
Version No. :
Create Date :
Prepared By :
Reviewed By :
Approved By :
Distribution To :
Distributed :
Date
Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 1 of 16

Trademarks: All brand names and product names used in this document are trade names, service marks, trademarks or
registered trademarks of their respective owners. ecVision Ltd. is not associated with any product or vendor mentioned in
this document.
Statement of Confidentiality
Non Disclosure Statement

Information contained in this document is proprietary
to ecVision Ltd. This document or its information may
not be copied, reproduced, disclosed, transferred,
reduced in any form, transmitted, publicly revealed by
any means, electronic or otherwise, without written
permission of ecVision.

this document.
Change History
Seq. Revised by Version Date Change Summary

this document.
TABLE OF CONTENT
1 SCOPE 5
2 DETAILS OF USER REQUIREMENTS...............................................................6
2.1 DATA EXCHANGE OVERVIEW................................................................................6
2.2 IMPORT JOB PLANNER........................................................................................9
2.3 EXPORT JOB PLANNER.....................................................................................10
2.4 JOB PLANNER & XPC SCHEDULE DATA SYNCHRONIZATION IN LOGON2...................10
2.5 OTHER REQUIREMENTS OF JOB PLANNER & XPC SCHEDULE...................................11
2.6 ASSUMPTIONS................................................................................................. 11
APPENDIX 12
2.7 EXISTING HBC TEXT FILE FORMAT......................................................................12
2.8 EXISTING LINMARK LOGON XML FILE FORMAT....................................................14
PROJECT MANAGER’S AND PROJECT AUTHORITY’S SIGNITURE............16

this document.
1 SCOPE
The scope of Job Planner Integration Requirements is/are following:
• Import Job Planner for Customer Data Exchange
• Export Job Planner for Customer Data Exchange
• Integration of Job Planner and XPC Schedule Module

this document.
2 DETAILS OF USER REQUIREMENTS
2.1 Data Exchange Overview
The Job Planner Data Exchange Module can be divided into two major
flows:
• Import Job Planner Data and Update XPC Schedule Task.
Customer Import XPC

File Job Planner
Processor Schedule
Tables
Module
• Export Job Planner and Schedule Data.
XPC Export Customer

Job Planner
+ Schedule Processor File
Tables
Module

this document.
The Customer File contains all the
updated data which is provided by
Customer
Customer. For more details, please
File refer to Appendix 3.1
The Import Processor is responsible for

executing all the import procedures
which includes:
• Parse Customer Data File
Import • Resolve the difference of Data
Format between Customer Data
Processor
and Linmark Data
• Insert New Job Planner Data
• Update XPC Schedule Data
• Generate the result of Import
The Export Process is responsible for

executing all export procedures which
includes:
• Query all Job Planner Data which
need to export.
Export • Query all the Updated Job
Processor Planner Data from XPC Schedule
Module
• Combine these two sets of Data
to produce a full set of Job
Planner Data
• Generate the Export File
The Job Planner Tables store 3 kinds
of Data
• Original Job Planner Data.
• Customer-specific Setting.
Job • Cross-reference Setting for
Planner mapping of Customer and
Tables Linmark Data

this document.
The XPC Schedule Module is
responsible for
• Store the Job Planner Data which
can be updated by Linmark User.
XPC
• Provide function for user to
Schedule manipulate the XPC Schedule
Module Data
• Provide a View of Job Planner
Data.

this document.
2.2 Import Job Planner
1. All the Customer uploaded Job Planner files will be processed in

ascending chronological order.
2. System should provide Cross-reference tables for storing Customer-
specified Setting and the Import Mapping between Customer Job Planner
Data and Linmark XPC Data.
3. The Cross-reference Tables may also help to parse the Import File with
Customer-specific Format.
4. System should store the Original Job Planner Data for data mapping when
export and restoration of XPC Schedule.
5. System should also update the corresponding XPC Schedules for those
Job Planner records which can be matched to existing XPC Schedules.
6. For the mapping of Job Planner Records and XPC Schedule Records,
System should make use of key “Job-id” + “Milestone-id” + “Task-item” +
“Color”.
7. If the key (“Job-id” + “Milestone-id” + “Task-item” + “Color”) cannot be
mapped to existing Linmark XPC Schedule Record, then System should
create a new XPC Schedule Record for storing of that new Customer Job
Planner Record.
8. For each Customer Job Planner Record with same Job-id should be
grouped into a single XPC Schedule.
9. System should only modify Job Planner Data with “I” or “U” flag in XPC
Schedule Task. Fields that are updated include “Plan Date” (Schedule Due
Date in XPC Schedule), “Actual Date”(Complete Date in XPC Schedule)
and “Task/Milestone Status”.
10. For cancelled Job-id, system will mark the “Milestone Status” of
corresponding tasks in the corresponding XPC Schedule as cancelled. For
those Job Planner Tasks with “I” Flag, system will also cancel the
corresponding XPC Schedule Tasks.
11. For failed Milestone, system will fail the XPC Schedule Task and
regenerate a new XPC Schedule Task.
12. System produces a result log of import process for each Job Planner
Records.
13. All successfully processed files will be moved to a specific destination.
14. All failed files will be moved to another specific destination.

this document.
2.3 Export Job Planner
1. System should export Job Planner Data to a Customer-specified Format

File.
2. System should export all Job Planner record under the following
conditions:
a. The last updated date of record is current date
b. The action type of record is “U”(Update), which means this record
can be updated by Linmark user.
3. System should provide Cross-reference tables for storing customer setting
and the Export Mapping template between Customer Data and Linmark
Data for Export.
4. The Cross-reference Tables may also help to re-produce the Export File
with Customer-specified Format.
5. The exported files will be generated to a specific destination.
2.4 Job Planner & XPC Schedule Data Synchronization in

LOGON2
1. System should allow user to view the Original Job Planner Data.
2. System should allow user to view the Modified Job Planner Data, which
includes “Plan Date”, “Actual Date” and “Task/Milestone Status”.
3. System should allow user to update the Job Planner Data, which includes
“Plan Date”, “Actual Date” and “Task/Milestone Status”.
4. In order to roll back XPC Schedule Data that has been misstakenly
updated by user, System should restore those XPC Schedule Data from
Job Planner daily under the following conditions:
a. The Last Updated Date of record is current date and the action type
of record is “I” (Information), which means this record is for
information only and should not be updated by Linmark user.
System will restore “Schedule Due Date”, “Complete Date” and
“Milestone Status”.
b. The Last Updated Date of record is current date and the action type
of record is “U” (Update), which means this record can be updated
by Linmark user and also the “Schedule Due Date” in XPC
Schedule and “Plan Date” in Job Planner are not same. (In this
case, system will only restore the field “Schedule Due Date”)

this document.
2.5 Other Requirements of Job Planner & XPC Schedule
1. System should allow user to search Job Planner records by using Style
No, Vendor Name, and Delivery Date.
2. System should allow user export the Job Planner Data manually by
passing the Job Id.
3. System should allow administrator to configure Exportable Flag (Yes/No)
for Export Job Planner/XPC Schedule Data with the following parameter.
a. Customer
b. Vendor
c. Milestone Status
4. System should provide a report for displaying newly created Job Id and
cancelled Job Id.
2.6 Assumptions
1. End users are responsible for mapping XPC Schedules correctly to Order
Items.

this document.
APPENDIX
2.7 Existing HBC Text file format
HEADER RECORD
Field Name Data Lengt Start End Notes
Type h position position
Record-type Char 1 1 1 Value = ‘H’ (header)
File-type Char 30 2 31 Value = ‘milestone
update ‘
Header-date Numeric 8 32 39 Format is
DDMMYYYY
Header-time Numeric 8 40 47 Format is HHMMSS
Filler Char 553 48 600 Blanks
DETAIL RECORD
Record-type Char 1 1 1 Value = ‘D’ (detail)
Job-Id Numeric 7 2 8 Internal use only
Banner- Char 3 9 11 Value = ‘Bay’ or ‘Zel’
name
Style Char 30 12 41
Ship-date Numeric 8 42 49
Vendor- Char 50 50 99
name
Template- Char 50 100 149
name
Milestone-id Numeric 7 150 156 Internal use only
Milestone- Char 50 157 206
name
Task-item Char 50 207 256
Colour Char 50 257 306
Description Char 25 307 331
Item-due- Numeric 8 332 339
date
Item-revised- Numeric 8 340 347
date
Item-arrival- Numeric 8 348 355
date
Review-due- Numeric 8 356 363
date

this document.
Review- Numeric 8 364 371
revised-date
Review- Numeric 8 372 379 LINMARK UPDATE
actual-date FIELD *
Milestone- Char 15 380 394 LINMARK UPDATE
status FIELD *
Comments Char 100 395 494 LINMARK UPDATE
FIELD *
Action-id Char 1 495 495 Value = ‘U’ (update)
or
‘I’ (information only)
* LINMARK to update field if action-id of record = ‘U’
-all date fields are in format DDMMYYYY
TRAILER RECORD
Record-type Char 1 1 1 Value = ‘T’ (trailer)
File-type Char 30 2 31 Value = ‘milestone
update ‘
Trailer-date Numeric 8 32 39 Format is DDMMYYYY
Trailer-date- Numeric 8 40 47 Format is HHMMSS
time
Record- Numeric 10 48 57 Excludes header and
count trailer record

this document.
2.8 Existing Linmark LOGON XML file format
<?xml version="1.0" encoding="UTF-8"?>
<action_calendar_data_exchange file_timestamp="" >
<item rownum="">
<warning_error></warning_error>
<error_code></error_code>
<error_message></error_message>
<import_status></import_status>
<action_id></action_id>
<allow_update_record></allow_update_record>
<job_id></job_id>
<customer_code></customer_code>
<style></style>
<ship_date></ship_date>
<vendor_name></vendor_name>
<factory_name/>
<ship_mode/>
<template_name></template_name>
<style_status></style_status>
<milestone_id></milestone_id>
<milestone_name></milestone_name>
<task_item/>
<colour_code/>
<colour/>
<description/>
<item_due_date xsi:nil="true"/>
<item_revised_date xsi:nil="true"/>
<item_arrival_date xsi:nil="true"/>
<logon_original_plan_date></logon_original_plan_date>
<review_plan_date></review_plan_date>
<logon_plan_date></logon_plan_date>
<logon_actual_date xsi:nil="true"/>
<milestone_status/>
<logon_action_item_remarks></logon_action_item_remarks>
<logon_cust_no></logon_cust_no>
<logon_style_no></logon_style_no>
<logon_delivery></logon_delivery>
<logon_vend_no/>
<logon_fact_code/>
<logon_ship_mode/>
<logon_actn_id></logon_actn_id>
<logon_action_item_code></logon_action_item_code>
<logon_subitem_name/>

this document.
<add_info1/>
<add_info2/>
<add_info3/>
<add_date1 xsi:nil="true"/>
<add_date2 xsi:nil="true"/>
</item>
</action_calendar_data_exchange>

this document.
PROJECT MANAGER’S AND PROJECT AUTHORITY’S
SIGNITURE
This User Requirement Specification is agreed by Linmark and

ecVision representatives.
____________________
Project Owner
ecVision Limited
____________________
Project Assurance
Linmark (HK) Limited

this document.

User Requirement Specification

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

User Requirement Specification

Caricato da

Copyright:

Formati disponibili

User Requirement Specification

Workshop E – Job Planner

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 1 of 16

Non Disclosure Statement

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 2 of 16

Seq. Revised by Version Date Change Summary

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 3 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 4 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 5 of 16

• Import Job Planner Data and Update XPC Schedule Task.

Customer Import XPC

• Export Job Planner and Schedule Data.

XPC Export Customer

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 6 of 16

The Import Processor is responsible for

The Export Process is responsible for

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 7 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 8 of 16

1. All the Customer uploaded Job Planner files will be processed in

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 9 of 16

1. System should export Job Planner Data to a Customer-specified Format

2.4 Job Planner & XPC Schedule Data Synchronization in

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 10 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 11 of 16

2.7 Existing HBC Text file format

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 12 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 13 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 14 of 16

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 15 of 16

This User Requirement Specification is agreed by Linmark and

Copyright (c) 2005 by ecVision Ltd. All Rights Reserved. Page 16 of 16

Potrebbero piacerti anche