CTR052815_-_Exhibit_A_-_ATLAS_Replacement_System_Requirements_Rev_1_Amendment_7.pdf

ATLAS Replacement

System Requirements Rev 1. Amendment 7

System Requirements

A R I Z O N A D E P A R T M E N T O F E C O N O M I C S E C U R I T Y

C H I L D S U P P O R T M O D E R N I Z A T I O N - A T L A S

R E P L A C E M E N T

Table of Contents

1. Overview

2. ATLAS Replacement System Requirements (Arizona Specific)

2.1 Global Requirements

2.2 Functional Requirements

2.2.1 Locate

2.2.2 Paternity and Support Order Establishment

2.2.3 Case Management/Case Closure

2.2.4 Modification

2.2.5 Intergovernmental

2.2.6 Financial Management

2.2.7 Case Initiation

2.2.8 Enforcement

2.2.9 Reporting

2.2.10 Customer Service

2.3 Technical Requirements

1. Overview Based on the results of an objective evaluation of the various alternatives, ADES decided that the best solution for legacy ATLAS replacement is to transfer the Delaware Child Support System (DECSS). This ATLAS Replacement System solution is based on transferring DECSS system functional and technical components from the DECSS and customizing to meet the needs of ADES requirements defined in this document. The developed ATLAS Replacement System should be in compliance with all the mandated Federal Certification requirements by the Federal Office of Child Support Enforcement to receive certification.

The link to the Federal Certification Guide updated in 2017 is https://www.acf.hhs.gov/sites/default/files/programs/css/certification_guide_2017_final.pdf .

In addition to meeting the latest federal certification requirements as defined in the Federal Certification Guide updated in 2017, the ATLAS Replacement system must meet the specific requirements gathered by the State of Arizona Department of Economic Security (ADES) during requirements sessions with child support staff.

Below sections define the Arizona Specific ATLAS Replacement System requirements by Subject Area identified by ADES staff in addition to the federal certification requirements. These detailed requirements are grouped into Global, Functional, and Technical sections with specific subject-groups for each Subject Area.

2. ATLAS Replacement System Requirements (Arizona Specific)

2.1 Global Requirements

Requireme nt ID

Amended Action

Subject Area Description

AZ-G-001 None

Scheduling The system must provide the capability to link with the agency’s calendar application for scheduling appointments based on user’s availability and add the appointments to users calendar application.

Note None Scheduling The agency is currently on Google Mail and Google calendar, but this will be confirmed during the requirements validation sessions.

https://www.acf.hhs.gov/sites/default/files/programs/css/certification_guide_2017_final.pdf

AZ-G-002 None Scheduling The system must include a mechanism, as part of the scheduling process, to provide for specific circumstances needed for the appointment.

AZ-G-003 None Scheduling The system must have the ability to alert users and clients of scheduled and re-scheduled appointments and send reminders.

AZ-G-004 None Scheduling The system must have the ability to cancel appointments based on a list of defined situations.

AZ-G-005 None Scheduling The system must have the ability to automatically re-schedule appointments.

AZ-G-006 None Scheduling The system must provide the ability for users to close missed appointments.

AZ-G-007 None Scheduling The system must have the capability for users to enter notes pertaining to the appointment for communicating helpful information for subsequent appointments with the client, which can be utilized by other users.

AZ-G-008 None Scheduling The system must provide the ability to track missed appointments and the reason for the missed appointments.

AZ-G-009 None Scheduling The system must provide functionality to schedule the intergovernmental initiating appointment within a configurable specified time in the future (e.g., 10 days from the current date). [Intergovernmental]

AZ-G-010 None Scheduling The system must provide the functionality to schedule interviews with the CP for intergovernmental referrals.

[Intergovernmental]

AZ-G-011 None Scheduling The system must provide the functionality to schedule face-to-face meetings with the CP when their assistance is needed to obtain the additional information requested by the responding tribunal.

[Intergovernmental]

AZ-G-012 None Scheduling The system must automatically notify the appropriate user when an intergovernmental initiating appointment is scheduled with a CP. [Intergovernmental]

AZ-G-013 None Scheduling The system must check demographics and choose closest location for testing when auto-scheduling the participants. [Paternity and Support Order Establishment]

AZ-G-014 None Scheduling The system must allow for scheduling intergovernmental cases, including with genetic testing labs. [Paternity and Support Order Establishment]

AZ-G-015 None Scheduling The system must allow for self-select appointment scheduling according to location and time preferences and must include generating the acceptance/agreement forms. [Paternity and Support Order Establishment]

AZ-G-016 None Scheduling The system must send alerts/reminders to participants of scheduled genetic testing appointments. [Paternity and Support Order Establishment]

AZ-G-017

None Scheduling The system must automatically schedule genetic testing for mother and dependent child when the participant’s genetic testing is scheduled, including agreement/consent forms. [Paternity and Support Order Establishment]

AZ-G-018 None Scheduling The system must alert the CP for scheduling of genetic test for the CP and the child once the AF has been tested. [Paternity and Support Order Establishment]

AZ-G-019 None Scheduling The system must send alerts/reminders to the mother and the dependent child of the scheduled genetic testing appointment.

[Paternity and Support Order Establishment]

AZ-G-020

None Scheduling The system must automatically schedule an appointment for the CP if Alleged Father genetic testing results are negative.

[Paternity and Support Order Establishment]

AZ-G-021 None Scheduling The system must generate the documents related to consent, e.g. informed consent form, agreement of service by mail, or agreement to be bound by the genetic test results. [Paternity and Support Order Establishment]

AZ-G-022 None Document Management

The system must capture the preferred method of communication for CP, NCP and Alleged Father, such as text, links to website for forms and results of actions, priority mail, and chat.

AZ-G-023 None Document Management

The system must provide for selecting the preferred method of communication.

AZ-G-024 None Document Management

The system must provide for opting out of certain types of communication.

AZ-G-025 None Document Management

The system must provide for links to portal documents or specific types of information for clients.

AZ-G-026 None Document Management

The system must provide for selecting an option for paperless documents by the client.

AZ-G-028 None Document Management

The system must provide for methods of communication for 3rd parties and unrelated parties.

AZ-G-029 None Document Management

The system must provide a checklist to users showing what documentation has and has not been provided.

AZ-G-030 None Document Management

The system must provide links to appropriate documents.

AZ-G-031 None Document Management

The system must provide for manual or electronic generated links to documents or specific types of information on the portal.

AZ-G-032 None Document Management

The system must be able to protect certain fields on forms, allow pre-defined specific formatted information such as dates, and also provide for drop downs.

AZ-G-033 None Document Management

The system must provide the ability to auto populate documents with data available on the system.

AZ-G-034 None Document Management

The system must provide the capability of fillable/editable forms.

AZ-G-035 None Document Management

The system must provide the capabilities to capture electronic signatures and initials on all documentation for ADES users.

AZ-G-036 None Document Management

The system must provide electronic signature and initials capabilities to the clients in a secured method.

AZ-G-037 None Document Management

The system must provide pre-case storage and set a retention time.

AZ-G-038 None Document Management

The system must provide documentation storage functionality.

AZ-G-039 None Document Management

The system must provide a repository to keep records attached to the child.

AZ-G-040 None Document Management

The system must provide print functionality.

AZ-G-041 None Document Management

The system must provide the generation of documents to 3rd parties.

AZ-G-042 None Document Management

The system must accept bar coded documents from the CP, NCP or any other party, and link to case or participant.

AZ-G-043 None Document Management

The system must provide the ability for users to access electronic documents.

AZ-G-044 None Document Management

The system must provide a checklist showing what required documents have and have not been received.

AZ-G-045 None Document Management

The system must trigger an alert to users when appropriate documents are not received based on a specific timeframe.

AZ-G-046 None Document

The system must provide and support checklists of required documentation according to type of appointment.

AZ-G-047 None Document Management

The system must provide a list of documents to the client based on the type of appointment to be completed prior to the appointment.

AZ-G-048 None Document Management

The system must house intergovernmental and financial case specific FIPS information that provides how to communicate with, and the types of information needed for each jurisdiction.

AZ-G-049 None Document Management

The system must read bar codes on returned documents.

AZ-G-050 None Document Management

The system must support the capability to identify the returned document, and auto resend with new address, according to established business rules, as part of the address verification process.

AZ-G-051 None Document Management

The system must support established address date rules.

AZ-G-053 None Document Management

The system must generate documents electronically and support e-signature.

AZ-G-054 None Document Management

The system must provide the capability for users to be able to upload documents based on a participant, provide for document type, sort on document type, prevent uploading of duplicates and incorrect documents, and provide checklist of received and documents still required.

AZ-G-055 None Document Management

The system must recognize when a child emancipates, and if it is not the last child emancipating, generate a notice for right for request for review and adjustment to the parties when it meets the criteria for review and adjustment notice.

AZ-G-056 None Document Management

The system must automatically generate and store all documents where appropriate.

AZ-G-057 Removed Document

The system must have the capability to assign multiple case numbers to the same documents. (e.g. change of custody)

AZ-G-058 None Document Management

The system must create an electronic packet of all forms for the Attorney General after approval.

AZ-G-059 None Document Management

The system must allow users to modify and save electronic forms at each step of process.

AZ-G-062 None Document Management

The system must support automatic and manual generation of letters to CP inquiring as to status of protection order at designated time frame. [Case Management]

AZ-G-063 None Document Management

The system must support the generation of notice of closure termination based on closure reason codes established by business rules. [Case Management]

AZ-G-064 Removed Document Management

The system must have the ability to generate appropriate closure documents to 3rd parties on demand. [Case Management]

AZ-G-065 None Document Management

The system must automatically generate a case closure letter to notify NCP when case is closed. [Case Management]

AZ-G-066 None Document Management

The system must automatically generate a termination of services letter to notify the NCP. [Case Management]

AZ-G-067 None Document Management

The system must automatically generate the appropriate notice based on the situations of the closure. [Case Management]

AZ-G-068 None Document Management

The system must be able to manually generate intergovernmental notices and forms for sending to other state and maintain a copy of what was provided on the system. [Intergovernmental]

AZ-G-069 None Document Management

The system must automatically populate and generate required documents to appropriate recipients upon request of an Administrative Review. [Intergovernmental]

AZ-G-070 None Document

The system must allow the user or the system to upload documents associated with the intergovernmental action.

[Intergovernmental]

AZ-G-071 None Document Management

The system must provide functionality for the user or the system to upload documents received from the responding tribunal to the case or participant record.

[Intergovernmental]

AZ-G-072 None Document Management

The system must follow established business rules to generate the appropriate verification letter, i.e., paternity only, establishment and enforcement income verification. [Locate]

AZ-G-073

Remove Document

The system must provide the capability to automatically generate appropriate documents to the CP to request more information when unable to serve the affidavit. [Locate]

AZ-G-074 Remove Document Management

The system must provide the capability to electronically file and send appropriate documents to Clerk of Court. [Locate]

AZ-G-076 None Document Management

The system must provide the capability to generate the employer verification letter electronically and manually. [Locate]

AZ-G-077 None Document Management

The system must allow for the Voluntary Paternity Packet to be stored based on case. [Paternity and Support Order Establishment]

AZ-G-078 None Document Management

The system must allow users to upload VPP from outside sources when there is not a case. [Paternity and Support Order Establishment]

AZ-G-080 None Document Management

The system must be able to generate documents that notify the CP, NCP, and AF when the system detects conflicting or incomplete information. [Paternity and Support Order Establishment]

AZ-G-081 None Document

The system must be able to send the appropriate forms (informed CP, and NCP consent, CP, NCP agreement to be bound by genetic test results) for signature by the CP and AF to the genetic testing lab.

[Paternity and Support Order Establishment]

AZ-G-082 Removed Document Management

The system must be able to accept the appropriate scanned forms or electronic forms when genetic test is performed, including E-signature options. [Paternity and Support Order Establishment]

AZ-G-083 None Document Management

They system must have the capability to store and display genetic testing results on the portal for clients to view. [Paternity and Support Order Establishment]

AZ-G-084 None Document Management

The system must send a letter to the AF with genetic test results. [Paternity and Support Order Establishment]

AZ-G-085 None Document Management

The system must auto populate the documents and refer to support order establishment process automatically when the paternity is resolved. [Paternity and Support Order Establishment]

AZ-G-135 None Document Management

The system must provide the functionality for users to upload the written response received from an income payor of type “Employer”. [Enforcement]

AZ-G-135.1 None Document Management

The system must initiate the process to add or modify an employer, based on responses received.

Note None Document Management

Requirement for new employer add by authorized users defined in Locate Requirement AZ-F-213.

AZ-G-136 None Document Management

The system must provide the functionality for the user to print an IWO. [Enforcement]

AZ-G-137 None Document Management

The system must support FIDM processes by automatically generating the appropriate notices based on business rules. [Enforcement]

AZ-G-138 None Document

The system must support the automated scanning of returned FIDM documents (where possible). [Enforcement]

AZ-G-139 None Document Management

The system must support the automated scanning of returned NMSNs, where possible, and store data provided by employers or plan administrators.

[Enforcement]

AZ-G-141 None Document Management

The system must have the ability to restrict fields based on job function

AZ-G-143 None Document Management

The system should allow for links within data to populate specifically mentioned documents (i.e. court orders on court order detail screens, notes when new document imaged, etc.)

AZ-G-161 None Document Management

The system must have the capability of uploading information from documents submitted electronically through the client portal and triggering an alert/task to the case worker/appropriate unit.

AZ-G-086 None Portal The system must provide a designed portal for users and clients.

AZ-G-087 None Portal The system must provide users the ability to access completed document via the portal.

AZ-G-088 None Portal The system must set reminders on the portal that ask clients to update contact information at designated intervals.

AZ-G-090 None Portal The system must track all activities on portal for clients.

AZ-G-091 None Portal The system must initiate a trigger to modify case as appropriate based on information from employer portal.

AZ-G-093 None Portal The system must have a self-service modification eligibility module which pulls relevant data and provides calculations for modifications. (Disclaimer – Worksheet use will not trigger a modification)

AZ-G-094 None Tasks/Alerts/Workflo ws

The system must support table driven processes.

AZ-G-095 None Tasks/Alerts/Workflo ws

The system must provide table driven information on actions based on FIPS codes.

AZ-G-096 None Tasks/Alerts/Workflo ws

The system must provide the capability to apply the appropriate established business rules for cases with designated IV-D and non IV-D workflows.

AZ-G-097 None Tasks/Alerts/Workflo ws

The system must not allow automated enforcements on designated non IV-D cases.

AZ-G-098 None Tasks/Alerts/Workflo ws

The system must provide capability to initiate appropriate workflow, per tier structure, based on data parameters, and generate alerts for users.

AZ-G-

098.1

None Tasks/Alerts/Workflo ws

The system must provide progressive, pop-up alerts on time-based service-level events (i.e. application received and case initiation

– X days remaining; eForm XXXX submission

– X days remaining).

AZ-G-099 None Tasks/Alerts/Workflo ws

The system must provide for automated triggers to move a case to the next step of workflow.

AZ-G-100 None Tasks/Alerts/Workflo ws

The system must have the capability to electronically send a case to the next step/function.

AZ-G-101 None Tasks/Alerts/Workflo ws

The system must provide an alert if no response is received based on business rules.

AZ-G-102 None Tasks/Alerts/Workflo ws

The system must allow users to initiate an alert on cases when users have identified critical forms or information that is missing and have the ability to remove the alert once the missing critical forms or information is received.

AZ-G-103 None Tasks/Alerts/Workflo ws

The system must support standardized workflows that prompts users through the tasks, or processes associated with a task, and must provide decision points within the workflow for moving to the next step.

AZ-G-104 None Tasks/Alerts/Workflo

The system must support assigning tasks to generalists and according to functions of specific offices, such as AG’s office.

AZ-G-105 None Tasks/Alerts/Workflo ws

The system must provide the ability to assign tasks to specific worker, team or roles that multiple workers share.

AZ-G-106 None Tasks/Alerts/Workflo ws

The system must allow access to other user’s worklists by authorized users.

AZ-G-107 None Tasks/Alerts/Workflo ws

The system must provide the capability to stop the workflow according to role-based permissions.

AZ-G-108 None Tasks/Alerts/Workflo ws

The system must provide the users with the ability to set priority parameters in a hierarchical structure for worklist items.

AZ-G-109 None Tasks/Alerts/Workflo ws

The system must provide supervisors with the ability to set task priorities to individual users or groups.

AZ-G-110 None Tasks/Alerts/Workflo ws

The system must remove tasks once the action is completed.

AZ-G-111 None Tasks/Alerts/Workflo ws

The system must provide an action description for each action set by the user or the system when creating a work task.

AZ-G-113 None Tasks/Alerts/Workflo ws

The system must validate a work task selected for reassignment by the user meets the work task reassignment criteria before reassigning the work task.

AZ-G-114 None Tasks/Alerts/Workflo ws

The system must allow users to view, take action or reassign tasks of other users within the same team, according to role-based access.

AZ-G-115 None Tasks/Alerts/Workflo ws

The system must allow the ability to sort on associated workflow tasks.

AZ-G-116 None Tasks/Alerts/Workflo ws

The system must allow the ability to export tasks to a spreadsheet software according to role base permissions.

Note None Tasks/Alerts/Workflo ws

The agency is currently using Microsoft Office but this will be confirmed during the requirement validation sessions.

AZ-G-117 None Tasks/Alerts/Workflo

The system must provide the ability for a supervisor to set priority of tasks to individual user or groups for work list items.

AZ-G-118 None Tasks/Alerts/Workflo ws

The system must support the ability to set priority parameters in a hierarchical structure work list items.

AZ-G-119 None Tasks/Alerts/Workflo ws

The system must provide and support an alert queue for users.

AZ-G-120 None Tasks/Alerts/Workflo ws

The system must support the ability to display default parameters for informational alerts.

AZ-G-121 None Tasks/Alerts/Workflo ws

The system must support the ability to purge tasks and informational alerts based on date parameters.

AZ-G-123 None Tasks/Alerts/Workflo ws

The system must generate a work task requiring user intervention which is determined by the source type and update address according to the hierarchy of sources.

AZ-G-124 None Tasks/Alerts/Workflo ws

The system must provide for escalation when a timeline for any task assigned to any entity is in jeopardy of being missed based on defined parameters.

AZ-G-125 None Tasks/Alerts/Workflo ws

The system must provide an alert for annual review of family violence indicator status. [Case Management]

AZ-G-126 None Tasks/Alerts/Workflo ws

The system must perform all locate activities while the case is assigned to any functional category (e.g., case initiation, establishment, enforcement, etc.). [Locate]

AZ-G-127 None Tasks/Alerts/Workflo ws

The system must automatically refer the case to the appropriate functional unit at the conclusion of the locate process.

[Locate]

AZ-G-128 None Tasks/Alerts/Workflo ws

The system must provide the capability to alert users when unable to serve affidavit, after pre-defined time frame, and start appropriate re-locate workflow, or case closure automatically. [Locate]

AZ-G-129 None Tasks/Alerts/Workflo

The system must provide the capability to process CP incarceration data generating a workflow. [Locate]

AZ-G-130 None Tasks/Alerts/Workflo ws

The system must initiate the appropriate workflow when paternity has been established, adoption, or change in placement, and must auto populate appropriate screen. [Locate]

AZ-G-131 None Tasks/Alerts/Workflo ws

The system must generate an establishment case workflow, or closure if DOC release date is after emancipation date of child. [Locate]

AZ-G-132 None Tasks/Alerts/Workflo ws

The system must generate a fast track establishment case workflow if DOC release date is prior to emancipation date of child.

[Locate]

AZ-G-133 None Tasks/Alerts/Workflo ws

The system must support the capability to trigger modifications, and terminations within a workflow or multiple workflows.

[Locate]

AZ-G-134 None Tasks/Alerts/Workflo ws

The system must initiate pre-defined workflow for deportation notices. [Locate]

AZ-G-140 None Tasks/Alerts/Workflo ws

The system must alert internal users when a case is under Administrative Review.

AZ-G-142 None Tasks/Alerts/ Workflows

The system must have the ability to display current case status (i.e., currently being reviewed by AGO).

AZ-G-144 None Tasks/Alerts/ Workflows

The system should allow for manual and automated task and workflow progress, based on actions taken in the system to complete an assigned task or workflow.

AZ-G-145 None Tasks/Alerts/Workflo ws

The system must allow workflows to be built for the different actions for IV-D, Non- IV-D and tribal environments. Depending on environment, certain workflows can be excluded. (example, there should not be enforcement workflows for Non IV-D cases.)

AZ-G-146 None Attorney General’s Office Legal Processing

The system must establish legal work flows for the attorney general’s office to track court proceedings

AZ-G-148 None Attorney General’s

Processing

The system must allow legal case assignment for attorney, legal case manager, legal data/case processor in a variety of ways (alpha, random, numeric)

AZ-G-149 None Attorney General’s

Processing

The system must show when a case is being worked by the Attorney General’s office

AZ-G-150 None Attorney General’s

Processing

The system must Include information that allows a user to know why the case is being worked by the attorneys e.g. case analysis or litigation

AZ-G-151 None Attorney General’s

Processing

The system must include a rules-based system for suppressing specific enforcement actions while a case is in litigation

AZ-G-152 None Attorney General’s

Processing

The system must provide a section where Attorney General can provide secured attorney/client privileged case notes separate from the day to day case notes.

AZ-G-153 None Attorney General’s

Processing

The system must be able to track different stages of litigation proceedings.

AZ-G-154 None Attorney General’s

Processing

The system must be able to assign task to appropriate individuals or team based on legal assignment.

AZ-G-155 None Attorney General’s

Processing

The system must include a document generation capability that will produce pleadings for litigation

AZ-G-156 None Attorney General’s

Processing

The system must track judgments and administrative liens that are recorded so that they can be timely released according to law.

AZ-G-157 None Attorney General’s

Processing

The system must track the creation and issuance of Administrative Income Withholding Orders

AZ-G-158 None Attorney General’s

Processing

The system will allow creation of case management reports by a user based on case criteria or stage of litigation and the attorney the case is assigned to.

AZ-G-159 None Attorney General’s

Processing

The system will have the ability to generate case management alert to the user regarding critical information (e.g. new information received, SOL running, insufficient or inconsistent data, etc.)

AZ-G-160 Removed Attorney General’s

Processing

The system will support interfaces with other agencies (e.g. ADOC, FAA and DCS), process servers and the court (including e-filing)

2.2 Functional Requirements

2.2.1 Locate

Requirement

ID

Amended Action

Interface Description

AZ-F-220 Removed The system must interface directly with all County probation offices.

AZ-F-220.1 Removed The system must provide an interface with all the County probation offices through a nightly batch job.

AZ-F-220.2 Changed to Primary Requirement

The system must capture demographic data for CP, NCP, and child, including the release address, employer data, address updates, terms of probation, case manager information, e.g. probation officer contact information, and other appropriate 3rd party data.

AZ-F-220.3 Removed The system must have the ability to send event-based requests to receive all data from County probation office for ADES to perform an initial match against system data.

AZ-F-220.4 Removed The system must have the capability to support a bi-directional interface with County Probation offices.

AZ-F-220.5 Removed The system must provide to Probation offices data pertaining to existing child support cases/compliance.

AZ-F-221

Removed The system must interface with Wage – Guide/BG01.

AZ-F-221.1 None The system must support a one directional interface to capture unemployment compensation data (DERS).

AZ-F-221.2 None The system must process application, the quarterly wage data, including taxes and benefits along with the source.

AZ-F-221.3 None The system must populate income data received from

GUIDE.

AZ-F-221.4 None The system must read active, single source addresses for UI benefits and auto update the system, and if not active, follow address tier structure rules for review.

AZ-F-221.5 None The system must inactivate the client employment when a UI benefits application is processed.

AZ-F-231 None The system must interface with Unemployment Insurance

(UI).

AZ-F-222

None The system must interface with Wire Third Party Query

(WTPY).

AZ-F-222.1 None The system must support a bi-directional interface with WTPY to add and verify SSN.

AZ-F-222.2 None The system must capture SSI/SSA income/benefits data from WTPY interface and provide a mechanism to auto match the data against existing system data.

AZ-F-222.3 Removed The system must provide a link to WTPY for users to access manually.

AZ-F-222.4 None The system must provide an interface with SSA to receive new and updated SSA data through nightly batch process.

AZ-F-222.5 None The system must obtain data from SSA/SSI for quarterly reconciliation.

AZ-F-233 Revised The system must interface with Social Security Administration. in real time.

AZ-F-262 None The system must use federal and state sources to acquire and verify Social Security Numbers.

AZ-F-262.1 None The system must use federal and state sources to acquire Social Security Numbers.

AZ-F-262.2 None The system must support FCR receiving the verified SSN.

AZ-F-262.3 None The system must support the ability to manually acquire the missing/partial SSN.

AZ-F-262.4 None The system must support FPLS as the last resort for verifying SSN/SSA.

AZ-F-261 None The system must update the database with all relevant information received from the FCR interface.

AZ-F-261.1 None The system must provide the capability to receive all relevant FCR data, run validation, filter out exceptions, process and load data into the system.

AZ-F-261.2 None The system must have the capability to process an FCR reconciliation file

AZ-F-261.3 None The system must generate correcting transaction when the two databases in an FCR reconciliation have discrepant data

AZ-F-223 None The system must interface with Vital Records to provide birth, death, marriage information.

Note None High level requirement modified. “The system must interface with Vital Records to provide birth and death information.”

AZ-F-223.1 None The system must support a bi-directional interface with Vital Records to send/receive data pertaining to CP, NCP, child, and all parties of the case.

AZ-F-223.2 None The system must obtain client’s date of death and location of death, both county and state.

AZ-F-224 None The system must interface with the Postal Service (National Change of Address (NCOA) via the FCR).

AZ-F-239 Removed The system must support receipt of postal verifications back from Post Office electronically.

AZ-F-239.1 Removed The system must send and receive postal verification data electronically, through a nightly batch process.

AZ-F-239.2 Changed to

Requirement

The system must provide the capability to support international address verification, example emailing the parties to verify addresses.

AZ-F-239.3 Changed to

Requirement

The system must end date the address when the postal verification is not successful.

AZ-F-239.4 Changed to

Requirement

The system must require a physical address for successful PO BOX address verification.

AZ-F-239.5 Removed The system should allow for automated electronic postal verification request when client address is older than six months (or according to timelines required by business).

AZ-F-238 Removed The system must interface with United State Postal Service (USPS).

AZ-F-238.1 Removed The system must provide users with a link to the USPS for manual Locate information, if data cannot be obtained automatically.

AZ-F-226 Removed The system must interface with cell phone carriers.

AZ-F-226.1 Removed The system should provide an interface with multiple cell phone carriers for obtaining CP, NCP demographics on new or updated customer service contracts.

AZ-F-227 Removed The system must interface with public utilities.

AZ-F-227.1 Removed The system must provide multiple public utilities bi-directional interfaces to obtain demographic data, e.g., employment data on CP and NCP.

AZ-F-228 Removed The system must interface with DCS – Child Protective Services.

AZ-F-228.1 Removed The system must provide a bi-directional interface with Child Protective Services to obtain adoption, change in placement, paternity establishment, current placement, and child demographic data.

AZ-F-228.2 None The system must capture and store all adoption demographic data pertaining to the child, e.g., the transfer of support rights, terminate, placement, etc.

AZ-F-228.3 Removed The system must alert the users, if no support order is on file, that the request for child support services informational letter can be sent to foster caregiver.

AZ-F-228.4 None The system must provide the capability to automatically remove the child when a family order is modified due to child no longer in foster care.

AZ-F-228.5 None The system must initiate the appropriate workflow when paternity has been established, adoption, or change in placement, and must auto populate the appropriate screen.

AZ-F-229

None The system must interface with AZ Department of Correction (DOC).

AZ-F-229.1 None The system must provide bi-directional interfaces with private, county, state, and federal jails for obtaining inmate account balances, demographics, incarnation’s records, and photos, and other information defined.

AZ-F-229.2 None The system must receive data pertaining to CP, NCP and child.

AZ-F-229.3 None The system must auto terminate child from a case and alert user when county/juvenile interface data verifies a child is incarcerated.

AZ-F-229.4 None The system must continue to support accruals, generate auto modification, and event triggers related to incarceration status.

AZ-F-230 None The system must interface with Professional Licensing Boards.

AZ-F-230.1 Removed The system provides bi-directional interfaces with multiple licensing boards to collect demographic and licensing data from the following boards:

• Board of Relators

• Register of Contractors

• Department of Health Services

• Board of Cosmetology

• State Board of Barbers

• State Board of Insurance Agents

• Medical Professional Licensing Boards (multiple depending on type of license)

• Liquor License (by county or state)

• Department of Agriculture

• Food Handlers Card

AZ-F-230.2 Removed The system must generate a non-issuance notice to appropriate licensing board if the NCP owes child support or is eligible for enforcement.

AZ-F-230.3 Removed The system must generate a notice of intention to suspend license to appropriate licensing board if NCP owes child support and, after pre-define timeframe, suspend license if still non-compliant.

AZ-F-230.4 Revised The system must have the ability support an incorporated administrative review within the automated procedures.

AZ-F-232 None The system must interface with Child Support Lien Network (CSLN).

AZ-F-232.1 None The system must provide for a bi-directional interface and provide status of actions taken.

AZ-F-232.2 None The system must support a bi-directional interface with CSLN to collect data, and to send status of action taken to CSLN and create a case summary.

AZ-F-232.3 Removed The system must support insurance settlement actions, including placing or removing admin liens and worker compensation liens.

AZ-F-225 Removed The system must interface with Workers Compensation.

AZ-F-225.1 Removed The system must provide a one-directional interface with the Industrial Commission to receive data pertaining to CP and NCP.

AZ-F-225.2 Revised The system must capture the attorney information, the insured client’s information and employer information.

and educational background information (used for data analytics).

AZ-F-225.3 None The system must provide the capability to initiate a Limited IWO and support any potential modification actions.

AZ-F-225.4 None The system must support a bi-directional interface with the Federal Insurance Match via FCR for data pertaining to CP and NCP.

AZ-F-251 Removed The system must interface with Arizona Property Ownership Records (Assessor).

AZ-F-251.1 Removed The system must provide a one directional interface with the Assessor to collect and store CP, NCP address data, e.g., residential, empty lot, business, condominium.

AZ-F-251.2 Change to Primary Requirement

The system must provide the capability to remove unused Assessor data.

AZ-F-251.3 Changed to

Requirement

The system must provide the capability to recognize if the primary address is a residential address and update the case address according to established business rules.

AZ-F-251.4 Changed to

Requirement

The system must display a list of all assets for CP, NCP owned property.

AZ-F-251.5 Changed to

Requirement

List all generated lien, and judgement orders recorded against the NCP or CP (including rental property), depending on jurisdiction of assets.

AZ-F-234 Removed The system must interface with the process servers tracking system.

AZ-F-234.1 Removed The system must interface bi-directionally with the process servers tracking system to support electronic service of process, and when the hearing date is assigned automatically send the documents to process server.

AZ-F-234.2 Changed to

The system must provide the capability to support the process servers both manually and electronically.

AZ-F-234.3 Removed The system must provide the capability to request and receive a hearing date from the Clerk of Court, when one is not assigned, prior to the electronic service of process filing with the process servers tracking system.

AZ-F-234.4 Removed The system must provide an electronic process to include updated addresses when process server is affected at an address different than provided.

AZ-F-234.5 Changed to

Requirement

The system must provide the capability to determine when the address from the Clerk of Court is not the same as address on file with the AG and follow pre-defined hierarchal tier structure for determining which address takes precedence.

AZ-F-234.6 Changed to Primary Requirement

The system must provide the capability to maintain history, for the AG, of the number of service affidavit attempts to include each attempt address attempt, data and time of attempts, number of days to serve, and all information on affidavit.

AZ-F-250 None The system must interface with Clerk of the Court.

AZ-F-250.1 None The system must provide a bi-directional interface with Clerk of the Court.

AZ-F-250.2 None The system must alert users to obtain/request probate information from the Clerk of Court (Superior Court) when CP/NCP death data is received.

AZ-F-250.3 None The system must electronically add orders, make adjustments to debts, populate demographic and employer data, and initiate appropriate workflow.

AZ-F-250.4 None The system must provide the capability for the Clerk of Court to collect and process CP and NCP data from the DMV, to include license suspension and re-statement, and receive confirmation suspension was removed, i.e., order # and date.

AZ-F-250.5 None The system must provide the capability to accommodate the Clerk of Court non-IV-D data capture.

AZ-F-250.6 None The system must provide Clerk of Court access to appropriate DCS screens for entering Locate data.

AZ-F-250.7 None The system must provide the option to opt in and out of electronic interface with Clerk of Court.

AZ-F-250.8 None The system must interface with the court systems to display information and alerts (i.e., warrants and power of attorney).

AZ-F-237 Removed The system must interface with U.S. Immigration.

AZ-F-237.1 Removed The system must provide a bi-directional interface with U.S. Immigration to collect data for CP, NCP, and child.

AZ-F-237.2 Removed The system must collect data from U.S. Immigration associated with employment, education, residential alien number, and tax identify number, green card, visa, student visa including expiration, and sponsor data, deportation status and all other demographic data needed for the Locate processes.

AZ-F-237.3 Removed The system must provide the capability to send notification to suspend, or not renew visa to U. S.

Immigration electronically. Please note this requirement would require a change at the federal level, and policy changes as it is not currently an IV-D function.

AZ-F-236 None The system must interface with all external sources currently in ATLAS.

AZ-F-236.1 Removed System must support interfaces with other bank vendors., e.g., BOA, AZ at Work program, and SDU vendors, to acquire Locate data for NCP and CP.

AZ-F-236.2 Removed The system must support interface with AZTEC to collect CP, NCP data needed for Locate processes.

AZ-F-236.3 Removed The system must support the bank vendor interface to receive the wages (EPC), and demographic data.

AZ-F-236.4 None The system must process unemployment benefit data from bank vendors nightly.

AZ-F-236.5 None The system must provide a bi-directional interface with the Child Support lien network for data pertaining to CP and NCP.

AZ-F-249 None The system must be able to add additional interfaces as needed.

AZ-F-249.1 None The system must support an interface with states DMV, to collect CP, NCP colored photos, vehicle registration data, all types of licenses data.

AZ-F-249.2 Removed The system must support interface with Secretary of State to collect CP, NCP data pertaining to voter registration, addresses, and ACP.

AZ-F-249.3 None The system must support interface with Health-e-Arizona Plus for demographic data.

AZ-F-249.4 Removed The system must provide an interface with Housing Department e.g., HUD, Section 8, to collect CP, NCP addresses, employment data and passport details.

AZ-F-249.5 Removed The system should provide a bi-directional interface with Accurint/Clear to support the continual validation of demographic data.

AZ-F-249.6 Removed The system must provide a bi-directional interface with the AZ Corporation Commission, including the Utilities Division, for CP and NCP address information on new or updated service contracts.

AZ-F-249.7 None The system must be able to interface with web-based portals.

AZ-F-249.8

Removed The system must support a bi-directional interface with

DCYF.

AZ-F-249.9 Revised The system must interface, real-time, with credit reporting agencies.

AZ-F-247 None The system must automate all Locate interfaces.

AZ-F-217 None The system must maintain a parameter file of Locate sources.

AZ-F-217.1 None The system must provide capability to support a parameter file that is table driven, and maintains source of data, date, and contact information.

AZ-F-217.2 None The system must utilize address modular to verify addresses, capturing verified date, and if no verified date allows for manual intervention.

AZ-F-244 None The system must provide exception reports for any interface requiring worker intervention.

AZ-F-244.1 None The system must provide a robust reporting mechanism to support exception reports, which recognizes exceptions that the system can validate utilizing interface sources, is interactive, and follows established business rules.

AZ-F-244.2 None The system must provide exception reporting to support users’ ability to apply appropriate actions, allows users interaction with the system, and allows users to add information into the system.

AZ-F-440 Removed The system must provide real time interface with Department of Public Safety (DPS) for current warrant information and license status.

Requirement

ID

Amended Action

Quick Locate Description

AZ-F-240 None The system must provide a screen from which users may request manual outgoing L01 Quick Locate requests to up to three states.

AZ-F-240.1 None The system must allow users to start an automated workflow for manual Quick Locate requests and generate manually the acknowledgment of receipt from the state.

AZ-F-240.2 None The system must allow for automatic address search capability and alert users if address is not found.

AZ-F-240.3 None The system must allow the user to start an auto workflow, with indicator that requesting state is manual and provide response manually.

AZ-F-241 None The system must provide for quick Locate requests, solicit the recipient state(s), and generate the form or route the request via CSENet.

AZ-F-241.1 None The system must list all states, and indicate if that the state utilizes CSENet e.g., yes, no, or partial.

AZ-F-241.2 None The system must provide the capability to recognize states with levels of agreement and electronically send related documents and data via CSENet.

AZ-F-241.3 None The system must provide the capability to receive Locate requests electronically from other states and initiate appropriate workflow.

AZ-F-241.4 None The system must provide the capability to reconcile with other states and maintain all the rules for that jurisdiction in one place to support electronic transmittals.

AZ-F-242 None The system must automatically process quick Locate requests received from other states by means of CSENet and return responses via CSENet.

Requirement

ID

Amended Action

Demographics Description

AZ-F-243 None The system must determine the case records with which the participant is associated.

AZ-F-243.1 None The system must consider all associated cases for the participant in Locate status.

AZ-F-252 None The system must consider a case is in Locate status when the NCP does not have a valid address of any type and does not have a known employer.

AZ-F-252.1 None The system must consider which participants are associated with Locate status.

AZ-F-252.2 None The system must have the capability to proactively search for participant’s address.

AZ-F-252.3 None The system must recognize the time duration a case has been in Locate status and validate SSN to determine according to pre-defined business rules, appropriate time duration, e.g., 1 year, 3 year, to initiate appropriate closure workflow.

AZ-F-254 None The system must maintain all demographic history for every member (i.e. address, name, SSN).

AZ-F-255 None The system must be able to determine age of address so that it doesn’t overwrite most recent address with old address.

AZ-F-248 None The system must scan and store the photograph of the CP and NCP.

AZ-F-248.1 None The system must have the capability to receive and maintain color photos, and date of photo from sources, e.g., DVM, genetic testing vendor, conferences or appointments, all kiosk vendors, and attach to CP, and

NCP.

AZ-F-248.2 None The system must provide a mechanism to blur images of non-associated persons.

AZ-F-248.3 Removed The system must allow for the automatic attachment of photos to the CP or CNP when receiving or making payments.

AZ-F-248.4 None The system must support users defined business rules for updating the CP and NCP demographics with photos.

AZ-F-248.5 Removed The system must provide mechanism to perform automatic photo searches on social media websites.

ID

Amended Action

Case Management Description

AZ-F-207 None The system must determine if the participant information received from Locate resources require verification.

AZ-F-207.1 None The system must provide the capability to perform verification according to users defined business rules governing reason and scope of verification, e.g., for AG, and federal audits.

AZ-F-260 None The system must document the acquisition date and source of the information and use logic to either update the current case information, alert the designated worker, or generate an inquiry as appropriate.

AZ-F-206 None The system must determine if the participant record is an acceptable match or a potential match.

AZ-F-211 None The system must protect against redundant and erroneous responses from the National Directory of New Hires (NDNH).

AZ-F-212 None The system must protect against redundant and erroneous responses from the State Directory of New Hires (SDNH).

AZ-F-264 None The system must provide an automatic notification screen of any critical information that is missing for users.

AZ-F-257 None The system must establish a member Locate status and monitor members in Locate status.

AZ-F-257.1 None The system must provide capability to perform continuous searches for CP, NCP demographic data, not only when in Locate status.

AZ-F-259 None The system must support the State Parent Locator Unit by monitoring the cases in Locate status.

Requirement

ID

Amended Action

Employer Description

AZ-F-210 None The system must provide the functionality for a user to upload employer information documents received from an employer.

AZ-F-213 None The system must provide the functionality according to authorized role-based users’ permissions to create a new employer record

AZ-F-213.1 None The system must protect against duplicate, and erroneous employer record, and perform search when employer record comes into the system, by FEIN, name Soundex, and address.

AZ-F-213.2 None The system must provide capability for users to search on employer info and displays list of data matching the search criteria, automatically add users selected choice.

AZ-F-214 None The system must provide the functionality according to role-based users’ permissions to update existing employer information.

AZ-F-219 Revised The interface with the employer portal must provide termination information. The system must be able to receive termination information from the Employer portal or employer web application.

AZ-F-219.1 None The system must provide the capability to inactivate income and insurance withholding, according to business rules and pre-defined time frame, when employment termination is…