Conferences & Events
Events for all Levels and InterestsStay
Jump Start Your Career GrowthStay
Get on the Higher Ed IT MapStay
Uncommon Thinking for the Common Good™Stay
There are many technology services available to provide collaboration tools for small and large groups of people to easily work together. The tools are used in the classroom, between departments in an institution, and between members of different institutions.
This section will define any terms that might need additional explanation to help people better understand the service components.
Successful approaches and options for providing the service
This section will list alternatives for providing the service. A framework for providing the service will include design recommendations and methodologies to improve efficiencies and processes. Alternative hardware and software products might be listed. Various support models and architectures could be identified. Various management tools can also be included. Advantages and disadvantages to each approach/option should be included.
- Google Apps
Requirements for providing a successful service
List of items required for ensuring a successful service delivery. Some of these requirements may be generalized or directly related to a specific delivery model and should be noted. Include dependencies on other services required to provide the service listed.
- Ability to share and edit documents among a group of people
- Ability to chat/message interactively in a group.
- Revision history for all documents and wb pages.
Benefits to providing the service
List of benefits to the various constituents (students, faculty, employees, alumni, parents, etc.) at the institution. Describe how the service can improve efficiencies and support the mission of the institution.
- Ability to collaborate without any geographic limitations.
Nice-to-Have Options for the service
Optional items that might be useful when providing the services, but are not critical to the success of the service.
Costs - Approximate costs for products and people
Costs should be approximated and are not required. They can include one-time costs, annual (on-going) costs, and staff/resourcing costs.
Provide a list of responsibilities staff will be required to perform to provide the services. This might include workflows on how the service is supported among different teams in the IT organization.
- Web Management Experience (IIS, Apache, etc.)
- Database Management Experience
- Ability to integrate and use directories (AD, LDAP)
Best Practices to providing the service
Include information regarding engaging stakeholders, tracking & resolving issues, planning the service implementation, training plans, communication plans, design architectures, etc.
Risks/Concerns with providing the service
This area will identify the factors and risks which might cause the service to fail. This area will also discuss how to plan to mitigate those risks. This area should include any potential customizations which might be required to providing the service.
Institutions using the service
List institution web sites in this area which provide the services.
Reference information for expert people in providing service
If an expert is interested in providing additional information on a service to others, they could list their contact information in this area.
Mailing list information for the service
Include information on joining appropriate Educause mailing lists, other higher education mailing lists for learning more about the service.
Other external resources available for the service
A list of reputable blogs, vendor web sites, linkedIn groups, twitter feeds, or other resources should be included.