CMS Logo
Cornell University Logo

Steering Team Environmental Officials Environmental Representatives IT Team  

CMS IT Team

MISSION

VISION

  • Create a flexible IT system that is user-friendly, incorporating safety, health, and environmental programs into everyday decisions and practices of the Cornell community.
  • Create a web site that is the front door to anyone within the Cornell community, providing the CMS information and resources they need quickly and efficiently.
  • Implement standards for data storage and access in support of collaboration.
  • Establish an IT model for other college and university environmental management systems.

Planning and Development Phase Activities

What do we do?

  • Develop and maintain the CMS web site and implementation tools
  • Gather functional and technical requirements for potential CMS tools
  • Investigate software products for possible CMS use
  • Research EMS IT strategies of other institutions

For whom?

  • ECO, EH&S, and CMS clients, including CMS Steering Team, Working Group, and Pilot members, Environmental Officials, Environmental Representatives and other members of the university community

Why?

  • To ensure our clients have the information they need to manage safety, health, and environmental compliance or voluntary initiatives
  • To provide Program Administrators with electronic tools to interface with our clients and enhance compliance management & tracking
  • To facilitate sharing of safety, health, and environmental compliance management tools & practices within Cornell University
  • To ensure a consistent user interface with the CMS, ECO and EH&S IT resources
  • To pool our varied IT skills and resources

CMS Tools Definition

Implementation Tools vs. CMS Tools

The CMS IT Team provides "implementation tools" for the CMS Manager and various CMS teams to facilitate the development and implementation of the CMS. These tools are not intended to be used long-term as part the CMS itself.

CMS Tools vs. Program Administrator Tools

The CMS IT Team has drawn a distinction between tools at the CMS level and tools at the Program Administrator (PA) level. CMS tools will be used university wide to facilitate CMS Processes as shown in the cube figure below. PA tools address specific Media as shown in the figure below. For example, a CMS tool could be provided to centrally track and manage training requirements for all safety, health, and environmental programs for the university. It would be useful to PAs to set training requirements and manage training sessions, and it would also be useful to all other faculty, staff, and students to track their training needs. In contrast, a tool for the Air PA could track all air emission sources on campus. It would be useful only to the Air PA for their job responsibilities.

MEMBERS

Environmental Compliance Office:

  • Laurie Cecere 
  • Sarah Zemanick 

Environmental Health and Safety:

  • Mike Allinger 

Planning, Design and Construction:

  • Chris VanHorn 

        sites: [ environmental health & safety | environmental compliance office ]
 resources: [ Home | CMS Evolution | CMS Manual | Roles | Communications | Others in the News | Help ]
Search powered by Google