| |
31 - Combine True Name and Aliases for timepay
|
|
| Request Status Summary |
| Request Status |
Authorized |
| JISC Priority |
12 |
|
| Request Detail |
| Requestor Name: |
| |
Vance, Aimee R |
| Origination Date: |
| |
09/21/2010 |
| |
|
|
Recommended Endorser:
|
| |
District and Municipal Court Management Association |
|
| Request Type: |
Change or Enhancement
|
| Which Systems are affected? |
Judicial Information System (JIS)
|
| Business Area: |
Accounting
|
| Communities Impacted: |
County Clerks
Superior Court Administrators
CLJ Managers
|
| Impact if not Resolved: |
Medium |
| Impact Description: |
A person could be set up on two different timepay agreements and required to make 2 payments in one month rather than a consolidated payment. |
|
|
| What is the Business Problem or Opportunity |
This is unresolved change requests #33 and #164
#33 - Courts want a function to combine all ARs for a true name and aliases to put on timepay.
#164 - Court has requested that cases attached to a person's AKA as well as true name be available on TPSE. |
| Expected Benefit: |
The court user would be able to see all ARs for the person and set up one timepay for the individual regardless of the name the case was filed under. |
| Endorsement Detail
|
| Endorsing Committee |
| |
District and Municipal Court Management Association |
| Endorser Name: |
| |
Vance, Aimee R |
| Origination Date: |
| |
09/21/2010 |
|
| Endorsing Action: |
Endorsed |
| Endorser’s Explanation and Comments |
This request was discussed by the Endorsement Group at a previous meeting. |
|
|
| AOC Analysis Detail
|
| Analysis Date: |
09/30/2010
|
| Request Rationale |
| Aligns with JIS Business Priorities, IT Strategies & Plans: |
Yes |
| Aligns with applicable policies and with ISD Standards: |
Yes |
| Breadth of Solution Benefit: |
Wide |
| Cost Estimates |
| Cost Benefit Analysis Complete? |
No |
| Cost to Implement? |
940 hours |
| Projected Maintenance cost? |
None |
| Feasibility Study needed? |
No |
| Court Level User Group |
| Courts of Limited Jurisdiction |
| Approving Authority |
JISC |
|
| Request Summary: |
This request seeks to enable all Accounts Receivables for a true name and associated aliases to be combined on the TPSE screen. This change will only affect the CLJs. |
| Business Impacts: |
This change will allow court personnel to see all accounts receivable for a person and set up a single Time Pay for the individual no matter which name the case was filed under. Currently the courts have to set up a Time Pay agreement for each name which can result in an individual having to make two payments in a month rather than a single, combined payment. |
| Summary of Proposed Solution |
The solution that the Administrative Office of the Courts (AOC) proposes will allow courts to combine Accounts Receivable (AR) for a true name and aliases into a single Time Pay agreement. This enhancement will function in the same way that the system currently allows courts to combine multiple ARs for a true name into a single Time Pay. |
| Proposed Solution |
AOC proposes to provide the ability to combine ARs from aliases into the true name ARs to create a single Time Pay. When a true name has associated aliases, court staff will be given an opportunity to select which ARs associated with the aliases will be combined into a single Time Pay. This request would impact screens: TPSC, TPSE, and RCP. In addition, Time Pay statements and Time Pay reports would also be affected. AOC anticipates a change to the data schema and a probable data conversion as part of this effort. |
|
|
| Confirmation of Endorsing Action Detail
|
| Endorsing Committee |
| |
District and Municipal Court Management Association |
| Endorser Name: |
| |
Vance, Aimee R |
| Origination Date: |
| |
10/07/2010 |
|
| Endorsing Action: |
Endorsed |
|
|
| Court Level User Group Decision Detail
|
| CLUG |
Courts of Limited Jurisdiction |
| Chair of Group |
Cynthia Marr |
| Date of Decision |
12/02/2010 |
| Decision |
| Decision to Recommend for Approval |
Unamimously recommended to the approving authority |
| Priority Processing Status |
Prioritized |
| Ranking |
| Request Priority |
13 |
| Request Importance |
Medium |
|
| Scoring Detail |
Score / Possible |
| Business Value |
3.5 / 10 |
| Relative Priority |
7 / 10 |
| Cost |
3 / 5 |
| Complexity/Level of Effort |
6 / 10 |
| Risk |
2.5 / 5 |
| Benefit / Impact |
3 / 5 |
| Impact of Doing Nothing |
0 / 5 |
| Total Score |
25 / 50 |
|
| Additional Notes |
The CLUG combined this request and Request #26, as recommended by the AOC analysis. Although the IT Governance Portal shows Requests #26 and #31 prioritized separately, the CLUG prioritized them and sent them forward for approval to the JISC as one combined request. |
|
| Implementation Detail
|
| Analysis Date: |
|
| Implementation Stage |
Authorized |
| Prioritization Option: |
Prioritized |
|
|
Comments:
|
|
This request was authorized by the JISC on Feb 18, 2011.
|
|
|
|
|
