MN DHS Systems RFI     Table of Contents Summary ....................................................................................................................................................... 2  Purpose ......................................................................................................................................................... 2  Conditions of RFI ........................................................................................................................................... 4  Deadline for Submission of RFI ..................................................................................................................... 4  Questions about this RFI ............................................................................................................................... 5  Notice of Limitations on Available Resources ............................................................................................... 5  RFI Submission Instruction ............................................................................................................................ 5  Response Format .......................................................................................................................................... 6  Information Requested ................................................................................................................................. 6  General Questions .................................................................................................................................... 6  Desired Functional Components ............................................................................................................... 7  Response Definition .............................................................................................................................. 7  Technical Information ................................................................................................................................. 12  Performance requirements and standards ............................................................................................. 12  Baseline license options .......................................................................................................................... 12  Optional technical support services  ....................................................................................................... 12  . Architectural Consistency Checklist ........................................................................................................ 13  System Design ......................................................................................................................................... 14  Appendices .................................................................................................................................................. 15  Appendix A: Minnesota Client Benefit Programs (Informational) .......................................................... 15  Minnesota Health Care Programs ....................................................................................................... 15  Health Insurance Exchange ................................................................................................................. 16  Economic Support ............................................................................................................................... 16  Child Safety and Permanency and Adult Protection ........................................................................... 20  Child Support ...................................................................................................................................... 23  CDCS ‐ Consumer Directed Community Supports .............................................................................. 23  MMIS ................................................................................................................................................... 24  SMI – Shared Master Index ................................................................................................................. 24  Appendix B: Technical Checklist (Optional) ............................................................................................ 25  Page 1      August 1, 2011      MN DHS Systems RFI       Summary The Minnesota Department of Human Services (DHS) is interested in an integrated service delivery and  payment system to support all DHS programs.  As a first step in determining direction the Commissioner  is issuing a Request for Information on available commecial‐off‐the‐shelf software to provide a  framework for an enterprise‐wide system.  Interested responders are asked to supply information in  writing by August 29, 2011.    The contact person for questions and further information is Jennifer Trombley.   Jennifer.Trombley@state.mn.us  Department of Human Services  PO Box 64998  St. Paul, MN 55164‐0998    Purpose Minnesota (MN) Department of Human Services (DHS) is issuing this Request for Information (RFI) related to the need to replace and integrate existing software applications that automate various functions throughout the Department. The goal of the Department is to implement an enterprise level product that will support automation of the many functions of the DHS enterprise using a single set of current technologies that allow us to be more agile in responding to the changing needs of our clients and partners, while continuing to meet Federal and legislative requirements. The desired goals of the new system will be to: • • • • • • Make it easier for an individual to navigate what has historically been a fragmented and duplicative system Increase the speed and accuracy of desired and mandated changes Allow portability across platforms Allow the externalizing of rules Support a highly modularized approach to development and implementation Support interoperability in a service oriented architecture • Reduce unnecessary administrative burdens and redirect resources to services that are essential to achieving better outcomes at lower cost. This is especially urgent at a time when State, local, • • • • and tribal governments face large budget shortfalls. Facilitate coordination across DHS divisions and across the agencies with which we work Realize efficiency, promote program integrity, and improve program outcomes Serve the full range of human need more effectively and efficiently Support Outcome measurement Minnesota (MN) Department of Human Services (DHS) is seeking information about commercial off-theshelf (COTS) software to support case management, eligibility determination, benefit payment, provider payment, health care enrollment, Child Support Collections and payments functions, and all of the related functions involved in the delivery of these and other programs supervised by the Department. DHS seeks Page 2      August 1, 2011      MN DHS Systems RFI     a COTS (commercial off-the-shelf) product that can be used "as-is": designed to be easily installed and to interoperate with existing system components. This RFI is the first step in the possible development and implementation of a comprehensive, fully integrated human services delivery management system. Through this RFI, the State seeks information about any COTS software packages, composed of proven configurable application modules and domain modules (enterprise framework) and/or open source modules that would need minimal customization to support Human Services delivery functions. Such a solution could reduce the time, risk, and cost of delivering a system that provides support for both the current and future automation needs of DHS Chemical and Mental Health Services, Children and Family Services , Continuing Care, State Operated Services, MN Sex Offender Program and Health Care Administrations, as well as the 87 county departments of social services, MN Tribes, health care organizations and other entities who require automated support to deliver services to the clients of DHS. The Appendices of this document offer some detail about the programs administered by DHS and about the people we serve through those programs, as well as about existing automated systems. We are interested in an integrated human services delivery system that could cross program and organizational boundaries to provide a client-centric, outcome-based, holistic and integrated service delivery approach to managing the services we deliver. Responders should be able to offer support for and discuss at least two of the following major program areas: • • • • • • • Children and Adult Services (Child Welfare, Vulnerable Adults, Home and Community Based Services) Child Support Health Care Eligibility Determination Chemical and Mental Health Services Health Care Provider Payment Economic Support Programs (Food Support, Child Care, Cash) Health Insurance Exchange We are interested in products that have: o o o o o o o o o o o already applied for and/or achieved Federal certification (e.g. SACWIS, FAMIS, MMIS) in other jurisdictions been implemented in a jurisdiction with characteristics similar to those of the State of Minnesota been upgraded for ICD-10 demonstrable SOA compliance adherence to the MITA architecture a consistent framework for all components a defined business and technical architecture, externalized business rules or a rules engine potential for use with hand-held devices the potential for availability through the cloud demonstrable features complying with the HITECH Act DHS is interested in hearing about a given product from the product vendor, and is interested in any offered demonstration of a given product only once. Product vendors may include Service Integrators (SI) at their discretion. Page 3      August 1, 2011      MN DHS Systems RFI     Vendors are encouraged to respond in writing and, if the vendor would be willing to show their product, to suggest an appropriate length of time for a demonstration of the major systems components offered. MN DHS at its discretion may request a demonstration of a vendor’s offering. The State has excluded Government Transfer Systems and new system development from this RFI. Conditions of RFI The issuance of this RFI constitutes exclusively an invitation to submit information to the Department. Any in-formation submitted as provided herein shall not be construed as an official and customary Request for Proposal, Request for Bid, or an offer for a future binding contract. Nothing in this RFI should be construed to imply an obligation of any kind by the Department. At its sole and absolute discretion, the Department may decide to further pursue one or more solutions by methods including, but not limited to: solicit further information from one or more potential vendors; issue a Request for Proposals or Request for Bid as the Department shall deem appropriate; solicit information from non-responding vendors with or without reference to this RFI; or take no action at all. The Department reserves the right to evaluate, use and determine, in its sole and absolute discretion, whether any aspect of the Responder’s information satisfies the purpose and intent of the RFI. Under no circumstances shall the Department have any liability to any Respondent for any cost incurred in connection with this RFI or otherwise. The Department is not obligated to respond to any Respondent’s information nor is it legally bound in any manner whatsoever by the submission of information. The Department may, upon request, make all information in the responses available to the public shortly after the deadline for submitting responses. A responder should not submit information that it does not want to become public. Responder agrees as a condition of submitting information that the Department will not be held liable or accountable for any loss or damage that may result from the Department’s public disclosure of information contained in a response. The Department reserves the right to accept or reject late responses at its sole discretion. The Department reserves the right to cancel or amend this RFI at any time, either in part or in its entirety, and will notify all known RFI Responders accordingly. The Department further reserves the right to extend the RFI due date. If a Responder needs an extension of time to prepare their submission, a written or e-mail request should be submitted no later than seven (7) days prior to the due date of this RFI and addressed to contact information in Section 5. The Department reserves the right to extend the submission deadline at the sole discretion of the Department and not at the mere request of the Responder. The Responder will be notified of the Department’s decision by letter or e-mail. Deadline for Submission of RFI The Department prefers to receive the response no later than August 29 by 4:00PM. Please send responses to: Minnesota Department of Human Services PO Box 64998  St. Paul, MN 55164-0998 Attention: Jennifer Trombley Page 4      August 1, 2011      MN DHS Systems RFI     Responders are encouraged to submit one original paper copy of their response, together with an electronic copy (MS Word or PDF) on computer disk. Responses should be prepared in such a way as to provide a straightforward, concise explanation of the vendor's product. Published materials to support your response to the RFI may be included with your response. Demonstration or presentation of your proposed solution may be requested. If demonstration media of your proposed product is available, submit them with your response. Questions about this RFI Questions regarding this RFI may be submitted by electronic mail or writing to the contact listed below, preferably by the questions due date. Minnesota Department of Human Services PO Box 64998  St. Paul, MN 55164-0998 Attention: Jennifer Trombley The Department reserves the right to add, change, or delete any provision or statement in the RFI at any time prior to the requested due date. If it becomes necessary to revise any part of the RFI, addenda to the RFI will be provided to all known Responders who received a copy of the RFI. Addenda will be posted on the Department’s website at http://www.dhs.state.mn.us/id_000102 Notice of Limitations on Available Resources As a consequence of the current economic environment in Minnesota and the resulting fiscal/budgetary constraints,the Department of Human Services has limits on available resources. • • While no funds have been appropriated or committed for the Project, we anticipate that initial funding may become available. It is unknown if or when such funds will be available. Limitations exist on resources for additional staffing, if any, required for utilization, operation or maintenance of any technology that may be deployed by the Department. RFI Submission Instruction Target Dates KEY ACTIVITY DATE Request for Information Issued August 1, 2011  Written Questions Due August 15, 2011  Agency Responses by August 22, 2011  Responses Due August 29, 2011  Presentations or demonstrations by Responders (if applicable) September/October, 2011  Page 5      August 1, 2011      MN DHS Systems RFI       Response Format Responders to this RFI are encouraged to include the following information:    Description of the Responding Organization:   o o Brief history of the organization and development of the product  Experience and examples of product deployment in environments similar to that described in  this RFI (Appendix A);  including experience with other large organizations, especially including  other states or major local governments   Information Requested The Responder is urged to respond to the information requested below and in “Appendix B – Technical  Checklist.” The Department may make all information in the responses available to the public shortly after the deadline for submitting responses. A responder should not submit information that it does not want to become public. General Questions What major components does your product support? Is support available for components that, in Minnesota, might not be part of the Department of Human Services but would support programs that serve our clients? Have you defined a complete business architecture that best matches your product’s approach to service delivery? What specific steps have been taken to insure simplicity in the architecture and design of the product? How has your product conformed to the MITA architecture and requirements? What is your approach to support of such changes as case-banking vs. case worker for a case, regionalization, or kiosk service delivery? Are any interfaces standard with the product? (e.g., SSA, CS Interstate, Department of Labor) How does your product integrate on- and off-line processing, e.g. using tablets, mobile phones, standalone devices? Has your product been used in a multi-tenancy implementation? Has the product vendor offered any/all functions as cloud services? How does the product vendor approach customer enhancement requests? Bug fixes? Prioritization of enhancement requests and bug fixes? What form(s) of customer relationship does the product vendor offer? Do customers sit on Advisory Boards? Do you support customer forums – such as periodic conferences or surveys? Other? Page 6      August 1, 2011      MN DHS Systems RFI     How does the product vendor respond to federal policy changes? To State policy changes? (assuming not all situations can be handled via customized business rules management) Does the product use or allow use of any open-source technology? If so, what? Will the product vendor require loyalty fee after solution implementation? If so, how much and how frequently? Is the solution dependant on other third party products? If so, will the MN Department of Human Services be obligated to pay for these products? If the final solution is amalgamation of multiple products, who will be responsible for identifying and resolving issues? How is the product/solution upgraded when the next version emerges (additional licensing fees, new product agreement, etc.)? Describe training approaches and frequencies. Desired Functional Components If responding in writing, responders are encouraged to provide a short narrative for each functional component available in their software. MN DHS is interested in how the COTS component might meet our needs, which we have briefly described in this section. A narrative presentation or oral (on-site or online) demonstration is encouraged. The Vendor should also provide a list of its certified Software Integration (SI) partners who have implemented the Vendor’s software product successfully, specifically including any public sector and human services implementations. Response Definition Note: If responding specifically to any functionality definition, vendors are encouraged to use the following to help us understand the state of the functionality and to help us understand any planned direction for the product: Included in base product (I). The business function is included in the base product(s) and is fully demonstrable. Configuration required (CoR). The business function can be met by configuring the base product through use of a base product tool set(s). The Vendor may propose using alternate third party software to meet the business function. Planned product release (PR) The business function is not included in the base product, but is planned for incorporation in a scheduled release of the base product. Customization required (CuR) The business function requires customized changes to the base product or software development apart from the base product’s design, process or structure. Not in product scope (N) The business function is not included in the base product, the base product cannot be configured to meet the required functionality. MN DHS is interested in including the following cross-program functions: Page 7      August 1, 2011      MN DHS Systems RFI     • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Online Screening and Application Client identity management and electronic signatures, with potential integration into the existing identity management architecture and tool suite User authentication and authorization (including clients) (Note: MN DHS has an existing identity management strategy and may be interested in using it.) Referral support both within the agency and to outside resources Intake Processing: Economic Support Programs, Health Care, Home and Community-Based Services (HCBS), Child and adult welfare/protection, foster care (FC), Child Support (CS) and other DHS programs, e.g. Chemical and Mental Health Verification support, including online verification interfaces for the Social Security Administration (SSA), MN Department of Employment and Economic Development (DEED) and many other organizations Assessment (child welfare, vulnerable adult, HCBS, etc.) Service Planning Service Authorization Eligibility Determination for Child Care (CC), Food Support (FS), Minnesota Family Investment Program (MFIP), other cash programs, health care (HC), HCBS. Benefit Issuance Payment Processing Payment issuance (e.g. child support) Provider claim processing and payment o Pharmacy Point-of-Sale claims processing Client, Partner, and Provider communication (mail, email, SMS, phone) Document creation (court orders, client notices, provider communications, etc.) Electronic Document Management Service Delivery Management Benefit Recovery Case Management (including transfers) Provider Payment Service Prior Authorization Provider Management Sanction management Change reporting Redetermination/recertification Self-service, e.g. self-registration (authentication/authorization), integrated voice response (IVR), call center, and online and eForms support, client portal (for info exchange between client & DHS), account management, information updates, Client representative/navigator support Workflow support (alerts, case notes, ticklers, etc.) and prioritization Outcome Measurement Cross-program reporting (reporting in general) Information for decision support at an enterprise level Ask-once/enter-once philosophy for data Support for retention policies to automate data purging Financial/accounting management Fraud detection/prevention Licensing (e.g. child care, foster care) Page 8      August 1, 2011      MN DHS Systems RFI     • • • • • Quality Assurance controls Healthcare premium processing Claims/recoupment processing (as opposed to paying medical claims) for overpayment of benefits Automated trend analysis based on data held within the COTS Ability to handle counties, county clusters, regionalization of counties, tribes, partners, voluntary agencies – recognizing the difference between “servicing” and “financially responsible” with all the appropriate security The list of functions we want to support includes but is not limited to • • • • • • • • • • • Reception   o Registration and Demographics   o Notification to worker that client is waiting   Client/representative self‐service screening and registration and account management  Calendaring   o Schedule appointments   o Maintain calendars   o Captures and displays work lists for staff   o Possible integration with County calendaring systems(s)  Client Search   o Create client/ID Assignment   o Find existing clients   o Query with multiple search criteria   Relationship management   o Within a case   o Among multiple cases   o With partners (e.g. county courts, healthcare plan providers, healthcare providers)  Screening /Intake  o Screening tool for workers or self‐service customers or non‐profit agents to determine  potential eligibility for clients   Worker Notification (Alerts/Ticklers)   o Notify one or many staff members of agency, policy, or case‐related information   Security   o Authentication   o Authorization by roles   o Administration assigns roles and permissions to users   o Assign contact information for counties   Narratives  and case notes  o Create automatically   o Create manually   o Query   Waiting Lists   o Create   o Update   o Query   Electronic Forms and Notices Management   o Automated completion of forms and notices using system data.  Page 9      August 1, 2011      MN DHS Systems RFI     Forms and notices available on demand   Query historical forms and notices with multiple search criteria   Interview Process (Application, Change, Review)   o Display interview questions by program area   o Display previous answers to interview questions   o Intelligent scripting (including/excluding questions based on responses to previous  questions)   o Single point of data entry with data made available across programs   Administrative Functionality   o Define and maintain date‐driven business rules    o Define and maintain business workflows   o Mass changes   Case Disposition   o Determine/Redetermine eligibility based on program specific rules   o Linked display of policy reason(s) for ineligibility   o Case Terminations   o Case Re‐opening   Case Maintenance   o Notification to workers when change in client’s information  across the enterprise  Case Transfers   o Worker‐to‐Worker   o County‐to‐County   o State‐to‐county  o Mass reassignments   o Program Category‐to‐Program Category   Issuance of Benefits   o Automatic issuances   o Manual issuances   Queries/Ad‐Hoc Reporting   o Create reports and show results   Supervisor Functionality   o Workload Management   o Administrative functionality for calendars, tasks, and workloads for multiple workers   Provider Functionality   o Portal for providers and/or external stakeholders   Financials (Client Payment, Auditing, Control Reporting)   o Audits financial transactions and separation of duties   o Maintains and displays confirmation of benefit and/or payments delivery   o Maintains and displays benefit and/or payment status   o Maintains and displays historical records of benefits and/or payments  issues for all  program areas   Assessments and Service Plans   o Structured intake tool   o Service plans   o Assessment tools  Structured Decision Making   Documentation   o Business Process Flows   o o • • • • • • • • • • • • Page 10      August 1, 2011      MN DHS Systems RFI     User Guides   Linked Access to Rules and Policy   Technical – County, DHS partner,  and user issues  o Counties may invoke services of case management functionality (Integration options  with county‐based systems) e.g. Person Search functionality exposed as externally  available web services.  o Web pages will be US Section 508 and American Disabilities Act (ADA) compliant  Support for major business process flows   Support for tracking and managing outcomes in human services, especially for individuals and  families participating in multiple programs  Tools to facilitate risk and safety assessments for families, adults , and children  MITA functions as identified in the architecture  o o • • • • •   Any County Considerations for Case Management  • • • • • Consider their need to purchase any products/tools to insure  integrated use of COTS product  for Human Services delivery   Considerations for workstations needed for staff  Consideration for internet bandwidth   Consideration for integration with county‐based systems  Consideration for support of multiple devices and off‐line use of some/all functions    Page 11      August 1, 2011      MN DHS Systems RFI     Technical Information DHS is interested in information about a detailed strategy for establishing the necessary hardware, system and network configuration for the installation of the base product software. DHS is interested in the data design and architecture, supported database product(s), data synchronization, approaches to conversion, approach to data for analytics, and approach to master data management. DHS is interested in your approach to rules management, the use of a rules engine, dated rules, dated data and how the product supports flexibility, scalability and ease of maintenance of complex rules. DHS is interested in a Service Oriented Architecture which will make integration with existing functionality and enhancements and extensions easier. Performance requirements and standards Performance requirements and standards must be included in our strategy for technical performance. We are interested in the approach taken by the product. Baseline license options Please describe available licensing option, inclusive of all processing platforms and environments licensing options include but are not limited to the following: 1. Single enterprise license (including any price reduction thresholds when upgrading from any  other license option to an enterprise license)  2. Platform‐based (e.g., server, CPUs, megahertz)  3. Utilization phases (e.g., limited configuration, development, system testing, user acceptance  testing (UAT), pilot, rollout, user training, production)  4. Major system component, functional module, or tool  5. Progressive or tiered user seat acquisition by ranges (e.g., 1‐500, 501‐1000, etc.)  6. Active users  7. Role‐based users  8. Named users  9. Floating seats  Optional technical support services If the product vendor offers support services, please outline your approach to the following: 1. Training for Department technical and business staff.  2. Consultation for training for end users, Department or Service Integration (SI) vendor training  staff.  3. Assistance to DHS in reviewing the system analysis and design deliverables for SI vendor(s).  4. Assistance to DHS and SI vendor(s) in the use of configuration tools for the package software.  5. Consultation with the Department and SI vendor(s) in the planning for and implementation of  legacy system replacement, integration and interfaces. This will include assistance in the use of  any data interface, synchronization and conversion tools provided as part of the Vendor’s base  product solution, and the sequencing of conversion activities.  6. Communication, cooperation, collaboration with and support of any and all SI vendor(s) selected  by the State for subsequent projects, or assistance to the State if the State chooses to act as its  own integrator, for the duration of the contract.  Page 12      August 1, 2011      MN DHS Systems RFI     7. System maintenance services.  8. Help Desk.  9. Release support planning and implementation services.  10. Upgrade services. Please discuss the criteria for what the Vendor considers to be a new product  offering vs. a software upgrade, as well as responsibilities for and experiences with problems  occurring during integration phase, and which cannot be resolved by the integrator.  Discuss/outline the history of the Vendor’s product releases, including frequency and examples,  as well as your strategy for future technical upgrades and function‐based releases. Architectural Consistency Checklist 1. Scalability: a. Provide detailed diagrams with complementing narrative describing proposed technical  solution.  b. Describe the maximum capacity of the proposed technical solution upon which performance  begins to degrade, including the results of any formal testing (e.g. Performance, Load, Stress).  c. Describe the largest production implementation by an existing customer that uses the  proposed technical solution.  d. Describe the testing methodology used in the development of the proposed technical  solution(E.g. Performance, Load, Stress, Security).  e. Describe the ability of the proposed solution to scale both horizontally and vertically.  f. Describe how the proposed solution can be scaled to manage pilot, rollout and growth rate  requirements.  2. Adaptability: a. Describe the overall architectural approach used to design the proposed solution (e.g. Service  Oriented, 3/N Tier, Composite Application).  b. Describe how the architectural approach and the technologies used enable solution  adaptability.  c. Describe the technology roadmap for the proposed solution.  d. Describe how the solution will be capable of adapting to meet changing business  requirements.  3. Secureability: a. Describe how the solution can be deployed to provide layered access controls. b. Describe how the solution can be deployed to accommodate both an integrated or externalized identity access and management solution. c. Describe the ability of the proposed solution to meet Federal and State regulatory requirements. 4. Availability: a. Describe the technologies and approach used to meet and/or exceed availability requirements. b. Describe an acceptable backup and recovery approach to meet and/or exceed availability requirements Page 13      August 1, 2011      MN DHS Systems RFI     5. Manageability: a. Describe the versioning and patch management process for the proposed solution.  b. Describe approaches that could be implemented to provide overall performance monitoring  for the proposed solution.  c. Describe the Quality Assurance (QA) measures that have been taken in the design,  implementation and maintenance with respect to the proposed solution.  d. Describe the management and monitoring tools that are supported by the proposed  technologies.  6. Interoperability: a. Describe the programming language(s) and development framework(s) that are used in the  design and implementation of the proposed solution.  b. Describe any open (industry and/or de facto) standards used to ensure interoperability of this  solution within a heterogeneous environment.  c. Describe the available options, along with the preferred approach, for integrating the  proposed solution with other intra/inter agency systems.  d. Describe the flexibility of this solution to meet future integration needs.  e. Describe how the solution meets accessibility (i.e. W3C and/or 508) requirements.  7. Enterprise: a. Describe how your product solution can leverage Shared Services.  b. Describe how consolidation of services and infrastructure can be accomplished.  System Design Describe whether/ how your product:  • • • • • • • • •     Provides an industry open standard development and runtime environment supported by a flexible application, business, and technical architecture (describe the architectures) Provides a Service Oriented Architecture (SOA) as validated and certified by a certification group Uses an Enterprise JavaBeans (EJB)/J2EE architecture to enable horizontal and vertical scalability Supports a range of Relational Database Management Systems, operating systems and middleware products to provide platform independence Supports many deployment models, from simple to complex, and delivers the scalability required by social enterprises Supports off-line use and define any supported devices Incorporates the Medicaid Information Technology Architecture (MITA) and standards and expands MITA to other service delivery areas. Supports the addition of new programs without extensive coding to support state‐only  programs and new state initiatives  Provides regular maintenance releases for bug fixes and for upgrades and enhancements   Page 14      August 1, 2011      MN DHS Systems RFI     Appendices Appendix A: Minnesota Client Benefit Programs (Informational) In this section we have included information about our programs and enrollees so that interested  vendors have some detail about MN DHS and our clients.  The information is neither comprehensive nor  guaranteed to be accurate but is provided as background.  Minnesota Health Care Programs Enrollment Eligibility Group  Jan 2011   1. Low‐income families (§1931) who would be eligible under former Aid to Families  105,606 with Dependent Children (AFDC) program  1a. Low‐income families who would be eligible under former AFDC program  (State‐funded eligibility for  Non‐qualified noncitizens)    2. Pregnant women  3. Auto Newborns   4. Infants < 2  983 5. Children 2 – 5  6. Children 6 – 18  7. Transitional Medical Assistance    7a. Transitional Medical Assistance  (State‐funded eligibility for Non‐qualified noncitizen parents)  8. Emergency Medical Assistance (EMA)   9. Refugee Medical Assistance  10. Children receiving IV‐E foster care benefits  11. Children receiving IV‐E adoption assistance   12. Children 19, 20  13. Medically needy families and children  13a. Medically needy families and children  (State‐funded eligibility for Non‐qualified noncitizen parents)  14. Individuals who need treatment for breast or cervical cancer  14a. Individuals who need treatment for breast or cervical cancer  (State‐funded eligibility for Non‐qualified noncitizens)  15. Targeted Low Income Children – Infants under 2 with income between 275%  and 280%  Minnesota’s CHIP State Plan population  16. Children receiving non‐IV‐E adoption assistance  17. Prenatal care for noncitizen pregnant women without other health insurance  CHIP state plan population  18. Adults without Children   72,273 164,751 15,358 Page 15      August 1, 2011  16,954 29,369 29,078 136 1,941 456 2,186 5,487 10,808 2,547 20 457 4 39 2,050 2,119 50,802     MN DHS Systems RFI     18a. Adults without Children   (State‐funded eligibility for Non‐qualified noncitizens)  ??? 19. Auto Newborns & Infants < 2  19a. Infants < 2  20. Children 2 – 21  20a. Children 2 – 21  21. Pregnant women  21a. Pregnant women  22. Parents and Relative  Caretakers  22a. Parents and Relative  Caretakers  23. MN Family Planning Program Section 1115 Demonstration Project – Individuals  between ages 15‐50  in  need of family planning services, and not enrolled in any  other Minnesota Health Care Program  2,686 0 44,167 285 1,062 31 37,274 606 4,363 Presumptive Eligibility 17,173 ongoing 830 24. State‐funded MA (Program IM)  for individuals ineligible for federally‐funded  MA due to residence in an Institution of Mental Diseases (IMD)  25. State‐funded MA for individuals receiving services at the Center for Victims of  Torture (CVT)  124 Health Insurance Exchange Minnesota DHS is interested in whether the vendor product supports a Health Insurance Exchange (HIE) or interacts with an existing HIE, or is planning an integration with a particular Exchange. Economic Support The Minnesota Family Investment Program (MFIP) The Minnesota Family Investment Program (MFIP) is the state’s welfare reform program for low-income families with children. MFIP helps families move to work and focuses on helping families become self-sufficient. It includes both cash and food assistance. When most families first apply for cash assistance, they will participate in the Diversionary Work Program  (DWP). Parents go immediately to work rather than receive welfare but may receive help with shelter and utilities and some living expenses for up to four months. Some families may be referred to MFIP when they first apply for assistance or after they receive DWP. MFIP helps families transition to economic stability. Parents are expected to work and are supported in working. Most families can get cash assistance for only 60 months. Diversionary Work Program and Work Benefit Program  DWP helps low-income Minnesota families find work. The goal of DWP is to help parents immediately go to work rather than go on welfare. Parents are expected to sign an employment plan before their family is approved for DWP. After families have an employment plan, they can receive financial assistance to meet their basic needs for up to four months and get other supports, such as food support and child and health care assistance. When most families first apply for cash assistance, they will participate in DWP. Some families may be referred to the Minnesota Family Investment Program.  DWP began in July 2004. The Work Benefit Program, implemented in 2009, is available to families who have left MFIP or DWP in the last 30 days and have at least one caregiver working a required number of hours. It provides a monthly cash grant incentive. Page 16      August 1, 2011      MN DHS Systems RFI     Minnesota Food Assistance Programs The Food Support [Supplemental Nutrition Assistance Program (SNAP)] program is a federal program that helps Minnesotans with low incomes get the food they need for sound nutrition and well-balanced meals. The program issues electronic food support benefits that can help stretch the household food budget. The Minnesota Food Assistance Program (MFAP) was created by the Minnesota Legislature in response to federal law changes which made certain noncitizens ineligible for federally funded Food Support. MFAP uses state funds to replace the benefits lost when federal Food Support eligibility ends. MFAP is only available to noncitizens 50 years of age or older. People apply for MFAP as they would for Food Support at county offices.  Refugee Assistance  Most of the refugees who are resettled in Minnesota are members of families with minor children who qualify for the same cash and medical assistance programs available to other low-income state residents through county human service agencies. They are predominately two-parent families. Refugee Cash Assistance (RCA) and Refugee Medical Assistance (RMA) are provided to needy refugees who do not have minor children in the home. These benefits, which are federally funded, are available for the first eight months after a refugee arrives in the country. These benefits are provided through county human service agencies and voluntary resettlement agencies (for refugees in the Twin Cities metro area and Olmsted County.) Services are also provided to assist unaccompanied minors without a responsible adult relative resettle into a foster home placement. The federal government reimburses the state for these services, which are provided until the minors are emancipated or reunited with their parents. Adult Supports  DHSDHS oversees economic assistance programs that provide a safety net for the elderly and people with disabilities. The General Assistance (GA) program provides cash assistance for single, unemployed adults without  children, including people who are elderly, ill, injured or otherwise incapacitated.  Minnesota Supplemental Aid (MSA) is a state-funded supplement for people who receive Supplemental Security Income (SSI). Group Residential Housing (GRH) grants provides income supplements for room, board, and other related housing services for people whose illnesses or disabilities prevent them from living independently. Minnesota’s Child Care Assistance Program (CCAP) can help to make quality child care affordable for income-eligible families. All families will have a copayment based on their gross income and family size. Child Care Assistance is available to: • • •  Families participating in MFIP Families that had an MFIP case close within the last 12 months  Low‐income families that may be eligible for the Basic Sliding Fee program  Page 17      August 1, 2011      MN DHS Systems RFI     CCAP can help families pay child care costs for children up to age 12, and for children with special needs up to age 14. Child care costs may be paid for qualifying families while they go to work, look for work or attend school. To qualify for CCAP, families must comply with child support enforcement if applicable for all children in the family. Care must be provided by a legal child care provider over the age of 18. An annual summary of statistical information about families and children participating in CCAP is available in the Child Care Assistance Program Family Profile.  Family size, family income and participation in authorized activities are considered. The amount of available funding also may be a factor. In some Minnesota counties there is a waiting list for access to day care under the Basic Sliding Fee program.  CCAP has two types of rates that are used to determine the maximum amount for reimbursement to child care providers who serve CCAP families: Current maximum rates Current maximum rates with accreditation/credential differential For additional information on the programs currently supported by our integrated eligibility system (MAXIS/MEC2), see below. Caseloads are recent but changing rapidly. The level of support for eligibility determination varies from fully automated to minimally automated. Program MFIP DWP Work Benefit MSA GA RCA EA EMSA EGA Page 18      Description Cash and food benefits for families Cash benefit for families Cash benefit for families Cash benefit for persons receiving SSI Cash benefit for single, unemployed adults without minor children Cash benefit for refugees without minor children Cash benefit for families in a crisis situation Total Cases Total Persons 35,452 94,123 Federal (TANF) and State 3134 9403 24 months State 1487 5009 None State 28,883 None State 19,053 19141 8 months including the month of arrival in the US Federal 241 253 Time Limit Funding 60 month lifetime limit (with exceptions) Federal (TANF) and State 4 months State varies 1421 4855 2, Cash benefit for MSA person in a crisis situation 1 time per 12 months Cash benefit for persons in a crisis situation 1 time per 12 months State and County, Optional County State and County, Optional County August 1, 2011  See GA cases 55, see MSA cases     MN DHS Systems RFI     GRH IV-E FC FS BSF – Basic Sliding Fee PP MFIP CC (CM) TY TYE MA EMA RMA IMD GAMC QMB SLMB QI NMED Page 19      Room and board payment, and in some cases services payments, for person residing in GRH Payment for child in foster care Food Benefit Child care payment for families not eligible for MFIP or DWP Child care payment for families who had received BSF Child care payment for families eligible for MFIP or DWP Child care payment for families when MFIP or DWP has closed Child care payment for families when TY has ended Medical payment to provider Medical payment to provider Medical payment to provider Medical payment to provider Payments made to CCDSs (Coordinated Care Delivery Systems) Payment of Medicare-related expenses Payment of Medicare-related expenses Payment of Medicare-related expenses Medical payment None State (some County) 17,638 None Federal and State 2084 ABAWD 3-month out of 36-month Federal and State 165,749 317,797 None State (Capped annual allocation) 11.090 20,604 6 months State 37 60 None Federal (Fully funded) 7961 14434 12 months Federal (Fully funded) 3328 5808 None Federal (Fully funded) 159 295 None Federal and State 311,989 582,862 None Federal and State 1520 1634 8 months after arrival in US Federal 237 248 None State 730 None State 45,000 None Federal 67,735 None Federal 16,004 16,497 None Federal 3507 3854 None State August 1, 2011  45,459 68,423     MN DHS Systems RFI     to provider Child Safety and Permanency and Adult Protection The division administers a number of federal funding programs that are important to ensuring safety, permanency and well-being for children, youth and their families. These federal programs, along with state and local funding, support a comprehensive continuum of services from child abuse/neglect prevention through adoption and other permanency supports: Title IV-E Foster Care; Title IV-E Adoption Assistance, Chafee Foster Care Independence Program (CFCIP), Education and Training Vouchers (ETV), Title IV-B,1 Child Welfare Services, Title IV-B,2 Promoting Safe and Stable Families, Child Abuse Prevention and Treatment Act (CAPTA), Community-Based Grants for the Prevention of Child Abuse and Neglect (CBCAP), Children’s Justice Act (CJA), and Title XX Block Grant. Social Service Information System (SSIS) MN currently has a federally required case management system offering functionality for county and tribal social workers supporting child protection, foster care, adoption, children's mental health, and other child welfare programs. The system also supports adult maltreatment reporting, waiver claiming, MMIS billing and other adult services. Approximately 6,000 users including county social workers, fiscal workers, administrative staff, eligibility workers, managers, case aides and DHS staff, use SSIS to track cases involving more than 270,000 individuals annually. SSIS documentation includes Intake, Assessment and Investigation modules for child and adult maltreatment reporting; social services case management; time tracking; service plans; case notes; vendor payments; Medicaid claiming, state outcome reporting and federal AFCARS and CAPTA outcome reporting, case notes, letters, documents and notices. Child Safety and Prevention Programs o 22,312 children were subjects of a family assessment or investigation in response to a report of abuse/neglect in 2009. o Parent Support Outreach Program - Over 3000 children per year and their families receive services through Parent Support Outreach Program, a voluntary, early intervention pilot program operating in 30 counties since 2005. o Protective or supportive services were required or offered to 6,516 families, the outcome in 39 percent of family assessments or investigations. Services most often recommended: mental health/counseling, parenting education, family counseling, chemical dependency services, family support and preservation, foster care, and miscellaneous other services. o Children’s Justice Act - Grants under this program supported training for 177 law enforcement, county attorney and child protection professionals in forensic interviewing and investigation skills. o Children’s Trust Fund – State trust and federal CBCAP funds support grants to 16 communitybased providers, local child abuse prevention councils in 60 counties, and statewide prevention activities through a contract with Prevent Child Abuse Minnesota (PCAMN). o Constituent Services – 1813 consults in 2010 from counties, community members, families and other states. Child Placement and Permanency Programs o 11,699 children/youth were in foster care in 2009. 6,036 children/youth entered and 6,557 children/youth left. Page 20      August 1, 2011      MN DHS Systems RFI     o Family Support and Preservation Services – Family Group Decision Making brings together children and their extended families, with a skilled facilitator to develop plans for placement prevention, reunification, permanency, placement transition or youth independent living. FGDM is supported through grants to counties and tribes and 2,588 children were served in 2009 o Relative Care Assistance - Between 1,850 and 1,950 relative custody assistance grants are paid each month to support children in permanent relative custody. o Adolescent Services - CFCIP - Nearly 800 foster care youth were served in programs delivered by counties, community-based organizations and tribes that provide assistance and Independent Living Programs. Education and Training Voucher Program - 188 former foster care youth were awarded an education voucher grant to help defray the costs of post-secondary education. Transition Supports-Over 1000 youth preparing to leave long-term foster care, or who have recently left foster care received transitional planning and housing assistance services through community-based providers. National Youth in Transition Database- A new requirement effective October 1, 2010. The state will be responsible for tracking the independent living services provided to youth and to measure outcomes for youth leaving foster care to independent living. States will be expected to survey certain youth at ages 17, 19 and 21 about the following outcomes: financial self-sufficiency, experience with homelessness, educational attainment, positive adult connections, high-risk behavior, access to health insurance. o Oversight on federal compliance for Title IV-E. o Interstate Compact on the Placement of Children (ICPC) –ICPC is responsible for the oversight of children/youth leaving and entering the state for purposes of adoption/foster care. In 2009 774 children were sent from MN to foster care/adoption locations in other states; 943 children were received in MN. o Adoption Services for Children Under State Guardianship – In 2009 652 children entered state guardianship, o Public Private Adoption Initiative/Adoption Incentive – Grants to 8 providers for recruitment of foster and adoptive families and efforts to place children under state guardianship in adoptive homes. Approximately 400 children and 650 families are served through these grants. o Adoption Assistance - Approximately 7,500 subsidized adoption grants are paid each month to support special needs children in adoptive homes. o Adoption Records Management - Maintain 1.7 – 2.0 million adoption records that must be retained permanently. The oldest records are on microfilm; the rest are in SSIS/EDMS P8. DHS maintains physical and electronic storage capacity. Coordination with Tribes o Indian Child Welfare – The state is required to consult and coordinate with Tribes to develop specific measures for complying with the Indian Child Welfare Act and make arrangements for the provision of child welfare services and protections to Indian children o Indian Child Welfare Grants fund 19 tribal and urban Indian social service agencies to provide a continuum of services. Over 2800 children were served under these grants in 2009. o American Indian Child Welfare Initiative - $4.7 million state funds are granted to Leech Lake and White Earth Bands of Ojibwe to provide the full continuum of child welfare services to children and families residing on the reservations. 3000 children and families have been served through this Initiative which was authorized by the 2005 legislature. Outcomes for Indian children served through the Initiative will be tracked to demonstrate the impact on disparities. Page 21      August 1, 2011      MN DHS Systems RFI     Child Welfare Training o Child Welfare Training – The Child Welfare Training System is supported through federal Title IVE, county contribution and state general fund. The training system provides pre-service and ongoing training to child welfare staff in county and tribal agencies. In 2009 the training system conducted 114 training events with 1505 participating trainees. o Foster, Adoptive and Kinship (FAK) Training – County and tribal foster, adoptive and kinship care providers receive pre-service and ongoing training through the Child Welfare Training System. In 2009 323 training events were conducted, with 3086 participating trainees. o Social Service Information System Training – SSIS Training supports County, tribal and DHS users through classroom, web-based, and self-directed training modules to accomplish proficient use of SSIS, important to federal reporting and performance monitoring. In 2009, 51 training events were conducted with 1389 participating trainees. Child Welfare Quality Assurance and Performance Monitoring o Quality Assurance – The federal Children’s Bureau carries out a program of Child and Family Service Review (CFSR) which periodically evaluates the state’s performance on 17 National Data Standards, 23 child welfare practice items, and 7 systemic factors. CFSR’s have been completed in Minnesota in 2001 and 2007. Following both reviews the state has been required to develop a Program Improvement Plan (PIP), and demonstrate improvement on areas needing improvement to avoid fiscal sanctions. The state successfully completed the first PIP in 2004; the current PIP is in the first year of implementation. Since 1998 CSP has carried out a quality assurance review program of county child welfare agencies. Since 2003 CSP has conducted quality assurance reviews using the same metrics and protocols applied by the federal CFSR. Approximately 20 counties per year are reviewed and develop a Program Improvement Plan to address those performance factors needing improvement. County PIPs are aligned with the state PIP in those areas needing improvement in common. o Child Mortality Review - Multidisciplinary panel review at the local and state level of child fatalities and near fatalities of children/youth resulting from child maltreatment. In 2009, there were 21 child fatalities and 44 life-threatening injuries as a result of maltreatment by a caretaker reported. Local and state panels make recommendations for improvements to the child protection system to prevent future deaths/near fatal injuries. The number of child fatality/near fatality has been rising since 2004. o Citizen Review Panels-Citizen review panels are a requirement under the CAPTA program. Minnesota supports the work of 5 panels in Hennepin, Ramsey, Washington, Winona and Chisago Counties. o Oversight for CW-TCM compliance. o Grants and contract management - $19 million dollars distributed through approximately 200 grants/contracts. o Federal Planning and Performance Reporting – The department is required to develop a Child and Family Service Plan every 5 years that describes and integrates the service continuum supported by the array of federal funds that support child welfare services. Annual Progress and Services Reports are required to report the state’s compliance with federal regulations and to assess progress toward meeting the goals and objectives set out in the plan. Currently CSP is Page 22      August 1, 2011      MN DHS Systems RFI     required to provide quarterly reports to the Administration of Children and Families to document progress on the PIP. The CSP Research Unit publishes an annual Report to the Legislature on child maltreatment and on children in out-of-home care as required by Minnesota Statute, section 257.0725, in addition to evaluating performance, supporting policy analysis and reporting on areas of priority in CSP. Child and Community Services Act (CCSA) – CCSA created a consolidated fund in 2003 to fund an array of social services to children, adolescents, and adults within the county who experience dependency, abuse, neglect, poverty, disability, chronic health conditions, or other factors, including ethnicity and race, that may result in poor outcomes or disparities, as well as services for family members to support such individuals. Allocations are made to county agencies have an approved biennial plan. Under these grants, county agencies provide services to approximately 350,000 people. o Child Support Minnesota’s current system for child support services includes • • • • • • • Locating parents Establishing parentage Establishing and enforcing court orders for child support, medical support and child care support Collecting and processing payments Reviewing and modifying court orders for child support, medical support and child care support Adjusting court orders based on the cost of living index Working with other states to enforce support when one parent does not live in Minnesota. A portion (FY 2010 approximately 18%) of program funding comes from Minnesota counties who have been very influential in determining system functions for the 243,000 open cases in Minnesota. The current system has 4500 registered users and typically has about 1700 simultaneous online users. 85% of our online cases have support orders and our child support guidelines determine support amounts based on: • • • • • The income of both parents The number of children The cost of raising a child at different income levels and The availability and cost of medical support Child Care Support In FFY 2009 Minnesota: Collected $598.1 million Spent $166.3 million to fund child support services Served 245,695 Title IV-D child support cases CDCS ‐ Consumer Directed Community Supports Consumer Directed Community Supports (CDCS) is a unique service option that gives persons more flexibility and responsibility for directing their services and supports, including hiring and managing direct care staff. CDCS may include services, support and/or items currently available through the Medical Page 23      August 1, 2011      MN DHS Systems RFI     Assistance waivers, as well as additional allowable services that provide needed support to persons. CDCS is a service option under several home and community-based programs. CDCS is available as a statewide service for persons enrolled in one of the following programs: • • • • • • • Alternative Care (AC) Program   Community Alternative Care (CAC) Waiver   Community Alternatives for Disabled individuals (CADI) Waiver  Developmental Disabilities (DD) Waiver   Elderly Waiver (EW)   Minnesota Senior Health Options (MSHO)   Traumatic Brain Injury (TBI) Waiver   The range of allowable CDCS services and supports can be tailored to meet a person’s needs. The flexibility built into CDCS allows a person to describe the services and supports in ways that are meaningful to the person. A person’s plan can include a mix of required and optional services and supports. • • • Community Support Plan (includes budget methodology) Fiscal support entity services Support Planner Person-centered planning MMIS MMIS is Minnesota’s automated system for payment of medical claims and capitation payments for Minnesota Health Care Programs (MHCP) which include MinnesotaCare, MA, GAMC, and Medicare Supplement Programs. Some support for eligibility for MinnesotaCare is on our MMIS system. SMI – Shared Master Index The SMI is a web-based system that interacts with DHS and County service entity systems, creating a common client identifier as well as maintaining a cross reference of client identifiers in the various systems. This master identifier assists workers, analysts, researchers and others in tracking clients across systems and provides a mechanism for synchronizing client data across DHS systems. The SMI provides functionality (search, match, merge) for the ongoing management of this single client identifier. In addition, the SMI provides workers a cross-systems view of client participation through real time web service integration with major DHS systems.   Page 24        August 1, 2011      MN DHS Systems RFI     Appendix B: Technical Checklist (Optional) Vendor System Design Checklist Response (Optional) - Select all that apply - Indicate all items checked for which the Vendor software is certified. Architectural Approach __ SOA __ 3/N Tier __ Other (specify): Processing Type __ OLTP __ OLAP __ Other (specify): Development Platform __ J2EE __ .NET __ Other (specify): Architectural Framework(s) __ STRUTS __ JATO __ JSF Other (specify): Architectural Pattern(s) __ MVC __ Factory __ Controller __ Data Access Object Other (specify): Application Communication Technologies Service Interface: __ Web Services (HTTP, XML, SOAP, WSDL, UDDI) __ Public Facing __ Internal Facing __ Messaging Platform Specific: __ .NET Remoting __ EJB/RMI __ IIOP __ Other (specify): System Integration Technologies __ XML __ Web Services __ Messaging __ EDI __ CORBA __ IIOP __ Adaptors __ Secure FTP __ Other (specify): Page 25      August 1, 2011      MN DHS Systems RFI     Software Testing General: __ Functional __ Regression __ System __ Integration Specialized: __ Performance __ Load __ Stress __ Error Handling __ Security __ Platform Accessibility: __ WCAG V1.0 __ Priority 1 __ Priority 2 __ Priority 3 __ WCAG V2.0 (Draft): __ Level 1 __ Level 2 __ Level 3 __ Section 508 User-Participation: __ Beta __ User Acceptance __ Other (specify): Vendor System Design Checklist Response - Select all that apply Security Technologies __ Identity and Access Management __ Integrated __ Externalizable __ Externalized __ SSL/TLS __ Data Encryption Level Supported: __ Column __ Row __ Table __ Database __ Cookie Encryption __ DES __ 3DES __ AES __ Other (specify): __ Other (specify): Client Operating Systems __ Apple __ Microsoft __ Linux __ UNIX __ Palm __ Microsoft PocketPC __ Other (specify): Client Platforms Page 26      August 1, 2011      MN DHS Systems RFI     __ Desktop/Laptop __ Tablet __ PDA __ Smart Phone __ Other (specify): Client Footprint by Platform Specify size of footprint in KB or MB: Desktop/Laptop: ___ Tablet: ___ PDA: ___ Smart Phone: ___ Other (specify): ___ Client Connection Speed Specify speed in kbps or mbps: Minimum: _____ Recommended: ________ Client Richness __ Browser-Based __ Rich Client __ Rich Internet (AJAX) Browsers and Versions Supported __ Internet Explorer (specify versions): __ Netscape Navigator (specify versions): __ Other (specify product and versions): Presentation - Client Side Languages __ HTML _ DHTML _ XML __ XHTML __ VB.NET __C# __ ActiveX Controls __ Java Applets __ Java __ JVM (specify details): __ JavaScript __ VBScript __ C++ __ Other (specify): Application State __ Cookies: __ Non-Persistent Cookies __ Persistent Cookies __ Session Ids __ State Stored in Hidden Fields __ Other (specify): Web Server Location __ Public Facing __ Internal Facing Web Server Operating System __ Windows __ Linux __ UNIX __ Other (specify): Specify Version: Web Server Software __ Apache Page 27      August 1, 2011      MN DHS Systems RFI     __ Microsoft __ Sun __ Oracle __ Other (specify): Specify Edition and Version: Web Server - High Availability Load Balancing Supported: __ Yes __ No 64 Bit Processors Supported: __ Yes __ No Dual Core Processors Supported: __ Yes __ No Other (specify): Presentation – Server Side Languages __ ASP.NET __ VB.NET ___C# __ JSP __ Servlets __ Java __ JVM (specify details): __ Server Side Includes (SSI) __ C++ __ Other (specify): Application Server Operating System __ Windows __ Linux __ UNIX __ Other (specify): Specify Version: Application Server Software __ Microsoft __ IBM __ Sun __ Oracle __ BEA __ Other (specify): Specify Edition and Version: Application Server – High Availability 64 Bit Processors Supported: __ Yes __ No Dual Core Processors Supported: __ Yes __ No RAID Supported: __ Yes __ No SAN Supported: __ Yes __ No Mirroring Supported: __ Yes __ No Clustering Supported: __ Yes __ No Grid/On Demand Supported: __ Yes __ No Other (specify): Business Rule – Application Languages __ VB.NET __C# __ Java (J2SE) __ Java/EJB (J2EE) __ JVM (specify details): __ C++ __ Other (specify): Page 28      August 1, 2011      MN DHS Systems RFI     Database Server Operating System __ Windows __ Linux __ UNIX __ Other (specify): Specify Version: Database Server Software __ Microsoft __ IBM __ Oracle __ Other (specify): Specify Version: Database Server – High Availability 64 Bit Processors Supported: __ Yes __ No Dual Core Processors Supported: __ Yes __ No RAID Supported: __ Yes __ No SAN Supported: __ Yes __ No Mirroring Supported: __ Yes __ No Clustering Supported: __ Yes __ No Grid/On Demand Supported: __ Yes __ No Other (specify): Data Access – Connectivity Methods __ ADO.NET __ ODBC __ OLE/DB __ JDBC __ JDO __ DB2 Connect __ Other (specify): SQL Languages __ T/SQL __ PL/SQL __ Other (specify): Stored Procedures Utilization __ Data Access __ Business Rules Page 29      August 1, 2011