-
Where did the design for TAMS come
from?
-
I am concerned about the 21-day
trial period. It sometimes takes more time to process
recommendations for a client; will I loose all of my
data after I enter it if the 21 days expires?
-
Where do I enter individual line
feature charges (like hunting)?
-
How do I get to the subject index
and search capability in TAMS Help?
-
If I buy a single user version of
TAMS can I upgrade it to a multi user version later on?
That is, would I get credit for the single user when
buying the multi user version?
-
Are the
values entered in a Supplier
Plan for Line Charge, USF, LNP, etc. used per line, or
per plan?
-
How can I handle partial billing
cycles which are prorated?
-
When I am entering plan
information should I include the taxes whose rates are
not specified (in lieu of specific Taxes & Surcharges
items like CA High Cost Fund Surcharge - A)?
-
How would you suggest handling
metro plans?
-
How can I change the name of a
supplier plan?
-
Does the Contract End date in the
Service Account view serve the purpose of/for Service
Providers (Plan) Term/Contract information?
-
How would an early termination fee
be handled in invoicing?
-
Should adjustments (like payphone
surcharge for V1.1) be entered before tax also?
-
How can I see earlier inputted
adjustments?
-
Is it by design that the Total
Cost field in the Existing Billing Cycles sub-window of
the Account Invoice Data tab shows a value of zero for
some none-zero cost records?
-
While entering billing data
manually should you enter the base cost or the cost
including taxes & surcharges? And when minutes are
entered does TAMS applies the taxes & surcharges in
determining the cost in its billing data records?
-
Can you give me more information
about Residual Group Allowance and Residual Usage?
------------------------- Answers -----------------------
Where did
the design for TAMS come from?
TAMS
was designed by Kris Macurdy based on his experience in the
telecom industry, his experience as a Telecom Consultant and
his computer experience.
[Return]

I am concerned about the 21-day trial period. It sometimes
takes more time to process recommendations for a client;
will I loose all of my data after I enter it if the 21 days
expires?
We recognize that the time to take a client
through the entire process (Service
Agreement to Invoicing) is longer than the
three weeks given for the trial. In fact,
some clients make take 12 weeks or more
before the implementation is complete and
the first billing cycle is available for
Savings Invoicing. The 21-Day trial is
designed to give enough time to evaluate the
functionality of TAMS and to make a decision
to buy
or not. Once the baseline data is captured
and the Recommendation Letter w/ Analysis
Reports are generated, the remaining
functionality of TAMS can be executed
without waiting for the approval and
implementation. This includes:
·
Supplier Change Orders for Local, Local
Toll, LD and Toll Free Services
·
sample
Invoice Generation (actual Invoices
require actual post-optimization data)
By registering your copy of TAMS after
installing it, you automatically get a
10-day extension to the trial. Also, we have
had some users require additional time to
complete their evaluation and are able to
provide an activation code which will extend
the trial even further.
Finally, you should know that the reports in
TAMS are exportable to various formats
including Excel, Word, RTF, and PDF. If you
are concerned about “losing” data (should
you decide not to purchase TAMS) note that
you will be
able to save your data in one of these
formats. We certainly hope that you will not
need to be concerned about this situation
once you’ve tried TAMS.
[Return]

Where do I enter individual line feature charges (like
hunting)?
Hunting (and other line-feature charges) are added as
“Ancillary Features”. “Ancillary Features” are a type of
service plan which do not have any usage or metered rates
associated with them (i.e. – fixed monthly charge). To do
this, add them as separate Plans for the Service Provider.
You can add one for Caller ID, one for Hunting, one for
Inside Wiring Maintenance, etc… Once the Lines and Service
Accounts are defined, you can add the Ancillary Features to
the lines via the “Manage Line Services” form, just like
other services. You can add as many Ancillary Features to
any line, as needed, to set the baseline. Each Feature can
then be individually optimized or removed, as needed. The
Analysis and Invoicing Reports will automatically handle the
costs each feature.
[Return]

How do I get to the subject index and search capability in
TAMS Help?
TAMS Help does have Index and Search tabs in the Help
Navigator, next to the Contents tab. If you don’t see
the Help Navigator, click the “Show” icon in the upper
left-hand corner.
[Return]

If I buy a single user version of TAMS can I upgrade it to a
multi user version later on? That is, would I get credit for
the single user when buying the multi user version?
Absolutely. The upgrade cost is the difference in price
between the Workstation License and the Server License
costs, so there is no risk in starting with the
Workstation Version. Once you convert to the Server
License, you would fall under the Server Maintenance
Agreement which includes more support for up to 5 users.
[Return]

Are
values entered in a Supplier Plan for Line Charge, USF, LNP,
etc. used per line, or per plan?
Per line. If you have charges that are applies
once per account (and not per-line), add them to
the Sub-Account. Sub-Account charges are only
charged once per billing cycle.
[Return]

How can I handle partial billing cycles which are prorated?
TAMS computes cost savings by comparing the
optimized expenses (fixed and usage-based) as of
the BILLING DATE for each billing cycle of each
optimized account, to the corresponding baseline
expenses which are in effect on each BILLING
DATE. The optimized AND baseline expenses are
always calculated for a FULL month for each
billing cycle. TAMS does NOT prorate for
partial billing cycles (as is often the case for
the first post-optimization bill).
One of three approaches can be used to handle
partial months:
1. Make the Billable Duration on the
optimization records one month longer than
the Default Billable Duration specified in the
Service Agreement and skip the
billing for the first partial month. For
example, if the agreement is to bill for
savings for 24 months, change the Billable
Duration to 25 months when applying the
Optimization Changes on the Manage Line Services
form. This value can also be adjusted at a later
time on the Line Service History records from
the Line Details form. By skipping the first
partial-month bill, 24 full cycles of savings
will be billed to
the client. For accounting purposes, you may
want to enter the first billing cycle
and usage to the account. You may do this and
then manually mark it as "Invoiced"
so that it does not appear on the Savings
Invoice to the client.
2. Manually apply a "Billing Adjustment"
to the first and last billing cycles to
make the desired corrections. The first
optimized billing cycle can have an extra
"charge" applied to reduce the savings. The
amount of the extra "charge" would be
the overstated savings between the optimized
fixed fees and the baseline fixed fees,
given by the formula:
(Monthly Baseline Fees - Monthly Optimized Fees)
* (1 - Prorated Days/Days in Month)
For example, consider the following simple
scenario:
Monthly Baseline Fees: $100
Monthly Optimized Fees: $25
TAMS will compute the monthly savings as $75
(plus taxes and surcharges)
If the fixed fees are prorated for 20 days in a
30-day calendar month,
then the overstated savings are $25, given by:
($100 - $25) * (1-20/30) = $75 * 1/3 = $25
A $25 "Charge" Billing Adjustment would be added
to the first billing cycle.
The month following the last billing cycle (e.g.
- 25 months later) can have a
matching "credit" applied to bill the
partial-month savings to which you are entitled.
Since the Billable Duration of the optimization
will have expired, the Optimized and
Baseline costs computed by TAMS will be the same
(i.e. - no net savings). The only net charge on
this billing cycle will be the manual
adjustment. In this case, the client
will receive an extra month of savings invoices
(e.g. - 25), with the first and last
representing partial months.
3. Make no special adjustments in TAMS
and explain to the client that the first month
of billed savings is a full month and that you
will not bill them for the partial
month at the end of the Billable Duration.
[Return]

When I am entering plan information should I include the
taxes whose rates are not specified (in lieu of specific
Taxes & Surcharges items like CA High Cost Fund Surcharge -
A)?
Many telecom bills are full of various
State/County/Local taxes, fees, and
surcharges. Sometimes the hardest part of
dealing with them is figuring out if they are a
fixed rate each month (which can change
regularly with updated regulations) or some
percentage of other charges. This problem is
independent of the tool you are using. Here are
some strategies in dealing with these, and how
TAMS can manage them for you:
1) For Flat-rate Fees/Surcharges which are
charged on every line, lump them
into the "Local Fees (per-line)" field on the
Plan Details.
2) For Flat-rate Fees/Surcharges which are
charged only once each month on the
account (independent of how many lines you
have), lump them into the
"Local Fees" field on the Sub-Account Details
form.
3) For charges that are a percentage of usage,
add them to the "Local Tax Rate"
on the Plan Details form.
4) Sometimes, the fees are a flat-rate and set
by the PUC, but they change often
(e.g. - quarterly). Most people ignore these
charges altogether so that they
don’t have to continually maintain the current
costs in TAMS (as well as make
adjustments to the baseline plans). This is a
legitimate approach since the
baseline and optimized plans would always change
in tandem and the result
would be zero net cost savings for those types
of fees.
TAMS provides the standard fields (EUCL, LNP,
911, etc...) plus a few extras like
"Local Fees" and "Local Taxes" to act as
"catch-alls" for the multitude of billing
conditions in the market.
[Return]

How
would you suggest handling metro plans?
Metro Plans are tricky. Let me clarify what
TAMS does / doesn’t do with Metro Plans.
What TAMS does is evaluate Local Toll & LD
call detail records (CDRs) to see how many
minutes each month, on average, are used in
the NPA-NXXs of the Metro Plan. This allows
you to determine if a Metro Plan is a
cost-saving alternative to low-cost Local
Toll/LD rates or not. If your client
already has a Metro Plan, the situation
is more difficult. The Suppliers usually do
not provide any durations of calls into
these NPA-NXXs so it is harder to determine
if low-cost Local Toll/LD rates are a better
alternative. As you mentioned, there are
several choices I see three:
a) Compare
similar Metro Plans from other providers, at
lower cost (which TAMS can handle for
billing cost-savings as an “Ancillary
Feature”)
b) Import
Traffic Study data or PBX SMDR data into
TAMS and then evaluated against the Metro
Plan
c)
If you believe the usage in the Metro Plan
areas is minimal, switch the client to a
low-cost Local Toll/LD plan and then confirm
the change with TAMS given the first billing
cycle from the LT/LD invoice. If the usage
is high, switch them back to the Metro Plan.
This approach is a little risky, but not too
much.
In all of these cases, TAMS can help you
make the right decision.
[Return]

How
can I change the name of a supplier plan?
You can edit and save the Plan Name
anytime from the Plan Details form.
Simply edit the Name and click “Save”.
TAMS does not allow the same Name to be
re-used for multiple plans. This is to
avoid confusion when looking at the list
of plans on the Supplier Form or in
various reports.
If you get an error upon Saving which
states that it would create a duplicate
value, try a different, unique name.
[Return]

Does the Contract End date in the Service Account view serve
the purpose of/for Service Providers (Plan) Term/Contract
information?
There are several fields for
tracking Term / Contract
information. The Contract End date
in the Service Account is designed
to track when an existing term
commitment for a client will expire.
The Notes field of the Service
Account can be used to capture any
other data relevant to the account
including multiple term dates.
[Return]

How would an early termination fee be handled in invoicing?
We recommend using a “Billing
Adjustment” for this type of
one-time expense.
[Return]

Should adjustments (like payphone surcharge for V1.1) be
entered before tax also?
Billing Adjustment records
are line-item entries. TAMS
does not apply taxes or
surcharges to them because
some items (like setup fees)
are non-taxable. If the
charge you are adjusting for
is taxable, add the tax to
the adjustment before
entering it, or add a second
adjustment for the taxes.
[Return]

How
can I see earlier inputted adjustments?
To view previously
entered Billing
Adjustments, click on
the “Adjustments” link
of the corresponding
Existing Billing Cycles
record on the Account
Invoice Data tab.
[Return]

Is it by design that the Total Cost field in the Existing
Billing Cycles sub-window of the Account Invoice Data tab
shows a value of zero for some none-zero cost records?
The Total Cost field
in the “Existing
Billing Cycles”
table is
informational only.
It is set manually
by entering the
“Total Cost” field
when adding a new
Billing Cycle
record. The purpose
of this field is to
store the Total from
the Supplier
Invoice. You can
manually perform two
primary validation
checks on the Total
Cost:
1.
Visually audit the
month-by-month Total
Costs to identify
trends or anomalies.
You will quickly be
able to see if the
usage is increasing
or decreasing over
time, as well as a
severe jump in Cost
which may identify
unauthorized
cramming charges.
2.
The
Analysis reports for
a single month, as
well as the Savings
Invoice report,
should accurately
reflect the same
Total Cost for the
Billing Cycle as is
stored in this field
(if all costs are
captured in TAMS).
If the TAMS reports
do not validate to
the Supplier
Invoice, you can
investigate the
charges and
reconcile the
difference.
To edit the Total
Cost field for
Existing Billing
Cycles, edit the
field in the table
and click Save..
[Return]

While entering billing data manually should you enter the
base cost or the cost including taxes & surcharges? And
when minutes are entered does TAMS applies the taxes &
surcharges in determining the cost in its billing data
records?
When entering billing
data manually, you
should enter the base
costs without taxes and
surcharges. If you
leave the “Duration” and
“# of Calls” fields
blank, TAMS will use the
rates from the Plan to
calculate those for you.
If you enter the
“Duration” and “# of
Calls” fields along with
the Cost field, then
TAMS will validate the
Cost based on the Plan
parameters. If it does
not validate, you will
get a warning but can
still proceed to save
the record.
TAMS computes costs by
using the raw call
volume data and then
applies Taxes and
Surchargesduring the
Analysis and Savings
Invoice Reporting
processes. Therefore,
you do not have to
apply any
taxes/surcharges during
billing data entry.
[Return]

Can you give me more information about Residual Group
Allowance and Residual Usage?
Residual Usage is just a bookkeeping value of “Net”
Usage charges from the lines on the Sub-Account which
are in excess of any “line-level” Allowances. For
example, suppose two lines (A & B) have a Local service
plan with a $10 Allowance per-line and the allowance is
shared with other lines on the Sub-Account. If line A
has $12 worth of usage, then it will contribute $0 to
the Residual Group Allowance and $2 to the Residual
Usage for the Sub-Account. If line B has $8 worth of
usage, then it contributes $2 to the
Residual Group Allowance and $0 to the Residual Usage
(i.e. – its usage was “consumed” by the Allowance) Since
the Allowances are Shared, line A’s $2 Residual Usage
will get offset by Line B’s Residual Group Allowance.
If Line B’s plan does not share its allowance, then it
will not contribute toward the Residual Group
Allowance.
In the case where there are no line-level allowances,
the Residual Usage will be the Total Usage charges for
all services on the sub-account. This value is
accumulated for all lines so that any Sub-Account level
Allowance can be subtracted from the Total Usage
(without going over when Allowance > Total Usage).
Notes:
- “line-level”
allowances are only available for Local Service Plans.
- Directory
Assistance charges do not apply towards Residual Usage
or subtract from the
Residual Group Allowance. Directory Assistance charges
are handled independently.
The reports in TAMS do a lot of bookkeeping work to keep
track of line-level usage, non-shared and shared
allowances, etc… that would require an enormous amount
of manual effort to try to match. Once you’re
comfortable with the data model and reporting results
from TAMS, you can “set and forget” these values
in TAMS and let it manage them all for you.
[Return]