Business Requirements Document1

Business Requirements for
<Project Name>
Revision
Date
Revision History
Description
Changed By
Intended audience
Business Partners, Stakeholders and Sponsors
Functional Resources
Technical Resources
BUSINESS PROCESS
Billing Requirements
Ref#
Requestor
Priority
Importance
(Weight)
Requirements
Status
Deliverables
Acceptance Criteria
Business Process Requirements

Process 1
108.0 Dranginis, Dianne

Short
Term
Medium
Term
Long
Term
Customer Trial: FTP the BDRs to the customer, but

billing (invoicing) is not enabled yet.
Minimum Invoice Amount (able to defer when this
minimum begins).
Ability to customize daily FTP files for each customer
Will need to be part of contract definition page that is

custom.
custom. Done in combination with pricing rules.
Ability to have daily FTPs (from provisioned system to

billing system) have different fields sent for each
activity (i.e. the way that it is today)
Incorporated into the design.
Example: Customer in production, but doing Bill

Integration testing. Need a way to 'mark' a BDR to not
invoice - although would be included in the FTP.
Define if this should appear as part of the Bill and also
credited or don't appear at all or show at $0.
BDR's marked to not invoice should include recording
a reason as part of 'marking' the BDR to not invoice.

custom. Also a custom page to go into a BDR and
mark it specifically to not bill.
For each customer, Voyant has an account - used for

testing, etc. We will need to identify the Subscriber ID
that is tied to Voyant for each customer ('Provider ID').
These transactions should be filtered from the FTP and
the invoicing. (Record the Voyant subscriber ID on the
contract definition page.

custom.
We round up BDRs to the nearest minute when we bill.

Thus, if a recording lasted 10 seconds it would state
that in the BDR, but the customer and service provider
should be billed for 1 minute.
Process 2
Process N
63991417.xls
CONFIDENTIAL 07/27/2011
2 of 16
FUNCTIONAL BUSINESS REQUIREMENTS

Ref#
Requestor
Functional Requirements
Integration
INT
1.0
Requirements
2.0
Billing usage data is sent to Avante without cost

information already attached, and is not ready to post.
INT
3.0
Ability to run the billing application on demand
INT
4.0
Scalable to large quantities of data
5.0
GEN
6.0
GEN
Deliverables
Configure new billable evenys from production system
INT
General
GEN
Status
Acceptance Criteria
Need to define a process for getting new billing event

messages into PS
PeopleSoft custom table would accept the BDR
records. In generating the sales order or invoice, we
would leverage the standard PS Price Rules to
calculate prices.
Yes, but the billing run would be only for those BDR
records received to date and pricing would be based
on the group of BDR records processed at the same
time.
Define number of activities
I think it won't be a problem. The solution is based on

accumulating the BDR records and summarizing them
to the invoicing and accounting processes. So the
BDR records would consume about 3000 records per
day (90000 records per month), but would summarize
to approximately 20 invoice lines per customer per
month. The actual printing of the invoice (statement)
would provide the approximately 20 line summary
followed by printing the BDR details on subsequent
pages.
Enhanced
Services
Enhanced
Services
Identify and bill for recordings requiring multiple CDs
7.0
Accounting
Identify records in the database that have been

processed for customer billing, and for accrued billing.
Yes
GEN
8.0
Accounting
Produce one file at the service provider level to input

all billing usage information into Avante for use in
billing the service provider. Summarize for journal
entry post.
Standard posting process
GEN
9.0
Accounting
Identify Service Provider internal usage of service and

media orders, flag these records for sales and use
taxing.
Future Release: We will need a method for this

indentification and then we can support separate
sales/use tax per ship-to and by product classification.
GEN
10.0 Enhanced
Services
11.0
GEN
GEN
12.0
General Ledger
G/L Reporting
G/L
13.0
Functional
Provide shipping and tax charges at an item level
Calculate Administration minutes

Ability to address current product, contract billing and
services billing functionality including Mobile Meeting
requirements
Function of BDR
Susan Sowl to coordinate this issue with Sandra Hahn Future Release: This is a function of how the data is
grouped. We anticipate consolidating BDR records of
the same time and the same location, so that tax would
not be at the BDR record, only at the accumulated
record.
Admin: (offhook - toll free playback) where offhook are Custom process to develop.
only those records with subscriber information.
Mobile meeting requirements
Need Mobile Meeting Requirements
Link between Siebel and billing system
No, possibly Future Release.
Report G/L with gross, net, discount and tax amount

line items
Yes. custom develop direct billing interface and

standard invoice process will do these postings to GL.
3 of 16

Ref#
Requestor
G/L
14.0
G/L
15.0
Manage Credits/Adjustments
ADJ
16.0
Requirements
Status
Deliverables
Acceptance Criteria
Automated load of G/L data (in a JE format) from

Billing System to Avante
Automated filed upload from Billing System to Avante
G/L with unbilled reversal information.
Yes. Standard Functionality.
Ability to manually enter adjustments
Standard capability for adjustments to an Invoice.

Custom for adjustments to a specific BDR record
(billed vs not billed yet).
Support for partial and full adjustment in percent or $

amounts
Ability to calculate tax on adjustments
Ability to tie an adjustment to a line item on a bill
Must be in $ amount. Text could define %.
Yes. Standard Functionality.
ADJ
17.0
ADJ
ADJ
18.0
19.0
ADJ
20.0
Ability to assign reason codes when applying credits,

or freeform credits and not be forced to assign codes
Yes.
ADJ
21.0
Ability to enforce an adjustment approval process (only

certain user types can approve adjustments)
Automated adjustment approval not available. Will

need to be procedural and Enhanced Services to work
with Dave Nelson (Dir Credit & Collections)
Yes
Yes, but bill line items would be summarized BDR
records. Adjustments would be made to the BDR
record creating a new BDR record that is a credit
and/or adjustment. These adjustments would have
pricing fixed and would be included in the next
invoicing cycle (but summarized with other BDR to an
invoice line). Credits might need to not be summarized
so that they show on the summary page as well as the
detail page - functional design decision.
Customer Management
Account Creation
1.0
Functional
Custom development to associate service provider ID

with internal to system customer ID. Customer ID will
be used to track within PS.
Ability to assign a meaningful service provider ID and

use that to track customers throughout the system.
Ability to store different bill to: and send to: addresses
Yes
2.0
3.0
Ability to store customer's credit limit

Ability to support a multi-level billing hierarchy and
report differently for different customers
Yes
Future Release: This is not clear. We can support a
multi-level hierarchy of a customer definition. A
customer record specifies it's parent. However, the
consolidation key for billing is only a single level. So
customers A, B, C, and D - B, C, and D can
consolidate invoices to A. A can have B and C as
children and B can havd D as a child to it.
4.0
5.0
Support customer specific rates (prices/contracts)

Ability to maintain different payment terms for
customers
Yes. Standard.
Yes. Standard.
4 of 16

Ref#
Requestor
6.0
Requirements
Status
Deliverables
Acceptance Criteria
Ability to apply discounts throughout customer

hierarchy
Future Release: Sort of. The discount defintion would

have all of the customers tied to it. So a discounting
rule could apply to only A or also to A, B, C, and D.
Ability to store pending status CD/transcripts and dates

for products for an account
Future Release: BDR to carry status that it is

'pending'. If created as an order and not fulfilled yet,
then can be shown as backlog. Orders can also be
entered in Pending status, but if these come from the
BDR there is no support for this.
8.0
Ability to easily modify service information
9.0
Ability to store contract number, PO number for VRAP

contracts and associated PO's for Professional
Services
Design of customization will determine how easily.

Reqmt: Add new types of BDRs, Change pricing.
Yes
10.0
Ability to view current charges on-line by service

provider
Future Release: Web access by service provider to

see current charges on-line.
Reporting out of PS. If can be supplied, then would

want to include non-billable events so that all reporting
from one place.
Reporting can be provided through: PS Query,

Business Objects, and Crystal Reports
Accounts Receivable Summary

Accounts Receivable Detail
Payments Summary
Yes
Only to summarized BDR Level.
Yes
Order Management
7.0
Reports
10.5
Accounts Receivable
11.0
12.0
13.0
14.0
Payments Detail
15.0
Reversals Summary
16.0
Reversals Detail
17.0
Refunds Summary
18.0
Refunds Detail
General Ledger
19.0
General Ledger Summary
21.0
22.0
General Ledger
Detail Product Revenue
Miscellaneous Adjustments
23.0
Functional
General Ledger - Chart of Accounts
20.0
Miscellaneous Adjustments Summary
Payments
Summary
Payments
Detail
Reversals
Summary
Reversals
Detail
Refunds
Summary
Refunds
Detail
Lists all the
G/L
Shows the
accounts in
summary
the Infranet
impact on
database.
each G/L
Breaks
account
revenue
balance
down by
during
a
product,
specified
showing
time period
total
by resource
Shows
debit
revenue
and credit
thenfor
by
each
G/L ID.
adjustments
product.
by
Includes
geographical
products
location of
whether
accounts.or
not they
have
a G/L
CONFIDENTIAL
07/27/2011
ID.

Yes
Yes
Yes
Yes
Yes
The level of detail that company is willing to track.
Greater detail is tracked in our RevFlash reporting
soln.
Yes, as adjustments to BDR are created in the BDR

records on PS Side.
5 of 16

Ref#
Requestor
24.0
Miscellaneous Adjustments Detail
Subscriber Accounts
25.0
Account Changes - Single Period
Requirements
26.0
Account Changes - Multiple Periods
27.0
New Account Lifetime
28.0
Closed Account Lifetime
29.0
30.0
31.0
32.0
Tax Jurisdiction Summary

Tax Jurisdiction Detail
Summary of all Taxes
Tax Exempt Accounts
33.0
34.0
Orders Report
Forecast report - off current orders and long term
forecast report
Voyant Sales Report
Pre-Billing Report - Ability to view unbilled usage,
current charges throughout the month
Tax
Status
Deliverables
For each
customer
account,
shows
Shows
the
event-level
number
debit andof
accounts
credit
Shows
the
created
or
adjustments.
number
closed of
accounts
during athe
Shows
created
or
specified
length
of
closed
time period,
service
for
during
athe
and shows
Shows
new
weekly
or
the netof
length
accounts.
monthly
change for
service
in
period,
and
accounts.
closed
shows the
accounts.
net change
in accounts
by period.
Acceptance Criteria
Yes, as adjustments to BDR are created in the BDR
records on PS Side.
Need specific requirements of changes
Need specific requirements of changes
Part of setup of contract
Part of maintenance of contract.
Std
Std
Std
Std
Misc
35.0
36.0
Define details
Define details
Need details
Need details
Define details
Fulfill through RevFlash reporting.

Possible to create such a report.
Billing
Billing Cycle
Functional
37.0
Enhanced
Services
Support minimum and maximum charge amounts verify that minimum charge has been met
38.0
Standard
39.0
Support modifications to existing products / service

1
offerings/ prices and quote modifcations
Produce single, consolidated invoice per billing cycle
for customers, separate invoices for different services
if desired
40.0
Ability to run billing application on demand
Future: Yes, but would only obtain invoices for BDR

records delivered to date and pricing will be based on
the BDR records accumulated for a single invoice (not
across invoices). (Perhaps pricing as if through this
date.)
41.0
Ability to manage and bill for recurring charges for

various cycles e.g. monthly, quarterly, annually.
(Private numbers)
This can be setup. Examples: VRAP Private# Private# Provisioned, Recurring Charge for Private#,
Private# Dropped. Mobile Meeting - Site
Commissioned, Monthly fee per site, Site
Decommissioned.
Custom Development. Could force to replicate pricing

functionality offline. If so, might as well pass directly to
Billing Interface.
Can do both.
6 of 16

Ref#
Requestor
42.0
43.0
44.0
Enhanced
Services
45.0
Enhanced
Services
Enhanced
Services
46.0
47.0
Requirements
Status
Deliverables
Acceptance Criteria
Ability to support a multi-level billing hierarchy
Future: Explained under customer mgmt.
Ability to pull all open credits/adjustments into an

invoice
Ability to set the default billing frequency, and change 1
if needed
Only through the consolidation key.
Ability to have multiple billing cycles
Yes, but only one billing cycle per customer. Multiple

means across multiple customer.
Standard capability is a credit/rebill. No automatic
back-out.
Load BDR records can be configured for how
frequently loaded. Need explanation on multiple
collection points.
Automatic bill back-out capabilities

Ability to obtain usage from multiple collection points
on a daily (configurable) basis
We will build that into the contract definition page.

Need to determine impact on volume discounts and
prorating if change from a cycle of 16th through 15th to
1st through 31st. How to handle transition month of
16th through 31st? Don't expect to need this initially.
48.0
System must store information that supports a service

business: running total of charges, previous payments,
outstanding balances, payment due date, etc..
This is information in the AR system, but at the invoice

level - not details.
49.0
1
Ability to automatically calculate tax based on
jurisdiction and product or link to tax table product
1
Ability to automate tax calculations during bill
generation or at time charge is assessed
Ability to tax for sales/use taxes on products and
recording/playback services on an individual item level.
Future: Yes
52.0
Ability to support FCC taxing ?
Future: Need info on this. Std is No. Reqmt is when

and if service is sold directly to end users.
53.0
Ability to support tax exemptions
Yes. Standard.
54.0
Support Sales & Use Tax Reports
Future: Yes. Standard through Taxware.
Ability to interface with Tax software
Future: Yes
Support Lockbox (electronic bank file) for checks

payment processing
Support for credit card processing for payment
Yes
Taxes
Calculation
50.0
51.0
Future: Tax is calculated at time of invoicing.

Future: No. We will accumulate by type of BDR into a
single invoice line item (scalability) and report details
from the BDR custom data storage.
Interface
55.0
Manage Payments
Payment Processing
56.0
57.0
Functional
nice to have
Could
7 of 16

Ref#
Requestor
58.0
59.0
Late Payments
60.0
Under/Over Payments
61.0
Additional Payments
62.0
Interface
63.0
64.0
Requirements
Status
Ability to receive payment via Electronic Fund Transfer 1
Deliverables
Acceptance Criteria
Support manual payment posting
I don't think we are doing this yet, but system does

support it.
Yes
Support to apply business rules to assess penalties,

interest fees and cancellation fees
Custom development
Ability to determine if a customer underpaid or

overpaid through statements
Assuming that we generate statements, yes.
Ability to post payment by bill number
Yes
Ability to interface for EFT requests
Ability to interface with lockbox
I don't think we are doing this yet, but system does

support it.
Yes
Yes
Price Plans
Rate Application/Rating Rules

65.0
Support customer-specific rates
66.0
Accounting/
Enhanced
Services
1
Capability for tiered, threshold, volume and
headquarters discounting and view on the bill
Support aggregation, calculation and allocation of 1
non-recurring and recurring charges based on
customer's products/services
Need examples to understand requirement.
Ability to assess shipping charges on an item

1
basis
Ability to maintain and bill for services on a
prorated basis - (specifically for private numbers)
Yes. This is on the BDR record.
70.0
Support advanced customer account hierarchy

processing for rate/discount aggregation,
calculation, and allocation purposes
See customer information and above.
71.0
Ability to associate usage/transaction charges

with products/services
Ability to associate time and expenses for
professional services
Yes
Yes
Ability to assign start and end dates to pricing of

products/services by contract basis
Part of definition of custom contracts page (it is

std in contracts, but contracts won't suffice for
these other requirements.
67.0
68.0
69.0
72.0
Effective Dates
73.0
Functional
Accounting/
Enhanced
Services
Enhanced
Services
74.0
Ability to have flag for renewal that can be

managed
75.0
Ability to assign start and end dates to

product/service rates
Aggregation can be supported. Calculation and

allocation would need custom development - pre
invoice creation. Need examples to understand
requirements.
Yes
Part of definition of custom contracts page (it is

std in contracts, but contracts won't suffice for
these other requirements.
1
Standard in price rules.
8 of 16

Ref#
Requestor
Promotions and Discounts

76.0
Requirements
Status
Deliverables
Acceptance Criteria
Ability to manage product and service discounts
Standard in price rules
77.0
Ability to support promotions
Example: 90 day free trial - 100% discount. Don't Standard in price rules
charge for a particular service withina period.
78.0
Ability to discount by a percentage
79.0
On invoice, suppress the record if the qty of the

service is $0, but include the record if the qty != 0
but the price/amount is $0.
Manage/Administration
80.0
81.0
Easily maintainable product and price list

Modifications to price list do not change
customers with pre-existing contracted prices
Through price rules, not directly on order/invoice.

Custom 'Statement' Development
1
1
You be the judge of how easy it is.

This will take some thinking on how to setup so
that existing contracts are not changed with price
list changes.
Invoices
Content
82.0
Ability to display the period-covered dates on the

invoice
Yes
83.0
84.0
85.0
86.0
87.0
88.0
89.0
90.0
91.0
Accounting
92.0
93.0
Accounting
Accounting
Ability to display taxes on the invoice, aggregated per

bill and displayed by line item
Ability to display the invoice date on the bill
Ability to display customer id on the bill
Ability to display contract number
Ability to display PO number with associated invoice
line items for professional services
Ability to display variable messages on invoices
Ability to sort the bill sections (i.e.. Recurring Charges,
Services, Products) by billable item
Use Statements - not invoices.
1
1
1
1
Yes
Usually not, but we can do so. Qty breaks can be
defined by a different discount.
Yes. My definition of line item is the aggregated BDR
by location, not each BDR.
Yes
Yes
Yes
Yes
1
1
Through Notes
Custom development, but Yes
94.0
Ability to display payment terms
Yes
95.0
Support line item product name/description on invoice 1
Yes
Ability to send/not sendpaper copy of invoices to all

customers regardless of payment method
No. We can throw invoices away though.
96.0
97.0
Functional
Enhanced
Services
Accounting
Ability to produce different invoice formats for each

customer, use of a GUI interface to accomplish this
Ability to display previous amount due, previous
payment, total current amount due
Ability to display sub-totals and adjustments
Ability to display discounts on the invoice
Not a GUI interface for invoice format creation.

Different invoice formats can be supported, but
recommend varying formats on an exception basis.
Ability to display $0 balances on invoice for free

periods/promotions
Yes
9 of 16

Ref#
Requestor
98.0 Enhanced
Services
Requirements
Status
Deliverables
Acceptance Criteria
Ability to provide the Subscriber Report at top-line

detail service provider, subscriber detail level,
recording id level and activity level, depending on
customer request
Need specs on the Subscriber Report (detailed pages

of Invoice/Statement).
Enhanced
Services
Ability to provide the Subscriber Report at top-line

detail service provider, subscriber detail level,
recording id level and activity level, depending on
customer request, with invoice dollars associated with
it.
Need specs on the Subscriber Report. (detailed

pages of Invoice/Statement).
100.0 Enhanced
Services
Ability to provide invoice support pages 2 - 500. This

will include the Subscriber Report with the operational
billing information at various levels mentioned above,
with the correct charges associated with it.
Need specs on the Subscriber Report. (detailed pages

of Invoice/Statement).
101.0 Acounting
Invoices must provide information to support a service

business: show a running total of charges, previous
payments, outstanding balances, payment due date,
etc..
Through Statements
102.0
Ability to group services and products together, in

whatever grouping desired.
Not in whatever grouping is desired. In a specified

grouping that gets defined.
103.0
Support for perforated remittance slips
Future: No, until volume warrants this.\
Ability to produce paper invoices

Ability to send electronic fund transfer with invoice
amount
Ability to web interface with query commands
Ability to send e-mail of invoice
1
1
Yes
Yes, but not using this yet.
Yes, but not implemented yet.

Yes.
99.0
Delivery Method
104.0
105.0
106.0
107.0
Additional Requirements
Content

minimum begins).

custom.

Discount Periods
Functional
10 of 16

Ref#
Requestor
Requirements
Status
Deliverables
Acceptance Criteria




custom.
Rounding
Functional
11 of 16
INTEGRATION
Ref#
Requestor
Integration Requirements
Content
Requirements

minimum begins).
Status
Deliverables
Acceptance Criteria

custom.





custom.


Discount Periods
Rounding
63991417.xls
12 of 16
SYSTEM PERFORMANCE
Ref#
Requestor
System Performance Requirements
On-Line Response

Requirements
Status
Customer Trial: FTP the BDRs to the customer,

but billing (invoicing) is not enabled yet.
minimum begins).
Ability to customize daily FTP files for each
customer
Open Issue
PeopleSoft Capability
Will need to be part of contract definition

page that is custom.
page that is custom. Done in combination
with pricing rules.
Ability to have daily FTPs (from provisioned

system to billing system) have different fields sent
for each activity (i.e. the way that it is today)

Integration testing. Need a way to 'mark' a BDR
to not invoice - although would be included in the
FTP.
Define if this should appear as part of the Bill and
also credited or don't appear at all or show at $0.
BDR's marked to not invoice should include
recording a reason as part of 'marking' the BDR
to not invoice.

page that is custom. Also a custom page to
go into a BDR and mark it specifically to not
bill.
For each customer, Voyant has an account used for testing, etc. We will need to identify the
Subscriber ID that is tied to Voyant for each
customer ('Provider ID'). These transactions
should be filtered from the FTP and the invoicing.
(Record the Voyant subscriber ID on the contract
definition page.

We round up BDRs to the nearest minute when

we bill. Thus, if a recording lasted 10 seconds it
would state that in the BDR, but the customer
and service provider should be billed for 1
minute.

Schedule Frequency
Etc.
63991417.xls
13 of 16
AUDIT, SECURITY, CONTROL

Ref#
Requestor
Audit, Security, & Control Requirements
Audit
Requirements
Status

Open Issue

with pricing rules.

minimum begins).
customer


FTP.
to not invoice.

bill.
definition page.

We round up BDRs to the nearest minute when

we bill. Thus, if a recording lasted 10 seconds it
would state that in the BDR, but the customer
and service provider should be billed for 1
minute.
Security
Control
63991417.xls
14 of 16
EXCLUSIONS
Ref#
Requestor
Exclusions
Status
Open Issue
Exclusions
Subject Area 1


minimum begins).
customer

with pricing rules.


FTP.
to not invoice.

bill.
definition page.


Subsject Area 2
63991417.xls

15 of 16
Acceptance & Signoff
Warren Baxley
[Print]
Sign
Date
John Duane
[Print]
Sign
Date
Robert Hagen
[Print]
Sign
Date
George Lantz
[Print]
Sign
Date
Randy Schultz
[Print]
Sign
Date
Paula Casey
[Print]
Sign
Date
Dave Nelson
[Print]
Sign
Date
Neil Dickson
[Print]
Sign
Date
Jeremy Anderson
[Print]
Sign
Date
63991417.xls
16 of 16

Business Requirements Document1

Загружено:

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

Оригинальное название

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

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

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

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

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

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

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

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

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

Business Requirements Document1

Загружено:

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

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

Business Requirements for

Business Process Requirements

108.0 Dranginis, Dianne

Customer Trial: FTP the BDRs to the customer, but

Ability to customize daily FTP files for each customer

Will need to be part of contract definition page that is

114.0 Dranginis, Dianne

Ability to have daily FTPs (from provisioned system to

Incorporated into the design.

110.0 Dranginis, Dianne

Example: Customer in production, but doing Bill

Will need to be part of contract definition page that is

111.0 Dranginis, Dianne

For each customer, Voyant has an account - used for

Will need to be part of contract definition page that is

112.0 Dranginis, Dianne

We round up BDRs to the nearest minute when we bill.

FUNCTIONAL BUSINESS REQUIREMENTS

Billing usage data is sent to Avante without cost

Ability to run the billing application on demand

Scalable to large quantities of data

Configure new billable evenys from production system

Need to define a process for getting new billing event

I think it won't be a problem. The solution is based on

Identify and bill for recordings requiring multiple CDs

Identify records in the database that have been

Produce one file at the service provider level to input

Standard posting process

Identify Service Provider internal usage of service and

Future Release: We will need a method for this

Provide shipping and tax charges at an item level

Calculate Administration minutes

Link between Siebel and billing system

No, possibly Future Release.

Report G/L with gross, net, discount and tax amount

Yes. custom develop direct billing interface and

FUNCTIONAL BUSINESS REQUIREMENTS

Automated load of G/L data (in a JE format) from

Yes. Standard Functionality.

Ability to manually enter adjustments

Standard capability for adjustments to an Invoice.

Support for partial and full adjustment in percent or $

Must be in $ amount. Text could define %.

Yes. Standard Functionality.

Ability to assign reason codes when applying credits,

Ability to enforce an adjustment approval process (only

Automated adjustment approval not available. Will

Custom development to associate service provider ID

Ability to assign a meaningful service provider ID and

Ability to store customer's credit limit

Support customer specific rates (prices/contracts)

FUNCTIONAL BUSINESS REQUIREMENTS

Ability to apply discounts throughout customer

Future Release: Sort of. The discount defintion would

Ability to store pending status CD/transcripts and dates

Future Release: BDR to carry status that it is

Ability to easily modify service information

Ability to store contract number, PO number for VRAP

Design of customization will determine how easily.

Ability to view current charges on-line by service

Future Release: Web access by service provider to

Reporting out of PS. If can be supplied, then would

Reporting can be provided through: PS Query,