Information Management Committee: Difference between revisions

From Bike Edmonton
Jump to navigation Jump to search
(Split Social media integration to IMC Social Media Integration)
(Unmerged (deleted) 2010 committee information)
Line 1: Line 1:
Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.
Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.
Information about the 2010 version of the Committee can be found [http://edmontonbikes.ca/w/2010_Committees#Information_Management here].


== Information Management Committee 2011-2012 ==
== Information Management Committee 2011-2012 ==
Line 90: Line 91:
* [[Committee Name Minutes December 2011]]
* [[Committee Name Minutes December 2011]]
* [[Committee Name Minutes January 2012]]
* [[Committee Name Minutes January 2012]]
== Information Management Committee 2010-2011 ==
* '''Chair:''' Chris
* James
* Brett
* Monica
* Olivier
* Axel
===Topics of Focus===
* membership database
* maintain archives and file security
* integration of website, google calendar/docs, facebook, twitter, other community calendars/social networks
* wiki maintenance
* migrate mailing list
* point of sales
=== Terms of Reference ===
==== General Purpose ====
To manage the technical infrastructure for EBC, enabling non-technical users to fully-utilize our resources and manage information. This includes setting up and managing physical infrastructure at BikeWorks, managing the backend of our internet presence (e.g. setting up, configuring, designing and maintaining things, but not being responsible for actual content). Specific work includes:
# selecting and deploying new technology (hardware and software)
# analyzing online security
# ensuring EBC documents (both public and private) are organized and accessible
# maintaining BikeWorks computers
# setting up remote access for financials
# setting up an online payment system for memberships
# developing and deploying new point of sales system/membership database
# migrating primary EBC website to new platform (Wordpress)
# online event registration/payment
# selecting and configuring in-house newsletter software
# maintenance of Google and social media presence
# managing EBC e-mail accounts (aliases, groups, gmail, calendar)
# "subletting" space on webhost to generate revenue
# collecting digital images for EBC use
# maintaining websites (stolenbikes, brb, cycleedmonton, edmontonbikes, ghostbikes.org, bikecollectives.org)
# analyzing data (e.g. membership data, climate data)
# some amount of data entry
# monitoring and archiving media
# manage hosting and domain names
# developing new online resources (e.g. trail condition reporting service).
# Documenting where and how information is stored in the organization.
# Audit IPv6 compliance
==== Key Duties and Responsibilities ====
===== Level of Authority =====
Much of this committee's work is very public-facing, and may be the first interaction people have with EBC. Any major, public-facing changes, therefore (such as a website redesign) should be passed before the board for review, though decisions can be made by the committee without a board vote once a reasonable amount of time has been given for review (unless the board indicates otherwise during this review period).
Decisions involving a significant new financial cost or liability to EBC must first be recommended to the board for approval.
Decisions involving significant privacy or security concerns must also first be recommended to the board for approval.
===== Reporting Relationship =====
The chair of the committee shall submit written reports to the board prior to each board meeting.
==== Composition and Appointments ====
The chair will be selected by the board of directors based on open nominations. The chair may appoint anyone to the committee. The president and executive director are ex officio members.
==== Meetings ====
At least once every 2 months.
==== Resources ====
===== Financial =====
$210/yr for hosting, $50/yr for domain names, $150/yr for infrastructure
===== Staff =====
Volunteers to do:
* web development
* systems analysis
* data entry
* IT support
* statistics
* security analysis
Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).
==== Specific Annual Objectives ====
==== Reports and Target Dates ====
==== Review and Evaluation Process ====
==== Approval Date and Review Date ====
=== Meetings ===

Revision as of 04:42, 29 March 2012

Note: Split Information about social media used by EBC to IMC_Social_Media_Integration. This page should only describe the commitee work. Information about the 2010 version of the Committee can be found here.

Information Management Committee 2011-2012

  • Chair: (name)
  • Members:
    • (name)
    • (name)

Topics of focus

  • Brief point form summary of major focus
  • topic
  • topic

Terms of Reference

  • The Terms of Reference (TOR) is used by a committee as a tool to help it guide its own direction, as well as to make clear its powers, boundaries, and role within the broader organization. It should answer most general questions that would arise during its work regarding the committee's relationship to the rest of EBC's governance structure. (e.g. does the hiring committee directly make job offers, or does it simply make hiring recommendations to the Board?) It should also answer, "what will this committee accomplish, what can I do as part of this committee, and why do we want to do this?"
  • The TOR must be clear, specific, and tangible. The purpose of it isn't to be a meaningless form: it should provide clear guidelines and measurable goals.
  • The following questions are examples of the kinds of considerations to make. The TOR doesn't have to answer every question, or go into every detail, nor are the questions exhaustive.

General Purpose

The raison d'être for this committee?

Key Duties and Responsibilities

Level of Authority
  • Is the committee's work public-facing?
    • Can the committee make decisions regarding public-facing matters?
    • Is board approval required?
    • Publications, blogs, and public representation?
  • What authority does the committee have to make decisions involving cash? Limits, thresholds?
  • What powers regarding privacy, security?
  • Access to member information?
  • Can the committee enter into contracts (verbal included) on behalf of EBC?
    • What kind?
    • Board approval required?
Reporting Relationship
  • Who will submit reports?
  • How often will reports be made?
  • When will they be submitted?
  • How will they be submitted (written, oral)?

Composition and Appointments

  • How will the chair be nominated?
  • Who will select the chair from nominations?
  • Who should be ex officio members?
  • How will members be selected?
  • Can the chair appoint members?
  • How many members should there be?
  • Who should individual committee members represent? e.g. 1 person from the mountain biking community, 1 person with urban planning experience, etc.

Meetings

  • How frequently will the committee meet, at minimum?

Resources

Financial
  • How much money, and over what time period, will the committee need to complete its goals?
Staff
  • How many volunteers will be needed?
  • How many hours of volunteer time?
  • What are the key volunteer roles?
  • What kind of paid staff time is needed?
  • Are paid staff required for meetings?
  • How many hours of staff time is needed?

Specific Annual Objectives

  • Goals with numbers, dates (e.g. 200 new members by June 2010)
  • Goals made measurable (e.g. 20% improved BikeWorks user satisfaction, measured using a survey developed by the committee)
  • Reason for prioritizing of these goals, if not clear

Reports and Target Dates

  • e.g. user satisfaction report published one month prior to the AGM

Review and Evaluation Process

  • How will progress and projects be evaluated?
    • When?
    • Who?
    • How often?
    • Using reports?
    • How will stats be collected?

Approval Date and Review Date

  • When was this TOR approved by the board?

Meetings

Meeting Minutes