University of North Texas

Information Resources Strategic Plan

Fiscal Years 2001 – 2005

Table 1: Goals, Objectives and Strategies

Item

Description

Goal

The University of North Texas will deliver seamless, integrated university services to citizens through coordinated, university-wide information resources.

Supports the 1999 State Strategic Plan for Information Resources Goal 1: Texas state government will deliver seamless, integrated government services to citizens through coordinated, statewide information resources.

Supports the University’s goals of (A) provide instructional and operations support, and (B) provide infrastructure support

Objectives

Integrated information technology services are available to students, faculty, staff, alumni, and citizens through a World Wide Web interface.

Outcomes:

· Full university admissions application, registration, financial aid, and fee payments are available through an appropriately secure electronic interface.

· A robust, production-quality, appropriately secured Web-based payment process for course registration is available.

· A robust, production-quality, appropriately secured Web-based admissions application process that conforms to State and Federal security and privacy regulations is available

· A robust, production-quality, appropriately secured Web-based financial aid application process that conforms to State and Federal security and privacy regulations is available.

· A robust, production-quality, appropriately secured Web-based student registration process is available.

· Web- and e-mail-based advising, degree audit, and course equivalency procedures for all students are available.

· Federally mandated student authentication requirements for personal identification numbers to grant access to systems on campus are implemented.

· An Undergraduate Admissions Prospect System based on modern technology (hardware and software) and with functionality to accommodate the needs of Graduate Admissions and International Admissions as well as Undergraduate Admissions is in use.

· A robust, production-quality, appropriately secured WEB interface for inquiry access to the human resources information system for departments and employees is available.

· A robust, production-quality, appropriately secured Web human resources training and development enrollment/ registration form that conforms to State and Federal security and privacy regulations is available.

· A Web employment application form for vacant staff positions is available to on- and off-campus applicants.

· A Web biographical data form for faculty and staff to review and change their biographical data in University Human Resource files that conforms to State and Federal security and privacy regulations is available.

· A robust, production-quality, appropriately secured process for distributing financial aid disbursements and reimbursements via electronic funds transfer (EFT) to student bank accounts is available.

· A robust, production-quality, appropriately secured Master Promissory Note process for state and student loans is available

· An evaluation of appropriate operating platform for the Degree Audit and Reporting System has been completed and migration to new platform completed if necessary.

· A university-wide scholarship database providing information about financial assistance opportunities across campus is available.

Strategies

By September 30, 2000, complete evaluation of commercial systems that provide desired functionality, with emphasis on student systems. Evaluate "build vs. buy" options (or combination of both) and determine which approach is preferred (also by September 30). Subsequent to this decision, seek funding and other resources required to implement appropriate solution. Proceed with system purchase (if that option is chosen), or with in-house development (or both) and implementation.

Additional staffing for the central programming staff of the Computing Center has been approved for FY 2001, strengthening the University’s ability to complete critical student records projects.

Goal

The University of North Texas will enhance the performance of its mandates, mission, and core competencies through appropriate application of information resources.

Supports the 1999 State Strategic Plan for Information Resources Goal 2: Texas state government will enhance the performance of its agencies’ mandates, missions, and core competencies through appropriate application of information resources.

Supports the University’s goals of (A) provide instructional and operations support, and (B) provide infrastructure support

Objective

A robust, highly functional suite of administrative applications supports administrative processes and allows reporting and processing mandates to be effectively accommodated.

Outcome:

· Support for administrative applications and computers systems, including meeting mandated requirements for changes to systems imposed by state, federal, and other regulatory bodies will be an ongoing process.

· A Web interface for insurance enrollment at the University is available.

· Modifications to the fiscal data systems are completed to consolidate annual financial reports for UNT and UNTHSC and to meet the requirements of Governmental Accounting Standards Board rules changes.

· A database on compliance requirements is available and supported.

Strategy

Additional programming staff will be added in the FY2001 fiscal year to support the workload of the administrative programming department, including a position to support the compliance database.

Objective

A robust and "best of class" communications infrastructure supports the use of the University’s information resources.

Outcomes:

· All University-owned dormitories are wired with 100Mbps Ethernet connections and attached to the campus backbone.

· All offices are wired with 100Mbps Ethernet connections and attached to the campus backbone, with selected research and high-speed computers connected at gigabit speed.

· The University’s Ethernet backbone operates at gigabit speeds, has redundant core switches, and connects all University buildings.

· The University connects to the Internet 2 network with a DS-3 circuit by August 2000, with an OC-3 connection by December 2001, and with higher speed connections in 2002 and beyond as demand warrants.

· The University connects to the Internet 1 network with a DS-3 circuit by August 2000, with an OC-3 connection by December 2001, and with higher speed connections in 2002 and beyond as demand warrants.

· The University will develop a co-location facility in the Dallas/Fort Worth Metroplex to house communications gear and equipment with UNT Internet content to allow the University to project its presence into this market.

· The voice communications network on campus provides state-of-the-art capabilities, including voice-over-IP if appropriate and cost effective.

· An adequate number of videoconferencing rooms are available on campus as well as at metroplex sites to allow the University to offer distributed learning courses at locations convenient to students.

· An RFP for telecommunications services will be issued to determine the future provision of voice services upon the expiration of our current CentraNet agreement with GTE on May 17, 2001, and the resulting successful proposal will be implemented.

· The University will select and implement a telemanagement system.

· A Network Operations Center will be developed to effectively manage the University’s data, video, and voice communications resources.

Strategies

· A project to wire the University dormitories will be completed in Summer, 2001, and a project to complete the conversion of the campus data communications infrastructure to 100Mbps connections with gigabit backbone is about 30% completed now, with the remainder of the project to be completed by the Summer of 2002.

· Quotes have been received to lease and provision a DS-3 circuit to the General Services Commission’s Internet provider (AT&T) and that circuit will be in place and operational by the Fall, 2000 semester. The University anticipates receiving a sizable Telecommunications Infrastructure Fund in the Fall of 2000, and the bulk of that grant will be used to expand our Internet 1 bandwidth either through the lease of fiber to a co-location in the Dallas/Ft. Worth metroplex or through the leasing and provisioning of additional DS-3 or OC-3 lines.

· UNT is currently employing a telecommunications consulting firm to study our long-term voice communications needs and one result of the study will be a functional RFP for our future provision of voice services. We expect to release the RFP in late Summer or early Fall, 2000 and will evaluate the proposals, select a vendor, and implement the plan depending upon the outcome of the evaluation and selection process.

An addition to the Information Sciences Building that houses the bulk of the Computing Center’s operations has been approved and architectural design work is being performed at this time. The building is expected to be completed in late 2002, at which time a network operations center being designed for the building will be brought on line.

Objective

Directory-enabled communications provide administrative information to individual or selected groups of students, faculty, staff, and other constituencies through standard e-mail addresses.

Outcomes:

· All University students have e-mail accounts on our server and are able to forward messages to preferred accounts.

· Students regularly check their University e-mail accounts for official messages from administrators.

· Faculty and staff e-mail system has capabilities for sending messages to selected groups of recipients (such as all tenure-track faculty, all staff in Printing Services, etc.)

Strategies

· Free e-mail accounts are already provided to any student registered at UNT, and any user of the mail system can use a Web form to set up mail forwarding to preferred mail accounts off campus.

· A bulk e-mail system is in the final stages of testing and will be released for use on June 1, 2000. That system will allow authorized university administrators as well as all faculty to send mail messages to selected groups of students through a Web form.

· Faculty will be notified of the bulk e-mail system in mid-May, 2000 and will be asked to notify their students of the requirement that they read their official e-mail on a regular basis. The Board of Regents passed a policy early in 2000 stating that e-mail is an official form of communications between the University and students.

Objective

The University will apply appropriate technology through the adoption and application of information resources standards and guidelines.

Outcomes:

· Desktop computers are acquired and upgraded under a regular replacement cycle plan.

· Desktop operating systems and software are upgraded on a regular basis to the most appropriate versions.

· Central general purpose Unix systems respond to growing demands for e-mail and Internet access.

· Central research Unix systems meet demands for high-end research computing.

· Central administrative computer hardware and software are upgraded as necessary to maintain adequate reliability, security, and response times and to provide the best support to users of administrative services.

Strategies

· Major portions of the University’s Higher Education Assistance Funds are allocated to colleges and administrative departments for the purchase of computers. Supplemental funds to replace the money that will be "lost" as a result of the reduction in UNT’s HEAF funds for FY2001 and beyond were set aside in the FY2001 budget.

· The University has a Microsoft Campus Agreement through which it purchases Windows operating systems and common desktop applications software. The campus-wide agreement reduces the cost to the departments for this software, greatly increases the efficiency of the purchase process, and thereby removes financial and procedural impediments to upgrading to appropriate versions of software.

· The Computing Center, with the advice of the Information Resource Council, regularly upgrades central Unix servers, such as the research Unix machine and the student e-mail server. HEAF funds are allocated for these purposes each year.

Objective

The University attracts, hires, and retains qualified information technology support staff.

Outcome:

Compensation levels of information technology support personnel are regularly reviewed and imbalances between University and competing organizations are corrected.

Strategy

· The University regularly reviews IT staff compensation (a significant augmentation of salaries for many IT workers was made early in 2000.)

Goal

The University will ensure the privacy and security of the information and information resources entrusted to it by the people of Texas.

Supports the 1999 State Strategic Plan for Information Resources Goal 3: Texas state government will ensure the privacy, security, and historical integrity of the information and information resources entrusted to government by the people of Texas.

Supports the University’s goals of (A) provide instructional and operations support, and (B) provide infrastructure support.

Objective

A standard, integrated directory service for user authentication and security is used to provide access to University information resources.

Outcomes:

· A single University ID and password provides authentication to all Web-based services.

· Authentication to University services and machines is based on digital certificates meeting State of Texas standard

Strategy

· The University continues to investigate digital certificate technologies that conform to the Department of Information Resources standards. Standards-based (LDAP) directory services have been developed and we are currently developing a strategy to merge various ID and password schemes on campus into a single scheme without degrading the security that the existing methods provide. Web-enabling our central student and administrative systems is accelerating the process of finding a solution to the single ID/password problem.

Objective

Information systems at the University are protected against security threats coming from both inside and outside the campus.

Outcomes:

· Security threats are detected and reported to the State as required.

· The University is protected against intrusion attempts and against software viruses.

Strategies

· The Computing Center has designated a position as the campus’ central security coordinator and the person in that position will report security threats and our responses as the new State regulations require.

· The University has a site license for one of the major virus protection packages (McAfee VirusScan) and will continue to renew that license to keep it in effect. We are also investigating additional technologies for virus scanning and protection, such as server-based or gateway-based scanning engines so we can respond more quickly to new viruses (not relying solely on installing the latest virus definition files on each desktop, for example.) By the end of the 2000 calendar year, we plan to have additional safeguards in place.

· A security team has been appointed to coordinate the campus’ efforts to detect and prevent security threats. The team is composed of the campus security coordinator, the virus software manager, administrative computing security personnel, data communications security personnel, and Web support personnel. Security incidents will be recorded and tracked in the call tracking system that all computing support departments on campus now use, Remedy.

Goal

The University’s acquisition, use, and management of information resources will be driven by customer needs.

Supports the 1999 State Strategic Plan for Information Resources Goal 4: Texas state government’s acquisition, use, and management of information resources will be driven by customer needs.

Supports the University’s goals of (A) provide instructional and operations support, and (B) provide infrastructure support.

Objective

Accurate and timely University documents, data, and services will be available and linked electronically.

Outcomes:

· Document imaging technology for the storage and retrieval of administrative records is employed and integrated into the administrative records databases and into the workflow of service departments.

· Required reports are available for viewing electronically, particularly over the Web as required by new State regulations.

· The Automated Purchasing and Accounts Payable module of the University’s General Ledger Accounting System provides on-line submission and updating of purchase order data.

· The University will implement a suite of long distance resale services, including residential long distance for students in University Housing, 1+ switched long distance for off campus students, faculty, and staff, prepaid calling cards, and an integrated UNT ID/AT&T calling card.

Strategies

· Several departments on campus are studying document imaging technologies to determine how they will integrate into current systems. A decision about which technology best meets the needs of the University will be made by the end of calendar year 2000.

·The Computing Center will continue to develop the APAP system and will enhance its functionality after its initial rollout.

· Following a request for proposal process, the Telecommunications department has selected AT&T to provide long distance resale services and that plan will be rolled out starting in the Summer of 2000.

· The University will explore partnering with one or more wireless communications services to provide wireless voice service and wireless Internet access to students, faculty, and staff for both on campus and off campus use.

Table 2: Information Resources Policies and Practices

Category

Brief Summary/Overview

IR Priorities

The responsibility for preparation of IR (Information Resources) plans and monitoring of implementation outcomes is jointly shared by the IRC (Information Resources Council,) the UNT Information Resources Manager (the Associate Vice President for Computing), and the IR Steering Committee. The IRC represents all academic units as well as major administrative units on campus and its advisory groups are key to successful UNT IR planning and effective resource sharing. Permanent subcommittees of the IRC which advise the IRC regarding issues related to specialized areas include:

· Instruction Program Group

· Research Program Group

· Communications Program Group

· Standards and Cooperation Program Group

· Administrative Program Group

The University also depends on the IRC and IR Steering Committee to regularly evaluate policies for the assignment of priorities for computer use and the allocation of computing information and instructional technology resources to ensure academic and administrative needs are adequately served. Priorities for development and maintenance of administrative information systems are set by the Vice Presidents for their respective areas (jointly for applications encompassing two or more VP functional areas). Other capital funding priorities are recommended by the IRC

IR Planning Methodology

The methodology used for information resources planning at UNT follows the state-mandated requirements and instructions. The responsibility for preparation of IR plans is jointly shared by the designated UNT Information Resources Manager (the Associate Vice President for Computing and Communications Services) and the University Information Resources Council (IRC). The Strategic Planning Committee of the IRC prepares a plan, which is reviewed by the IRC. The Board of Regents approves the IR Strategic Plan, which is submitted in conjunction with the University Strategic Plan.

Operating System

On the desktop, Windows 98 is currently the predominant operating system, with Windows NT occupying a significant number of machines on campus. Apple Macintosh and several versions of UNIX, including Linux, are also supported in some areas. Novell NetWare is the standard supported network operating system, with Windows NT being used and supported on application servers in many areas. Sun’s Solaris operating system in the UNIX standard for UNT's minicomputer systems. VM/CMS and OS390 are the supported operating systems on the academic partition of the IBM mainframe. OS390 is supported on the administrative partition.

Development Methodology

Major administrative applications are developed using the "LBMS Structured Development Method/Systems Engineer" methodology. This is an established approach for the analysis, design and specification of computer systems using "Composite Logical Data Design" that seeks the optimum combination of the positive features of "relational" and "entity modeling" approaches. Systems Engineer is a powerful microcomputer based software package that fully supports the LBMS methodology.

Software Audit and Management

The University will use automated software inventory packages in most cases for conducting software audits. UNT has a site license for Novell’s ManageWise, which performs centralized discovery of software on desktops. Lists of software will be checked against purchase orders and proofs of ownership.

UNT aggressively pursues site licenses for common desktop application software in order to minimize management of licenses. The university currently has a Microsoft Campus Agreement for Microsoft operating systems and office productivity packages, a Microsoft Open License Program contract for other Microsoft products, a campus-wide license for Computer Associates McAfee virus protection software, an Adobe volume purchase agreement for several of that company’s products, and other similar licenses.

Quality Assurance Practices

Providing and maintaining high quality administrative software that functions correctly and predictably is a major concern of the UNT Computing Center staff at all levels. The Administrative Computing division uses LBMS' Systems Engineer CASE (Computer Assisted Systems Engineering) product and follows LBMS' Logical Structured Development Methodology (LSDM) for developing major administrative software applications. Also, rigorous change control procedures are followed when developing, testing, and making modifications to mainframe computer programs. A separate test environment is maintained on the mainframe and all testing must occur in the test environment. (Note: Final testing of ad hoc query / report programs [i.e., programs which are "read only" and will not update production files or the production data base] may be done in the production environment.) New programs (or programs which have been modified) are tested prior to being moved to the production environment. The level of testing done is proportionate to the criticality of the program or the significance of any modifications that have been made. This testing typically includes observation and/or hands-on testing by responsible end users.

E-Government

The University currently has in place electronic forms for course registration and credit card payment of registration fees. The credit card payment function utilizes SSL forms and was extensively studied by the financial office on campus as well as the university’s internal audit office before being released into production. Extending Web-based administrative services such as financial aid, transcript ordering, advising, directory updates, and other such applications is at the top of the university’s list of IR priorities for the next two years. Progress has already been made in providing a middleware interface between our mainframe application and Web interfaces, and our plan is to have all of the major administrative applications Web-enabled by the end of the 2001 calendar year. The University is also investigating commercial student systems that may provide payment options via e-commerce: the decision about which approach is preferred (build vs. buy) will be made by September 30, 2000.

Change Control

Administrative Computing programmers must receive approval of a team leader or other senior analyst in order for software to be moved from the development/test environment to production. It is the responsibility of the analyst(s) to review the testing procedures and results, then to approve the promotion of the software to production. The actual movement of the software into production is done by the Production Control staff, thereby providing for separation of duties between the development and production/operations staff. Once programs have been placed into production they cannot be modified except by being "checked out" from production and placed back into the development/test environment. TreeHouse Software's N2O change control system in use automatically produces a log of changes showing the name of programs being promoted back into production, the date, and a brief explanation of changes made. Internal Audit has on-line access to the change log and they review this log at their discretion.

Security

The Assistant Director for Computing Center Planning and Administration has been delegated responsibility for UNT's information security function. UNT's policies for information security are in place (available on the Web at http://www.unt.edu/irc/policy/security.htm,) and are based on statewide standards. A review of UNT’s information security program for compliance with 1 TAC 201.13(b), Information Security Standards, is scheduled to be conducted by UNT’s Internal Audit department in June, 2000. Information resource users formally acknowledge that they will comply with UNT’s security policies and procedures. A Security Risk Analysis was completed and documented in December, 1997 and was updated in May, 2000. Physical security for UNT's major host systems is based on state standards.

Geographic Information Systems

State GIS standards are used as guidelines for any new projects that could be useful to other agencies, but at this time no GIS applications or databases are in use at UNT.

Disaster Recovery/ Business Continuity Planning

A Disaster Recovery Plan is written for UNT's administrative mainframe and critical data communications systems. The plan is regularly updated and improved. A test of the plan will be conducted in June, 2000. Critical data files and programs needed to resume normal operations are backed up on a regularly scheduled basis and stored in an off-site location. The current plan uses our former mainframe computer room as a cold site. The University currently has a contract to perform a Business Impact Analysis (BIA) with Northrop Grumman, the WTDROC contractor. They have arranged for SunGard to conduct the BIA, with plans to follow that analysis with a contract to develop a full-fledged disaster recovery plan, updating our current plan.

Resource Use

All UNT faculty, staff and students are permitted to utilize UNT computing resources in support of University activities. All faculty and staff have access, as appropriate, to basic microcomputer network services, such as e-mail, general application software, etc. Faculty and staff users are granted access to UNT host systems and applications as required by their respective job functions. All students have access to the General Access Computer Labs, to on-campus and dial-up access to the general Unix/Internet system, and e-mail services on a central UNIX host. User-ID’s on other systems are granted as required to meet each student's academic needs.

UNT’s videoconferencing facilities fully comply with state standards for conducting open or closed meetings using video conferencing.

Contract/Consultant

No formal policy or procedures, other than normal state purchasing procedures, are used for IT consulting and contract programming. However, UNT does not use contract programming services. Occasionally, installation assistance, troubleshooting, and training are acquired in connection with software acquisitions.

Information Sharing

The University regularly exchanges data via network with various State of Texas systems, including the Texas Common Application System, Uniform Statewide Accounting System, State Property Accounting, Texas Payee Identification System, Automated Budget Evaluation System of Texas, Texas Higher Education Coordinating Board, Employee Retirement System, and the Department of Public Safety. Student transcripts are exchanged with other universities and community colleges. Financial information is exchanged with the Texas Guaranteed Student Loan Corporation, banks, etc.

In addition, UNT responds to Open Records Requests through a variety of offices. The Chancellor of the University has designated UNT's Vice President for Legal Affairs & General Counsel as the custodian of records regarding all requests for information under the Open Records Act. Departments may respond directly to the requests with notification to the Vice President for Legal Affairs & General Counsel or the departments may provide the requested information to the Vice President for Legal Affairs & General Counsel's Office, which forward it to the requestor.

Training and Continuing Education

Managers of information technology workers make the determination of training and education needs of their employees as well as arrangements to provide requisite training to those employees. The University provides access to a large number of computer-based training packages that have been purchased over both the on-campus LAN and through remote Internet access. The Human Resources department maintains records of employees’ attendance at UNT training programs.

Data Center Operations

UNT is currently utilizing the WTDROC contractor, Northrop Grumman, to assist in updating our disaster recovery plan and will fully evaluate the cost effectiveness of utilizing the WTDROC for disaster recovery services. The University currently has a waiver in place for its disaster recovery procedures, which include off-site storage of backup tapes.

 

Table 3: Agency Platforms, Systems, and Telecommunications

Agency Platforms and Systems

Category

Type

Operating System

Database Mgmt. System

Capacity/ Size/Count

Comments/Descriptive Information

Mainframe

IBM 9672-R24

MVS/ESA, VM/CMS, OS/390

ADABAS

82 MIPS

The IBM 9672-R24 is a CMOS-based air-cooled mainframe which uses two central processing units to deliver approximately 82 MIPS processing capacity. Characteristics of this machine include minimal space requirements, low power consumption, and low air conditioning (cooling) requirements. The machine has logical partitioning capabilities, which allows our academic functions (instruction and research activities) and administrative functions to each operate in separate logical partitions, so that it appears to each functional area as though they were using two physically separate machines. The processing capacity available to each logical partition is adjustable. Unused CPU cycles in either partition can be used by programs in the other partition. This reduces the impact of short "bursts" of CPU-intensive activities in either partition.

Minicomputer

Sun Ultra Enterprise 500

Solaris

None

8 UltraSparc CPU’s

Primary academic research computer

Minicomputer

Sun E250

Solaris

None

42UltraSparc CPU’s

Primary student Internet access/e-mail server

Network

       

Network topology map follows this table.

Lan Servers (central)

Novell Netware

None

about 104 servers

The campus is migrating to Compaq servers from older servers that were assembled and supported by the Microcomputer Maintenance Shop

Lan Servers (central)

Windows NT

None

about 40 servers

Windows NT servers generally are not used for file and print services, but for Web and various application services. The campus is migrating to Compaq servers from older servers that were assembled and supported by the Microcomputer Maintenance Shop

LAN Servers (Remote)

Migrating from locally assembled to Compaq servers

Novell Netware

None

3 servers

One server is located at the Dallas Education Center to support administrative applications and a computer lab there ; 2 are located at the UNT System Center at Dallas

LAN Client/ Workstations (Central)

Locally-assembled or Mac

Windows 95, Windows 98, Windows NT 4.1, or Macintosh

None

7,000+

Approximately 10% of the microcomputers on campus are Macintosh machines. Most Intel-based computers are assembled on campus by the Microcomputer Maintenance Shop and run Windows 98, with a significant number running Windows NT 4.0

LAN Client/ Workstations (Remote)

Locally-assembled

Windows 98

None

125

The University supports administrative and student computer lab machines at the Dallas Education Center. In addition, about 100 administrative and student computer lab machines are at the System Center at Dallas

WAN Servers

Mail Servers

Novell Netware, Groupwise

Sun Solaris, IMAP

Proprietary

14 Novell servers, one Unix server

Groupwise is the primary mail system used by faculty and staff and is supported by 14 PC-based servers. Student e-mail services are provided centrally through an IMAP server running on a Sun Unix server that is accessed using various clients, particularly the Simeon software and the MailSpinner Web client.

WAN Servers

Web

Sun Solaris, Netscape Enterprise, Windows NT Server, MS Internet Information Server

None

4

The primary central Web server is a Sun Netra running Netscape Enterprise server software. Another Sun Netra runs WebCT, the campus’ Web course management system and yet another Sun Netra runs a streaming video server. In addition, a Compaq server running IIS is used for specialized Web applications. A number of departmental and/or college Web servers are employed on campus as well but are not included in the count here.

WAN Servers

Internet News Server

Sun Solaris

None

1

A Sun SparcServer 20 supports the newsgroup service.

WAN Servers

Internet Mail Router, Mailing List Server

Sun Solaris

None

1

A Sun Ultra 2 hosts the Internet mail router and listserv services.

WAN Servers

DNS, BootP, MX[Mail Exchange] and DHCP Servers

Sun Solaris

None

9

DNS server is Sun E250. One off-site DNS backup is at utexas.edu. . All network managers on campus can manage their own MX/BootP/DHCP/DNS configurations with the software developed here at UNT.

Standalone PC Workstations

PC

DOS, Linux, etc.

None

about 300

Some special-purpose PC’s such as lab data collection machines are not attached to the network. In addition, some obsolescent machines are not on the network.

Internet Service Provider

UNT

 

The University is its own ISP but gets Internet access via the GSC network

Shared Network

General Services Commission

 

The University gets Internet access via the GSC network and also participates in TTVN and VidNet

Network Topology

Table 4: Agency Databases

Database Name

Admissions Management System (AMS) Database

Database Description

This database contains basic information for all categories of applicants to the University. It and the system which maintains the database includes provisions for communicating with students re. missing information, etc. Information maintained is electronically passed to the SRS (Student Records System) when admitted applicants actually register to become students.

Database System

ADABAS

Estimated Physical Storage Requirements

0.04 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

There are plans to store additional information about transfer work in this database. There are no plans to add or enhance GIS functionality or to link this database to a GIS. Depending upon the outcome of the investigation of commercial student records systems, this database may be superseded if a new system is selected.

Database Name

Advancement / Development Information System (ADIS) Database

Database Description

This database and the application which maintains it collects, maintains, and reports detail information about all UNT alumni and other specific donors and supplies information for various solicitation campaigns.

Database System

ADABAS

Estimated Physical Storage Requirements

0.14 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

No major changes are currently planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Automated Purchasing and Accounts Payable (APAP) Database

Database Description

This database contains information needed to support processing of payment vouchers for purchases, travel, interdepartmental orders (IDOs) and other payments handled by UNT’s Payment Services area.

Database System

Oracle

Estimated Physical Storage Requirements

1.5 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

Information contained in this database is shared with other internal (to UNT) systems.

Future

Database changes (primarily addition of new tables) will be required to support anticipated enhancements to the Automated Purchasing and Accounts Payable (APAP) application.

Database Name

Billing / Receivables System (BRS) Database

Database Description

This database and the application which maintains it collects, maintains, and reports student accounts receivable information. Information is electronically exchanged with the Student Records System (SRS) and the Financial Aid Management System (FAMS)

Database System

ADABAS

Estimated Physical Storage Requirements

1.57 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

No major changes are currently planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Capital Equipment Account Tracking System (CEATS) Database

Database Description

This database and the application which maintains it collects, maintains, and reports detail property information about individual items of capital/controlled equipment, including purchase date and cost, current location, general ledger data, acquiring account, person with inventory responsibility for the equipment, etc. System is interfaced to the State Comptroller's State Property Accounting (SPA) system to provide that system with data mandated by the State Comptroller.

Database System

ADABAS

Estimated Physical Storage Requirements

0.16 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

UNT transmits transactions quarterly reflecting activity in CEATS to the State Property Accounting System (SPA). Additionally the Agency Extract from SPA is utilized by UNT's CEATS to produce a reconciliation report for UNT's property manager. UNT's Property Manager interfaces online with SPA to enter some transactions which cannot be sent via batch due to timing or functional reasons. UNT's Property Manager also uses the inquiry functions in SPA.

Future

Changes will be required to this database and to the CEATS application to support GASB rule changes. Examples include a requirement to account for depreciation of capital assets. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Degree Audit Reporting System (DARS) Database

Database Description

DARS or the audit report is designed to compare a student's academic work - at any point in the student's career - with the requirements of an institution's academic program or programs, and to prepare a comprehensive report detailing the student's progress toward meeting those requirements. The report may be produced to report all satisfied requirements first following by any unsatisfied requirements, vice versa, or to report using several other run options.

Audit reports may be prepared in either a "batch" or "on-line" mode. Batch reports are usually prepared for large numbers of students as might be needed prior to student registration, or for all degree candidates, or for a particular major or college.

On-line reports are typically prepared to handle individual student advising needs, to determine where a student would stand in some other academic program, or in using another catalog year/term, ("what if" type questions), or to confirm the affects of some academic program "exception" action for a student.

The Transfer Equivalency System (TRES), a subsystem of DARS, provides automated support for determining the transferability of course work from other institutions (whose courses have been evaluated) to determine the UNT equivalent. Currently this includes all community/junior colleges in Texas and selected senior-level universities. Classes from other institutions for which course equivalencies have been established can be evaluated to determine the applicability of those courses toward a UNT degree. Course data for individual students are either input through a computer terminal or received electronically over the AHE Electronic Transcript Network. Transcripts/reports are then produced showing the equivalency of the course work.

Database System

ADABAS

Estimated Physical Storage Requirements

0.25 GB

GIS Data Classification

This database does not support spatial (GIS)operations and does not contain geographic data.

Sharing

Transfer equivalency information is provided to community colleges.

Future

It is possible that we will need to convert the DARS application to the vendor’s client/server version, in which case the associated database would also be affected. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Development Query System Database

Database Description

This database contains selected data from the Advancement / Development System which is periodically downloaded from that system and stored in an ORACLE database file on a database server attached to the campus network. This database is made available to Advancement Personnel, College Development Officers, and others (as deemed appropriate by the Advancement Office administrators) who use Crystal Reports or other PC-based end-user oriented query and reporting software tools to run ad-hoc queries and produce reports as needed.

Database System

ORACLE

Estimated Physical Storage Requirements

0.75 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

No major changes are currently planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Financial Aid Management System (FAMS) Database

Database Description

This database contains information necessary to allow applicants for student financial aid to be considered for available funds. The database and the application which maintains it support financial aid awarding, packaging, student notification, and BRS system feed functions.

Database System

ADABAS

Estimated Physical Storage Requirements

1.1 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

Information contained in this database is shared with other internal (to UNT) systems, including the Billing / Receivables System (BRS).

Future

Other than maintenance modifications required to comply with periodic changes in federal regulations, no major changes are planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS. Depending upon the outcome of the investigation of commercial student records systems, this database may be superseded if a new system is selected.

Database Name

General Ledger Accounting System (GLAS) Database

Database Description

This database contains basic general ledger accounting information. It and the application which maintains it provide the following functions: 1) post and maintain the general ledger, 2) process claims to produce payments to vendors operating on a modified accrual basis, and 3) produce periodic accounting statements as required by the University, and to meet state and federal reporting requirements. Also allows for on-line inquiry and display of departmental account balances. System is interfaced to the State Comptroller's Uniform Statewide Accounting System (USAS) to provide that system with information as mandated by the State Comptroller. System is used by both UNT and UNT Health Science Center.

Database System

ADABAS

Estimated Physical Storage Requirements

1.56 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

Selected transactions from the GLAS are sent daily to the comptroller's office to be posted in USAS. Encumbrance balances and payable balances from GLAS are calculated and transmitted quarterly to be posted in USAS. UNT receives the USAS History extract and updates some tracking information in GLAS from USAS. Additionally reports are printed locally and distributed to UNT Controller office personnel. UNT Controller Office personnel also interface online to input certain transactions directly into USAS.

Future

We anticipate that GASB rule changes will result in changes to this database and to the GLAS application. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Housing Information System Database

Database System

ORACLE

Estimated Physical Storage Requirements

 

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

No major changes are currently planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Payroll/Personnel / Human Resources Management Information System (HRMIS) Database

Database Description

This database contains basic payroll and human resources / personnel information about employees. It contains the necessary information to allow automated support for payroll processing (including mandatory associated record-keeping and reporting) as well as meeting the special, complex, and critical management information needs of the University for Payroll/Personnel related information. The overall HRMIS system (which collects and maintains the information in this database) includes four major sub-systems as follows: 1) Employee Maintenance: Accommodates all master file maintenance activities related to employee-related data, benefits enrollments, and assorted codes used in payroll processing. 2) Payroll Detail: Supports gross pay and net pay calculations, printing of checks, processing of check reversals, payment of benefits vendors, and periodic payroll reporting. 3) Budgets: Supports all activities associated with the preparation of fiscal year budgets, including both personnel and non-personnel items. 4) Position Control: Supports the requisition and support of individuals to fill those positions. System is used by both UNT and UNTHSC.

Database System

ADABAS

Estimated Physical Storage Requirements

1.82 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

Employee Retirement System - Two way interface of all information concerning state provided insurance benefits in support of plan administration and premium reconciliation. Online inquiry and update of the ERS system in Austin is available locally.

Comptroller's Human Resource Information System - Interface of payroll and personnel data to the states human resource reporting database. Online inquiry and update of the HRIS database in Austin is available locally.

Uniform Statewide Accounting System – Transmission of state paid payroll information to Austin for reimbursement. Online inquiry and some updating of the USAS system in Austin is available locally.

Future

No major modifications are planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Database Name

Student Records System (SRS) Database

Database Description

This database contains information about current students, and course-related information (by term). It also contains facilities (building and room) information to support course scheduling. The database contains the information necessary to allow the SRS application (which collects and maintains the information in the database) to report students' permanent academic record (transcript) information. It also supports student registration for classes via the Telephone Registration (Telreg) System, and via on-line terminals.

Database System

ADABAS

Estimated Physical Storage Requirements

1.2 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

CBM001, 002, 004, 003, 005, 008, and 009 reports are sent to the Texas Higher Education Coordinating Board via FTP. The IPEDS and VA reports are sent to the appropriate federal agency and the NCAA reports are sent to the NCAA. All are sent via FTP.

Future

We will be modifying the SRS application to compute a new grade point average each time a graduate student begins a new degree. These additional GPAs will need to be stored in the database. There are no plans to add or enhance GIS functionality or to link this database to a GIS. Depending upon the outcome of the investigation of commercial student records systems, this database may be superseded if a new system is selected.

Database Name

Telephone Information System (TIMS) Database

Database Description

This database contains detail information about university telephones (location, characteristics, etc.) and usage for long-distance calls. The TIMS application which collects, maintains, and reports the information contained in the database receives long-distance call information from local telephone companies (GTE and AT&T), produces statements (bills), and electronically passes information to the General Ledger Accounting System (GLAS).

Database System

ADABAS

Estimated Physical Storage Requirements

< 0.01 GB

GIS Data Classification

This database does not support spatial (GIS) operations and does not contain geographic data.

Sharing

 

Future

No major changes are currently planned for this database during this planning period. There are no plans to add or enhance GIS functionality or to link this database to a GIS.

Table 5: Agency Applications

Application Name

Access Control Information System

Application Type

Unix-Based Transaction Processing System

Application Description

Remote access from vendor supplied authorization terminals updates statistical and customer data and provides authorization for transactions. Administrative access for fixed format and ad-hoc reporting.

Database System

Proprietary (Vendor Supplied)

Development Language

Proprietary (Vendor Supplied)

Sharing

 

Future

No major modifications are planned to this application during this planning period.

Application Name

Access Student Service Information Systems by Technology (ASSIST-IVR)

Application Type

Interactive Voice Response

Application Description

This interactive voice response (IVR) system interacts in real-time with mainframe-bases systems (including the Admissions Management System, Student Records System, Financial Aid Management System, and Billing Records System) to allow students to do the functions listed below from any touch-tone phone. (Except where otherwise noted, the requested information is spoken back to the student on the phone using computer-generated speech.):

Receive admission, registration, and scheduling information

Order transcripts and university publications (requested documents are subsequently mailed to requester)

Receive academic record and course information by phone (includes fax option for academic status and grades and for student course schedule)

Receive student account receivable information (account balances and payment deadlines)

Pay account balances by credit card (telephone only)

Receive housing and financial aid information

Receive academic calendar and graduation information

Database System

Accesses Student Records System (SRS) Database which is maintained by that application. The SRS Database uses ADABAS.

Development Language

C, Write-1, COBOL

Sharing

 

Future

No major modifications are planned to this application during this planning period. The application is included in the project "AD1301: Upgrade Voice Response System" in the Biennial Operating Plan.

Application Name

Access Student Service Information Systems by Technology (ASSIST on the WWW)

Application Type

Web-Based

Application Description

[Note: This application is, in essence, a Web-based version of the ASSIST-IVR application described above]

This web strategic system interacts in real-time mode with mainframe-based systems (including the Admissions Management System, Student Records System, Financial Aid Management System, and the Billing / Receivables System) to allow students to do the functions listed below from the WWW (world-wide web).

 

Receive admission, registration, and scheduling information

Order transcripts and university publications (requested documents are subsequently mailed to requester)

Receive academic record and course information by phone (includes fax option for academic status and grades and for student course schedule)

Receive student account receivable information (account balances and payment deadlines)

Pay account balances by credit card (uses the same access method to the clearing house as the IVR ASSIST application)

Receive housing and financial aid information

Receive academic calendar and graduation information

Database System

Accesses Student Records System (SRS) Database which is maintained by that application. The SRS Database uses ADABAS.

Development Language

Java

Sharing

 

Future

This application currently uses the same access methods to the mainframe as the IVR version of ASSIST. The application will be converted to use the Entire Broker product (from SAGA Software) to access the mainframe-based data. This application is included in the project "AD2003: Web enable administrative systems" in the Biennial Operating Plan. Depending upon the outcome of the investigation of commercial student records systems, this application may be superseded if a new system is selected.

Application Name

Admissions Management System (AMS)

Application Type

Mainframe-based application using OLTP and batch techniques.

Application Description

This application maintains the AMS Database which contains basic information for all categories of applicants to the University. The application includes provisions for communicating with students regarding missing information, etc. Information maintained is electronically passed to the SRS (Student Records System) when admitted applicants actually register to become students.

Database System

ADABAS

Development Language

COBOL, NATURAL

Sharing

 

Future

There are plans to have this application collect and store additional information about transfer work. Depending upon the outcome of the investigation of commercial student records systems, this application may be superseded if a new system is selected.

Application Name

Admissions Prospect System (Undergraduate)

Application Type

Unix-Based Transaction Processing System

Application Description

Collects, maintains, and reports information about prospective applicants. This information potentially comes from a variety of sources, including Admissions Office staff recruiting visits to high schools and junior/community colleges. Student information accompanying admissions exam scores processed on the mainframe is also downloaded to the Prospect System, creating prospect records. The system produces personalized reply letters and labels for mailing requested materials, including Catalogs and Schedules of Classes. If the prospect has requested an application for housing, financial aid, or information from a specific school or college, mailing labels are forwarded to the appropriate unit for mailing the requested materials. Periodically the prospect records contained in the Prospect System are matched against the records contained in the Admissions Management System (AMS) on the administrative mainframe. Prospect records which contain essential identifying information can create a new record in the mainframe based AMS if no record exists there for the person. For matching records, information from AMS is added to the Prospect System to provide a more complete and current record. The Prospect System supports and tracks follow­up contacts with prospective students over an extended period of time, in some cases for years, depending upon an individual's classification, or year in school, at the time of initial inquiry into UNT. The Prospect System was substantially enhanced in 1994 to support electronic transmittal of student information requests to Printing Services via the (then) new Recruitment Materials Distribution System (RMDS).

Database System

 

Development Language

SPEED II (4GL Application Development Product from APPX Software, Inc., Release 06.01.07)

Sharing

Information from this system is passed to the Recruitment Materials Distribution System (RMDS).

Future

We plan to phase out this system, which is based on aging technology and replace it and the companion Admissions Prospect System (Graduate) with a single system which will accommodate undergraduate, graduate, and international prospects. Depending upon the outcome of the investigation of commercial student records systems, this application may be superseded if a new system is selected.

Application Name

Admissions Prospect System (Graduate)

Application Type

Client Server

Application Description

[Note: This application serves the Graduate School and accomplishes essentially the same functions for that area as the companion Admission Prospect System (Undergraduate) System performs for the Undergraduate Admissions Department.] This system collects, maintains, and reports information about prospective applicants. This information comes from a variety of sources, including Admissions Office staff recruiting visits to other universities and to business education fairs. The system produces personalized reply letters and labels for mailing requested materials, including Catalogs and Schedules of Classes. If the prospect has requested an application for housing, financial aid, or information from a specific school or college, comma-delimited data files are forwarded to the appropriate unit for mailing the requested materials. The Prospect System supports and tracks follow-up contacts with prospective students over an extended period of time, in some cases for years, depending on an individual’s classification, or year in school, at the time of initial inquiry into UNT. The system supports electronic transmittal of student information requests to Printing Services via the Recruitment Materials Distribution System (RMDS).

Database System

Oracle

Development Language

Visual Basic 6.0

Sharing

Information from this system is passed to the Recruitment Materials Distribution System (RMDS).

Future

We plan to either replace this system and the companion Admissions Prospect System (Undergraduate) with a single system which will accommodate Undergraduate, Graduate, and International Admissions or modify or rewrite this application such that it will accommodate those areas. Depending upon the outcome of the investigation of commercial student records systems, this application may be superseded if a new system is selected.

Application Name

Advancement / Development Information System (ADIS)

Application Type

Mainframe-based application using OLTP and batch techniques.

Application Description

This application collects, maintains, and reports detail information about all UNT alumni and other specific donors and supplies information for various solicitation campaigns.

Database System

ADABAS

Development Language

NATURAL, COBOL

Sharing

 

Future

No major modifications are planned to this application during this planning period.

Application Name

Automated Purchasing and Accounts Payable (APAP) System

Application Type

Client Server Financial System

Application Description

When fully completed, this application will support electronic entry, routing, approval and management of purchases from the requisition stage through to final payment to vendors. System will also support other types of account payable activities including travel vouchers, inter-departmental orders and payments, etc. Functionality currently available in production includes creation of payment vouchers for all types of payments currently handled by UNT’s Payment Services area.

Database System

Oracle

Development Language

Uniface

Sharing

Information is shared with GLAS, another UNT system.

Future

Future plans include completion of purchasing front-end to include entry, routing, approval and management of purchase orders and development of system for inter-departmental orders, travel, and other types of accounts payable. This application is included in the project listed as "Automated Purchasing-Accounts Payable (APAP)" in the Biennial Operating Plan.

Application Name

Billing / Receivables System (BRS)

Application Type

Mainframe-based financial application using OLTP and batch techniques.

Application Description

This application collects, maintains, and reports on student accounts receivable information in the BRS Database. Information is electronically exchanged with the Student Records System (SRS) and the Financial Aid Management System (FAMS).

Database System

ADABAS.

Development Language

COBOL, NATURAL

Sharing

 

Future

Planned modifications to this application include providing access to selected functions from the Web.

Application Name

Capital Equipment Account Tracking System (CEATS)

Application Type

Mainframe-based application using OLTP and batch techniques.

Application Description

This application collects, maintains, and reports on the detail property information about individual items of capital / controlled equipment maintained in the CEATS Database. Information maintained includes purchase date and cost, current location, general ledger data, acquiring account, person with inventory responsibility for the equipment, etc. System is interfaced to the State Comptroller's State Property Accounting (SPA) to provide that system with data mandated by the State Comptroller.

Database System

ADABAS

Development Language

NATURAL, COBOL

Sharing

 

Future

Changes will be required to this application and to the CEATS database to support GASB rule changes. Examples include a requirement to account for depreciation of capital assets.

Application Name

Career Opportunities Center Service Job Line

Application Type

Interactive Voice Response

Application Description

This interactive voice response system allows anyone who has registered with the Career Opportunities Center (COC) Office to call in and hear descriptions of job offerings in various categories. Employers first call COC and describe job openings. COC staff record the information about job offerings and categorize jobs into four major categories. These are Business, Education, Higher Education, and Other. Jobs are further categorized by geographic area and specialty. A "Business" job, for example, might be further categorized as accounting, retail, marketing, etc. Prospective graduates who register with COC are allowed to call the job line interactive voice response system and hear information about job offerings. They can then call COC if they wish to schedule interviews with prospective employers. We hope to eventually expand the system's functionality so that prospective graduates can schedule interviews directly without calling COC. The job information and prospective graduation information is maintained on a file server in Student Affairs. This interactive voice response application receives information from that system as needed.

Database System

 

Development Language

C, Write-1

Sharing

 

Future

No major modifications are planned to this application during this planning period.

Application Name

Degree Audit Reporting System (DARS)

Application Type

Mainframe-based application using OLTP and batch techniques.

Application Description

DARS or the audit report is designed to compare a student's academic work - at any point in the student's career - with the requirements of an institution's academic program or programs, and to prepare a comprehensive report detailing the student's progress toward meeting those requirements. The report may be produced to report all satisfied requirements first following by any unsatisfied requirements, vice versa, or to report using several other run options.

Audit reports may be prepared in either a "batch" or "on-line" mode. Batch reports are usually prepared for large numbers of students as might be needed prior to student registration, or for all degree candidates, or for a particular major or college.

On-line reports are typically prepared to handle individual student advising needs, to determine where a student would stand in some other academic program, or in using another catalog year/term, ("what if" type questions), or to confirm the affects of some academic program "exception" action for a student.

The Transfer Equivalency System (TRES), a subsystem of DARS, provides automated support for determining the transferability of course work from other institutions (whose courses have been evaluated) to determine the UNT equivalent. Currently this includes all community/junior colleges in Texas and selected senior-level universities. Classes from other institutions for which course equivalencies have been established can be evaluated to determine the applicability of those courses toward a UNT degree. Course data for individual students are either input through a computer terminal or received electronically over the AHE Electronic Transcript Network. Transcripts/reports are then produced showing the equivalency of the course work.

Database System

ADABAS

Development Language

COBOL, NATURAL

Sharing

Transfer equivalency reports are provided to area community colleges.

Future

Modifications planned for this application during this planning period include:

· Provide remote access to DARS functions via secure WWW interface

· Provide capability to allow students to request an audit and have results delivered via e-mail

· Implement a subset of DARS functions (primarily advising-related functions) from the vendor's Client/Server package

Application Name

Development Query System

Application Type

Data Warehouse

Application Description

This application periodically selects data from the Advancement / Development System and downloads it to an ORACLE database file on a database server attached to the campus network. This database is made available to Advancement personnel, College Development Officers, and others, as deemed appropriate by the Advancement Office administrators, who use Esperant or other PC-based end-user oriented query and reporting software tools to run ad-hoc queries and produce reports as needed.

Database System

ADABAS

Development Language

Crystal Reports, other PC-based query tools.

Sharing

 

Future

No major modifications are planned to this application during this planning period.

Application Name

EC Image Imaging System

Application Type

Imaging

Application Description

This application allows for scanning, filing, retrieving, viewing, and printing of document images on laser optical filing media. It also provides the capability to fax images. This system is currently being used by the Controller's Office to file backup documentation relating to claims disbursements made to vendors. Over 800,000 document images are currently maintained in the system, consisting of vouchers and related documents processed beginning September 1, 1990 (for fiscal year 1991).

Database System

Oracle

Development Language

C++ and Centura SQLWindows

Sharing

 

Future

Other than expanding its usage, no major modifications are planned to this application during this planning period.

Application Name

Facilities Inventory System

Application Type

Mainframe-based application using OLTP and batch techniques.

Application Description

This application collects, maintains, and reports on information about the University's buildings and room.

Database System

This application uses information stored in the SRS database, which is stored in ADABAS.

Development Language

COBOL, NATURAL

Sharing

 

Future

No major modifications are planned to this application during this planning period

Application Name

Financial Aid Management System (FAMS)

Application Type

Mainframe-based financial application using OLTP and batch techniques.

Application Description

This application collects, maintains, and reports on information stored in the FAMS Database. The application supports financial aid awarding, packaging, student notification, and BRS system feed functions.

Database System

ADABAS.

Development Language

COBOL

Sharing

&