kinaxis - rapidresponse: how is it so fast?
DESCRIPTION
Here's a presentation by Ravi Puvan, senior product manager, Kinaxis, on how RapidResponse is so fast compared to other supply chain software on the market. To view the full technical whitepaper, visit: http://www.kinaxis.com/downloads/pdf/Kinaxis-TechWP-RR-Fast.pdfTRANSCRIPT
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 1
Copyright © 2011 Kinaxis Inc. All Rights Reserved.
By Ravi Puvan, senior product manager, Kinaxis
RapidResponse: How is it so fast?
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 3
RapidResponse: How is it so fast?
• Kinaxis has built specialized supply chain software expertise and experience over many years.
• RapidResponse is unrivaled in speed and performance breakthroughs.
• This PPT will show the technology architecture and analytic capabilities of RapidResponse.
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 4
Technology Architecture
• RapidResponse uses an in-memory database.– Relies on main memory for computer data storage. – Employs patented technology to store multiple versions of
data using only incremental changes (deltas) in input date.– Provides access to numerous scenarios without incurring
large storage costs.RapidResponse
Scenario B
Scenario ABase Scenario
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 5
Technology Architecture
• Competitive systems store complete copies of each set of input data.
• However, the storage requirements to save complete copies of each dataset (or version) can be very large, as shown below.
Other Database
Base Scenario Scenario A Scenario B
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 6
Database Design
• Dealing with complex data relationships like the Bill of Materials (BOM), the database design employed by RapidResponse provides a significant performance advantage over other competing designs like relational and columnar databases.
Comparing Database Design
Relational Columnar RapidResponse
Search Speed w/ Few Columns
Search Speed w/ Many Columns
Efficient Data Storage
Performance with Complex Relationships e.g. BOM
Poor
Excellent
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 7
Relational Database
Pros:• Most common choice for data warehouse applications.• Data is organized in tables and allows for query flexibility. • There is a vast array of analytic and integration tools built
for relational databases. Cons: • Analytic-intensive applications are difficult to design,
challenging to maintain, and require designers to compromise between query performance and maximizing query flexibility.
• Performance breaks down when handling complex relationships like BOMs.
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 8
Columnar Database
Pros: • Stores content by column instead of row
– Can reduce the storage requirements where there is data duplication.
• Advanced search functions– Spans fewer columns of aggregated data
Cons:• Can’t handle complex relationships like BOMs.• Less efficient when many columns of a single row are
required at the same time.
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 9
RapidResponse Database
• RapidResponse uses direct memory references to quickly access the necessary data.
• Speed is significantly improved when accessing data.
Part
Set
Independent Demand
Part ABC
Demand 1 for Part ABC Ref
Ref
Ref
Ref
Demand 2 for Part ABC
Demand 3 for Part ABC
Demand 4 for Part ABC
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 10
RapidResponse Optimized Analytics
• Analytics code is directly compiled into the database engine. Has direct access to the memory data.– Less moving of data between database and analytics
improves performance.
• Analytic Modifiers – Introduces additional logic to be considered by core
analytics. – Can then modify calculations with additional logic.
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 11
RapidResponse Analytics Examples
• Capable-to-Promise– Uses patented method to calculate realistic order completion
dates. – Following calculations are performed by the CTP analytics:
• Supply demand allocation.• Available date.• Gating part.• Incremental availability.
• Multi-Sourcing– Allows a part to have more than one source of supply to satisfy
demand requirement. – Allows for allocation of different sources of supply based on factors
such as; target, priority, and contractual agreements.
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 12
RapidResponse Performance Tests
Copyright © 2011 Kinaxis Inc. All Rights Reserved. 13
RapidResponse Performance Tests
• Simple Query Speeds– Add up all the quantity fields on the scheduled receipts:
0.050 sec – Count number of scheduled receipts whose start date is
more than 90 “working days” before the due date: 0.065 sec– Produced report of parts sorted by site and name: 7.0 sec
• Complex Query Speed – Run complete netting (MRP calculation) and count the
number of planned order recommendations: 45 seconds!– Running the same calculation again: 5 seconds!
Copyright © 2011 Kinaxis Inc. All Rights Reserved.
You can download the full technical
whitepaper “RapidResponse: How is it so fast?” at:
www.kinaxis.com/go/technology-papers
Copyright © 2011 Kinaxis Inc. All Rights Reserved.
Thank you!