ITS Services List and Current Projects - draft


Purposes of this document:


Current services are in normal text.

Current or Planned Projects are in Italics.

I have tried to put [in brackets] the T-Reqs group responsible for each service, or what information I have about projects and project leads for current or planned projects.

Note that this is not a list of tasks or ongoing projects which are integral to the functionality of each service.  That level of granularity can be provided if necessary.  This is intended as a list from a broad user perspective of our services.

 The last section, ITS Internal Services, is added on because infrastructure needs of the rest of the services on the list are dependent on certain services which ITS provides for its own use.  In a sense, we are our own users for these services.


ITS Lab Services [ITS Lab group]

UNIX Cluster Services [ITS Unix Admins, ITS Accounts, ITS Aliases groups]

Windows Cluster Services [ITS Win Admins groups]

Mac Cluster Services [ITS Lab group, at least for now]

Student House Lab Services [ITS House Labs group]

News/NNTP Services [ITS Usenet News group]

Online Calendar Service (still in development) [ITS UNIX Admins, at least for now. Project lead: Jennifer]

Caltech Email Services

Web Publishing Services [ITS Web Group. Project lead: Adele]

Computer Security Services [ITS Computer Security group]

Sitewide Software Licensing:  for pay and campus-wide, client-side and server installs [ITS Software Licensing group]

Registry Services

Remote Network Access Services [ITS Network group]

Network Infrastructure [ITS Network group, ITS NI Cluster Admins group]

Network Services [ITS Network group, ITS NI Cluster Admins group]

Digital Media Center Services [DMC group]

Helpdesk - support on demand and by appointment [ITS Helpdesk group]

Hardware Repair [ITS Hardware Repairs group]

Outreach Services

Contract Services (I think that I've got all these under the correct heading. Need to check with Tony!)

Services For Sysadmins

ITS Internal Services (things we provide to our own department to keep us functional!)


Future Developements

We'd like to have clearly defined priorities for ongoing services and current and planned projects, so we all understand how resources are being allocated and why, and to give us a better idea of how to spend our own energies relative to the big picture.

We would like to get to the following point of service standards:

For an ITS service to be considered "in production", certain criteria should always be met, to guarantee quality or service and continuity of standards across group boundaries within ITS.  This table shows what features must be in place for an ITS service to be in a certain state:
Supported

Red

Not Supported
Production Exists.
Repeats.
Is documented.
Automation optimization is assigned and/or noted as in progress by project lead.
Auditing development is assigned and/or noted by project lead.
Current problems are assigned and/or noted by project lead.

-- Nothing exists in this category,
by definition and policy. --

Black Line

Not Production Exists.
Repeats.
Is on it's way to being documented.

Line

Exists.

To cross the red line from Not Supported to Supported, a software package or service must:

To cross the black line from Not Production to Production, a software package or service must:


Author: Adele Shakal
Filename: services.html
Location: http://www.its.caltech.edu/~adele/services.html
Draft as of 15:12 February 14, 2001