Instructions Complete this business and technical requirements matrix by addressing how the bidder proposes to meet each requirement. ID RFP Appendix A - Statement of Work Section Requirement Response I.D General – Project Governance Must participate in the MMIS Replacement Project governance as required by the State. II.A Design, Development, and Implementation (DDI) – Phase Overview Must develop a realistic and achievable implementation plan with contingencies throughout rather than assuming the best possible outcome will always occur. II.A Design, Development, and Implementation (DDI) – Phase Overview Must provide organizational change management support to the State throughout the DDI phase to prepare the State staff for major operational changes. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must manage all aspects of the project that affect cost, schedule, performance (scope and quality), risk/issues/opportunities, and resources that are under its control. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must develop and put into practice a holistic project management plan or series of plans and associated integration(s), based on its proposed project management and SDLC methodologies. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must seek, and obtain approval from the State, for a project schedule baseline for each plan or series of plans it develops based on its proposed project management and SDLC methodologies. and - – Business
II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide updated and compatible weekly extracts (or any other interval requested by the State) of its plan(s) to the State for import into Microsoft Project or CA Clarity. Extracts must include, at a minimum, tasks, start dates, completion dates, resource assignments, levels of effort, durations, dependencies, constraints, percent completion, milestones, variances from baselines, predecessors, and successors. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must employ a proven project management approach promoting the development of a strong working relationship and facilitating open and timely collaboration between the State, the Contractor, other Contractors, and project stakeholders. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must employ a proven project management approach ensuring the transparency of management actions and project results so that all parties remain properly informed. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must lead coordination with all other organizations whose participation is necessary for project success. The State will reasonably support the Contractor’s coordination efforts.
II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must prepare and submit the integrated master schedule (IMS) that addresses each phase of the PMLC and SDLC and must identify all integration points between all Contractors and the State including interfaces, inputs, and outputs that the Contractor requires from other Contractors, the State, or other entities. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Within the IMS, must at a minimum decompose all tasks starting within a 120-day window into the future. This 120-day view should be maintained from month-to-month to provide an appropriate level of visibility for 120 days forward. Any task exceeding ten days in duration must be broken down to include subtasks detailing an appropriate level of work effort. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must submit for review and approval by the State all changes to the approved project management plans and IMS. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must use a commercial, project planning software for building and maintaining the IMS. However, if it uses software other than Microsoft Project, Project Server, or Clarity, it must provide training for State project staff, provide a reasonable number of licenses for the State’s designated use, and ensure compatibility with the State’s computers.
II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide a State approved Master Data Management Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. The plan must address integration with other State toolsets and support the State’s standardization and processes. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide a State approved Data Modeling Plan that includes strategy, methodology, process, tools, resourcing, quality and contingency aspects. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide, implement, and maintain a State approved Data Integration Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide a State approved Data Sharing Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide, implement, and maintain a State approved Data Transformation Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects.
II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide, implement, and maintain a State approved DMA Audit and Control Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. II.C.1 Design, Development, and Implementation (DDI) – Performance and Status Reporting Must prepare and submit a weekly status report. II.C.1 Design, Development, and Implementation (DDI) – Performance and Status Reporting Must prepare and submit a monthly status report. II.C.1 Design, Development, and Implementation (DDI) – Performance and Status Reporting Must prepare and submit a quarterly status report.
II.D Design, Development, and Implementation (DDI) – Deliverables Must submit any changes to previously approved deliverables for approval through the review process. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must develop and put into practice a comprehensive quality assurance plan or series of plans to infuse quality throughout the project lifecycle and monitor, test, and audit the projects products prior to delivery. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must manage and perform all aspects of quality assurance and monitoring necessary to meet the requirements of this contract. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must develop documented quality assurance procedures. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must report within the weekly status report identified deficiencies with weekly updates until deficiencies are corrected. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must develop, submit, and put into practice a comprehensive test plan to ensure that the provided solution effectively meets the requirements. II.E Design, Development, and Implementation (DDI) – Quality Assurance and Monitoring Must provide and follow a rating system for defects. II.F Design, Development, and Implementation (DDI) – Change Management Must establish a process to track and manage change requests within the performance of the contract. The process must accommodate escalation and disposition of change requests escalated to the project or organizational change control approval levels.
II.F Design, Development, and Implementation (DDI) – Change Management Must implement change requests in a manner with the least possible impact to the project timeframes and budget while maintaining a high quality delivery. II.F Design, Development, and Implementation (DDI) – Change Management Must document change requests utilizing a format and process approved by the State. II.F Design, Development, and Implementation (DDI) – Change Management At the request of the State, the Contractor must analyze change requests and submit the results of analysis to the State. At a minimum, the estimate and results must include estimates for effort by resource category by work package, cost, schedule impact, impacts to the system, impacted external entities and interface partners, and impacted business operations. II.F Design, Development, and Implementation (DDI) – Change Management Must monitor changes in Federal and State laws and rules for impacts to the project. II.F Design, Development, and Implementation (DDI) – Change Management Must support discussions and meetings on the disposition of change requests with the necessary team members to enable decision making. II.F Design, Development, and Implementation (DDI) – Change Management Must submit monthly detailed accounting for change requests to the State’s satisfaction of the work performed by each individual billing time to the change request. II.F Design, Development, and Implementation (DDI) – Change Management Must submit a Change Management Plan detailing the change management process and approach along with a visual aid of the overall process and approach.
II.H Design, Development, and Implementation (DDI) – Environments Must submit an infrastructure and architecture plan describing the DDI environments and network connectivity. II.I Design, Development, and Implementation (DDI) – Disaster Recovery Must submit a Disaster Recovery Plan for DDI that includes strategy, methodology, process, tools, quality and contingency aspects. II.I Design, Development, and Implementation (DDI) – Disaster Recovery Must perform testing to demonstrate that the Disaster Recovery Plan has been correctly implemented, is operational and complies with prescribed recovery timelines in the Disaster Recovery Plan. II.I Design, Development, and Implementation (DDI) – Disaster Recovery Must maintain system redundancy as identified in the Disaster Recovery Plan and approved by the State. II.J Design, Development, and Implementation (DDI) – Facility Must provide secure facilities for hosting of all environments within the continental United States. II.J Design, Development, and Implementation (DDI) – Facility Must have plans in place at Contractor provided facilities to minimize project work impact due to outages. II.J Design, Development, and Implementation (DDI) – Facility Must have controlled access to all Contractor facilities in compliance with privacy and security requirements. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must provide criminal background initial investigations on all personnel prior to project assignment and follow-up investigations every five years.
II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must provide and retain a team and sufficient staff in the right mix, inclusive of technical (e.g. systems analysts, technicians) and (e.g. clerical, business analysts) resources to complete the services and meet the requirements specified in this contract. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must not reassign or replace key personnel without prior approval from the State. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must provide an interim resource within a maximum of five (5) business days for any key personnel vacancies regardless of the reason for the vacancy. II.L Design, Development, and Implementation (DDI) – Documentation Must provide and maintain an online repository accessible by State staff and designees for all project documentation. II.L Design, Development, and Implementation (DDI) – Documentation Must ensure that documentation is developed in a consistent style using consistent formats and defined terminology and acronyms (i.e. standard template, style guide, definitions, and acronyms). II.L Design, Development, and Implementation (DDI) – Documentation Must provide user and system documentation that is effective for both new and experienced users. II.L Design, Development, and Implementation (DDI) – Documentation Must develop and provide project notes and artifacts. II.L Design, Development, and Implementation (DDI) – Documentation Must provide Companion Guides, tutorials, help files, FAQ’s and tool tips. II.L Design, Development, and Implementation (DDI) – Documentation Must develop a meaningful classification system to organize the documentation by type, subject, phase, and audience.
II.N Design, Development, and Implementation (DDI) – System Readiness Must conduct end-to-end testing with interface partners both external and internal II.N Design, Development, and Implementation (DDI) – System Readiness Must include defect status information in the weekly status report. II.N Design, Development, and Implementation (DDI) – System Readiness Must provide documented results and conduct walkthroughs of test results. II.N Design, Development, and Implementation (DDI) – System Readiness Must receive State approval to entering and exiting system readiness. II.N Design, Development, and Implementation (DDI) – System Readiness Must perform all set-up, preparation, and result documentation activities for testing regardless of whether the Contractor or State designee is performing the test case. II.O Design, Development, and Implementation (DDI) – Operational Readiness Must develop and provide an Operational Readiness Plan to the State for approval that is effective for both new and experienced end users of the system. II.O Design, Development, and Implementation (DDI) – Operational Readiness Must develop and provide Business and Technical Operating Procedures to the State for approval. II.O Design, Development, and Implementation (DDI) – Operational Readiness Must submit a signed certification to the State of operational readiness including results of operational readiness checklists and testing. II.O Design, Development, and Implementation (DDI) – Operational Readiness Must provide training and training materials for all operational aspects of the solution to all end users, internal and external. II.O Design, Development, and Implementation (DDI) – Operational Readiness Must test and certify that all components are ready for operations.
II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must validate all production data (e.g. reference, history) and source code is loaded to the appropriate environments. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must validate that interfaces to exchange data are production ready. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must validate that appropriate network connectivity is in place and production ready. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must validate all necessary system and ancillary access is in place, including passwords and security permissions, for all resources per the approved security matrix. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must provide the State with all reasonably requested information to support a go / no-go decision prior to go-live. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must receive State approval prior to beginning the implementation and prior to go-live. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must coordinate and communicate with all actors to ensure each understands the tasks and sequence of actions each must take and that an integrated ‘practice’ of go-live actions takes place prior to the actual cut over. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must provide event driven communications updates to designated State staff and leadership during cut over.
III.D Initial Operations and CMS Certification – Organizational Staffing Must relieve any of the Contractor’s personnel from any further work under the Contract if in the State’s sole discretion (i) the individual does not perform at the applicable skill level specified in the Contractor’s Technical Proposal or elsewhere in the Contract, (ii) the individual does not deliver work that conforms to the performance standards Stated in the RFP, the Contractor’s Technical Proposal, and elsewhere in the Contract, or (iii) the person exhibits personal or professional conflicts with State personnel that hinder effective progress on the project. Upon being notified in writing by the State Contract Administrator that a member of the Contractor’s personnel is unacceptable, the Contractor must immediately remove that individual from any assignments on the Contract. In the event that a member of the Contractor’s personnel is removed pursuant to this paragraph, the process set out for submission of resumes, interviews, and approval must apply as if the person removed were among the Key Personnel.
IV.A Operations Phase - Phase Overview Must provide recommendations to the State for process and system improvements. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must manage all aspects of the contract that affect operations, cost, schedule, and performance (scope and quality); including any risks, issues, opportunities, and resources that are under its control. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must develop and submit for approval an Operational Project Management Plan describing the strategies, tactics, and procedures by which daily operations will be managed while maintaining the production system and implementing changes to the production system. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must put into practice and follow the approved Operational SDLC Plan and submit for re-approval any changes to the approved plan. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must employ a proven project management approach promoting the development of a strong working relationship and facilitating open and timely collaboration between the State, the Contractor, other contractors, and project stakeholders. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must employ a proven project management approach ensuring the transparency of management actions and project results so that all parties remain properly informed. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must lead coordination with all other organizations whose participation is necessary for project success. The State must
than Microsoft Project, Project Server, or CA Clarity PPM, it must provide training for State project staff, provide a reasonable number of licenses for State designated use, and ensure compatibility with the State’s computers. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must provide all PMLC and SDLC deliverables included in the Contractor’s proposed deliverable catalog in conformance with the provided templates, instructions, and procedures and of the quality of the provided examples used on previous projects. Any templates or forms developed during the course of the project must be submitted for review and approval by the State prior to their use. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must perform work in accordance with the approved IMS timeframes. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must perform cohesive project management in all aspects of operational planning, organizing, staffing, scheduling, and monitoring. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must ensure the transparency of operational management plans, actions and outcomes so that all stakeholders remain properly informed. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must implement and monitor an internal quality control process to ensure that all deliverables, documents, and reports are complete, accurate, easy to understand, and of high quality. Include a process to record and
IV.F Operations Phase - Change Management Must provide the ability to rapidly revert to the previous system configuration when a newly implemented change causes an undesirable impact. IV.F Operations Phase - Change Management Must develop and submit for approval a remediation plan for reconfiguration and redeployment when a newly implemented change causes an undesirable impact. IV.F Operations Phase - Change Management Must schedule, attend, and facilitate system change development activities with the necessary internal and external stakeholders impacted by the change to define requirements, roles, and responsibilities. IV.F Operations Phase - Change Management Must submit a monthly detailed accounting of the work performed by each individual billing time to a system change within the monthly status report. IV.F Operations Phase - Change Management Must include in the monthly status report to the State information regarding all system changes implemented within the previous month. At a minimum, the report will include actual vs. estimated schedule, hours, cost, and resources. IV.F Operations Phase - Change Management Must include in the monthly status report to the State all projected system changes that will be implemented in the upcoming months. At a minimum, the report will include the projected schedule, estimated hours, cost, and resources.
IV.F Operations Phase - Change Management Must conform to future Federal and/or the State-specific standards for data exchange a minimum of 90 calendar days prior to the standard’s effective date, as directed by CMS or the State. IV.F Operations Phase - Change Management Must support system updates or changes by drafting the appropriate revisions to the documentation, and forward them to the State for review and approval a minimum of 45 calendar days prior to intended implementation. Upon the State approval, the Contractor must prepare revisions to the appropriate manuals before implementing the system changes. IV.F Operations Phase - Change Management Must support discussions and meetings on the disposition of change requests with the necessary team members to enable decision making. IV.G Operations Phase - Data and Record Retention Must conduct data refreshes when necessary, that are recoverable. IV.G Operations Phase - Data and Record Retention Must provide access to all data including metadata, to authorized users. IV.G Operations Phase - Data and Record Retention Must continue to follow the State approved Data Retention and Archive Plan. IV.G Operations Phase - Data and Record Retention Must submit a Data Reconciliation Plan for State approval and execute per the approved plan. IV.G Operations Phase - Data and Record Retention Must comply with all applicable Federal and State data retention and archival rules, regulations, and requirements for all program information, data, and correspondence that is received and produced through the solution.
IV.H Operations Phase - Business Continuity and Disaster Recovery Must perform periodic testing to demonstrate that the Business Continuity and Disaster Recovery Plan is correctly implemented and operational and comply with prescribed recovery timelines. IV.H Operations Phase - Business Continuity and Disaster Recovery Must maintain system redundancy as identified in the Business Continuity and Disaster Recovery Plan and approved by the State. IV.H Operations Phase - Business Continuity and Disaster Recovery Must allow MLTC to perform review of data center area that houses solution servers and redundant hardware. IV.H Operations Phase - Business Continuity and Disaster Recovery Must regularly maintain full back up of all data and software at a secure off-site location. IV.H Operations Phase - Business Continuity and Disaster Recovery Must establish and adhere to back-up and recovery procedures. IV.H Operations Phase - Business Continuity and Disaster Recovery Must demonstrate readiness to a production environment in the event of a disaster. IV.H Operations Phase - Business Continuity and Disaster Recovery Must ensure, in the event of a declared major failure or disaster, the DMA must be back online within a maximum of 48 hours of the failure or disaster. IV.H Operations Phase - Business Continuity and Disaster Recovery Must notify the State within a maximum of 15 minutes of discovery of any problem when the problem results in delays in report distribution or problems with online access to critical system functions and information during a business day. site
IV.I Operations Phase - Facility Must provide and maintain a secured facility with access as specified by the State that is ADA compliant. IV.I Operations Phase - Facility Must maintain a secure server room with appropriate HVAC and security for any application servers located on at the Contractors facility. IV.I Operations Phase - Facility Must equip the Contractor facility with connectivity as required for any and all Contractor personnel. IV.I Operations Phase - Facility Must provide all office equipment needed by Contractor personnel while assigned to the DMA contract, including PCs, printers, software, and other necessary office equipment. IV.I Operations Phase - Facility Must provide State access to Contractor’s office space as requested during regular business hours. IV.I Operations Phase - Facility Must provide off-site facilities for storage with secured access. IV.I Operations Phase - Facility Must develop and submit for State approval an Operations Facility Closing Plan. IV.J Operations Phase - Organizational Staffing Must provide a Staffing Plan detailing the Contractor’s staffing levels throughout the duration of the contract to maintain performance measures and support ongoing operations. Plan must include key position qualifications, expected number of resources per position, and hours expected per resource. IV.J Operations Phase - Organizational Staffing Must perform criminal background investigations on all personnel and follow-up investigations every 5 years.
IV.J Operations Phase - Organizational Staffing With respect to all persisting vacancies of Key Personnel during the DDI phase, must receive a credit the State an amount equal to the full-time labor cost including the Contractor’s overhead and margin costs of the unavailable individual, prorated for each day or partial day until the position is satisfactorily filled. For vacancies due to any reason other than dismissal by the State, of the applicable individual, the credit must begin to accrue at the time the vacancy occurs. For vacancies that occur due to the State’s request, the credit must begin to accrue on the sixtieth (60th) business day after the vacancy occurs. Key personnel must be replaced with individuals with comparable experience and qualifications as those submitted by the Contractor in the proposal pending State approval. The Contractor is required to submit resumes and allow the State to interview applicants as part of the approval process. IV.J Operations Phase - Organizational Staffing Must provide key personnel in accordance with Appendix A – Statement of Work Section IV.J.1.a Required Key Positions IV.J Operations Phase - Organizational Staffing Must provide an interim resource within a maximum of five (5) business days for any key personnel vacancies regardless of the reason for the vacancy.
IV.L Operations Phase - User Support Must provide user support through a fully functional user support help desk for external and internal authorized users. Users must have various contact options (e.g. email, online, phone). IV.L Operations Phase - User Support Must provide a means to alert user support personnel when no one is available to take their call for priority issues. IV.L Operations Phase - User Support Must follow State approved escalation procedures. IV.L Operations Phase - User Support Must prioritize and resolve issues using mutually agreed upon severity definitions. IV.L Operations Phase - User Support Must track, manage, and report on user support requests and statuses using the proposed tool. IV.L Operations Phase - User Support Must maintain a portal for submission of User reported errors, questions, and concerns that is searchable by users. This portal must include description of the issue, severity level assigned to the ticket, dates of generation and resolution, User IDs associated with the creation of the ticket, and a method of status update surrounding the issue. IV.L Operations Phase - User Support Must provide ongoing education and training of user support procedures and policies, particularly when a change in the process is needed or required. IV.L Operations Phase - User Support Must make available self-paced training for authorized users. IV.L Operations Phase - User Support Must provide training that includes an overview of the system and hands-on training on the system as requested by the State.
IV.L Operations Phase - User Support Must provide systems help desk via local and toll-free telephone service and via e-mail from 7:00 am to 7:00 pm, central time, Monday through Friday. If requested by the State, the Contractor must staff the SHD on a Saturday or Sunday. IV.L Operations Phase - User Support Must provide help desk staff that must be able to answer user questions regarding DMA system functions and capabilities; report any recurring programmatic and operational problems to appropriate DMA or the State staff for follow-up. IV.L Operations Phase - User Support Must provide help desk staff that must be able to redirect problems or queries that are not supported by the SHD, as appropriate, via a telephone transfer or other agreed upon methodology; and redirect problems or queries specific to data access authorization to the appropriate support staff. IV.L Operations Phase - User Support Must ensure that individuals who place calls to the SHD between the hours of 7:00 pm to 7:00 am, central time, Monday through Friday, are able to leave a message. The SHD must respond to messages by noon of the following business day. IV.L Operations Phase - User Support Must ensure that recurring problems, not specific to system outage, identified by the SHD are documented and reported to DMA management within a maximum of one (1) business day of recognition so that deficiencies are promptly corrected.
IV.M Operations Phase - Privacy and Security Must support the ability to disable user accounts and ensure no disabled accounts can log in or access the system. IV.M Operations Phase - Privacy and Security Must support the automatic disabling of user accounts if failed logins exceed a configurable threshold. IV.M Operations Phase - Privacy and Security Must automatically log off authenticated users after a configurable period of inactivity and display a warning message to the user prior to session timeout. IV.M Operations Phase - Privacy and Security Must support the saving of user profiles for archival purposes, including the ability to the profile. IV.M Operations Phase - Privacy and Security Must generate automatic alerts to system administrators when a breach pattern or unauthorized use activity is detected. IV.M Operations Phase - Privacy and Security Must provide appropriate encryption mechanisms to protect the confidentiality and integrity of critical data, including but not limited to passwords, social security numbers and bank account numbers. IV.M Operations Phase - Privacy and Security Must encrypt sensitive data in transit (including emails) to protect data confidentiality and integrity as appropriate based on the sensitivity of data. IV.M Operations Phase - Privacy and Security Must support the latest version of Security Sockets Layer (SSL)/Transport Layer Security. IV.M Operations Phase - Privacy and Security Must prevent the creation of duplicate accounts. IV.M Operations Phase - Privacy and Security Must support the use HTTPS/SSL for connections between interfaces.
IV.M Operations Phase - Privacy and Security Must deliver to the State a corrective action plan to address deficiencies identified during the audit process within a maximum of ten (10) business days of receipt of the audit report. IV.M Operations Phase - Privacy and Security Must include in audit requirements the applicable subcontractors or vendors delegated any responsibilities related to the DMA’s information systems obligations. The cost of the audit must be borne by the Contractor or subcontractor, not the State. IV.M Operations Phase - Privacy and Security Must support and integrate with the State’s single-sign-on when and as applicable. IV.N.1 Operations Phase - Business Architecture Overview - General Must provide industry expertise and thought leadership in data analytics for all areas of the State’s business architecture. IV.N.1 Operations Phase - Business Architecture Overview - General Must support the State’s operational continual improvement efforts. IV.N.1 Operations Phase - Business Architecture Overview - General Must support the State’s future MITA assessment efforts by evaluating MITA maturity for business architecture processes within the scope of the contract. IV.N.1 Operations Phase - Business Architecture Overview - General Must monitor and inform the State of potential Federal or industry changes which may impact business processes supported by the contract. IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must provide proven, high quality reporting and analytic capabilities that leverage an industry-leading suite of reporting and business intelligence tools.
IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must provide a reporting and analytic tool that is easily configurable by the average user. IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must work with the State to identify and develop requirements for reports and analytics for the DMA solution, including mechanisms and methodologies for each. IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must provide, implement, and maintain the reports, analytics, and associated catalogue/index/metadata based on State approved requirements for the DMA solution, including mechanisms and methodologies for each. IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must produce and distribute all production reports and analytics within the timeframes and according to the format, input parameters, content, frequency, media, and number of copies specified by the State. IV.N.2 Operations Phase - Business Architecture Overview - Reporting and Analytics Must generate system activity, balancing and error reports as defined by the State and as requested by the State. IV.N.3 Operations Phase - Business Architecture Overview - Creating, managing, and performing statistical analysis, forecasting, and predictive analytics Must track all variable data in the database resulting in the provision of statistical analysis, forecasting, and predictive analytics and deliver results to the State on a frequency as determined by the State.
IV.N.3 Operations Phase - Business Architecture Overview - Creating, managing, and performing statistical analysis, forecasting, and predictive analytics Must provide Contractor and future predictive algorithms to the State on a frequency as determined by the State. IV.N.3 Operations Phase - Business Architecture Overview - Creating, managing, and performing statistical analysis, forecasting, and predictive analytics Must identify, interrogate, monitor, assess and categorize various variable data in the database resulting in the provision of statistical analysis, forecasting, and predictive analytics. IV.N.3 Operations Phase - Business Architecture Overview - Creating, managing, and performing statistical analysis, forecasting, and predictive analytics Must manage the results of statistical analysis, forecasting, and predictive analytics to meet State and Federal guidelines and laws. IV.N.3 Operations Phase - Business Architecture Overview - Creating, managing, and performing statistical analysis, forecasting, and predictive analytics Must provide interpretation, guidance and training to State users regarding predictive algorithms and other results of statistical analysis, forecasting, and predictive analytics. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide secure generation and on-line real-time access of all data entities (as identified in the overview) of pre-defined queries, ad-hoc and business reports on a timely basis to meet Federal, State and Contract requirements. Reference the Bidders Library for a list of required reports.
IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain State approved processes and methods to support the management of a dynamic information request practice that includes pre-defined and ad hoc reports and analytics. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain State approved reports and supporting documentation that meet State and Federal specifications. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain the DMA report catalog, analytics catalog, and data dictionary that includes relationship and reference mapping. This information must be available in electronic searchable format and exportable to support print formats. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must document and provide verification of pre-defined reports’ accuracy and validity on an annual basis. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain State approved algorithms and supporting documentation utilized within the DMA. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain a State approved Communication Plan regarding DMA system and data events, information on known data issues, and status updates. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide support services to provide, implement, and maintain analytics and reports of complexity levels outside the scope of State staff knowledge and training levels.
IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must utilize a minimal level of manual effort in providing information that reveals potential defects in level of care and quality of service. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must suppress processing on an individual(s) within specified categories on a run-to-run basis. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must support pattern recognition and provide an automated fraud and abuse profiling system for the ongoing monitoring of provider and member claims to detect patterns of potential fraud, waste, abuse and excessive billing. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must update all reference data based on a schedule agreed upon with State.(e.g. claims, provider, member) IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must maintain a process to apply weighting and ranking of those exception report items identified by the State. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must exempt individual and mass adjustments or voids from SURS profiles and reports based on configurable rules. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must recommend members for referral to restricted access programs. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must perform “absence of” scenario analysis (examples include inpatient hospitalizations or prescriptions with no physician visit, durable medical equipment with no relevant diagnosis).
IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must provide statistical models to support simple random sampling and extrapolation that complies with generally accepted statistical audit and governmental accounting standards. (Nebraska Medicaid currently uses RAT- STATS Statistical Software) IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must suggest additional projects and ideas for Program Integrity efforts to prevent or identify fraud, waste, abuse, or erroneous payments. IV.N.6.a Operations Phase - Business Architecture Overview - Case Management - General Must provide a real time, State of the art, configurable case management tool to identify, create, document, and manage fraud, waste, abuse, and erroneous payments in connection with the State’s Program Integrity process. IV.N.6.a Operations Phase - Business Architecture Overview - Case Management - General Must provide a solution that is configurable and capable of supporting multiple business processes in addition to Program Integrity. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must initiate cases from a referral form and must support manual initiation of cases. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must receive, record and funnel all initial cases into a queue for assessment, assignment and investigation. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must assign caseload “weights” to cases (e.g., characteristics of claim, claim edits, claim submission type, prior authorization, and client).
IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must provide the user the choice to either automatically assign cases or assign cases on a case-by-case basis. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must utilize multi-level drop-down menus for consistent categorization and reporting. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must track and manage all case management data including adverse actions, outcomes, expenditures, payments, receivables, recoupments and adjustments in accordance with State guidelines. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must track and report AR/AP (e.g., check numbers, payer, payee, date, amount, and memo). IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must capture, track, display, and maintain all provider data, including agreement and termination information and historical communications. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must maintain, track, log, archive, display, generate and auto generate, as defined by the State, all provider communications. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide search capability of all current and historic case management data. IV.N.6.c Operations Phase - Business Architecture Overview - Case Must provide letter templates including the use of digital signatures for all case management letters.
Management - Manage Case Information IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide tracking for individual cases, multiple cases/projects, and policy recommendations. Each case type has a unique set of fields and events that reflect the unique characteristics and processes for that case. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must maintain links between cases and historical scanned/uploaded documents. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide customized access to cases to ensure case information is only visible to those authorized to see it, based on role level, case type, or other criteria. This will also restrict rights so that certain users can be given “read-only” access to cases and others can edit case files. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must allow users to sort and search for keywords or names throughout the case management tool. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must allow users to add notes to any case from the dashboard or from within the case and automatically store these notes based on configurable business rules.
IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide functionality to establish and modify workload distribution to manage workloads on an as needed basis. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must incorporate tools such as a spell-check option for all free-form data entry fields and use menus for common data elements such as date fields and provider types. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must modify and adapt case management processes, procedures and functionality to business process changes and maintain up to date functionality with minimal impact to users. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide training to all current and new users initially and when upgrades are implemented and/or when processes, procedures and/or functionality changes. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide user manuals with updates as appropriate. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must provide on-line help for all features, functions and data element fields. IV.N.6.c Operations Phase - Business Architecture Overview - Case Management - Manage Case Information Must allow for users to see all assigned cases and identify all of their open cases and those which have deadlines that are approaching or have passed.
IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must provide applications, operating software, middleware, and networking hardware and software that is able to interoperate as needed with the State’s systems and must conform to applicable standards and specifications set by the State. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must comply with Section 508 of the Federal Rehabilitation Act and the World Wide WDMA Consortium (W3C), WDMA Accessibility Initiation, Section 508 (a)(1)(A). IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must support branding using official State content (e.g. logos, images). IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must follow a modular, flexible approach to systems design consistent with the MITA 3.0 guidelines, CMS Seven Conditions and Standards for Enhanced Funding and Service-Oriented Architecture (SOA) design principles including but not limited to the use of open interfaces and exposed application programming interfaces (API); the separation of business rules from core programming; and the availability of business rules in both human and machine-readable formats. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must provide contextual “help” functionality throughout the system that users can link to for clarification or additional information.
IV.O.4 Operations Phase - Business Information and Technical Architecture - Master Data Management Must support the global identification, linking and synchronization of entity (e.g. consumer, provider, facility) information across DMA data sources through semantic reconciliation of master data. IV.O.4 Operations Phase - Business Information and Technical Architecture - Master Data Management Must support ongoing master data stewardship and governance requirements through monitoring and techniques as defined in the Master Data Management Plan. IV.O.4 Operations Phase - Business Information and Technical Architecture - Master Data Management Must enable access and usability of single entity views providing essential identification and reference information across trading partners. IV.O.4 Operations Phase - Business Information and Technical Architecture - Master Data Management Must establish State approved automated processes and workflow for notifying the appropriate State systems of MDM impact transactions (e.g. member address changes). IV.O.5 Operations Phase - Business Information and Technical Architecture - Data Models Must provide, implement, and maintain a State approved Data Modeling Plan that includes strategy, methodology, process, tools, resourcing, quality and contingency aspects. IV.O.5 Operations Phase - Business Information and Technical Architecture - Data Models Must provide, implement, and maintain State approved DMA Data Models for State Medicaid operations including meta, semantic, conceptual, logical, and physical data models based on State Medicaid business areas and processes.
IV.O.6 Operations Phase - Business Information and Technical Architecture - Data Integration Must provide, implement, and maintain a State approved Data Integration Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. IV.O.6 Operations Phase - Business Information and Technical Architecture - Data Integration Must provide, implement, and maintain all State approved data integration processes (e.g., ETL, ELT). IV.O.6 Operations Phase - Business Information and Technical Architecture - Data Integration Must identify potential duplicate records and, upon confirmation of said duplicate record by the State, resolve the duplication such that the duplicate records are resolved (e.g. linked, merged). IV.O.6 Operations Phase - Business Information and Technical Architecture - Data Integration Must process transactions to merge and separate records as defined by the State. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must provide, implement, and maintain a State approved Data Sharing Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must support data semantics, data harmonization strategies, ownership, compliance, security & privacy, and the quality assurance of shared data as defined in the Data Sharing Plan. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must provide, implement, and maintain middleware (e.g., ESB/interface/integration engine) that enables DMA to effectively exchange information with the State trading partners as defined in the Data Sharing Plan.
IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must develop, implement, and maintain State approved Interface Control Documents (ICDs) that provide specifications and SLA’s for each data exchange and interface. IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must develop, implement, and maintain a State approved catalogue of Interface Control Documents (ICDs). IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must transmit all appropriate data through the State data exchanges and interfaces as specified in the Interface Control Document. IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must provide the capability to interface with existing and future systems via batch file transfers and transactionally via standard service. IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must work with the State to develop and support an effective data exchange between the DMA and all stakeholders involved in the DMA business processes, including the State. IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must send and receive files and transactions, in formats and methods specified by the State. IV.O.8 Operations Phase - Business Information and Technical Architecture - Data Exchanges & Interfaces Must receive and investigate any discrepancies on data exchanges.
IV.O.10.b Operations Phase - Business Information and Technical Architecture - Enterprise Data Warehouse (EDW) - EDW Architecture Must provide, implement, and maintain a State approved Enterprise Data Warehouse (EDW) Architecture that provides EDW architecture views using architectural standards, includes alignment to all DMA related components of business, technology, and information, and addresses data semantics, data harmonization strategies, data ownership, compliance, security & privacy, and the quality assurance of EDW data. IV.O.10.b Operations Phase - Business Information and Technical Architecture - Enterprise Data Warehouse (EDW) - EDW Architecture Must provide, implement, and maintain multi-dimensional data architecture (e.g., data cubes, data marts) that supports both derived and aggregated data based on business area, function and process. IV.O.10.c Operations Phase - Business Information and Technical Architecture - Enterprise Data Warehouse (EDW) - EDW Tools and Methods Must provide, implement, and maintain EDW tools and methods that support design, development, deployment, and maintenance of the EDW. IV.O.10.c Operations Phase - Business Information and Technical Architecture - Enterprise Data Warehouse (EDW) - EDW Tools and Methods Must provide, implement, and maintain State approved data prototyping tools and methods to promote understanding of DMA EDW usage as aligned to business objectives. IV.O.10.c Operations Phase - Business Information and Technical Architecture - Enterprise Data Warehouse (EDW) - EDW Tools and Methods Must provide, implement, and maintain State approved data mining tools and methods to identify and report on various patterns, generalizations, dependencies, and anomalies within the data.
IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to query, analyze, and report on multidimensional data. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to slice, dice, and rollup the results of queries and analysis. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that support traditional, statistical, cluster, predictive, prescriptive, sampling, extrapolation, trending, and geospatial reporting and analysis. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to establish and modify delivery schedule and mode of delivery for reports and analytics based on configurable rules. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to merge geospatial datasets. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to load and unload data efficiently.
IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to integrate data through cross-platform SQL queries. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide users the ability to compare and synchronize data between different data sources. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that support statistical analysis (e.g. mathematical and statistical calculations). IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that support random sampling, using standard statistical methodologies for monitoring functions. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that support creating temporary data elements for reports by specifying functions that operate on existing data elements. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide the ability for use by novice and expert users to generate charts, graphs, and other visual representations of data results.
IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods to create scorecards and dashboards. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide the ability to make all reporting assets (e.g. reports, dashboards) available through online, hardcopy, and industry standard data extract outputs including CSV, Microsoft Excel, Microsoft Word, and Adobe PDF. IV.O.11 Operations Phase - Business Information and Technical Architecture - Reporting and Analytics Tools and Methods Must provide, implement, and maintain reporting and analytic tools and methods that provide the ability to generate information (e.g. reports, data sets, alerts, notifications) based on configurable rules applied against queried data (e.g. notify User X if # of encounters exceed N), on demand or scheduled. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must enable policies, rules, operational logic, and related decisions to be defined, tested, executed, and maintained separately from application code. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must perform rules addition, deletion, and modification per State direction and approval without modifying the application code. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must support rules management (rules addition, deletion, modification and validation) in natural language, English-like syntax without the need to learn a specialized coding language.
IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the ability to clone rules, modify them and then implement them as new separate rules. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must test, validate and receive State approval for rule changes prior to implementation. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for users to receive push notifications/alerts based on parameters (rules and/or rules groups). IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability to track and report rule usage, exception usage, and when a rules fail to work as designed, and provide recommendations to resolve rule failure. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for a multi-level rule review and approval process that will validate logic errors, conflicts, redundancy and incompleteness across business rules to identify any conflicts in business rules as they are being developed, tested, and implemented. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide version control including the ability to revert to a prior version of the rules if there are unwanted or unexpected consequences of a rule change.
IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide, implement, and maintain a State approved DMA Audit and Control Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must track, log, and provide reporting on, in human readable format, data changes including State approved audit information such as the date, time and user or system making the change. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must track, log, and provide reporting on, in human readable format, inquiries, views, reports, or access of data that may require such tracking as a result of law, policy, or data use agreements including State approved audit information such as the date, time and user or system initiating the transaction. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide controls including preventive controls (i.e. controls designed to prevent errors and unauthorized events from occurring), detective controls (i.e. controls designed to identify errors and unauthorized transactions which have occurred in the system), and corrective controls (controls to ensure the correction of problems identified by detective controls).
IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide the date and identification “stamp” displayed on any online inquiry. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide the ability to trace data from the final place of recording back to its source data file or document. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must support audit listings, transaction reports, update reports, transaction logs, or error logs. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must facilitate auditing of individual records as well as batch audits. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must maintain audit information online for a minimum of two years and be retrievable within a maximum of 48 hours. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must capture and retain the data that was used at the point in time that a particular action took place. Subsequent changes to data elements should not overwrite the values used to make a determination in the past. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide inherent functionality that prevents the alteration of finalized audit records. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must maintain a comprehensive audit trail of systematic and physical access to PHI, PII and FTI. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must track and retain a log of all successful and unsuccessful logins.
IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must correct system issues by the effective date to be approved by the State. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must not schedule systems downtime to perform system maintenance, repair, or upgrade activities to occur during hours that could compromise or prevent critical business operations, unless otherwise agreed to in advance by the State. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must work with the State on any testing initiative required by the State and must provide sufficient system access to allow the State staff to participate in the testing activities. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must provide, implement, and maintain a State approved annual system refresh plan that must outline how information systems within the DMA’s span of control will be systematically assessed to determine the need to modify, upgrade, or replace application software, operating hardware and software, telecommunications capabilities, or information management policies and procedures in response to changes in business requirements, technology obsolescence, staff turnover, or any other relevant issues.
V.B Turnover – Turnover Planning Must submit a Turnover Pla, to the State for approval, that includes strategy, methodology, process, tools, quality and contingency aspects within a maximum of two (2) years of the start of operations. The turnover plan must be reviewed and submitted every contract year. The plan must include an inventory list of all materials that will be transitioned and an inventory list of all materials that will not be transitioned during the Turnover Phase. V.B Turnover – Turnover Planning Must produce and submit an updated Turnover Plan to the State for approval within a maximum of thirty (30) days after being informed by the State that the Turnover Phase is to begin. V.B Turnover – Turnover Planning Must include in the Turnover Plan at a minimum, the proposed approach, tasks, schedule, entrance and exit criteria, training, readiness walkthrough process, and documentation update procedures. V.B Turnover – Turnover Planning Must participate in planning sessions with the State and successor Contractor during the turnover phase. V.C Turnover – Project Management and Systems Development Lifecycle Must manage all aspects of the turnover that affect cost, schedule, performance (scope and quality), risk/issues/opportunities and resources that are under Contractor control.
V.D.1 Turnover – Performance and Status Reporting Must have required expertise available at turnover meetings as request by the State. The State must provide a minimum of one (1) business day notice except in emergency situations. V.D.1 Turnover – Performance and Status Reporting Must deduct any State required deductions from the Contractor’s monthly operational invoices. V.D.1 Turnover – Performance and Status Reporting Must develop and implement corrective action plans as requested by the State. V.D.2 Turnover – Performance and Status Reporting Must prepare and submit a weekly status report specific to turnover activities. V.D.2 Turnover – Performance and Status Reporting Must prepare and submit a monthly status report specific to turnover activities. V.D.2 Turnover – Performance and Status Reporting Must prepare and submit a quarterly status report specific to turnover activities. V.D.2 Turnover – Performance and Status Reporting Must produce transaction data, reports, and performance information that would contribute to program evaluation, continuous improvement in business operations, and transparency and accountability. V.E Turnover – Close-Out Deliverables Must provide current versions of all documentation deliverables included in the Contractor’s proposed deliverables catalog for the life of the contract in conformance with the provided templates, media, instructions, and procedures and of the quality of the provided examples submitted with the proposal.
V.F Turnover – Quality Assurance and Monitoring Must use the established rating system for defects. V.F Turnover – Quality Assurance and Monitoring Must certify that all turnover items and deliverables have been completed to the best of the ability of the Contractor in aiding the State and/or successor Contractor be successful in turnover. V.F Turnover – Quality Assurance and Monitoring Must ensure compliance with all Privacy and Security regulations during the turnover phase and maintain confidentiality in the transmission of documentation to the State or the successor Contractor. V.F Turnover – Quality Assurance and Monitoring Must identify and document any issues or deficiencies that remain unresolved at the end of the turnover phase. V.G Turnover – Change Management Must request and receive State approval prior to implementing a change during the turnover phase of the contract. V.G Turnover – Change Management Must update and submit for review and approval the Operational Change Management Plan to address turnover based on the methodologies proposed to manage and implement changes to the production system during the turnover phase of the contract. V.G Turnover – Change Management Must put into practice and follow the approved updates to the Operational Change Management Plan for Turnover and use sound System Development Life Cycle (SDLC) methodologies to implement system changes while maintain production system operations.
V.G Turnover – Change Management Must maintain a formal process to track and manage change requests within the turnover phase of the contract. V.G Turnover – Change Management Must provide a projection of change requests to be implemented in the upcoming months prior to turnover. V.G Turnover – Change Management Must analyze all change requests and submit an assessment to the State within a maximum of ten (10) days of the request. At a minimum, the assessment must include resource estimates, cost, schedule, and impacts to external entities and business operations. V.G Turnover – Change Management Must perform a MITA assessment of all change requests and coordinate with the State’s MITA Coordinator. V.G Turnover – Change Management Must submit all change requests and analysis results to the State Change Review Board for disposition and prioritization. V.G Turnover – Change Management Must develop and submit for review and approval a detailed Integrated Master Schedule (IMS) for all approved changes; addressing each phase the SDLC and identifying all integration points and dependencies between all Contractors and the State including interfaces, inputs, and outputs that the Contractor requires from other Contractors, the State, or other impacted entities. V.G Turnover – Change Management Must design, develop, test and implement approved changes within the approved IMS timeframes.
V.G Turnover – Change Management Must implement changes in a manner with the least possible impact to operations and turnover timeframes while maintaining a high quality delivery. V.G Turnover – Change Management Must provide the ability to rapidly revert to the previous system configuration when a newly implemented change causes an undesirable impact, as defined within the approved Change Management Plan. V.G Turnover – Change Management Must develop and submit for review and approval a remediation plan for reconfiguration and redeployment when a newly implemented change causes an undesirable impact, as defined within the approved Change Management Plan. V.G Turnover – Change Management Must include in the weekly status report an update on the status of each change request in work. V.G Turnover – Change Management Must submit monthly detailed accounting to the State’s satisfaction, of the work performed by each individual billing time to change requests. V.H Turnover – Data and Record Migration and Turnover Must include details regarding data and record migration within the turnover plan. V.H Turnover – Data and Record Migration and Turnover Must conduct data and related content refreshes according to the approved plan. V.H Turnover – Data and Record Migration and Turnover Must comply with all applicable Federal and State rules, regulations and requirements for all program information, data, and correspondence that is received and/or produced.
V.H Turnover – Data and Record Migration and Turnover Must transition all data to the State or successor in the documented physical data model format per the approved turnover plan and schedule. If the Contractor’s data model is proprietary, the Contractor may transition in another format, but must provide documentation of the model format including data relationships. V.H Turnover – Data and Record Migration and Turnover Must provide all data documentation to the State and/or successor. Examples of documentation including interface specifications, report specifications, conceptual, logical and physical data models, and the extract transform and load logic for data received during operations, etc. If the Contractor’s data model is proprietary, the Contractor must update the documentation to reflect the format in which the data is being transitioned and migrated. V.I Turnover – Organizational Staffing Must submit and maintain an Organizational Chart for the Turnover Phase. V.I Turnover – Organizational Staffing Must submit resumes of Key personnel to the State for approval.
V.I Turnover – Organizational Staffing Must submit a Staffing Contingency Plan for operations during the Turnover Phase. V.I Turnover – Organizational Staffing Must acquire State approval for key staff and key staff replacements. V.I Turnover – Organizational Staffing Must provide unrestricted access to appropriate Contractor personnel for discussion of problems or concerns. V.I Turnover – Organizational Staffing Must cooperate with the State and/or successor Contractor on transition of staff supporting the contract to either the State or the successor. V.I Turnover – Organizational Staffing Must not in any way interfere with the transition of employees and/or subcontractors to the State or a successor. V.J Turnover – Cooperation with Successor Must provide open access of knowledgeable teams to the State and / or successor Contractor to answer questions. V.J Turnover – Cooperation with Successor Must coordinate and facilitate timely transition to the State and / or successor Contractor. V.J Turnover – Cooperation with Successor Must not interfere in any way with the transition to the State and / or successor Contractor. V.J Turnover – Cooperation with Successor Must provide direction in identifying the necessary processes and procedures for maintenance and support activities. V.J Turnover – Cooperation with Successor Must provide business operations support as the successor begins assuming the business operations functions. V.J Turnover – Cooperation with Successor Must demonstrate how the system tools are used to operate, control and maintain the system.