Engineering Intranet

1
Engineering Intranet Presented by Paul
Davis Project Web site intranet.engr.cornell.
edu/intranet/IT/collegeIntranet
2
Goals for the Intranet

• Develop a Website to support Faculty and Staff in
  doing administrative parts of their jobs.
• To provide Infrastructure to Support College's
  Best Practices Deliverables .
• To provide intranet to academic departments, not
  just the Dean's office.
• Phase I
• One stop shopping" for information about
  administrative processes in several areas.
• Almanac of reference materials such as data
  tables, reports, and a college fact book

3
Vision How Do I AnswersOne stop shopping for
Information

• Address needs from the users perspective
• Use the language of the reader.
• Complete authoritative information for each
  area covered
• If the topic area is covered on the intranet, you
  shouldnt have to look elsewhere.
• Easy to find what you need
• excellent navigation
• Best source of information on Campus
• But dont rewrite stuff available elsewhere, link
  to it
• Not simply a catalog of existing materials
• Decide what we want first. If its not available,
  write it.

4
Audiences

• Customers
• E.g. someone who needs to buy something
• Need text written in their language
• Presented from their perspective
• Many people will read each page
• Should be written well
• Processors
• Only 10 or 30 people for each topic (e.g. all
  purchasing professionals in the college)
• Will be writing for other people like you
• Can be much more informal

5
Pilot is Addressing Five Topic Areas

• Human Resources
• Graduate Program Administration
• Safety (Addressing safety manual)
• Purchasing (part of finance)
• Almanac (fact book, etc.)

6
Intranet Content and Best Practice Team
Responsibilities

• Identify your audiences and the information they
  need
• Prioritize pages to write
• Write the content or find someone to write it
• Develop site map and navigation
• Identify and make changes as needed
• Audience driven improvement
• Determine how well you are meeting your audiences
  needs
• Improve information navigation as needed

7
Oversight Team Responsibilities

• Overall project management Coordination
• Technology
• Overall navigation
• Maintaining consistency across site
• Providing tools and training you need
• Phasing of the project

8
How Do I AnswersOne stop shopping for
Information

• Address needs from the users perspective
• Use the language of the reader.
• Complete authoritative information for each
  area covered
• If the topic area is covered on the intranet, you
  shouldnt have to look elsewhere.
• Easy to find what you need
• excellent navigation
• Best source of information on Campus
• But dont rewrite stuff available elsewhere, link
  to it
• Not simply a catalog of existing materials
• Decide what we want first. If its not available,
  write it.

9
Navigation Homepage
10
Navigation Second level Nav Page
11
Navigation Choice Page
12
Template Answer Page
13
Later Phases

• Staff and Department Directories
• Manage department, committee and other types of
  memberships, print mailing labels, create email
  lists, etc.
• Access control
• Use memberships from directories (described
  above) to limit access to pages or subsites
• Project and committee sub sites
• Have a place for everyone on a committee to post
  and share documents so you dont have to email
  them around all the time
• Other administrative tools
• We are starting specification of a space
  inventory system

14
Intranet Collaboration Model

• Web Financials
• Started in one dept
• Grew to CALS
• Then grew to many colleges
• Finally grew to campus
• GAPS
• Developed in ECE dept
• Grew to College of Engineering
• Now outside units using it too
• Both leveraged local knowledge and grew based on
  demand

15
Two Adoption Options

• Take Our Code
• Well give you our code
• You can hire same person we are using at CIT to
  support your effort
• Can join us in hosting at CIT
• Join us on our server
• You can pilot with us on our server
• You can hire same person we are using at CIT to
  support your effort on our servers
• This allows more interconnection of content
• This is the plan for the safety manual

16
Open Issues re EHS Partnership

• Branding
• Control of content
• Interlinkages between Engineering and EHS
  content
• Structure of Safety Manual on web site (book or
  answer pages)