Frequently Asked Questions

" The Power of the Button" is achieved using the RLJL Language. A Button Object can be programmed using the RLJL Language to allow users to execute commands to perform tasks on peripheral devices without having direct access to the peripheral devices. The user simply clicks the button that executes the object to perform that particular task.

Button Objects are the heart of the RLJL Suite. Button Objects use the RLJL Language to insert variables (telephone number, line equipment, port assignment, etc.) automatically at the required times. Button Objects can be used to create user forms, input or message boxes to gather and display information.

Yes. All users with the correct security level can create, edit, or update any of the Button Objects.

In a typical telecommunications environment, there are a number of systems that require administration to be done through a serial line interface. Each peripheral has its own set of syntax or commands through which administration and maintenance are done. The RLJL Language allows the CO personnel to build Button Objects using simple logic and the syntax of the switch or peripheral to create a graphical, centralized interface so simple administrative repetitive tasks can be accomplished by less skilled employees allowing the more skilled personnel to spend more time on other tasks. The RLJL Suite allows you to maximize resources and consolidate your broad range of peripherals into one easy to manage communications network.

Yes. The RLJL Suite will not only save you money, in some cases it will make you money! The RLJL Suite can save you money by decreasing redundant tasks, eliminating double-entry, and allowing you to spread complex tasks among several employees. A great example of this is cutoffs; by automating cutoffs (400 - 600 lines per hour) the personnel usually devoted to this task simply have time for other responsibilities. The RLJL Suite can increase revenue by revealing inconsistencies between the switch and billing systems through Button Objects programmed to perform audits between the two systems.

No one can communicate with the RLJL Suite software unless they have its mated client. Mated clients provide complete security through use of proprietary 168-bit encryption. This feature creates total security in a LAN / WAN environment. The administrator has the ability to control access for mated clients through user profiles. Security levels range from total access to no interaction abilities except through Button Objects (created by the central office engineers).

It will run on Windows 9X, NT, 2000, ME, and XP platforms.

Yes. It will support TTY, ANSI, VT 52/100/220/320/220 7 bit/320 7 bit, HTML, TVI, Wyse, and DMS-ENet.

Yes. It has the capability to schedule Button Object execution daily, weekly, monthly or as a one-time event.

The RLJL Suite was designed with open architecture and flexibility as a primary consideration. Our desire was to create a system that would meet the needs of every unique network. As a result of this power and flexibility, no limitations have been found and our users continually find new uses for the RLJL Suite.

The RLJL (Reduced Logic Job Linking) Language is an intuitive, object-based language for programming Button Objects. This propriety language contains numerous imbedded functions that allow the user to easily create and edit customized Button Objects. The beauty of the language is that as CO equipment is upgraded the CO personnel can implement the changes without further assistance from DSC.

The ECS is the controller for all other programs in the RLJL Suite. It provides access to network peripherals according to security levels created by the central office manager. A technician can build a Button Set for each peripheral that can be used by any non-technical person in the company. For example, the technician can build a Button Set for a switching system such as a DCO, DMS, EWSD, etc. that will add new service. Then a customer service representative can click on this button from their workstation and populate this form. Once this form is completed, the ECS will send the syntax in the Button Object to the switch, which will activate the service. This takes a redundant task off of the technician's workload and allows him to concentrate on other matters. This same procedure can be applied to any number of peripherals in the network.

It provides batched provisioning of network elements, transparent to the end-user. This allows network elements that have one port to process many jobs from different users.

Real-time provisioning gives direct access to the management port of a network device. This is critical in applications such as troubleshooting, complex provisioning and queries where information is needed immediately. Batched provisioning allows you to queue all requests and execute them in a predetermined fashion (e.g., removal before installation). The batched process can be used to execute commands at off peak times to conserve port access and processing capability. The RLJL Suite supports both types of provisioning applications.

Unlimited

Unlimited. Peripheral connections are done via ports through the ECS.

Absolutely. ECS and SIS can be expanded to meet your network's needs.

Port Queuing allows for efficient use of ComObjects. In the event that a ComObject is busy when a user requests access to it, the user is then placed in queue (first in first out architecture) and he will obtain the port as soon as it becomes free. When used in conjunction with Port Takeover, a user can be placed in queue by requesting access providing that the requesting user has a higher security level. Once the requesting user has completed the task using the ComObject, the user is then removed from queue and the job will resume.

The SIS adds to the RLJL Suite's flexibility. It is designed to integrate with any service order and billing system software. The SIS appears to the billing system as a printer on the network. The SIS reads the printed service order, pulls data from user defined areas of the printed order, performs the requested transaction in the correct peripheral, and then sends the completed action to the billing system software for completion. This eliminates the possibility of entry errors by flowing the data seamlessly from the CSR to the switch and then to the billing system.

The ASN system uses the RLJL technology that utilizes "The Power of the Button" to monitor alarm activity reported to our alarm controllers. ASN takes action on any alarms detected based on the customized instructions the user establishes. ASN can detect alarms using SNMP traps, DAC Logging, or contact closures. ASN will call, e-mail or page with text or voice messages to notify personnel of alarms or run buttons to automatically handle the alarms. ASN also uses TAPI as a means of alarm handling using voice and keypad responses to activate buttons.

ASN is capable of being scaled to monitor an unlimited number of alarms from an unlimited number of locations.