Attachment H Solution Requirements S-DASOBO-00014853.xlsx
XLSX spreadsheet 65 KB Posted
- Attached to
- RFP for Litigation Case Tracking Solution
- Solicitation number
- S-DASOBO-00014853
- Issued by
- Oregon
About this file
This is a Solution Requirements document for an Oregon litigation case tracking solution RFP (S-DASOBO-00014853). The document outlines functional and technical requirements that prospective vendors must address in their proposals. The solution must support case management workflows including intake, case assignment, document management, and reporting capabilities. Key functional requirements include user role-based access controls, integration with existing systems, mobile accessibility, and customizable case status tracking. The system must accommodate multiple case types and manage associated documents, evidence, and correspondence. Technical requirements specify cloud-based or on-premise deployment options, with mandatory security standards including encryption, audit logging, and compliance with state data protection regulations. The solution must support concurrent users estimated in the range of 50-200 users and handle storage of case files with scalability provisions for growth.
The document establishes detailed specifications for system performance, including response time benchmarks of under three seconds for standard queries and uptime requirements of 99.5 percent. Vendors must demonstrate experience with similar litigation management systems serving government or legal organizations. The requirements include disaster recovery capabilities with backup systems, user support and training provisions, and a phased implementation approach. Data migration from legacy systems is required with minimal disruption to ongoing operations. The solution must provide reporting and analytics functionality, including customizable dashboards and export capabilities for case metrics and performance data. Pricing should encompass licensing, implementation, training, and ongoing support costs with clearly defined service level agreements and penalty provisions for non-compliance.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Addendum_2_WCB_DASOBO-00014853.docx | DOCX document | |
| Addendum_1_WCB_DASOBO-00014853.docx | DOCX document | |
| Attachment J eis-css-oregon-standards-spreadsheet-S-DASOBO-00014853.xlsx | XLSX spreadsheet | |
| Answers to Questions Clarification 1_WCB RFP S-DASOBO-00014853.xlsx | XLSX spreadsheet | |
| Answers to Questions Clarification 2_WCB RFP S-DASOBO-00014853.xlsx | XLSX spreadsheet | |
| Attachment A - Sample Contract 3.23.26.docx | DOCX document | |
| RFP_WCB Litigation Tracker 4.16.26 - As Posted.docx | DOCX document | |
| Attachment I - Accessibility Compliance Report Cover Sheet S-DASOBO-00014853.docx | DOCX document | |
| Attachment E Price Proposal Form_S-DASOBO-00014853.xlsx | XLSX spreadsheet |
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
Instructions
RFP S-DASOBO-00014853
Proposer Instructions - Responding to Attachment H
| Table of Contents | Reviewer Discretionary Points Available | ||||||||
| Tab & Category Number | Requirements Functional Area | Number of Requirements | Maximum Available Points | ||||||
| Tab | # Requirements | All X (requests for description) | Specific Details Request | ||||||
| Administrative Services Division | 1-Administrative Services Div | 45 | 267 | 8 | 4 | ||||
| 1 | New Request Reporting | 10 | |||||||
| 2 | Docketing of Initial Set Hearings and Subsequent Set Hearings | 9 | |||||||
| 3 | Interpreter Hiring | 11 | 2-Hearings Division | 114 | 840 | 10 | 8 | ||
| 4 | Hearing Notices | 6 | |||||||
| 5 | Settlement Documents | 4 | |||||||
| 6 | Mailroom | 5 | 3-Board Review Division | 105 | 657 | 3 | 2 | ||
| Hearings Division | |||||||||
| 7 | Case & File Management | 13 | |||||||
| 8 | Scheduling & Docketing | 13 | 4-WCB System Services Division | 14 | 93 | 10 | 1 | ||
| 9 | Notifications & Alerts | 11 | |||||||
| 10 | Hearing & Mediation Proceedings | 11 | |||||||
| 11 | Interpreter & Accessibility Mgmt | 5 | 5-Technical | 37 | 285 | 6 | 0 | ||
| 12 | Correspondence & Communication | 13 | max *1 point each | ||||||
| (0, 0.5, 1) | max *2 points each |
(0, 0.5, 1, 1.5, 2)
| 13 | Motions, Exhibits & Evidence | 25 | Maximum Base Points | 2142 | ||
| 14 | Workload & Resource Management | 2 | Reviewer Discretionary Points | 67 | 37 | 30 |
| 15 | Orders & Settlement Processing | 12 | Total Available | 2209 | ||
| 16 | Reporting & Analytics | 9 | ||||
| Board Review Division | ||||||
| 17 | Board Review | 24 | ||||
| 18 | Board Settlements | 10 | ||||
| 19 | Crime Victim Hearings | 22 | ||||
| 20 | Third-Party Settlements | 15 | ||||
| 21 | Third-Party Settlements > $1 Million | 3 | ||||
| 22 | Own Motion | 18 | ||||
| 23 | Request for Recording of Proceedings | 5 | ||||
| 24 | Request for Written Transcript of Recorded Proceedings | 8 | ||||
| WCB System Services Division | ||||||
| 25 | Litigation Scanning | 6 | ||||
| 26 | Litigation Closed-Coding | 8 | ||||
| Technical | ||||||
| 27 | Configurability | 1 | ||||
| 28 | Hosting Requirements | 4 | ||||
| 29 | Product Support | 4 | ||||
| 30 | Security | 16 | ||||
| 31 | Accessibility | 2 | ||||
| 32 | Integration | 2 | ||||
| 33 | Legal & Compliance | 1 | ||||
| 33 | Reporting | 6 | ||||
| 33 | New Request Reporting | 1 | ||||
| Total Requirements | 315 |
| Prioritization of Requirements | |
| Must Have | A Critical requirement without which the product is not acceptable to the stakeholders. |
| Highly Desirable | A necessary requirement that significantly enhances usability, efficiency, or overall value. If not available at launch, proposers may describe planned development or configuration options that would meet the need. |
| Desirable | A beneficial feature or enhancement that would improve the solution but is not required for successful implementation. |
| Instructions: Provide a response indicator in the column titled "Proposer Response" based on the description of indicators below and the drop down box provided in the column. For a requirement that receives an indicator other than "4 - Currently Exists," utilize the Proposer Comments, Descriptions, and Explanation field to provide additional information. | |
| 4 - Currently Exists | Feature/Function is included in the current release. |
| 3 - Future | Feature/function will be available within 12 months in a future release. The responding Vendor should provide the planned delivery date of the future release in comment area. |
| 2 - Custom | Feature/function is not included in the current software release, and is not planned to be a part of a future release within the next 12 months. However, this feature could be provided with custom modifications. The responding vendor should provide estimated hours to design, develop, test, and implement the customization in the comment area. |
| 1 - Third Party | Feature/function is not included in the current software release, and is not planned to be a part of a future release. However, the feature could be provided with integration with a third-party system. The responding vendor should provide the name of the third-party vendor and the number of times this integration has been performed for other customers in the comment area and define the proposed delivery date. |
| 0 - Not Available | Feature/function cannot be provided. |
| Describe Request | |
| X | For items marked with a 'x or those that request a detailed response, please ensure your proposal documentation answers specific questions/referenced products within the requirement description. Proposals may include separate documentation with the reference category and tag number to highlight key/differentiating features of the vendor solution that meet the specific requirement. (ie 1-11). Solution Requirements are worth a base total of 2,142 points. Requirements marked with an X, or those that request a detailed response, may be awarded additional points up to 67 in total. Maximum total points for all Solution Requirements shall be 2,209 points. |
Proposers stating that functions will be supplied will be contractually obligated to warrant their claim. In the event that such functionality is not available in the current release, the Proposer will be liable for any additional services and/or costs associated with developing or procuring such functionality.
Any modification to this workbook outside of the "Proposer Response" and "Proposer Comments, Descriptions, and Explanation" fields is an automatic disqualification from the Request for Proposal.
1-Administrative Services Div
| Attachment H - LCMS Requirements |
| Administrative Services Division |
| ID # | Solution Category | Functional Need | WCB Requirement | Requirement Value | Proposer Response (Please select from drop-down menu) | Describe | Proposer Comments, Descriptions, and Explanation | Auto Caluculated Response Selection Points | Maximum Available Points | |||
| Response Options | Response Points | |||||||||||
| 1 | New Request Reporting | Ability for litigants to electronically submit and file a request for hearing to WCB, requiring all information to initiate a case. Submission must trigger an auto-generated notice to designated users. | Highly Desirable | 2 | Describe how any litigant (injured worker, attorney, insurance company, employer, etc) would be able to submit and file a request for hearing electronically including what information is required by the system to complete the request, if any. | ERROR:#N/A | 6 | 4 - Currently Exists | 3 | |||
| 2 | New Request Reporting | Ability for litigants to select the type of case so it is accurately reflected on the generated notice. | Highly Desirable | 2 | ERROR:#N/A | 6 | 3 - Future | 1.5 | ||||
| 3 | New Request Reporting | Ability to indicate the need for an interpreter and specify the language required. | Highly Desirable | 2 | ERROR:#N/A | 6 | 2 - Custom | 1 | ||||
| 4 | New Request Reporting | Ability for litigants to request all‑day, half‑day, or multi‑day hearings during submission. | Highly Desirable | 2 | ERROR:#N/A | 6 | 1 - Third Party | 2 | ||||
| 5 | New Request Reporting | System must must provide confirmation when a request for hearing has been successfully submitted. | Highly Desirable | 2 | ERROR:#N/A | 6 | 0 - Not Available | 0 | ||||
| 6 | New Request Reporting | System must automatically date-stamp the receipt of each request for hearing submission. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 7 | New Request Reporting | Ability for the New Requests Specialist to receive a notification whenever a hearing request is submitted. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 8 | New Request Reporting | System must generate and retain a digital case file containing all necessary case information. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 9 | New Request Reporting | Ability to quickly identify the type of case selected during submission. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 10 | New Request Reporting | Ability to see when the acknowledgement of submission was sent to the user. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 11 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to view all submitted requests for hearing, including the date of submission. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 12 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability for the Docketing Coordinator to receive notifications when a new hearing request is submitted and a digital case file is created so the hearing can be scheduled within statutory timelines. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 13 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to determine the correct WCB location for docketing based on claimant zip code. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 14 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to view all new requests for hearing, postponed cases, and undocketed cases waiting to be scheduled. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 15 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to calculate and display the number of days since submission and identify the 90th day from the request for hearing. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 16 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to identify cases that need to be docketed for an initial 90-day set hearing. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 17 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to identify and calculate postponed cases to be redocketed within 120 days of postponement. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 18 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to build and view administrative events on the docket, including hearing/mediation pre-docket allocations, home hearing week, and travel week designations to assist scheduling. | Highly Desirable | 2 | Please provide an explanation as to how the docket is managed. Our hearings and mediations are set 3-6 months in advance, and we need to be able to set out the "pre-docket" months in advance. | ERROR:#N/A | 6 | |||||
| 19 | Docketing of Initial Set Hearings and Subsequent Set Hearings | Ability to view a proposed docketing schedule for each ALJ, considering statutory guidelines, attorney conflicts, and travel limitations. | Desirable | 1 | X | ERROR:#N/A | 3 | |||||
| 20 | Interpreter Hiring | Ability for litigant to electronically request interpreter services and specify language at any point during the litigation process. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 21 | Interpreter Hiring | The Interpreter Services Coordinator or designated users must be notified when a litigant requests interpreter services and a hearing is set. Information should include claimant name, WCB number, hearing date/time, location, assigned ALJ, and language needed. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 22 | Interpreter Hiring | Ability for the Interpreter Services Coordinator or designated users to add the interpreter hired to each case requiring interpreter services. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 23 | Interpreter Hiring | Ability for the Interpreter Services Coordinator or designated users to generate and send a notice to all parties when an interpreter is hired, including claimant details, hearing information, interpreter details, and certification information. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 24 | Interpreter Hiring | Ability for the Interpreter Services Coordinator or designated users to generate a contract for interpreter services for all hearings requiring an interpreter. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 25 | Interpreter Hiring | Ability to notify the hired interpreter and the Interpreter Services Coordinator or designated users whenever a hearing is cancelled, settled, or postponed. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 26 | Interpreter Hiring | The Interpreter Services Coordinator or designated users must be notified when a hearing is held so billing can be processed. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 27 | Interpreter Hiring | The system must provide a way to track and approve interpreter time and travel for payment. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 28 | Interpreter Hiring | Ability for hired interpreters to electronically submit signed contracts and billing documents for review and approval. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 29 | Interpreter Hiring | The system must store all hiring records for interpreter services related to each case. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 30 | Interpreter Hiring | Ability for the Interpreter Services Coordinator to track and view interpreter services data for reporting and statistics. | Highly Desirable | 2 | Please describe what data is captured and how it is reported for analysis. | ERROR:#N/A | 6 | |||||
| 31 | Hearing Notices | Ability for the Docketing Coordinator and other WCB users to enter hearing or mediation details and generate or request the appropriate notice, including event date, time, location, and notice type, when scheduling hearings or mediation events on the docket. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 32 | Hearing Notices | Ability to generate different versions of notices depending on the case type. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 33 | Hearing Notices | Ability to send notices electronically. | Highly Desirable | 2 | Please submit an example of electronic notices and how they are delivered to recipients. | ERROR:#N/A | 6 | |||||
| 34 | Hearing Notices | Ability to send printed notices by mail to parties without electronic access. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 35 | Hearing Notices | Ability to send amended notices to parties, including reasons for amendments. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 36 | Hearing Notices | Ability to view and retain all notices generated for each case. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 37 | Settlement Documents | Parties must be able to enter required information to submit and upload settlement documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 38 | Settlement Documents | Settlement documents must be date and time stamped when submitted. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 39 | Settlement Documents | LCMS must inform designated WCB users when a new document is received. The system must provide the ability for designated WCB users to review the documents in order to assign a new case number or associate them with existing cases. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 40 | Settlement Documents | Once the WCB user has associated or created a new case number, LCMS must send an electronic notification to the assigned ALJ/JA team informing them of the receipt of settlement documents. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | |||||
| 41 | Settlement Documents | Settlement documents received by mail must be physically scanned into LCMS and treated like electronic documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 42 | Mailroom | Ability to link accepted documents to currently open cases. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 43 | Mailroom | Ability to notify parties that documents were received with a date and time stamp. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 44 | Mailroom | Ability to notify parties if there was an error in uploading their documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| 45 | Mailroom | Ability to scan paper documents received into the electronic case file. | Highly Desirable | 2 | ERROR:#N/A | 6 | ||||||
| ERROR:#N/A | 267 |
2-Hearings Division
| Attachment H - LCMS Requirements |
| Hearings Division |
| ID # | Solution Category | Functional Need | WCB Requirement | Requirement Value | Proposer Response (Please select from drop-down menu) | Describe | Proposer Comments, Descriptions, and Explanation | Auto Caluculated Response Selection Points | Maximum Available Points | Response Options | Response Points |
| 46 | Case & File Management | Ability to notify administrative staff and Judicial Assistants of new file assignments. | Must Have | 3 | ERROR:#N/A | 9 | 4 - Currently Exists | 3 | |||
| 47 | Case & File Management | Ability to acknowledge new files, review, update, edit, or remove case data. | Must Have | 3 | ERROR:#N/A | 9 | 3 - Future | 1.5 | |||
| 48 | Case & File Management | Ability to review new files to determine case type (WC, OSHA, Crime Victims, Own Motion). | Must Have | 3 | ERROR:#N/A | 9 | 2 - Custom | 1 | |||
| 49 | Scheduling & Docketing | Ability to identify ALJ scheduling conflicts or conflicts with litigants. | Must Have | 3 | ERROR:#N/A | 9 | 1 - Third Party | 2 | |||
| 50 | Notifications & Alerts | Ability to add notes, set reminders, and alerts for deadlines and future actions. | Must Have | 3 | ERROR:#N/A | 9 | 0 - Not Available | 0 | |||
| 51 | Notifications & Alerts | Ability to set reminders and set alerts for deadlines and future actions for the ALJ’s attention. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 52 | Notifications & Alerts | Ability to set reminders and alerts for deadlines and future actions. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 53 | Notifications & Alerts | Ability to receive alerts if a deadline has been missed by a litigant. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 54 | Notifications & Alerts | Ability to set reminders for the JA, the ALJ, or both. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 55 | Scheduling & Docketing | Ability to add, edit, and remove events from the docket. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 56 | Hearing & Mediation Proceedings | Ability to issue notices of hearings and mediations. | Must Have | 3 | Please provide an explanation of what notice looks like, and whether information contained on the notice is customizable. | ERROR:#N/A | 9 | ||||
| 57 | Scheduling & Docketing | Ability to view all events on the docket and sort by ALJ, location, litigant, date, and time. | Must Have | 3 | Please provide an explanation of what the docket and calendar looks like for individual judges, and a compiled view of the docket for all judges at one time. | ERROR:#N/A | 9 | ||||
| 58 | Hearing & Mediation Proceedings | Ability to identify the manner of an event (in person, phone, video, hybrid). | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 59 | Hearing & Mediation Proceedings | Ability for litigants and interested parties to receive notices electronically. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 60 | Scheduling & Docketing | Ability for an attorney or law firm to view all events scheduled for that attorney or firm. | Highly Desirable | 2 | Please provide an explanation of what this calendar would look like. | ERROR:#N/A | 6 | ||||
| 61 | Scheduling & Docketing | Ability for attorney or law firm to view all events scheduled on a specific day for that attorney or law firm. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 62 | Case & File Management | Ability to update, edit, or amend case information, including parties, dates of injury, claim numbers, and WCB numbers. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 63 | Interpreter & Accessibility Mgmt | Ability to add interpreter information, including contact details for scheduling, cancellation, and hearings. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 64 | Case & File Management | Ability to consolidate or bifurcate cases. | Must Have | 3 | Please provide explanation on how case numbers can be joined in the same proceeding, or separated and set individually. | ERROR:#N/A | 9 | ||||
| 65 | Correspondence & Communication | Ability to log and document telephone communications, attempts to contact, and notes about the communication on each case. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 66 | Correspondence & Communication | Ability to link incoming and outgoing email communication to the correct case file. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 67 | Case & File Management | Ability to keep notes or create an action log within the electronic file. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 68 | Correspondence & Communication | Ability to view all correspondence submitted on a file. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 69 | Correspondence & Communication | Ability to log and view incoming and outgoing correspondence, including letters, emails, faxes, and other documents. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 70 | Correspondence & Communication | Ability for litigants to submit correspondence to the JA/ALJ on specific case files. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 71 | Correspondence & Communication | Ability for litigants to receive confirmation that correspondence has been received. | Desirable | 1 | ERROR:#N/A | 3 | |||||
| 72 | Correspondence & Communication | Ability for litigants to identify the case file when submitting correspondence or documentation. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 73 | Correspondence & Communication | Ability to create templates for correspondence. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 74 | Correspondence & Communication | Ability to create and edit language within templates. | Must Have | 3 | How are these templates generated, and is your system compatible with Microsoft Word? | ERROR:#N/A | 9 | ||||
| 75 | Correspondence & Communication | Ability to generate hard copies of correspondence. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 76 | Correspondence & Communication | Ability to scan documents received by mail or in person into the electronic file. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 77 | Interpreter & Accessibility Mgmt | Ability for litigants to request an interpreter for events, including conference calls, hearings, and mediations. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 78 | Interpreter & Accessibility Mgmt | Ability to request an interpreter for events, including conference calls, hearings, and mediations. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 79 | Motions, Exhibits & Evidence | Ability for litigants to submit motions to the ALJ both before and after a hearing. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 80 | Motions, Exhibits & Evidence | Ability for litigants to identify the type of motion when submitted. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 81 | Motions, Exhibits & Evidence | Ability for litigants to receive confirmation that a motion has been received. | Desirable | 1 | ERROR:#N/A | 3 | |||||
| 82 | Notifications & Alerts | Ability to receive alerts when a litigant submits a motion. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 83 | Motions, Exhibits & Evidence | Ability to identify the type of motion submitted. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 84 | Notifications & Alerts | Ability to receive alerts when a motion has been submitted by litigants. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 85 | Motions, Exhibits & Evidence | Ability to review motions filed by parties to make rulings. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 86 | Motions, Exhibits & Evidence | Ability to receive and identify subpoenaed records for ALJ review. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 87 | Motions, Exhibits & Evidence | Ability to assign subpoenaed records to any ALJ for review. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 88 | Motions, Exhibits & Evidence | Ability to review medical records, claim notes, or other documents in dispute by litigants. | Must Have | 3 | Please provide an explanation of how the viewer can manipulate the documents, redact them and/or remove them. | ERROR:#N/A | 9 | ||||
| 89 | Motions, Exhibits & Evidence | Ability to release and withhold some or all of the reviewed documents. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 90 | Motions, Exhibits & Evidence | Ability to store withheld documents in a secure location separate from the evidentiary record in the case file. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 91 | Motions, Exhibits & Evidence | Ability for the litigants to identify, categorize, and submit proposed exhibits, including an index. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 92 | Motions, Exhibits & Evidence | Ability for litigants to receive acknowledgement or confirmation that submitted exhibits have been received. | Desirable | 1 | ERROR:#N/A | 3 | |||||
| 93 | Motions, Exhibits & Evidence | Ability for litigants to submit video evidence in a variety of electonic formats. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 94 | Motions, Exhibits & Evidence | Ability to submit photographic evidence in a variety of electronic formats. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 95 | Motions, Exhibits & Evidence | Ability to receive and identify proposed exhibits submitted by litigants. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 96 | Motions, Exhibits & Evidence | Ability to scan exhibit submissions received by mail or in person. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 97 | Motions, Exhibits & Evidence | Ability to identify and remove duplicate submissions. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 98 | Motions, Exhibits & Evidence | Ability to identify admitted and excluded exhibits. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 99 | Motions, Exhibits & Evidence | Ability to receive and identify videos and image-based evidence. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 100 | Motions, Exhibits & Evidence | Ability to receive and identify photographs and other image-based evidence. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 101 | Motions, Exhibits & Evidence | Ability to view video and photographic evidence submitted in various formats. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 102 | Motions, Exhibits & Evidence | Ability to receive and identify physical items as evidence. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 103 | Motions, Exhibits & Evidence | Ability to change, update, or edit exhibit submissions from any computer. | Must Have | 3 | Please provide an explanation of how an exhibit is marked and re-marked. | ERROR:#N/A | 9 | ||||
| 104 | Scheduling & Docketing | Ability to set room assignments. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 105 | Interpreter & Accessibility Mgmt | Ability to document special needs for hearings related to accessibility, security, etc. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 106 | Motions, Exhibits & Evidence | Ability to review and amend evidentiary submissions in real time during a hearing. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 107 | Case & File Management | Ability to change case information in real time during a hearing. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 108 | Correspondence & Communication | Ability to take notes during the hearing in the case file. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 109 | Correspondence & Communication | Ability to send alerts, requests or messages to JA in real time during the hearing. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 110 | Case & File Management | Ability to link recording of hearing to the electronic file. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 111 | Motions, Exhibits & Evidence | Ability to review exhibits and make temporary notations or highlights. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 112 | Interpreter & Accessibility Mgmt | Ability to approve interpreter’s time spent in a hearing, conference call, or mediation. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 113 | Orders & Settlement Processing | Ability to create order templates. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 114 | Orders & Settlement Processing | Ability to write an order and review exhibits at the same time on separate screens. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 115 | Orders & Settlement Processing | Ability to review correspondence and notes on a case while writing an order (dual screen view). | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 116 | Orders & Settlement Processing | Ability to send orders to the ALJ for signature. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 117 | Orders & Settlement Processing | Ability to review orders, sign electronically, and route back to JA to issue. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 118 | Case & File Management | Ability to access final copy of order and date issued through electronic case file. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 119 | Orders & Settlement Processing | Ability for litigants to submit signed settlement documents for ALJ approval. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 120 | Orders & Settlement Processing | Ability for litigants to receive notification that settlement documents have been received. | Desirable | 1 | ERROR:#N/A | 3 | |||||
| 121 | Orders & Settlement Processing | Ability to receive notification when settlement documents have been submitted. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 122 | Orders & Settlement Processing | Ability to route settlement documents to ALJ for approval. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 123 | Orders & Settlement Processing | Ability to review settlement documents when submitted. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 124 | Case & File Management | Ability to set up a separate confidential mediation file not accessible by other ALJs. | Highly Desirable | 2 | Please describe how a confidential file would be connected to case file. | ERROR:#N/A | 6 | ||||
| 125 | Scheduling & Docketing | Ability to reserve rooms. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 126 | Case & File Management | Ability to enter contact information for multiple parties. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 127 | Hearing & Mediation Proceedings | Ability for litigants to submit confidential mediation position papers. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 128 | Hearing & Mediation Proceedings | Ability for litigants to receive confirmation that confidential mediation position papers have been received. | Desirable | 1 | ERROR:#N/A | 3 | |||||
| 129 | Hearing & Mediation Proceedings | Ability for litigants to submit documentation and/or exhibits specific to mediation. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 130 | Scheduling & Docketing | Ability for litigants to request a specific mediator and date. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 131 | Scheduling & Docketing | Ability for litigants to review a mediation availability calendar to select an available mediator and date. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 132 | Hearing & Mediation Proceedings | Ability to review documentation and/or exhibits submitted specific to mediation. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 133 | Hearing & Mediation Proceedings | Ability to review all documentation and exhibits submitted related to other events on the case file. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 134 | Notifications & Alerts | Ability to receive alerts when a hearing is cancelled for mediation. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 135 | Hearing & Mediation Proceedings | Ability to assign mediation to the requested mediator and corresponding JA. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 136 | Case & File Management | Ability to create mediation files. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 137 | Scheduling & Docketing | Ability to schedule mediations. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 138 | Hearing & Mediation Proceedings | Ability to make notes that are confidential to the mediation file only. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 139 | Hearing & Mediation Proceedings | Ability to document settlement terms if mediation is successful. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 140 | Case & File Management | Ability to redirect the hearing file to docketing or the assigned hearings ALJ to continue litigation. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 141 | Orders & Settlement Processing | Ability to review settlement documents and prepare an order to route to ALJ for approval. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 142 | Orders & Settlement Processing | Ability to review settlement documents at the same time as mediation file notes. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 143 | Notifications & Alerts | Ability to receive alerts as to whether mediation was successful. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 144 | Reporting & Analytics | Ability to receive data regarding ALJ time spent in mediation and settlement amounts if successful. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 145 | Reporting & Analytics | Ability to collect data regarding mediation status, location, and manner. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 146 | Reporting & Analytics | Ability to track number of mediations set, held, settled, or not settled, for specific periods and by ALJ. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 147 | Reporting & Analytics | Ability to collect data regarding hearings set, held, settled, postponed, or cancelled. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 148 | Reporting & Analytics | Ability to collect data regarding timeliness of orders and workload for individual ALJs and for ALJs overall. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 149 | Reporting & Analytics | Ability to run comparison reports for all data collected. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 150 | Notifications & Alerts | Ability to receive alerts if an Opinion and Order is not issued on time. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 151 | Reporting & Analytics | Ability to determine processing times for settlements and other submissions. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 152 | Reporting & Analytics | Ability to collect data regarding all orders by location, type of order, and ALJ. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 153 | Reporting & Analytics | Ability to run overall reports by month, year, and specific periods of time for each ALJ to track timeliness of orders issued. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 154 | Workload & Resource Management | Ability for Hearings Division manager to assign work to an ALJ or JA. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 155 | Workload & Resource Management | Ability to review workload of a specific ALJ or JA. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 156 | Notifications & Alerts | Ability to create alerts for ALJs, JAs, and themselves. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 157 | Scheduling & Docketing | Ability to add, change, edit, and remove ALJ conflicts from docket consideration. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 158 | Scheduling & Docketing | Ability to set pre-docket, including number of hearing weeks and mediation weeks per ALJ, number of hearing sets per week, and number of trip weeks, in advance. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 159 | Scheduling & Docketing | Ability to set, reschedule, transfer, or remove events from the docket. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| ERROR:#N/A | 840 |
3-Board Review Division
| Attachment H - LCMS Requirements |
| Board Review Division |
| ID # | Solution Category | Functional Need | WCB Requirement | Requirement Value | Proposer Response (Please select drop-down menu) | Describe | Proposer Comments, Descriptions, and Explanation | Auto Caluculated Response Selection Points | Maximum Available Points | Response Options | Response Points |
| 160 | Board Review | Ability to change user access so Board Review Staff can grant access after a case is appealed and adjust access as the case progresses. | Highly Desirable | 2 | The WCB houses the Hearings Division and Board Review, which is the first level of appeal from the Hearings Division. Please explain how the system can change user access so cases on appeal to Board Review can no longer be accessed by the Hearings Division | ERROR:#N/A | 6 | 4 - Currently Exists | 3 | ||
| 161 | Board Review | Ability for litigants to electronically submit and file a request or cross‑request for Board Review, ensuring all required information is captured to initiate the process. | Highly Desirable | 2 | Please explain how system allows litigants to file appeal requests and ensure that all required information is included. | ERROR:#N/A | 6 | 3 - Future | 1.5 | ||
| 162 | Board Review | LCMS must record the date a requst for review is received by WCB. | Highly Desirable | 2 | ERROR:#N/A | 6 | 2 - Custom | 1 | |||
| 163 | Board Review | Ability to auto‑generate and send a notification to the Board Review Specialist each time a request for Board Review is filed or received. | Highly Desirable | 2 | ERROR:#N/A | 6 | 1 - Third Party | 2 | |||
| 164 | Board Review | Ability for the Board Review Specialist to acknowledge receipt of the request and update the checkout code in LCMS to reflect the file’s status in Board Review. | Highly Desirable | 2 | ERROR:#N/A | 6 | 0 - Not Available | 0 | |||
| 165 | Board Review | Board Review Specialist must be able to data enter a request for hearing transcript. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 166 | Board Review | Ability to electronically receive hearing transcripts and notify the Board Review Specialist when the transcript becomes available.. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 167 | Board Review | Board Review Specialist must enter due dates for the briefing schedule, and LCMS must auto-generate a letter of acknowledgment and set the schedule. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 168 | Board Review | Ability to send automated reminders to designated internal users regarding due dates for briefs and other file deadlines. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 169 | Board Review | The system must provide the ability to store Board Review documents in a dedicated location only accessible to Board Review staff and allow the Board Review Specialist to add exhibits, letters, and hearing transcripts accepted at the Board level to the case file. | Highly Desirable | 2 | X | ERROR:#N/A | 6 | ||||
| 170 | Board Review | Ability for litigants to electronically file a request for extension of time to file a written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 171 | Board Review | Ability for litigants to file a written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 172 | Board Review | LCMS must record the date WCB receives a written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 173 | Board Review | Ability for Board Review staff to randomly assign case files to Board Member panelists and add additional panelists if the case requires a tiebreaker vote or is heard en banc | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 174 | Board Review | Ability for Board Members to vote on the case outcome after reviewing the case file | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 175 | Board Review | Abilit for Managing Attorney to assign case files to the appropriate staff attorney or paralegal to draft an order or memorandum | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 176 | Board Review | Ability for staff attorney to send draft orders and memoranda to the Board panel Members for review and approval | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 177 | Board Review | Ability to electronically route the file. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 178 | Board Review | As a Board Members, I need to be able to edit or approve a draft sent to me by a staff attorney | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 179 | Board Review | Ability to issue final orders electronically. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 180 | Board Review | Ability for litigants to file a request for reconsideration. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 181 | Board Review | Ability to separate confidential Board Review work product from the record sent to the court on judicial review or remanded to the Hearings Division. | Must Have | 3 | X | ERROR:#N/A | 9 | ||||
| 182 | Board Review | Ability to electronically transfer file to parties and other agencies. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 183 | Board Review | Board Requests Specialist must receive auto-generated notification of request. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 184 | Board Settlements | Ability for litigants to enter all required information into LCMS to submit and upload settlement documents. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 185 | Board Settlements | Submission of settlement documents must trigger LCMS to record the date and time of receipt. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 186 | Board Settlements | LCMS must inform the Settlement Specialist when a new document is received. The Settlement Specialist must review documents to assign a new case number or associate them with existing cases. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 187 | Board Settlements | Once the Settlement Specialist has associated or created a new case number, LCMS must send an electronic notification to the assigned Administrative Law Judge and Judicial assistant team or the appropriate Board Review attorney. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 188 | Board Settlements | Ability to review settlement documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 189 | Board Settlements | Ability to scan mailed settlement documents into LCMS and treat them like electronic documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 190 | Board Settlements | Ability to distribute settlement orders to appropriate decision maker for review and approval. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 191 | Board Settlements | Ability to notify or alert appropriate staff of tasks waiting for their review. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 192 | Board Settlements | Ability to electronically distribute final settlement orders to involved parties, with support for printing and mailing copies to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 193 | Board Settlements | Ability to review file and sign order. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 194 | Crime Victim Hearings | Ability for litigants to file a request for Crime Victim Hearing. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 195 | Crime Victim Hearings | LCMS must record the date of receipt by WCB on the request for Crime Victim Hearing document. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 196 | Crime Victim Hearings | Board Review Coordinator must receive auto-generated notification of request. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 197 | Crime Victim Hearings | System must auto-generate a digital case file reflecting claimant and DOJ information. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 198 | Crime Victim Hearings | System must store the new request for hearing in the digital case file, showing the date received by WCB. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 199 | Crime Victim Hearings | Board Request Specialist must be able to view the request and select the correct case type. LCMS must automatically assign a new case number for the selected case type. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 200 | Crime Victim Hearings | Once the WCB case number is created, the digital case file name must be updated to include claimant’s name, WCB case number, and claimant’s attorney name. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 201 | Crime Victim Hearings | LCMS must list the date of receipt and type of document received in the case history. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 202 | Crime Victim Hearings | Ability to request and digitally receive records from the Oregon Department of Justice. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 203 | Crime Victim Hearings | Ability to schedule hearings by entering hearing information into the docket. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 204 | Crime Victim Hearings | Ability to generate and electronically send notices on demand. Paper copies must be printed for parties not in LCMS. Notifications of new notices must be sent to the Board Review Specialist. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 205 | Crime Victim Hearings | Ability to data enter case status into docket. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 206 | Crime Victim Hearings | Ability to enter due dates for the briefing schedule, with LCMS auto-generating a letter of acknowledgment and setting the schedule. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 207 | Crime Victim Hearings | LCMS must send reminders on due dates to specific groups of users. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 208 | Crime Victim Hearings | Ability for litigants to file a request for briefing extension. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 209 | Crime Victim Hearings | Ability for litigants to file a written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 210 | Crime Victim Hearings | LCMS must insert the date of receipt by WCB on the received written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 211 | Crime Victim Hearings | Ability to electronically route the file to appropriate staff for drafting a final order once the briefing schedule or hearing is completed. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 212 | Crime Victim Hearings | Ability to electronically publish proposed orders to involved parties, with support for printing and mailing copies to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 213 | Crime Victim Hearings | Ability to electronically review case documents and exhibits from any computer during and after the hearing to support drafting decisions or orders. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 214 | Crime Victim Hearings | Ability for litigants to file objections to proposed orders. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 215 | Crime Victim Hearings | Ability to issue final orders electronically. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 216 | Third-Party Settlements | Ability for litigants to file a request for Board resolution of third-party settlement. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 217 | Third-Party Settlements | LCMS must record the date of receipt by WCB on the request. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 218 | Third-Party Settlements | Ability to auto‑generate and send a notification to the Board Requests Specialist each time a request for Board resolution of a third‑party settlement is filed or received. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 219 | Third-Party Settlements | System must auto-generate a digital case file reflecting claimant’s name. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 220 | Third-Party Settlements | System must store the request for Board resolution of a third‑party settlement in the digital case file, including the date received by WCB. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 221 | Third-Party Settlements | Board Requests Specialist must be able to view the request and select the correct case type. LCMS must automatically assign a new case number for the selected case type. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 222 | Third-Party Settlements | Once the WCB case number is created, the digital case file name must be updated to include claimant’s name, WCB case number, and claimant’s attorney name. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 223 | Third-Party Settlements | LCMS must list the date of receipt and type of document received in the case history. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 224 | Third-Party Settlements | Ability to enter briefing‑schedule due dates and automatically generate and electronically send an acknowledgment letter with those dates, along with the hearing transcript, to the parties involved. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 225 | Third-Party Settlements | LCMS must send automated reminders to designated internal users regarding due dates for briefs. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 226 | Third-Party Settlements | Ability for litigants to file a request for briefing extension. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 227 | Third-Party Settlements | Ability for litigants to electronically submit and file a written brief, ensuring all required information is captured. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 228 | Third-Party Settlements | LCMS must automatically date‑stamp any written brief or related document received by WCB. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 229 | Third-Party Settlements | Ability to electronically route the file to appropriate staff for drafting a final order once the briefing schedule is completed. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 230 | Third-Party Settlements | Ability to issue final orders electronically. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 231 | Third-Party Settlements > $1 Million | Ability for litigants to file a request for Board resolution of third-party settlements over $1 million. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 232 | Third-Party Settlements > $1 Million | LCMS must record the date of receipt by WCB on the third-party settlement over $1 million. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 233 | Third-Party Settlements > $1 Million | Ability to electronically publish the Board’s acknowledgment of third‑party settlements over $1 million. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 234 | Own Motion | Ability for litigants to file an Own Motion Request/Recommendation, including uploading pertinent documents. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 235 | Own Motion | LCMS must automatically record the date any Own Motion Request/Recommendation is received by WCB. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 236 | Own Motion | Own Motion Coordinator must receive auto-generated notifications of new requests. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 237 | Own Motion | System must auto-generate a digital case file reflecting claimant’s name. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 238 | Own Motion | System must store the new Own Motion Request/Recommendation in the digital case file, showing the date received by WCB. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 239 | Own Motion | Ability for the Own Motion Coordinator to view the request, select the correct case type, and have LCMS automatically assign a new WCB case number. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 240 | Own Motion | LCMS must list the date of receipt and document type in the case history for all received documents. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 241 | Own Motion | Ability for the Own Motion Coordinator to acknowledge the request, update the checkout code, and ensure notifications are electronically sent to all parties, with paper copies mailed to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 242 | Own Motion | Ability to electronically send letters and interim orders. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 243 | Own Motion | Ability to enter briefing‑schedule due dates and automatically generate and electronically send an acknowledgment letter with those dates, along with the hearing transcript, to the parties, with paper copies mailed to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 244 | Own Motion | LCMS must send automated reminders to designated internal users regarding due dates for briefs, with paper copies mailed to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 245 | Own Motion | Ability for litigants to file a request for briefing extension. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 246 | Own Motion | Ability for litigants to file a written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 247 | Own Motion | LCMS must record the date of receipt by WCB on the received written brief. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 248 | Own Motion | Ability to electronically refer case to other agencies (e.g., arbiter scheduling team at WCD). | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 249 | Own Motion | Ability to electronically receive arbiter records from other agencies (WCD/arbiter panel). | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 250 | Own Motion | Ability to electronically assign and route the file to appropriate staff for drafting a final order once the briefing schedule is completed. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 251 | Own Motion | Ability to electronically publish final orders to involved parties, with paper copies mailed to parties not using LCMS. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 252 | Request for Recording of Proceedings | Ability for litigants to file a request for digital recording of proceedings. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 253 | Request for Recording of Proceedings | LCMS must generate a letter acknowledging receipt of the digital recording request. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 254 | Request for Recording of Proceedings | Ability to electronically communicate with ALJ for approval of release if case is within ALJ jurisdiction. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 255 | Request for Recording of Proceedings | Ability to submit electronic bills to requesting parties. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 256 | Request for Recording of Proceedings | Ability to electronically distribute requested digital recordings. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 257 | Request for Written Transcript of Recorded Proceedings | Ability for staff to request a written transcript of recorded proceedings from the Transcript Coordinator. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 258 | Request for Written Transcript of Recorded Proceedings | Ability to receive electronic notification of transcript requests. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 259 | Request for Written Transcript of Recorded Proceedings | Ability to electronically transmit audio recordings and required information to the vendor for transcript processing. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 260 | Request for Written Transcript of Recorded Proceedings | Ability to receive digital copies of typed transcripts from vendor. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 261 | Request for Written Transcript of Recorded Proceedings | Submission of typed transcripts must trigger LCMS to record the date and time of receipt. | Highly Desirable | 2 | ERROR:#N/A | 6 | |||||
| 262 | Request for Written Transcript of Recorded Proceedings | LCMS must store a copy of each written transcript in the case file. | Must Have | 3 | ERROR:#N/A | 9 | |||||
| 263 | Request for Written Transcript of Recorded Proceedings | Ability to receive electronic billing from the vendor. | Highly Desirable | 2 | ERROR:#N/A | 6 |
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 .