SOURCES SOUGHT
D -- CDER Common Budget Tracking System
- Notice Date
- 1/18/2013
- Notice Type
- Sources Sought
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Department of Health and Human Services, Food and Drug Administration, Office of Acquisitions and Grants Services, 5630 Fishers Lane, Room 2129, Rockville, Maryland, 20857-0001
- ZIP Code
- 20857-0001
- Solicitation Number
- FDA-RFI-1113331
- Archive Date
- 2/15/2013
- Point of Contact
- Sherry Rowlett, , Jennifer Fagan,
- E-Mail Address
-
sherry.rowlett@fda.hhs.gov, jennifer.fagan@fda.hhs.gov
(sherry.rowlett@fda.hhs.gov, jennifer.fagan@fda.hhs.gov)
- Small Business Set-Aside
- N/A
- Description
- Request for Information From: Food & Drug Administration, Department of Health & Human Services Subject: Common Budget Tracking System (CBTS) -Center for Drug Evaluation (CDER) Date: January 18, 2013 THIS IS A REQUEST FOR INFORMATION ONLY AND YOUR RESPONSE IS NOT AN OFFER. THIS REQUEST FOR INFORMATION DOES NOT COMMIT THE GOVERNMENT TO PAY ANY COSTS INCURRED IN PREPARATION OF ANY SUBMISSION TO THIS NOTICE, OR TO CONTRACT FOR SERVICES. This Request for Information (RFI) is for information, planning and market research purposes only and shall not be construed as either a solicitation or obligation on the part of the Food and Drug Administration or its Centers. The purpose of this RFI is to help the FDA understand the market availability, functional and technical of solutions, and the Commercial of The Shelf (COTS) products and services capable of satisfying the business, functional, technical, and operational characteristics of available tools that can function as a Common Budget Tracking System as described in this RFI. FDA welcomes responses from all interested parties. FDA does not intend to make a selection decision or award a contract on the basis of responses nor otherwise pay for the preparation of any information submitted or FDA's use of such information. Acknowledgment of receipt of responses will not be made, nor will respondents be notified of the outcome of the FDA's evaluation of the information received. Additionally, the FDA does not intend to hold discussions concerning this RFI with any interested parties. I. General Requirements. The Center for Drug Evaluation and Research is a division of the U.S. Food and Drug Administration (FDA) that monitors most drugs as defined in the Food, Drug, and Cosmetic Act. The center reviews applications for new and generic pharmaceuticals, manages US current Good Manufacturing Practice (cGMP) regulations for pharmaceutical manufacturing, determines which medications require a medical prescription, monitors advertising of approved medications, and collects and analyzes safety data about pharmaceuticals that are already on the market. CDER reviews New Drug Applications to ensure that the drugs are safe and effective. Its primary objective is to ensure that all prescription and over-the-counter (OTC) medications are safe and effective when used as directed. The FDA's budget for approving, labeling, and monitoring drugs is roughly $290 million per year. The safety team monitors the effects of more than 3,000 prescription drugs on 200 million people with a budget of about $15 million a year. II. Centralized Budget Tracking System The standard accounting system in use by the Department of Health and Human Services and the Food and Drug Administration is known internally as Unified Financial Management System (UFMS), and is known commercially as Oracle Federal Financials. However, CDER Offices, Divisions, Branches and Teams with budget authority currently track expenditures through a variety of tools and templates such as in MS Excel and Access. Considerable staff time is devoted to the creation, maintenance and reconciliation of these "home-grown" tools. Errors are more likely since updates are manually added, and not in synchronization with disbursements or changes reflecting actual spend. Centralized monitoring of allocations and expenditures would improve budget management, especially in years where Congress has provided a shorter period of time for obligations. Because of these concerns, CDER is considering implementing a Centralized Budget Tracking System. Any Centralized Budget Tracking System should have the following characteristics: • Provide access to historical data at the Office, Division, Branch and Team levels of budget authority for reporting purposes; • Track all changes that are made by each user to foster user accountability; • Provide role-based access to data, with the ability to change information based on authority and responsibility; • Provide reasonable system speed, access, screen refreshes, and processing during times when multiple users are in the system; • Have the ability to receive a "push" of information from UFMS when updates are made. Examples include, but are not limited to: o Travel funding changing from order estimates to voucher disbursements o Projected obligations on purchase cards when purchases are made versus when bills are reconciled o Track requisitions as they move from obligations to commitments to disbursements • Must be compatible with Oracle Federal Financials software reports, including formatting (currency, object class code, fields, etc.) consistent with Oracle Federal Financials • Must conform to FDA/HHS security and infrastructure requirements. Please see http://www.hhs.gov/policies/hhsar/subpart352.html#Subpart352.2--TextsofProvisionsandClauses for minimum requirements. • Must contain all current fields in Excel and decide which are necessary, including tagging and comments • Must have the capability to sort by line items and category o Sort by system (UFMS, IMPAC, Transfers, ORISE, Taps) o Sort by module (e.g. Purchase Card: outstanding, actual, paid/not paid, partial payment field, travel, etc.) o Decision tree, open and close mechanism o Ability to track and sort projections by line item o Ability to add line items o Pull-down menu for object classes or any frequently-used codes. This field should be able to be updated. o Pull-down menu to label travel by object classes (e.g., conference, foreign, sponsor, domestic) to enable entry and reporting o Must track all types of operating money: grants, payroll center accounting number (CAN), operating center accounting number (CAN), and pivot table o Must be able to see sections within a division - from sub-team to super office level • Must provide various levels of access rights, including proxy entries. • Must have the ability to enter initial allocations and internal and external transfers with the ability to amend. • Must be able to distinguish between different funding sources. • Must have report design and running capabilities o Ability to answer both ad hoc and routine report request without rework o Any system must be able to generate reports with data obtained from Oracle Business Intelligence Enterprise Edition • Must be able to highlight any entry and see all details • Must be able to highlight any entry and see an explanation/comment field • Must have automatic generation of the next P# (Project Codes) using the same numbers as UFMS/Oracle Federal Financials (D#, GIF#) • Must flag differences and errors III. Instructions: Interested parties shall submit the following information along with other documentation that would help the FDA better understand the functional capabilities of available products/solutions. 1) Provide information on the COTS component(s) that might make up the overall CBTS solution. Include information on application compatibility, including supporting database management systems; hardware and operating systems; architecture; client architecture (such as web-based, client/server); support for handheld devices; performance impact; and scalability. Include information on the product's ability to interface and integrate with other FDA systems. Also include an overview of the COTS Software's ability to meet regulatory standards such as 21 CFR Part 58, 21 CFR Part 11, etc. 2) Provide a narrative overview of the COTS software's ability to support the core features, functions, data, and reporting needs of CBTS identified above. Please specify any functional areas that may require extensions or customization of COTS software. Also describe any CBTS components that may need to be or should be custom built. Include a brief rationale for any custom built components. 3) Provide a Rough Order of Magnitude (ROM). The ROM should take into account software licenses to support several hundred to several thousand users. 4) Explain whether or not your product adheres to Section 508 Accessibility Requirements which requires Federal agencies to ensure that individuals with disabilities who are members of the public or Federal employees have access to and use of electronic and information technology (EIT) that is comparable to that provided to individuals without disabilities. See http://www.access-board.gov/508.htm for more information. 5) Provide information concerning contract vehicles available to be used by the FDA in acquiring your product (GSA Federal Schedules, Government-wide Acquisition Contract, SmartBuy, etc.). 6) On the FACE PAGE of your submittal, please list the following information: a. Organization Name b. Name, email address, telephone number and mailing address of primary point of contact c. Organization Address, Telephone/Fax number d. Organization website e. Number of employees in organization f. Organization's current and gross revenue g. Organization's business size status (small or other than small business) h. Socio-economic status (small business, SDB, 8(a), WOSB, SDVOSB, HubZone, etc.) 7) Please suggest an appropriate North American Industry Classification System (NAICS) code and rationale. Please submit responses to this RFI in accordance with the following: 1) A submittal not to exceed five (5) pages (excluding transmittal page) that, at a minimum, addresses each of the topics described in the Instructions section; 2) Submit your response via email to sherry.rowlett@fda.hhs.gov 3) Deadline for responses is 12:00 P.M. ET on 31 January, 2013; 4) Mark your response as "Proprietary Information" if the information is considered business sensitive.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/HHS/FDA/DCASC/FDA-RFI-1113331/listing.html)
- Place of Performance
- Address: 5630 Fishers Lane, Rockville, Maryland, 20857, United States
- Zip Code: 20857
- Zip Code: 20857
- Record
- SN02968726-W 20130120/130118234319-1a5bf80cb8dd0d90ff7bc46f6cee5a54 (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 |