CF.

250 FUNCTIONAL DESIGN

GE Infrastructure
DE202.01 WIP
MS Project Interface

Author: TCS
Creation Date: 07. Jun 2006
Last Updated: 22. Jun 2006
Document Ref: CF250_FuncSpec_WIP-xx
Version: v.3.2

Approvals:

Thomas Schultze Project Manager – GE

Walter Neuhauser Project Manager – GE

Gabor Olah GE CoE

Ajay Sirohi Financial Controller - Europe

Document Control

Change Record
1

Date Author Version Change Reference

07.06.2006 D. Harmsen 0 Initial Version

08.06.2006 D. Harmsen 0 Adding more details on source Data
16.06.2006 D. Harmsen 1 Specification of Data to be transferred
19.06.2006 D. Harmsen 2 Updated with Frank’s input
20.06.2006 D. Harmsen 3 Update Call with M. Bembenek
21.06.2006 D. Harmsen 3.1
22.06.2006 D. Harmsen 3.1 Changes based on M. Bembenek feedback
22.06.2006 D. Harmsen 3.2 Add new Functionality ‘Availability’

Reviewers

Name Position

Distribution

Copy No. Name Location

1

2
3
4

Page ii of 24
Contents

Document Control......................................................................................................................ii

Executive Summary....................................................................................................................4

Business Rules............................................................................................................................5

Assumptions................................................................................................................................8

Solution Design..........................................................................................................................9
1. Solution Design – Outbound Interface.................................................................9
2. Solution Design – Inbound Interface, Part I Staging.........................................15
3. Solution Design – Inbound Interface, Part II Std. Interfaces.............................19
4. Solution Design – Interface Technology............................................................20
5. Solution Design – MS Project Scheduling Main Features.................................20
Process Flow.............................................................................................................................21

QFD Use Cases for Unit Testing..............................................................................................22

Appendix...................................................................................................................................23

Open and Closed Issues for this Deliverable...........................................................................24

Open Issues........................................................................................................................24
Closed Issues.....................................................................................................................24

Page iii of 24
Executive Summary
The standard Oracle Manufacturing Scheduling Module does not fit to the GE Wind requirements around
the WIP Job scheduling logic.

The main Requirements are

 Having the ability to hard link WIP jobs to keep the Production sequence when shifting an
Operation or a complete Job.

 Variable Leadtimes (TACT TIMES) for Operations for a given periode

 Recalculation and optimizing of WIP Jobs for station based production

Because Oracle Manufacturing Scheduling cannot deliver both of the needed main Requirements GE Wind
wants to integrate the existing MS Project Tool.

The purpose of this Document is to provide a rough solution concept as an bases for estimating the
integration effort and being able to decide what whether to go forward with this Solution or investigating
alternative options.

Page 4 of 24
Business Rules
1. To be selected WIP Job Routing Information in Oracle

 Explanation of Basic Agreements on Routing definition:

1. Tact time Subassembly = tact time Mainline
a. Subassemblies always in same Routing => One Routing fits All!
b. Subassembly always ends with beginning of Mainline Operation Sequence
c. Pick List Lots (PLL, Internal Kits, manufacturing Kits or Commissioning Kits,
Packing Pallets) become non scheduled Operation Sequence, for material
allocation only and do NOT get own item number/BOM
d. Sourcing Kits are the ONLY Kits to get own item number/BOM
2. Numbering system for Operation Sequence
a. Mainline Operation Sequence: hundreds, 100, 200, 300…..
b. PLL: single step, 101, 102, 103…, 201, 202….291, 292….
c. Subassemblies, parallel activity: ten with “high” number preferred to
show closeness to next Mainline Operation Sequence, 190, 290
3. A-Components are allocated to the Mainline Operations, all other components to
separate PLLs Operation Sequences

 Explanation of Routing Concept in Oracle

Numbering System for Opera tion Sequences

90 WIP1 (Mainline):
90 ends at 100
100 100 scheduled
101 101 sero time
102 sero time
102 200 scheduled
201 sero time
200 290 ends at 300
201 291 sero time
300 scheduled
290 390 ends at 400
291 400 scheduled

300
370
380 Legend:
390 Mainline Operation Sequence
Pick List Lot Operation Sequence
400 Subassembly Operation Sequence

GE Wind will have three different Types of Operations

1. Main Line Operations (red)

2. Assembly Operations running before and in parallel to the Mainline Operations (green)

3. Operations for Material Picking Lots with no impact on Lead Times (blue)

 WIP Job Header information: WIP Job Start and End Date

Page 5 of 24
 WIP Job Operation information:

WIP Job Operation Start and End Date and the Operation Status has to be selected

Descriptive Flexfield for creating additional Data Fields on Operation Level e.g.

o Operation relationship definition (e.g. Picking Operation 201 is related to Mainline OPS 200)

o Operation Predecessor Number (Oracle Operation Sequence ID)

o MS Project Task Type (Mainline-, Subassy- Operation)

o See Section ‘Solution Design – Outbound Interface’

Page 6 of 24
2. Selected WIP Job Routing Information has to be sent to MS Project

 MS Project application connects to a custom schema in the Oracle database via

ODBC /ADO

 MS Project application selects from Custom Database views

 MS Project imports the Data and build up the Project Plan (Only the ‘Green’ and ‘Red’
Operations)

3. WIP Job Routing Information has to be modified in MS Projects (Scheduling)

 During the Scheduling Process the WIP Job Start and End Date plus the Start and End
Date of each Operation will be updated in MS Project

 If needed Jobs have to be flagged as ‘Firmed’ in MS Projects to indicate the ASCP

Planning Process in Oracle (after sending Scheduled WIP Job Data back to Oracle) that
no rescheduling for those Jobs have to done

 Optional: Save Project Plan Local for caching

4. Sending modified WIP Job Data back to Oracle

 The WIP Job Start and End Date plus the Start and End Date of each Operation will be
sent back from MS Project to Oracle.

 MS Project application connects to a custom schema in the Oracle database via

ODBC / ADO

 MS Project Application inserts into custom staging tables.

5. Processing modified WIP Job Data in staging Tables

 Custom concurrent program selects from staging tables and inserts rows into
standard interface tables

 Custom concurrent program selects related ‘Blue’ Operations, calculates the Date
(Start Date = End Date = Start Date of related Main- or Subassy-Operation) and
inserts into standard interface tables

 The Standard Oracle WIP Scheduling Interfaces will be used for that

 Standard open interface imports data into base tables.

Page 7 of 24
Assumptions
1. Data Transfer will be done by a direct Database Link.

2. A specific Database User will be created to connect the Oracle Database. That
user is only permitted to Read and Update only the WIP Interface Staging
Tables.

3. The main MS Project related functionalities will still remaining in Access

Database with the exception of storing Assembly and Main Component
information.

Page 8 of 24
Solution Design
This section describes the outbound Interface from Oracle as the leading System to MS Project and
the inbound Interface from MS Project back to Oracle. In Addition a short description of the
existing MS Project features are explained and the technical type of system integration is briefly
described.

1. Solution Design – Outbound Interface

Following will be the details of the outbound Interface functionality based on a Custom View in Oracle

Component Name: Oracle Outbound to MS Project

Reponsibility: Work in Process

Pre-Requisition / Setups:

1. To be set up a Descriptive Flexfield on WIP_OPERATIONS Level with the following

Segments (Attribute Fields):

a. Operation Type

b. Operation Relationship p

c. Operation Predecessor

d. Reason Code for Gaps in the Production Plan

e. Delay time for Gaps in the production plan

f. MS Project Task Type (Mainline-, Subassy- Operation)

2. To be set up a Descriptive Flexfield on BOM_OPERATIONAL_ROUTINGS Level with

the following Segment (Attribute Field), defined in Standard Routings:

a. Unique Identifier: Type of Production / Line Type (Moving Line, Station)

For Example:
10 = Moving Line 1
11 = Moving Line 2
20 = Station 1
21 = Station 2
3. To be set up a Descriptive Flexfield on WIP_DISCRETE_JOBS Level with the following
Segments (Attribute Fields), Not displayed:

a. Assigned Workstation No. for DTE production (Coming with inbound Interface)

Page 9 of 24
Data query logic:

The custom View has to select the Oracle Data based on the on the following Rules (Start Parameter in MS
Project):

a. Attribute for selecting only Heads, Hubs or DTEs [Planer Field in Organization Item]

b. Type Production / Line Type [Moving Line, Station]

c. WIP Job Status is Unreleased, Released, Completed, Closed [WIP Job Header]

d. Load Jobs including anciently created production sequence [YES / NO]

(Attention: Depending on the Job selection based on Job status the sequence can be
incomplete!)

e. WIP Job Type is only Standard

f. The Time Fence for the selected Data has to be variable [From Date / To Date]

g. When loading the Data from Oracle the Plan in MS Project will be build based on
Date Fields (sequence Predecessor / Successor). In addition a sequence number will
be stored in a Attribute Field on Operation Level.

Page 10 of 24
Data Structure and Source: The Outbound Interface is selecting the following Data from Oracle which
are mapped to the corresponding fields in MS Project.

Oracle Field Name Oracle Table or MS Project Data Data Description

View Name Field Name Type Format
WIP JOB Header (MS Project wording = Project Name + Running Number ???) Information
= MS Project Task Type ‘100’
ORGANIZATION_ID WIP_DISCRETE_ Organizatio Optional: In case
JOBS_V n the MS Project
Tool will be used
not only for MFG
Plant Salzbergen
this is the
identifier
WIP_ENTITY_NAME WIP_DISCRETE_ Job Number. Can
JOBS_V be overwritten in
the Oracle Form.
Not the Unique
identifier
WIP_ENTITY_ID WIP_DISCRETE_ Identifies
JOBS_V individual jobs
in a
given group and
ties a header
record to a set
of detail
records.
SCHEDULED_START_DA WIP_DISCRETE_ SCHEDULED START
TE JOBS_V DATE for the WIP
Job
SCHEDULED_COMPLETI WIP_DISCRETE_ SCHEDULED
ON_DATE JOBS_V COMPLETION DATE
for the WIP Job
PROJECT_NUMBER WIP_DISCRETE_ Project
JOBS_V definition in
PROJECT_NAME WIP_DISCRETE_ Oracle: A Project
JOBS_V can have more
TASK_NUMBER WIP_DISCRETE_ than one Turbine
JOBS_V attached to (e.g.
TASK_NAME WIP_DISCRETE_ Windfarm). Each
JOBS_V Turbine is tagged
to a different
Task.
DUE_DATE WIP_DISCRETE_ Original
JOBS_V Scheduled Ship
Date coming from
Sales Order Line
PROMISE_DATE OE_ORDER_LINE Sales Order Line
S_V Date (Real Pick
up Date)
DATE_COMPLETED WIP_DISCRETE_ Real Status, WIP
JOBS_V Job Completion
Date
FIRM_PLANNED_FLAG WIP_DISCRETE_ Indicates whether
JOBS_V Oracle ASCP will
suggest a job to
be rescheduled or
not

INVENTORY_PLANNING MTL_SYSTEM_IT ‘Planner’>>

_CODE EMS_B Identifier for
Head, Hub, DTE

ATTRIBUTE1 BOM_OPERATION Unique

Page 11 of 24
 AL_ROUTINGS Identifier:
Production Type /
Line Type (Moving
Line, Station)
defined in
Standard Routing
ATTRIBUTE1 WIP_DISCRETE_ Configuration
Power Model JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE2 WIP_DISCRETE_ Configuration
Type JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE3 WIP_DISCRETE_ Configuration
Frequency JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE4 WIP_DISCRETE_ Configuration
Weather JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE5 WIP_DISCRETE_ Configuration
Hub Height JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE6 WIP_DISCRETE_ Configuration
Tower Type JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE7 WIP_DISCRETE_ Configuration
Base Length JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE8 WIP_DISCRETE_ Configuration
LVRT JOBS_V Details stored in
DFF Segments (DFF
AttributeX)
ATTRIBUTE9 WIP_DISCRETE_ Configuration
Country Code JOBS_V Details stored in
DFF Segments (DFF
AttributeX)

ATTRIBUTE13 WIP_OPERATION Reason Code (Task

S_V Constraint Code?)
for Gaps in the
Production Plan:
Field will be
filled with the
inbound Interface
coming from MS
Project. Has to
be re-selected.
ATTRIBUTE14 WIP_OPERATION Delay time for Gaps
S_V in the production
plan:
Field will be
filled with the
inbound Interface
coming from MS
Project. Has to
be re-selected.

ATTRIBUTE15 WIP_JOB_HEADE DTE: Assigned

R Workstation No.
Information has

Page 12 of 24
 to be stored in
Oracle (Coming
with inbound
Interface), (DFF
AttributeX)

WIP JOB Operation Information (MS Project = Cycle) = MS Project Task Type 120/121
and 130/131
OPERATION_SEQ_NUM WIP_OPERATION Operation
S_V Sequence (OPS)
Number
WIP_ENTITY_ID WIP_OPERATION Link to WIP Job
S_V Header (and
Project),
HEADER_ID in
Interface Table
FIRST_UNIT_START_D WIP_OPERATION OPS Start Date
ATE S_V First Unit.
Equals OPS Start
Date Last Unit
LAST_UNIT_START_DA WIP_OPERATION OPS Start Date
TE S_V Last Unit. Equals
OPS Start Date
First Unit
FIRST_UNIT_COMPLET WIP_OPERATION OPS End Date
ION_DATE S_V First Unit,
Equals OPS End
Date Last Unit
LAST_UNIT_COMPLETI WIP_OPERATION OPS End Date Last
ON_DATE S_V Unit, Equals OPS
End Date First
Unit
QUANTITY_COMPLETED WIP_OPERATION OPS Completion
S_V Date: Operation
Real Finish Date
when
QUANTITY_COMPLETE
D = 1
ATTRIBUTE1 WIP_OPERATION MS Project Task
S_V Type (Mainline-,
Subassy-
Operation) Has to
be maintained in
Oracle on Routing
Templates.
Indicator for
building the MS
Project Plan.
Task Type PLL
(Pick List Lot
Operation)
indicates that it
is an Operation
that will not be
selected to be
transferred.
ATTRIBUTE2 WIP_OPERATION OPS Relationship:
S_V Has to be
maintained in
Oracle on Routing
Templates.
ATTRIBUTE3 WIP_OPERATION OPS Predecessor:
S_V Has to be re-
selected.
Field will be
filled with the

Page 13 of 24
 inbound Interface
coming from MS
Project. (Maybe
more than one
Attribute Field
is needed)
ATTRIBUTE4 WIP_OPERATION Reason Code (Task
S_V Constraint Code?)
for Gaps in the
Production Plan:
Field will be
filled with the
inbound Interface
coming from MS
Project. Has to
be re-selected.
ATTRIBUTE5 WIP_OPERATION Delay time for Gaps
S_V in the production
plan:
Field will be
filled with the
inbound Interface
coming from MS
Project. Has to
be re-selected.

PROMISE_DATE PO_LINES Select Promise Date

for all Main
Components

Page 14 of 24
2. Solution Design – Inbound Interface, Part I Staging

Following will be the details of the Interface functionality

Component Name: Oracle Inbound from MS Project to Oracle Custom Staging Tables

Reponsibility: Work in Process

Pre-Requisitions / Setups:

Program Logic:

The Data to be selected in MS Project has to written into the Oracle Custom Staging Tables for Header and
Operation Information (GEWE_WIP_HEADER_STAGING and GEWE_WIP_DETAILS_STAGING)

Data Structure and Destination: The Inbound Staging Tables have to be designed as described below.

MS Oracle Field Oracle Table Data Data Description

Project Name Name Type Format
Field
Name

WIP JOB Header (MS Project wording = Project Name + Running Number ???)
Information = MS Project Task Type ‘100’
CREATED_BY
GEWE_WIP_HEAD Standard Who column.
ER_STAGING
CREATED_BY_
NAME GEWE_WIP_HEAD Standard Who column.
ER_STAGING
CREATION_DATE Has a NOT NULL
GEWE_WIP_HEAD restriction; not
ER_STAGING loaded into the table;
default is
SYSDATE.
LAST_UPDATE_ Has a NOT NULL
DATE GEWE_WIP_HEAD restriction; is
ER_STAGING not loaded into interface
table;
SYSDATE is used.
LAST_UPDATED_B Standard Who column.
Y GEWE_WIP_HEAD
ER_STAGING
LAST_UPDATED_ Standard Who column.
BY_NAME GEWE_WIP_HEAD
ER_STAGING
LOAD_TYPE HAS to be 3
GEWE_WIP_HEAD (3 = Update standard or
ER_STAGING non-standard Discrete
job)
GROUP_ID
GEWE_WIP_HEAD Identifies a batch of
ER_STAGING records for processing;
when loading detail
records, this column
cannot be NULL (see
Control Columns).
HEADER_ID Identifies individual
GEWE_WIP_HEAD jobs in a given group and
ER_STAGING ties a header record to a

Page 15 of 24
 set of detail records.
Cannot be NULL when
loading detail records.
Ignored by Repetitive
schedules.
WIP_ENTITY_ID WIP Discrete job
GEWE_WIP_HEAD identifier. Copied to
ER_STAGING WIP_DISCRETE_JOBS on job
creation. Must be unique
across all organizations.
Either ID or Name must be
entered on reschedule. If
both entered, must match.
If NULL on creation,
generated using a
sequence.
When rescheduling
Discrete jobs,
WIP_ENTITY_ID,
WIP_ENTITY_NAME, and
ORGANIZATION_ID,
ORGANIZATION_CODE
must match record in WIP_
DISCRETE_JOBS table or
you receive an error
message.
WIP_ENTITY_NAM GEWE_WIP_HEAD See WIP_ENTITY_ID.
E ER_STAGING

ORGANIZATION_C GEWE_WIP_HEAD If you only enter the

ODE, ER_STAGING code, the ID is derived
ORGANIZATION_I from
D ORG_ORGANIZATION_DEFINITI
ONS, thus, the ID must
exist and be active in
ORG_ORGANIZATION_DEFINITI
ONS

Job Start Date GEWE_WIP_HEAD Not needed, will be

ER_STAGING calculated based on
‘First Unit Start Date’
for first Operation

Job End Date GEWE_WIP_HEAD Not needed, will be

ER_STAGING calculated based on
‘First Unit Completion
Date’ for last Operation
FIRM_PLANNED_F WIP_DISCRETE_ Indicates whether Oracle
LAG JOBS_V ASCP will suggest a job
to be rescheduled or not
[Value must be 1, 2 (Y or
N)]

ATTRIBUTE13 WIP_OPERATION Reason Code (Task

S_V Constraint Code?) for
Gaps in the Production
Plan: Field will be
filled with the inbound
Interface coming from MS
Project. Has to be re-
selected.
ATTRIBUTE14 WIP_OPERATION Delay time for Gaps in the
S_V production plan:

Page 16 of 24
 Field will be filled with
the inbound Interface
coming from MS Project.
Has to be re-selected.
ATTRIBUTE15 WIP_JOB_HEADE DTE: Assigned Workstation
R No. Information has to be
stored in Oracle (Coming
with inbound Interface),
(DFF AttributeX)
WIP JOB Operation Information (MS Project = Cycle) = MS Project Task Type 120/121
and 130/131

GROUP_ID GEWE_WIP_DETA If details pertain to

ILS_STAGING header record loaded at
same time, value must be
same as GROUP_ID in
GEWE_WIP_HEADER_STAGING
table

LOAD_TYPE GEWE_WIP_DETA = 3 for loading /

ILS_STAGING updating an

operation

OPERATION_SEQ_ GEWE_WIP_DETA Operation Sequence (OPS)

ILS_STAGING No.
NUM

PARENT_ Link to WIP Job Header

(and Project)
HEADER_ID
FIRST_UNIT_
START_DATE GEWE_WIP_DETA Required for loading
ILS_STAGING operations; optional for
updating. To change
´schedule start or
completion date without
explosion,´must also
provide first unit start
date and last unit
completion date.
FIRST_UNIT_
COMPLETION_ GEWE_WIP_DETA Required for loading
DATE ILS_STAGING operations; optional when
updating.
LAST_UNIT_
START_DATE GEWE_WIP_DETA Required for loading
ILS_STAGING operations; optional when
updating.
LAST_UNIT_
COMPLETION_ GEWE_WIP_DETA Required for loading
DATE ILS_STAGING operations; optional for
updating. To change
schedule start or
completion date without
explosion, must also
provide first unit start
date and last unit
completion date.

ATTRIBUTE3 GEWE_WIP_DETA OPS Predecessor: Has to

ILS_STAGING be re-selected.

Page 17 of 24
 Field will be filled with
the inbound Interface
coming from MS Project.
(Maybe more than one
Attribute Field is
needed)
ATTRIBUTE4 WIP_OPERATION Reason Code (Task
S_V Constraint Code ?) for
Gaps in the Production
Plan:
Field will be filled with
the inbound Interface
coming from MS Project.
Has to be re-selected.
ATTRIBUTE5 WIP_OPERATION Delay time for Gaps in the
S_V production plan:
Field will be filled with
the inbound Interface
coming from MS Project.
Has to be re-selected.

Page 18 of 24
3. Solution Design – Inbound Interface, Part II Std. Interfaces

Following will be the details of the Interface functionality

Component Name: Oracle Inbound from MS Project to Oracle Custom Staging Table

Reponsibility: Work in Process

Pre-Requisitions / Setups:

Program Logic:

The Work Order Interface consists of two tables: the WIP_JOB_SCHEDULE_INTERFACE table (Open Job
and Schedule Interface table), and the WIP_JOB_DTLS_INTERFACE table (WIP Job Details Interface
table). You load header information into the WIP_JOB_SCHEDULE_INTERFACE table, and operations
into WIP_JOB_DTLS_INTERFACE table.

The Data Structure is the same then ‘Solution Design – Inbound Interface, Part I Staging’ except of the
following logic. A Custom Program has to be developed for loading the Data coming from the Custom
Staging Tables into the Standard Interface tables

1. The program has to capture all Data in the GEWE_WIP_DETAILS_STAGING Table and
has to check via the Operation relationship definition in the Standard Oracle WIP Job
Operation Table if there are related Operations defined that was original not loaded to MS
Project (because of the Operation Type = PLL). The relationship will be defined in the
DFF Attribute Fields in the WIP_OPERATIONS Table. If there are related PLL
Operations they have to be selected, the Date (First Unit Start Date = Last Unit Start Date
= First Unit End Date = First Unit End Date) has to be set to the Start Date of the related
Main or Assembly Operation.

2. Operations and/or Jobs in Status Completed are not getting updated.

3. If the program detects a Reason Code (Task Constraint Code; Field Name =
ATTRIBUTE4) and Delay Time (Field Name = ATTRIBUTE5) for Gaps in the
Production Plan for a specific Operation or a complete Job, in Oracle it has no impact.
The Data will only be transferred to the Standard Attribute fields on WIP Job Operation.

4. Check for interim changes on to be updated WIP Jobs. In case someone hast changed WIP
Job Header or Operation Data for a WIP Job to be imported the Program has to handel the
exception by sending a E-Mail notification.

a. Changes are: Add or remove Operation. Closing a WIP Jobs.

b. The Scheduled sequence of the WIP Jobs will be written back to Oracle
(Attribute Field) except of the Changed WIP Jobs. Changed Jobs are not written
back.

Page 19 of 24
4. Solution Design – Interface Technology

The current solution works with MS Project as frontend and MS Access as backend. MS Access stores the
template data which are editable via a Access GUI. Data exchange between MS Project and MS Access uses
ADO (Active Data Objects), which is compatible with Oracle in wide ranges.

The tool can read prepared view on Oracle using ADO. For writing back data, the Oracle data import
interface can be used. ADO need a direct access to parts of the database (i.e. a view) and a logon account to
read the needed data. Data access can be restricted a a single view, which provides MS Project with all
necessary data.

5. Solution Design – MS Project Scheduling Main Features

Main Features:

 MS Projects determines the start date of the job headers to find the initial order of the
job headers

 MS Project uses the (start date / order of the import table) of the operations and the
task type for separation operations into cycles and assemblies and to find the right order

 MS Project read local data to find the cycle times for moving lines or the number of
stations, determinded by the line type

 The plan is reviewed by the Production Scheduler and optimized, dependend on cycle
times, delays or other upcoming issues.

 Defining Workday Calendar, Shifts and Tact Times

New Features:

 ‘Firm’ functionality on WIP Job Header Level to indicate ASCP Planning whether
suggest a rescheduling or not. Based on that different Exception Messages are generated
in Oracle.

 Promise Date for Main Components

Page 20 of 24
Process Flow

Process Name: ‘Adjust Schedule’

BP080 reference GSCM

PR.8 Adjust Schedule Turbine

PR.9 Adjust Schedule Hub

PR.10 Adjust Schedule DTA

Page 21 of 24
QFD Use Cases for Unit Testing

Use Case
Actors Production Scheduler (PS)
Purpose WIP Job Scheduling
Precondition
Assumption

Main Path –
Actor Actor Action System Response
PS Log on to MS Project.
PS Enters select Parameters in the initial Dialog Form in MS Project
PS Run Data Import and ‘Build Project Plan’ functionality Project Plan is created in MS
Project
PS Check if Plan Objects (All Tasks) are linked correctly in MS Projects

PS Change the Job Sequence. Change the Tact Time, Change a Leadtime of a specific Operation manual.

PS Save / write back the new Scheduled Dates to Oracle Re-Scheduled WIP Jobs in
Oracle
PS Check Jobs in Oracle: Date Fields for all three Types of Operations and Firm Flag

PS Run MPS / MRP Plan in Oracle Planning results

PS Check exceptions messages in Oracle

PS Release new Planned WIP Jobs for given Time Fence

PS Log on to MS Project again.

PS Enters select Parameters in the initial Dialog Form in MS Project again

PS Run Data Import and ‘Build Project Plan’ functionality again Project Plan is created in MS
Project
PS Check if Plan Objects (All Tasks) are linked correctly in MS Projects

Exception Path -
Actor Actor Action System Response

Exception Path –
Actor Actor Action System Response

Page 22 of 24
Appendix

Page 23 of 24
Open and Closed Issues for this Deliverable
Open Issues

Issue Resolution

Do we really need the “Promise Date” for Main Components. Validate functional requirements
List of Use Cases have to be verified and extended after technical design

Closed Issues

Issue Resolution

Page 24 of 24