Overview
The FOLIO project aims to facilitate a sustainable, community-driven collaboration around the creation of a modern technology ecosystem that empowers libraries through open-source applications to manage library resources and expand library value. At the heart of FOLIO is an open source, cloud-ready application framework that is designed to support collaboration among development teams. It is also designed to enable vendors, libraries, tenants, and users to configure their experience to an unprecedented level. We see FOLIO as an “innovation platform” in which librarians and software developers can work together to imagine and create new kinds of library services.

The goal of the CUL FOLIO Steering Committee is to ensure that CUL’s FOLIO implementation serves CUL’s business needs in a sustainable way. This will be achieved
through:

• Enhancing horizontal and vertical coordination;
• Coordinating systematic change;
• Promoting standard business rules; and
• Documenting and promoting shared understanding.

Steering Committee Charge
The CUL FOLIO Steering Committee is charged by the Library Executive Group (LEG).

The Steering Committee will provide oversight for the management and evolution of CUL’s FOLIO implementation, with the goals of:

1. Management
   1. Vet and approve proposed Settings and Policy changes
   2. Ensure continuity across CUL for FOLIO apps that cross multiple departments (ex: Notes, Tags, custom fields); mediate across various functional needs
   3. Manage technical debt 
   4. Ensure the development of documentation of procedures, policies, and requirements 
   5. Charge the sub committees for Support and Security under the oversight of the FOLIO Application Manager 
2. Change Management
   1. Facilitate significant enhancement requests 
   2. Ensure that CUL does not undertake local development that deviates from the FOLIO core code. 
   3. Provide oversight and guidance of FOLIO integrations 
   4. Determine if and when we implement new FOLIO applications
      1. Evaluate new features from the FOLIO development community and recommend/plan for adoption
      2. Follow release notes for significant changes and assess the impact to CUL

The Steering Committee:
The Committee must include representation from across CUL and meet at least bi-monthly.
The FOLIO Steering Committee should be led by a convener. This convener will also:

• Coordinate with CUL’s hosting provider (EBSCO)
• Provide vendor and contract management
• Coordinate scheduled downtime
• Monitor FOLIO development for new features for committee consideration
• Follow release notes for significant changes and assess the impact to CUL
• Coordinate with subject matter experts (SMEs) within CUL to manage the ongoing implementation of FOLIO within CUL

In addition to the convener (Debra Howell), Committee membership must include the following representation:

• 1 – FOLIO Application Manager: Thomas Trutt
• 1 - Access & Public Services: Andy Horbal
• 1 - Information Technology: Debra Howell/Thomas Trutt
• 1 - Technical Services: Laura Daniels
• 1 - Finance: Ann Crowley
• 1 - Special Collections: TBD
• 1 - Assessment / Reporting: Vandana Shah
• FOLIO Product Council Representative if CUL is represented on the Product Council: Jesse Koennecke
• FOLIO Community Council Representative if CUL is represented on the Community Council: Simeon Warner
• FOLIO Community Technical Council Representative if CUL is represented on the Technical Council: Jenn Colt

The Steering Committee is proposed as a standing committee, and as such, the work will be iterative and ongoing, and the processes and procedures developed by the Committee should document and reflect a continuous improvement approach.

Each committee member is responsible for:

• Representing the interests of their department and similar departments when making decisions and recommendations;
• Assisting in implementing standards and new business processes relevant to their departments;
• Facilitating communication between the committee and the subject matter experts; and
• Designating a proxy in the event of an absence