Professional Documents
Culture Documents
SOFA Audits
Updated 8/4/06
F_Run_Rate Revenue
(Billing Data) Commitment
Orders NRL Compare at
(Order Data) Service level by
Audits
PIID-SCID for a set
of attributes
Products included are
those that are Clarify
One-Off Audits
initiated. These are
primarily the Network & Audit Name = Revenue
Internet Services Commitments (future)
products.
DIGRS Audit Name = One-Offs
Products:
Network & Internet Services Audit Name = DIGRS
Managed Modem
Clarify Voice
Excludes: Magma and SLDB Active Items that are a Mis-Match (E) or No Match
Voice (N). Must be active in either Clarify or Kenan, not
necessarily in both. If disconnected in both, those SOFA
Match Status: are held in DIGRS and not moved to SOFA.
M-Match
SLDB E-Mis-Match
(Voice Order Data) N-No Match
Attributes:
MRR
NRR
YRR
Service Status:
Active
Disconnect
SOFA gives an
Pending
Yes Audit Status of
Billing?
“Pending Billing”
SOFA checks to see if the
item has just been received by
SES (Billing) within a period of
time. Currently, this Pending
Billing Window is 60 days.
No
Enter SOFA
E Routine Audit
1.0
Match Status?
Enter SOFA
N “N” Process
2.0
Enter SOFA
Routine Audit
1.0
Submit Fix
Fix Completed
Audit Request Complete Audit
in Field
1.4
1.2 1.3 1.5
Note:
Step 1.1 was removed and moved to step 1.2.4.
I did not re-number these boxes as it would require
renumbering throghout our documentaiton. Thus, this
process now begins with 1.2 (there is no 1.1)
Audit 1.2.
FA Only FA Only
Prioritize Audit
Create Pending
Queue Update Root Cause Contact Account Teams
Scorecard record if
Level 3
Billing Only
Progeon
1.2.1
The following filters and priorities are applied for new items (IAP-null)
Threshold
Items above $1,000 in absolute value of the difference between Kenan and Clarify are
considered Above Threshold. The team works to resolve all Above Threshold items within
the 3 month window. Below Threshold items are worked if there is time.
Audit Category
As DIGRS logic or related issues are identified for false positives, a category is applied and
these items are ignored by the auditors as the DIGRS logic fix should resolve these items.
One exception is Audit Category of IA orders. These are not audited as they are out of scope
and there are no DIGRS fixes planned.
Discrepancy Type
Some items are able to be automatically identified with a discrepancy type. Where possible,
this is used to focus on Rev Impact discrepancies over other issues. However, the majority
of items must be researched to identify the discrepancy type; thus, this does not drive priority
at present. Current priority of Discrepancy Type is as follows.
1. Rev Impact-Under
2. Rev Impact-Over
3. Discrepancy Type =Null
4. Data Integrity
Conduct Manual Audit 1.2.2.
13 Unable to Fix
14 Fix Needed
Records
that have
Audit Check current “In Audit Billing Only
Status of Process Sub-Status”
“In Audit Pull Order History
Look up COF in
Process” (TOES Qry)
Documentum
(ATG 4.0)
Follow the audit
procedure Is problem Move to “Update Audit
1 (null) Yes
(see Progeon M&P determined? Statuses 1.2.3”
FA Only Billing Only documentation)
Pull Billing History
Progeon
Look up Billing
(RM Qry)
in Kenan
(ATG 5.0)
No
4 DIGRS=M
Update Discrepancy Type 1.2.4.
Populate Discrepancy
System (SOFA)
Yes
No
Move to “Audit 1.2”
Analysts
Analyst
Analysts to do initial Populate Discrepancy
research to determine Type according to
Discrepancy Type definitions
(See Status Definitions)
Consider Additional Audit Steps 1.2.2.1.
Records
from 1.2.2
Does Rev amt from Move to
where Update Audit Statuses as
DIGRS match current No “Update Discrepancy
discrep. UI-SOFA/DIGRS Issue
billing amt? Status 1.2.4”
problem is
unknown.
Yes
No No
Progeon
No
Is there a question
Check network info
as to the active/disco status Yes
(ATG 9.0)
of this service?
No
Records
that have
Validate audit results and
completed
determine fix approach
Audit 1.2
Step
No
Sub Statuses
14 – Fix Needed
Or, possibly
6 – (3) Help Submitted to Billing
7 – Order Fix
8 – No Fix Needed Vicki will need to
Update Audit Status to
13 – Unable to Fix run a query (or RC
“6 IAP-(3)Help Submitted
Is a Fix Needed? Billing Only Submit BIRD Request build a queue?)
to Billing”
and update comments
Update to one of
these statuses, as
Move to “Complete 1.5”
appropriate, per the
Status Definitions.
Yes
Update Audit Status to
No “13 IAP-Unable to Fix”
and update comments
No (E or N) No No (System)
IAP-Pending SH Review
SOFA changes Audit
Status & Sub to “IAP-
Current Status should DIGRS=M”
be (could only be) IAP-Pending Further
Record enters (or Record ignored by Research
“IAP (no sub status)”
remains in) SOFA SOFA
with “System” as the
Owner
Yes
IAP-(3)Help Submitted to
Billing SOFA changes Audit
SOFA changes Audit Status & Sub to
Status & Sub to “Complete-FA Fixed”
“Complete-FA Validated” IAP-Order Fix Submitted
Audit Complete
This process documentation is
Enter SOFA “N” out of date. See SOFA Issues
Process log and other documentation for
2.0 current list of categories and
processes.
Query to
Determine
Filtered N-
“N” Category Yes – “N”
A Records
2.1
Populate Discrepancy
2. Asia-Pac Orders Type as “Data Integrity-
Order Issue
Assess and Fix via Is this record still an Move to “Complete Audit
4. IA Orders Yes No – “M”
Reporting Offline “N”? 1.5”
No – “E”
Populate Discrepancy
Move to “SOFA Routine
5. Cancelled Discos Type as “Revenue
Audit 1.0”
Impact-Under”
Audit Statuses:
In Audit Process
- (null)