MiBAS 12 Dimetra User Manual

Motorola confidential proprietary information
MiBAS
Motorola Integrated Billing

and Administration System
Motorola integrated Billing & Administration

System
User Manual
Version 12.0
Revision 2, October 2005
Copyright Notice
(c) 1996-2004, MOTOROLA COMMUNICATIONS ISRAEL LTD. All rights reserved. No part of this file
may be reproduced or transmitted in any form or means (including photocopying) without prior
permission of Motorola Communications Israel Ltd.
Proprietary Information Notice

The information contained in this document is MOTOROLA PROPRIETARY INFORMATION. The
unauthorized distribution of this information to any individual or organization not employed by
MOTOROLA is strictly prohibited. Any person receiving this document will be held strictly
accountable for the discretion and judgment associated with the use of this information.
Non-Disclosure Statement
PLEASE READ THIS NON-DISCLOSURE STATEMENT FIRST
This file contains confidential proprietary information of Motorola. It should only be opened after
you have read and agreed to be bound to the terms of this Non-Disclosure Statement. By reading
this file, you agree to be bound to the terms herewith. If you do not agree to the terms of this NonDisclosure Statement, promptly return this unopened file to Motorola's representative.
This is a binding agreement between you, for yourself and for the entity in which you are employed
(collectively: the ENTITY), and MOTOROLA COMMUNICATIONS ISRAEL LTD. of 3 Kremenetzky St.
Tel-Aviv 67899, Israel, for itself and for other participating MOTOROLA ISRAEL LTD. subsidiary
companies (collectively: "MOTOROLA").
In consideration of the mutual covenants and conditions set forth herein it is agreed as follows:
1.
1.1
CONFIDENTIAL PROPRIETARY INFORMATION is defined as meaning all business,
commercial, technical and any other information identified as or relating to the (MiBAS)
SOFTWARE (The PRODUCT) contained herein in this file or which is disclosed by MOTOROLA to
ENTITY in oral, visual, written, graphic, machine recognizable and/or sample and/or other tangible
form and all other information marked by MOTOROLA with a "confidential" "proprietary", or similar
legend.
1.2
Confidential Proprietary Information disclosed hereunder may only be used according to
the terms of this Agreement signed between the parties on the Effective Date, and as will be
instructed by MOTOROLA from time to time.
1.3
No License, express, implied or otherwise in this Agreement is granted to the ENTITY other
than the use of the Confidential Proprietary Information for evaluation purposes only, in the
manner and to the extent authorized by this Agreement.
2.
The ENTITY agrees that all Confidential Proprietary Information is and shall at all times
remain the property of MOTOROLA, who shall not be obligated to disclose any particular information
to ENTITY. No use of such information is permitted except as otherwise provided herein and no
grant under any MOTOROLA Intellectual Property rights is hereby given or intended.
3.
The ENTITY agrees that for a period of five (5) years following the Effective Date of this
Agreement, the ENTITY will maintain the confidentiality of the furnished MOTOROLAs Confidential
Proprietary Information and not disclose such Information to any third party, except as authorized
by MOTOROLA in writing. Notwithstanding the provisions in this section, the above term of five (5)
years shall be extended indefinitely for Confidential Proprietary Information which is clearly marked
and/or identified by the Disclosing Party with a "confidential" "proprietary", or similar legend, until
such time as the Confidential Proprietary Information no longer constitutes Confidential Proprietary
Information, all subject to the provisions of this Agreement. The ENTITY further agrees to keep
confidential the existence of this Agreement, any prospects of business with MOTOROLA, and that it
is meeting with, or receiving such Information from MOTOROLA.
4.
The ENTITY agrees to restrict disclosure of Confidential Proprietary Information to only
those employees who have a "need to know" and must be directly involved in the use of the
Confidential Information and use the same degree of care as for its own information of like
importance but at least reasonable care in safeguarding against disclosure of Confidential
Proprietary Information, and shall not be exported, directly or indirectly, to any country without the
prior written consent of MOTOROLA.
5.
Disclosures made by MOTOROLA which can be demonstrated to be in the public domain
shall not be construed as Confidential Proprietary Information.
6.
The ENTITY agrees to immediately return to MOTOROLA, upon its request all Confidential
Proprietary Information received and any copies made thereof of all devices, graphic, writings and
all information in all tangible forms, containing any of the Confidential Proprietary Information
referred to in this Agreement.
7.
The ENTITY agrees to refrain from making any use of the Confidential Proprietary
Information and that it will not compete or be engaged, directly or indirectly, in any activity which
may jeopardize or affect MOTOROLAs interest pertaining to the PRODUCT.
8.
It is hereby declared and agreed that this Agreement does not, in any way, establish any
principal/agent employee and/or ownership relationship between the parties hereto.
9.
This Agreement shall not be construed as a Teaming, Joint Venture or other such
arrangement; rather, the parties hereto expressly agree that this Agreement is for the purpose of
protecting Confidential Proprietary Information of MOTOROLA.
10.
This Agreement and the rights and obligations hereunder may not be transferred or
assigned by ENTITY, without the prior, written consent of MOTOROLA.
11.
This Agreement contains the entire understanding between the parties relative to the
protection of Confidential Proprietary Information and supersedes all prior and collateral
communication, reports and understanding between the parties in respect thereto. No change,
modification, revision or addition to any provision hereof shall be binding unless in writing and
signed by authorized representatives of both Parties
REVISION HISTORY
Revision
Date
Comments
Author
October 2005
First draft
M Sharon
October 2005
Edits
M Diamant
Table of Contents
Introduction.............................................................................................................................8
Terms and Concepts..............................................................................................................................8
Accessing and Exiting MiBAS..............................................................................................................9
Accessing MiBAS................................................................................................................................9
Exiting MiBAS..................................................................................................................................10
Operating MiBAS.................................................................................................................11
Accessing MiBAS.................................................................................................................................11
Changing Your E-Mail Address.........................................................................................................11
Exiting MiBAS.....................................................................................................................................11
The Navigation System.......................................................................................................................12
Main Navigation Tools.....................................................................................................................12
Quick Navigation.............................................................................................................................12
The Top Menu...................................................................................................................................13
Disabled Menu Commands............................................................................................................13
Accessible Data....................................................................................................................................14
Search Tools.........................................................................................................................................14
Browsing...........................................................................................................................................15
Using the Search Bar........................................................................................................................15
Using the Local Search Tool............................................................................................................16
The Status Bar......................................................................................................................................17
Using Effective From/Until Dates.....................................................................................................17
The Effective Date................................................................................................................................19
Available and Attached Values..........................................................................................................19
Data Entry............................................................................................................................................19
Modifying, Deleting, Reporting and Auditing Records.................................................................20
Showing History..................................................................................................................................21
Using the Floating Calendar..............................................................................................................22
Printing Inquiry Results and Other Data.........................................................................................22
Provisioning Administration.............................................................................................23
One-Time Tasks...................................................................................................................................23
Security Groups................................................................................................................................23
Frequencies and Channels..............................................................................................................24
Radio and Fleet Administrative Group Definitions.....................................................................26
Call Route..........................................................................................................................................28
Radio Roles.......................................................................................................................................29
Identity Types...................................................................................................................................29
Ongoing Tasks.....................................................................................................................................30
Profiles...............................................................................................................................................30
Selecting the Active Administrative Group...................................................................................33
Customers..............................................................................................................................35
Adding and Configuring Customers................................................................................................35
Customer Main Details....................................................................................................................35
Customer Security Groups..............................................................................................................37
Accessing Configured Customers.....................................................................................................37
Table of Contents | 5
Modifying Details of Configured Customers...................................................................................38

Assigning Number Pools to Customers............................................................................................38
Assigning Telephone Numbers......................................................................................................38
Assigning IP Addresses...................................................................................................................40
Assigning Radio IDs........................................................................................................................40
Assigning Dispatch IDs...................................................................................................................41
Associating Customers with Groups................................................................................................41
Starting the Process..........................................................................................................................41
Scan Lists...........................................................................................................................................43
DMO Talkgroups.............................................................................................................................44
Shared Talkgroups and DMO Talkgroups....................................................................................45
Administrative Groups....................................................................................................................46
Modifying and Deleting Groups....................................................................................................47
Associating Customers with Roles....................................................................................................47
Suspending and Resuming Customers.............................................................................................47
Radios.....................................................................................................................................49
The Device Inventory..........................................................................................................................49
The Radio List......................................................................................................................................50
Creating a Radio Record.....................................................................................................................51
The Subscriber Details Page...............................................................................................................52
Assigning Radios to Administrative Groups...................................................................................53
Configuring a Radio............................................................................................................................54
Template, Model and Services........................................................................................................54
Properties..........................................................................................................................................56
Groups...............................................................................................................................................57
Identity..............................................................................................................................................61
Finalizing the Configuration and Activating the Radio...............................................................61
Activating a Radio...............................................................................................................................61
Sending the Configuration Data to the Radios................................................................................62
Creating a Radio by Replication........................................................................................................63
Modifying the Radio Configuration.................................................................................................63
Changing Ownership.........................................................................................................................64
Replacing a Device..............................................................................................................................64
Refreshing Radio Data in the FNE....................................................................................................65
Suspending and Resuming Radios...................................................................................................66
Deleting a Radio..................................................................................................................................67
Deleting a Group.................................................................................................................................68
Inquiries.................................................................................................................................69
Customer Report.................................................................................................................................69
Customer Events.................................................................................................................................70
Mass Operations List..........................................................................................................................71
Security...................................................................................................................................73
The MiBAS Security Concept.............................................................................................................73
Delegation.........................................................................................................................................73
Groups and Users............................................................................................................................73
Accessing Security...............................................................................................................................74
Defining Groups..................................................................................................................................74
Main Details......................................................................................................................................75
Functional Permissions....................................................................................................................76
Data Access Permissions.................................................................................................................77

Add New Group Confirmation......................................................................................................77
Modifying Group Definitions............................................................................................................78
Deleting a Group.................................................................................................................................79
Adding New Users..............................................................................................................................79
Main Details......................................................................................................................................80
Groups...............................................................................................................................................81
Functional Permissions....................................................................................................................82
Data Access Permissions.................................................................................................................82
User Confirmation...........................................................................................................................83
Modifying User Definitions...............................................................................................................83
Deleting a User....................................................................................................................................84
Utilities...................................................................................................................................86
Mass Actions........................................................................................................................................86
Selecting a Population for Mass Actions........................................................................................86
Printing Population Selection Results............................................................................................88
Mass Configuration Changes..........................................................................................................88
Mass Exchange of Member IDs......................................................................................................90
Mass Changes of Serial Numbers and Holder Names.................................................................90
Mass Ownership Changes...............................................................................................................91
Mass Activations..............................................................................................................................92
Mass Suspensions............................................................................................................................92
Mass Resumptions...........................................................................................................................93
Mass Deletions.................................................................................................................................94
Mass Action Status...........................................................................................................................94
Interface Controller..............................................................................................................96
Accessing FNE Interfaces...................................................................................................................96
Activating Interfaces...........................................................................................................................97
Suspending Interfaces.........................................................................................................................98
Viewing and Updating FNE Details.................................................................................................98
Measuring Request Traveling Times.................................................................................................99
Refreshing the Monitor Interfaces View.........................................................................................100
Viewing Logs.....................................................................................................................................100
Queues..................................................................................................................................103
Accessing Queues..............................................................................................................................103
Finding and Viewing Requests........................................................................................................103
Handling Pending Requests.............................................................................................................104
Handling Rejected Requests.............................................................................................................105
Audit Queues: Request History.......................................................................................................105
Index.....................................................................................................................................107
1
Introduction
MiBAS is a billing and administration system designed for managing mobile telecommunication
units. MiBAS Web Access is a Web-based application designed for accessing MiBAS functions
over the Internet or an Intranet.
This version of MiBAS serves network operators as well as large customers of network
operators. Using the advanced security model introduced in this version, the network operator
can grant its customers permission to access MiBAS and to perform operations via Web Access.
For example, a customer that has a large number of radio users can be permitted to perform
such operations as replacing a defective unit or assigning services to the radio users.
Terms and Concepts

This section describes basic MiBAS concepts and terms.
Customer, Radio
A customer is a global entity. Customers may have an inventory of radios.

Sub-markets and Markets
The sub-market represents a group of customers that are located in a given geographical region
and that share mobile network resources. Every sub-market is served by a set of FNEs.
Customers and their radio users are assigned to sub-markets.
Once defined, a sub-market cannot be split into smaller groups. To allow for the division of a
growing sub-market into smaller groups, the market entity is used which can contain multiple
sub-markets. The market is a managerial entity solely designed to put together several submarkets.
Customer Hierarchy
MiBAS allows you to establish parental relationships between customers. A customer may have
multiple child customers and the children may have further descendants. For all practical
purposes there is no limit to the hierarchic levels that can be established.
The hierarchy applies to billing attributes. When you assign a certain billing attribute to a parent
customer all of its descendants inherit it unless they have the same attribute themselves.
The hierarchy is easy to establish: when creating a new customer record you simply select its
immediate parent from among the customers that have been defined in MiBAS. If you move a
descendant from one parent to another, MiBAS records the transfer date and performs billing
calculations accordingly: all consumption that took place before the transfer is evaluated
according to the billing attributes inherited from the previous parent and all subsequent
consumption is evaluated according to the attributes inherited from the new parent.
Central Office Name, Area Code, Office Code
The office code is the first few digits of a telephone number. Office codes can be combined with
relevant area (dialing) codes to form an office name. Such combinations are created by the
MiBAS system administrator. When assigning a telephone number to a radio user, MiBAS
allows you to select an office name which automatically offers you the relevant area codes and
office codes. Then you can enter the remaining digits of the telephone number. Example: if the
telephone number contains 7 digits - Office Name = My Large Customer; Area Code = 212;
Office Code = 363; Telephone Number = the remaining five digits of the number, e.g. 21 42; the
entire number is: 212 363 21 42.
Talkgroup
A talkgroup is a group of radio users that can communicate with each other but not with radio
users from other talkgroups.
Scan list
A scan list a series of talkgroups a radio scans regularly, letting the radio user hear the
communications talking place in one talkgroup, before moving to the other. Thus, the radio user
can regularly hear the communications taking place in all talkgroups included in his scan list,
while the radio scans the list.
Multi-group
A multi-group too consist of a series of talkgroups, only that a call initiated by the member of
the multi-group is heard by the members of all the talkgroups included in the multi-group.
Range
A range consists of a series of groups that can be easily found on the handset in networks that
contain a very large number of talkgroups. Handset owners select a range that include the
talkgroup they wish to contact, instead of searching for the specific talkgroup among many
others.
Accessing and Exiting MiBAS

This section explains how to log on to MiBAS and how to exit when you finish a work session.
Accessing MiBAS
To access MiBAS:
1.
Open your browser and access the URL that was supplied to you.
The Login page appears.
2.
Enter your User ID and Password, and click the Enter button.
The Customer List appears.
Changing User Details

To change your personal details:
1.
Click the My Profile link on the top bar.

The My Profile box appears.
2.
Change the details you want.
3.
Click Update Details.
Accessible Data and System Pages

After you log on, MiBAS allows you to access the information you are authorized to see, as
defined by your system administrator. For example, a customer list displays the customers that
you are entitled to handle.
Also, some pages reviewed in this manual may not appear at all if you are not authorized to
access them. For example, the MiBAS pages where security information is recorded are visible
only to the system administrator who has the appropriate authorization.
Exiting MiBAS
Exit MiBAS by clicking the Logout link located at the top of the page.
2
Operating MiBAS
This chapter explains how to log on to and how to exit MiBAS, and explains operations that are
common to various MiBAS functions. For example, procedures such as performing a search or
adding additional attribute values to a record are identical in all relevant MiBAS pages. They are
covered in this chapter and are not repeated in other MiBAS documents. Please read the
relevant information in this chapter when you need to perform a common operation.
Accessing MiBAS
To access MiBAS:
1.
Open your browser and access the URL that was supplied to you.
The Login page appears.
2.
Enter your User ID and Password, and click the Enter button.
The Customer List appears.
Changing Your E-Mail Address

If you have changed your e-mail address:
1.
Click the My Profile link on the top bar.

The My Profile box appears.
2.
Click the Change E-Mail button.

The Change E-Mail dialog box appears.
3.
In New E-Mail, type the password you want to adopt.
4.
Click OK.
Exiting MiBAS
Do not close the Internet browser when you finish your work with MiBAS. Always click the
Logout link located at the top of the page.
Operating MiBAS | 11
The Navigation System

MiBAS uses a three-level navigation system. The following explains how to navigate to an
option.
Main Navigation Tools

1
First you select a tab in the

upper section of the page.
Selecting a tab displays an

options bar. You select an
option from this bar.
Selecting an option on the

options bar opens a menu. You
select a menu command. Note
that the on the right
indicates the presence of a submenu from which you can
select a menu command.
When you select a menu

command from the menu or
from a sub- menu, option steps
appear (instead of the menu).
They indicate the steps
involved in the operation of the
selected command.
Quick Navigation
The following quick navigation links are available:
The Customer ID Link displayed below the search bar takes you to the Inventory list of the
customer.
While in a wizard, you can quickly jump to a previous page by clicking a menu entry
marked with the
icon.
Use the navigation path links located at the top of a page, to return to a page quickly;
simply click a link on path.
The Top Menu

After accessing a page, using the main navigation tools, a menu may appear on the options bar,
which includes commands that can be applied to the specific page.
This is called the "top menu". Clicking the bar drops the menu down and exposes the
commands it contains.
Disabled Menu Commands

The icon
is used to explain why certain menu commands are disabled.
When a global reason causes several menu items to be disabled, the icon appears in the menu
title. This happens, for example, when a subscriber is disconnected (you cannot, for instance,
modify a disconnected subscriber's record or replace the handset).
Pointing to the icon with the mouse pointer displays a tooltip that explains why the commands
are disabled.
When a local reason causes a certain menu item to be disabled, the icon appears in the menu
entry. In this case too, pointing to the icon displays a tooltip that explains why the command is
disabled.
Accessible Data
Some pages or data reviewed in this manual may not appear on your system if you are not
authorized to access them or your MiBAS installation does not include optional features. For
example, the MiBAS pages where security information is recorded are visible only to the system
administrator who has the appropriate authorization or some security options, such as the
delegation feature, are available only if your installation includes a full security module.
Some fields may not appear on your system if they do not contain data or contain limited data.
For example, if templates are not defined in your MiBAS installation, the template selection list
will not appear in the subscriber configuration pages. Or, if your network involves one dial area
and you defined just one area, the area code selection field will not appear in the number
allocation pages: MiBAS will default to the only area defined in the system.
In addition, some information may not appear on your pages even though it exists. For example,
if a new service type is added to the system, you may not be able to assign the service to a
subscriber if your MiBAS is not refreshed. To make such system-level changes available to all
MiBAS users, click the My Profile link on the top bar and then click the Refresh System
Attributes, or restart your Web server.
Search Tools
This section explains how to locate information and how to navigate between MiBAS pages.
Browsing
In a list such as a subscriber list or an inquiry, each row represents one item (for example, one
subscriber, one inquiry entry). The list shows a pre-defined number of rows. If there are more
items than this pre-defined number, use the links located above the list. The following figure
illustrates the browsing links of an inquiry:
The number of record displayed on one page is a pre-defined value. Records are displayed by
chunks and by pages, each containing a preset number of rows. Thus, a link that reads
Previous Chunk and a link that reads Previous Page display, each, a different number of
rows. Links such as 1, 2, 3 allow you to jump to a specific page. For example, click the link 3 in
an inquiry, to jump to the third page of that inquiry.
In certain cases, using the Back and Next buttons of your Internet browser may display an error
page. This is dues to the fact that as you enter data through the step-by-step wizards, MiBAS
retains the entered information and saves it only after you go through the entire process (this is
similar to the functioning banking systems on the Internet where you cannot go back using the
Back button).
Therefore, it is advisable not to use the browsers navigation buttons and to navigate only using
the navigation functions of the MiBAS Web Access.
Using the Search Bar

The search bar appears at the top of each page. You can use it on any page in order to find a
customer, a subscriber or any other entity.
To conduct a search using the search bar

1.
In the Search For list, select the item you want to find.
For example, to find a customer, select Customer or to find a Rate Scheme select Rate
Scheme.
2.
On the By list, select the information by which you want to conduct a search.
For example, to find a subscriber by looking for its holder name, select Holder Name.
Note that the contents of this list changes according to your selection in Search For. For
example, if you select Customer, you can search by customer ID or name.
3.
In the adjacent box, type the value to search.

For example, if you selected to search by Holder Name, type the name you are looking for.
You can enter the first few character of the value and an asterisk (e.g. Description= rate*) to
find all items whose searched value begins with those characters. You can place the
asterisk in first position to find all items whose searched value ends with the specified
characters. Entering the asterisk only retrieves all relevant records.
Note that certain search criteria require you to enter more than one value, in which case
MiBAS displays several value boxes.
4.
Click the
button .
The Search Results page appears. The data that displays in this page depends on the item
you searched.
If there are no items that meet the criteria you specified in the search bar, the page will be
empty. Otherwise, the records that were found are listed.
5.
Click a row to access the item you want.

This displays the item card (for example, Subscriber Card, Interval Rate Card), as well as a
menu on the left side where you can select to modify or delete the displayed item.
Notes
The search process returns only the data you are authorized to access. If a search fails to return
the results you expected to obtain, you may have searched for information that exceeds your
permissions.
You can quickly return from any page to the results of the latest search by clicking on the Last
link located at the upper-right corner of the search bar.
Using the Local Search Tool

The local search tool allows you to search for information while performing an operation. For
example, when performing an operation that requires you to select a customer, you can open the
local customer search tool in order to find and select the customer you want.
The following are examples that show how to use the local search.
Example: Customer Search
This tool allows you to find a customer registered in MiBAS and to select it.
1.
In Search By, select the data item according to which you want to run the search.
2.
In the box or boxes below it, type the information to search.

For example, the box may be a single field or a pair of From/To fields. In the latter case,
you search the information within a range, such as a range of member IDs.
3.
Click the
button.
All customers that meet the criteria you specified in Search By are now listed in the Results
list.
4.
Open the Results list and select the customer you want.
5.
Click OK.
The Status Bar

The status bar at the bottom of MiBAS pages provide indications about system performance.
The information included in the status bar indicate the time it took MiBAS to display the
current page. Times are shown in milliseconds.
Time
Description
response time
The time it took the MiBAS server to process a user's request to

display a page and return it to the browser.
building
The time it took the MiBAS server to build the page in the server
machine.
loading
The time it took the built page to travel from the server to the client
machine.
rendering
The time it took the browser to build the page on the client
machine.
user ready
The time that elapsed since the user requested a page and until the
page appeared in the browser window.
Using Effective From/Until Dates

In MiBAS, data is usually handled in two stages: first you define the data and then you assign it
(select it from lists) in different MiBAS programs. For each definition and assignment
record, MiBAS offers two standard dates: the Effective From date and the Effective Until date.
For definition records, Effective From means that the data will be available to the MiBAS user
for selection at the indicated date. Effective Until means that the data will not be available for
selection after the indicated date (it will disappear from selection lists in MiBAS).
For assignment records, the Effective From and Until dates set a validity period. For example,
the Effective Until date of a billing attribute value sets the last date at which the subscriber will
be billed according to that value. After that date MiBAS, stops applying that value. Setting an
Effective Until date for an assignment requires, therefore, special attention: you may need to
make another assignment that will become valid (Effective From) after the validity of the
previous one ends. MiBAS moves from one value to another automatically, at the designated
dates (see explanation below on multiple validity periods).
To make a definition or an assignment valid indefinitely, omit the dates or, at least, the Effective
Until date. You can always record validity dates later, whenever the need arises to do so. If you
set an Effective Until date, you can always extend the period by changing the date.
Depending on the nature of the record, MiBAS may offer default dates when creating new
records. For example, Effective From may be automatically set to a date of your choice or to the
start date of the bill cycle.
The ... From field shows todays date. If you want to use it, leave it as is. If you want to change
it, click the
button and select the date you want. This date will be inserted in the Effective
From field of new records (created with the Add command). Selecting the Start Bill Cycle button
inserts the starting date of the current bill cycle.
If you have defined a period previously, the day that follows the Until date of the previous
period is offered as the beginning of the next periods From date. If a known period is involved,
MiBAS automatically computes the Effective Until date.
Multiple validity periods for the same item. Where applicable, you can set multiple validity
periods with a different value for each period. As one period ends, MiBAS automatically
switches value/mode specified by the next validity period. You can leave the last period with a
blank Effective Until date in order to keep the last value in force indefinitely.
The multiple validity periods are entered in a sub-table that opens below the relevant item, by
clicking the button. The button changes to . You can click it to close the sub-table.
When you open the sub-table, MiBAS displays a period definition with the data you entered in
the main table. This period starts at date selected in the upper section of the page. If necessary,
you can enter the period's end date.
To add a new value/period, click the Add button. You can add past periods as long as they do
not start before the start date of the current bill cycle.
To delete a future period, select the appropriate row and click the Delete button.
Periods that ended are automatically removed from the display. You can use the Show History
button to list the past values and their periods.
The Effective Date

The Effective Date field that appears above some lists is designed to show a list that existed at
the specified date.
For example, a page that lists the fixed charges items shows only those items that were active at
that date. Use the
button to select the date you want.
Available and Attached Values

In some MiBAS pages, you will see two groups of values: an "available" group and an "attached"
group. The "available" group lists the values that have not been assigned to the subject of the
current operation (such as customers). The "attached" group lists the values that have been
assigned to the subject of the operation. The following figure illustrates the two groups.
To assign a value to the subject of the operation for example, to affiliate a customer (subject)
with a security group (value) select one or more values in the "available" pane and click the
button. The assigned values appear in the "attached" pane.
To cancel an assignment, select the values you want in the "attached" pane and click the button.
The values return to the "available" pane from where you can, if need be, re-select them.
Data Entry
Entries marked with a red asterisk are mandatory. You cannot save your entries without filling
the mandatory fields.
In some MiBAS pages a special data entry method is used that involves three values: default,
current and new, as shown in the following figure:
To modify a value, enter it or select it in New Value. The next time you access the same page the
currently applied value appears in the Current Value field. The Default Value field always
displays the value set during system setup.
Note the following:
The new value enters into effect after it is acknowledged by the network element. Before
the acknowledgment is received, the current value continues to remain in force.
If you mark the checkbox of an entry, you must specify a value in New Value or leave the
field blank to let MiBAS use the parameter's default value (if one was defined).
Modifying, Deleting, Reporting and Auditing

Records
The Modify option that appears on the various menus open the current record and allows you
to view and modify data. For example, if you select the Modify command after opening the
Customer Card, MiBAS opens the current customer's record and allows you to access the fields
for modifications. In some cases MiBAS may block access to some data items. To change them
you need to delete the old record and create a new one.
The Delete command or button allows you to delete the record that currently appears on the
screen. For records that appear in tabular format, first click the row to delete and then select the
Delete command. To delete multiple rows, check their "trash"
box on the leftmost column,
and click Delete.
Some rows include the
button. Clicking the button deletes the record.
In some cases, when you click the Submit button to save a new record, the record card
appears together with a side menu.
The menu includes the following record handling commands:

Option
Description
Add
Opens a page where you can enter a new record.
Modify
Opens the current record for modifications. You can access the
fields and change the data.
Delete
Deletes the current record.
Report
Opens the reporting page and allows you to print the current
record in report format.
Audit
Opens the reporting page and allows you to print the changes that
occurred in the current record, in report format.
For example, if you access an existing record and change the value
of a field, MiBAS automatically posts an audit record describing the
change. The Audit report displays such changes.
In some pages, an Audit button may appear which provides the
same functionality.
In addition, MiBAS includes utilities for deleting and modifying large numbers of records in a
single operation. These utilities allow you to build a query to select the population to update or
to delete.
If the modification or deletion involves operations that exceed the standard procedure described
above, they are explained in the appropriate sections of the MiBAS user guides.
Showing History
Effective From/Until. Lists that have Effective From/Until dates always display the records that
are currently in effect. Checking the Show History box displays the records that have been in
effect in the past.
Other values. For some values, such as an accounts status, MiBAS displays the current values
(e.g. the current account status). Checking the Show History box displays the history of the
changes that occurred in those values.
Using the Floating Calendar

In date fields, you can specify a date by selecting it using the floating calendar. Click the
button that appears next to the date field to open the calendar.
Using the arrow buttons that appear to the right of the month, select the month you want. Then
select a year. Finally, click the starting day. This selects the date and closes the calendar.
Printing Inquiry Results and Other Data

The Print button generates a file that you can later open with an appropriate application and
print using that application's printing command.
To produce an Adobe Acrobat file
1.
Scroll to the end of the inquiry results.
2.
Click the Printer Friendly button.

This converts the inquiry results to a PDF file and displays them in the Adobe Acrobat
Reader (the reader must be installed on your computer).
3.
Use the Acrobat functions to print the inquiry results.
To produce a Rich Text or Excel file
1.
Scroll to the end of the inquiry results.
2.
In Download, select the format of the file where you want to save the inquiry results: Rich
Text Format or Excel.
This starts the standard Windows download process.
3.
Click Save and specify where to save the file
3
Provisioning Administration
This chapter is intended for the MiBAS system administrator. It describes operations that the
system administrator should perform so that other MiBAS functions may be executed properly.
For example, in order to perform radio groupings, the group names should be initially defined
in Provisioning Administration.
To access administrative functions, select the Provisioning Admin tab.
One-Time Tasks
This section reviews administrative operations that are usually performed only once, after
installing MiBAS. Such operations are accessed during the lifetime of the system only for
updates, which occur infrequently.
Security Groups
For details about security groups, consult your Dimetra documentation. At this stage you only
define the Dimetra security groups in MiBAS so that they can later be associated with MiBAS
entities such as customers.
To define Dimetra security groups:
1.
Click the Provisioning Admin tab.
2.
Select the Infrastructure option.
3.
From the menu, select the Security Groups command.
Provisioning Administration | 23
4.
Click the Add button to create a new security group definition.
5.
In Name, type the group's name.
6.
Click the
7.
Click the Submit button.
button to expand the group to specify its sub-market affiliation.
Frequencies and Channels

The channels that are available to your DMO talkgroups should be first entered in MiBAS so
that they can be later allocated to radios. Channels transmit on a given frequency and therefore,
before you define the channels you need to record your available frequencies in MiBAS.
Before setting frequencies, the operator should determine the base frequency and the frequency
offset. These are set through the system parameters BaseFrequency and FrequencyOffset.
To define channels in MiBAS
1.
2.
3.
From the menu, select Frequencies.
4.
Click the Add button to open a new row.
5.
In Name, enter the frequency.
6.
If the frequency exclusively belongs to a customer, in Owner click the

and select the customer.
7.
Repeat the above steps (Add, etc.) to create all the frequency records you need in order to
define the channels.
8.
9.
From the menu, select Channels.
10.
11.
In Frequency, select the frequency over which this channel will transmit.
12.
In Cluster select the cluster to which this channel belongs.
13.
Check the DMO Enabled box to make this channel available to DMO talkgroups.
button and find
14.
Repeat the channel creation steps (Add, etc.) to create all the channel records you need.
15.
Radio and Fleet Administrative Group Definitions

The grouping function is designed to group radios and fleet elements (talkgroups, etc.). At any
given time, only one administrative group can be active in the network that is, only the radios
attached to the active group can communicate.
Grouping is especially designed to let a small number of radios have the entire network at their
disposal, for example, in times of emergency. A typical configuration would have two groups: a
large group that includes all radios and active at all times, and a small group of radios assigned
to an inactive administrative group. The second group would be activated in times of
emergency. Administrative group switching is explained in Selecting the Active Administrative
Group on page 33.
First you will define the group types and build the actual groups of different types. A group
type can be "Departments" and you may have, for example, 10 different department-type
groups, each grouping a number of departments.
Defining the Group Types

To define group types:
1.
Select the Provisioning Admin tab and then select the Infrastructure option.
2.
From the menu select Groupings and from the sub-menu select Grouping Definitions.
The Grouping page opens.
3.
4.
Enter the information described below.
5.
Grouping
Enter a name for the group type. For example: Departments.
(expand group), Entity
Click the + button to expand a group name.
Mark the entities that can be part of a group of this group type.
For example, if you check the Radios option, MiBAS will allow you to assign radios to groups of
this type. If you don't, radios may not be part of groups of this type.
Cardinality
Select the relationship that will bind the group type and the entity. The options are:
Option
Meaning
Zero-to-many
You do not have to assign entities to groups, but you can if

you want.
Zero-to-one
You do not have to assign entities to groups. However, if you

do want to make assignments, you can assign an entity to
only one group of this type.
One-to-one
The entities must be included in one and only one group of

this type.
One-to-many
The entities must be included in at least one group of this

type.
Owner
A group may have a customer as an owner. If you select a customer in this field, the group will
be used only by that customer.
Description
Enter text that described this group.
Building the Groups

Once the group types are established, you will proceed to building the different groups of each
type. For example, if you have 100 departments you can build four groups for "Department"
type, each containing 25 departments.
To build the groups:
1.
2.
From the menu select Groupings and from the sub-menu select Grouping Instances.
The Grouping Instances page opens.
3.
In the drop-down list select the group type of the group you are about to build.
4.
5.
In the Name field, type the name of the group member.

For example, if the group type is Departments, and one of its members is the Sports
Department, type Sports Department.
6.
In Description you can optionally type text that describes the group.
7.
Call Route
For details about call route, consult your Dimetra documentation. At this stage you only define
the call route in MiBAS so that they can later be associated with MiBAS entities such as Radio
User Interconnect profile.
To define call route:
1.
2.
3.
From the menu, select the Call Route command.
4.
5.
In Alias, enter an alias
6.
In ID, enter the ID.
7.
In Gateway, select the Gateway id .This is the TETRA ISSI signaled over the air indicating
which call route is required by the radio user.
8.
In Security Group, select the Security Group to which this Call Route belongs.
9.
In Incoming Prefix, enter the value that indicates which outgoing pre-fix numbers the
external network adds to the incoming telephone number in order to indicate which
external network route the call followed. This is used when multiple networks are
connected using PABX as route mechanism. The field may be blank. If the field is blank,
only one call route may be defined.
10.
In Outgoing Prefix, enter the value that indicates which outgoing pre-fix numbers shall be
added to the called telephone number. This prefix may be used by network equipment
connected to the TIG (typically a PABX) to route the call.
11.
In Zone ID, enter the number which identifies the zone.
12.
In Note, enter plain text that is intended to provide relevant information about the call
route.
13.
Repeat the channel creation steps (Add, etc.) to create all the Call Routes you need.
14.
Radio Roles
Radios may be assigned roles. The assignment can be used for administrative purposes.
At this stage you only define the names of the different roles.
To build a list of roles:
1.
2.
From the menu select Groupings and from the sub-menu select Roles.
The Roles page opens.
3.
4.
In the Name field, type the name of the role.
5.
In Description you can optionally type text that describes the role.
6.
Identity Types
The identity types are data item through which a radio's actual user can be uniquely identified.
For example, radio users can be identified through their passport number or through their
driving license number. When creating a radio record you also specify the identity type through
which its owner will be identified.
In Provisioning Admin you define the types of identities you want to use in MiBAS to identify
radio owners. For example, you can create a type named "Passport Number".
To create identity types:
1.
2.
From the menu select Identity Types.

The Identity Types page opens.
3.
4.
In the Description field, type the name of the identity type.

For example, type Passport Number or Driving License Number.
5.
In Data Type select the nature of the identifying element:

Select String if the identity may include digits, letters and other characters.
Select Number if the identity may include only digits.
6.
In Min Length and Max Length enter the minimum and maximum number of characters
the identity should include.
Note that when creating a radio record, MiBAS will require you to specify an identity of
the indicated nature (string or number) and makes sure that the identity does not include
less or more than the indicated minimum or maximum.
7.
Ongoing Tasks
This section describes administrative operations that are performed frequently.
Profiles
This section explains how to build Dimetra profiles using the MiBAS Profiles tool. It assumes
professional knowledge of Dimetra profiles.
UCS API's exists only for the following profiles:
Radio User Capability Profile
Radio User interconnect profile
Therefore handling these profiles should be done only by MiBAS
Other profiles:
Valid sites profile
TG/MG capability profile
TG/MG valid sites profile
should be handled simultaneously in MiBAS and the UCS.
Adding a New Profile

To add a profile:
1.
2.
Select the Profiles option.
3.
Click Add New.

The Add New Profile page opens.
4.
Assign an alias and select the profile type.

The properties of the selected type appear in the lower half of the page.
5.
Optionally, add a description of the profile.
6.
In Belongs To, assign the profile to a market or to a customer.

Assigning a profile to a customer helps you quickly locate a profile, when assigning
profiles to radios: MiBAS will allow you to select only from a list of profiles belonging to
the customer that owns the radio.
To assign the profile to a customer, click the
you want.
button and find and select the customer
7.
In New Value, enter the property values for this profile.
8.
Click Submit.
Viewing and Modifying a Profile

To easily access a profile for modifications, MiBAS provides a filtering tool through which you
can locate profiles by their market, type or customer affiliation.
To access and modify a profile:
1.
2.
Select the Profiles option.

A list of the existing profiles appears.
3.
In the Profiles list, specify a market, a profile type and/or a customer, and click Retrieve.
Note
You can also use the Search tool and search profiles by their ID or alias.
The profiles that meet your search criteria appear.
You can also expand a profile type by clicking
4.
Click the profile you want to access.
5.
Select the Modify command from the menu.
button and list the profiles of that type.
The Modify Profile page appears.
6.
Change the data you want.

You can change the description and the property values (in New Value).
7.
Selecting the Active Administrative Group

At any given time, only one of the administrative groups are active. This means that at any
given time only the radios belonging to the active administrative group can communicate.
Radios that do not belong to the active group cannot communicate.
You can change the active group by selecting another group. The procedure involves
suspending the radios belonging to the currently active group and resuming the radios of the
new active group.
To make an administrative group active:
1.
Select the Provisioning Admin tab and then select the Operations option.
2.
From the menu select Switching Groupings.
3.
In New Grouping select the group that will become the active group instead of the one
shown in Current Grouping.
4.
This creates requests for suspending the radios of the active group and resuming the radios of
the newly selected group. The Sent progress bar indicates the number of requests sent and the
Completed progress bar indicates the number of suspend and resume requests that have been
implemented on the FNE.
Handling Rejections
If rejections occur, the Completed bar will stop before it fully runs its course. You can see the
rejections by selecting Rejected Groupings on the menu.
After handling the rejections on the appropriate queues, return to the Switching Groupings
page and click the Restart button to resend the rejected requests.
4
Customers
This chapter explains how to define, access and modify customer details.
To access customer data, select the Customer Care tab.
Adding and Configuring Customers

Depending on your MiBAS settings, customer records are either initially entered in a MiBAS
table, using tools that are not covered in this manual, or they are manually recorded in MiBAS.
If your MiBAS installation is set to use customer records initially entered in a MiBAS table,
during the initial stage only basic information such as the customer ID and name are entered.
Subsequently, you use MiBAS to complete the details.
Customer Main Details

First, you will enter the basic customer details. Follow these steps:
1.
After accessing MiBAS and selecting the Customer option, a list of customers recoded in
the initial stage appears.
2.
Click the customer you want to configure.

The Customer Card appears.
3.
Select the Add Customer command from the menu.

The main details page appears.
Customers | 35
4.
5.
Click Next.
The main details are:

Customer ID
If basic customer details have been entered during an initial stage, this field displays the
customer ID. You cannot change it.
Otherwise, enter the customer ID.
Customer Name
If basic customer details have been entered during an initial stage, this field displays the
customer name. You cannot change it.
Otherwise, enter the customer name.
Parent Customer ID
If you are using the parent hierarchy feature, click the

button to activate the search tool, and
find and select the ID number of this customer's parent. The parent must be a customer that has
already been configured in MiBAS.
Market.Submarket
Select the sub-market to which this customer belongs.

Use Owned Phone Numbers
Check this box if this customer's radio users will be allocated telephone numbers from a pool of
numbers especially reserved for this customer. If you do not check the box, this customer's radio
users will get telephone numbers from the system's global pool.
The pool itself is assigned to the customer at a later stage. See Assigning Number Pools to
Customers on page 38.
Use Owned IP Addresses
Same as Use Owned Phone Numbers but for IP addresses.
Customers | 36
Use Owned Dispatch IDs
Same as Use Owned Phone Numbers but for dispatch IDs.

Use Owned Radio IDs
Same as Use Owned Phone Numbers but for subscriber IDs (IMSI).
Customer Security Groups

Security groups are an optional Dimetra feature.
A customer's radios may be grouped in security groups. Before you perform the actual
grouping of the radios, you need to associate the customer with the different security groups.
This will later help you assign the radios only to the groups associated with their customer. The
association of the customer with the different security groups does not have an operational
impact on the system. It is only designed to make radio grouping easier.
This operation is performed in the Security Groups page that appears when you click Next in
the previous page.
The security groups have already been defined in MiBAS by your system administrator. At this
stage you only need to associate this customer to the available security groups.
Assign the customer to groups by moving groups from the "available" list to the "attached" list.
You can assign the customer to more than one group.
Accessing Configured Customers

The list of the configured customers you are authorized to handle appears as soon as you log
on. You can also display it by clicking the Customer link below the Search bar.
If you are authorized to access all customers in MiBAS, no list appears. In this case use the
Search tool to find the customer you want.
The customer list consists of links: a main link marked with the icon indicates a parent
customer. Click the icon to list the descendant customers. This both lists the descendants and
changes the icon to , which you can click to collapse (hide) the descendants list. You always
access a descendant.
Customers | 37
After clicking a link, the Customer Card appears. It includes the data you have entered when
configuring the customer.
Modifying Details of Configured Customers

After accessing the customer card of a configured customer, select the Modify command. This
activates the customer configuration tool through which you can modify the data in the same
way you entered it.
Assigning Number Pools to Customers

The radio users of a customer are allocated addresses such as telephone numbers and IP
addressed from a reserved pool or from the global MiBAS pool. If you configured customers to
use their own private pool, follow the procedure described in this section to allocate the pools.
Assigning Telephone Numbers

Follow these steps:
1.
Select the customer and display its customer card.
2.
From the menu select Reserve Pools and from the sub-menu select Phone Numbers.
Customers | 38
3.
Do one of the following:
To select a pool of telephone numbers that are within the scope of a pre-defined office
(as determined by your system administrator), select the office from the Office Name list.
MiBAS automatically fills the Areas Code and Office Code.
Some office names may be identical, in which case they have numbers between
parentheses, like this: My Office Name (404 - 535), My Office Name (404 573). The
numbers indicate the starting area code and office code. Select the one you want.
To select a pool of numbers in a specific dialing area, in Area Code select the dialing area.
Office Code automatically lists the available office codes in the selected area. Select the
desired office code.
The Available Pools pane lists the telephone number pools that are available in the selected
office/area.
To select a specific number, check the Exact box, type the number in the adjacent field and
click the Retrieve button. If the number is available, it will appear in Available Pools.
Otherwise it will be listed as taken in Reserved Pools.
To select a pool of numbers included in a range of numbers, clear the Exact box. This opens
the range fields.
In the first field, type the first number in the range. In the second field, type the last
number in the range. Then click the Retrieve button. Those numbers within the range that
are available will appear in Available Pools. Those that are not will be listed in Reserved
Pools.
To select numbers from among all telephone numbers pooled in MiBAS, clear the Exact
box and click the Retrieve button. Those numbers that have not been taken yet, will appear
in Available Pools. Those that have been taken will be listed in Reserved Pools. Note,
Customers | 39
however, that the operation might not retrieve all the numbers from the database, in which
case the message "Partially retrieved appears.
The extent of the retrieval is controlled by a system parameter internally set in your MiBAS
installation.
4.
5.
Select the pools you want by moving them to Reserved Pools.

a.
In Available Pools, click the icon of the pool entry you want to divide. This opens the
Divide Pool dialog box.
b.
In the From/To fields, specify a different range. The range must be entirely included in
the selected pool.
c.
Click OK. The window closes. The new pool appears in the Reserved Pools list. The
original pool is updated accordingly.
Assigning IP Addresses
The procedure is the same as the one explained for telephone numbers. Note the following
differences:
In the Reserve Pool sub-menu, select IP Addresses.
To make the addresses internationally unique, check the "Routable IP addresses" box. To
make the addresses unique within global network, clear the box.
Assigning Radio IDs

differences:
In the Reserve Pool sub-menu, select Radio IDs.
First select a sub-market and then make the assignments.
Customers | 40
Assigning Dispatch IDs

differences:
In the Reserve Pool sub-menu, select Dispatch IDs.
First select a sub-market and then make the assignments.
Associating Customers with Groups

A customer's radios may be grouped in talkgroups, multigroups, scan lists and DMO
talkgroups (for information consult the Dimetra documentation) as well as into administrative
groups.
Before you perform the actual grouping of the radios, you need to associate the customer with
the different groups. This will later help you assign the radios only to the groups associated
with their customer. The association of the customer with the different groups does not have an
operational impact on the system. It is only designed to make radio grouping easier.
The association process differs according to the grouping type. In some cases (e.g. talkgroup)
you will actually create the grouping type and in others (e.g. administrative grouping), you will
use data that has already been created by the system administrator.
Starting the Process

To start the group definition process:
1.
Select the customer and display its customer card.
2.
From the menu, select Maintain Fleet.

The Maintain Fleet page opens.
3.
Enter the group information described below.
Customers | 41
4.
When you are done, click the Submit button.
Talkgroups
Talkgroups always belong to a sub-market and to an administrative group.
To create a talkgroup:
1.
Select the Talkgroups tab and click the Add button.

The Add Talkgroup dialog box opens.
2.
In Talkgroup Name, enter a name for the talkgroup.

The name must be unique among all TMO talkgroups.
3.
Click OK.
The new definition appears under Talkgroups.
4.
Expand the new talkgroup by clicking its
button.
This displays the talkgroup properties.
5.
Configure the talkgroup by specifying values for the properties.

For details about the properties, consult the Dimetra documentation.
6.
Customers | 42
The talkgroup ID number is now allocated and appears in the ID column. The information
is sent to the queue. A new talkgroup can be added only after the queued talkgroup is
registered in and acknowledged by the FNE (the Assign Fleet command remains grayed
until the fleet is duly registered by the FNE).
As soon as the fleet is queued, its State is set to New. After it is acknowledged by the FNE,
its state changes to NOP.
Multi-groups
A multi-group too consist of a series of talkgroups, only that a call initiated by the member of
the multi-group is heard by the members of all the talkgroups included in the multi-group.
To define a multigroup:
1.
Select the Multigroup tab and click the Add button.

The Add Multigroup dialog box opens.
2.
In Multigroup Name, enter a name for the multigroup.

The alias must be unique among all multigroups.
3.
Build multigroups by moving talkgroups from the "available" list to the "assigned" list.
You must add at least two talkgroups to a multigroup.
4.
Click OK.
A multigroup definition appears under the Multigroups tab.
Scan Lists
A scan list a series of talkgroups a radio scans regularly, letting the radio user hear the
communications taking place in the scanned groups.
Customers | 43
To define scan lists:

1.
Select the Scan Lists tab and click the Add button.
The Add Scan Lists dialog box opens.
2.
In Scan List Alias, enter a name for the scan list.

The alias must be unique among all scan lists.
3.
Build scan lists by moving talkgroups from the "available" list to the "assigned" list.
You must add at least two talkgroups to a scan list.
4.
Click OK.
A new scan list definition appears under the Scan Lists tab.
DMO Talkgroups
Mobile stations can select Direct Mode Operation (DMO) to directly communicate with other
mobile stations without calling through the system infrastructure.
To create DMO talkgroups:
1.
Select the DMO Talkgroups tab and click the Add button.
The Add New DMO Talkgroup dialog box opens.
Customers | 44
2.
In DMO Talkgroup Alias, enter a name for the DMO talkgroup.

The name must be unique among all talkgroups.
3.
In DMO Channel, select the channel over which this radio will communicate in the
framework of this DMO talkgroup.
The channels to use have already been defined by your system administrator and the
channels you need should appear on this list.
4.
Click OK.
The new definition appears under DMO Talkgroups.
5.
Expand the new DMO talkgroup by clicking its
button.
This displays the DMO talkgroup properties.

6.
Configure the DMO talkgroup by specifying values for the properties.

For details about the properties, consult the Dimetra documentation.
7.
Shared Talkgroups and DMO Talkgroups

The sharing feature allows other customers to use the talkgroups of this customer.
To create shared talkgroups:
1.
Access the customer.
2.
Select Shared Talkgroups.
3.
Select a tab: Talkgroups or DMO Talkgroups.

The groups associated with this customer are listed.
4.
Expand a talkgroup you want to share with other customers.
Customers | 45
5.
Click the Add button in order to select another customer that will share this group.
This opens the customer search tool.
6.
Find the customer and select it.
7.
Repeat this procedure for all customers that should share this talkgroup.
Administrative Groups
Administrative groups have already been created by your system administrator. At this stage
you will associate the customer with one or more groups.
To associate the customer with administrative groups:
1.
2.
Form the side menu, select Grouping.
The page lists the group types defined in MiBAS.
Customers | 46
3.
Click the + icon of the type you want.

This displays the actual groups of this type, as defined in MiBAS.
4.
Assign this customer to groups by checking the boxes of the groups you want.
You can repeat this step for the different group types listed on this page.
5.
Modifying and Deleting Groups

You can access any of the talkgroups, scan lists, multigroups and administrative groups, and
modify them. For multigroups and scan lists, use the
button located on the rightmost cell of
the entry to access the data for modifications. To delete an entry use the
button. This button
becomes available if the talkgroup does not have any radios assigned to it.
Associating Customers with Roles

Roles have already been created by your system administrator. At this stage you will associate
the customer with one or more roles in order to facilitate the actual classification of the radios as
a later stage.
To associate the customer with roles:
1.
2.
Form the side menu, select Roles.
The page lists the roles defined in MiBAS.

3.
Associate this customer with roles by checking the boxes of the roles you want.
4.
Suspending and Resuming Customers

Suspending a customer means stopping (suspending) all of its radios. The suspension is a
temporary status: the customer can be quickly resumed with a simple menu selection. You can
also suspend (and resume) individual radios; see Suspending and Resuming Radios on page 66.
To suspend a radio:
1.
Access the customer and display its customer card.
Customers | 47
2.
From the menu select the Suspend command.

The Suspend Radio General Details page opens, displaying the details of the radio to
suspend.
You can enter a future date if you want to delay the operation.
3.
In Reason, select a reason that explains why the customer is being suspended.
Note
Some of the reasons may have been originally defined (by your system administrator) as
reasons that do not permit resumption. If you select such a reason you will not be able to
resume the subscriber.
4.
Click Submit.
The Suspend Customer Confirmation page opens, displaying the full details of the
customer for which the suspension request has now been submitted.
5.
Click OK.
To resume a suspended customer:

1.
Access the suspended customer.
2.
From the menu select the Resume command.

The Resume Customer General Details page opens, displaying the details of the customer
to resume.
3.
Click Submit.
The Resume Customer Confirmation page opens, displaying the full details of the
customer for which the resumption request has now been submitted.
4.
Click OK.
Customers | 48
5
Radios
This chapter explains how to register radios in MiBAS and how to configure and activate them.
Radios are managed per customer.
To access radio data, select the Customer Care tab.
The Device Inventory

The devices (handsets) allocated to a customer constitute its "inventory".
To access the device inventory:
1.
2.
Click the Inventory option.

The customer's devices are listed.
In this list you can do the following:

Sorting records. To sort the records according to one of the fields, open the "Sort By" list and
select the name of the field according to which you want to sort the records. The heading of the
column according to which the records are currently sorted appears against a gray background.
Paging through records. The page displays as many devices as the number that appears in
"Rows per page". You can see more of the devices by selecting a bigger number or by clicking
the links 1, 2, 3...
Displaying all fields. The device record contains many fields. Only part of the fields are
displayed when you access the page. To see all of them, click the "extended view" link and then
use the horizontal scroll bar. To return to the original display, click the "short view" link.
Selecting records. To select all of the currently displayed rows (as many as the number
displayed in "Rows per page"), mark the checkbox located at the top of the leftmost column. To
Radios | 49
select all the devices, including those that are not currently displayed, click the "Select all" link.
Clearing the box or clicking the "Unselect all" link clears the corresponding selection.
Refreshing the list. As other MiBAS uses may be adding or removing devices, click the Refresh
button once in a while to see the most updated list. Devices are automatically withdrawn from
this list when they are activated.
The Radio List

The radio list appears when you click the Subscribers & Accounts option on the options bar.
The Deleted tab lists the radios that have been deleted. Drilling down the Deleted entry links
leads to the Deleted Radio Card where only a minimal amount of information remains.
The Active tab lists the radios that currently exist in the MiBAS system, including the suspended
ones. When you click a radios (a row), the radio card appears.
The Radio Card displays basic radio details as well as the alerts associated with the specific
radio.
Radios | 50
The side menu of this card allows you to perform billing operations that may still be needed.
The functions that you can use in this page are identical to those described for the Inventory list.
Creating a Radio Record

Creating a radio record means registering in MiBAS a radio to a customer.
To create a radio record:
1.
2.

The customer's radios, if any, are listed.
3.
From the menu select the Add New Radio button.

The Add Radio page appears.
4.
5.

If you do not want another radio to this customer, click the Submit button. The Radio Card
page appears, displaying the details of the newly added radio.
Radios | 51
If you want to add another radio to this customer, click the Submit and Add Another
button. This clears the screen and allows you to enter another radio to the customer's
inventory.
If you want to access radio configuration now, click Submit and Configure.
A description of the radio definition parameters follows.
TEI
Enter the radios Tetra Equipment Identity.

Alias
Enter the radio's alias.

This entry is mandatory. The alias must be unique in the network (two radios may not have the
same alias).
Radio ID
Specify the radios ID number. This ID can also be assigned at a later stage, through the radio
configuration tool.
Submarket (Zone)
Select the submarket (Zone) to which this radio belongs.

Model
Select the radio's model.

Serial Number
Type the serial number of the radio.

This is not a mandatory entry. If you do not specify the serial number, MiBAS assigns a value.
First Name, Last Name
Enter the first and the last name of this radio's actual user.
Identity Type
Select the type of the identity through which this radio's user should be identified. For example,
if your MiBAS system is set to identify radio users through their passport number, the list
should include a type such as "Passport" or "Passport Number" (or a similar entry).
Identity
Enter the identifying information. For example, if the identity type is passport, enter the
passport number.
Role
This drop-down list contains the roles that have been associated with this radio's customer.
Open the list and select this radio's role.
If the selected role has already been assigned to another radio of the same customer, the First
Name, Last Name and Identify fields become mandatory. Unique names allow you to
differentiate between the various radios that have the same role.
The Subscriber Details Page

Accessed from the menu, after selecting a radio from the list, the Subscriber Details page is
identical to the radio data entry page, only that it only allows you to view the subscriber
information.
Radios | 52
Click the Refresh button to view the latest details. You may need to refresh the display to view
the data that has been modified by other MiBAS users after you displayed this page.
Assigning Radios to Administrative Groups

This feature is available only if MiBAS has been initially set to use it. This is done through a
dedicated system parameter. Changes in this status should be done through MiBAS Support.
Administrative groups have already been created by your system administrator and the current
customer has already been assigned its default groups. A radio is assigned to an administrative
group by associating it to one of the groups assigned to the customer.
To assign a radio to administrative groups:
1.
Access the radio.
2.
Form the side menu, select Grouping.
The page lists the group types associated with this radio's customer.
3.
Click the + icon of the type you want.

This displays the actual groups of this type, associated with the customer.
4.
Assign this radio to groups by checking the boxes of the groups you want or remove this
radio from a group by clearing the appropriate box.
5.

This displays the Confirmation page, listing the administrative groups you have selected.
From this page you can proceed to the radio configuration stage by clicking Configure.
Radios | 53
Configuring a Radio
You can access the radio configuration function in one of the following ways:
While creating a new radio record in the Add New Radio page, click the Submit and
Configure button.
Click the Radios option, select a radio and from the menu select Configure.
After selecting the radios administrative group and reaching the confirmation page, click
the Configure button.
This displays the configuration page.
Follow these steps:

1.
Open the Model drop-down list and select the radios, model.
2.
Click the tabs (Services, Properties, etc.) to access the configuration details and enter the
information described below.
Template, Model and Services

The communication options of subscribers depend on the services assigned to their handset.
Thus, a handset configured with the telephony service has a telephone number and can be used
to conduct telephone conversations as well.
You can assign services in one of the following ways:
Via a template
Manually, one-by-one
Radios | 54
Using both methods
The template is a service package that contains a set of services of your organization's choice.
Subscribers who chose to acquire a certain package are assigned the appropriate template
instead of assigning the relevant services one-by one. If necessary, after assigning a template
you can also allocate additional services manually, to supplement the package with other
features.
Template
To assign a template, open the Template drop-down list and select the one you want.
Model
To assign a model, open the Model drop-down list and select the one you want.
Manual Service Configuration

Select the Services tab and specify the services the radio can use, and configure the services.
Services are selected by checking boxes. If you have selected a template the services included in
it are already checked.
You can withdraw any service by clearing a box.
Dispatch and Radio Ref

A Dimetra radio is a dispatch device by default and therefore all radios registered in MiBAS are
automatically configured with the Dispatch service. You do not need to configure radios with
any other services, if they will function as dispatch devices only.
Radios | 55
The Dispatch service in the Principal Services section is therefore selected and cannot be
deselected as Dimetra radios must function at least as dispatch devices by default.
The same applies to Radio Ref. (In MtR only)
Telephony
To allow the radio to be used as a telephone, check the Telephony checkbox.
Checking the box automatically allocates the telephone number, based on the dispatch ID.
To further configure the telephony service, click its button and enter the values you want for
the different additional properties. For information about the properties, consult the Dimetra
documentation.
Packet Data
Check the Packet Data box to enable the radio for data transfer.
Packet-data-enabled radios must have an IP address.
To assign an IP address to this radio:
1.
Click the
button in the New Address column.
The IP Address window pops up.
2.
Run a search in order to find an available address.
Short Data
To enable SMS communications for this radio, check the Short Data box.
Properties
The properties determine the way the radio will function. Enter property values in the New
Value column, For information about the radio properties consult the Dimetra documentation.
Radios | 56
Groups
This tab lists the various groups assigned to the customer. Use this tab to affiliate this radio with
different groups.
Radios | 57
The number of groups of a certain type (talkgroup, scan list, etc.) a radio can be part of is
limited. The limit is specified at the bottom of the page. "Selected" indicates the number of
groups that contain this radio. The number between parentheses ("max") indicates the
maximum number of groups with which the group can be affiliated.
TMO Groups
To affiliate this radio with TMO groups:
1.
Select the TMO Groups tab.

The left section lists the multigroups assigned to this radios customer. The right section
lists the talkgroups assigned to this radios customer, including those that are members of
the multigroups listed on the left.
2.
To assign the radio to multigroups, mark the corresponding checkboxes in the

Multigroups section.
The talkgroups included in it are automatically selected. You can clear boxes to remove one
or more talkgroups from the selection (you do not have to select entire multigroups).
If the list is too long, you can search for the multigroup you want by entering its ID or its
Alias in the top row: as you type the entry, MiBAS brings the nearest multigroup into view.
3.
To assign the radio to individual talkgroups, check the corresponding checkboxes in the
TMO Groups section.
To remove a radio from a group, clear the corresponding checkbox in the TMO Groups
section.
If the list is too long, you can search for the talkgroup you want as explained for
multigroups above.
TMO Ranges
On networks using a large number of talkgroups, selecting a talkgroup on the handset may be
tedious. The TMO Ranges feature allows you to group the talkgroups in a certain order. On the
handset, you can select a range, rather than a talkgroup, and then select a talkgroup from within
the range.
Ranges may include only the talkgroups selected under the TMO Groups tab.
To establish TMO ranges:
1.
Select the TMO Ranges tab.
Radios | 58
2.
Mark the checkbox of the next empty line.
3.
In Name, enter a name for the group.
4.
Click the
5.
Click the Add button.
button.
The Add Groups dialog box appears.
6.
Select the talkgroups you want to add to this range by clicking them.
If the list is too long, you can enter an ID or an alias on the top row. As you type, MiBAS
pulls up the nearest talkgroup.
7.
Click OK to add the selected talkgroups to the range.
8.
If necessary, select a talkgroup and click Move Up or Move Down to change its location on
the list.
Radios | 59
You can repeat the above procedure and create various ranges that include a desired set of
talkgroups.
Scan Lists, DMO Groups

Same As TMO Groups for scan lists and DMO groups. Mark the checkboxes of the groups that
this radio will be entitled to use. The displayed list contains the items assigned to this radios
customer.
DMO Ranges
Same as TMO ranges for DMO groups.
Failover
You can establish correspondences between talkgroups and DMO groups to provide for
automatic switching from one communication mode to the other in case of network failures. For
example, you can define talkgroups that will automatically switch to DMO mode in case the
network servicing the talkgroups becomes unavailable. The opposite is also permitted: DMO
groups can be defined to automatically switch to regular talkgroup mode if and when the DMO
infrastructure fails.
To map groups for failover:
1.
Select the Failover tab.
This page lists the TMO and the DMO groups that have been selected for this radio.
2.
In TMO Groups and in DMO Groups select one row on each side.
3.

To cause the selected talkgroup to switch to the selected DMO group in case of failure,
click the
button.
To cause the selected DMO group to switch to the selected talkgroup in case of failure,
click the
button.
Radios | 60
To cancel a previously established correspondence (in any direction) between the

selected talkgroup and the selected DMO group, click the
button.
Identity
This tab shows the basic identification details that you entered while creating the new radio
record.
You can complete missing items and modify editing data.
Finalizing the Configuration and Activating the Radio

To activate the radio now, click the Activate button. Clicking the Activate button both saves the
data and activates the radio.
To save the data without activating the radio, click the Submit. You can activate the radio later.
See Activating a Radio on page 61.
When you click Submit, the configuration (and activation, if you clicked Activate) request is sent
to a queue and then to the FNE. All the information enters into effect after the FNE
acknowledges its validity.
Activating a Radio
Activating a radio means allowing it to communicate on the network. Only configured radios
can be activated.
If you have not activated a radio during the configuration stage, you can activate it by following
this procedure:
1.
Click the Customers option and select the customer who owns the radio.
2.
3.
Select a radio.
4.
From the menu select the Activate command.

This command is enabled only if the radio has been configured.
Radios | 61
The Activation page appears, displaying the radio configuration parameters.
5.
Click the Activate button located at the bottom of the page.
Activating a radio using the above method or while configuring the handset does not
immediately cause the radio to be active on the network. MiBAS sends the activation request to
the FNE; the radio becomes active after the FNE acknowledges the validity of the configuration.
On the Radios list the status of a radio not yet acknowledged by the FNE is "Activation". For
active radios no status indication is displayed.
Sending the Configuration Data to the Radios

All of the configuration data entered in MiBAS should be downloaded to the individual radios.
You first need to prepare a template for each radio brand and model on your network. There
may be multiple templates for a certain brand/model, each serving different subscriber groups.
Templates are built using the Customer Programming Software (CPS). The template files should
be placed in the following folder on a computer to which MiBAS has access: C:\tetra\templates
To send the configuration data to a radio:
1.
Click the Subscribers & Accounts option and select the subscriber who needed to be
programmed.
2.
From the menu, select the Download CPS File command.
3.
Select a template and click the Download CPS File button.

Repeat this step for the various templates to be assigned to the different radios.
Radios | 62
This operation adds to the template general configuration elements such as talkgroups and
scan lists (hotfix).
4.
On the computer running the CPS system, connect the radio to the computer and transfer
the appropriate template to the radio.
Creating a Radio by Replication

The duplication feature allows you to quickly create a radio by copying to an inventory device
the services of an existing radio.
To create a radio by duplication:
1.
Display the inventory list and select a device.
2.
From the side menu, select Replicate Subscriber.

The Replicate Subscriber page opens.
3.
In Subscriber Search, run a search to find the radio the services of which you want to copy.
4.
After selecting the radio in the search results, do one of the following:
If the copied configuration does not need to be modified, click the Submit button.
If you want to make adjustments in the copied configuration, click the Submit and
Configure button to access the configuration details.
Modifying the Radio Configuration

To access the radio configuration parameters and change them:
1.
2.
Click the Subscribers option to list this customer's radios.
3.
Select the radio whose configuration you want to modify.
4.
Click the Modify button to access the configuration parameters.
5.
Change the values you want.
Radios | 63
If you add a new service that requires an address, the address will be automatically
allocated (Allocate Numbers is checked and cannot be cleared, meaning that the number
will be allocated automatically). However, you can click the
button and enter the
address manually.
Note that the activation checkbox is not available here. You can deactivate or reactivate a
radio via the Suspend/Resume command.
6.
Changing Ownership
The change ownership feature is used to transfer a device to another customer or to withdraw
the device from service.
To change device ownership:
1.
Access the device.
2.
From the menu, select Change Ownership.
3.
In To customer, click the
4.
In Account ID, select one of the following options:
5.
button to select the new owner.
Option
Description
New
Assigns a new account ID to the receiving subscriber. The

account ID used by the previous subscriber goes to a special
pool. That customer (the old one) can always reuse that ID for
a new unit.
Keep
Copies the account ID to the new owner.
Replacing a Device
You can replace a device by one of the devices in the inventory.
The replacement operation does the following:
Copies the deficient devices configuration to the new device.
Radios | 64
Activates the new device automatically.
To replace a device:
1.
In the Inventory List, click the Device ID link of the new device.
Note that if you select a device that has been configured, its configuration will be lost; it
will be replaced by the configuration of the replaced device.
2.
Select the Replace command on the menu.

The Replace page appears.
3.
In Search subscriber to be replaced run a search to find the old device.

When the device is found, its details appear in the fields under Subscriber to be
replaced. Check the details and make sure that you are replacing the correct device.
4.
Refreshing Radio Data in the FNE

Should discrepancies materialize between the radio data registered in the FNE and the radio
data stored in the MiBAS database, you can replace the details registered in the FNE with the
details that are available in the MiBAS database. To do so:
1.
2.
Click the Subscribers option to list this customer's radios.
3.
On the displayed list, click a subscriber.
4.
Select the Refresh command on the side menu.

The Subscriber Refresh page opens. It contains a list of the FNEs where this radio is
provisioned.
Radios | 65
5.
Check the boxes of the FNEs to refresh.
6.
Suspending and Resuming Radios

Sometimes the need may arise to suspend a radio and then resume it after the problem that led
to the suspension has been resolved. This section explains how to suspend and resume a radio.
To suspend a radio:
1.
2.
Click the Radios option to list the radios of the selected customer.
3.
Click the radio to suspend.

The Radio Card of the selected radio appears.
4.
From the menu select the Suspend command.

The Suspend Radio General Details page opens, displaying the details of the radio to
suspend.
5.
In Reason, select a reason that explains why the radio is being suspended.
6.
Click Submit.
Radios | 66
The Suspend Radio Confirmation page opens, displaying the full details of the radio for
which the suspension request has now been submitted.
7.
Click OK to return to the Radios list.
To resume a suspended radio:

1.
2.
Click the Radio link to list the radio of the selected customer.
3.
Click the radio to resume.
4.
From the menu select the Resume command.

The Resume Radio General Details page opens, displaying the details of the radio to
resume.
5.
Click Submit.
The Resume Radio Confirmation page opens, displaying the full details of the radio for
which the resumption request has now been submitted.
6.
Click OK to return to the Radios list.
When you return to the Radios list, the Service State field indicates that the request is being
processed and the radio record appears against a gray background. When the request is
finalized, the status is not updated automatically. You need to refresh the page once in a while to
see the current status. To do so, click the Refresh link on the page (and not the Refresh button of
your browser).
Deleting a Radio
When you delete a radio all of its addresses are automatically restored to the pools from which
they have been taken.
To delete a radio:
1.
Select a customer and display its customer card.
2.
Click the Inventory or the Subscribers option.
3.
Select a radio.
4.
From the menu select the Delete command.
Radios | 67
The Delete page appears.
5.
In the Reason field select the reasons why this radio is deleted.
You must select a reason on each list
6.

If you deleted an inventory item, the radio is removed from the customer's inventory.
If you deleted an active radio, the deletion request is sent to the FNEs where it is
provisioned. The radio entry will disappear from your lists after FNEs approve the
operation.
Deleting a Group
To delete a group, you will run a search in order to first display the group card.
To delete a group:
1.
Access a customer, a radio, or an inventory item.
2.
In Search for select the group type.
3.
Enter the group ID and launch the search.

The group card appears.
4. From the menu, select the Delete command.
Radios | 68
6
Inquiries
This chapter reviews the MiBAS inquiries. It explains the procedure common to all inquiries
and the inquiry-specific steps.
To access the inquiries select the Customer Care tab.
Customer Report
The customer report presents a list of the current radio users and radios of a customer, including
the removed ones.
To produce a customer report, follow these steps:
1.
Access a customer and display its customer card.
2.
From the menu click the Customer Report option.

The Customer Report page appears.
3.
Select the customers to print as follows:

Option
Description
All
Prints all customers.
Current User
Prints the customer records created by the user running this

report.
Enter User Filter
Prints the customer records created by a MiBAS user. Enter

the username in the box.
Inquiries | 69
4.
To further limit the customer population you selected in the previous step select one or
more of the following:
5.
Option
Description
Service Status
Prints only those customers that are in a certain service

status. Select the status.
From/To Activation
Date/Time
Prints only those customer that have been activated in a

selected period. Specify the start date/time and the end
date/time of the period.
If the customer has a large number of subscribers, you can limit the number to retrieve by
entering the number in Maximum Subscribers to Retrieve.
For each radio user or radio the following information is provided:

Account ID
For accounts, displays the account ID.

Serial Number
Displays the radio's serial number.

Alias
Displays the name of the radio holder.

Model
Displays the model of the radio.

Purchased Services
Displays the services assigned to the radio. Click the

detailed view of the services.
button to see a more descriptive and
Status and Date
Displays the current status of the radio user, as follows:

N
means New.
means Connected.
means Disconnected.
means Removed
Next to the status letter, MiBAS displays the date at which the radio user assumed that current
status.
TK Groups
For radio users, lists the IDs of the talkgroups to which the radio user belongs.
Customer Events
This inquiry lists operations that have been applied to customers during a given period. For
example, you can produce a list of customer deletions performed in the past week.
Inquiries | 70
To produce a customer events report:

1.
Select the customer.
2.
From the menu, select Customer Events.

The criteria selection page opens.
3.
In the Operations column, select the operations you want to list.
4.
In Starting, select the extent of the history to retrieve in terms of x months or x events back.
5.
Click the Retrieve button to display the results.
Mass Operations List

This inquiry lists the mass actions that have been executed for a specific customer or for all
customers.
To display the mass operations list:
1.
To access the mass actions executed for a specific customer, find the customer and from the
menu select Mass Operations List.
To access a list of all mass actions executed in MiBAS, after logging in to MiBAS select
Mass Operations List from the menu.
The inquiry displays the following information:
Inquiries | 71
2.
Column
Description
Operation
The mass operation that was executed.
Start Time
The date and time when the operation started.
End Time
The date and time when the operation was completed.
Results
Indicates whether or not the operation was successful.
Total Request
Count
The total number of mass action requests.
To display detailed information about a certain mass operation, click the row you want.
This displays the Mass Operation Report.
The upper section displays summary information and the lower section lists the entities
that participated in the mass action. Clicking a row, lists the record of the corresponding
entity.
Inquiries | 72
7
Security
This chapter explains how to define users authorized to access MiBAS and how to define their
permissions.
The MiBAS Security Concept

The MiBAS security module is designed to define the users who are permitted to access MiBAS
and to perform operations in MiBAS. Each MiBAS user can have a different set of permissions.
For example, one user may be authorized to provision radio users while another can be
authorized to only view provisioning data (without the permission to change it).
The sets of permissions are called groups.
Delegation
The delegation feature is optional.
An important aspect of the MiBAS security concept is its ability to delegate authority. The
network operator can permit its customers to directly access MiBAS and to perform operations.
A customer, for example, can be allowed to replace radios within its own organization without
the network operators intervention.
Based on the same principle, authorizations can be further delegated to individual radio users.
For example, the radio user can add or remove services instead of going to a customer service
station in order to modify the service configuration.
In principle, the security module allows authorizations to be delegated in an unlimited number
of levels: the network operator can delegate rights to its customers, each customer can delegate
rights to some other entity under its control (for example, a large customer organization can
delegate MiBAS rights to its departments), and so on. In practice, however, it is recommended
not to let customers delegate rights further down in the authorizations line.
One exception to this rule is the private user. Only the network operator can delegate rights to a
private user.
Delegation is implemented by simply granting limited rights to the lower level. Thus, the
network operator delegates to its customers the right to perform MiBAS operations but not all
possible operations. In this case too, the private user is an exception: a private user can be
granted only permissions from a pre-defined set of permissions especially defined for this
purpose.
Index | 73
Groups and Users

The combination of the group/user feature and the delegation feature yields the following
types of groups and users:
The main domain group and the main domain administrator. MiBAS is supplied to the
network operator with one main domain group and one main domain administrator definition.
The main domain group includes permissions to all possible operations in MiBAS and,
therefore, the global administrator can perform all possible operations in MiBAS.
The customer domain group and the customer domain administrator. This is relevant if the
network is willing to delegate MiBAS access rights to customers. An authorized main domain
user can define a customer domain group (and administrator) that includes the permissions that
the network operator is willing to delegate to the customer.
Corporate groups and users. These are the regular groups and users of the organization (the
network operator or customer organizations) and they are designed for the regular distribution
of tasks within the organization. For example, one corporate group would include the
permission to provision radio users while another would be permitted to only view data. The
main domain administrator defines the groups and users needed in his organization (the
network operator) and the customer domain administrator does the same for his own
organization.
Private users. Users of the main domain who have the authority to delegate rights to a lower
level may grant individual radio users the necessary permissions to administer their handset(s).
Like any other MiBAS user, private users can access MiBAS using their Web browser and
perform the operations they have been authorized to perform.
Accessing Security
To access the security tool
On the MiBAS home page, click the Security tab.

The Users list is displayed. The first time you open it, it is empty.
Defining Groups
To start a group definition
1.
In the Users List, click the Groups button (below the Search bar).
The Groups list is displayed.
Index | 74
2.
In the Groups List, select the Add New Group command from the menu.
The Add New Groups: Main Details page opens.
Main Details
1.
Enter the following information:

Group Name
Type a name for the group.

Owner ID (Customer ID)
If this is a local group, skip this field.

Optional delegation feature: If this is a customer domain group, type the customer ID of the
customer to which you want to delegate rights.
Public
Check this box to make the group public; clear it to make the group private.
All users can view the details of public groups (but cannot change details). Private groups
are visible only to the users who have created them.
Description
Type a few words that describe this group.

2.
Click the Next button.

The Functional Permissions page opens.
Index | 75
Functional Permissions
In the Functional Permissions page you define the MiBAS functions that this groups members
(users that will be assigned to this group) can access. The Functional Permissions page lists the
functions that have been assigned to the group to which you belong.
Originally, all displayed functions are enabled. You determine this groups permissions by
removing functions.
1.
Clear the boxes of the functions you want to withdraw from this group.
If necessary, expand a function branches by clicking their
branch.
icon. Use
to collapse the
When you check/clear a parent box, all descendant functions are automatically
added/withdrawn.
2.

This Displays the Data Access Permissions page.
Index | 76
Data Access Permissions

In the Data Access Permissions page you determine:
The customers that this group will be entitled to handle.
The templates that the members of this group can assign to radio users, that is, the services
they can allow the radio users to use.
The Data Access Permissions page that appears now may include a Customer List or just the
Customer ID field (no customer list). The following figure illustrates a page that includes the
Customer List section. The difference is explained below.
1.
If you are a user who has access to all the customers defined in MiBAS, the Customer ID
field appears.
Otherwise, the Customer List appears.
Customer ID case: Type the ID number of the customer and click the Add button to grant
permission to access it. Repeat this step for all the customers the members of this group
should have access to. To allow the members of this group to access all the customers you
have access to, just type * (an asterisk) in the Customer ID field and click Add.
Customer List case: In Customer List, click a customer and then Add button.
In both cases, the customer ID you typed or selected from the list appears in Attached
Customers. The members of this group will be allowed to handle only the customers that
appear in Attached Customers.
You can withdraw a permission to a customer, by clicking it in Attached Customers and
then the Remove button.
2.
Do the same in Available Templates.

The member of this group will be allowed to assign to radio users only the templates that
appear in Attached Templates.
3.

This displays the Confirmation page.
Add New Group Confirmation

The Confirmation page provides a summary of all your selections, including the functional
permissions and the data permissions.
Index | 77
Click the OK button to exit the wizard and return to the Groups List. The new group appears on
the Groups List.
Modifying Group Definitions

MiBAS allows you to access a group and modify its settings.
To modify group definitions
1.
Click the Security tab.

The Users List is displayed.
2.
In the Users List, click the Groups button (below the Search bar).
3.
Click the Group ID link of the group you want to access.

This activates the group definition wizard. You can move from one page to another, using
the Next/Previous buttons, and modify the settings you want.
You cannot change the group name and the customer ID for the customer domain user.
4.
Click Submit in Data Access Permissions page to save your changes.
Index | 78
Deleting a Group
To delete a group definition
1.
2.
Click the Groups option.

3.
Click the Group ID link of the group you want to access.

The Group Details page appears.
4.
Select the Delete Group command on the side menu.

The Details Check page opens allowing you to have a last look at the details of the user to
make sure that this is the one you want to delete.
5.
Click the Delete Group button.

The Confirmation page appears.
6.
Click OK to return to the Groups list.
Adding New Users

To start a user definition
1.
In the Users List, make sure that the Users button is selected (below the Search bar).
2.
If this is a corporate user or a customer domain administrator, select the Add New User
command from the menu.
If this is a private user, select Add Private User.
Index | 79
Depending on what you have selected, the Add New User or Add Private User (Main
Details) page is displayed.
Main Details
1.
Enter the following information:

User ID
Enter an ID number for the user.

First Name
Type the first name of the user.

Last Name
Type the last name of the user.

User Name
Specify the user name that the user should specify in order to access MiBAS.
Password
Specify the password that user should specify in order to access MiBAS.
The password may include only digits and must be at least 5-digit long.
Repeat Password
Type the password again to confirm it.

Description
Type any notes you want about this user.
Index | 80
Locale
Select the language in which you want to present the Web Access pages to this user.
This is relevant if your MiBAS installation supports multiple languages. For example, if
you have MiBAS interface pages developed in French, you would select an option such as
French.
Customer Group
If this is a corporate user, skip this field.

Optional delegation feature: If this is a customer domain administrator, the relevant customer
domain group.
E-Mail
Type the e-mail address of the user.

Phone
Enter the telephone number where the use can be contacted.

Day of Birth
Specify the birth date of the user.

Address
Specify the home address of the user.

2.

For users who are not private users, the Groups page appears.
Groups
If this is a customer domain administrator, skip this section. The customer domain administrator
has already been assigned to the corporate administration group (in Main Details) and therefore
his permissions have already been set,
Use this page if the user is a corporate user, in order to set his permissions. This done by
assigning him to one of more groups.
1.
Select a group in Available Groups Lists and click Add.

This moves the group to Attached Groups.
Index | 81
2.
Repeat this step for all the groups to which you want to assign this user. You can withdraw
permissions by clicking a group in Attached Groups and then the Remove button.
3.
Click Next.
The Functional Permissions page opens.
Functional Permissions
1.
If this is a customer domain administrator, skip this section.

If this is a corporate user, the permissions granted to the corporate user via the groups he
is associated with appear checked. You can change the permissions.
If this is a private user, a limited set of permissions that can be granted to such users
appear.
Withdraw or assign permissions by clearing and marking checkboxes. The process is the
same as the one described for groups.
2.
If this is a private user, click Submit.

For other types of users, the Next button appears. Click it to move to the Data Access
Permissions page.
Data Access Permissions

1.
If this is a customer domain administrator, skip this page.

On this page the customers and templates assigned to this corporate user via his
associated groups appear on the right side of the page.
On this page too you can fine-tune this corporate users customer access and template
usage permissions by adding and removing templates. The process is the same as the one
described for groups.
2.

Index | 82
User Confirmation
The Confirmation page displays a summary of your definitions.
Click the OK button to exit the wizard and return to the Users List. The new user appears on the
Users List.
Modifying User Definitions

MiBAS allows you to access all types of users and modify their settings.
To modify user definitions
1.

The Users List is displayed.
2.
Click the User ID link of the user you want to access.

The User Details page appears listing all the information recorded in the user record.
Index | 83
3.
Select the Modify User command on the side menu.

This activates the user definition wizard. You can move from one page to another, using
the Next/Previous buttons, and modify the settings you want.
The user ID cannot be changed.
4.
Click the Submit button in Data Access Permissions page to save your changes.
Deleting a User
To delete a user definition
1.

The Users list is displayed.
2.
Click the User ID link of the user you want to access.

The User Details page appears.
3.
Select the Delete User command on the side menu.

The Details Check page opens allowing you to have a last look at the details of the user to
make sure that this is the one you want to delete.
Index | 84
4.
Click the Delete User button.

5.
Click OK to return to the Users list.
Index | 85
8
Utilities
To chapter covers the auxiliary MiBAS tools.
Mass Actions
The mass action utilities allow you to perform certain operations on a large number of items in a
single action. These are the same actions that you can perform on individual items, such as
activating or suspending subscribers.
To perform a mass action you need to select the population to which you want to apply the
action. For example, to delete a number of a devices in a single operation, you first need to build
a list of the devices to delete. This section explains how to select the population.
Selecting a Population for Mass Actions

This section explains how to select the customers or subscribers that will participate in the mass
action.
To select the mass action population:
1.
Find the customer.
2.
Click the Subscribers & Accounts or the Inventory option on the options bar.
This displays the subscribers or the devices list.
3.
Mark the checkboxes of the subscribers or devices to which you want to apply a mass
action.
If the list is too long and the items difficult to find, you can select the population later,
using the search tool described below.
4.
Click the Menu entry below the search bar, in order to open the menu.
5.
Select the Mass Actions command.

The Mass Actions page opens.
Index | 86
The lower half of the page lists the subscribers or devices that you have selected in the
previous page and to which the mass action will be applied.
6.

To include all subscribers/devices: Select the All Subscribers box, to apply the action to all
the subscribers/devices of the selected customer. Selecting this option grays out the
selected rows in the lower section, meaning that all subscribers/devices will participate in
the mass action.
To include individual subscribers/devices: In "Search by" select, for example, Account ID
and in the adjacent field enter an account number in order to add the corresponding
subscriber to the mass action.
Some search criteria, such as member ID, includes two data entry fields to specify a range
of values (from/to member ID, from/to telephone number, and the like).
In the value field(s) you can specify partial values and use the wild card character (*) in
order to retrieve all the records that include the partial value. You can place the * anywhere
in the partial value. Entering * only retrieves all the relevant records.
To include by services: The "Search by" tool allows you to include in the mass action all
subscribers that have a certain principal or additional service. After selecting one of these
options (for example, Principal Service) in the adjacent field enter the mnemonic of the
service (e.g. DISPATCH).
To exclude by services: In "Search by" select Principal Service or Additional Service, and
in the adjacent field enter the mnemonic of the service to exclude. This displays the
Exclude checkbox.
Check the box in order to include all subscribers, except for those that have the specified
service.
Complex search. You can also run a complex search by specifying multiple search criteria
expressions. To add another expression, click the button and make another criteria
selection. Clicking the button removes the corresponding expression. The expression are
linked with AND.
7.
Click the Search button to execute the search (or click Reset to cancel your selections).
Index | 87
The accounts that meet the search criteria are automatically added under the Main tab.
The search covers only the subscribers or devices associated with the selected customer.
You can repeat the search procedure as many times as you want to select more subscribers
or devices.
Additional information for each account (services, addresses, groups, etc.) is provided
under the other tabs.
8.
Under the tabs, you can fine-tune the list of selected items by clearing the selection boxes
of those items that you want to exclude from the mass action.
For example, you can use the Services tab to view the services associated with the specific
account. This may help you exclude an account that has a specific service that you do not
wish to involve in the mass action. Clearing a box excludes the account and not all the
accounts that have that service.
You can also quickly de-select large numbers of items by selecting an option in the dropdown list located in the upper-right corner of the lower section. For example, when using
the Subscribers-Mass Action option, you can select Suspended in order to exclude all
subscribers that are not suspended (to clear the checkboxes of all non-suspended
subscribers).
Printing Population Selection Results

After establishing the population you can produce a report that presents the details of the
selected accounts to keep a hard copy of the information or for other administrative and
referential purposes.
To produce a population report:
1.
Select the population to be included in the report.
2.
Form the top menu, select Subscriber Report.
Mass Configuration Changes

This function allows you change the subscriber configuration for multiple subscribers/devices
in a single operation. A special function in this context allows you to copy configuration settings
from one subscriber to many others.
To perform configuration changes:
1.
2.
Click the Subscribers & Accounts or the Inventory option.
3.
Select the Mass Actions option and then select the population.
4.
Open the top menu and select Configure.

The list of the selected subscribers/devices appears. The lower half of the page presents
the configuration options.
Index | 88
You can exclude some items by clearing their selection checkboxes.

5.
In this page you can apply the following operations to the selected records:
Change their template: Select the Template radio button and in the drop-down list select
the new template. Click the Apply button.
Replace their configuration with the configuration of a specific subscriber/device: Select
the Subscriber radio button, run a search using the search tool, select the subscriber in the
Subscriber Search box, and click Apply.
Add or withdraw services: In the lower section select a tab (and, if applicable, a secondary
tab under the main one), and then select the Add radio button for the services you want to
add or the Delete radio button for the services you want to withdraw.
To allocate addresses to an added service, click the Starting Address icon and run the
relevant search. Then, in the Search Result list select the first address to allocate. MiBAS
automatically allocates the addresses to the selected subscribers, starting from this
address.
Some services may be dependent on the existence of other services. In such cases their
Delete radio button is grayed out, meaning that you cannot remove them independently.
6.
Index | 89
Mass Exchange of Member IDs

A MiBAS utility allows you to swap dispatch member IDs among subscribers.
To swap member IDs:
1.
2.
Click the Subscribers & Accounts option.
3.
4.
Open the top menu and select the Exchange Member IDs command.
The Exchange Member IDs page opens.
5.
Click a row and then another row to swap their member IDs.
The new IDs appear in Requested Member IDs (and the old IDs appear in Member ID).
Alternatively, you can search and select a member ID for a specific subscriber: click the
button and perform the search.
Repeat this step as many times as needed. You can cancel all changes by clicking the
Refresh button.
6.
Mass Changes of Serial Numbers and Holder Names

This action is designed to list a selected population of devices and to access the serial number
and/or the holder name of each device for manual changes.
To modify serial numbers and/or holder names:
1.
2.
3.
4.
Open the top menu and select Modify Parameters.

The list of the selected items appears, with the Serial Number and Holder Name fields.
Index | 90
You can change the sorting order of the rows by clicking the heading of a column.
5.
In Serial No or in Holder Name, type the numbers or names you want.
6.
Mass Ownership Changes

One of the mass actions allow to massively transfer multiple subscribers from one customer to
another.
To perform a mass ownership change:
1.
2.
3.
4.
Open the top menu and select Change Ownership.
5.
In Account ID, select one of the following options:

Option
Description
New
Assigns a new account ID to each transferred subscriber. The

account IDs used previously goes to a special pool. That
customer (the old one) can always reuse those IDs.
Index | 91
Option
Description
Keep
Moves the account IDs to the new customer.
6.
In To customer, use the search tool to find the new customer, and select it.
7.
Check the Save Billing Attributes box if you want to also transfer the billing attributes
associated with the subscribers.
8.
Mass Activations
MiBAS allows you to activate a number of devices in a single action.
To massively activate devices:
1.
2.
3.
4.
Open the top menu and select Activate.

A page appears that lists the items to which the mass action will be applied. You can still
exclude items by clearing their selection boxes.
5.
Click the Submit button to initiate the mass action.
Mass Suspensions
You can suspend a number of subscribers in a single action.
To massively suspend subscribers:
1.
2.
3.
4.
Open the top menu and select Suspend

The Suspend page appears that lists the items to which the mass action will be applied.
Index | 92
5.
You can still exclude items by clearing their selection boxes.
6.
The page that appears now may also include fields for selecting the reason of the
suspension. In such cases, select the reason(s). For details about the reasons fields, consult
for MiBAS system administrator.
7.
Mass Resumptions
You can resume a number of subscribers in a single action.
To massively resume subscribers:
1.
2.
3.
4.
Open the top menu and select Resume.

The Resume page appears that lists the items to which the mass action will be applied.
5.
You can still exclude items by clearing their selection boxes.
Index | 93
6.
Mass Deletions
MiBAS allows you to delete a number of subscribers or devices in a single action.
To massively delete subscribers or devices:
1.
2.
Click the Subscribers & Accounts or the Inventory option.
3.
4.
Open the top menu and select Delete.

The Delete page appears.
5.
The Delete page may also include fields for selecting the reason of the deletion. In such
cases, select the reason(s). For details about the reasons fields, consult for MiBAS system
administrator.
6.
If you are deleting subscribers, check the Keep Devices checkbox in order to return their
devices to the Inventory list where they can be reconfigured. Clear the box to delete the
device from MiBAS. The latter option would apply to devices that become unusable.
7.
The lower section lists the items to which the mass action will be applied. You can still
exclude items by clearing their selection boxes.
8.
Mass Action Status

Mass actions are not executed immediately. When you click the Submit button, processing
begins, which may take some time to complete. When you submit a mass action, the
Confirmation page displays the transaction ID, through which you can view the current status
of the actions.
Index | 94
To access the status report, click the Transaction ID link. This opens a report that specifies the
outcome of the procedure. If this is a mass action, the report also lists the records that
participated in each action with a status indication for each.
The report provides the following information:

Completion Time, Refresh
If a date appears, this indicates that the operation has been completed. If the operation is not
complete yet, use the Refresh button to see the most updated information.
Results
Indicates the outcome of the operation.

Total Request Count
Indicates the number of items that have been processed. For example, in a mass operation this
would be the number of items included in the selected population.
Failure Message
In case of failure, point to this field to display an explanation of the failure.
Index | 95
9
Interface Controller
All interfaces are monitored and managed centrally, from the FNE Queues application of the
MiBAS Web Access.
Accessing FNE Interfaces

To access FNE interfaces:
1.
Open your Internet browser and log on to MiBAS Web Access.
2.
Click the FNE Queues tab.
3.
Select the Interfaces option.

The Monitor Interfaces page opens, listing the currently defined interfaces.
Use of Dimetra FNEs as an example:
The list presents the information described below. Click any column header to change the
column sorting accordingly.
Index | 96
Instance ID
The unique identifying number of the interface instance. MiBAS may have multiple interface
instances communicating with the same FNE.
Description
A description of the instance.

FNE
The network element to which this instance interfaces MiBAS.

Status
The current status of the instance. The options are:

Option
Means
Active
The interface is currently working normally.
Failed
Interface start or shutdown failed and the

interface aborted abnormally.
Suspended
The interface is not currently running.
Operation Mode
An instance can be working in normal production mode or in simulation mode. The simulation
mode is used in testing environments: requests are sent to the interface and processed without
actually being directed to an FNE.
Activating Interfaces
You need to activate suspended interfaces so that MiBAS can send requests to the network
elements.
To activate interfaces:
1.
On the Monitoring Interfaces page, select the interfaces to activate, by checking their
checkboxes on the leftmost column.
Use the Select All link, to select all of the interfaces in a single operation. Use the Deselect
All link to clear all markings.
2.
On the menu that appears on the left, click the Activate button.
The Activate Interfaces page appears, listing the FNEs you have selected for activation.
Index | 97
3.
Click the Activate Interfaces button to activate the interfaces.

A successful activation changes the interfaces Status field to Active.
Use Dimetra interfaces here in the whole chapter of controlling interfaces
Suspending Interfaces
Interfaces must be active at all times to ensure uninterrupted service. However, if you need to
stop sending requests to a specific FNE, you can suspend the interface.
To suspend interfaces:
1.
On the Monitoring Interfaces page, select the interfaces to suspend, by checking their
Use the Select All link, to select all of the interfaces in a single operation. Use the Deselect
All link to clear all markings.
2.
On the menu that appears on the left, click the Suspend button.
The Suspend Interfaces page appears, listing the FNEs you have selected for suspension.
3.
Select one of the following suspension options, by clicking the corresponding button:
Click
To
Suspend on Idle
Suspend the interface after carrying out all of the

requests waiting on the FNEs queue.
Suspend on Next
Suspend the interface after it finishes processing

the current request and before going to the next
request on the queue.
Suspend Immediately
Suspend the interface without any delay.
Viewing and Updating FNE Details

FNE details consist of such data items as the IP address and the port number at which the
interface communicates with the FNE, and the user name and password needed to access the
FNE. You can view and update this information.
To view and update FNE details:
1.
On the Monitor Interfaces, click the Instance ID link of the FNE to view or edit.
Index | 98
The FNE Card appears.
2.
To modify any of the details that appear on the card, click the Update button on the left.
This opens the card fields for editing and the page title changes to Update Interface Values:
Main Details.
3.
Change the values you want.

See details below.
4.
Click the Update Values button to save you changes.
You can view and modify the following FNE details:

Description
Type a description that describes the interface briefly but accurately. The description helps you
identify the interface instance on various pages.
IP Address
The IP address of the FNE with which this interface communicates.

FNE Port
The port at which the FNE listens to the interface.

User Name, Password
The user name and password the interface needs to access the FNE.
Operation Mode
If necessary, you can change the operation mode (Simulate or Normal) from here).
Status
If necessary, you can change the status to Active or Suspended, from here.
Measuring Request Traveling Times

You can measure the time it takes a request to travel from the database to the network element
and back. Use this feature to check the source of any delays you may experience sending new
requests to the FNEs.
The measurements appear in the interface log reviewed in Viewing Logs on page 100.
To measure request traveling time:
Index | 99
1.
On the Monitoring Interfaces page, select the interfaces to test, by checking their
2.
On the menu that appears on the left, click the Start Measuring button.
3.
Click the Start Measuring Requests button.
The measuring process continues until you click the Stop Measuring button on the menu and
then the Stop Measuring Requests button on the main details page.
Refreshing the Monitor Interfaces View

The information displayed on the Monitor Interfaces page reflects the state of the system as it
was when you opened the page. Click the Refresh link to view the current situation.
Viewing Logs
The View Logs command on the menu pane allows you to formulate a query in order to retrieve
a specific population of log entries from the MiBAS-FNE interface log.
To query the log and display results:
1.
Click the View Logs command on the menu pane.

The Logs Specification page opens.
2.
In FNE select one of the following:
Index | 100
Select
To view
FNE name
The log entries posted for a specific FNE.
Supervisor
The control entries.
3.
If you selected an FNE name in FNE, in Instance ID select a number to view the log entries
relating to a specific instance, or select All to view log entries relating to all the instances of
the selected FNE.
4.
In Show results only for select one of the following options.

Option
Description
FNE Key
Select this option to view log entries relating to a

specific subscriber. In the adjacent box specify the
data item that identifies the subscriber. For
example, a telephone number limits the retrieved
logs to the log entries relating to that telephone
number.
Status
Select:
Confirmed
To view log entries that reflect
success (all types of success and not only those
relating to successfully handled requests).
Reject To view log entries posted for requests
that have been rejected by the FNE.
Exception
To view log entries that reflect
failure (opposite of Confirmed).
Transaction ID
Not in use.
Queue ID
Each log entry is identified by an identification

number that identifies the queue through which
it was sent to the FNE. Specify the queue ID to
limit the retrieval to log entries relating to a
specify queue.
5.
In Time Stamp, you can limit the retrieved information to events that were logged between
certain hours. You must enter a start time in the From field. If you want to limit the period
to an end time, check the To box and enter the time.
6.
Click Go.
The Log Content page appears, listing the retrieved log entries.
Index | 101
The Log Content column describes the reason that led to the creation of the log entry. If
necessary, click the
link to expand the field to display the entire description.
Index | 102
10
Queues
Operations that require updating the FNEs, such as provisioning a handset with a certain
service, are placed in queues from where they are gradually sent to the FNEs. Requests that
cannot be processed are rejected. Rejected requests are kept in separate queues. Requests that
are processed successfully are transferred to the audit tables.
Accessing Queues
To access the queues:
1.
Open your Internet browser and log on to MiBAS Web Access.
2.
Click the FNE Queues tab.
3.
Select the Queues option.

The Show Queues Count page opens, listing the queues.
The UCS entry shows the pending requests (not sent to the FNEs yet) and the Completion entry
shows the requests that have returned from the FNEs. When requests are returned to the
Completion queue, they undergo one last process (a database cleanup process). A successful
processing of requests in the Completion queue removes them from the queue.
The Queued column shows the number of pending (UCS) and successfully returned
(Completion) requests. The Rejected column shows the number of requests that have been
rejected by the FNEs (UCS) and the number of requests that failed the completion stage
(Completion).
After opening the Show Queues Count page, the Queued and Rejected counters are not
updated automatically. Click the Refresh button once in while to get the latest count.
Finding and Viewing Requests

You can access the actual requests using one of the following methods:
Click on a number in the Queued or Rejected column, in the Show Queues Count page.
Index | 103
Search. For example, in Search For select Subscriber Queues, in By select UCS and in FNE
Instance specify the instance to access all requests queued for sending to the specified
instance.
The Search For=Subscriber State option allows you to find a specific request and see where
exactly it is currently waiting. When you select Subscriber State, you can fine-tune the
search by specifying, for example, the subscriber's phone number or IMEI in order to
pinpoint the relevant requests.
After entering the search criteria, click the
button.
The page that opens displays one request per row. The results change according to the method
you have used to find the requests. For example, if you used Search For=Subscriber State,
MiBAS returns (if the request is a pending request) all FNE queues where the request is
currently waiting. If you click a number in the Show Queues Count page, MiBAS returns all the
requests included in the selected queue.
Handling Pending Requests

In the page that lists the requests (its name changes according to what you have selected), you
can do the following:
Click the Refresh button once in a while to see an updated list of the requests.
If a request consists of one or more individual commands, the button appears in the
leftmost column. You can click it to display the queued commands.
Index | 104
Pending requests may cause the interfaces to fail. If some pending requests remain on
queue for a relatively long time and interface failures keep occurring, you can try to solve
the problem by locking the problematic requests. Locked requests are excluded from the
processing cycle and the next time the interfaces run, they (the requests) are ignored. To
lock a request, click its blue lock, in the Lock column, and then click the Apply Changes
button. The lock turns red. To handle locked requests, contact MiBAS Support.
The queued requests are processed in the order in which they have been queued. If you
want MiBAS to process a request before others are, you can change its priority. To do so,
type a number in the request's Priority field. The higher the number the higher the
priority.
Handling Rejected Requests

In rejected requests queues you can do the following:
Rejected requests can be viewed by selecting the Rejected link (the number) in the
Show Queues Count page or using the Search tool. Such requests contain the following
options (appear on the leftmost column):
None: Select this option if you do not want to handle this request now.
Resend: If you have corrected the error that triggered the rejection, select this option to
resend the request to the FNE.
Accept: Select this option to accept the request as correct (as if it were accepted by the
FNE).
Requests may be rejected by just one of the commands they include. To exclude the
problematic command from the processing, change its tuple state from R to C and then
resend the request.
Audit Queues: Request History

Once a request is finalized successfully, that is, once it disappears from the Completion queue, it
is transferred to the Audit queue. The Audit queue is not really a queue in that it does contain
requests that need to be handled; it is a history of the requests that moved through the queues
in the past. MiBAS allows you to access the subscriber events that took place in the framework
of the different requests stored in the Audit queue. For example, you can access requests that
have been sent to the different FNEs for the activation of a given handset.
The history is kept by subscriber:
To access subscriber events:
1.
After accessing the Queues tab, in Search By select Subscriber Events.
2.
In By, select a subscriber identification, such as IMEI.
3.
In the additional field, enter the search criteria (for example, the IMEI).
4.
Click the
button.
The results page displays a series of criteria for an additional search.
Index | 105
5.
In Operation, check the boxes that correspond to the operations you want to examine.
6.
In Starting, select the extent of history to retrieve:

To retrieve the events that took place in the last x months, enter a number in "months
back".
To retrieve the last x events (without regard as to when they took place), enter a number in
"events back".
7.
Select By Account ID or By Device ID to retrieve requests relating to the selected

subscriber's account or handset.
8.
Click the Retrieve button.

The requests that meet the specified criteria are displayed.
The results show the operation-specific data for the event and the different FNE audit requests
involved.
Index | 106
Index
defined, 8
hierarchy, 8
modifying, 38
parent, 37
report, 69
resume, 48
security groups, 37
suspend, 47
A
Accept, 105
Activate, 92
Active, 97
Add Radio, 51
Adobe Acrobat Reader, 22
All Subscribers, 87
Area Code, 9
customer domain administrator, 74, 79, 81
assignment records, 18
customer domain group, 74, 75
attached value, 19
Customer Events, 70
Audit, 21
Audit button, 21
audit queues, 105
Available Pools, 39, 40
available value, 19
data access permissions, 77, 82

Data Type, 30
default value, 20
definition records, 18
delegation, 73
Belongs To, 31
Delete, 94
Deleted, 50
Deleted Subscriber Card, 50
calendar, 22
device inventory, 49
Cardinality, 27
Dispatch IDs, reserved, 41
Change Ownership, 64, 91
Divide Pool, 40
channels, 24, 45
DMO Channel, 45
Completion Time, 95
DMO Talkgroup Alias, 44
complex search in mass actions, 87
DMO talkgroups, 44
Configure, 88
Download, 22
Confirmed, 101
corporate group, 74
corporate user, 74, 79, 81
effective from/until
current value, 20
multiple validity periods, 18

single validity period, 17
e-mail address, 10
customer
accessing configured, 37
creating and configuring, 35
Exact, 39
Excel, 22
Index | 107
Exception, 101
Exchange Member IDs, 90
main domain administrator, 74
Exclude, 87
main domain group, 74

market, 8
F
Failed, 97
failover, 60
Failure Message, 95
FNE Card, 99
FNE Key, 101
frequencies, 24
functional permissions, 76, 82
mass action status, 94

mass actions, 86
Mass Operations List, 71
Max Length, 30
Maximum Subscribers to Retrieve, 70
Min Length, 30
Model, 54
Modify Parameters, 90
Monitor Interfaces, 96
grouping radios, 37, 57
Move Up/Down, 59
assigning admin groups, 46

creating admin groups, 26
customers, 41
radios, 53
switching admin groups, 33
multigroups, 9, 43
multiple rates mechanism, 18
Multiple Subscribers Report, 88
My Profile, 10
N
H
Holder Name, 90
I
identity, 29, 52, 61
Identity Type, 52
Incoming Prefix, 29
inquiries
Adobe Acrobat, 22
Excel, RTF, 22
printing, 22
Inventory, 51
inventory, device, 49
IP addresses, reserved, 40
navigation, 12
New, 91
New (change ownership), 64
New Customers, 35
new value, 20
None, 105
Note, 29
Number, 30
number pools, 38
O
Office Code, 9, 39
Office Name, 9, 39
One-to-many, 27
One-to-one, 27
Keep, 64, 92
Operations, 71
Keep Devices, 94
Outgoing Prefix, 29
L
Last, 16
logs, 100
ownership change, 91
ownership, changing, 64
P
parent customer, 37
Index | 108
Parent Customer ID, 36
roles, 29, 47
PDF file, 22
Rows per page, 49
pending requests, 104

pools of numbers, 38
Print, 22
private user, 79
private users, 74
S
scan list, 43
Scan List Alias, 44
scan lists, 43
profiles, 30
Scan lists, 9
search bar, 15
Queue ID, 101
search function in mass actions, 87
Queued, 103
security groups, 23, 28, 37
queues, 103
Serial Number, 90
R
radio
configuring, 54
creating, 51
resume, 67
suspend, 66
Radio IDs, reserved, 40
search, 14
services, 55
shared talkgroups, 45
Show History, 19, 21
Show Queues Count, 103
Start Bill Cycle, 18
Start Measuring, 100
Starting, 71
ranges, 9
Starting Address, 89
Reason, 48
State, 43
Refresh, 90, 100, 104
Status, 101
Reject, 101
status bar, 17
rejected requests, 105
status, mass action, 94
Replace, 65
String, 30
Replicate Subscriber, 63
sub-market, 8
Report, 21
Subscriber Details, 52
requests
subscriber list, 50
pending, 104
rejected, 105
viewing, 103
Resend, 105
Subscriber Report, 88
Reserve Pools, 38
Reserved Pools, 39, 40
resume
active group, 33
customer, 48
radio, 67
Resume, 93
Rich Text Format, 22
Supervisor, 101
suspend
active group, 33
customer, 47
radio, 66
Suspend, 92
Suspend Immediately, 98
Suspend on Idle, 98
Suspend on Next, 98
Suspended, 97
role, 52
Index | 109
T
Talkgroup Alias, 42
talkgroups, 9, 42
shared, 45
telephone numbers, reserved, 38
TMO Ranges, 58
top menu, 13
Total Request Count, 95
Transaction ID, 95, 101
U
Use Owned Dispatch IDs, 37
Use Owned IP Addresses, 36
Use Owned Phone Numbers, 36
Use Owned Radio IDs, 37
V
View Logs, 100
Z
Zero-to-many, 27
Index | 110
Index | 111

MiBAS 12 Dimetra User Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MiBAS 12 Dimetra User Manual

Загружено:

Авторское право:

Доступные форматы

Motorola confidential proprietary information

Motorola Integrated Billing

Motorola integrated Billing & Administration

Motorola confidential proprietary information

Proprietary Information Notice

Motorola confidential proprietary information

Motorola confidential proprietary information

Motorola confidential proprietary information

Motorola confidential proprietary information

Modifying Details of Configured Customers...................................................................................38

Motorola confidential proprietary information

Data Access Permissions.................................................................................................................77

Motorola confidential proprietary information

Terms and Concepts

A customer is a global entity. Customers may have an inventory of radios.

Motorola confidential proprietary information

Central Office Name, Area Code, Office Code

Accessing and Exiting MiBAS

Motorola confidential proprietary information

The Customer List appears.

Changing User Details

Click the My Profile link on the top bar.

Change the details you want.

Click Update Details.

Accessible Data and System Pages

Motorola confidential proprietary information

Changing Your E-Mail Address

Click the My Profile link on the top bar.

Click the Change E-Mail button.

In New E-Mail, type the password you want to adopt.

Motorola confidential proprietary information

The Navigation System

Main Navigation Tools

First you select a tab in the

Selecting a tab displays an

Selecting an option on the

When you select a menu

Motorola confidential proprietary information

The Top Menu

Disabled Menu Commands

is used to explain why certain menu commands are disabled.

Motorola confidential proprietary information

Motorola confidential proprietary information

Using the Search Bar

To conduct a search using the search bar

In the adjacent box, type the value to search.

Motorola confidential proprietary information

Click a row to access the item you want.

Using the Local Search Tool

Motorola confidential proprietary information

In the box or boxes below it, type the information to search.

The Status Bar

The time it took the MiBAS server to process a user's request to

Using Effective From/Until Dates

Motorola confidential proprietary information

Motorola confidential proprietary information

The Effective Date

Available and Attached Values

Motorola confidential proprietary information

Modifying, Deleting, Reporting and Auditing

button. Clicking the button deletes the record.

Motorola confidential proprietary information

The menu includes the following record handling commands:

Opens a page where you can enter a new record.