 |
 |
 |
|
|
|
|
 |
Adhesion - Web based IT management software.
|
 |
|
| |
 |
Adhesion is a web-based asset manager that allows you to track work orders, manage parts inventory, and predict when you will need to order parts for scheduled maintenance. It is perfect for I.T. organizations to manage PCs across the company or for manufacturing companies to manage equipment. Works with any combination of our products using IntegrateNow technology.For a Limited Time: Enter "save25now" in the promotional code field on the checkout page to save 25% on your order today!
|
|
 |
 |
| Price $ 89.00 |
 |
|
|
|
|
|
|
Features Specific To This Product
|
|
|
| |
Equipment and Parts |
| |
• Management screens provided to add, edit and list equipment that your company needs to track and service. |
| |
• Equipment fields: name, code, description, vendor, model number, serial, asset, date in service, cost, etc. |
| |
• Extra fields for storing hazardous waste, installation, or calibration information on equipment provided. |
| |
• Parts reference supplied that displays all parts required for a piece of equipment. |
| |
• Part management section for adding, editing, deleting parts, and listing all parts in the system/inventory. |
| |
• In-stock, in-reserve, on-order, and on-back-order quantity fields provided for parts inventory control. |
| |
• Parts fields: name, family, code, descr., vendor, vendor part #, internal part #, cost, warehouse/row/bin, etc. |
| |
Work Orders |
| |
• Work order listing that is tailored to the person logged in, allowing view only, approvals, or changes. |
| |
• Work order fields: open date, priority, type, status, equipment, requestor, problem, solution, dept., prime, etc. |
| |
• Work orders can also have part line items that were necessary to complete the job. |
| |
Preventative Maintenance and Rebuild Schedules |
| |
• Schedule types are typically prev. maintenance and rebuild but others can be added through schedule section. |
| |
• Schedules are like a calendar, and roll forwards and backwards for as many months as necessary. |
| |
• Schedules can be a repeating daily or weekly schedule, as well as a rolling monthly calendar with start date. |
| |
• Monthly schedules offer drill-down capabilities for weekly and daily views. |
| |
• Schedule tasks can be assigned every 1/2 hour, for 24 hours, and may have multiple resources responsible. |
| |
• Task fields: type, equipment name, start/end times, description, instructions, priority, tools, supplies, parts, etc. |
| |
• Parts threshold report that will signal in red if any part quantity falls below set threshold. |
| |
• JIT (Just-In-Time) parts inventory alert & report that will signal when to order parts for scheduled maintenance. |
| |
Administration Application |
| |
• Schedule manager included to add, update, or archive maintenance schedules. |
| |
• Separate archived schedules listing provided to retain schedules for use at a later date. |
| |
• Contact management screens for adding/editing contacts, accounts, passwords, & security levels. |
| |
• Company management screens supplied to add/edit companies (that own projects and contacts). |
| |
• Security group management screens for granting contacts access to schedules. |
| |
Security and Restriction Controls |
| |
• Separate main and admin applications to protect/control: contacts, companies, schedules, work orders, etc. |
| |
• Schedule access is restricted with the use of security groups (for managers, technicians, operators). |
| |
• Each technician/operator/employee will be able to see certain schedules & any work orders assigned to them. |
| |
• Prime persons can be assigned for: parts inventory control, work order add/edit, & work order approvals. |
| |
• The parts inventory alert is configurable to be shown for the parts inventory prime, all persons, or not at all. |
|
|
|
|
|
| |
• Centralized database design that includes core, and sub-core tables ... see IntegrateNow. |
| |
• All products can be used independently or together, forming an application suite tailored for your business. |
| |
• Normalized database design to avoid redundant data storage and maximize retrieval efficiency. |
| |
• Integration with legacy enterprise resource planning systems is made easy due to pre-planned data mapping. |
| |
• Business entities (companies, contacts, projects, etc.) are stored with numeric system identifiers. |
| |
• Exclusive usage of stored procedures to perform all database calls; except some report generators. |
|
|
|
|
|
Security / Scalability / Installation
|
|
|
| |
• Easy installation (FTP the ASP files up to your server, and run the database script). |
| |
• Products use a "keyed-cookie" that has a name and a key for increased security and data organization. |
| |
• "Logout" feature to end a session when a user has completed their work. |
| |
• User credentials verified on every page of the application, not just on the login page. |
| |
• Exclusive grouped security model that is database driven and restricts access for teams, projects, etc. |
| |
• Built in security levels that control a user's access to important or sensitive information, in every application. |
| |
• Global use of stored procedures put sensitive SQL commands in a strict and hidden environment. |
| |
• Applications keep the use of the querystring to a minimum, and utilize cookie values where possible. |
| |
• Applications are designed with scalable work flows that can be altered to handle almost any business. |
| |
• Double Integers are used to store business entity id's to enable massive amounts of data. |
| |
• Separate bill-to and ship-to addresses provide the needed diversity for invoicing and shipping. |
|
|
|
|
|
Configurations and Customizations
|
|
|
| |
• Canned configurations included for quick customizations, and source code for more in depth changes. |
| |
• Include files used for site headers/footers, common functions, etc., so changes can be reflected globally. |
| |
• Folders, stored procedures and image files are named using an alphabetically sortable format. |
| |
• Comments included in every source code paragraph, making it easy to understand and change. |
| |
• In-application security configurations enabling approval primes, task hours/billing approvals, etc. |
|
|
|
|
|
| |
• International symbols and icons used to speed navigation in: tab toolbars, sub-menus, summary listings, etc. |
| |
• Utilization of cascading style sheets (CSS) to standardize look and feel of text and hyperlinks. |
| |
• Tab oriented graphical user interface (GUI) to enable quick and familiar navigation. |
| |
• Application section sub-menus make getting around easy and productive. |
| |
• Placement of entity add, edit, delete, and listing links are congruent throughout applications. |
| |
• Relative screen sizing within browser to maximize window usage. |
| |
• Browser compatible for various versions of Internet Explorer (IE), FireFox, Safari, and Chrome. |
|
|
|
|
|
|
|
|
 |
|
 |
|
