The file's text, extracted by GovTribe without its formatting.
SCHEDULE A – ATTACHMENT 1 – BUSINESS SPECIFICATION WORKSHEET
Instructions for Completing the Business Specifications Worksheet Contractors must respond to each business Specification on how they will meet the requirements in the document provided. Contractor must not alter the document.
The Business Specifications Worksheet contains columns and is defined as follows:
Column A: Business Specification number.
Column B: Business Specification Column C: Contractor must indicate how they will deliver the business Specification and should not just indicate they can do it, or they can meet the requirement. Such responses may be considered deficient.
NOTE:
All configuration changes made during the term of the awarded contract must be forward-compatible with future releases and be fully supported by the awarded Contractor without additional costs.
| Business Specification Number |
| Business Specification |
| Contractor must explain how they will deliver the Business Specification |
General System: All core system level requirements (e.g. Creating a record, standard formatting, etc.)
| 1 |
| The system must only allow sensitive information (i.e. PII) to allowed users, following state and federal rules. |
| 2 |
| The system must have a process to create a viewable history log and audit trail of all transactions, this includes all correspondence received and/or sent, and all modifications made. |
| 3 |
| The system must automatically update any county/city/state fields from an entered zip code. |
| 4 |
| The system must allow for user to select county/city if multiple counties/cities are found for a zip code. |
| 5 |
| The system must have the ability to stay current with any zip code changes. |
| 6 |
| The system must allow for standard US zip codes formatting of 5 or 9 digits. |
| 7 |
| The system must allow for standard formatting of foreign postal codes. |
| 8 |
| The system must have a process to validate and verify addresses. |
| 9 |
| The system must allow for partial search functionality. |
| 10 |
| The system must have a process to restore deleted, archived, or purged records. |
| 11 |
| The system must only allow comments to be changed or deleted for those with allowed privilege. |
| 12 |
| The system must have the capability to validate data entered on required fields. |
| 13 |
| The system must display informative error messages when invalid data is entered by users. |
| 14 |
| The system must standardize the display of a required field. |
| 15 |
| The system must, during a workflow process, be able to create summary and detailed reports of all workflow actions. |
| 16 |
| The system must be able to manually initiate any workflow step. |
| 17 |
| The system must be able to start workflows based on automatic actions, such as receiving a document electronically or the type of document received |
| 18 |
| The system must inform, via email/alert, the DIFS staff that are responsible for any task contained within the workflow. |
| 19 |
| The system must have a standard and consistent format for telephone numbers |
| 20 |
| The system must display an error message when the FEIN # is not entered. |
| 21 |
| The system must have an edit feature. The purpose of edit feature - Back button or recall button when a wrong entry is entered and saved |
| 22 |
| The system must have the ability to reopen or revert back to a prior workflow step if the wrong attempt was selected or information was received subsequently that changed the direction of DIFS decision. |
| 23 |
| The system must have the ability to delete an attachment |
| 24 |
| The system must have an option to rollback when user choosing a wrong attempt. |
| 25 |
| The system must provide the ability to notify users and show reminders for pending workflow tasks based on the due date threshold defined for the task. |
| 26 |
| The system must provide the ability to notify users of past-due tasks. |
| 27 |
| The system must allow the user to revert workflow tasks to any previous task in the workflow with notification. |
| 28 |
| The system must provide a process to send ad hoc correspondence with attachments to Entity contacts. |
| 29 |
| The system must provide a process to send correspondence from business workflow with applicable email templates, documents, and attachments. |
| 30 |
| The system must provide the ability to add attachments to Entity, Charter, Charter workflow, Examination, and Investigation. |
| 31 |
| The system must provide the ability for staff members to perform key word and phrase searches of content within specified documents and/or document types across all Cases. (ie, search functionality within documents of a specified type). |
| 32 |
| The system must provide the ability for staff members to perform robust search capabilities within all recorded Auto Insurer data. |
| 33 |
| The system must provide the ability for staff members to perform robust search capabilities within all recorded Arbitrator data, including Comments. |
| 34 |
| The system must provide the ability to search using many search functions at the same time (key word phrases, Booleans and proximity.) |
| 35 |
| The system must provide the ability to search within all Rule Sets and document content associated to other Rule Sets. |
| 36 |
| The system must provide the ability to search by author or Attorney. |
| 37 |
| The system must provide the ability to perform powerful searches for Investigation(s) using previously entered Investigation Data. |
| 38 |
| The system must provide the ability to send bulk e-mails to Licensees in certain programs, Segments of certain Licensees and/or, to all Programs. |
| 39 |
| The system must allow for digression through the wizard when creating a new folder, allowing for editing of previous input. |
| 40 |
| The system, when setting up folders and generating letters, must default to the mailing address on file for the company or individual, removing the need for manual selection by the user. |
| 41 |
| The system must generate letters with accurate formatting as formatted in the Word document template as configured by staff members. |
| 42 |
| The system must contain clear descriptions of the error, free of spelling and grammatical errors when alerts are generated. |
| 43 |
| The system must populate a staff member's task list, when a task is assigned to them. |
| 44 |
| The system must provide staff members clear names and descriptions of Tasks, Checklist items, Reports, Documents and other system functionality. |
| 45 |
| The system must allow for the Addresses to be same anywhere in the system where multiple Addresses are captured and allow staff members to choose when they are the same. The system would then automatically pre-fill the Addresses. (ie. Mailing Address, Physical Address, Complaint Address etc.) |
| 46 |
| The system must allow for staff members to configure, maintain and define e-mail template Subject line format utilizing the Mailing Contact (ie. Prefix of Applicant name or Licensee name, Purpose, etc.) |
| 47 |
| The system must properly display the status of a task and only show Sent when an item has been Sent. |
| 48 |
| The system must allow for staff members to configure, maintain and define the body for e-mail templates. |
| 49 |
| The system must allow for staff members to configure, maintain and define letter templates. |
| 50 |
| The system must automatically generate letters and e-mail the letters for certain actions pre-defined by staff members based on business rules. |
| 51 |
| The system should provide staff members the ability to format and save Comments in the system, and the format of the Comment be retained. |
| 52 |
| The system must default the Status to Active when a new person record is created. |
| 53 |
| The system must automatically send attachments when specifying correspondence, when configured. |
| 54 |
| The system must be able to automatically calculate due dates, taking into account, state holidays, calendar days and business days. |
Referrals: Process of sending task to another business user and/or business office.
| 1 |
| The system must provide the ability to receive and process referral tasks from other offices. |
| 2 |
| The system must be able to refer Entity or Entity contact for fraud investigation. |
| 3 |
| The system must have the ability to refer cases to other areas of DIFS (ex. Compliance, OCS). |
| 4 |
| The system must notify the staff member of a new case assignment by e-mail and entry into a Case Tracker log. |
| 5 |
| The system must automatically notify a staff member of a pending review for the Case assign to them. |
| 6 |
| The system must automatically send notifications to OALRMR of newly established auto insurance companies by non-OALRMR DIFS offices. |
| 7 |
| The system must be able to automatically notify staff members based on configured due dates. |
| 8 |
| The system must be able to specify a cross reference value based on an originating offices' issue (ex. PRIRA Complaint.) |
| 9 |
| The system must be able to automatically notify the Legal Research team of newly created Matters. |
| 10 |
| The system must provide staff members the ability to create Referrals, referring any system created entities (Cases, Matters, Investigations, Rule Set, etc.) to another DIFS office, which automatically notifies that office of the referral and the action to be taken. |
| 11 |
| The system must be able to automatically notify the Legal Research team of newly created Rule Set. |
| 12 |
| The system must have the ability to refer Investigations to other areas of DIFS (ex. OGC, OIRF). |
| 13 |
| The system must provide staff members the ability to create Referrals, referring any system created entities (Cases, Matters, Investigations, Rule Set, Investigations etc.) to another DIFS office, which automatically notifies that office of the referral and the action to be taken. |
| 14 |
| The system must provide staff members the ability to attach documents and add comments and details to Referrals. |
| 15 |
| The system must notify the staff member of a new Investigation assignment by e-mail and entry into an Investigation Tracker log. |
| 16 |
| The system must automatically notify a staff member of a pending review for the Investigation assign to them. |
| 17 |
| The system must allow staff members to initiate a review process by selecting a review status (ex. Peer review, Manager review, Director review, Attorney review.) |
| 18 |
| The system must provide staff members the ability to create Referrals, referring any system created entities (Cases, Matters, Investigations, Rule Set, etc.) to another DIFS office, which automatically notifies that office of the referral and the action to be taken. |
| 19 |
| The system must provide the ability to notify staff members via e-mail when a Task is assigned to them. |
| 20 |
| The system must provide for the ability of OCS staff members to refer a Complaint to OCF staff members, with access to all system stored data relating to the Complaint. |
| 21 |
| The system must provide for the ability for staff members to configure to whom referrals are sent. |
The system must route referrals to the OGC based on referral routing configuration.
| 22 |
| The system must automatically and correctly route tasks to the correct user when a task is marked "deficient" and clearly display the task and the newly assigned user. |
| 23 |
| The system must automatically generate a review task for the Section Director when a proposed Close letter is generated. |
| 24 |
| The system must provide a generic Inquiry tracker, showing Inquiries to be routed from one DIFS office to another. This facilitates the ability for offices to intake paper documentation NOT belonging to them, and route it to the correct DIFS office. |
| 25 |
| The system must alert staff members of any open Enforcement cases, Exam, or Investigation when creating the folder for the Respondent. |
| 26 |
| The system must alert staff members when replacing an incorrect Respondent to change the Type and Product Type. |
| 27 |
| The system must provide a process to send the memorandum to the office that it belongs and get the approval signature via workflow and security roles. |
| 28 |
| The system must provide a process to notify the referring/concerned DIFS office when penalties are applied to the respondent |
| 29 |
| The system must provide a process to send notifications to the referring DIFS office at various stages of the Hearing |
| 30 |
| The system must allow to search for Matters referred by different offices |
| 31 |
| The system must provide a process to create an Advice Matter as a request from another DIFS Office which does not involve an entity (respondent) |
| 32 |
| The system must provide a process to notify other DIFS offices in addition to the referring office on the outcome etc. of an Advice Matter |
| 33 |
| The system must provide a process to create an OGC Matter by request from another DIFS Office and bring over the respondent information from the referring process. |
| 34 |
| The system must allow for creating a contested case that was received as appeals from another DIFS office |
| 35 |
| The system must provide a process to send an email to the DIFS office and allow summary and other files related to the Fraud Report to be attached, when the Fraud Report is being referred to another DIFS office |
| 36 |
| The system must initiate the Receivership process on a company when the referral is made from another DIFS office |
| 37 |
| The system must need to notify relevant DIFS offices with triggering events, using a templated notification |
| 38 |
| The system must allow for a method to refer licensee to OGC |
| 39 |
| The system must have the ability to automatically refer DRLP loss to OGC |
| 40 |
| The system must allow for a list of code violations with referral dates |
| 41 |
| The system must send an alert to affected offices when changes are made creating discrepancy |
| 42 |
| The system must track sign off of any cross office changes and send alerts to offices as needed |
| 43 |
| The system must have the option to refer to other offices |
| 44 |
| The system creates a problem report when referred to other offices |
| 45 |
| The system notifies other offices when cancel for cause is sent from NIPR |
| 46 |
| The system must have a process to assign cases to other office members |
| 47 |
| The system must have a process to refer a compliance review for an audit |
| 48 |
| The system must provide a process for OIRF to receive the complaints/non-compliance/issue research and route the request to OGC/OIE/research attorney |
| 49 |
| The system must add the OIRF process in the respective complaints folder from each office and will have two status for OIRF to respond. The OIRF process status are 1. Review Completed 2. Need more information |
| 50 |
| The system must allow OIRF to request for issue (Matter) brief regarding regulatory change or specific issue. Researched and written by Legal Research attorney. |
| 51 |
| The system must allow OIRF to provide a process to refer enforcement requests (Matter) to OGC and receive the final documentation. |
| 52 |
| The system must provide a process for OIRF to refer 3rd party contracts (Matter) to OGC for review. |
| 53 |
| The system must provide a process to refer complaints to OIRF from OCS. |
| 54 |
| The system must provide a process for OIE to notify OFAS to start the regulatory assessment budget calculations. |
| 55 |
| The system must send a notification to OIE and OILIA users to review the numbers entered in the Assessment Variable screen. |
| 56 |
| The system must notify OIE to review the regulatory assessment fees calculated. |
Document Management: Systematic organization, storage, retrieval, and tracking of electronic or physical documents within DIFS.
| 1 |
| The system must be able to maintain and create documents and document templates. |
| 2 |
| The system must be able to generate documents from business rules, on demand, or defined events such as status changes. |
| 3 |
| The system must be able to pre-fill data on generated documents. |
| 4 |
| The system must provide a method to receive, store, and produce documents electronically. |
| 5 |
| The system must be able to view, print, or retrieve documents from search criteria that has been entered. |
| 6 |
| The system must allow for configurable rules regarding document purging, archiving, and retention. |
| 7 |
| The system must be able to add and remove edits to documents that will not affect the original document. |
| 8 |
| The system must allow users with the appropriate privileges to delete documents. |
| 9 |
| The system must allow users to print any forms, correspondence, or documents to a local print, or send them to the queue for printing services. |
| 10 |
| The system must be able to maintain and create templates for correspondence. |
| 11 |
| The system must be able to generate correspondence from business rules, on demand, or defined events such as status changes. |
| 12 |
| The system must be able to pre-fill data on generated correspondence. |
| 13 |
| The system must be able to send correspondence with a custom format, standard forma, or a template. |
| 14 |
| The system must provide a method to receive, store, and produce correspondence electronically. |
| 15 |
| The system must be able to configure type codes for correspondence and assign them accordingly (for example, complaint, investigations, inquiry of licensee, etc.) |
| 16 |
| The system must be able to view, print, or retrieve correspondence from search criteria that has been entered. |
| 17 |
| The system must allow for configurable rules regarding correspondence purging, archiving, and retention. |
| 18 |
| The system must be able to add and remove edits to correspondence that will not affect the original correspondence. |
| 19 |
| The system must allow users with the appropriate privileges to delete correspondence. |
| 20 |
| The system must be able to re-create correspondence. |
| 21 |
| The system must be able to send a mass correspondence by email. |
| 22 |
| The system must be able to have pre-filled data for mass emails (for example, names of individual/party. |
| 23 |
| The system must provide a process to create and maintain numerous Document templates with optional editable fields. |
| 24 |
| The system shall be able to create documents on-demand and via automation, including but not limited to business rules, events, or status changes. |
| 25 |
| The system must provide a process to create and maintain numerous Email templates, including but not limited to editable fields, document types, attachment types, default sender email address, To, CC flags to indicate if logged users' email address is included as sender, encryption required flags, information security classifications, and FOIA classifications. |
| 26 |
| The system must provide the ability to send email correspondence on-demand and via automation, including but not limited to business rules, events, or status changes with attachments and documents. |
| 27 |
| The system must provide a process to systemically manage and apply the office-specific retention schedule for data and documents. |
| 28 |
| The system must provide the ability to scan, save and label paper documents and associate them to a Case. |
| 29 |
| The system must provide the ability to save and label electronic attachments and associate them to a Case (ex. E-mails and e-mail attachments.) |
| 30 |
| The system must provide the ability for a staff member to search for all documents associated to a Case. |
| 31 |
| The system must provide the ability to easily bundle all documents associated to a Case for the purposes of complying with document requests. |
| 32 |
| The system must provide the ability for staff members to create and maintain letter templates in Microsoft Word. |
| 33 |
| The system must provide the ability for a staff member to modify a MS Word letter on a Case, such as markup a letter with comments. |
| 34 |
| The system must provide the ability for staff members to designate a document type for all documents attached to a Case. |
| 35 |
| The system must provide the ability for staff members to designate a document type for all documents attached to a Case. |
| 36 |
| The system must provide the ability for staff members to perform key word and phrase searches of content within specified documents and/or document types across all Cases or specified Cases. (ie, search functionality within documents of a specified type). |
| 37 |
| The system must provide the ability for staff members to assign a letter via template to a Case. |
| 38 |
| The system must provide the ability to select pre-configured text to add to a letter. |
| 39 |
| The system must provide the ability to open multiple letters for reference when crafting a letter to be sent. |
| 40 |
| The system must provide a function to generate and e-mail documents (ex. Proof of Service, IRO report and Order.) |
| 41 |
| The system must auto-populate letters based on letter templates with appropriately tagged data. |
| 42 |
| The system must provide the ability to convert the MS word document to a PDF document. |
| 43 |
| The system must provide the ability to staff members to delete documents. |
| 44 |
| The system must have the ability for staff to download documents. |
| 45 |
| The system must allow for the storage and organization of received attachments. |
| 46 |
| The system must provide the ability to receive, save and view attachments (ex. PDF, Outlook e-mails, etc.) |
| 47 |
| The system must provide the ability for staff members to create and maintain letter templates in Microsoft Word. |
| 48 |
| The system must provide the ability to send e-mail communication utilizing letter templates. |
| 49 |
| The system must provide the ability to create, store and access documents (ex. Word, Outlook, PDF, etc.) and associate them to a Matter. |
| 50 |
| The system must provide the ability for staff members to e-mail documents associated to a Matter. |
| 51 |
| The system must automatically store e-mails associated to a Matter when initiated from within a Matter. |
| 52 |
| The system must provide the ability to search within all Matters and document content associated to other Matters. |
| 53 |
| The system, when performing a document search, must provide the ability for staff members to search using key word phrases (ex. PIP, MCL 500.31.57). |
| 54 |
| The system, when performing a document search, must provide the ability for staff members to specify Boolean searches (ex, AND, OR etc.) |
| 55 |
| The system, when performing a document search, must provide the ability for staff members to search using Proximity Search functionality by Number of Words (ex. Automobile /3 insurance), by Sentence, by Paragraph. |
| 56 |
| The system must provide the ability for staff members to configure document retention policies based on document categories. |
| 57 |
| The system must provide the ability for staff members to assign a document category to a document. |
| 58 |
| The system must provide staff members the ability to attach documents and add comments and details to Referrals. |
| 59 |
| The system must provide the ability to create, store and access documents (ex. Word, Outlook, PDF, etc.) and associate them to a Rule Set. |
| 60 |
| The system must provide the ability for staff members to e-mail documents associated to a Rule Set. |
| 61 |
| The system must automatically store e-mails associated to a Rule Set when initiated from within a Rule Set. |
| 62 |
| The system must provide the ability to scan, save and label paper documents and associate them to an Investigation. |
| 63 |
| The system must provide the ability to save and label electronic attachments and associate them to an Investigation (ex. E-mails and e-mail attachments.) |
| 64 |
| The system must provide the ability for a staff member to search for all documents associated to an Investigation. |
| 65 |
| The system must provide the ability to easily bundle all documents associated to an Investigation for the purposes of complying with document requests. |
| 66 |
| The system must provide the ability for staff members to designate a document type for all documents attached to an Investigation. |
| 67 |
| The system must provide the ability for staff members to perform key word and phrase searches of content within specified documents and/or document types across all Investigations or specified Investigations. (ie, search functionality within documents of a specified type). |
| 68 |
| The system must provide the ability for staff members to assign a letter via template to an Investigation. |
| 69 |
| The system must provide the ability to select pre-configured text to add to a letter. |
| 70 |
| The system must provide the ability to open multiple letters for reference when crafting a letter to be sent. |
| 71 |
| The system must provide a function to generate and e-mail documents (ex. letters and supporting documents to companies.) |
| 72 |
| The system must auto-populate letters based on letter templates with appropriately tagged data. |
| 73 |
| The system must provide the ability for authorized staff members to delete documents. |
| 74 |
| The system must have the ability for staff to download documents. |
| 75 |
| The system must provide the ability for a staff member to modify a MS Word letter on an Investigation, such as markup a letter with comments. |
| 76 |
| The system must provide staff members the ability to attach documents and add comments and details to Referrals. |
| 77 |
| The system must automatically associate documents to a work step (Work List, Task List) when that work step requires document specific tasks. |
| 78 |
| The system must allow for the attachment of documents to Tasks. |
| 79 |
| The system must allow for the attachment of e-mails and zip files as documents. |
| 80 |
| The system must provide for the ability to scan paper documents and create an Inquiry file, with the ability to assign this Inquiry file to another DIFS office and automatically notify the assigned to DIFS office of the assignment. |
| 81 |
| The system must for staff members to configure what attachments related to specific correspondence. |
| 82 |
| The system must provide the functionality to attach documentation (all file types) to all pages/screens. |
| 83 |
| The system must provide a process to generate cover letters |
| 84 |
| The system must provide a process to generate captions for use in Memos, NOSCs etc. |
| 85 |
| The system must provide a process to generate Certificate of Service |
| 86 |
| The system must store a maintainable Michigan Statutes list and allow to insert Statutes into any documents that are generated |
| 87 |
| The system must attach a copy of letter to the application |
| 88 |
| The system must add a comment for sent letters |
| 89 |
| The system must auto-generate emails to applicants with those who have taken the exam that does not match qualifications (line of authority) |
| 90 |
| The system must allow upload of organization documents received with application |
| 91 |
| The system must allow for storage of organization documents received with application |
| 92 |
| The system must require documents to be submitted for the application |
| 93 |
| The system must allow for upload of organizational documents with the renewal via an online portal |
| 94 |
| The system must allow for upload of organizational documents with the renewal |
| 95 |
| The system must allow for storage of organization documents received with renewal |
| 96 |
| The system must store the warning letter as an attachment |
| 97 |
| The system must allow for reprinting of agency DRLP letter |
| 98 |
| The system must allow for attachments to be added and/or downloaded |
| 99 |
| The system must allow users to create output documents |
| 100 |
| The system must allow for storage of documentation provided from agency |
| 101 |
| The system must have an email process to agencies for any follow-up correspondence |
| 102 |
| The system must have an email process to agencies that the review is closed, using a templated email |
| 103 |
| The system must have a process to print all letters to a local printer or print center (some must be mailed) |
| 104 |
| The system must be able to save warning letters |
| 105 |
| The system must allow for upload of organizational documents with the renewal via an online portal |
| 106 |
| The system must allow for upload of organizational documents with the renewal |
| 107 |
| The system must allow for storage of organization documents received with renewal |
| 108 |
| The system must have dynamic templated letters and templated emails based on license type |
| 109 |
| The system must allow users to save attachments (pdf, excel, word) |
| 110 |
| The system must provide a process to specify document attributes, including but not limited to type, Information security classification, and FOIA classification. |
| 111 |
| The system shall provide the ability to store, view, and retrieve the Documents with audit information. |
| 112 |
| The system must provide a process to specify Document types and assign them to the appropriate Entity, Entity License, or Business process. |
| 113 |
| The system shall be able to add, remove, and edit Documents based on user privileges. |
| 114 |
| The system must provide the ability to maintain an audit of data and document archiving and purging rules. |
| 115 |
| The system must provide the ability to DIFS Admin to approve the Office data and document archiving and purging rules. |
| 116 |
| The system must provide the ability to create data and document hold reports for DIFS and Offices. |
| 117 |
| The system shall archive all data and documents in compliance with the applicable DIFS Overall and Office data and document archiving rules. |
| 118 |
| The system shall maintain the integrity of data and documents when archiving information. |
| 119 |
| The system shall provide the ability to notify Offices prior (configuration in months) to archiving the Office data and documents. |
| 120 |
| The system shall monitor the archiving process and report the success and failure of the archive process. |
| 121 |
| The system shall provide the ability to create archive reports for DIFS and Offices. |
| 122 |
| The system shall provide the ability to view archived data and documents. |
| 123 |
| The system shall provide the ability to restore archived data and documents. |
| 124 |
| The system must not allow the archived data to be updated. |
| 125 |
| The system shall purge all data and documents in compliance with the applicable DIFS Overall and Office data and document purging rules. |
| 126 |
| The system shall maintain the integrity of data and documents when purging information. |
| 127 |
| The system shall provide the ability to notify Offices prior (configuration in months) to purging the Office data and documents. |
| 128 |
| The system shall provide the ability to create reports of the archived data and documents from the archive repository. |
| 129 |
| The system shall monitor the purge process and report the success and failure of the purge process. |
| 130 |
| The system shall provide the ability to create purge reports for DIFS and Offices. |
Entity Management: Process involving oversight and administration of all changes made to an entity regulated by DIFS, such as demographic changes, branch changes, affiliations, etc.
| 1 |
| The system must provide a process to change the Entity's name on the effective date identified in the approved certificate of organization amendment application. |
| 2 |
| The system must provide a process to reconcile NCUA Entity information with the Entity information in the system and the process to resolve data issues. |
| 3 |
| The system must provide the ability to request background Checks for Individuals associated with Entities within the office. |
| 4 |
| The system must provide a process to receive and view background check outcomes. |
| 5 |
| The system must provide a process to view business processes and outcomes for Entities within the office, including but not limited to Enforcements, Complaints, and Advice Matters. |
| 6 |
| The system must optionally auto populate Entity names, or partially entered names, that can be cross referenced with their national Entity number, such as NAIC #, NPN #, EIN etc. This will ensure consistency in data entry. |
| 7 |
| The systems must allow for agencies to be marked as inactive |
| 8 |
| The system must provide a process to save in the Company details with OIRF's status on annual 2129 exemption process and financial status/growth/change of companies. |
| 9 |
| The system must allow management of address and contact information for insurance companies (Data Call and Rates and Forms) |
| 10 |
| The system must provide the ability to specify numerous external identifiers for an Entity. |
| 11 |
| The system must provide the ability to specify external identifiers for an Entity specific to an Office . |
| 12 |
| The system must check for duplicate Entities and notify the user if the Entity identifier(s) or name already exists within an office. |
| 13 |
| The system must provide for generating a unique Michigan charter number or License number for an Entity License. |
| 14 |
| The system must provide the ability to search Entity and Entity licenses using external identifiers, Entity names, and MI License/Charter numbers. |
| 15 |
| The system must provide the ability to specify numerous addresses for an Entity or an Entity License across all business offices. |
| 16 |
| The system must provide the ability to include multiple addresses for an Entity or an Entity License within a single business office. |
| 17 |
| The system must be able to create emails/letters for all addresses listed within a single business office. |
| 18 |
| The system must provide the ability to search Entity and Entity Licenses using the Address. |
| 19 |
| The system must maintain an audit (history) of all address changes. |
| 20 |
| The system must provide a process to maintain a configuration for valid zip codes for State/City and country codes. |
| 21 |
| The system must provide a process to validate the zip code, city name, and country code using configuration. |
| 22 |
| The system must provide the ability to manage specific addresses for an Entity and Entity License across offices based on the user privilege. |
| 23 |
| The system must provide the ability to specify numerous Contacts for an Entity or an Entity License. |
| 24 |
| The system must provide the ability to specify Contact information without an address. |
| 25 |
| The system must provide the ability to search Entity and Entity Licenses using the Contact information. |
| 26 |
| The system must maintain an audit (history) of all Contact changes. |
| 27 |
| The System must provide the ability to specify numerous Aliases for an Entity or an Entity License with an effective date. |
| 28 |
| The system must provide the ability to search Entity and Entity Licenses using the Alias. |
| 29 |
| The system must maintain an audit (history) of all Alias changes. |
| 30 |
| The system must provide the ability to search regulated Entity and Entity Licenses for an office or all offices. |
| 31 |
| The system must provide the ability to search Entity Licenses using the License statutes. |
| 32 |
| The system must provide the ability to search any and all Entity and Entity License Information, including but not limited to the Entity name, MI License/Charter type, MI License/Charter number, external identifier, Address, Contact, Alias, license type, and location type. |
| 33 |
| The system must provide the ability to search Entity and Entity Licenses using the invoice information including open invoices, invoice numbers, and invoice/check amounts. |
| 34 |
| The system must provide the ability to search Entity and Entity Licenses based on the user access privilege. |
| 35 |
| The system must provide the ability to search Entity and Entity Licenses information using the Boolean operators - AND / OR / NOT. |
| 36 |
| The system must provide the ability to search Entity and Entity License transactions, including Applications, Renewals, Exams, Financial Analyses, Investigations, Complaints, Enforcements, and Fraud. |
| 37 |
| The system must provide the ability to search entities and entity licenses using the cross-office link. |
| 38 |
| The system must provide the ability to specify optional external identifiers for an Entity. |
| 39 |
| The system must provide the ability to create office and cross-office level non-regulated Entities. |
| 40 |
| The system must provide the ability to check for duplicate Entities and notify the user if the Entity identifier(s) or name already exists within an office for an office-specific non-regulated Entity. |
| 41 |
| The system must provide the ability to check for duplicate Entities and notify the user if the Entity identifier(s) or name already exists across offices for a cross-office non-regulated Entity. |
| 42 |
| The system must provide the ability to search Entities using external identifiers and Entity names. |
| 43 |
| The system must provide the ability to specify numerous addresses for an Entity across all business offices. |
| 44 |
| The system must provide the ability to include multiple addresses for an Entity within a single business office. |
| 45 |
| The system must be able to create emails/letters for all addresses listed within a single business office. |
| 46 |
| The system must provide the ability to search Entities using the Address. |
| 47 |
| The system must provide the ability to specify numerous Contacts for an Entity. |
| 48 |
| The system must provide the ability to link Contacts to an Entity address. |
| 49 |
| The system must provide the ability to specify Contact information without an address. |
| 50 |
| The system must provide the ability to search Entities using the Contact information. |
| 51 |
| The System must provide the ability to specify numerous Aliases for an Entity with an effective date. |
| 52 |
| The system must provide the ability to search Entity using the Alias. |
| 53 |
| The system must provide the ability to search non-regulated Entities for an office or all offices. |
The system must provide the ability to search any and all Entity and Entity License Information, including but not limited to the Entity name, external identifier, Address, Contact, and Alias.
| 55 |
| The system must provide the ability to search Entity and Entity Licenses using the invoice information including open invoices, invoice numbers, and invoice/check amounts. |
| 56 |
| The system must provide the ability to search any and all Entity and Entity License transactions, including but not limited to Investigations, Complaints, Enforcements, and Fraud. |
| 57 |
| The system must provide the ability to manage office-level and cross-office level non-regulated entities. |
| 58 |
| The system must provide the ability to convert a Non-Regulated Entity to an Office-Level Regulated Entity. |
| 59 |
| The system must provide the ability to specify numerous external identifiers for an Entity. |
| 60 |
| The system must provide the ability to specify external identifiers for an Entity specific to an Office. |
| 61 |
| The system must check for duplicate Entities and notify the user if the Entity identifier(s) or name already exists within an office. |
| 62 |
| The system must provide the ability to specify numerous addresses for an Entity or an Entity License across all business offices. |
| 63 |
| The system must provide the ability to include multiple addresses for an Entity or an Entity License within a single business office. |
| 64 |
| The system must provide a process to maintain a configuration for valid zip codes for State/City and country codes. |
| 65 |
| The system must provide a process to validate the zip code, city name, and country code using configuration. |
| 66 |
| The system must provide the ability to manage specific addresses for an Entity and Entity License across offices based on the user privilege. |
| 67 |
| The System must provide the ability to specify numerous Aliases for an Entity or an Entity License with an effective date. |
| 68 |
| The system must provide the ability to search entities and entity licenses using the cross-office link. |
| 69 |
| The system must provide the ability to specify optional external identifiers for an Entity. |
| 70 |
| The system must provide the ability to create office and cross-office level non-regulated Entities. |
| 71 |
| The system must provide the ability to check for duplicate Entities and notify the user if the Entity identifier(s), and name already exists within an office for an office-specific non-regulated Entity. |
| 72 |
| The system must provide the ability to check for duplicate Entities and notify the user if the Entity identifier(s) or name already exists across offices for a cross-office non-regulated Entity. |
| 73 |
| The system must provide the ability to search Entities using external identifiers and Entity names. |
| 74 |
| The system must provide the ability to specify numerous addresses for an Entity across all folders/business offices. |
| 75 |
| The system must provide the ability to include multiple addresses for an Entity within a single folder/business office. |
| 76 |
| The system must be able to create emails/letters for all addresses listed within a single folder/business office. |
| 77 |
| The system must provide the ability to search Entities using the Address. |
| 78 |
| The system must maintain an audit (history) of all address changes. |
| 79 |
| The system must provide a process to maintain a configuration for valid zip codes for State/City and country codes. |
| 80 |
| The system must provide a process to validate the zip code, city name, and country code using configuration. |
| 81 |
| The System must provide the ability to specify numerous Aliases for an Entity with an effective date. |
| 82 |
| The system must provide the ability to search Entities using the Alias. |
| 83 |
| The system must maintain an audit (history) of all Alias changes. |
| 84 |
| The system must provide the ability to search Entity information, including the using Entity name, external identifier, Address, and Alias. |
| 85 |
| The system must provide the ability to search any and all Entity Information, including but not limited to the Entity name, external identifier, Address, and Alias. |
| 86 |
| The system must provide the ability to search Entities using the invoice information including open invoices, invoice numbers, and invoice/check amounts. |
| 87 |
| The system must provide the ability to search Entity based on the user access privilege. |
| 88 |
| The system must provide the ability to search Entity information using the Boolean operators - AND / OR / NOT. |
| 89 |
| The system must provide the ability to search Entity transactions, including Investigations, Complaints, Enforcements, and Fraud. |
| 90 |
| The system must provide the ability to manage office-level and cross-office level non-regulated entities. |
| 91 |
| The system must provide the ability to convert a Non-Regulated Entity to an Office-Level Regulated Entity. |
Manage Business Rules: Maintaining the guidelines for DIFS users, processes, and systematic behavior.
| 1 |
| The system must have a configurable rule allowing for a time period of when comments can be changed. |
| 2 |
| The system must allow DIFS a way to maintain and create error messages. |
| 3 |
| The system must allow for a configurable method for field formatting, including identifying required fields. |
| 4 |
| The system must maintain a configurable list of staff members for the purpose of case assignment. |
| 5 |
| The system must be able to capture configurable statistics business rules. |
| 6 |
| The system must be able to calculate and record various statistics based on configurable statistics business rules. |
| 7 |
| The system must allow staff members to maintain a configurable list of staff members for the purpose of a Peer review process. |
| 8 |
| The system must provide a configurable retention schedule for all Cases and documents associated to a Case. |
| 9 |
| The system must provide the ability to configure a Plan / Plan Type cross reference. |
| 10 |
| The system must visually provide a Plan / Plan Type cross reference for staff members. |
| 11 |
| The system must provide a configurable retention schedule for all Cases and documents associated to a Case. |
| 12 |
| The system must provide the ability for authorized staff members to configure selection values, with active and inactive statuses based on date values, used in Case creation. |
| 13 |
| The system must maintain a configurable list of staff members for the purpose of case assignment. |
| 14 |
| The system must for provide for access management at various levels. |
| 15 |
| The system must provide the ability to configure due dates based on business rules for steps in the appeals process. Due dates are based on business rules. |
| 16 |
| The system must be able to capture configurable statistics business rules. |
| 17 |
| The system must be able to calculate and record various statistics based on configurable statistics business rules for staff reports and management/performance reports. |
| 18 |
| The system must allow staff members to maintain a configurable list of staff members for the purpose of a Peer review process. |
| 19 |
| The system must allow staff members to maintain a configurable list of Independent Review Organizations (IROs) for the purpose of selecting an IRO for independent reviews. |
| 20 |
| The system must provide for the ability for staff members to define and configure due dates. The due dates are based on business rules and statues. |
| 21 |
| The system must provide the ability for staff members to configure a Review Checklist. |
| 22 |
| The system must provide the ability to configure Due Dates based on business rules. |
| 23 |
| The system must provide the ability for staff members to create a Rule Set, with varying levels of Rule Set data fields. |
| 24 |
| The system must be able to autogenerate Rule Set numbers sequentially. |
| 25 |
| The system must provide a Rule Set Tracker with varying levels of detail showing Rule Sets in various statuses. |
| 26 |
| The system must automatically calculate Due Dates based on configured Due Date rules. |
| 27 |
| The system must provide the ability to manually specify a Due Date, overriding any automatically calculated Due Date. |
| 28 |
| The system must be able to trigger automatic functions, such as e-mail notification, based on Rule Status change. |
| 29 |
| The system must be able to trigger automatic functions, such as e-mail notification, based on the completion of a Task. |
| 30 |
| The system must, when configuring and calculating Due Dates, take into consideration State Holidays, and Business Days vs Calendar Days. |
| 31 |
| The system must provide a configurable retention schedule for all Investigations and documents associated to an Investigation. |
| 32 |
| The system must provide the ability for authorized staff members to configure selection values, with active and inactive statuses based on date values, used in Investigation creation. |
| 33 |
| The system must store a maintainable State of Michigan Statute list and make it available for selection from within the application. |
| 34 |
| The system must provide the ability to configure due dates based on business rules for steps in the Investigations process. Due dates are based on business rules. |
| 35 |
| The system must be able to capture configurable statistics business rules. |
| 36 |
| The system must be able to calculate and record various statistics based on configurable statistics business rules for staff reports and management/performance reports. |
| 37 |
| The system must provide the ability to configure due dates based on business rules for steps in the Investigations/Examinations/Visitations process. Due dates are based on business rules. |
| 38 |
| The system must automatically Close Investigations/Examinations/Visitations based on business rules. |
| 39 |
| The system must automatically calculate due dates for Visitations and display the due date to staff members, per business rules. |
| 40 |
| The system must be able to display Fee Descriptions in accordance with business rules and requirements. |
| 41 |
| The system must route the supervisory activity to the correct individual based on business rules. (ie. Supervisor creates an investigation which is at the intake phase. |
| 42 |
| The system must provide the ability for staff members to define and configure staff members due dates for all work items. |
| 43 |
| The system must provide the ability for staff members to define and configure Applicant/Licensee due dates for all work items. |
| 44 |
| The system must provide the ability for staff members to configure checklist templates. |
| 45 |
| The system must provide the ability to manually add line items to checklists on the fly. |
| 46 |
| The system must provide the ability for staff members to configure due dates to checklist items in checklist templates. |
| 47 |
| The system must provide the ability for staff members to add due dates for manually added checklist items. |
| 48 |
| The system must automatically notify Licensees by e-mail when certain pre-defined system actions are taken as defined by staff members via business rules. |
| 49 |
| The system must automatically assign staff members for certain actions pre-defined by staff members based on business rules. |
| 50 |
| The system must allow for staff members to configure where a Complaint is routed based on Complaint Type. |
| 51 |
| The system must provide the ability for staff members to trigger mass Company e-mails based on various business rules. |
| 52 |
| The system must provide for the ability for Licensees to search for and select and view a Complaint Reconciliation report, based on business rules. |
| 53 |
| The system must provide a process to calculate due dates for legal actions based on business rules |
| 54 |
| The system must allow for maintaining choices across all OGC processes - statuses, action types, outcomes, party types etc. |
| 55 |
| The system must allow to store business rules for calculating the cost (First 3 hours are not charged etc.) |
| 56 |
| The system must provide a business rule to maintain the staff Name that will be used as the "Prepared By" staff member for the FOIA Invoice |
| 57 |
| The system must provide a process to maintain business rules for allowing the Receivership status changes |
| 58 |
| The system must display error using non-configurable business rules |
| 59 |
| The system must allow for the background questions that are asked to be changed with a business rule |
| 60 |
| The system must allow for background questions that are asked to be added with a business rule |
| 61 |
| The system must require a configurable business rule for renewal deadline date |
| 62 |
| The system must require a way to configure business rules for renewal approvals |
| 63 |
| The system must have a configurable set of business rules for license renewal |
| 64 |
| The system must allow for configurable rules for association modifications |
| 65 |
| The system must have configurable business rules for changes to data points |
| 66 |
| The system must have configurable business rules to allow certain users to make changes |
| 67 |
| The system must have different configurable business rules per area (i.e. Ind, Agency, TPA) |
| 68 |
| The system must allow for BRs to control the back dating and forward dating |
| 69 |
| The system must allow for rules to control use of actions within a process |
| 70 |
| The system must have a configurable rule for review dates, with systematic notification |
| 71 |
| The system must have a configurable business rule to change the timing of reminder notices |
| 72 |
| The system must have rules for the business to control the renewal timing period |
| 73 |
| The system must have a configurable business rule to change the timing of reminder notices |
| 74 |
| The system must have rules for the business to control the renewal timing period |
| 75 |
| The system must allow for configurable alert types with templated letters |
| 76 |
| The system must set defaults on some detailed fields, based on business rules |
| 77 |
| The system must allow for configurable list of no action reasons when status is changed to finished |
| 78 |
| The system must have business rules on who received inactivation notices |
| 79 |
| The system must require a way to configure business rules for renewal approvals |
| 80 |
| The system must require a configurable way to control what changes can be made and to what type |
| 81 |
| The system must require business rules regarding the impact to licenses, appointments, sponsorships, or affiliations based on changes made to a record |
| 82 |
| The system must have configurable business rules used to check applications and create appropriate issues, and to run automated processes |
| 83 |
| The system must allow for separate configurable business rules depending on license types |
| 84 |
| The system must have business rules regarding eligible qualifications and appointments based on license type |
| 85 |
| The system must provide the ability for Offices to specify data and document archiving and purging rules according to the Office Retention Policy and DIFS Overall Retention Policy. |
| 86 |
| The system must have configurable rules for timing of reminders |
Merging/Linking Records: Management of duplicate records within DIFS databases.
| 1 |
| The system must have a process to identify duplicate records. |
| 2 |
| The system must have a process to merge duplicated records. |
This is the start of the file's text. The full file is on GovTribe.