Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt

ChemIT staff members work hard to bring value to to CCB research, teaching support, and administrative groups. Learn more about what drives us!

 

See also

Questions to answer

...

  • What do we value?
  • What do we measure, gauge, evaluate?
    • Ideas: What was done? What affect did we have? (practical outcomes, emotional impacts) How much did we do? What are reasonable targets for any of these measures?
  • Where are we relative to our goals or aspirations? (How define?)
  • Where do we want to go? (How define and measure areas of work?)

ChemIT exists to:

Provide local, focused IT services in:

  • Research
  • Teaching
  • Administration

The types of services are either unique or value-added.

  • For commodity services, only provide them if super-efficient and/ or highly valued.
 

Office Desktop Computing and related

Instrument supportComputational and Cluster serversOther stand-alone serversOther*
ResearchYesYesYes

Yes: Crane: Fileshare

Scheraga: Synology storage

Yes
TeachingYesYesNo Yes
AdministrationYesNoNo

ChemIT: Large storage for software

CCB: License server

Yes

*Other includes:

Chen group's data storage "bays"

Cerione and Crane's 3D-viewing hardware and software (Linux)

Crane (and others?) SBGrid

Teaching lab computers, 3 distinct sets totalling over 100(?) off-network laptops

Stockroom's custom-built Point-of-Sale WebApp

Physics Testing Center custom-built grading systems (3)

ChemIT's Actions and Decisions are:

  • Transparent
    • Ensure we are working on the "right" things
  • Efficient
    • Ensure we are doing the work right.
      • Learn to productively say no, when appropriate. (smile)
  • Sustainable
    • Avoid staff burn-out, train to ensure continued relevance, and budgets & funding reinforcing most valued services

ChemIT Priorities are:

  • Relationships
    • Work on the "right" thing though mutual understanding and appreciation.
      • Meet real needs, balanced against total costs and competing demands

...

  • Track most every non-project request, called a "ticket".
    • A snapshot of "open" tickets: Title description, who it's assigned to, date it was created, its status, etc.
    • Monthly count of tickets per person completed.

Tools and Techniques

SWOT

  • Strengths (internal)
  • Weaknesses (internal)
  • Opportunities (external)
  • Threats (external)

Example

Context

...