7-Attachment 5 - SOP User Stories.pdf
PDF 134 KB Posted
- Attached to
- Service of Process (SoP) Request for Proposal
- Solicitation number
- 302-26-02263
- Issued by
- Texas
About this file
This document is a user stories attachment for a Service of Process (SoP) Request for Proposal issued by the Texas Office of the Attorney General (OAG) for the Child Support Division (CSD). The attachment outlines ten vendor user stories that define system requirements for a Service of Process platform. The contractor must receive service requests and documents from CSD's portal, accept multiple file types (PDF, XLS, XLSX, DOC, DOCX, JPG, PNG, GIF) with a maximum of 20 files per request and 20MB per file, and validate whether received service packets are complete or incomplete. The system must communicate service attempt results using specific reason codes, receive updates including closure requests, cancellation requests, and address changes, and facilitate information exchange between CSD field users and the contractor. The contractor must also send Return of Service affidavits as separate images, provide associated dates (submission, filing, and return dates), receive and process substitute service types and show cause order information, and send photo images of service attempt locations with supporting data fields for date, time, and location.
The user stories document does not address pricing terms, set asides, incumbents, funding amounts, or contract duration, as it functions as a technical specifications attachment rather than a comprehensive RFP summary. This attachment serves as functional requirements documentation that establishes acceptance criteria for system capabilities the selected contractor must develop and implement to support CSD's Service of Process operations across in-state, nationwide, and international locations.
View the file
Other files
Show all 15
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 5, Service of Process User Stories
Vendor User Stories (US) US 1 – Receive Service Request from CSD Description - When a CSD user initiates a service request to the Contractor, they will be required to upload the service documents to CSD’s portal and the Contractor should accept the service documents from CSD’s portal with the service request data. In addition, a CSD user may add or change documents associated with an open service request in CSD’s portal, and the Contractor should accept the updated the service documents from CSD’s portal.
Acceptance Criteria 1 - The service documents, including document type and other information (data), received from CSD with the initial service request should be loaded into the Contractor’s system.
Document types and other information includes:
• Citations, with any document referenced in the Citation (exist)
• Subpoena (exist)
• Precepts, with any document referenced in the Precept (exist)
• Notice, along with any document referenced in the Notice (exist)
• Identification (ID) sheet (exist)
• Photo (exist)
• Service Request Packet (when documents are combined)
• Refer to the IEPD20 for data received with a services request
Acceptance Criteria 2 - New and/or updated service documents received from CSD for an existing service request should be loaded into the Contractor’s system.
Acceptance Criteria 3 - Accept the following file types *.*PDF, .XLS, .XLSX, .DOC, .DOCX, JPG, .PNG, .GIF and 20 or fewer files.
Acceptance Criteria 4 – Accept files that are 20MB or smaller.
US 2 – Notify CSD if a Service Packet Received is Complete or Incomplete Description – When the Contractor receives a service packet from CSD’s portal, the Contractor should notify CSD if the packet is complete or incomplete. If incomplete, reason(s) should be returned to CSD.
Acceptance Criteria 1 – When a service packet is received from CSD, the Contractor should review and provide a response to CSDs portal identifying if the packet is complete or incomplete. If incomplete, the Contractor should document the reasons the packet is incomplete and send it to CSD in a free form text field.
US 3 – Communicate Result Reason Code for a Service Attempt Description – When the Contractor attempts service, successful or unsuccessful, provide CSD with a result reason so that CSD can determine the next appropriate action. (Note: CSD wants this information at an attempt level vs. a request level)
Acceptance Criteria 1 – When a service attempt is made, provide CSD with the appropriate result reason codes. The current list of result code values is provided in a workbook that is attached.
• See result codes workbook
• Information provided.
o Attempt Result - Successful/Unsuccessful o Attempt Result Reason o Overall attempt result per address o Attempted address [existing attribute already provided] o Service Request Result [existing attribute already provided] o Date/Time of attempt [existing attribute already provided] o Refer to the IEPD21 for result data sent
US 4 – Receive Closure and Cancellation Requests, Address Updates and other Updates from CSD
• Description – The Contractor should receive closure and cancellation requests, and other service request updates from from CSD and update a request as appropriate.
• Acceptance Criteria 1 – When an update to an existing service request is received, the appropriate data on the service request record in the Contractor’s system should be updated.
Refer to the IEPD20 for data that can potentially be updates on a service request. Refer to the IEPD20 for data updates for a services request.
US 5 – Exchange Information with a CSD Field User Description – The Contractor should enable exchange of information between a CSD field user and the Contractor without having to provide a new address or associate it to a service attempt.
Acceptance Criteria 1 – Receive and send free form text information from CSD field users that is not associated with a service attempt, service request, or a new address.
US 6 – Send Return of Service (RoS) Images to CSD Description – After completion of service, send CSD the return of service affidavits as separate images.
Acceptance Criteria 1 – When the Contractor receives RoS affidavits from the court, the Contractor should send the affidavits to CSD as separate images named as follows. (need to confirm names in design)
Documents include:
• Affidavit of Non-Service (Due Diligence) by Private Process Server
• Affidavit of Proof of Service by Private Process Server - Pre-filing
• Affidavit of Proof of Service by Private Process Server - Post-filing
• Affidavit for Substituted Service Under Rule 106/536 by Private Process Server
US 7 – Send Return of Service (RoS) Dates to CSD Description – During completion of a service request, send CSD the date the RoS (affidavits) were submitted to the court, the date the affidavit is filed (file marked), and the date it is returned to the Contractor by the court.
Acceptance Criteria 1 – When each of the following dates occur (is identified), send it to CSD. The dates the Contractor should send to CSD are:
- Affidavit submitted date
- Affidavit filed date (file marked date)
- Date affidavits returned from court
- Refer to the IEPD21 for return of service data sent
US 8 – Receive Substitute Service Type from CSD Description – When Substitute Service is used for a service request, CSD will send the type of Substitute Service request (Posting or Other) to the Contractor.
Acceptance Criteria 1 – When Substitute Service type is received from CSD, load the information into the Contractor’s system allowing user access to the information.
Substitute Service Types include:
- Posted (Attached to the door/other surface)
- Other (ex. Delivered to anyone over the age of 18 at the residence)
- Refer to the IEPD20 for substitute service data received
US 9 – Receive Show Cause Order Information From CSD Description – When a service request includes a Show Cause order, CSD will notify the Contractor in the request.
Acceptance Criteria 1 – When a service request that includes a Show Cause order is received from CSD, load the information into the Contractor’s system allowing user access to the information. Refer to the IEPD20 for substitute service data received.
US 10 – Send Service Attempt Images to CSD and Supporting Information Description – After a service attempt, send CSD a photo image of the service request attempt location.
Include data fields for:
• date
• time
• location
Acceptance Criteria 1 – Photo images are received for each service attempt including supporting information.
File details come from the government source that posted it. Updated .