Welcome to the Kepion Training Video Series. In this series, we'll walk-through the steps to build a sample Revenue Planning Application together. We'll also explore all of the key components and concepts within Kepion. If you've never used Kepion before, this is the best place to begin.
Welcome to the Kepion Training Video Series. In this series, we’ll outline the main features of Kepion as we walk through the steps of building a sample Revenue Planning Application together. We’ll explain how to translate customer requirements from spreadsheets, to an architecture document, to a fully-realized Kepion application. At each step, we’ll provide resources to help you follow along.
In addition, if you have any questions about features that aren’t covered in this series, our Support Center is the number one resource to learn best practices and troubleshoot issues. If your question isn’t answered in the support center, you can always submit a new ticket.
Here’s an example of the kind of application that can be built in Kepion. For our purposes, let’s scope this Application down to its essential components as we learn to work in Kepion. By the time you finish this video series however, you should have all the skills necessary to build any level of Application.
Let’s begin by taking a closer look at the one we’ll be building. This is a simplified Revenue Planning Application. On the first page we have a Profit and Loss report that summarizes our planning operation. At the top, we have a series of filters that can slice and dice our data into different contexts. I can flip from our US operation to our Canadian operation, or view all of North America at the same time.
On the other three pages I have a series of Input Forms that drive the data in the Report. I can update any of the data here and then see exactly how it affects the entire planning process.
Before we can start building this directly in Kepion, we first need to plan out the design and architecture of the entire Application. In the first session of this Tutorial Series, we’ll do just that, by taking a look at how to translate customer requirements into an Architecture Document formatted for Kepion.
Table of Contents
Part I - Architecture Design
- Session 1 - Identifying Forms
- Session 2 - Identifying Dimensions
- Session 3 - Identifying Models, Rules, and Apps
Part II - Dimensions, Models, and Forms
- Session 4 - Building Dimensions
- Session 5 - Building Models
- Session 6 - Building Reports
- Session 7 - Building Input Forms
Part III - Dashboards and Data
- Session 8 - Building Dashboards
- Session 9 - Building Dashboard Apps
- Session 10 - Managing Data and Partitions
Part IV - Rules
- Session 11 - Building Data Rules
- Session 12 - Calculating Revenue and COGS
- Session 13 - Calculating On-Sale Discounts
- Session 14 - Calculating Gross Margin %
Part V - Security and Workflow