MODIFICATION
D -- Enhancements to the TTB Specific Filemaker Pro Database
- Notice Date
- 8/8/2006
- Notice Type
- Modification
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Department of Health and Human Services, National Institutes of Health, National Cancer Institute, Office of Acquisitions, 6120 Executive Blvd. EPS Suite 600, Rockville, MD, 20852
- ZIP Code
- 20852
- Solicitation Number
- RFQ-NCI-60115-NV
- Response Due
- 8/15/2006
- Archive Date
- 8/30/2006
- Point of Contact
- Deborah Moore, Contract Specialist, Phone (301) 402-4509, Fax (301) 402-4513,
- E-Mail Address
-
dm170b@nih.gov
- Description
- This amendment is being issued to provide clarification on place of performance. The place of performance shall be at the contractor’s place of business and the contractor will only need to visit Rockville, Maryland to deliver the product if necessary. This is a combined synopsis/solicitation for commercial services prepared in accordance with the format in FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. This solicitation RFQ-NCI-60115-NV includes all applicable provisions and clauses in effect through FAR FAC 2005-11. The National Cancer Institute (NCI), Technology Transfers Branch (TTB) plans to enter into a contract with an organization to enhance the current Technology Information Management System (TIMS) database with enhanced features and re-program TIMS to maximize features of FileMaker 8.0 or most current version. The North American Industry Classification code is 541511, and the business size standard is $21M. This solicitation is set-aside for small businesses. Background: General Description: The Technology Transfer Branch (TTB) of the Federal Government’s National Cancer Institute (NCI) converted eight (8) individual and separate flat files of varying record size from FileMaker Pro (FMPro) version 4.1 into a FMPro 6.0 relational database referred to as the Technology Information Management System (TIMS). Contracts have been awarded to design the new relational database, to design a user interface, and build the database. The TTB now requires FMPro expertise to upgrade and enhance the database. Evolution of Requirements: A self-designed “unrelated” FMPro system had been used by TTB for the management and tracking of mission-related work since the early 1990s. In the late 1990's TTB determined that the number of records and the needs of the office had outgrown the capabilities of the “unrelated” database system. A relationally designed database to most efficiently maintain the integrity of and standardize the entry of data, to track mission-related efforts and to produce accurate and cogent reports was developed and has been in use since November 2002. TTB continues to enhance TIMS to meet the changing needs of NCI and TTB. Those needs include new technology transfer requirements, specialized reporting to the Office of the Director, NCI, and changes in TTB procedures. Purpose and Objective: The TTB is responsible for negotiating agreements between NCI scientist and private sector companies for the collaborative development of federally funded bio-medical research into commercially successful products. The Main focus of these collaborative efforts is to produce commercial products that will improve the public health. In addition, the TTB is also a Competitive Service Center (CSC) for technology transfer. Under the CSC, the TTB negotiates agreements for 10 other Institutes of the National Institutes of Health. One of the responsibilities of these collaborative agreements is to track the agreement negotiations from initial request to execution of the agreement, and through agreement expiration to final destruction of the physical file itself. This process can span several years and involve many tracking dates. TTB currently negotiates eight different types of agreements for the NIH. The specific objectives of this procurement are to: 1) enhance the current TIMS database with enhanced features such as reporting, advertising, action items, etc. and 2) re-program TIMS to maximize the features of FileMaker 8.0 or most current version. Statement of Work: PLACE OF PERFORMANCE: Shall be at the contractor's place of business and the contactor will only need to visit Rockville to deliver the product if necessary. CONTRACTOR REQUIREMENTS Specific Tasks to be Performed: The contractor shall provide technical skills, insights and expertise on FMPro database development and implementation. The contractor shall be a certified FileMaker Pro 8 developer. Due to the complexity of the information that is tracked in the TIMS database, the many inter-relationships of the various agreements, and the need to obtain and integrate into TIMS data from other databases which are written in different programming languages, the contractor shall have at least 10 years FMPro experience in order to perform the work. TTB shall provide all TTB mission-related information necessary to develop the database upon execution of contract. 1. Add additional features to the database from the list of projects below. The order in which additional features are selected to work on will be determined by a variety of factors such as needs of TTB, logical progression depending on re-programming (see 2 below), etc. 2. Re-program the current TIMS database in FileMaker Pro 8.0 to maximize the features of version 8 and enhance the current database structure, file structure and user interface and produce a Beta version: The contractor shall build all of the files with field definitions, create relationships between the files, show related data, and put business rules and constraints in place on field values. The contractor shall test the system for: 1) the database and file structure design, 2) the user interface for functionality. Once the system is upgraded, tested, and bug free, the Contractor shall provide a beta version to TTB for testing. The contractor shall install the Beta version on TTB's server and on 5 TTB staff members' computers. TTB Staff shall use the beta version for 10 business days and provide comments to the Project Officer. The Project Officer shall inform the Contractor of all comments. Corrections and changes shall be made by the Contractor within 30 days from of receipt of comments and corrections. The Contractor shall provide the final version of the system in a client/server format for about 51 TTB staff members. 3. The final product shall be Section 508 compliant. PROJECTS LIST: 1. Reports: a) Add ability to design or customize individual reports. b) Add/enhance ability to easily export report information into Word or Excel 2. Search Function: a) Enhance the search capabilities so they are more flexible and robust b) Add the ability to remove or omit specific records from a found set 3. General a) Create the ability, like in old FMPro to move from record to record in a found set without going back and forth to a list of records. b) The scroll feature needs work so that when you have scrolled down a list of records, selected and examined one record, and come back to the main screen, you will go to the record you selected and not up to the top of the list as it currently is set. [it is called Sticky Portal] c) Ability to add text to modules/records d) Link the status to the date field e) Add Spell Check option so that it offers ability to add names, etc. so they don’t come up again and again. [This may be a standard feature in FMP 8+] f) Make fields with pull down menus not modifiable 4. CRADA Module a) Program the amendments window to allow for page breaks and multi-page documents. b) Make it easier to generate a CRADA amendment c) The Amendment Form Header pulls from the same updated fields as the Clearance form, yet the information required for each is different. Program so it pulls in the current information in its fields, not the new information being added via the amendment. The latter should be captured in the body of the amendment. d) When the months for a CRADA amendment extension are entered in the record, have the expiration date be automatically recalculated by the system. e) Appendix C Language Changes table searchable for each paragraph and ability to review the language. 5. CTA Module a) Add Negotiator field and a specialist field in the CTA module as exists in all other agreement modules. 6. AdOps Module a) Redesigned 7. Extramural Invention Waivers a) Redesigned 8. Letters and Memos a) Have the ability to save modified letters for specific agreements within the agreement record in TIMS. [As a PDF file would be best. This would be helpful in moving to a “document management system”. Should also consider adding patent document to the EIR record, these document could include: OTT recommendation, original EIR, patent application, etc.] b) Have ability to print address labels from the contacts/org modules and to have the address merge into a letter. 9. EIR Module a) Add Automatic Action item to generate a report if the future “Cost Sharing” button is added. b) Add ability to pull the issued patent from USPTO website. This is relatively easy since there is a specific web-link for each Patent. I am sure this could be applied to the published patent applications, including foreign patents and patent applications. We just need the web-link information. c) Add ability to add post TRG items, similar to TRG Requests. This would help tracking the transactional development items in an EIR. 10. Action Items a) Move the Action Items toward an Agreement History, that is, remove the comments field and make every “comment” and Action Item a “History Item” b) Certain action items should be a mandatory part of what we do (one year post provisional, 18 months post PCT filing, 3 months prior to CRADA expiration, 2 months prior to CRADA LOI expiration). TTB to decide what things need to be mandatory action items, then Colleen will need to program. 11. Ability to set non-PHS/NIH contacts on Signatory List. Currently the user can only designate PHS/NIH Contacts as “signatory”. We need this function to identify a non-PHS/NIH Contact as signatory so their name appears on an agreement signature block. 12. Create and store .pdf of agreement related documents If standard NIH document with no modifications then .pdf of signature page is scanned, imported to TIMS and stored If standard NIH document with modifications then .pdf of entire document is scanned, imported to TIMS and stored If non-standard NIH document then .pdf of entire document is scanned, imported to TIMS and stored If printing an agreement, have the option to add a PDF file into TIMS (or specific location) See idea below (next bullet) for printing letter/memos/forms. (All scanned document are sent to a "default" location and stored so TIMS knows where to find them) 13. Have a feature added which asks User "is this final?" when printing letter/memo/internal document. This would eliminate the multiple Automatic Action Items when documents (Letters/Memos/Forms are printed multiple times before the User is satisfied. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (08-AUG-2006); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link to FedBizOpps document.
(http://www.fbo.gov/spg/HHS/NIH/RCB/RFQ-NCI-60115-NV/listing.html)
- Record
- SN01109749-F 20060810/060808223612 (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 |