IRM is a Web-based asset tracking and help desk/work request system built for IT departments and help desks. It keeps detailed information about each computer, as well as a complete history of work requests. It keeps track of detailed computer information such as CPU type/speed, amount of RAM, Hard Drive Size, serial numbers, etc. The system includes the ability to track networking hardware and any type of software. Also included is support for email notification of both users and technicians, and some support for monitoring computer systems via SNMP.
phpMyAdmin is a tool intended to handle the administration of MySQL over the Web. It can create, rename, and drop databases, create/drop/alter tables, delete/edit/add fields, execute any SQL statement, manage keys on fields, create dumps of tables and databases, export/import CSV data, and administrate one single database and multiple MySQL servers.
The Machine Inventory Database (MID) is a Perl-based CGI interface to manage the machines on and off your network, both from the IP assignment perspective and the asset-tracking perspective. On top of acting as a frontend to a handful of MySQL tables, it handles IP assignment and acts as a frontend to the configuration files for BIND, YP, and DHCPD to reduce the chance for typos in the configuration files which tend to bring down service.
Zaval Database Front-end is a light and functional Web-based front-end to any database for which you have JDBC drivers. It allows raw SQL code execution and is limited only by the extent of the database's SQL support. It supports multiple query execution, alternate languages, and more.
OpenTicket functions as an incident manager, handling trouble-tickets and providing a mechanism for the resolution of all incidents. More specifically, openTicket serves as the Service Desk interface and handles the life cycle of incidents and service requests. The focus of openTicket is speed and efficiency. Unlike other call-tracking tools which offer a plethora of text fields, pull-down menus, and associated data, openTicket's interface is stripped down as much as possible without sacrificing key information. The benchmark used to determine efficiency is the 30-second test. If you know the user's name and you know the issue, it should take no longer than 30 seconds from the moment you begin looking up the user to the moment the ticket (including all relevant information) has been created and entered into the database.