NEIT16+Open+Space+1C+-+Lake+(off+Laurel)

SIS Discussion

Jim Anderson Pascal Vallet Jonathan King Nick Anastos Dan Corcoran Bernie McComick David Lang Jennifer Davenport and a few others - sorry I couldn’t see your name tags.

Data systems complex and varied and takes a lot fo support them and the arrival of data is delayed. Inefficient.

Start the process of evaluating an SIS. Typically need 3 days of sales meetings per vendor.

Bring in agnostic consultant to evaluate systems and process. Compile rubric to hand to sales people to condense the sales period to 1 day to minimize the meetings.

Good Process Documentation (process model) - this changes - and has life beyond the technology. Data Model - standardizes vocabulary - this does not change.

Both have things that sit by themselves.

If you can’t get your data out of a product, do not put your data into it - Dan Corcoran

Using an outside consultant takes tension out of the meeting and they inherently know more than you.

This is built to shorten the sales cycle.

Rubric can be thrown away when the biggest stakeholders put their feet down.

What do we want vs what we should do?

Map all processes in the school. Identify where it doesn’t work well. Identify assets.

Senior leadership will listen to a consultant more so than they will listen to IT or other internal evaluators.

Administrative audit - who goes where and who does what - too many administrators Have a process audit - ideally by 3rd party consultants

Have glue built off a standardized platform.

Salesforce as a platform? Veracross? mentioned as targets

People fighting change the most are the people who don’t want to sit in a room and talk about what they do. - Bernie

How do you determine the stakeholders? They are the department.

Who owns the person? Politics of the data. Who owns the data?

Most of these problems have nothing to do with technology - not systems talking - its departments talking.

Find some pretty things to put in the dirt when making major changes to keep the squeaky wheel happy.

Top down buy in is essential.

How much of you IT budget supports education directly?

Project is not done until documentation is handed off. Documentation must be updated.

You're not buying a software package - you are buying a community.

Is the ROI better hiring staff (programmer) or better in a canned system and propper documentation.