Student Affairs Information Technology (SAIT) monitors some web applications in real time using a product called New Relic. New Relic is a service that tracks an enormous amount of information useful to both developers and customers. The information helps SAIT diagnose problems, improve application performance and develop our products. The statistics you see here are only a small slice of the New Relic data. Generally speaking, we post information relevant to the customers we code for, including application uptime, average browser response time, Apdex score and a host of other items.

Each application monitored by New Relic shows a different set of performance graphs. Each graph has a title that explains what it measures; most of the graph legends are clickable, allowing you to isolate different parameters.

Enough talk — let’s show you some numbers! Select the links below to view application statistics.

Campus Quality Fee


Student Access and Accomodation System (SAAS)

Select the following links to view version history.

Campus Quality Fee

NCOD Service Request App


Student Access and Accommodation System (SAAS)

Testing Center Registration App

What is Apdex?

Apdex, or application performance index, is a standard method for reporting and comparing the performance of software applications. The method converts many measurements in to one number on a uniform scale of zero to one, with zero meaning none of the users are satisfied and one meaning all of the users are satisfied. The resulting Apdex score is a numerical measurement of user satisfaction with the performance of applications.

The Apdex formula is the number of satisfied samples plus half of the tolerating samples plus none of the frustrated samples, divided by all the samples.

Apdext = satisfied count + (tolerated count / 2) / total samples

It is easy to see how the ratio is always directly related to users' perceptions of satisfactory application responsiveness. For more information about Apdex scores, read the technical specification.

Source: Wikipedia

Version Numbering

SAIT uses version numbers to track features and bug fixes in our Web applications; some of our Web applications include a version number in the page footer. Each digit has a specific meaning. For example, a version number example might look like 1.2.3.

The number one signifies a major release, with dramatic changes to functionality or look and feel. The number two signifies a minor release, with noticeable change to functionality or look and feel. The number three signifies a hotfix, or immediate bug fixes. Number three resets to zero on a subsequent minor release.


  1. In consultation with the customer, a list of features and bugs is established for the week.
  1. The list of features and bugs is grouped together and given a version number, like 1.1.0.
  2. Features and bugs in a version number may only be removed in the following cases:

a. If an item has not been worked on and the customer has consulted with SAIT, the customer may remove an item if it should not be in the next release. The customer is obligated to record the removal in Redmine; a phone call or email notification should also be placed to inform SAIT.

b. In consultation with the customer, SAIT may remove an item if there is not enough time to get it ready for release. SAIT is obligated to record this removal in Redmine; a phone call or email notification should also be placed to inform the customer.


  1. SAIT holds a change management meeting via phone call or Google Hangout with our customers every week at an agreed-upon time.
  2. The app version being worked on is reviewed to ensure all features and bugs have been completed to the customer's satisfaction.
  3. The app version being worked on is either held back or approved for release during the following week’s regular release window.

The approved version is pushed to production the following Wednesday night during SAIT's regular release window, 10 p.m.-midnight.