rfp required or comments category/requirement exhibit

RFP Exhibit D Technical Evaluation Scoring Matrix 7/10/2014

SPOKANE COUNTY REGIONAL SUPPORT NETWORK (SCRSN)EXHIBIT D

TECHNICAL EVALUATION SCORING MATRIX - SECTION 9.0 OF RFP

The evaluation committee will review and evaluate the offers according to the following criteria based on a pass or fail decision. If deemed necessary, SCRSN may request additional information to determine an Offeror's ability to provide the services. While all technical deliverables/requirements require a response from the Offeror, some of the deliverables/requirements are required and some are desired (optional). Refer to the column “Required or Optional” below for specifics regarding whether each of the following individual deliverables/requirements is required or desired (optional). The following Technical Requirements are found in Section 9.9.1 of the RFP; additional specific references for each requirement are provided below in the “RFP Section” column.

Note: The pass or fail decision will be assigned based on the Scoring Guide in Section 6.

Note: Offeror’s are required to complete the RFP based on implementing with the required and preferred (or Offeror’s proposed as substituted for the preferred) SCRSN Data Warehousing and Business Intelligence software, found in Section 9.2, and includes responding to the requirements that follow.

Offeror Name: _________________________________

Category/RequirementRFP

Section/ Exhibit

Required or Optional

EvaluationComments

Offerors must provide description for each item listed.

ABILITY TO MEET REQUIREMENTS AND PROVIDE INFORMATION FOR: PROJECT/TIMELINE, HIPAA COMPLIANCE, TECHNICAL STAFF QUALIFICATIONS, TECHNICAL COMPONENTS, SOFTWARE FUNCTIONALITY & TECHNICAL SYSTEMS SUPPORT

A. MEET PROJECT DELIVERABLES See Table Below, Meet Deliverables on Schedule = Pass; Cannot Meet Deliverables on Schedule = Fail

A.1 Meet Project Deliverables on Schedule 4.1.4, Exhibit D

Required Pass/Fail

A.2 What are the Offeror’s change managementprocess and procedures after the business and technical requirements have been defined, documented and approved by SCRSN during the Requirements Phase of the project?

4.1.4, 9.9.1,Exhibit D

Required Pass/Fail

B. HIPAA COMPLIANCE REQUIREMENTS See Table Below, Meet Deliverables on Schedule = Pass; Cannot Meet Deliverables on


Schedule = Fail

B.1 Comply with HIPAA HITECH Security and HIPAA Privacy Compliance and Annual Monitoring

3.2.1(G1), 9.9.1, Exhibit

C(G1) & Exhibit D

Required Pass/Fail

B.2 Ability to comply with HIPAA privacy and HITECH security standards, specifications, and other requirements as contained in HIPAA 42 CFR Part 2, 45 CFR 160, 45 CFR162, 45 CFR 164, and all other statutes, regulations and/or ordinances that govern the confidentiality and protection of protected health information (PHI).

3.2.1(G1), 9.9.1, Exhibit

C(G1), & Exhibit D

Required Pass/Fail

B.3 Ability to provide documented evidence of official policies, procedures, Disaster Recovery and Business Resumption Plan, system backup/restore/verification, risk analysis, Risk Management Plan, and other demonstrable evidence of HIPAA 42 CFR Part 2, 45 CFR 160, 45 CFR 162, 45 CFR 164 compliance (e.g. system logs, training, staff background checks, encryption, etc.).

3.2.1(G1), 9.9.1, Exhibit

C(G1), & Exhibit D

Required Pass/Fail

B.4 Ability to support and respond to annual monitoring performed by SCRSN on all IS vendors, including annual on-site inspections, providing compliance documentation, responding to SCRSN monitoring reports with corrective action plans if needed, and implementing approved corrective action plans for HIPAA HITECH Security Rule compliance.

3.2.1(G1), 9.9.1, Exhibit

C(G1), & Exhibit D

Required Pass/Fail

C. TECHNICAL STAFF QUALIFICATIONS REQUIREMENTS

See Table Below, Meet Deliverables on Schedule = Pass; Cannot Meet Deliverables on Schedule = Fail

C.1 Business Dimensional Data Modeling Software Consultant

o Behavioral Health Industry (mental health and substance abuse services) Business Rule and Data Modeling Expert, preferably with:

Direct experience addressing

9.8, 9.9.1, & Exhibit D

Required Pass/Fail


the needs of the business and technical deliverables with the preferred Data Modeling software, the Offeror’s Behavioral Health Data Model (or other standard data model provided by the Offeror for customizing to fit SCRSN’s datamodeling needs), and the Offeror’s Behavioral Health dimensional matrix of the DW Bus Architecture

o Kimball Dimensional Data Methodology Expertise

o Preferred (or Offeror’s proposed) Dimensional Data Modeling Software Expertise

o Previously produced a Behavioral Health services organization’s business Data Model, a Dimensional Matrix of DW Bus Architecture, and identified Slowly Changing Dimensions within the Dimensional Matrix for implementation purposes

C.2 Extraction/Transformation/Loading SoftwareConsultant:

o Behavioral Health (mental health and substance abuse services) Business Data Transformation and Business Rule Expert, preferably with:

Direct experience addressing the needs of this RFP’s business and technical deliverables with the preferred (or Offeror’s proposed) ETL software.

o Preferred (or Offeror’s proposed) ETL Software Expert

o Preferred (or Offeror’s proposed)

9.8, 9.9.1, & Exhibit D

Required Pass/Fail


Metadata Repository/Integration Software Expertise

o Business Data Traceability, Data Reconciliation, Data Lineage, and Impact Analysis Expertise

o DW Bus Architecture Expertiseo Data Profiling and Data

Reconciliation Expertiseo Job Scheduling Expertise (e.g.

automated/scheduled batch processing)

o Experience with Preferred (or Offeror’s proposed) Job Scheduling Software

C.3 End User Business Intelligence (BI) Data Analytics and GUI Front End Application Consultant:

o Behavioral Health (mental health and substance abuse services) BI Data Analytics and Front End Application Expert, preferably with:

Direct experience developing and addressing end user BI data analytics needs as specified in the Business Requirements with the preferred (or Offeror’s proposed) BI Data Analytics software; and implementing BI data analytics solutions in a Behavioral Health service organization’s business environment

o End User BI Data Analytics and GUIFront End Application Software Expert with the preferred (or Offeror’s proposed) BI Data Analytics Software

o Preferred (or Offeror’s proposed) Metadata Repository/Integration Software

o Business Data Traceability, Data

9.8, 9.9.1, & Exhibit D

Required Pass/Fail


Lineage, and Impact Analysis Expertise

C.4 Microsoft SQL DBMS Consultant:o Microsoft SQL DBMS Expert,

Specializing in BI/DW Performance Tuning/Optimization in the RequiredSoftware Version

o Experience with Preferred (or Offeror’s proposed) ETL Software

o Experience with Preferred or (or Offeror’s proposed) Data Modeling Software

o Experience with Preferred (or Offeror’s proposed) Metadata Repository/Integration Software

o Experience with the Preferred (or Offeror’s proposed) End User Business Intelligence (BI) Data Analytics and Front End Application Software

o Experience with DW/BI Data Traceability, Data Reconciliation, Data Lineage, and Impact Analysis

o Experience with DW Bus Architecture

9.8, 9.9.1, & Exhibit D

Required Pass/Fail

C.5 Architect Consultant:o Experience Designing/Architecting

Data Warehouse & Business Intelligence Environments

o Experience with DW Bus Architecture

o Experience with Preferred (or Offeror’s proposed) ETL Software Expertise

o Experience with Preferred (or Offeror’s proposed) Data Modeling Software and with Dimensional Data Modeling

o Experience with Preferred (or Offeror’s proposed) Metadata Repository/Integration Software

o Experience with the Preferred (or Offeror’s proposed) End User

9.8, 9.9.1, & Exhibit D

Required Pass/Fail


Business Intelligence (BI) Data Analytics and Front End Application Software

o Experience with DW/BI Data Traceability, Data Reconciliation, Data Lineage, and Impact Analysis

o Experience with MS SQL DBMS Performance Tuning/Data Sizing/Data Growth in the Required Software Version

o Experience/Expertise with Offeror’s DW/BI Hardware in a Hosted Environment

o Experience/Expertise with Offeror’s DW/BI Infrastructure in a Hosted Environment

o Experience/Expertise with DW/BI Architecture/Infrastructure Expansion/Growth

o Experience/Expertise with Planning Job Scheduling Execution with the Preferred (or Offeror’s proposed) Job Scheduling Software

D. TECHNICAL COMPONENTS: HARDWARE AND CONNECTIVITY REQUIREMENTS AND INFORMATION


D.1 Provide hardware information required for SCRSN to implement a hosted environment with the Offeror as part of the SCRSN’s Data Warehouse and Business Intelligence project.

9.0, 9.9.1, & Exhibit D

Required Pass/Fail

D.2 Can the hosted environment, applications, and data be securely accessed from any location with an Internet/broadband connection? If so, how are they securely accessed?

9.0, 9.9.1, & Exhibit D

Required Pass/Fail

D.3 Provide remote connectivity requirements and information required for SCRSN to implement with the Offeror the data integration/loading of SCRSN source data to the hosted data warehouse environment, and for users to connect with the Data

9.0, 9.2, 9.9.1, &Exhibit D

Required Pass/Fail


Warehouse and Business Intelligence environments for both technical support/development users and for end user purposes associated with the SCRSN project specifications and the preferred (or Offeror’s proposed) project software found in Section 9.2 of the RFP.

D.4 Can the implementation of the hosted environment support a staggered installation/availability approach for the development, testing, and production environments based on the project timeline in Section 4.1.4 of the RFP?

4.1.4, 9.0, 9.2, 9.9.1, & Exhibit D

Required Pass/Fail

D.5 Provide detail regarding the backup and emergency fail over methodology and processes for the hardware (e.g. mirrored server or simple backup and restore).

9.0, 9.2, 9.9.1, & Exhibit D

Required Pass/Fail

E. TECHNICAL COMPONENTS: ARCHITECTURE AND INFRASTRUCTURE REQUIREMENTS AND INFORMATION


E.1 Provide architecture information required forSCRSN to implement a hosted environment with the Offeror as part of the SCRSN’s Data Warehouse and Business Intelligence project.

9.9.1 and Exhibit D

Required Pass/Fail

E.2 Provide Infrastructure information required for SCRSN to implement a hosted environment with the Offeror as part of theSCRSN’s Data Warehouse and Business Intelligence project.

9.9.1 andExhibit D

Required Pass/Fail

E.3 Provide a well-integrated, optimized, and robust Data Warehouse and Business Intelligence platform that is supportable and low cost, please describe the overall technology stack, including the integration points for the overall solution.

9.9.1 and Exhibit D

Required Pass/Fail

E.4 Describe the skill sets required to develop, support, and maintain the well-integrated and robust Data Warehouse and Business Intelligence platform described in the previous question.

9.9.1 and Exhibit D

Required Pass/Fail


E.5 Describe the training required to develop, support, and maintain the well-integrated and robust Data Warehouse and Business Intelligence platform described in the previous two questions.

9.9.1 and Exhibit D

Required Pass/Fail

E.6 Provide the ability to do end to end data encryption from the database to the users’ desktop (important, please describe the methods or protocols supported.)

9.9.1 and Exhibit D

Required Pass/Fail

E.7 Ability to do user authentication that is secure and encrypted in all tools within the technology stack.

9.9.1 and Exhibit D

Required Pass/Fail

F. TECHNICAL SYSTEMS SUPPORTREQUIREMENTS AND INFORMATION


F.1 How often is routine maintenance performedon the hosted environment?

9.9.1 and Exhibit D

Required Pass/Fail

F.2 How often are system updates applied in the hosted environment?

9.9.1 and Exhibit D

Required Pass/Fail

F.3 How often is performance monitoring performed in the hosted environment?

9.9.1 and Exhibit D

Required Pass/Fail

F.4 How often are customer requested enhancements applied in the hosted environment?

9.9.1 and Exhibit D

Required Pass/Fail

F.5 Define the Support Structure (e.g. Tiered Approach, Client assigned 1 point of contact, etc.)

9.9.1 and Exhibit D

Required Pass/Fail

F.6 What hours and days is customer support available (specify times zones)?

9.9.1 and Exhibit D

Required Pass/Fail

F.7 What are the available and preferred methods of contact for customer support (phone call, e-mail, etc.)?

9.9.1 and Exhibit D

Required Pass/Fail

F.8 Where are your customer support staff members located (list city, state, country for all locations)?

9.9.1 and Exhibit D

Required Pass/Fail

F.9 How is after hours, emergency support handled? What is your definition of an emergency to obtain emergency support?

9.9.1 and Exhibit D

Required Pass/Fail

F.10 Is customer support staff available at all times (e.g. in an on-call capacity)?

9.9.1 and Exhibit D

Required Pass/Fail


F.11 What is the range and average for system downtime (scheduled and unscheduled) for your clients’ systems on an annual basis?

9.9.1 and Exhibit D

Required Pass/Fail

F.12 Problem/Resolution Process: What is the average response time to support tickets/calls for all levels of severity?

9.9.1 and Exhibit D

Required Pass/Fail

F.13 Problem/Resolution Process: What is the average time to resolve support tickets/calls by severity level?

9.9.1 and Exhibit D

Required Pass/Fail

F.14 Problem/Resolution Process: Describe your system support escalation process andprocedures

9.9.1 and Exhibit D

Required Pass/Fail

G. SOFTWARE FUNCTIONALREQUIREMENTS


G.1 Ability to complete and demonstrate a verifiable proof of concept for SCRSN Data Warehouse and Business Intelligence Program based on SCRSN’s criteria and data.

9.7, 9.9.1, & Exhibit D

Required Pass/Fail

G.2 Ability to complete a documented Architecture Plan/Model with SCRSN Project Team meeting the software and business requirements.

4.1.3, 4.1.4, 9.9.1 & Exhibit D

Required Pass/Fail

G.3 Ability to complete a documentedInfrastructure Plan with SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.4 Ability to complete a documented Project Charter with SCRSN Project Team meeting the software and business requirements.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.5 Ability to complete Business Requirements Document with SCRSN Project Team meeting the software and business requirements.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.6 Ability to complete installation of required and preferred (or Offeror’s proposed) software in a hosted environment to support development, QA testing and training activities, and ultimate deployment to the Production Environment.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.7 Ability to complete on-the-job training for Offeror’s solutions with Dimensional Data

4.1.3, 4.1.4,9.9.1 &

Required Pass/Fail


Modeling, ETL, Metadata Repository/Integration, End User BI Data Analytics and GUI Front End Application based on SCRSN’s required and preferred (or Offeror’s proposed) software.

Exhibit D

G.8 Ability to complete system checkout of software with SCRSN Project Team (DBMS,Data Modeling, ETL, Metadata Integration, End User BI Data Analytics and GUI Front End Application with the SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.9 Ability to complete Design Phase for Business Requirements (logical and physical data models for data mart requirements, dimensional matrix of DW Bus Architecture with identified slow changing dimensions, DBMS, ETL processes, staging plans by table, metadataintegration, end user BI data analytics and GUI front end application, and set of report/extract/dashboard specifications) withthe SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.10 Ability to provide a preliminary business dimensional data model and complete the Development Phase (logical & physical datamodels, data marts, dimensional matrix of DW Bus Architecture with identified slow changing dimensions, ETL processes, DBMS, metadata repository/integration, end user BI data analytics and GUI front end application, and end user reports/extracts/dashboards) with the SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.11 Ability to complete the Testing Phases (unit, integration, performance, Quality Assurance, and User Acceptance Testing, initial/incremental/full data loads) with the SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.12 Ability to complete the Acceptance Certification Phase with the SCRSN Project Team (ability to certify the acceptance of hardware & software functionality, testing

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail


results from QA Testing, Performance & Load Testing, User Acceptance Testing, and System Checkout from Production Environment).

G.13 Ability to perform and complete the Technical On–the-Job Training and Technical Documentation with the SCRSN IS project team based on Offeror’s project implementation solutions and the required and preferred (or Offeror’s proposed) software.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.14 Ability to plan/complete Go Live Deployment & for transitioning to a Post Live Support state with the SCRSN Project Team.

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

G.15 Ability to complete future Business Intelligence projects with the SCRSN ProjectTeam (if requested).

4.1.3, 4.1.4,9.9.1 & Exhibit D

Required Pass/Fail

Subsection 1 - SPECIFIC SOFTWARE FUNCTIONAL REQUIREMENTS: Metadata Integration and Metadata Repository Software—REQUIRED RESPONSEG.16 Ability to provide architecture and

technical stack for the project.4.1.3, 4.1.4,

9.9.1 & Exhibit D

Required Pass/Fail

G.17 Ability to store named database connections with the username, password (secure and encrypted), and connect string that have the same name but different values in Development, QA, and Production.Allowing a smooth migration among environments without changes. The passwords and connect strings will change but the connection names will remain the same.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.18 Able to back out a modification from Production if there is a problem with the changes (important, please describe how the back out occurs.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.19 Provides the ability to capture and store behavioral health services organization’sbusiness rules and business terms along with the technical metadata.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.20 Supports ability of incremental scripting of 4.1.3, 9.9.1 Optional


all edits so that a customer can migrate the test system into production or development (or vice versa) in a single command or update script or a reasonable code migration method (important, please describe how edits are migrated from one system to the other).

& Exhibit D

G.21 Supports bi-directional integration betweenthe metadata repository and other Data Warehousing and Business Intelligence (DW/BI) tools (important, please describe integration methods and what DW/BI tools).

4.1.3, 9.9.1 & Exhibit D

Optional

G.22 Ability to integrate metadata from all tools in the DW/BI technology stack; DBMS system tables, schema design tools, data reconciliation processes, ETL process-flow, and Reporting tool Information (important, please describe how this works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.23 Perform integration with all the tools in the stack via built-in connectors, not requiring the client to have to create all the mapping elements between the tools.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.24 Ability to run standard and custom reports for validating data lineage, mappings, data dependency analysis, data-store structures, users, and documentation; browse, and explore database and other metadata.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.24 Ability to integrate metadata from all tools in the DW/BI technology stack; DBMS system tables, schema design tools, data cleaning processes, and ETL process-flow, and Reporting tool Information (important, please describe how this works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.25 Ability to show data lineage in both a textual and graphic format for traceability and impact analysis.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.26 Ability to show impact analysis; e.g. the tool can proactively identify downstream impact to the semantic metadata layer and end user reports based on data source table changes for change management planning (important please describe how it

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


works.)G.27 Ability to extract or retrieve metadata from

the preferred (or Offeror’s proposed) data modeling software into the metadata repository (important, please include the metamodel used).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.28 Ability to extract or retrieve metadata from the preferred (or Offeror’s proposed) ETL software into the metadata repository (important, please include the metamodel used).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.29 Ability to extract or retrieve metadata from the required Microsoft SQL Database software into the metadata repository (important, please include the metamodel used.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.30 Ability to extract or retrieve metadata from the preferred (or Offeror’s proposed) Business Intelligence Data Analytics and Reporting software into the metadata repository (important, please include the metamodel used).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

Subsection 2 - SPECIFIC SOFTWARE FUNCTIONAL REQUIREMENTS: ETL Software—REQUIRED RESPONSEG.31 Provide architecture and technical stack

for the required ETL software.4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.32 Ability to specify memory management settings like shared memory and buffer block size (important, please list the settingssupported.)

4.1.3, 9.9.1 & Exhibit D

Optional

G.33 Ability to pipe data directly into the database via the bulk-load utility without having to place data on disk until it hits its final destination (important, please indicate how the bulk load works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.34 Ability to do collaborative design and development work with multiple users with features like locking or check in/check out, difference tracking, and version management.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.35 Ability to store named database connections with the username, password (secure and encrypted), and connect string

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


that have the same name but different values in Development, QA, and Production.Allowing a smooth migration among environments without changes. The passwords and connect strings will change but the connection names will remain the same.

G.36 Ability to support xml formats and xml datainterchange.

4.1.3, 9.9.1 & Exhibit D

Optional

G.37 Provides native database connections for a Microsoft SQL database and other databases supported (important, please include the list of databases supported.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.38 Ability to save mappings to a file that can be checked into the SCRSN standard version management software Sourcegear Vault Professional (important, please list theformats available.)

4.1.3, 9.9.1 & Exhibit D

Optional

G.39 Able to back out a modification from Production if there is a problem with the changes (important, please describe how the back out occurs.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.40 Provides the ability to capture and extract, transfer, and load (or export) Behavioral Health business metadata (business rules, business terms, business definitions), along with the technical metadata.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.41 Supports ability of incremental scripting of all edits so that a client can migrate the test system into production or development (or vice versa) in a single command or update script or a reasonable code migration method (important, please describe how edits are migrated from one system to the other.)

4.1.3, 9.9.1 & Exhibit D

Optional

G.42 Ability to design ETL processes in a comprehensive and systematic manner through a single interface without having fragmented steps and multiple tools involved.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.43 Ability to do collaborative design and development work with multiple users with

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


features like locking or check in/check out, difference tracking, and version management.

G.44 Provides a state-of-the-art graphical user interface (GUI) for all ETL functions to aid in design and visualization of the data flow and enhances design efficiency.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.45 Provides the capability to create reusable modules that can be used in many mappings to prevent redundant code (important, please describe how reusable modules work).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.46 Ability to perform updates to the metadata layer which propagates the change through the ETL process (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.47 Ability to publish/alert reporting structure revisions--dimension tables to data cubes/marts/subject areas and fact tables tousers.

4.1.3, 9.9.1 & Exhibit D

Optional

G.48 Ability to track implied data conversion andcan deliver reports that identify any such conversions (e.g. data overflow errors).

4.1.3, 9.9.1 & Exhibit D

Optional

G.49 Contains a metadata layer within the ETL Tool for use in the tool and integrating with other metadata tools.

4.1.3, 9.9.1 & Exhibit D

Optional

G.50 Ability to perform impact analysis of a change both backward and forward in the data flow (important, please describe how it works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.51 Ability to automate the metadata integration with the metadata tool.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.52 Ability to integrate metadata with the preferred (or Offeror’s proposed) metadata software tool with minimal to no hand coding by the customer (important, please describe how the tools are integrated).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.53 Captures logical data mapping information/metadata so that a logical data flow diagram (source to target) can be generated.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.54 Captures process metadata/metrics, e.g.: number of rows inserted /updated /deleted / rejected for each process, process start time, end time, and duration without code enhancements (important, please list the metrics captured).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.55 Contains automated self-documenting capabilities and enterable documenting capabilities to allow objects and processes to be commented (include what type of documents can be generated).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.56 Ability to monitor Query and Transformation performance (important, please describe the functionality).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.57 Ability to monitor mapping execution (real time) like status, through put, run times, etc. (important, please list the metrics available).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.58 Ability to monitor user activity and have visibility to what is happening in the preferred (or Offeror’s proposed) ETL software (important, please describe the functionality).

4.1.3, 9.9.1 & Exhibit D

Optional

G.59 Ability to manage complex load scenarios (e.g. balancing load across servers for scalability).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.60 Ability to support parallel transformations (e.g. parallel processing in the transformation engine.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.61 Ability to provide through put benchmarks (evaluation will be granted based on normalized results).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.62 Provides built in data previewing to assist in design work (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.63 Provides data quality handling with exception reporting records, generates auditrecords attached to the final dimension or fact data, or other data quality tracking/auditing capabilities (important, please describe).

4.1.3, 9.9.1 & Exhibit D

Optional

G.64 Provides built in data profiling to assist in design and analysis of source data.

4.1.3, 9.9.1 & Exhibit D

Optional


G.65 Provides token aware, intra-day execution,and real-time scheduling capabilities.

4.1.3, 9.9.1 & Exhibit D

Optional

G.66 Ability to integrate with web services in an SOA architecture (important, please describe the methods provided).

4.1.3, 9.9.1 & Exhibit D

Optional

G.67 Ability to create pre and post scripts for a mapping (important, please specify scriptingcapabilities they have "like execute a shell script").

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.68 Ability to hold a mapping until another mapping completes (dependency management/enforcement).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.69 Ability to poll the local file system to check for the existence of sentinel files (used to ensure transfers are complete, file has no meaningful content, its existence signifies the readiness of the file to which it relates).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.70 Possesses a checkpoint feature that guarantees that any record to reach a certain point in the process is written to disk for safekeeping.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.71 Possesses scheduling automation capabilities (e.g. can be run from the command line for integration with the preferred or proposed job scheduling tool).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.72 Provide error handling capabilities (e.g. error messages that can be over-written at each transformation step. Should have errorseverity levels and allow different things to occur based on the severity), (important to describe severity levels supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.73 Provides batch management with navigation via a graphical interface.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.74 Provides notification via email and/or SMS cell phone messaging as part of the error handling capabilities (important, please specify what methods are utilized).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.75 Supports exception handling and the ability to recover from abnormal ending of mapping & restart (important, please describe how the recovery is carried out).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.76 Ability to do in-line data compression for performance (important, please describe the methods provided).

4.1.3, 9.9.1 & Exhibit D

Optional

G.77 Ability to do in-line data encryption from database to database for private data (important, please describe the methods provided).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.78 Ability to separate the fact data by granularity automatically (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.79 Ability to use checksums calculations or use other advanced redundancy check methods (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.80 Ability to generating surrogate keys for dimension tables.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.81 Ability to capture dimension change history regardless of the update type, like standard, slowly changing, rapidly changing,etc. (important, please list the dimension types supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.82 Ability to create complex data transformations.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.83 Ability to do referential integrity checking (from table to table).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.84 Ability to extract and combine fact data from operational source systems.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.85 Ability to map keys from one system to another (important, please describe how thefunctionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.86 Ability to perform allocations (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.87 Ability to perform Data Cleansing functions(important, please list methods or functions).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.88 Ability to replicate dimensions from dimension authorities (important, please describe how the replication works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.89 Ability to set and use custom global variables within mapping to pass values between transformations and between records (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.90 Ability to set and use parameters for the mapping to allow reuse and flexibility of the mappings. These parameters would be passed into the mapping.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.91 Ability to turn on various levels of process logging and auditing for debugging (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.92 Allows for selected processing modules to be hand coded in SQL if needed (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.93 Provide aggregate development and administration with the ability to feed in detailed non-aggregated data and get out aggregated data (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.94 Provides a pre-built library of Data Warehouse specific transformations or what it would take to create them (important, please list the transformations).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.95 Provides a rich set of industry standard transformations (important, please include the list).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.96 Provides deduplicating capabilities (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.97 Provides full insert, update and deletion capabilities.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.98 Provides match and merging capabilities (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.99 Provides null value handling capabilities, like null substitution and the ability to recognize null from blank.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.100 Provides out of the box global variables for use with mapping, like current row count,batch, date/time, mapping name, etc. (important, please list the variables provided).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.101 Provides renormalization capabilities (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.102 Provides robust error detection and data corrections capabilities like the ability to support late arriving facts and dimension rows (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.103 Provides the ability to customize and reuse master key lookup transformation (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.104 Provides the ability to identify updated data (important, please list the methods).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.105 Provides the ability to manage slowly changing dimensions (important, please list the methods supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

Subsection 3 - SPECIFIC SOFTWARE FUNCTIONAL REQUIREMENTS: End User Business Intelligence (BI) Data Analytics and GUI Front End User Application Software—REQUIRED RESPONSE

G.106 Provide architecture and technical stack for the required End User BI Data Analytics and GUI Front End User Application software.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.107 Ability to dynamically read email addresses and address lists from MS Exchange server vs. maintaining multiple distribution lists and email addresses separately.

4.1.3, 9.9.1 & Exhibit D

Optional

G.108 Ability to push notification or alert of a specific business event via portal, email, pager, fax, SMS cell phone messaging/paging, or PDA when a particular metric condition is reached (important, please list alert capabilities and how they work.)

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.109 Ability to do collaborative design and development work with multiple users with features like locking or check in/check out, difference tracking, and version management.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.110 Ability to store named database connections with the username, password (secure and encrypted), and connect string that have the same name but different values in Development, QA, and Production.Allowing a smooth migration among environments without changes. The passwords and connect strings will change but the connection names will remain the same.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.111 Ability to do formulas and functions: Allow formulas and functions to be used in the metadata layer, the query, or the report. Allow different sets of functions for metadata, query, and report-based calculations (important, please include the list of formulas and functions).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.112 Ability to do report Linking & Navigation: Navigate across multiple reports.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.113 Ability to provide traceability from Excel back to the BI analytics, and back to the DW environment (important, please describe how the traceability is done).

4.1.3, 9.9.1 & Exhibit D

Optional

G.114 Ability to integrate with MS Excel, and export data to Excel with formatting, charts, and formulas (important, please include the versions of Excel supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.115 Ability to refresh data in specific MS Excel spreadsheets.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.116 Ability to save reports and metadata layerchanges to a file that can be checked into the SCRSN’s required version management software (important, please list the formats available).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.117 Able to back out a modification from the Production environment if there is a problem with the changes (important,

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


please describe how the back out occurs).G.118 Provides the ability to capture and

report/display a behavioral health service organization’s business rules and business terms along with the technical metadata.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.119 Supports ability of incremental scripting ofall edits so that a customer can migrate the test system into production or development (or vice versa) in a single command or update script or a reasonable code migration method (important, please describe how edits are migrated from one system to the other).

4.1.3, 9.9.1 & Exhibit D

Optional

G.120 Allows for metadata browsing within the reporting tool.

4.1.3, 9.9.1 & Exhibit D

Optional

G.121 Contains a development aid that allows for browsing to examine relationships among attributes in a dimension table, identifying distinct values, and storing them as a set of constraints saved with a user defined name for future queries.

4.1.3, 9.9.1 & Exhibit D

Optional

G.122 Ability to automate the metadata integration with the required metadata integration tool.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.123 Ability to integrate metadata with the recommended metadata tool with minimal to no hand coding by the customer (important, please describe how the tools are integrated).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.124 The ability for users to see data lineage information from the data output perspective. Important, please describe the metadata viewing capabilities the end user will get from the preferred (or Offeror’s proposed) BI analytics and/or reporting software.

4.1.3, 9.9.1 & Exhibit D

Optional

G.125 Ability to drill down into detail data and drill back up again to summary data.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.126 Ability to drill through to, or display on line, the source system metadata.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.127 Ability to slice and dice the data. 4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.128 Ability to use a Third-party OLAP tool (important, please list the tools supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.129 Capable of supporting multiple OLAP Architectures like DOLAP, MOLAP, HOLAP,ROLAP (important, please list the types of OLAP supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.130 Contains a rich set of Multi-dimensional calculations or the ability to do them (important, please include the list).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.131 Contains an Aggregate Navigator which allows queries to take advantage of aggregate tables without the users having to learn to navigate to them manually when building a query (important, please describe how the functionality works).

4.1.3, 9.9.1 & Exhibit D

Optional

G.132 Provide Query Management Services likequery reformulation or query retargeting (parse an incoming query & figure out how itcan best be resolved).

4.1.3, 9.9.1 & Exhibit D

Optional

G.133 Ability to do query governing to control the stability of the BI Data Analytics and Reporting environment (e.g. the ability to place a simple limit on the number of minutes a query can run before it times out, or limit the number of rows it can return).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.134 Ability to query multiple and separate data sources simultaneously (important, please describe).

4.1.3, 9.9.1 & Exhibit D

Optional

G.135 Advance date functionality like the ability to show Prior Year to Date next to Current Year to date side by side for comparison (describe method for doing this).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.136 Provides performance management toolsand applications: Ability to build custom dashboards ad hoc queries, alerts, and performing descriptive, prescriptive, predictive modeling, interactive analyses, forecasting, simulation, etc., including custom metrics and alerting (important, please describe the capabilities).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.137 Ability to burst a large report and parsing it to individual users based on dimensions,

4.1.3, 9.9.1 & Exhibit D

Optional


attributes, or hierarchies.G.138 Ability for IT and end users to schedule

and pull reports so results are pre-cached for users.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.139 Ability to generate reports immediately or in a scheduled capacity; pushing the results to the end users via a portal, email, wireless device, printer or other document delivery service.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.140 Ability to monitor usage and reporting activities, reporting metrics like start and finish time, status, user running the report so we can monitor utilization of reports/dashboards/etc. and how long they take to run (important, please list the metrics provided and how they are captured).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.141 Ability to develop predictive analytical solutions (important, please describe the capabilities and methods for doing so),

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.142 Contains a customizable scheduling calendar (important, please describe how it works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.143 Ability to assign and manage user authorization and security profiles (important, please describe how it works).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.144 Ability to set up advanced security (important, please list the advanced securitycapabilities).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.145 Ability to do external reporting and expose the reporting front end to external business partners over the internet (important, please describe how it works and how the data is secured/encrypted in transit).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.146 Ability to do inline data encryption from database to the users desktop for private data (important, please describe the methods or protocols supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.147 Ability to optionally display or associate SQL logic and/or query/report parameter selections, within or with, BI data results to

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


end user(s).G.148 Ability for external end users to explore

report data and personalize existing formatted fixed/canned reports, including the ability to sort and filter data, without the ability to add calculations, change chart types, or change the format of the output.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.149 Ability for internal end users to explore report data and personalize existing formatted fixed/canned reports, including the ability to sort and filter data, add calculations, change chart types, format the output, and save their favorite version for the next time they run the report or query.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.150 Ability to answer complex business questions like multi-pass SQL to query 2 star schemas to calculate a metric (important, please describe how multi-pass queries work).

4.1.3, 9.9.1 & Exhibit D

Optional

G.151 Ability to control chart aspects like min/max scale, label placement, 3D effect, and colors of individual lines and bars (important, please include the list of controls).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.152 Ability to have dual Y axes for charting multiple measures.

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.153 Ability to run queries to pre-populate parameters before the main and sub queries run.

4.1.3, 9.9.1 & Exhibit D

Optional

G.154 Ability to send alerts or controls that monitor specified values, ranges, or differences and notify the user when they exceed or have fallen below target levels (important, please describe alert capabilities).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.155 Ability to store reports in multiple file formats like PDF (important, please list the file formats).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail


G.156 Ability to support multiple consumer types (depending on technical skill levels and degrees of analytical sophistication), multiple types of information needs (e.g.: high level monitoring, business tracking, investigating, and complex analysis).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.157 Contains a robust set of prompting capabilities like column and row prompting or filtering on query or report design, aka parameters, pick lists, cascading prompts ordynamic filters, etc. (important, please include the list of prompt types supported).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.158 Provides a business view of the data in a semantic layer (shielding users from complexities of underlying database schema).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.159 Provides a rich set of charting capabilitieslike bar, line, pie, map, gauge histogram, bubble (important, please include the list of capabilities).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.160 Provides a rich set of report interactivity like collapsible table of contents displaying major groupings & subtotals, drill down capability, banded reporting, find functionality (important, please include a list of interactive capabilities).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.161 Provides advanced tool capabilities (e.g.: easy generation of sophisticated, interactive,engaging front-end screens, simple navigation controls, automatic replacement or on-the-fly creation of underlying report contents, user interface controls for conceptual representation like stoplights, gauges, sophisticated charts, geographical charts using GIS capabilities with links to underlying reports).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.162 Provides desktop or thick client reporting capabilities (if applicable, important to list the benefits of using the full client over the web-based reporting client).

4.1.3, 9.9.1 & Exhibit D

Optional


G.163 Provides the ability to reuse code where possible (important, please indicate how the code is reused).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.164 Provides Web-based or thin client reporting and authoring of ad hoc queries or reports by end users (important, please list any limitations).

4.1.3, 9.9.1 & Exhibit D

Required Pass/Fail

G.165 Provides the ability for the end user to click on a URL or link that is stored in the database and displayed on the report. This allows users to have the ability to reference detailed content from a Web page

4.1.3, 9.9.1 & Exhibit D

Optional

G.166 Provides the ability for the end user to access business intelligence data analytics, dashboards, reports, alerts, etc. from mobiledevices.

4.1.3, 9.9.1 & Exhibit D

Optional

rfp required or comments category/requirement exhibit

Documents