
See also the SIS Project Management Team Chart for details.
Project Sponsors: Chief Executive Officer and Chief Academic Officer.
Project Manager: Responsible for the day-to-day management of the SIS implementation project. Has the authority to make decisions that will keep the project moving, and is responsible for managing the project plan, communicating with senior management, and managing the tasks and resources for plan tasks.
Associate Project Managers: Assist the Project Manager in overall management of the implementation project. Serve as project liaisons to faculty, department chairs, Deans, administrative unit heads, and IT staff.
Project Executive Committee: Empowered to make decisions on policy, strategy, and budget matters. Will review issues forwarded from Project Manager and/or Project Steering Committee and make final decisions.
Project Steering Committee: Membership includes representation from each department lending resources to the project, plus representatives from the governance groups. They will meet regularly to discuss issues, review progress, and provide resources. Responsible for communicating to unit staff and colleagues about the project and its potential impact on normal or expected activities, and the time it will take to complete them.
Cross Functional Team: Members work in or manage the functional areas that are implementing PeopleSoft. Members have good working knowledge of current systems and sub-systems. Assist with data mapping, data conversion, testing, and building and reviewing prototypes. Also participate in defining test data and creating test scripts. Membership includes DBA and IT analyst/programmers.
Database Administrator (DBA): The universitys database platform expert. Responsible for managing data and data definitions stored in the system, including standards such as naming conventions, and knowing how and why the data is necessary to determine the number of indexes and keys required for acceptable performance. Also responsible for change control over the objects in the system--when and why modifications are made and how to migrate the changes in and out of different environments.
Security Administrator: Manages the access and authorization to the system--designating the access different operators and operator classes have to different functions in the system. Involved in defining and maintaining security trees, and manages security profiles for a variety of processes and query tools.
System Administrator: IT technical team member responsible for the management and support of the system. Familiar with all components that make up the client/server environment, including development, connectivity issues, migration approaches, and hardware/software compatibility.
Network Specialists: IT staff familiar with the connectivity from the client workstations to the database management system, wherever and however theyre connected. Knowledgeable about the protocol, wiring, and layering of software, and the path the software takes to access the database management system from all client workstation locations to the database engine.
Questions/comments? Email berens@uwosh.edu
Return
to Information Technology
Return
to UW Oshkosh