Hot-housing, not warehousing

Packola is about getting the most out of each piece of data. We ruthlessly reduce the number of figures, so that each one works hard for its place in the system. Sometimes we call this One Core Truth.

Or we contrast it with the Data Warehouse approach. Where that is about bulk and comprehensiveness, Packola is about indivisible precision. Sweat the data. Hothouse it.

Grid Grouping

Before:

After:


When a grid exists as multiple boards, say one per year of account, Packola's Grid Grouping concept lets the user switch between looking at one and looking at all together. The instructions for grouping are subtle, but the screens above show a typical scenario. A title line is copied, here just the currencies, followed by a line from each board in turn, then a total. This is repeated for a selection of the lines on the boards.

Anatomy of a Packola Screen


Here is a typical, though fictional, screen shot from Packola.

We're looking at a board called Fees Analysis / All - you can see that title in the tabs just above the grid of data. We also have open the Trial Balance grid for years 2006, 2007 and 2010.

Cell L13 has just been clicked on, and shows as white on dark blue. It's a formula cell, so the formula is shown just above the grid, and the cells it uses are shown with heavy borders : C13, D13 and E13. The formula uses the WSGBPA method to do a GBP conversion at Average rates.

Cell colours are used to distinguish different types of cell. F3 is an entered figure. G3 is an entered figure that has not yet been set. C6 is a formula. J8 is a carry forward figure. A6 is a logic cell. C11 is a precedent figure copied from another board. C3 is a group precedent, summing a value across multiple boards.

F3 also has a comment attached, as shown by the red marker.

Database Diagram


Structural Data controls the design of the grids
Exercise has a row for each month which most other data hangs off
MicroGrid has a row per designed grid
MGCell has a row per cell in a MicroGrid
Scope defines which instantiations of a grid might exist - per year, per currency etc
Deck links MicroGrid and Scope, and sets which grids are instantiated as Boards
DiffScope sets the navigation between Boards of different Scopes
Appearance sets the display format for a cell - with commas, decimal places etc
GridGroupCommand controls the way a set of Boards are grouped for display

Primary Monthly Data covers the values we expect users to change
Datum holds entered values, including a dated history of each
Adjustment holds adjustments, overrides and comments against squares
ExchangeRate holds the exchange rates, and is universal, not per exercise

Secondary Monthly Data covers values which may change should an exercise differ from the previous month
WorkFlow and WorkStep guide the user through the monthly process
SpecialCase and SpecialUsage provide a mechanism for values that affect multiple squares
ExportParameter holds the information for uploading a square's value as a journal into the Accounting System
FetchInstruction has the knowledge of Excel worksheet cells that can be uploaded into Packola

System Data covers standard elements
Operator has a row for each user authorised to access the system
Session has a row for each occasion a user logged on
Preference controls certain system-wide values

Later Additions
COASubset, COACode and COADatum cover the chart of accounts treatment added October 2010

Making the Easy Things Trivial

Packola's goal is to make the easy things trivial. Then your attention can focus on what's important.

As much as possible, we make Packola fetch data automatically and safely. Then we give you clear places to put amendments. That leaves you to worry about the significant issues in your figures.

Workflows

A workflow can remind you what you're meant to do next, help you do that task, and let you show that you've done it.

In Packola we've a screen which shows a flow through any number of related steps. You can load the relevant board just by right-clicking on the step. Simple but effective.

It's all about streamlining

Packola is all about streamlining the process. We identify the important outputs. Then we work back to the inputs that are required and automate them. In a perfect world, that's it: one streamlined reporting cycle.

We've never done one like that. In the real world there are inputs which can't be automated, discretionary options which need to be allowed. But we still only do what needs to be done, pruning away figures that used to interest someone but are now just a distraction. Like a Formula One car, the end result has a shape which is not 100% sleek, but is as streamlined as it possibly can be.