HUES Enterprise Consultants

fangscaryΤεχνίτη Νοημοσύνη και Ρομποτική

13 Νοε 2013 (πριν από 3 χρόνια και 4 μήνες)

207 εμφανίσεις

Bryan Kilpatrick Senior Account Manager

Stephen Martino Network Systems

Ella Buitrago Senior Integration
Specialist

Alexey
Yermilov Senior Application Developer



© 2013 GLOCO


Confidential and Proprietary


HUES Enterprise Consultants





GLOCO Warehouse Integration Proposal



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |


Table of Contents



Executive Summary

................................
................................
................................
................

3

Part I. Business Requirements

................................
................................
................................
....

5

Business Context

................................
................................
................................
................................
.

5

Use Case 1: GLOCO Customer Order Fulfillment Process (As
-
is)

................................
..........................

5

Use Case 1: GLOCO Customer Order Fulfillment Process (To
-
be)

................................
........................

5

Use Case 2: GLOCO Inventory Repl
enishment Process (As
-
is)

................................
.............................

6

Use Case 2: GLOCO Inventory Replenishment Process (To
-
be)

................................
............................

6

Required Functionality

................................
................................
................................
........................

7

Business Benefit Justification

................................
................................
................................
..............

7

Customer Order Fulfillment
-

Automation Business Benefits:

................................
...............................

7

Customers and Vendors
-

Automation Business Benefits:

................................
................................
....

7

Inventory Replenishment
-

Automation Busi
ness Benefits for GLOCO:
................................
................

7

Reduced Capital Expenditures & Labor Costs
-

Automation Business Benefits for GLOCO:

...............

8

Current vs. Solution Warehouse Cost Comparison

................................
................................
................

8

Capital and Operating Solution Costs

................................
................................
................................
...

8

Solution Benefits

................................
................................
................................
................................
.

9

FINAL Capital, Operating and Revenue Benefits

................................
................................
...................

9

Success Metrics

................................
................................
................................
................................
.

10

Part II. Technical Specification and Prototype

................................
................................
....
11

Architectural Approach

................................
................................
................................
.....................

11

Software Components

................................
................................
................................
.......................

14

Amazon Cloud Services

................................
................................
................................
.............................

15

Data Exchange Technology

................................
................................
................................
................................
...

15

Data Security and Transport

................................
................................
................................
................................
.

15

Development Platform

................................
................................
................................
..............................

16

Software Solutions

................................
................................
................................
............................

16

Module view

................................
................................
................................
................................
..............

16

Component Connector View

................................
................................
................................
.....................

18

Allocation View

................................
................................
................................
................................
..........

19

System Metrics

................................
................................
................................
................................
..........

20


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
i

Integration with existing enterprise systems

................................
................................
......................

21

Customer Order Fulfillment Integration

................................
................................
................................
...

21

Inventory Replenishment Integration

................................
................................
................................
.......

22

Data Design and Management

................................
................................
................................
..........

23

Order Fulfillment Data Design

................................
................................
................................
...................

23

Reporting

................................
................................
................................
................................
...................

24

Solution Demonstration

................................
................................
................................
....................

26

Part III. Implementation Plan

................................
................................
................................
....
27

Project Development and Deployment

................................
................................
..............................

27

Project Development Timeline

................................
................................
................................
..................

27

Figure 11: GLOCO Warehouse Integration Timeline

................................
................................
............................

28

Figure 12: Project Milestones

................................
................................
................................
...............................

29

Project Deliverables

................................
................................
................................
................................
..

29

Project Deployment

................................
................................
................................
................................
..

30

Software Design
................................
................................
................................
................................
....................

30

Business Process Redesign

................................
................................
................................
................................
...

31

Operational Governance

................................
................................
................................
...................

31

Resources

................................
................................
................................
................................
..................

31

Exception Resolution Flow

................................
................................
................................
................................
...

32

GLOCO, HUES Enterprise Consultants and Kiva Project Team

................................
................................
.............

32

GLOCO Stakeholders

................................
................................
................................
................................
.

35

Communications Dashboard

................................
................................
................................
.....................

37

Go Live and Post Go Live Communications Plan

................................
................................
.......................

37

Risk Management

................................
................................
................................
................................
......

38

Dependencies and Constraints
................................
................................
................................
..................

39

Supporting Non
-
Functional Components
................................
................................
................................
..

40

Background Processes Health Monitoring

................................
................................
................................
...........

40

Orders Execution Monitoring

................................
................................
................................
...............................

40

S3 and SQS Services Access Management

................................
................................
................................
............

41

Technical Support and Disaster Recovery

................................
................................
................................
............

41

Users Support and Help Desk

................................
................................
................................
....................

41

MHS Software and Hardware Support

................................
................................
................................
......

41

User Enablement and Training

................................
................................
................................
...........

42

Data and Content Management
................................
................................
................................
................

43


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
ii

Kiva System Data and Management

................................
................................
................................
.....................

43

ERP


MHS Data and Management

................................
................................
................................
......................

43

Amazon Storage Data Management

................................
................................
................................
....................

44

Amazon Simple Queue Service (SQS) Data Management

................................
................................
....................

44

System Administration Data and Management

................................
................................
................................
...

44

Kiva Software Updates

................................
................................
................................
................................
.........

44

System Patch Updates

................................
................................
................................
................................
..........

44

Success Metrics

................................
................................
................................
................................
.

45

Appendix A. GLOCO Software Integration Scripts

................................
................................
......
46

Upload a File to Amazon S3

................................
................................
................................
...............

46

Download a File from Amazon S3 and save it to a file

................................
................................
.........

46

Send Message
-

PHP Code for Amazon Simple Queue Service

................................
.............................

47

Receive Message
-

PHP Code for Amazon S
imple Queue Service

................................
.........................

47

Delete Message
-

PHP Code for Amazon Simple Queue Service

................................
..........................

47

GLOCO ERP XML Import Script For Customer Order Fulfillment

................................
..........................

48

GLOCO ERP XML Import Script For Inventory Replenishment

................................
.............................

48

Appendix B. GLOCO Control Documents & Data Descriptions

................................
....................
50

Customer Order Fulfillment Documents

................................
................................
.............................

50

Customer Order Fulfillment Control Documents

................................
................................
......................

50

GLOCO Data Description Standards

................................
................................
................................
..........

50

Inventory Replenishment Data Design And C
ontrol Documents

................................
..........................

5
1

Inventory Replenishment Data Design

................................
................................
................................
......

51

Reporting

................................
................................
................................
................................
...................

51

Inventory Replenishment Control Documents
................................
................................
..........................

53

Inventory Replenishment Data Description Standards

................................
................................
.............

54

Appendix C. GLOCO XML Document Type Samples

................................
................................
....
55

GLOCO XML Document Types

................................
................................
................................
............

55

Event Message Document Sample

................................
................................
................................
............

55

Shipment Order Document Sample

................................
................................
................................
..........

55

Shipment Order Result Document Sample

................................
................................
...............................

55

Inventory Replenishment Purchase Order Document in XML Form
at

................................
.....................

56


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
3

Executive Summary

Client

Headquartered in Cambridge Massachusetts with manufacturing plants and distribution centers in the Asia
-
Pacific
Region, South America and Europe, GLOCO is one of the largest manufactures of medical equipment in the world.
Boasting

7 Billion dollars in total revenue, GLOCO employs 29,000 employees with 110 company sites worldwide.
Michelle Matus, the new Chief Information Officer (CIO) is charged with ensuring the success of business objectives
through the use of technology solutio
ns.

Solution Provider

HUES Enterprise Consultants is an expert in supply chain automation for global corporations and is the preferred
Value Added Reseller (VAR) for Kiva Systems. The team is comprised of Bryan Kilpatrick, Senior Account Manager,
Stephen
Martino, Network Systems, Ella Buitrago, Senior Systems Integration Specialist, and Alex Yermilov, Senior
Application Developer.

Business Problem

Within GLOCO’s B2B and B2C Medical Supply Divisions, 50% of labor costs associated with order fulfillment are
a
result of workers walking around the warehouse locating racks, shelves, and picking and packing the correct
products to fulfill orders. This manual order execution has resulted in the following specific fulfillment deficiencies.

1.

Inefficient Use
of

Employee Labor:
Employees spend up to 70% of their day walking the warehouse.

2.

Order Fulfillment Inefficiency:
GLOCO employees currently work on a single order at a time.

3.

Inaccurate Order Fulfillment:
GLOCO’s order fulfillment accuracy is 95%.

4.

Sub
-
stand
ard Inventory Control:

The inability to accurately manage inventory results in lost sales, and
customer dissatisfaction.

Proposed Solution

HUES Enterprise Consultants is proposing a
Proof
of Concept

implementation of a world
-
class Automated Material
Handli
ng System that utilizes the Kiva Mobile Robotic Fulfillment System. Kiva is a total fulfillment solution that
incorporates hardware and software elements to perform replenishment, picking, and shipping sortation. The
system is comprised of a robotic fleet

of Kiva Robots and Pods (mobile racks) that report back order and operational
transactions status utilizing Kiva’s software agent as the bridge (Figure 1) to GLOCO’s Material Handling System. The
Kiva (MRFS) is a goods to person automation system that wil
l address GLOCO’s business identified problems by:




Eliminate

99% of employee warehouse walking.



Increase the inventory accuracy from 94% to 99.9%.



D
ouble the daily orders picked by each employee.



Increase the
order fulfillment accuracy from 95% to
99.9%.






HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
4

GLOCO Total Fulfillment Solution and Enterprise System Integration






Figure 1

HUES Enterprise Consultants will be designing and implementing a
Total Fulfillment Automated Solution that will migrate the following
GLOCO’s current in
-
桯hse
Ware桯hse Management 卹Ste洠
晵fc瑩tns 瑯 瑨t 䭉噁⁍a瑥rial 䡡n摬楮朠卹Stem (䭈匩S

佲der 偩捫楮g

卬潴瑩ng

佲der 偡ck楮g

兵Ql楴礠䍯itr潬

却Sck Re灬en楳iment

Lab潲 Management

The outlined issues will be addressed by replacing GLOCO’s manual person to goods order fulfillment process with Kiva’s
楮n潶o瑩te 杯潤猠瑯t灥rs潮 Ma瑥r楡l 䡡n摬in朠卹S瑥洠(M䡓⤻

周e
HUES Enterprise Consultants

team will work with
GLOCO’s
ICT

team to ensur
e the complete and smooth integration of the different integration points to the GLOCO's
WMS.

GLOCO’s WMS


MHS Bridge

The WMS


M䡓 br楤ie 瑨r潵杨 瑨e 畳e 潦o
s瑡n摡r搠浥ssa杩g朠pr潴潣ols (F呐ⰠJa癡 M匬
C畳瑯洬tMQ Series) w楬l 灲o癩摥 瑷o
-
睡礠楮tegra瑩tn
畳楮朠晩fe base搠(tex琬t晬a琬tor XML) 浥ssa杩n朠in 瑨e
s祮y桲hn楺i瑩潮 潦o卋唬 佰era瑯t, Re灬en楳imen琬t
佲ders, Mana来浥n琬tA摪畳t
浥n瑳Ⱐand Re灯pt
s瑡瑵tes⸠(F楧畲e ㈩⸠


F楧畲e 2


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
5

Part I. Business Requirements

Business Context



Use Case 1:

Customer Order Fulfillment



Use Case 2:

Inventory Replenishment

Use Case 1:
GLOCO Customer Order Fulfillment Process (As
-
is)

The
followi
ng diagram shows the
GLOCO AS
-
is order fulfillment process for picking 5 items.

The
picker
select
s

a

customer order
, repeats

the processing tasks, and closes the order
, then t
ransfers the order to Order Packing
.

Figure 3: As
-
is Flow Diagram (Use Case 1)


Use Case 1:
GLOCO Customer Order Fulfillment Process (To
-
be)

The following diagram shows GLOCO’s Automated Material Handling System that will automate the order fulfillment
process. The solution will raise fulfillment accuracy by 5.4%,

and
transform a
2
-
person task into a single
task
.


Figure 4: To
-
be Flow Diagram (Use Case 1)



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
6

Use Case 2:
GLOCO Inventory Replenishment Process (As
-
is)

The following diagram shows the receiving worker
checking in and transferring stock to the replenish worker who
repeat
s the replenishment process 5 times
to
put

a
way

all of the

received stock in the proper
bin
locations.


Figure 5: As
-
is Flow Diagram (Use Case 2)


Use Case 2:
GLOCO Inventory Replenishment Process (To
-
be)

The following diagram shows GLOCO’s Automated
Inventory Replenishment System that will automate the receiv
ing

stock. The solution will increase the

inventory accuracy by 5.4%,
and transform a 2
-
person task into a single
one
.


Figure 6:
To
-
be

Flow Diagram (Use Case 2)






HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
7

Required Functionality

The
following points outline the IT functionality to be provided under this proposal:

1.

MHS must be able to import and periodically update by requests from ERP/WMS core data (inventory,
customer
s, users, security).

2.

GLOCO ERP
modules
must
support the
import

of

XML documents by request
.

3.

MHS must be able to receive notifications and start processing new fulfillment and replenishment
orders requests.

4.

MHS must notify WMS about following processes completion/events: order fulfillment, replenishment,
and inventory adjust/reconciliation.



5.

MHS should start to process new orders less than 30 sec after notification.


6.

MHS must generate summary reports of dai
ly activity and reconcile it with WMS system with the
ability to deliver
via Internet mail
.

7.

MHS must be able to handle new inventory items at replenishment process and export them to
ERP/WMS

8.

MHS must integrate into GLOCO errors/notifications system.

9.

MHS
mu
st support PDF and XML report

formats to integrate into GLOCO ERP reporting system.

10.

GLOCO ERP must be able to save the Customer’s order form (Web interface and API).

11.

GLOCO ERP must be able to save the Vendor’s fulfillment order (web interface and API).

Bus
iness Benefit Justification

Customer Order Fulfillment
-

Automation Business Benefits:



Customer order processing will increase by 4x the order lines picked per day.



The MHS will decrease average order
-
to
-
ship time by 1 day.



Customer sales revenue will
increase 2% due to customer satisfaction with GLOCO’s fast order
-
to
-
ship
times.



The profit margin per customer order will increase by 2% as a result of a higher fulfillment rate that will
reduce order re
-
print, packing, and shipping costs for backordered i
tems.



The Material Handling System will cut the order fulfillment time by 5 minutes per order.



GLOCO’s customer service representatives will be able to provide real
-
time order status to its customers.



Newly implemented automation will reduce annual
operating costs by

reducing employee payroll by 60
%.



New efficiencies with the automated fulfillment system will lead to a reduced need for capital designated for
new warehouse construction.

Customers and
Vendors
-

Automation Business Benefits:



Customers
and Vendors will have and API and a web interface to submit orders to GLOCO.

Inventory Replenishment
-

Automation Business Benefits for GLOCO:



Customer Sales revenue will increase
though

improved In
-
Stock Inventory accuracy.



A 5.4% increase in cash flow will be realized as a result of improving inventory management.



Inventory will be replenished to the MHS faster that will reduce out
-
of
-
stock items by 5%.


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
8

Reduced Capital Expenditures & Labor Costs
-

Automation Business Benefi
ts for GLOCO:



Newly implemented automation will reduce annual operating costs by reducing employee payroll by

60%.



New efficiencies with the automated fulfillment system will lead to a reduced need for capital designated for
new warehouse construction.

Cu
rrent vs.
Solution
Warehouse
Cost

Comparison

The following table shows a cost comparison between the current operating system and the proposed solution.

Capital Expenditures & Operating Costs
3

Year Comparison

Description

QTY

Yearly Cost

3

Year Total
Old System

3

Year Total
Automated System



Warehouse employees payroll (Total
Number of employees)

100
/
40

$
4
,
000
,
000
/

$
1
,
600
,
000

$12,
000
,
000

$
4
,
800
,
000

Land Purchase/Lease

Eac栠卩瑥

2

␱ⰰ
〰ⰰ〰

$
2
ⰰ〰ⰰ〰



Ne眠Cons瑲畣瑩潮 / Eac栠
Ware桯hse

2

␱ⰰ
〰ⰰ〰

$
2
ⰰ〰ⰰ〰



Ware桯hse 佰era瑩tg

Eq畩p浥nt

2

␵〰$
〰0

␱$
0
〰ⰰ〰

␲ⰰ㈵ⰰ〰

佰era瑩t朠E
x
灥nses

less Lab潲


Eac栠hareh潵oe

2

␴〰ⰰ〰

$
8

ⰰ〰

$
ㄬ㠵㠬㔰1

Total Warehouse
Expenditures


$17,800,000

$8,683,500

Total
Operating
Savings Old System


New System

* Old warehouse yearly operating costs = $12,800,000

-
$
9
,
116
,
500

Capital and Operating
Solution
Costs

The following table shows the GLOCO Automated Material Handling
System Solution Benefit costs in financial terms.

Capital Costs

Description

Qty.

Extended Initial Cost

Annual Cost


Bots (Standard Duty)

35

$875,000

$131,250

Pods (Standard)

500

$500,000

$75,000

Ergonomic Work Stations

5

$50,000

$7,500

Wireless
Network Equipment

4

$75,000

$11,250

KIVA Material Handling Control Software

1

$400,000

$60,000

Kiva Material Handling Environment Software

1

$125,000

$18,750

Professional Services (WMS integration)

1

Included


$0

Hardware and Software Training


1

Included

$0

Total Capital
Cost
s

$2,025,000

$303,750



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
9

Operating Costs

Description

Qty.

Per Unit Cost

Annual Cost

Bots Annual Hardware Maintenance

35

$
3
,
750

$131,250

Pods
Annual Hardware
Maintenance

500

$
150

$75,000

Ergonomic Work Stations

Annual Hardware Maintenance

5

$
1
,
500

$7,500

Wireless Network Equipment

Annual Hdwe Maintenance

4

$
2
,
812.5
0

$11,250

KIVA Material Handling Control Software

Maintenance

1

$60,000

$60,000

Kiva Material

Handling Environment Sftw Maintenance

1

$18,750

$18,750

Professional Services (WMS integration)

1

$0

$0

Project Management Costs

1

$12,000

$12,000

Hardware and Software Training

1

$0

$0

Total Operating
Cost
s

$98,962.50

$315,750.00

Solution Benefits

The following table shows the GLOCO Automated Material Handling System Solution
Revenue benefits

in financial
terms.

Description

Estimated
Year 1
Benefit

Estimated
Year 2
Benefit

Estimated
Year 3
Benefit




Increased
Customer Satisfaction (2% increased revenue)

$468,000

$514,800

$566,280

Pickers job optimization (5 FTE)

$250,000

$250,000

$250,000

Increased Customer Order Profit Margins




␱㈱ⰶ㠰

␱㔸ⰱ㠴

␲〵ⰶ㌹

䥮捲Iase搠Cas栠hl潷


5⸴┠(䥮癥n瑯ty 噡l略 潦o
$ㄬ㔰〬1〰0

␱〵ⰳ〰

␱㌶ⰸ㤰

␱㜷ⰹ㔷

Total Revenue Benefits

$944,980

$1,059,874

$1,199,876

FINAL Capital, Operating and Revenue Benefits

The following table shows the
GLOCO Automated Material Handling System Solution Benefit
s

in financial terms

over
3 years
.

Description

Estimated
Benefit
s


Total Capital & Operating Costs Savings (3 Year)

-

$
9
,
116
,
500

Total Revenue Benefits (3 Year)

$
3
,
204
,
730

Total realized financial benefit from new
solution

$
12
,
321
,
230



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
10

Success Metrics

This proposal offers the following metrics for measuring the success of the project:

GLOCO Metric
s

GLOCO Goal
s


Increased Revenue

Customer order processing will increase by

4x the order lines picked per day.

Increased Revenue

Increase order fulfillment accuracy from 95% to 99.9%.

Improved Customer Experience

The MHS will decrease average order
-
to
-
ship time by 1 day.

Insurance Cost Reduction

Decrease GLOCO’s Insurance
Premium Costs by 5%.

Cash Flow

Increase GLOCO’s cash flow by 5.4%.

Inventory Accuracy

Increase the inventory accuracy from 94% to 99.9%.

Order Fulfillment Picking Rates

Increase GLOCO’s Order Fulfillment rate by 5.4%.


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
11

Part II. Technical Specification
and Prototype

After an extensive RFP process of Automated Material Handling Systems (MHS) and in
-
depth analysis of GLOCO’s
order fulfillment and inventory replenishment business requirements, GLOCO and HUES Enterprise Consultants
have chosen Kiva Systems a
s its Automated MHS. The following sections will describe the technical specifications
that will enable the integrations of Kiva Systems into GLOCO’s enterprise systems.



Architectural approach:

a broad overview of the solution and its components.



Softwa
re
components
:

a detailed description of software components and their interactions.



Software solution
s
:

a discussion of specific software packages.



Integration with existing enterprise systems:

interfaces between new and existing components.



Data design a
nd management:

architecture and flow of data between components.



Solution demonstration:

a guided tour of user interfaces for the solution.

Architectural Approach

The following figure provides a high level architectural approach of GLOCO’s Order Fulfillmen
t Process using
Amazon Cloud Services. As a standard approach, all communications between components use REST Web Service
protocol. The figure can be best understood by examining the lifecycle of the order fulfillment process.

1.

A GLOCO B2B ERP System, B2C
Customer or Inside Sales person places and order within the Order
Fulfillment Portal.

2.

The customer order data is saved in XML format on Amazon’s Simple Storage Service.

3.

An Order Event Message from the Amazon Simple
Storage (
using Amazon’s Messaging
Service) is sent to
GLOCO’s ERP system that an order has been placed.

4.

GLOCO’s ERP system retrieves the customer order and stores it in the ERP


WMS databases.

5.

MHS receives notification from ERP and starts processing new fulfillment orders within 30 second
s.


Figure 7: GLOCO Order Fulfillment High Level Architecture



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
12

The second figure provides a high level architectural approach of GLOCO’s Inventory Replenishment Process using
Amazon Cloud Services. The process can be best understood by examining the life
cycle of the inventory
replenishment process.


1.

A purchase order employee creates a PO using GLOCO’s ERP Purchasing Module.

2.

The purchase order data is saved in XML format on Amazon’s Simple Storage Service.

3.

A Purchase Order Event Message is sent from the Am
azon Simple Storage (using Amazon’s Messaging
Service) to the vendors ERP system that a purchase order has been placed.

4.

The vendor ERP system retrieves the customer order and stores it in their ERP databases, ready for
fulfillment.

5.

Vendor Ships the order t
o GLOCO’s Shipping & Receiving address.

6.

GLOCO Inventory Replenishment employee scans the inventory into the Kiva MHS System.

7.

The Kiva MHS System Exports Purchase Order & Inventory Data to GLOCO’s ERP and WMS systems.


Figure 8: GLOCO Inventory Replenishmen
t High Level Architecture






























HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
13

Figure 9: GLOCO Detailed Technical Architecture







HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
14

Software Components

The installation of the Kiva MHS software will be an enhancement / wraparound to GLOCO’s current ERP and WMS
Systems by automating the order fulfillment and inventory replenishment business processes. The integration of
GLOCO’s Enterprise Systems (ERP and

WMS) with Kiva’s Material Handling System (MHS) and Amazon’s S3 services
will require extensions to existing software.



The
Application Servers running

GLOCO’s ERP Software
are existing application servers running ERP
modules that:

o

Accepts Customer Order

Data from the Order Fulfillment Portal Web Servers.

o

Updates Customer Order Data Databases Received from Kiva MHS Application Databases.

o

Transfers customer order data to Kiva MHS Application Databases to ERP Databases.

o

Stores XML formatted customer and Pur
chase orders to Amazon’s Simple Storage Service (Via
Proxy Server).

o

Sends Customer Order or Inventory Event Messages to Amazon’s Messaging Service (Via Proxy
Server).




The
Application Servers running
GLOCO’s WMS Systems
is an existing supply chain applicat
ion that:

o

Receives Customer

Order Data from Kiva MHS Application Servers.

(Note: The existing WMS Systems must remain in existence for non
-
Kiva Automated Inventory)




The

Application Servers running

GLOCO Kiva MHS Systems
is a
n
automated Material Handling
System
(MHS) application that:

o

Imports and periodically updates customer & inventory replenishment order data from GLOCO’s
ERP and WMS systems.

o

Uses a MHS

to ERP script that runs continuously to:



Receive New Customer Order Data Notifications from ERP Data
bases to MHS Databases.



Transfer Completed Order Data from MHS Databases to ERP Databases.



Transfer Inventory Received Data from MHS Databases to ERP Databases.



Notify WMS & ERP on process completion/events (Order Fulfillment, replenishment, etc.)

o

Supports

Customer Order Lines Picked Reports, daily activity and reconcile with WMS.

o

Integrates and reports to standard GLOCO error notification and handling.

o

Supports the import of XML formatted files.

o

Processes received ERP orders within 30 Seconds of the custom
er order import.




The Web Servers running
GLOCO’s Order Fulfillment Portal Software

is an existing system that:

o

Provides a web interface for customer and inside sales ordering.

o

Web Server Statistics:



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
15



Web Site Hits
per

Day.



Web Browser Types Accessing
the

Order Fulfillment Portal.



Geographical Location of Users Utilizing the Order Fulfillment Portal.



Event time.




The Proxy Server will provide Proxy Services for GLOCO’s ERP Systems and perform the following:

o

Setup a secure SSL session with Amazon’s S3 servic
es.

o

Pass GLOCO’s Amazon Credentials for Authorization and Authentication.

o

Provide a Security Layer on top of GLOCO Enterprise Systems.




There will be S3 Amazon specific scripts that will be running on GLOCO’s ERP and Web Systems that send
the following dat
a to Amazon S3 Amazon Cloud service via (Proxy Server) using a secure SSL connection.

o

Immediately:

An XML formatted Customer Order Fulfillment or Inventory Replenishment Document.

o

Immediately:

A Customer Order or Inventory Replenishment Event Message.

Amazon Cloud Services

Many cloud solution providers exist that provide storage related services. Below are three solutions that provide
these services:

1.

Windows Azure Storage (
http://msdn.microsoft.com/en
-
us/...
)

2.

Amazon Simple Storage Service (
http://aws.amazon.com/s3/
)

3.

Google Cloud Storage (
htt
p://cloud.google.com/products...
)


The main reason that HUES Enterprise Consultants selected Amazon’s Simple Storage Service
is that Web Services
(AWS) also offers an integrated Messaging Service, which is key to signaling GLOCO’s ERP systems of new or
ders.
Secondly HUES Enterprise Consultants has strong internal PHP scripting support and have implemented Amazon’s
Simple Storage and Simple Queue Services at previous clients utilizing Kiva’s MHS Software with great success.
Further detail of the featu
res and security services of Amazon’s S3 Services are as follows:

Data Exchange Technology

GLOCO uses standard web service technology to facilitate the previously described processes using REST protocols.
The underlying storage (Simple Storage Service) and communications (Simple Queue Service) technology
is
provided via AWS.

Data Security and T
ransport

All transactions are protected by multiple security methods, one of which is a GLOCO Customer
-
assigned key.

The
services
can securely upload/download data to Amazon S3 via the SSL encrypted endpoints using the HTTPS
protocol. Amazon S3 also provi
des multiple options for encryption of data at rest
.




The
Amazon Simple Storage Service

(S3) provides Blackboard Services that:



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
16

o

Store XML documents as objects within S3. GLOCO provides two secure document spaces for each customer,
one for testing and one for production.

o

GLOCO and customers can read, write,
and delete objects
from the S3 customer objects
.

o

GLOCO and customer

object
s are

stored in a bucket and r
etrieved via a unique, Customer
-
assigned key.

o

Customer
bucket
s

can be
stored in several regions to address latency, cost and regulatory requirements
.

o

Data upload/download and encryption of data at rest are provided for additi
onal data protection.



The
Amazon Messaging Service
, Simple Queue Service (SQS) provides:

o

Message exchange to alert of Customer Orders and Inventory PO’s via Amazon (SQS) to exchange message
objects where one party originates messages and the other receives

them.

o

Two queues for document control, one that acts as an originator and the other as a recipient
.

o

A que
ue
that
can be created in any region and the message body can contain 64 KB of text in any format.

o

Messages can be sent, received or deleted in ba
tches of up to 10 messages or 64kb.

o

Messages can be retained in queues for up to 14 days.

o

Messages can be sent and read simultaneously.

Development Platform

The GLOCO Customer Web Portal’s presentation layer must be cross
-
browser compatible and support bo
th the
Macintosh and Windows operating systems. To ensure compatibility
on
the
client side we are using HTML5 with

CSS3 standards and jQuery with jQueryUI libraries. On server side we are

using

Apache Software Foundation by

using

the

Apache Cocoon serial
ize XML

to HTML pages.

Microsoft SQL 2012 was selected as the database server
platform because of its
AlwaysOn SQL Server Failover Cluster Instances and Availability Groups
features, and
integration with GLOCO’s current SQL Server environment for their
ERP systems.


Software Solutions

Module view

Presentation Layer:

This layer is comprised of the main user interface modules, which are responsible for sending
the presentation aspects of the solution to the user’s browser. This layer receives information and transaction
results from the application/business logic layer

and displays all system information to the user. This layer also has
direct interaction with the cross component services such as security, operational management, communications,
and reporting.

Application/Business Logic Layer:

This layer orchestrates al
l of GLOCO’s business requirements and workflows
for the customer order fulfillment and inventory replenishment processes.

Information resulting from the business
processes and workflows are shared with the integration layer for event notifications, data s
torage via the data
layer, and data transformation. This layer also makes use of the cross component services.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
17

Integration and Data Layer:

This layer provides the core scripting, data processing, XML Transformation, and data
storage services. This layer

is responsible for ensuring data integrity and appropriate storage in each respective
software component database. This layer also makes use of the cross component services.






HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
18

Component Connector View

The component connector view illustrates the logi
cal runtime connections and protocols used for module
intercommunication. The Web Browser performs REST invocations over HTTP(s) via the JQuery libraries to the
GLOCO Web Services residing on the web servers. The web servers act as main request proxy servi
ces, which
implement the common services such as security. Once the request is validated and a route is determined, the web
server issues a REST invocation via HTTP (S) to the application/business logic layer. Depending on the workflows
executed by the ap
plication/business logic layer, this layer will then issue the appropriate invocations via REST over
HTTP(s) to the integrated GLOCO and third party services. Once this process has been completed, the
application/business logic layer sends XML documents ov
er REST to the integration/data layer for XML processing,
transformation, and storage. The data layer utilizes ADO.NET to issue the appropriate SQL queries to persist the data
in the respective databases.










HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
19

Allocation View

The web browsers will be
hosted and executed on user’s mobile, laptop, or desktop computers. Amazon will be
hosting the third party S3 and SQS services, and will allocate the appropriate hardware and software necessary for
these common services. GLOCO is responsible for installin
g and configuring the network devices necessary for
inbound Internet or third party HTTP(s) traffic. These devices may include but are not limited to firewalls, load
balancers, and application layer firewalls. GLOCO will be hosting h
ardware and software fo
r the Apache
web servers,
which host the http(s) proxies. The web servers will be allocated in the demilitarized zone (DMZ). The application
servers will be hosted and allocated in GLOCO’s internal secured private network, which may only be accessed by
the

GLOCO web servers in the DMZ. The GLOCO Integration and data servers are also hosted in the interna
l private
network. The Microsoft SQL
servers will be configured in clustered and fault tolerant mode and will host all the
respective databases for the sol
ution.








HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
20


System Metrics

GLOCO System Metrics

Factor

Estimated Value


Number of Users

The projected number of users that will utilize the Kiva MHS system is 247. This is derived
from 190 Internet customers, 50 GLOCO vendors, 5 order pickers, and 2

inventory
replenishment workers.

Customer Order
Transactions

GLOCO will processes about 216 orders per 8
-
hour day based on an average of 12
lines per order.


This will translate into 78,840 orders per year being shipped and
processed through GLOCO’s ERP
-
WMS and Kiva MHS systems.

Inventory Replenishment
Transactions

GLOCO has 50 authorized vendors, each of which receives 24 Purchase Orders per year
that average 800 inventory line items. The Kiva MHS and GLOCO ERP
-
WMS systems will
receive and process
960,000 inventory lines per year.

Lines Per Day

It is estimated that each worker will pick 65 inventory lines per hour per Kiva workstation
(Total of 5 workstations) resulting in a total of 2,600 transactions lines being processed by
the Kiva MHS and GLOC
O ERP
-
WMS systems per 8
-
hour day.

System Response Time

GLOCO customer response time using the Order Fulfillment Portal will be based on their
Internet connectivity speeds and GLOCO’s web server response times.

The Page
-
Load Speed / Cost Calculator

was introduced during this engagement by Bryan
Kilpatrick to GLOCO and testing with a standard broadband connection shows that
GLOCO’s web page loads average 1.4 seconds. GLOCO continues to monitor the end
-
to
-
end
page load averages and add additional web

servers (if necessary) into the load balancer
web infrastructure to ensure predictable web server response times.

Server Availability

GLOCO’s ERP
-
WMS and Kiva MHS systems are designed in a server cluster environment
that allows GLOCO to fail over server
nodes for system hardware replacement, software
patching and Operating System patching. This ensures 100% uptime of GLOCO’s critical
processing systems.

Database Availability

GLOCO currently utilizes
SQL Server 2012

for its ERP systems that utilize the
A
lwaysOn
SQL Server Failover Cluster Instances and Availability Groups
features that ensure high
availability for their database infrastructure. The Kiva MHS databases instances will be
added to GLOCO’s existing SQL Server infrastructure to ensure 100% upt
ime of GLOCO’s
critical database infrastructure that supports the ERP
-
WMS and Kiva MHS applications.

Network Availability

The Kiva MHS system utilizes Extricom’s wireless network switches and wireless access
points that are installed in a 2N configuration
. The design deploys 2 wireless access
switches, each of which provide a primary and secondary wireless access point to the
wireless coverage areas within GLOCO’s warehouse.

Kiva Robots

A total of 35 Kiva robots exist in the configuration, each requiring

5 minutes of battery

HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
21

recharge every 2 hours. During an 8
-
hour shift each robot will be unavailable for a total of
40 minutes for recharging purposes resulting in 23.33 hours (approx. 3 robots) of
downtime. The system design requires 30 robots to meet the

order picking and inventory
replenishment business requirements of GLOCO and factors in 5 additional robots. The 5
additional robots allow GLOCO to continue to meet their business requirements by
providing 3 robots during battery maintenance periods, and

2 robots in the event of robot
failure.





Integration with existing enterprise systems

Customer Order Fulfillment Integration

The Kiva MHS core software components utilize the Kiva’s
WMS

API to integrate into GLOCO’s Enterprise ERP
-
WMS

module.

Upon the completion of the customer fulfillment process, the MHS customer order fulfillment record is
updated to the appropria
te ERP

modules on GLOCO’s systems.



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
22

Inventory
Replenishment Integration

The Kiva MHS core software components utilize the Kiva
’s ERP API to integrate into GLOCO’s Enterprise ERP
systems. Upon the completion of the inventory replenishment process, the MHS inventory record is updated to the
appropriate ERP modules on GLOCO’s systems.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
23

Data Design and M
anagement

Order Fulfillm
ent Data Design

The Order Fulfillment XML document stores the necessary information needed by the GLOCO ERP system to process
an order. Below is a table depicting the data fields necessary to create an XML formatted Order Fulfillment
document. During the

Implementation Phase, a data field mapping exercise will occur between GLOCO’s ERP
systems, Kiva Systems and the below XML fields to ensure cross system compatibility. See
Appendix B

for GLOCO
attribute naming stan
dards and
Appendix C

for a description of the xml attributes.


CustomerID

Customer

code

assigned

by

GLOCO

BusinessUnit

Customer

business

unit

identifier

assigned

by

GLOCO

OrderNumber

Customer assigned order number

OrderType

SO = Sales Order

OrderDate

Customer Order Date (date and time the order was placed)

ShipDate

GLOCO shipment date

Comments

Free

form

comments

Carrier

Carrier code

ServiceLevel

Carrier service level code


Gr潵湤, A楲


周T bel潷 摩d杲am (F楧畲e ㄰1 s桯睳⁴he C畳t潭er 佲der F畬晩fl浥nt 䑡瑡 Fl潷 f潲 a c畳瑯浥r l潣a瑥d 潮 瑨e
䥮Ierne琮 周T s瑡r琠潦o摡瑡 晬潷 be杩gs 睩瑨 a c畳瑯ter (a晴fr a畴uen瑩ta瑩tn) bein朠presented 睩瑨 瑨e Order
F畬晩fl浥n琠䑡瑡 En瑲y
卣Seen fr潭o瑨t Or摥r F畬晩fl浥nt Web Server 潶er a sec畲e c潮nec瑩tn⸠ 周e c畳瑯ter nee摳d
瑯tenter 楮 瑨t in景f浡瑩tn fr潭o瑨t 灲e癩潵v 瑡ble (C畳t潭or䥄Ⱐ䉵sinessUn楴Ⱐe瑣⸩ 潮 瑨e c畳瑯浥r order web
景fm an搠瑨tn c潭灬ete 瑨e 潲der⸠ 啰Un 潲der c潭ole瑩
潮Ⱐ瑨e
佲摥r F畬晩fl浥n琠
Por瑡l s瑯tes 瑨e C畳瑯浥r Order
in XML format on Amazon’s Simple Storage Service by using the Proxy Server Amazon credentials. The
Order
Fulfillment

Portal additionally places a Customer Order Event Message in GLOCO’s messaging
queue within
Amazon’s Simple Queue Service (SQS). Amazon’s Messaging Service then sends an Event Message to GLOCO’s ERP
system that initiates a continuously running PHP script (
See
Appendix A

for script details) that downloads the
Customer Order and imports it into GLOCO’s ERP and WMS databases. Finally a continuously running PHP script
running on the Kiva MHS downloads the new customer order and immediately begins order processing.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
24

Report
ing

During the Required Functionality phase of the project it was identified that the Kiva MHS

system

must support PDF
and XML report

formats

to integrate with GLOCO ERP reporting systems. The API’s of the Kiva MHS and ERP
systems allow for the transport
of the XML data between each of the systems, thus enabling GLOCO to continue to
use its ERP reporting systems.


Figure 10: GLOCO Order Fulfillment Data Flow





HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
25

GLOCO ERP
Database Entities:

The following GLOCO ERP database entities are updated during the above
dataflow:

Sales Database

Inventory Control Database

Shipping Database





***
NOTE:

See
Inventory Replenishment Data Design

in
Appendix B

for the Inventory Replenishment Data Design.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
26

Solution Demonstration

The following figure shows an image of the MHS<
-
>WMS Integration Dashboard. The dashboard shows the
inventory replenishment form and its graphic flow though the architecture
involved in the process. The Dashboard
tap shows the MHS Synchronization status of inventory, inventory replenishment and orders. The Inventory and
Inventory replenishment tap show the synchronization status detail of these tasks and the XML documents used

during the same tasks. The Orders tap shows the xml documents log as well.

Site with demonstration located at
http://hues.gloco.ermilov.com

















HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
27

Part III.
Implementation Plan

This part of the proposal describes the implementation plan for the solution.



Project development and deployment

describes the approach, timeline, and milestones.



Operational

governance

identifies the project team, describes how stakeholders will stay inv
olved, and
describes plans for handling risks, communication, and change during the project.



User enablement and training

describes how to train people for using the system.



Success metrics

explains
how the
outcomes of the project are

measured and reported
.

Project Development and Deployment

The GLOCO Warehouse Integration project automates both a hardware and software component of the order
fulfillment and inventory replenishment services within GLOCO. While the implementation of Kiva robots and
inventory

pod hardware will automate the pick and replenish functions, it is equally important to automate the
customer and inventory data integration and synchronization into GLOCO’s Enterprise ERP Systems. A three
-
day
design meeting will occur during the hardwar
e and software design phases between the teams responsible for each
of the five phases within the proposed proof of concept (POC) to ensure seamless integration between Kiva Systems,
GLOCO ERP and Vendor Enterprise Systems.

Project Development Timeline

T
he timeline below reflects the five major phases necessary for the successful implementation of the Warehouse
Integration POC Project for the GLOCO’s warehouse chosen as the pilot site. The first phase will include all project
stakeholders and owners of e
ach warehouse functional area to kick off both the project and requirements gathering
and documentation phase. The second phase will be designing the applicable Kiva and GLOCO hardware and
software architecture and interfaces including the required data de
finition templates (i.e. field mapping and XML
documents) and database schema. The third phase will be configuring and installing the major hardware and
software components of the Kiva robots, pods and wireless infrastructure in addition to the integration

interfaces
with the WMS and Amazon Web Services. The fourth phase involves testing the system, business processes, and
interfaces, which comprise the entire proposed solution. The final phase will provide training for the end users and
administrator in c
onjunction with the subsequent Go
-
Live of the POC environment. The project manager will
consistently communicate project status to stakeholders via a project status dashboard.

The training for this project will consist of Business Process training and Pro
of of Concept system training sessions
to ensure that all hardware, business process, and data integration are operational and clearly understood by
GLOCO personnel. The business process training will occur on August 28
th



September 3
rd

to introduce the

new
automated processes that are replacing the manual ones. Order Fulfillment, Inventory Replenishment, and ERP
Database POC training will occur simultaneously. The actual Go
-
Live and GO
-
Live support for the GLOCO Warehouse
Integration Project will be o
n September 20
th


October 4
th

with the HUES Enterprise Consultant Team on
-
site to
provide continued support, and training.


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
28


Figure 1
1: GLOCO Warehouse Integration Timeline



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
29


Figure 1
2: Project Milestones

Project Deliverables

Table 3.1 Project Deliverables

GLOCO
Warehouse Integration Proof of Concept Deliverables

Phases

Deliverables


Kickoff, Requirements Gathering and
Documentation



Business Requirements and Constraints Document



WMS


ERP


M䡓 啳e Cases



System Actors (Operators, Kiva Robots, and Systems)



Risk Analysis



Prelimi
nary Project Plan (See Figure 1
1)



GLOCO and Kiva Software and Hardware Designs



POC Implementation



Go Live, and Post Live Support Implementation Plans.

Hardware and Software Design



Kiva Pod and Bot Designs



Inventory Replenishment Use Cases



Customer Order Fulfillment Use Cases



Iteration Requirements Workshops



WMS
-
MHS Software Architecture



Kiva Hardware Architecture



Updated Project Plan



Updated Risk Analysis



Preliminary Test Plan



Preliminary GLOCO Warehouse Integration Training Plan



Preliminary HUES


䭉噁 卵灰潲琠偬an


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
30

Hardware and Software Installation



Installed KIVA Hardware Components



Installed MHS Software Components



Integration of Kiva hardware and WMS
-
MHS Software



Extended
Test Plan



Extended Training Plan



Extended Support Plan

System and Interface Testing



MHS Software and KIVA Hardware Test Results & Test
Results Modifications



Updated Project Plan



Identified Constraints, Bottlenecks and Risks impacting
final training and
Go Live.

Training and POC Go live



System Training Manual



Personnel Training Result Report



KIVA Support Manual



Operations Training w/Service Management Concepts



Helpdesk Training



Incident & Problem Management Training.

Project Deployment

The GLOCO
Warehouse Integration Project will be a flash cut of GLOCO’s Medical Supply Order Fulfil
lment and
Inventory Replenishment product lines from a manual input process to an automated process using Amazon
services and XML documents.
A flash cut date and time

will be defined to cease all manual procedures for order
fulfillment and inventory replenishment and cut over to the new automated procedures. Unfinished orders will be
bulk loaded into Amazon S3 services for automated order fulfillment and inventory repl
enishment.
A coinciding
Green
-
Field

installation of Kiva Hardware will
take place in one

of GLOC
O’s 100,000 square foot facilities
. The
major migration steps for the project deployment are as follows.

Software
Design

This phase will involve designing an

XML formatted “Customer Order Fulfillment Document” and a
n

“Inventory
Replenishment Purchase Order Document” that map to GLOCO’s ERP Database fields. The following tasks will be
required to successfully complete this phase:

Table 3.2 Software Design Task
s

Task

Dependency


Mapping of ERP Database fields to MHS Databases


None.

Map ERP database fields to XML Order Document

|
Map
ERP database fields to XML Inventory Document


Depends on the initial
Mapping of ERP Database fields
to MHS Databases

ERP
Scripts Designed to reflect Database Mappings

Depends on all database and XML mappings to be
complete.

Customer Web Portal Code Updated To Output XML


Depends on all database and XML mappings to be
complete.

Sales Web Portal Code Updated to Output XML


Depends on all database and XML mappings to be
complete.

Update Screen Interfaces for Medical Line


This task depends on previous recorded and approved
interface requirements.

Order Lines Picked and Inventory Replenish reports

Depends on all database and

XML mappings to be
complete. In addition, this task depends on previous

HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
31

recorded and approved reporting requirements.


Business Process Redesign

Many of GLOCO’s manual business processes will be replaced by automated hardware or software components of
the project.
During the POC phase the manual business processes
below
will be flash cut to the automated process.
Below is a mapping of GLOCO’s manu
al
to automated processes for this project.

Table 3.3 GLOCO Business Processes

GLOCO Business Processes

Manual Process

Automated Process


Customer Order Entry

Customer Order Entry Web Portal

Sales Order Entry

Sales Order Entry Web Portal (Medical
Devices Only)

Inventory Replenishment Database Stock Received

Automated Inventory Database Update Upon Scanning

Customer Order Items Shipped Database Updates

Automated Items Shipped Database Updates

Customer Order Pick and Pack

Robotic Goods To Person
and Pack

Sales Order databases u
pdated with Customer Order data

Customer Order Data will update from the MHS to the
ERP Sales Order Database automatically.

Purchase Order databases updated with vendor received
data

Purchase order received data will
update from the MHS
to the ERP Purchase Order database automatically

Calculation of and Reporting on order lines picked

Automated order lines picked report

Operational Governance

This section describes operational governance for the project.
This

section:



Identifies needed resources.



Describes how stakeholders will stay involved.



Describes plans for handling change, communication, and risk during the project.

Resources

The main resources required
to complete

this project are
staff from GLOCO, team

members from Kiva and
HUES
Enterprise Consultants
.

GLOCO

Executive sponsorship and oversight is a key element for the success of the project, their support and
management increases the probability of success and enables better management of risks.

HUES will recommend to GLOCO a full project governance model
which

includes and executive and steering
committee; the table below describes de roles included in the committees.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
32

Table 3.4 Project Team

Project Governance Roles

Role

Description


GLOCO
Executive Sponsor

This person provides final approval for major project
changes such as the Implementation Time Line and the
overall project budget. In addition, the Executive
Sponsor approves any exceptions that are escalated by
the GLOCO Steering Committ
ee.

GLOCO Steering Committee (Business Representative)

This role ensures that the project is directly aligned
with GLOCO’s business drivers, requirements, and
潵瑣潭os. 䥮 a摤楴楯n 瑨楳 role 楳⁴ie l楡楳潮 bet睥en
瑨t 却Ser楮g C潭浩瑴ee, tec桮楣hl re灲e
sen瑡瑩tes an搠
瑨t GL佃传Exec畴楶e s灯nsor⸠

GL佃传却eerin朠Co浭楴瑥e (呥c桮楣hl Represen瑡瑩癥)

周楳⁲潬e ensure 瑨t琠瑨e tec桮楣ha s潬畴楯u 楳 al楧ie搠瑯
GLOCO’s business drivers, requirements, and
潵瑣潭os. In a摤楴楯nⰠ瑨楳 r潬e 楳 瑨t l楡楳潮i瑯t
瑨e
e硴en摥d tec桮楣hl 浥浢ers 潦o瑨e 灲o橥ct 瑥am.

Exception Resolution Flow

The flow of the exception resolution, decision
-
making and dispute resolution will be primarily governed by the
steering committee. If an exception arises from within the extended team this exception is submitted to the steering
committee for evaluation and

resolution. If the exception is related to a technical topic then the technical
representative is responsible for resolving the exception and the business representative will be responsible for
resolving the business related exceptions.

If the exception

cannot be resolved within the steering committee, it will be escalated to the executive sponsor,
which will provide the final decision.

GLOCO, HUES Enterprise Consultants and Kiva Project Team

The table below provides a listing of the key individuals need
ed to complete the project. Each position shows a basic
area of responsibility.

Table 3.5 Project Team

GLOCO, HUES Enterprise and Kiva Project Team

Role

Responsibility


HUES Enterprise Consultants Project
Manager


Works with Stakeholders and Product
development team in
understanding business needs and transforming into technical details
with better project timelines.

GLOCO
Software Engineer

Develop and maintain the software systems satisfying all the
requirements that have been defined.

GLOCO
Software Architect


Establishes the basic structure of the computer system, defining the
essential core design features and elements

ensuring that the new
system components integrate with the existing software pieces
.

GLOCO
Database Engineer

Defines the t
ables, indexes, views, constraints, triggers, stored
procedures, storage parameters, and other entities needed to store,
retrieve, and delete persistent objects from the databases used in the
project.



HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
33

GLOCO Hardware

Architect

Establishes the basic struct
ure of the computer system, defining the
essential core design features and elements.

GLOCO
System Administrator

Maintain and operate a computer system and/or network.

GLOCO
Hardware Engineer

Assemble and maintain the hardware systems satisfying all the
requirements that have been defined.

HUES
Implementation Lead

Oversees and directs the deployment of the new products, services and
components for the project.

HUES
Business Analyst

Analyzes the existing environment and design of systems, including
businesses, departments, and organizations assessing new business
models and their integration with new project technology.

GLOCO
QA Manager

Provides end user support and dispatches tickets to service
technicians.

GLOCO
Technical Support

Responsible for
top
-
tier customer and technical support to clients
working remotely using email, phone, chat and videoconferencing to
resolve issues.

HUES
Technical Clerk

Organize and maintain project requirements as well as security and
training records. Scheduling and
producing progress reports and
reviewing technical documentation.

Kiva Implementation Manager

Managing onsite client relationships from implementation through
formal customer acceptance of system

Kiva Architect

Ensures that the

basic structure of the computer system, defining the
essential core design features and elements

meet the Kiva
implementation standards
.

Kiva Trainer

Provides training on the Kiva product components to key personnel.

GLOCO
Web Designer

Produce and
maintain all new Web pages and portals associated with
the project.

GLOCO
Software QA Engineer

Monitoring the software engineering processes and methods used to
ensure quality.

GLOCO
Documentation Writer

Develops all project documentation.

GLOCO
Informa
tion Security Engineer

Focuses on the security aspects in the design of all systems.


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
34


Figure 1
3: Project Team





HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
35

GLOCO Stakeholders


As GLOCO implements the Kiva system there will be a considerable number of people within the
organization that
will be
effected
. To a degree all of them will be stakeholders however, there will be several key individuals that will play a
critical role in making sure that the system is deployed and running smoothly.

Table 3.6 GLOCO Stakeholders

Group

Key Personnel

Activit
ies




GLOCO Executive Team

CEO, COO, CFO, CIO

Aligns the project with company strategy and goals.

GLOCO System

System Architect

System Administrator

Hardware Engineer

System Analyst

Works with Kiva and Hues to ensure development and
implementation of
all requirements.

Helps to design and deliver the final

solution
.

GLOCO Technical

Software Engineer

Database Engineer

Provide project management support to deliver projects
within the established budget and time line.

Develop
and maintain the software
systems satisfying all the
requirements that have been defined.

Suggests course
corrections as needed.

GLOCO Training

Technical Support

QA Manager

Provides the end
-
user stakeholder training needed to
run the new fulfillment system from every involved
depa
rtment.

GLOCO Development

Designer

Software QA Engineer

Documentation Lead

Information Security
Engineer

Provides the final deliverables for all stakeholders to
consider from the top down. Effects changes as needed
to accommodate any new developments or
obstacles.

Hues Project
Management

Project Manager

Project Specialist

Follows communication plan
.

Follows risk management plan
.

Monitors health of project
.

Reports to supervisory stakeholders
.

Holds no direct responsibility for
the
project
.

Hues
Implementation

Requirements Analyst

Business Analyst

Technical Clerk

Generates project documents

and ensures that the
project follows the previously identified goals from the
major stakeholders.

Kiva

Implementation Manager

Trainer

Ensures that the impleme
ntation follows the prescribed
process for all integration and work necessary to
complete the project and hand it off.

Warehouse End Users

Warehouse fulfillment
workers, Warehouse
replenishment workers

The end users of the systems and hardware that is to
be
implemented. These workers will provide feedback on
the new systems and how they are functioning
providing possible recommendations on issues that may
need to be addressed.




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
36

The

chart below depicts the various stakeholders within the project team. Special note should be made regarding
the HUES implementation team and the Kiva team shown in orange, both of which will be serving as consultants
throughout the project but will have
no involvement once the implementation is complete. The team has varying
degrees of involvement from the top, which will have the least amount of hands on responsibilities, to the bottom,
where individuals will be working very closely with different eleme
nts of the project. However, regardless of the
position within the chart all of the stakeholders have a vested interest in seeing the implementation through to a
successful end.

Figure 1
4 Stakeholders




HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
37


Communications Dashboard

During the length of the
project one of the primary mediums of communication will be the GLOCO Warehouse
Integration Dashboard. This dashboard will be updated on a weekly basis and will serve as a key project tracking
mechanism. The dashboard will contain overall red, amber, green

(RAG) status in addition to a Gantt chart, Ongoing
Activities, High Level Milestone Chart, Risk Log and an Issue Tracker.


Go Live and Post Go Live Communications Plan


As part of the POC Training and Go Live phase,

an Operations training/workshop will be provided to identify
appropriate incident and problem management procedures. As an output of this phase, a Helpdesk Training and
Escalation Procedures Document will be defined. To mitigate risk, all procedures wi
ll be based on service
management concepts (ITSM) with the expectation that the Go Live personnel will follow these documented
procedures.

For the Go
-
live and Post Go
-
Live phases the project will implement a process to resolve issues and any kind of
change

that could be needed in a timely manner, delivering quick resolutions. The strategy is developed focused on
end users and enabling them to access the correct information and assistance to complete the tasks related to their
jobs.

F
igure 1
5: Communications Dashboard


HUES Enterprise Consultants

Warehouse Integration
Proposal




©

2013

GLOCO


Confidential and Proprietary


Page |
38


In the early instances
of Go
-
Live defined as the first 3 weeks, the project team will offer On
-
site assistance to key
areas in the implementation; those areas are: GLOCO Data center operations, GLOCO Service Center including