Computing & Communications

Also known as Institutional Computing, Administrative Computing supports the computing functions running on the IBM mainframe and consults with the Institutional Computing Advisory Committee concerning:

• Administrative Computing service rates
  
• Priorities for allocation of institutional computing resources
  
• Long range institutional computing planning

Mission Statement

Administrative Computing provides UCR with the highest quality programming and technical services possible, supporting campus instruction, research, and public service. Administrative Computing fulfils its mission primarily via the support of the campus Payroll Personnel System (PPS) and the Student Information System (SIS) and other applications/services as required by the campus and the University of California Office of the President (UCOP). In all its endeavors, the Administrative Computing team will abide by UCR's policies and procedures and will strive to operate within budget and per approved campus recharge rates.

Services

• Data Control Service The Data Control service is designed to provide special handling for the administrative user who needs individual attention for production runs. Data Control personnel will provide the following: schedule and monitor job processing, coordinate delays, verify job output, and arrange for the distribution of the output.
• Equipment Shipping, Pickups, & Surplus
• Mainframe Security IBM's RACF security package operates on the IBM mainframe. RACF access to data is granted on a need-to-know basis; requests for data access must be made in writing to Administrative Computing. RACF utilizes a combination of userid and password to control who can access what resources and how and when those resources can be accessed.
• Storehouse Requisitions Storehouse now uses CAS authentication.  You may browse storehouse products without signing on, but if you wish to place an order, press here to authenticate.  If you are not authorized to place storehouse orders please see your departmental SAA for authorization.
• Trouble Reporting Any problem reported should be supported with a listing and output, or in the case of an online system problem a list of exactly the steps you were doing leading up to the problem. Suspected software problems should be brought to the attention of the programmer in charge of the application.

Staff