Impact

Analyze Phase High Low

Easy 1 2
Step 6 Identify Potential X’s Implementation
3 4
Hard

Source Systems Procedures

No clear understanding of 1
units transfer
Delay in data
availability 3

Slow performance Too many duplications of

2 1
for getting data codes in baselines

Cycle time for feed

execution
3 SQL Replication slowing Delay in inputs from
overall process 2
planners
2 Variable network speed
1 Feed out indexes not up to
date Wrong inputs from
2 Variable servers speed 2
1 JAVA API rules planners
optimizations
Improper tagging after
1 Data preparation simplification 3 copy of projects

Others
Technology People

1/
GE GB LSS /
Improve Phase
Step 7,8,9 Screen potential causes, Discover variable
relationships Improved
Scores
Opportunity Review process within the Proposal lifecycle:
Step
Xelimination
Cycle time can vary from week to week

Pull from
source systems X
Data
Replication
Data
preparation
P6 Integration
API

Data

X
Data
Replication
P6 Integration
API
preparation for
relationship X
Data
Replication

Data Data preparation

preparation for
baseline
P6 Integration
API
Data
X
Replication
for baseline
relationships

Feed out
Data
X
Replication
P6 Integration
API - schedule
P6 Integration
API

2/
GE GB LSS /
Improve Phase
Step 7,8,9 Screen potential causes, Discover variable
relationships

We had strong engagement from the functional owner to identify potential causes

1. The number of changes happening in the source systems is directly impacting

the duration of the process
2. Having a replication of data between Oracle and SQL is one of the big driver of
the current cycle
3. The feed out process is taking more time than expected due to the number of
un-required indexes slowing down data insertion
4. JAVA API is taking a little more time than it should due to the complexity of
some rules (ex: dual manipulations)
5. Data phase preparation vary with amount of data to be processed
6. Wrong planners inputs impact the data selected by the feed

3/
GE GB LSS /