Attachment A--Section C.7 Customization-Future Release Solution Spreadsheet3.xls

XLS spreadsheet 118 KB Posted Jul 13, 2009

Attached to: Crime Victims Compensation Management System (CVCMS) Federal contract opportunity
Solicitation number: CSP-09-038
Issued by: District of Columbia Government

About this file

From the source

Attachment A--Functional Requirements Spreadsheet

View the file

Other files for this federal contract opportunity

Other files attached to Crime Victims Compensation Management System (CVCMS), newest first.
File	Type	Posted
CVCMS Solicitation No. CSP-09-038.doc	DOC document	Jul 13, 2009
J.2 through J.9 Attachments.pdf	PDF	Jul 13, 2009
Attachment J.1--DC Courts General Contract Provisions.pdf	PDF	Jul 13, 2009

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Sheet1

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.0:

Functional Requirements

1.1:

Case Initiation

1.1.1:

Case Data

Allow the entry and maintenance of all Case related information and artifacts.

1.1.1.1:

Collect all existing data.

1.1.1.2:

Collect all case notes data.

1.1.1.3:

Allow tracking of all Case numbers for an action.

1.1.1.4:

Allow for an electronic copy of all forms and documents associated with a Case to be stored with the Case.

1.1.1.5:

Allow for the image of all electronically created documents and forms to be automatically saved with the Case.

1.1.1.6:

Allow for the generation of a paper copy of all Case forms and documents created electronically.

1.1.1.7:

Allow printing of Case [docket] note information on demand.

1.1.1.8:

Allow all data associated with a Case to be viewable from inquiry screens.

1.1.1.9:

Assignment of Claims Examiner

The system shall require a Claims Examiner to be assigned to a Case.

1.1.1.9.1:

Provide or allow for the creation of rules to assign a Claims Examiner.

1.1.1.9.2:

Allow all data views to be printed as reports.

1.1.2:

Case Numbering

Allow the use of multiple legacy Case numbering schemes.

1.1.2.1:

Generate and assign unique identifying numbers for each case.

1.1.2.2:

Generate and assign unique identifying numbers by fiscal year (October 1 through September 30).

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.1.2.3:

Allow the assignment of a Secondary Case number to be assigned if a Primary Claim has been filed. (Example: Primary Case = 08-0001; Secondary Case = 08-0001A

1.1.3:

E-Filing of Cases

Allow the distributed Case initiation via the Internet.

1.1.3.1:

Allow a Case to be initiated via the Internet.

1.1.3.2:

Allow assignment of participant roles at Case Initiation.

1.1.4:

Case Notification

Allow notification to Claimant and/or Victim of Case Initiation.

1.1.4.1:

Allow notification to Clamant and/or Victim of Case Initiation.

1.1.4.1.1:

Allow the generation of notifications to be printed and mailed to Claimant and/or Victim.

1.1.4.1.2:

Allow the generation of electronic notifications to be electronically sent to interested Claimant and/or Victim.

1.1.4.2:

Provide or allow the generation of notices based on activity and user defined rules.

1.2:

Case Processing

Case Initiation

1.2.1.1:

Allow for the initiation of individual cases.

1.2.1.1.1:

Maintain data collected from the CVCP Application.

1.2.1.1.2:

Assign a unique number for each case filed.

1.2.1.2:

Allow for the batch filing of Cases.

1.2.1.2.1:

Assign unique numbers for each Case in the batch.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.2.1.3:

Provide or allow the creation of a view listing the number of CVC Applications filed by a selected individual for a selected timeframe.

1.2.1.4:

Provide or allow the creation of a selection of cases by the victim or claimant.

1.2.1.4.1:

Allow a user to search a Case by user defined criteria, (i.e., Case number, full or partial name, full or partial address, offender name, Social Security Number, etc.)

1.2.1.5:

Allow maintenance of victim or claimant data.

1.2.1.5.1:

Provide or allow the assessment of payments made in each Case.

1.2.1.5.2:

Calculate the total amount of payments made in each Case.

1.2.1.5.3:

Allow the tracking of requests for payments made to servicing agencies (i.e., Hospitals, Hotels, etc.)

1.2.1.6:

Provide or allow the creation of a link to police reports by victim name

1.2.1.7:

Provide or allow the creation of a link to police reports by Central Crime Number (CCN).

1.2.1.8:

Provide or allow for the entry of information regarding bills received from service providers.

1.2.1.8.1:

Allow a user to add, edit or delete bill information from a case

1.2.1.8.2:

Allow user to indicate that a payment is approved after expense has been verified, limits have been checked, calculation completed and claim has been approved based on user defined Security Rules

1.2.1.8.3:

Capture the date that a payment has been approved.

1.2.1.9:

Provide or allow an alert or flag based on user defined requirements

1.2.1.9.1

Provide or allow for an alert or flag when an Application involves Domestic Abuse.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.2.1.9.1.1:

Maintain information on placement facilities when an Application involves Domestic Abuse.

1.2.1.9.1.2:

Provide or allow an alert or flag when an Application involves crimes committed outside of the District of Columbia.

1.2.1.9.1.3:

Provide or allow an alert or flag when a duplicate claim is filed.

1.2.1.9.1.4:

Provide or allow an alert or flag when a duplicate Social Security Number is entered.

1.2.1.9.1.5:

Provide or allow an alert or flag when related and/or companion claims have been filed.

1.2.1.9.1.6:

Provide or allow an alert or flag when a Victim is an offender in another claim

1.2.1.9.1.7:

Provide or allow an alert or flag if an Application is not filed within a timely manner based on user defined rules. (Currently 12 months from the date of a crime.)

1.2.1.9.1.7.1:

Provide or allow an alert or flag if a crime was not reported within a specific number of days based on user defined rules.

1.2.1.9.1.8:

Provide or allow an alert or flag if a Claimant is a minor.

1.2.1.9.1.9:

Provide or allow an alert or flag when information requested on the Law Enforcement Verification Form is not received.

1.2.1.9.1.10:

Provide or allow an alert or flag when information requested on the Acknowledgement Letter to the Victim and/or Claimant has not been received.

1.2.1.9.1.11:

Provide or allow an alert or flag of collateral sources on any bills received from service providers in a Case.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.2.1.9.1.12:

Provide or allow an alert or flag if duplicate bills for the same date of service are received from the same payee.

1.2.1.9.1.13:

Provide or allow an alert or flag if the maximum for each benefit type has been met or exceeded.

1.2.1.9.1.14:

Provide or allow an alert or flag if bill received has a date for service prior to the date of the crime committed.

1.2.1.10:

Allow for automatic alert or flag in a case upon total payment of the maximum amont allowed (currently $25,000).

1.2.1.11:

Provide or allow the creation of a view listing of assigned CVC cases without payment after 60 days of assignment to the Claims Examiner

1.2.1.12:

Allow for the user to manually change the status of a Case based on internal Business Processes. (Current Case Statuses used: Approved; Denied; Eligible – No Payment; and Administratively Closed)

1.2.1.12.1:

Allow for the user to define and add any additional required Case Statuses to the System

1.3:

Schedule Management

1.3.1:

Schedule Management

1.3.1.1:

Allow user creation of scheduling rules.

1.3.1.1.1:

Provide or allow the creation of Case templates with standard scheduling rules to be used at Case initiation and/or assignment.

1.3.1.2:

Allow users with proper authority to override scheduling rules.

1.3.1.3:

Allow for the tracking of prerequisites for an [event].

1.3.1.4:

Notify participants when prerequisites for an [event] have not been met.

1.3.1.5:

Allow for the tracking of prerequisites for an [event].

1.3.2:

Notify participants when prerequisites for an [event] have not been met.

1.3.2.1:

Provide a listing of Cases with outstanding prerequisites.

1.3.2.2:

Allow user creation of scheduling priority rules.

1.4:

Calendar Management

Calendar Management [organize cases under a certain individual or location]

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.4.1:

Provide a multi-dimensional calendar management.

1.4.1.1:

Allow the user to select dimensions for which a calendar can be managed.

1.4.1.2:

Coordinate scheduling events across calendar dimensions.

1.4.1.3:

Allow display of multiple calendars.

1.4.1.4:

Allow on demand printing of calendar view.

1.4.1.5:

Allow calendar events be highlighted based on user defined rules.

1.4.1.6:

Allow mass updates to the calendar.

1.4.1.7:

Allow rollbacks on mass updates.

1.4.1.8:

Allow calendar events to be recorded on the Case [docket].

1.4.1.9:

Allow the reason for a calendar change to be tracked.

1.4.1.10:

Allow notification of Case participants of Calendar changes.

1.4.2:

Caseload

Allow the management of caseloads.

1.4.2.1:

Allow claims examiners view their caseload.

1.4.2.2:

Allow all or part of a claims examiners caseload to be reassigned to another claims examiner.

1.4.3:

Calendar View

Allow calendars to be viewed by interested parties.

1.5:

Record Keeping

1.5.1:

Case Records

Allow management of all records pertaining to a Case

1.5.1.1:

Allow for the official record of a Case to be maintained electronically.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.1.1.1:

Allow for the entry and tracking of the Type of Crime committed against a Victim.

1.5.1.1.1.1:

Limit the number of Crimes to be chosen to one (1) per Application.

1.5.1.1.1.2:

Allow the addition of Types of Crime(s) committed against a Victim to any Code Tables

1.5.1.1.1.3:

Allow the editing of Types of Crime(s) committed against a Victim in the existing Code Table.

1.5.1.1.1.4:

Allow the editing of Types of Crime(s) committed against a Victim in an existing Case.

1.5.1.1.2:

Allow for the entry and tracking of the type(s) of claim(s) being submitted.

1.5.1.1.2.1:

Allow for the editing of the expense limitations set within the System.

1.5.1.1.2.2:

Allow for the editing of expense categories set within the System.

1.5.1.1.2.3:

Allow for the entry and tracking of Medical costs paid on behalf of a Victim or Claimant.

1.5.1.1.2.3.1:

Allow for the tracking of limitations on dollar amounts paid for medical costs for mental health by adult and/or minor.

1.5.1.1.2.3.2:

Allow for the tracking of to whom medical costs are paid.

1.5.1.1.2.4:

Allow for the entry of any Funeral Expenses paid.

1.5.1.1.2.4.1:

Allow for the tracking of to whom medical costs are paid.

1.5.1.1.2.5:

Allow for the entry of payments made due to loss of support for survivors of homicide.

1.5.1.1.2.5.1:

Allow for the tracking of limitations on the dollar amounts paid for loss of support for survivors of homicide by dependant and by claim

1.5.1.1.2.6:

Allow for the entry of payments made for loss of services and expenses for substitute services.

1.5.1.1.2.6.1

Allow for the tracking of limitations on the dollar amounts paid for loss of services and expenses for substitute services

1.5.1.1.2.7:

Allow for the entry of payments made for loss of wages.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.1.1.2.7.1:

Allow for the tracking of limitations on the dollar amounts paid for loss of wages at 80% of net pay, up to $10,000 or one year, whichever is reached first.

1.5.1.1.2.7.2:

Allow for the emergency flagging on an ward for payment of lost wages

1.5.1.1.2.8:

Allow for the entry of payments for temporary housing.

1.5.1.1.2.8.1:

Allow for the tracking of limitations on the dollar amount paid for temporary housing.

1.5.1.1.2.9:

Allow for the entry of payments for moving expenses.

1.5.1.1.2.9.1:

Allow for the tracking of limitations on the dollar amount paid for moving expenses.

1.5.1.1.2.10:

Allow for the entry of payments for clothing replacement.

1.5.1.1.2.10.1:

Allow for the tracking of limitations on the dollar amount paid for clothing replacement.

1.5.1.1.2.11:

Allow for the entry of payments for transportation expeneses in state.

1.5.1.1.2.11.1:

Allow for the tracking of limitations on the dollar amount paid for transportation expenses in state

1.5.1.1.2.12:

Allow for the entry of payments for transportation expenses out of state.

1.5.1.1.2.12.1:

Allow for the tracking of limitation on the dollar amount paid for transportation expenses out of state.

1.5.1.1.2.13:

Allow for the entry of payments of reimbursement for rental of a car to replace a car being held as evidence.

1.5.1.1.2.13.1:

Allow for the tracking of limitations on the dollar amount paid for rental of a car.

1.5.1.1.2.14:

Allow for the entry of payments for security measures for the home.

1.5.1.1.2.14.1:

Allow for the tracking of limitations on the dollar amount paid for security measures for the home.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.1.2:

Allow for the batch entry of Case data.

1.5.1.3:

Allow for all Case related information to be maintained as a chronological Case history.

1.5.1.4:

Automatically update the Case history upon an action or the completion of an event, (i.e., payment made, Case Note added, etc.).

1.5.1.5:

Allow for the editing of Case history entries.

1.5.1.6:

Closure

1.5.1.6.1:

Allow for the manual closure of a Case based on user defined rules.

1.5.1.7:

Validity Checking

Allow rules based validity checking.

1.5.1.7.1:

Allow the tracking of all events and actions related to a Case, (i.e., Requests for Payment, Payments made, etc.).

1.5.1.7.2:

Allow the tracking of the status of events or actions related to a Case.

1.5.1.7.3:

Track all dates associated with an event or action (i.e., Request for Payment date, Payment date, Denial of Payment date, etc.).

1.5.1.7.4:

Allow for the Case status to be changed based on User defined rules.

1.5.1.9.5:

Allow for validity checking to prevent incorrect data from being entered, (i.e. the date of February 29 being entered when it is not leap year, text being entered in a dollar amount field, etc.)

1.5.1.8:

Mass Updates

Allow mass updates of records.

1.5.1.8.1:

Allow for the selection by participant of Cases to be updated.

1.5.1.8.2:

Allow the mass reassignment of Cases from one claims examiner to another.

1.5.1.8.3:

Allow for [docket] entries to be created by mass changes.

1.5.1.8.5:

Provide user confirmation of records to be updated.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.1.9:

Individual Data

Track individuals associated with a Case

1.5.1.9.1:

Track party history in a Case.

1.5.1.9.1.1:

Track address history for parties to a Case.

1.5.1.9.1.2:

Track telephone number history for parties to a Case.

1.5.1.11.1.3:

Track Employment history for the Victim and/or Claimant to a Case.

1.5.1.9.2:

Allow for multiple names for a party to a Case, (i.e., AKA – Also Known As).

1.5.1.9.3:

Track roles for all individuals associated with a Case.

1.5.1.9.4:

Allow maintenance of information associated with an individual on a Case.

1.5.1.9.5:

Allow for one record per individual.

1.5.1.9.6:

Allow for the merging of multiple records of duplicate claims into a single record based on user defined rules.

1.5.1.9.7:

Allow for the tracking of multiple legacy unique numbers assigned to an individual (i.e., Social Security Number, Criminal Complaint Number, Civil Protection Order Case Number, Neglect Number, Criminal Number, Domestic Violence Number, etc.).

1.5.1.9.8:

Allow for identification of all Cases associated with an individual.

1.5.1.9.9:

Allow Agencies or organizations to be tracked as participants in a Case.

1.5.1.9.9.1:

Allow then entry of collateral sources in a Case.

1.5.1.9.9.2:

Allow the entry of referral sources to a Case, (i.e., name of referring Agency or Organization).

1.5.1.9.9.3:

Allow individuals to be associated with an organization.

1.5.1.9.10:

Allow Cases to be linked based on user defined rules.

1.5.1.9.11:

Allow the collection and tracking of individual physical characteristics of the victim and/or claimant.

1.5.1.9.11.1:

Allow the collection and tracking of an individual’s race.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.1.9.11.2:

Allow the collection and tracking of an individual’s age.

1.5.1.9.11.3:

Allow the collection and tracking of an individual’s medical, dental and or mental health.

1.5.1.9.11.4:

Allow the collection and tracking of an individual’s gender.

1.5.1.9.11.5:

Allow the collection and tracking of an individual’s [prior] disability.

1.5.1.9.11.6:

Allow the collection and tracking of an individual’s primary language.

1.5.1.9.12:

Allow for the entry of secondary Victims and/or Claimants, and/or Dependants on a case.

1.5.1.9.13:

Allow for the entry of a Claimant on a Case.

1.5.1.9.13.1:

If the Claimant is the Victim, the solution shall automatically populate the Victim information into all pertinent Claimant fields.

1.5.1.9.13.2:

If the Claimant is not the same as the Victim, the solution shall allow for the entry of the Claimant’s information.

1.5.1.11.13.2.1:

Allow entry of the Claimants relationship to the Victim in a Case.

1.5.1.9.14:

Allow the entry of Victim and/or Claimant attorney information when an Appeal is filed.

1.5.1.10:

Restitution

Allow tracking of restitution payments.

1.5.1.10.1:

Allow tracking of restitution ordered to be paid in a Criminal Case associated with the CVC Application.

1.5.2:

Records Archive

Allow archive management of records.

1.5.2.1:

Provide or allow the creation of Case archiving rules.

1.5.2.2:

Provide or allow the creation of a view listing cases ready to be archived based on user defined rules.

1.5.2.3:

Allow the identification of Cases to be archived by case type.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.5.2.4:

Allow the identification of all physical items associated with a case to be archived.

1.5.2.5:

Provide or allow the creation of a view listing archived cases and status.

1.5.2.6:

Provide or allow data necessary for reporting to remain available after the record has been archived.

1.6

Document Management

Document Management [Generate & automatically Save without scanning]

1.6.1:

Document Management

Allow the capture and management of all documents relating to a Case.

1.6.1.1:

Accept files in generally acceptable standard image formats.

1.6.1.2:

Accept files in generally acceptable standard formats, i.e. Word Documents, PDF, TIF, etc.

1.6.1.3:

Provide access to all files in a record.

1.6.1.4:

Allow the addition of text entries to the Case history record.

1.6.2:

Document Generation

Allow the generation of all Case related documents.

1.6.2.1:

Allow for the generation of documents based on Case data and events, i.e. Law Enforcement Verification Form, etc.

1.6.2.2:

Generate notifications (paper, electronic, etc.) to case participants based on Case history entries and changes in Case history entries, and automatically save the document without scanning.

1.6.2.3:

Allow the user to define rules for document generation based on Case events.

1.6.2.4:

Provide or allow the creation of time dependent rules for document generation (i.e., Acknowledgment Letter).

1.6.2.5:

Allow the batch creation of forms based on selected Cases, and automatically save to each case without scanning, (i.e., an operator can create a batch of Acknowledgment Letters for selected cases.)

1.6.2.6:

Allow the user to define the selection criteria for document generation.

1.6.2.7:

Allow printing of preprinted mailer forms.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.6.2.8:

Allow the user creation of form templates.

1.6.2.9:

Allow the use of images and watermarks on templates.

1.6.2.10:

Provide or allow the creation of a document from selected boilerplate language.

1.6.2.11:

Allow the user to maintain boilerplate language.

1.6.2.12:

Allow the generation of labels on demand.

1.6.2.13:

Allow for the placement of an electronic signature on generated documents.

1.6.2.14:

Allow for the generation of documents requesting specific information, i.e., the Law Enforcement Verification Form.

1.6.2.14.1:

Allow the tracking and monitoring of each items requested and alert user when information is not received.

1.6.3:

Document Workflow

1.6.3.1:

Allow document routing based on user-defined criteria.

1.6.3.2:

Allow documents to be routed from external sources, i.e., the Finance Office.

1.6.3.3:

Allow documents to be routed to external destinations, i.e., the Finance Office.

1.6.3.4:

Allow documents to be authorized electronically.

1.6.4:

Design & Development of Document Workflow

Allow the design and development of document workflow.

1.6.4.1:

Allow a user to develop document routing criteria.

1.6.4.2:

Allow user review and editing of documents prior to committing them to the Case record.

1.6.5:

Workflow Tracking

Allow workflow tracking.

1.6.5.1:

Allow a document to be tracked at any stage of its routing.

1.7:

Accounting

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

Account Reconciliation

1.7.1.1:

Allow the reconciliation of non-Case related requests to purchase Metro Fare Cards and Food Cards with the disbursement of those cards at the case level.

1.7.2:

Accounts Payable

1.7.2.1:

Allow the management of requests for payment.

1.7.2.1.1:

Allow for the maintenance of request for payment data.

1.7.2.1.2:

The system shall allow for requests for payment to be tracked from initiation to payment.

1.7.2.1.3:

Provide a view listing of request for payment by payee.

1.7.2.1.4:

Provide a view listing of requests for payment by Case.

1.7.2.1.5:

Provide a view listing of requests for payment that have not been paid.

1.7.2.1.6:

Allow requests for payment to be flagged based on user defined rules.

1.7.2.1.7:

Provide or allow the creation of user defined rules associated with requests for payment authorization.

1.7.2.1.9:

Allow for direct payments to be made by the Court.

1.7.2.1.10:

Allow for non-Case related requests for payment.

1.7.2.1.11:

Allow for disbursement of fare cards and/or food cards at the case level.

1.7.3:

Integration with Case Activities

1.7.3.1:

Allow interfacing with the court’s financial management system.

1.7.3.2:

Allow financial events to create an entry in the Case history.

1.7.3.3:

Allow financial adjustments to a case that would affect the amount payable.

1.7.3.4:

Provide or allow the creation of user defined rules for specific events.

1.7.3.5:

Allow the transfer of funds associated with one Case to another Case.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.7.3.6:

Allow payments to be associated with a Case.

1.7.3.7:

The system shall have the ability to make a single payment for multiple Cases and distribute the payment over the cases.

1.7.3.8:

Allow for the tracking of disbursements of fare card and/or food cards at the case level.

1.7.3.9:

Allow the entry of payment related information.

1.7.3.10:

Allow tracking of payments by Case.

1.7.3.10.1:

Allow for the tracking of payment related information.

1.7.3.10.2:

Allow for the tracking of limitations on payment related information.

1.7.3.10.3:

Allow for the tracking of payments made to attorneys handling appeals.

1.7.3.10.3.1:

Allow payments to attorneys to be tracked separately from all other payments on a case.

1.7.3.11:

Create a view listing of the payment record for a Case.

1.7.3.12:

Allow the allocation of payment to an organization based on user defined rules.

1.7.3.13:

Allow the user to define rules for payment allocation.

1.7.3.14:

Allow the generation of single payment from multiple claim requests.

1.7.3.15:

Track requests for payment during all steps of the payment process.

1.8:

Reporting

1.8.1:

Scheduled Standard Reports

1.8.1.1:

Allow for the automatic scheduling and generation of reports.

1.8.1.1.1:

Allow the users to define standard reports for automatic generation.

1.8.1.1.2:

Allow the users to define standard export files for automatic generation.

1.8.1.1.4:

Allow the users to designate the output device for the report.

1.8.1.1.4.1:

Support microfiche output.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.8.1.1.4.2:

Support FTP output.

1.8.1.1.4.3:

Support tape output.

1.8.1.1.5:

Produce standard audit reports detailing changes made to the system.

1.8.1.1.6:

Allow the generation of graphical reports.

1.8.1.1.6.1:

Allow multiple views of graphical display data.

1.8.1.1.6.2:

Allow the drill down to detail from summary graphs.

1.8.1.2:

On Demand Reports

Allow for the generation of on demand reports.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

1.8.1.2.1:

Allow the user to create, display and print on demand reports.

1.8.1.2.1.1:

Provide or allow the creation of reports detailing system tables.

1.8.1.2.1.2:

Provide or allow the creation of reports detailing system rules.

1.8.1.2.1.3:

Provide or allow the creation of reports detailing user-defined rules.

1.8.1.2.1.4:

Allow the user to define selection criteria for on demand reports.

1.8.1.2.1.5:

Allow the user to define data to be displayed on the on demand reports.

1.8.1.2.1.6:

Allow the user to define other report parameters such as sorting, headings, totals, and subtotals.

1.8.1.2.2:

Allow the user to access, display and print predefined on demand reports.

1.8.1.2.3:

Allow the user to customize predefined on demand reports.

1.8.1.2.4:

Allow on demand selection of records to export into an analysis tool (i.e., Excel).

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.8.1.2.5:

Case Reports

Provide or allow the creation of Case Reports

1.8.1.2.5.1:

Allow the selection and printing of all forms and documents associated with a Case.

1.8.1.2.5.2:

Provide or allow the creation of a Case history report.

1.8.1.2.5.3:

Provide or allow the creation of a Case report showing case status by case type. Note Current Case Statuses: Pending; Approved; Eligible – No Payment; Administrative Closure; and Denied.

1.8.1.2.5.4:

Provide or allow the creation of a report showing Cases for a Victim or Claimant by Criminal Complaint Number (Police Report Number), Social Security or Date of Birth, etc.

1.8.1.2.5.5:

Provide or allow the creation for a report listing all parties to Cases before the CVC Program.

1.8.1.2.5.6:

Provide or allow the creation of a report listing the addresses of all parties with Cases before the CVC Program

1.8.1.2.5.7:

Provide or allow the creation of a historical report listing all parties with archived Cases.

1.8.1.2.5.8:

Provide or allow the creation of a historical report listing addresses of all parties with archived Cases.

1.8.1.2.5.9:

Provide or allow the creation of lists of pending caseloads by type of [case type], by nature of action [type of crime] or by Claims Examiner.

1.8.1.2.5.10:

Provide or allow the creation of a report of cases without a scheduled next activity.

1.8.1.2.5.11:

Provide or allow the creation of a report of disposed cases.

1.8.1.2.5.12:

Provide or allow the creation of a report of cases pending specific action by selected action.

1.8.1.2.5.13:

Provide or allow the creation of a report of specific activities by selected activity.

1.8.1.2.6:

Calendar Reports

Provide or allow the creation of calendar reports. For example, could we use ‘Calendars’ for the Claims Examiners to track specific things – like the fact that they are waiting for Insurance payments before they pay a claim for payment from a Hospital?

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.8.1.2.6.1:

Provide or allow the creation of calendar reports by Case.

1.8.1.2.6.2:

Provide or allow the creation of calendar reports by selected Participant, i.e. Claims Examiner, Payee, etc.

1.8.1.2.6.3:

Provide or allow the creation of Calendar reports by selected resource [Claims Examiner].

1.8.1.2.6.4:

Provide or allow the creation of Calendar reports by date range.

1.8.1.2.7:

Financial Reports

Provide or allow the creation of financial reports

1.8.1.2.7.1:

Provide or allow the creation of reports listing financial transactions by date range (ex. All disbursements, disbursements by type).

1.8.1.2.7.2:

Allow the generation of financial reports based on type of crimes (i.e., assault, homicide, etc.).

1.8.1.2.7.3:

Allow the generation of financial reports based on type of services (i.e., medical, funeral, relocation, food cards, Metro Fare Cards, etc.).

1.8.1.2.7.4:

Allow the generation of financial reports by provider of services (i.e., Hospital, Hotel, etc.).

1.8.1.2.7.5:

Allow the generation of financial reports by type of services for a specific crime (i.e., domestic violence, assault, etc.)

1.8.1.2.7.6:

Allow the generation of financial reports for a specific Claim.

1.8.1.2.7.6.1:

Allow the generation of financial reports for a specific Claim by payee.

1.8.1.2.7.6.2:

Allow the generation of financial reports for a specific Claim by date of payment.

1.8.1.2.7.6.3:

Allow the generation of financial reports for a specific Claim by amount of payment.

1.8.1.2.7.6.4:

Allow the generation of financial reports for a specific Claim by type of services provided.

1.8.1.2.7.7:

Provide or allow the generation of financial reports based on the number of payments that have been made.

1.8.1.2.7.8:

Provide or allow the generation of financial reports based on the number of Claims paid during a period of time.

ATTACHMENT A--FUNCTIONAL REQUIREMENTS

System Currently Satisfies requirement (yes/no)

If no, future Release Version / Date

Customization/Modification Required (yes/no)

Additional Comments

1.8.1.2.7.8.1:

Provide or allow the generation of financial reports based on the number of Claims paid during a period of time by types of crimes.

1.8.1.2.7.8.2:

Provide of allow the generation of financial reports based on the number of Domestic Violence related Claims Paid.

1.8.1.2.7.9:

Provide or allow the generation of financial reports based on the number of Requests for Payment pending in Budget and Finance.

1.8.1.2.7.10:

Provide or allow the generation of financial reports providing a Summary of Payment Requests for a specific date.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Nov 14, 2017.