June 5, 2014. Agenda Welcome Introductions NMTIE Event Recap Discussion on Consortium Group...

Preview:

Citation preview

June 5, 2014

Agenda• Welcome Introductions• NMTIE Event Recap• Discussion on Consortium Group Structure

o Leadership Groupo Technical Architectureo Trainingo Contracts & RFPo Security

• NM Banner XE Roadmap/Timeline2

Welcome Introductions• NMSU

o Pamela Jeffries, Sr. Director, Enterprise Application Serviceso Pankaj Sharma, ICT Project Management Office o Alejandro Garcia, ICT Project Management Officeo Grace La Torra, ICT Project Management Office

• CNMo Joe Gieri, Office of IT Services Executive Director o Ray Avila, Enterprise Application Director

• UNMo Duane Arruti, IT Applications Directoro Paige Briggs, IT Applications Manager

3

NMTIE Event RecapInaugural Banner Track effort at NMTIE

• Best Practices for Implementing Banner XE (Alan Hansen, VP of Product Enhancement at Ellucian)

• Lessons Learned from a Beta Partner (TTU)• Planning and Preparation (NMSU, UNM)• Chartering a NM Banner Consortium (Round Table)• Existing Collaborative Groups• Benefits/Concerns of a Consortium• Proposed Structures/Subcommittees

4

Existing Collaborative Groups

• CHECS• NM Independent Community College• NM Financial Aid group • Registrars NM Registrars Group• NM IT Exchange (smaller version of Banner Consortium)• NM Oracle Users Group• Security Group

5

Benefits/Concerns of a Consortium

Benefits:• Training• Standardization• Cost Benefits• Sharing• Idea & Collaboration• Best practices• No duplications of effort• Common reporting - HED• Simplify state data• 3rd Party Integration &

inventory/version/contact/issues

• Leverage buying power

6

Concerns:• More meetings• Consensus• Fizzle with no bang• Different priorities and timelines• All our eggs in one basket• Need more users in the consortium to balance technical• Funding considerations• Legislators• Focus

Brainstorming on Subcommittees

7

• Leadership Committee to cover structure and communication• Technical Architecture Group• Module specific with Tech and Users• Training Group• Contracts/RFP Group reviewing agreements• CHECS? (What are they currently doing)• Reporting/Data Management • Ellucian Code Repository• Community/Outreach• Security • Compliance• Leveraging shared infrastructure/Service Center Model• Common Infrastructure Group• Common App Development Group• DBA

Discussion on Consortium Group Structure

o The purpose of each group is o To be a forum for exchange of ideas,o To identify common problems, ando To collaborate on scalable common solutions

8

Discussion on Consortium Group Structure

o Leadershipo Provide strategic guidance to the consortium

o Technical Architectureo Identify opportunities for standardizing technical

architecture across the state and propose recommended scalable technical architecture(s)

o Trainingo Identify common training needs and propose a

recommended training curriculum for consortium members

9

o Contracts & RFPo Identify opportunities for collective

bargaining with vendorso Securityo Identify common security needs and

recommend a scalable security framework

10

Discussion on Consortium Group Structure

Discussion on Consortium Group Structure

o Discussion pointso Process for constituting the groups

o Open enrollment or through nomination by respective institutions?

o How do we appropriately balance representation?

o Chartering the groupso What is the charge of each group?

11

NM Banner XE Roadmap/Timeline

12

13

14

15

Closing and Next Steps

16

Recommended