About the Cyberinfrastructure (CI) Council
Formed in 2013, MU’s CI Council is composed of faculty and professional IT staff from all of MU’s schools and colleges. They meet monthly and welcome others to join them. The meetings often explore the research and CI needs of a particular lab or project. If you would like to participate, please contact the CI Council member in your school or college or Timothy Middelkoop via email: firstname.lastname@example.org.
CI Council Members List
MU’s CI Council is generally organized along school/college organizational structure. This allows each researcher to have an easily identifiable contact who serves as her/his representative. View the members list.
Responsibilities of the CI Council
- Understand the demands for CI resources, and recommend priorities for purchase; or if feasible, enable access through a local, regional, or national source.
- Provide leadership in properly securing research data.
- Help ensure campus leaders are informed of the needs for CI and how other universities are meeting those needs; in particular, the needs for human resources, not just hardware and software.
- Ensure MU has a defined CI architecture to explicitly determine what will (and will not be) supported.
- Establish, refine, and communicate a business model that will provide the sustainable funding necessary for CI resources, likely some level of generally available no-charge resources and a higher level of for-fee services.
- Facilitate communications, seeking input on research CI needs and priorities, and share CI Council information in MU’s schools and colleges.
- Oversee the allocation and use of high-performance computing and disk storage designated for special projects.
- Demonstrate best practices and help facilitate and inspire effective collaborations.
- Review progress toward MU’s CI Plan and refine the plan as demand and situations dictate.
CI Council Meeting Schedule
|January 11||3:00 – 4:30 p.m.||E205A & B, Locust Street Building|
|February 15||3:30 – 5:00 p.m.||E304, Locust Street Building|
|March 21||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|April 18||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|May 16||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|June 20||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|July 18||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|August 15||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|September 19||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|October 17||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|November 21||3:30 – 5:00 p.m.||E205A & B, Locust Street Building|
|December 19||3:30 – 5:00 p.m.||EE205A & B, Locust Street Building|
MU CI Plan
Read the current CI Plan and the CI Council’s Focus Area Planning Update, both adopted March 21, 2016.
CI Day is an annual event that fosters collaboration, networking, and collective problem solving. Attendees learn more about advanced computing technologies across a wide range of disciplines. Learn more about this year’s event, to be held on April 13, 2016. View related documents on MOSpace.
CI Resources at MU
About Research Computing at MU
The Division of IT’s Research Computing Support Services (RCSS) group, directed by Dr. Timothy Middelkoop, provides research computing services and support for the campus. These services include a newly upgraded High Performance Computing cluster that we are continuing to expand, a new General Purpose Research Storage (GPRS) system with more than one Petabyte of research data storage, a 100-Gigabit AL2S connection to Internet2 that can provide direct high-speed connections to peer institutions, and a dedicated science DMZ that allows unrestricted access to Internet2. There are a number of grant-friendly investment services to allow researchers to obtain the capacity that a project requires without having the cost or complexity of managing these systems. If you have questions about research computing, including how you can strengthen your research funding proposals, please contact Timothy Middelkoop via email: email@example.com.