The Defense Finance and Accounting Service is conducting market research to identify vendors capable of providing a web-based analytic metrics capture/presentation/display solution for DFAS. The requirement is as follows: DFAS Analytic Metrics capture/Definition/Presentation/Display Capability is defined as the means to leverage a single software application or module – or integrated suite (two or more) of software applications and/or modules – to provide a web-based, analytic metrics capture/definition/presentation/display solution for DFAS. Minimum Functional/Technical Requirements Metric Data Collection/Input: Single point, direct manual entry or flat-file extraction/importation of metric data from an existing database or database options to the application/module. This must be user-friendly. Color-based or symbol-based error alert/indicator – if data entry is not made as planned (i.e., data missing, due date missed) – requiring corrective action. Include MS Outlook (email) generated reminder to the business line point of contact (POC). Also, a pop-up or similar feature which allows the POC to provide instructional information to feeder sites when the latter log-on to the application. Access/change-control and “lock out” for designated users, frameworks and data types – to prevent unauthorized data manipulation, especially of historical data – and, an audit trail. These must be easy to set up and administer. Include a super-user access level for the business line POC to allow validation of business line data from feeder sites without having to log out/log in for each site. Varied formats – text (clear-text or yes/no) and/or numeric (positive or negative; whole number or decimal) – that can be used to pre-define valid data entries and associated parameters, thresholds, and/or tolerance levels. Expanded text/numeric data fields, in limited instances (e.g., 500 characters for data definitions or commentary; 14 positive digits and 3 decimal). Required commentary for anomalistic, changed or out-of-tolerance data inputs, calculations or ratings – or for as desired explanations/rationale. Include MS Outlook (email) generated notice to users when a proposed and/or approved change is posted thereby enabling a current view of the data. Default/exception-based, user-specific data entry such that data fields a user is not required to update can be set to not expect/require any (or zero-based) data entry. Period constraints – to restrict data entry to values for a specific period (e.g., a month, a quarter). Metric Data Array/Calculation: Linking, sorting and tailoring of data for user-defined distinct/multiple frameworks (e.g., President’s Management Agenda, Balanced Scorecard(s) for various organizational levels, OSD Metrics – and strategic goals/targets or actual/index (tolerance) values which may be unique to (a) specific organizational level(s)). Setting of pre-defined, pre-established defaults (including definitions and formulas) for each framework at user-defined organizational levels (including clients and customers). Automatic cascading of “linked” data – to avoid duplicate entry. Performance rating(s) indicator(s) calculated – and color-coded – from either positive or negative numbers or text-based entries; rating(s) to be a combination of the color and the calculated result. This rating/text must be posted to the appropriate presentation/display summary. This is interrelated with the presentation/display summary requirement (first entry) under Data Presentation. Change tracking/audit trail summary that records such activity for a stated period (e.g., the past month). This is interrelated with the data entry requirement for access/change control/audit trail. Exception-based calculations such that data fields a user is not required to update for a specific period – or at all – are exempted from calculations for that period. Exportation to other applications (e.g., Excel, Access, SQL). This must be user-friendly and easy to complete. Linkage to/archive capability for historical data retained by DFAS in an Oracle database. Metric Data Presentation/Display: Varied user-defined (at desktop) and system administrator-defined (by default) presentation/display summaries (including, but not limited to, a briefing book metaphor for executive users (critical), charts, graphs, maps, scorecards, dashboards in canned/standardized (common) or customized formats) for a broad range of statistical (analytical) methods. The user or systems administrator must easily achieve customization, to include displaying multiple metrics on a single presentation/display summary. The latter may be needed to test/prototype a format before it is recommended/approved as a canned format. Restricted, interactive, web-based access, viewing (including trend comparisons and alternative formats), data change, and review/approval for the presentation/display summaries. A home page gadget or desktop icon is an acceptable solution. Robust user drill-down capability within each presentation/display summary that addresses the framework and organizational levels it represents. Text sections within the varied presentation/display summaries for providing commentary, explanations, rationale for anomalistic, changed or out-of-tolerance data inputs, calculations or ratings. This is interrelated with the expanded data field requirement under Data Entry. Comparison of current period and prior period data. The prior period is often the prior (rolling) 12-13 months or the prior fiscal year, although it may be the prior month or quarter. Access to historical data for trend analysis. This is interrelated with the prior requirement and the linkage requirement under Data Array. Allow for ‘what if’ scenario development and results while viewing a presentation/display summary, including a save (for future reuse without a need to recreate) or delete (for discard) option. Color-based or symbol-based indicator/alert to note improvement or decline from a previous period’s data – or when prior data may not be directly comparable due to changes in definition, formulas, etc. Section 508 compliance. Environment: Compatible with DoD’s/DFAS’ Microsoft Office/Windows NT-based technology. Presentable via a Plumtree-based ePortal. Funding (Cost): Within DoD’s/DFAS’ non-capital (<$250,000) threshold. The $250,000 is inclusive of: The software license and software installation. Orientation training. (See Training/Implementation Support) Troubleshooting, helpdesk support and maintenance during the first year. (See Technical Support) Exclusive of DoD’s/DFAS’ financial management business intelligence solution. Linkages: Compatible with DFAS’ Oracle database-based historical data repository. Systems Administration: A non-Information Technology (IT) trained/skilled user should not be needed to perform this function. Self-sustaining, vendor-independent on-going technical support, except as noted in the requirements under Technical Support. The goal is in-house maintenance unless unique circumstances dictate a need for vendor assistance, to include the introduction of application/module new releases/upgrades. Technical Support: On-line help icon that leads to a concise, context-driven help menu – inclusive of context-related drop-down options. Application/module-specific 24-hour/7-day help desk staffed by subject matter experts for the specific application/module. Emergency, on-call/on-site 24-hour/7-day expert assistance for the specific application/module. Access to and use of one of the prior requirements if the application’s/module’s new release or upgrade proves beyond or outside of the in-house system administrator’s technical capabilities. On-line, web-based initial or refresher training at any time. Training/Implementation Support – within 4-6 weeks of purchase at DFAS-named sites: 2-days planning/system administrator training; 1-day follow-up training (as needed, at a later date). 2-days to build/populate the application(s)/module(s). 2- days user training - for up to 100 full access and 100 read-only end-users; each session to be a ½ day (3-4 hours) (i.e., same session conducted 4 times); 1-day follow-up training (as needed, at a later date). This may include train-the-trainer sessions. Vendors are requested to submit 1. Cover Letter to include the company name, date of submittal, POC and any applicable GSA FSS schedule contracts or other existing Federal Government contract vehicles. 2. A capability statement that addresses the contractor’s ability to meet the requirement. Responses to the RFI must be submitted via email to
[email protected] by no later than 8AM Feb 7, 2005. No questions will be accepted by phone. This is not a request for proposal/quote and the Government does not intend to pay for information submitted. Respondents will not be notified of the results of the evaluation of the data received. This notice is not to be construed as a commitment by DFAS to contract for services. The use of the information submitted to DFAS as a result of this RFI will be at the discretion of the DFAS, and DFAS will not provide comments to any vendor’s submission