SOURCES SOUGHT
70 -- Case Management System
- Notice Date
- 8/17/2011
- Notice Type
- Sources Sought
- NAICS
- 423430
— Computer and Computer Peripheral Equipment and Software Merchant Wholesalers
- Contracting Office
- Department of Justice, Drug Enforcement Administration, Office of Acquisition Management, None, Washington, District of Columbia, 20537
- ZIP Code
- 20537
- Solicitation Number
- DJD-11-R-0049
- Archive Date
- 9/15/2011
- Point of Contact
- Amanda, Phone: 2023078337
- E-Mail Address
-
amanda.j.marsh@usdoj.gov
(amanda.j.marsh@usdoj.gov)
- Small Business Set-Aside
- N/A
- Description
- This is a REQUEST FOR INFORMATION (RFI). This is not a request for proposals and does not obligate the Government to award a contract. All responsible businesses, including small businesses, are encouraged to respond to this RFI. The Drug Enforcement Administration (DEA) is conducting market research and requests input from industry to assist in requirements planning. The information requested by this synopsis will be used within the DEA to facilitate the decision making process and will not be disclosed outside the agency. The DEA will not be responsible for any cost incurred by interested parties in responding to this RFI. Unsolicited proposals or offers of any kind will not be considered in response to this RFI. All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. At this time, questions concerning the composition and requirements for a future RFP, as well as those regarding the nature of the services to be performed under any future airborne imaging systems initiative will not be accepted. Email responses to this RFI to Amanda Marsh at amanda.j.marsh@usdoj.gov by 3:00 PM Eastern Standard Time (EST) on Wednesday, August 31, 2011. The Government encourages creativity and innovation in responses to this RFI. The purpose of this RFI is to gather information about commercially available case management systems that meet the requirements discussed below. Interested vendors should submit a technical description of their capabilities such as the number of users your application can support, any architecture(s) or configuration(s) necessary to support each range of users, licensing requirements, and any annual maintenance fee. Interested vendors should also submit Rough Order of Magnitude (ROM) pricing for their products to include system hardware, support, and installation. REQUIREMENTS The DEA is seeking information from potential sources for a case management system. The DEA requires a multi-user, case management system that supports customizable administrative law workflows, case tracking and reporting. The system should be compatible with Microsoft Windows client workstations and utilize a relational database management system (Oracle 10g/11g or SQL Server 2005/2008). Please address the following: • Ability to support the installation and configuration of a "proof of concept" system in DEA's development environment • Describe the number of users your application supports • Describe the architecture and/or configuration necessary to support each range of users • Total number of customer installation sites for the application • Average number of users at each installation site • Total number of customer installation sites supporting between 10 and 100 users • Describe the licensing and application requirements • Describe any services that are included in an annual maintenance fee (if applicable) • Provide details on ongoing support resources available for this application (process for requesting support, staffing level, availability, response times, knowledge base, etc.). • Does your application support strong password complexity ("strong password" refers to a password with a system-specified minimum length that also requires the use of a specified combination of lower case alpha, upper case alpha, numeric, and special characters)? • Can your application be configured to require strong password complexity? • Can your application be configured to enforce password aging? • Does your application support organizing users into customer-defined groups based on their application access and function? • Describe the requirements for configuring Single Sign On (SSO). • Explain how this role-based security is implemented (embedded in the application, via database capability, etc.)? • Auditing capability for changes made to data • Auditing capability for both successful and unsuccessful user log on events • Auditing capability for any other user actions or application events • Tools for reviewing and maintaining any application or database audit log(s) • Does your application require the use of a relational database management system? If so, can this database storage utilize either Oracle 11g or Microsoft SQL Server 2005/2008? If not, describe any required product(s). • Ability to export data via user OR administrator-accessible tools. Dscribe what data formats are supported (e.g., CSV, XML, txt, Excel spreadsheet, etc.) • Ability to import legacy data via user OR administrator-accessible tools • Client-side component(s) (.exe, active X, etc.) that must be installed on or downloaded to the user workstations, if applicable • Software used for report generation (e.g. Crystal Reports, Oracle Reports, etc.) • Report format(s) the software support (e.g. PDF, Excel, CSV, etc.) • Is the application Section 508 compliant? If Section 508 compliance is stipulated, please describe the validation process and tool(s) used. • Migration of existing legacy data (regardless of additional cost) • Encryption of associated case documents in their stored location (file server, database, etc.). If applicable, state encryption mechanism, algorithm, and FIPS compliance. • Does your application capture the following information: a. individual case information b. detailed notes and additional information associated with each case c. information related to hearing requests. d. information on pre-hearing statements e. information on pre-hearing ruling f. information related to the motions filed or supplemental pre-hearing statements dates of specific events/milestones such as the Issue PreHearing Ruling and Assignment of Cases to Judges etc. • Ability to generate a case docket numbers in a custom format? • Ability to create ad-hoc reports. Describe the tools required and process for creating ad-hoc reports. • Ability to modify any canned reports. If so, describe the tools required and process for modifying canned reports. • Capability of sending out e-mail alerts for upcoming, past, and overdue deadlines based on defined policies and statutes. • Is the software a full packaged application tailored to meet our needs out of the box? Or is it more of open shell type of software application that we would need to configure once installed to meet our needs? • Compliance with our current environment; Federal Information Security Management Act (FISMA) of 2002 Interested vendors who feel they possess the necessary capabilities should respond by providing the Government the following information: point of contact, address, telephone and fax numbers, email address, DUNS number, Tax ID Number, as well as size category (large, small, small disadvantaged, etc), a brief summary of the company's capabilities, personnel, related experience, and existing NATO, ISAF or US secured area credentials. Interested organizations should also include information regarding previous work similar to this requirement and, if applicable, whether this work was/is being done for other government agencies (and if so, the names of the government agencies).
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DOJ/DEA/OAM/DJD-11-R-0049/listing.html)
- Record
- SN02538170-W 20110819/110817235618-a445a65d02e15c3088aee9cb33cc777c (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |