Progress Report on Folio Development


As we begin preparing for agency A-11 submissions in the fall, we wanted to highlight some improvements we’ve made to Folio over the past nine months. Since October 2017, we have completed 12 development sprints dedicated primarily towards Folio. We have achieved a great deal of success in implementing the functionality that our users need, so let us tell you about what that functionality includes:

Investment and Project Components

We’ve created the component constructs for our two primary data collection structures in Folio – Investments and Projects. These components can capture unique data about individual investment or project records, and then align projects to the appropriate investment record. The ability to align distinct components together is a key aspect of our data architecture.

Data Collections

The data our users manage is complex, and they need the ability to capture multiple, complex data records within a single investment or project. To achieve this, we’ve implemented a construct we call Collections. Collections use templates (instead of a large data grid) to capture data and embed it into an investment or project. We think this approach will make it easier to enter data, and streamline data review and management.

Project Activities Table

We applied the same Collections construct to tackle the challenge of tracking project activities in a hierarchical structure. Using the collections architecture on the backend, we leverage a unique user interface to interact with activity data directly in Folio. This will enable Folio to be more easily adapt to changing requirements in the future.

Basic User Access

Agencies need to know that their data is secure, and visible only to the people who need access. We have begun to tackle this issue by implementing basic user access functions, including User permissions, Templates, and Views.


We’ve implemented the architecture for Folio’s site navigation, from data collection, to OMB submissions, to reporting. We also have template navigation within component records, to help users access the section and subsection data within an investment or project record.

So, What’s Next?

We’ve accomplished a lot these past months, but we’re not relaxing! While our development team focuses on legacy eCPIC over the summer to get the application ready for agency IT budget submissions, our Folio requirements and design teams will continue gathering and prioritizing requirements, and developing wireframes and mockups to test with stakeholders. Then we’ll be in a great position to pivot back to Folio development when the next OMB submission period is complete.

This image depicts the Folio Requirements Development Process.

This image depicts the Folio Requirements Development Process.


We will begin showing the live site to our FESCOM Tiger Team meetings over the summer, and we’d love your input! Join us to preview Folio and provide us with valuable feedback on how we can make Folio work better for you.