eFECS Teams

The project's success depends on volunteer teams whose efforts encompass everything from high-level process change recommendations, to requirements gathering and use case documentation, to technical collaboration and system design.

Organizational Chart (.ppt)

Meet the Teams:

Business Advisory Group (BAG) - The BAG provides knowledge of institutional priorities and lends top down support to the project. The group meets monthly and provides input and perspective on major decisions and issues that arise. The group helps to facilitate cooperation across organizational lines and works to remove barriers to communication, cooperation and change.

Financial Business Advisory Group (FBAG)

Process Improvement Team (PIT) - The PIT is charged with the day-to-day leadership of the project, identifying the project scope and ensuring that end-user involvement drives each stage of product development. PIT members are familiar with the business requirements of the project, and take a global view in representing campus as they develop a phasing strategy and prioritize deliverables. The team meets two or more times a month as needed, and along with UTG members, they assist the project staff with outreach activities such as training and communication strategies.

USER Task Group (UTG) - USER Task Groups are volunteers who represent a broad range of end-users, with first hand knowledge of the process to be improved. This team meets weekly and works with Application Developers to define requirements and determine the look and feel of software products.

PI Advisory Team - Composed of a cross-section of Principal Investigators Representing a broad constituent base, this team meets quarterly to provide input and direction to the project team. They help to establish buy-in, support, and participation during all phases of the project.

Technical Architecture Teams (3)- These teams were formed to initiate collaboration among SAGE, eFECS and FDI developers in the design and creation of the eFECS database and related schemas. The teams will also make decisions regarding the storage of the data and long-term system maintenance.

Core Team - meets weekly, responsible for the group's deliverables.
Consulting team - members attend meetings on an ad-hoc, topic-dependant basis to provide input regarding specific functional areas.
Advisory team -Meets quarterly to ensure successful collaboration among SAGE, eFECS, FDI, and other related teams. The team provides advisory review of eFECS Foundation database plans and related schemas. This team also clarifies which decisions the Architecture group is empowered to make and which decisions require additional sign off. If sign off is needed, they specify the decision-makers

Transition Team - The cost share components currently housed within the University's BGT mainframe system will be migrated to the new eFECS Foundation database. This small team composed of cost share, effort reporting and BGT system subject matter experts will, along with other stakeholders, make recommendations regarding the new platform and data migration. The team will meet bi-weekly on a short term basis.