support  |  log in
 
features  >  WORK ORDERS & TROUBLES

 

reduce the madness, simplify your network

 

> Request a Demo

Work Orders & Troubles

If you have a big network, chances are your organization is made up of several work centers, each playing a key role in getting daily tasks done. The cairs.net Orders & Troubles system brings your teams together, connected through strategically planned work flows, enabling each team member to focus on their unique mission. Cairs.net enables you to build workflow templates that address both static and irregular processes ensuring that you can respond to both equally. When unanticipated work is required, pull in additional work centers on the fly to get the job done. The Orders & Trouble system strategically connects your work centers to not only each other, but also your network and database for MAC work, network configuration changes, inventory changes, and billing.  

 

Orders & Troubles

Through the Orders & Troubles system, each work order and trouble ticket is connected to key records in the cairs.net database, set devices, circuits, subscribers, cell phones, cabling and connectivity routes, equipment and services, and accounting. Each work flow contains three elements; time frames, work centers, and data components (sets, circuits, cell phone, etc.). The work flow is organized into an itinerary that tickets follow from start to finish. Each work center is tagged to complete the tasks connected to their mission. Multiple work centers can be in each time frame, allowing for multiple people from different work centers to work on the same order at one time. As each work center completes their work, the ticket progresses to the next group of work centers.

As you know things do not always go to plan, cairs.net allows your work orders or trouble tickets to be held, rejected or canceled allowing the work to be paused and restarted without affecting your completion statistics.

Cairs.net allows users a variety of ways to view the work orders they are working on. They can view all work orders, my work center orders, and my orders, in addition to filtering tickets by data values like a building, or organization.

Cairs.net also provides a complete history of every work order and trouble ticket processed through the system. Every action that your users perform on the ticket is recorded and visible before and after the work is completed.

Sometimes a work order is cancelled or closed prematurely, ciars.net provides a reopen option. In a simple click, your ticket is reopened and returned and active work center.

  • Design your work flows to mimic how you do business
  • Send a work order to a certain person within the next work center
  • Each work order is required to be assigned to a site
  • All configured components are visible within one pane through tab viewing
  • You can assign equipment or services to the work order for billing purposes
  • Work order attachments allow you to bring more information into the work flow to accurately complete the work flow
  • Hold, reject and/or cancel a work order
  • For each work order, you can make a work center optional
  • View each action performed on the work order within the order log
  • Once a work order is created a history is created
  • Work Order history is available within each work order as well as its own menu option
  • The history screen and the work order screen are the same so there is no confusion on where to find the information
  • View the information for each data component
  • Reopen a work order whether it has been closed or canceled
  • View the work order statistics within one pane: open date, close date, last opened by, etc.

Work Flow Management

Maintaining the way you currently do business is very important to us. Within work flow, you customize cairs.net to match your unique business processes. Building a work flow is easy. First you name it and select your work centers. Then you organize the work centers into time frames, which controls when work centers access a ticket. Next you select the fields and data components that each work center will update. Cairs.net organizes your primary records into five data components: Set Device, Cell Phones, Circuit, Account, and Subscribers. Data components reduce the time and challenge of creating a work flow because it enables you to quickly assign work center access to a record and all of its fields while cairs.net draws on your normal security profiles to keep track of which fields on the data component that your users are responsible for updating. Supporting data like connectivity (terminals, pairs, strains, jacks), switch data (number plans, switch ports, and features), and inventory (equipment and services), are accessed through each data component. As users update their fields on the data component (like phone number and switch port on a set) the ticket is sent onto the next stop in the work flow to update the next set of info.

On a side note, we have a built in measure to insure that information is not lost in the process. When a user opens a work order, they have control, when another user opens the order they receive a message indicating that the order is under the control of another user and the information they enter may be lost. 

  • Create all your work centers before you build your work flows
  • Create custom fields that may not be available within the data components
  • For each work order, designate how many days are allowed for completion
  • For each work center, you designate whether the work center is an optional stop, meaning that the entire center can be ignored for the work flow
  • You determine if the data component is required
  • Create work order templates that allow you to reuse the same set of data components and custom fields

Subscriber Portal

The cairs.net Subscriber Portal provides your customers a browser based interfaces to submit work order and trouble ticket requests. In cairs.net you create request and trouble packages which are offered to your customer. You determine the fields they fill out, the packages, and what equipment, services, and or charges are associated with the request, so your customers know the upfront cost.

You can also determine if request needs approval from either a Telephone Control Officer (TCO) or Resource Manager (RM) before it gets processed. When approvals are required, the TCO or RM will receive a notification to review the request. Once approved, the request is transferred to an order ticket and is sent through the desired work flow.

  • Cairs.net administrators determine what requests can be made through the Subscriber Portal
  • You determine what equipment and/or services are included with each request
  • You have different packages available for your different sites, organizations or subscriber types
  • You can require that each package be approved by a TCO or RM before being submitted into cairs.net
  • If the request is a new telephone, you determine the set type and template

User Interface Features

  • Easy to user Office 2007 style interface.
  • View and search for sets by active features, directory info, primary, multiplies, CS/PBX, and location.
  • Easily find data through the Instant Search Control by field and query type (contains, equal to, less or equal, etc…).
  • Customize your interfaces by controlling field visibility, field name, field order, and page layout.
  • Create profiles for user groups specific for their needs.

Scalability

Requirements

    • Server OS - MS Server 2003 or 2008, IIS 6.0, .NET Framework 2.0, MS SQL 2005 or 2008, 1.5 GHz, 3.0 MB RAM, 100 Gig Hard Drive.
    • Work Station – Windows XP, Vista, or 7, 2.0 GHz, 4.0 MB RAM.
 
© Unique Communications Solutions Inc. 2011
);