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) – 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. II.B Design, Development, and Implementation (DDI) – Project Management and Must provide updated and compatible weekly extracts (or any other interval requested by the State) of its plan(s) to the State for and – Business
Systems Development Life Cycle (SDLC) II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life (SDLC) Must complete and maintain a requirements traceability matrix. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life Cycle (SDLC) Must provide a State approved Data Management 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 Governance Plan that includes approach, strategy, methodology, process, tools, resourcing, quality and contingency aspects. II.B Design, Development, and Implementation (DDI) – Project Management and Systems Development Life (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 (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.
Data Conversion and Data Load process and data load from all source systems. II.G Design, Development, Implementation (DDI) – Data Conversion and Data Load Must develop and provide iterative and data conversion execution packages according to plan that includes appropriate information on the process, methods, logic, data sets converted, quality findings, and test results. II.G Design, Development, and Implementation (DDI) – Data Conversion and Data Load Must convert and load the appropriate data from all State systems necessary to support the requirements of the contract. II.H Design, Development, and Implementation (DDI) – Environments Must provide and host all hardware, software, and connectivity required to maintain and operate the environments and for all authorized users to access and use the system. II.H Design, Development, and Implementation (DDI) – Environments Must manage and maintain software upgrades and licenses necessary to fulfill the requirements of the contract. II.H Design, Development, and Implementation (DDI) – Environments Must provide environments that enforce standard security and privacy. 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 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 submit a monthly updated resource utilization matrix that identifies resource use expectations by month (i.e. hours by person, throughout the DDI phase including actuals vs planned for previous months. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must submit resumes of Key personnel to the for approval, for chage in personnel. II.K Design, Development, and Implementation (DDI) – 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
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. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must provide key personnel in accordance with II.K.1. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must ensure that customer facing staff are within Lincoln, Nebraska 90% of the time during the implementation. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must maintain an Organizational Chart and project contact list. II.K Design, Development, and Implementation (DDI) – Organizational Staffing Must acquire State approval for key staff and key staff replacements. 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 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.L Design, Development, and Implementation (DDI) – Documentation Must produce agendas and minutes of project meetings and maintain in the online repository. II.M Design, Development, and Implementation (DDI) – User Support Must provide State users access to each environment as directed by the State. II.M Design, Development, and Implementation (DDI) – User Support Must establish a contact point for State users to address access issues with environments during the hours of 8 am – 5 pm local time during all SState business days. II.M Design, Development, and Implementation (DDI) – User Support Must resolve user access issues within a maximum of one (1) business day. II.M Design, Development, and Implementation (DDI) – User Support Must provide telephone and email support for user support and questions. II.M Design, Development, and Implementation (DDI) – User Support Must provide training to users as needed in support of the DDI phase.
II.N Design, Development, and Implementation (DDI) – System Readiness Must perform system readiness testing of all system functionality. II.N Design, Development, and Implementation (DDI) – System Readiness Must provide a comprehensive System Readiness Test Plan. 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 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.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. 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 to back out of a go-live, including an integrated practice of these actions with the requisite actors prior to undertaking a go-live cutover. II.Q Design, Development, and Implementation (DDI) – Implementation and Contingency Must provide the State a post implementation report noting any issues encountered in hardware, network, software or operations during implementation and what their resolution was or is expected to be. III.A Initial Operations and CMS Certification – Phase Overview Must perform all functions necessary to manage the initial operations to meet all requirements, performance, and service levels required for the Operations Phase. III.A Initial Operations and CMS Certification – Phase Overview Must coordinate with the and other contractors as necessary to achieve certification retro-active to the date of implementation.
operational audit questions, help with certifications and respond to requests for information on system use, navigation, work flow, function, etc. III.C Initial Operations and CMS Certification – CMS Certification Must submit a certification plan within a minimum of 120 days to implementation. III.C Initial Operations and CMS Certification – CMS Certification Must submit all necessary materials such as certification packets required by CMS for certification within a maximum of 150 days after the implementation date. III.C Initial Operations and CMS Certification – CMS Certification Must provide any necessary support to the State throughout the CMS certification planning and review process. III.C Initial Operations and CMS Certification – CMS Certification Must provide training and education to State personnel on the most current CMS certification process prior to the start of certification activities. III.C Initial Operations and CMS Certification – CMS Certification Must remedy all system or operational issues required for CMS certification. III.D Initial Operations and CMS Certification – Organizational Staffing Must provide a resource utilization matrix detailing the Contractor’s increased staffing levels to address go-live issues, preparation and planning for certification, and maintaining performance measures. III.D Initial Operations and CMS Certification – Organizational Staffing Must submit resumes of Key personnel to the State for approval. 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
implementing changes to the production system. IV.B Operations - 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 - 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 reasonably support the Contractor’s coordination efforts. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must prepare and submit the Integrated Master Schedule (IMS) for releases which 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. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Within the IMS, must at a minimum decompose all tasks starting within a 120-day forward window into the future. This 120-day view must be maintained from month-to-month to
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 - 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 address corrective and preventive actions. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must include in the proposed Operational Project Management Plan all integration points between all Contractors, organizations, and the State including interfaces, inputs, and outputs required from other Contractors, organizations, or the State. IV.B Operations Phase - Project Management and Systems Development Life Cycle (SDLC) Must put into practice and follow the approved Operational Project Management Plan and submit for re-approval any changes to the approved plan. IV.B Operations Phase - Project Management and Must schedule, attend, and facilitate recurring Operational Project Management status
IV.H Operations Phase - Business Continuity and Disaster Recovery Must provide remote back-up that includes operating instructions, procedures, reference system documentation, and operational files. IV.H Operations Phase - Business Continuity and Disaster Recovery Must provide data back-up and restoration policy and procedures that include, but not be limited to: Descriptions of the controls for back-up processing, including how frequently and target restoration times. Documented back-up and restoration procedures. Location of where data will be backed up (off-site or on-site, as applicable). Identification and description of what is being backed up as part of the back-up plan. Any change in back-up procedures in relation to the DMA’s technology changes. IV.H Operations Phase - Business Continuity and Disaster Recovery Must provide a list of all back-up files to be stored at remote locations, which must be approved by the State before tapes are moved off-site. IV.I Operations Phase - Facility Must develop and submit for State approval an Operations Facility Plan.
IV.J Operations - Organizational Staffing Must provide and maintain an updated project contact list. IV.K Operations Phase - Documentation Must maintain Business and Technical Operating Procedures as any changes are made (e.g. job schedules, data dictionary, and system software and hardware failure procedures) and submit for State approval. IV.K Operations - Documentation Must create and maintain project artifacts, agendas and meeting minutes in a State approved format for the duration of the contract. IV.K Operations Phase - Documentation Must maintain companion guides for HIPAA transactions applicable to the DMA scope of work. Companion Guides, tutorials, help files, FAQ’s and tool tips for online applications. IV.K Operations Phase - Documentation Must develop, prepare, print, maintain/update, produce, and distribute DMA system documentation and DMA user manuals during the term of the contract. All manuals must be available in an electronic format that is compatible with Department standards. The Contractor is responsible for developing and providing to the Department complete, accurate, and timely documentation of the DMA. IV.K Operations Phase - Documentation Must update system documentation and user manuals and distribute in final form, for all changes, corrections, or enhancements to the system, prior to Department approval of the system change.
password protected for both sending and receiving any PHI, PII and/or FTI. IV.M Operations Phase - Privacy and Security Must utilize an access management function that restricts access to varying levels of system functionality and information. IV.M Operations - Privacy and Security Must restrict access to information on a “least privilege” basis (e.g., users who are permitted inquiry privileges only will not be permitted to modify information). IV.M Operations Phase - Privacy and Security Must restrict access to specific system functions and information based on an individual user profile, including inquiry only capabilities. Access to all functions must be restricted to specified staff, with approval of the State. IV.M Operations Phase - Privacy and Security Must restrict unsuccessful attempts to access system functions to attempts, with a system function that automatically prevents further access attempts and records those occurrences. IV.M Operations - Privacy and Security Must provide for the physical safeguarding of its data processing facilities and the systems and information housed within those facilities. The DMA must provide the State with access to data facilities on request. IV.M Operations Phase - Privacy and Security Must restrict perimeter access to equipment sites, processing areas, and storage areas through a key card or other comparable system, as well as provide accountability control to record access attempts, including attempts of unauthorized access.
forecasting, and predictive analytics 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 - 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 - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide the ability to view, search, print and export into various formats (e.g. Excel, Word, charts, graphs) all data entities of pre-defined queries, ad-hoc and business reports. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must allow authorized users to view results of filtered reports, and pre-defined query searches based on multiple or single criteria, with the ability to perform secondary and tertiary searches within the primary search results. IV.N.4 Operations Phase - Business Architecture Must authorized users to view results of filtered reports, ad-hoc
Overview - Managing Queries and Reports – Predefined and Ad-Hoc and user defined query searches based on multiple or single criteria, with the ability to perform secondary and tertiary searches within the primary search results. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must create all CMS Federal Reports including but not limited to: TMSIS CMS-64 CMS64-EC CMS-21 CMS-21E CMS-21B CMS-37 Note: Nebraska CHIP program is a combined Medicaid Expansion and Separate CHIP. Also, managed care is operated under a 1915(b) waiver. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports Predefined and Ad-Hoc Must create all CMS Federal Annual reports including but not limited to: CMS-416 CMS-372 reports for all active HCBS waivers. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must create all new required Federal Reports including file submissions as defined by CMS and the State. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide dashboard solutions and performance management scorecards that are updated on a schedule defined by the State. IV.N.4 Operations Phase - Business Architecture Must provide a secured provider portal displaying provider specific
Overview - Managing Queries and Reports – Predefined and Ad-Hoc reports informing the provider of how their trends compare with their peers. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide the flexibility to vary time periods for reporting purposes and to produce reports on any frequency specified by the State. IV.N.4 Operations - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must store and maintain business reports for a period specified by the State. IV.N.4 Operations Phase - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide the ability to save and query results for a period specified by the State. 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 - 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 formats. IV.N.4 Operations Phase - Business Architecture Overview - Managing Must document and provide verification of pre-defined reports’
Queries and Reports – Predefined and Ad-Hoc accuracy and validity on an annual 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 - Business Architecture Overview - Managing Queries and Reports – Predefined and Ad-Hoc Must provide, implement, and maintain a 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 provide a configurable that identifies potential incidents of fraud, waste, abuse and erroneous payments. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must develop, update and maintain an algorithm library throughout the life of the contract. New algorithms will be created by SState staff, the Contractor, and the program integrity field as the industry changes and as the nature of fraud, waste abuse, and erroneous payments evolves. IV.N.5 Operations - Business Architecture Overview - Program Integrity Must authorized users to create, modify, and run the rules and algorithms with limited or no technical support. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must incorporate link analysis of providers and members where relationships extend beyond provider to provider relationships (e.g. interwoven relationships between providers, members,
owners, addresses, members that use the same cluster of providers. Members that are providers). IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must provide a subject matter expert, who understands the algorithms used to extract data, to testify and support an administrative State or Federal action, and the appeals process. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must provide predictive modeling (leveraging historical information to project outcomes) and early warning capabilities and analytics for detecting fraud, waste, abuse and erroneous payments in paid claims and managed care entity encounter data. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must include application training modules including self-paced computer-based modules, training, application tutorials, and searchable help features for authorized users. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must implement, maintain and operate a configurable surveillance, utilization, and review subsystem according to Department business rules. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must implement, maintain, and operate a configurable program integrity solution which meets all requirements for CMS certification. IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must profile provider groups, independent/solo providers, and individual providers within group IV.N.5 Operations Phase - Business Architecture Overview - Program Integrity Must perform analysis of rendering, attending, admitting, supervising, ordering and prescribing provider's billing practices to generate reports of aberrant utilization patterns.
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 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 Must initiate cases from a referral form and must support manual initiation of cases.
Management - Case Identification and Creation 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 auto-populate fields and values on all case-related forms and web-based tools including exclusionary provider data. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must have access to internal and external agency databases to extract data to pre-populate index fields, and/or values (e.g. MMIS, provider data, MMIS member data, Electronic Health Records). Interfaces between State Contractors for data will be arranged to facilitate the IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must suggest and supply data and information from other sources to pre-populate values (address, licensure). IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must identify and link related case data and activities. IV.N.6.b Operations Phase - Business Architecture Overview - Case Must include text note functionality (e.g. keyword search, sort functions) for cases.
Management - Case Identification and Creation IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must customize case data to the State’s business processes. IV.N.6.b Operations Phase - Business Architecture Overview - Case Management - Case Identification and Creation Must provide notification to the assigned investigator when a new case is created. IV.N.6.b Operations - 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 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 Must maintain, track, log, archive, display, generate and auto
Overview - Case Management - Manage Case Information 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 Management - Manage Case Information Must provide letter templates including the use of digital signatures for all case management letters. 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 - Business Architecture Must allow users to add notes to any case from the dashboard or
Management - Manage Case Information designated work queues and processing. IV.N.6.c Operations - 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.N.6.c Operations Phase - Business Architecture Must update multiple cases in a project by selecting certain cases
IV.N.6.d Operations Phase - Business Architecture Overview - Case Management - Audit Cases Must allow managers to track investigator caseloads, missed deadlines and aging cases. IV.N.6.d Operations Phase - Business Architecture Overview - Case Management - Audit Cases Must maintain a complete history and audit trail of all cases. IV.N.6.d Operations Phase - Business Architecture Overview - Case Management - Audit Cases Must provide the functionality to analyze caseloads, clearance rates, dispositions and other management data. IV.N.6.d Operations Phase - Business Architecture Overview - Case Management - Audit Cases Must provide time tracking and complete history/audit trails. IV.N.6.d Operations Phase - Business Architecture Overview - Case Management - Audit Cases Must retain all data on-line for a period of time defined by the State. IV.N.7 Operations - Business Architecture Overview – Encounter Processing Must process and load encounter and FFS claims to the data warehouse received in HIPAA and NCPDP standard formats as applicable by claim type. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must validate that encounter and FFS claims are in compliance with and NCPDP standards and operating rules as applicable by claim type. IV.N.7 Operations - Business Architecture Overview – Encounter Processing Must perform integrity edits as directed by the State. Integrity edits are those that would be in addition to HIPAA compliance edits. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must maintain all applicable reference for encounter processing purposes.
IV.N.7 Operations - Business Architecture Overview – Encounter Processing Must maintain a method to distinguish between encounter and FFS claim records. IV.N.7 Operations - Business Architecture Overview – Encounter Processing Must reject claims that fail compliance edits. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must flag, capture and report on encounters and claims that fail integrity edits. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must support a workflow and method to work with the MCO for submission of a corrected encounter IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must provide a detailed integrity edit report describing the reason for the integrity flag and work with MCO to resolve and resubmit. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must provide management reconciliation reports for rejected encounters and claims resolution. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must provide online work queues for flagged claims resolution. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must capture and report on other types of payment records including MCO supplemental payments such as maternity Kick Payments. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must report on content of the database via dashboards, static and ad-hoc reports. IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must report on the activity of encounter and claim receipts.
IV.N.7 Operations Phase - Business Architecture Overview – Encounter Processing Must receive and process other encounter data (e.g. authorization, quality of care, performance, etc.). IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must provide, implement, and maintain a approved DMA information and technical architecture that provides architecture views using architectural standards including alignment to all DMA related components of business, technology, and information. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must work with the to identify and develop requirements for services in the context of service oriented architecture (SOA) for the DMA solution, including mechanisms and methodologies for each. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must provide, implement, and maintain the State approved services in the context of service oriented architecture (SOA) for the DMA solution, including mechanisms and methodologies for each. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must provide, implement, and maintain a State approved services catalogue and services registry that describes the services provided and details the performance (time and quality service levels), functionality (a description of the inputs, outputs and transformation provided by the service), costs (and cost model), and delivery model (how the service is provided). IV.O.1 Operations - Business Information and Must support the in the alignment of the DMA with the MITA Framework and its
Technical Architecture - General capability/maturity model, CMS Seven Standards and Conditions, industry standards, and other nationally recognized standards for information and technology. IV.O.1 Operations Phase - Business Information and Technical Architecture - General Must ensure that the DMA solution meets the requirements of this RFP, and all applicable State and Federal laws, rules and regulations, including Medicaid confidentiality, and HIPAA, American Recovery and Reinvestment Act (ARRA), Patient Protection and Affordable Care Act (PPACA) privacy and security requirements. IV.O.1 Operations - Business Information and Technical Architecture - General Must demonstrate high levels of capability/maturity with respect to service orientation, interoperability, and data exchange. IV.O.1 Operations - 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
resourcing, quality and contingency aspects. IV.O.2 Operations Phase - Business Information and Technical Architecture - Data Management Must perform data management processes, activities, and that include managing all DMA data, data standards, metadata, data semantics, data harmonization, data ownership and management, interoperability, security & privacy, access methods, data integrity, data quality, and performance standards according to the Data Management Plan. IV.O.2 Operations Phase - Business Information and Technical Architecture - Data Management Must verify the accuracy and timeliness of reported data. IV.O.2 Operations Phase - Information and Technical Architecture - Data Management Must screen the data for completeness, logicalness, and consistency. IV.O.2 Operations Phase - Business Information and Technical Architecture - Data Management Must collect information in standardized formats to the extent feasible and appropriate. IV.O.2 Operations Phase - Business Information and Technical Architecture - Data Management Must implement controls to maintain information integrity. These controls must be in place at all appropriate points of processing. The controls must be tested in periodic audits using a methodology to be developed jointly by the State and the Contractor. IV.O.3 Operations Phase - Business Information and Technical Architecture - Data Governance Must provide, implement, and maintain a State approved Data Governance Plan that includes approach, strategy, methodology, process, tools, resourcing, quality and contingency aspects.
IV.O.3 Operations Phase - Business Information and Technical Architecture - Data Governance Must participate and support the State in DMA governance, stewardship, and data management processes according to the Data Governance Plan. IV.O.4 Operations - Business Information and Technical Architecture - Master Data Management Must provide, implement, and maintain a State approved Master Data Management Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. 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 - 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 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 approved data integration processes (e.g., ETL, ELT). IV.O.6 Operations - 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 - 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 - Business Information and Must support data semantics, data harmonization strategies, ownership, compliance,
Technical Architecture - Data Sharing 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.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must provide, implement, and maintain middleware (e.g., ESB/interface/integration engine) that streamlines the building, testing, and deploying of new and/or modified data exchanges. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must support the State in the adoption of national mechanisms used for data sharing (i.e., data hubs, repositories, and registries). IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must communicate with the State over a secure virtual private network (VPN) as needed. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must transmit and receive data in compliance with all applicable Federal (including but not limited to HIPAA), and State standards and mandates, both currently and in the future. IV.O.7 Operations Phase - Business Information and Technical Architecture - Data Sharing Must provide a flexible framework that allows the import and export of data industry standard file transmission protocols. IV.O.7 Operations - Business Information and Technical Architecture - Data Sharing Must support open standards and industry standard protocols, such as Secure File Transfer (SFTP), SOAP over HTTPS and JMS/MO messages. IV.O.8 Operations Phase - Business Information and Must work with the State and the State trading partners to identify
Reporting and Analytics Tools and Methods 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 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 Must provide, implement, and maintain reporting and analytic
Technical Architecture - Reporting and Analytics Tools and Methods 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 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 - Business Information and Must provide, implement, and maintain reporting and analytic
Technical Architecture - Reporting and Analytics Tools and Methods 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 - 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 - 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 - 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 Must provide the capability to track and report rule usage, exception
IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must provide a continuously available electronic mail communication link (email system) to facilitate communication with the State. This email system must be capable of attaching and sending documents created using software compatible with the State's installed version of Microsoft Office and any subsequent upgrades as adopted. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must have in written systems policies and procedures that document all manual and automated processes for its information systems, including the safeguarding of all its information. IV.O.14 Operations - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must ensure that the systems and processes within its span of control associated with its data exchanges with the are available and operational according to specifications and the data exchange schedule. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must respond in writing within a maximum of five (5) calendar days of notification from the State of a system issue. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must resolve the system or provide a requirements analysis and specifications document within a maximum of fifteen (15) calendar days. 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.
software development firm (SDF), or a third party authorized to support the information system component. IV.O.14 Operations Phase - Business Information and Technical Architecture - DMA Infrastructure and Solution Lifecycle Management Must provide, implement, maintain, and be continually ready to implement, a contingency plan to protect the availability, integrity, and security of data during unexpected failures or disasters (either natural or man-made), to continue essential application or information system functions during or immediately following the failure or disaster. V.A Turnover – Phase Overview Must support to the best of the Contractor’s abilities the orderly turnover and transition of all operations to the State’s designated successor. 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 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.C Turnover – Project Management and Systems Development Lifecycle Must prepare and submit the turnover schedule, within a maximum of sixty (60) days after being informed by the State that the Turnover phase is to begin, in cooperation with the successor addressing all turnover activities until the successful transition of operations. V.C Turnover – Project Management and Systems Development Lifecycle Must develop and submit for review and approval a turnover requirements Document; defining roles, responsibilities, and requirements for the State and/or successor Contractor to complete a successful turnover process. V.C Turnover – Project Management and Systems Development Lifecycle Must attend and collaborate joint turnover management meetings with the State and or successor Contractor. V.C Turnover – Project Management and Systems Development Lifecycle Must work with the State and or successor to integrate turnover work plans with dependencies and dates.
V.C Turnover – Project Management and Systems Development Lifecycle Must include in the weekly status reporting a list of outstanding contractual items along with a plan for completing these items. V.C Turnover – Project Management and Systems Development Lifecycle Must include in the weekly status reporting a list, for approval by the State, of outstanding items to be transitioned to the State or successor. V.D.1 Turnover – Performance and Status Reporting Must submit all turnover items on the turnover inventory list in accordance with the turnover work plan. 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, instructions, and procedures and of the quality of the provided examples submitted with the proposal. V.E Turnover – Close-Out Deliverables Must perform work and submit deliverables for State or designated agent review and approval in accordance with the approved frequency as identified in the deliverable catalog. V.E Turnover – Deliverables Must allow sufficient time to review and approve each deliverable by scaling to the size and complexity of the deliverable. V.E Turnover – Deliverables Must conduct deliverable review sessions prior to submission to the State or designated agent. V.E Turnover – Close-Out Deliverables Must complete all deliverables up to and including approval prior to turning operations of the solution over to the State or prospective Contractor. V.E Turnover – Deliverables Must provide documentation of all necessary resource requirements including hardware and software requirements for successful turnover. V.F Turnover – Quality Assurance and Monitoring Must update the Operations Quality Assurance Plan for turnover procedures and deliver to the for approval. V.F Turnover – Quality Assurance and Monitoring Must validate that the Quality Assurance Plan or series of plans for turnover activities has been executed accurately.
V.F Turnover – Quality Assurance and Monitoring Must manage, perform and monitor the remaining Quality Assurance steps of the plan. V.F Turnover – Quality Assurance and Monitoring Must maintain the process of recording and addressing corrective and preventive actions through the turnover phase. V.F Turnover – Quality Assurance and Monitoring Must identify and track defects and service level deficiencies. 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 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 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 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 MITA Coordinator. V.G Turnover – Change Management Must submit all change requests and analysis results to the 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.
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. V.J Turnover – Cooperation with Successor Must collaborate with the successor to develop a customized methodology to work with the new technology and infrastructure implemented. V.J Turnover – Cooperation with Successor Must review the system’s stability and performance, system recovery, operations and threshold compliance with the successor. V.J Turnover – Cooperation with Successor Must provide modifications and corrective actions taken to add to or resolve any deficiencies or omissions discovered in the system. V.J Turnover – Cooperation with Successor Must provide technical support (e.g. system-related problems, routine maintenance and error resolution, database administration functions, software distribution), as needed during transition. V.J Turnover – Cooperation with Successor Must provide knowledge transfer/onsite training to the successor. V.J Turnover – Cooperation with Successor Must plan, facilitate and document turnover discussions among stakeholders. V.K Turnover – Contract Closeout Must complete all activities to the State’s satisfaction within the State approved turnover plan, turnover inventory, and work plan.
V.K Turnover – Contract Closeout Must transfer all State owned property to the State or State’s designee in an orderly manner. V.K Turnover – Contract Closeout Must transition all leases, licenses, etc. for materials or services to the State or designee. (e.g. toll free phone lines, post office boxes, web addresses, hardware, software, facilities, etc.). The State has sole discretion on whether a material or service is not necessary for transfer. V.K Turnover – Contract Closeout Must provide all finalized and production ready documentation organized and cataloged (e.g. User Manual, Business Operating Procedures, Technical Operating Procedures, Training Guide). V.K Turnover – Contract Closeout Must provide all system data to the State or successor (e.g. files, records, transactions). V.K Turnover – Contract Closeout Must complete all work required of the Contractor during the Operations phase of the contract unless otherwise agreed to by the State for turnover to the State or successor. V.K Turnover – Contract Closeout Must implement all maintenance, and started changes in accordance with the agreed upon system release schedule defined in the Operations Change Management Phase. V.K Turnover – Contract Closeout Must resolve malfunctions/defects which existed in the system prior to turnover or which were caused by lack of support at turnover in accordance with the agreed upon response and resolution schedule. V.K Turnover – Contract Closeout Must permanently destroy all confidential data and protected