The relatively open architecture of PPS allows for nice flexibility in approaching solutions. While the open nature does make things more complex at first, it allows for "thinking outside" the box a bit.
For instance, the preface of the Planning component is built aroud your basic Planning, Budgeting and Forecasting (PBF) framework, typically seen in most medium to large sized corporate finance departments. While the basic framework is built around this, it is certainly not limited to it.
Currently, I'm developing and testing an application to collect, plan and analyze daily workout routines. The PPS Planning component and Excel are utilized to collect daily weight lifting routines based on low level inputs and then summarize the data at a meaningful analytical level. From here, the monitoring and analytics components provide reporting at time driven levels and any other dimensional breakout one would find beneficial in analyzing a fitness routine.
Therefore, staring with the Planning component, I'm able to build a full "operations" based application that has nothing to do with finance, but serves as a full blown data collection and scorecard and dashboard solution for operations.