SPECIAL NOTICE
99 -- Form Bridge
- Notice Date
- 9/9/2009
- Notice Type
- Special Notice
- Contracting Office
- DEA Headquarters; 8701 Morrissette Drive Attn: FAC, Springfield, VA 22152
- ZIP Code
- 22152
- Archive Date
- 9/16/2009
- Point of Contact
- John Girard
- E-Mail Address
-
John.C.Girard@usdoj.gov
(John.C.Girard@usdoj.gov)
- Small Business Set-Aside
- N/A
- Description
- The Drug Enforcement Administration (DEA) has a requirement for the acquisition of FormBridge Software to convert the entire set of DEA forms from JetForm to InfoPath 2007.Line Item 0001: Conversion of 1584 pages of forms from JetForm IFD to InfoPath Browser formsLine Item 0002: FormBridge Development License, quantity 5 eachLine Item 0003: Form Bridge Training Course (1 day on-site for up to 6 people)This is anticipated to be a sole source purchase order to Texcel System, Inc under the test program described in the Federal Acquisition Regulation (FAR), Subpart 13.5, and under authority 41 U.S.C.253 (c)(1) as implemented by FAR Part 6.302-1. The Contracting Officer certifies the accuracy and completeness of the justification. The following FAR Part 12.3 provisions and clauses are applicable to this acquisition: 52.212-1 Intructions to Offerors - Commercial Items (JUN 2008); 52.212-3 - Offerors Representations and Certifications-Commercial Items (AUG 09); 52.212-4 - Contract Terms and Conditions - Commercial Items (MAR 2009); 52.212-5 - Contract Terms and Conditions Required to Implement Statutes or Executive Orders - Commercial Items (AUG 2009). Questions/comments will be accepted and may be email, or fax by 12:00pm. eastern standard time, September 11, 2009 to the primary point of contact in this announcement. No questions/comments will be accepted via telephone. All sou! rces may submit a quotation which will be evaluated. Responses must be submitted by 2:30pm. eastern standard time, September 16, 2009 via email to John.C.Girard@usdoj.gov Conversion technical details: 1. The JetForm form layout and field design will be retained with the following changes: Single character text fields in the JetForm forms which represent True/False or mutuallyexclusive selection will be converted to checkboxes and radio buttons (optionally with radiobutton behavior selected by mutually exclusive checkboxes). The vendor shall provide defaultexport values for radio buttons which can be updated later by DEA when DEA has fullydefined their data standards. JetForm text fields containing dates in standard formats will be converted to InfoPath datedata types. Other fields will retain their original data type. (DEA may want to change someof the data types in a follow-up phase to the project.) Some of the data on the JetForm forms was captured using a separate field for eachcharacter, e.g.: a social security number composed of 9 separate fields or a date with 3 fields(month, day, year). In most cases, these items will be combined into single fields to aid indata collection and to make the forms more user friendly. Small changes to the layout may be necessary in some forms to meet InfoPath renderingconstraints. (This is normal in any conversion due to differences in the source and targetforms environments.) 2. The calculations from the JetForm forms will be inserted in the InfoPath forms. 3. Multi-part forms will be presented as a single part for data entry and print. Printing of multiplecopies (with copy designators if present) will not be added as part of this effort, but can be addedwithin the form at a later date or through workflow. 4. Digital signatures will not be added as part of the conversion. They can be added in a future phase. 5. DEA uses Internet Explorer (v6 and v7). No testing will be done with other browsers as part of thisproject. 6. For the Group 1 forms (DEA202, DEA210, DEA48, DEA48a, DEA7, DEA7a, DEA7b, SSF,DEA284, DEA220, DEA220a, DEA12) if DEA is able to supply field names prior to the start of theconversion, they will be used for the converted forms. For the remaining forms, the vendor shall retain theoriginal JetForm names, where possible. 7. High quality Section 508 compatibility for any forms is not included in this initial requirement. 8. DEA will be responsible for adding additional functionality to the forms as necessary such as formsubmit capabilities, data retrieval and submission, custom programming, conditional formatting,and validations or rules other than those generated by FormBridge. Assumptions 9. The initial phase of the project will consist of planning and software development steps prior to thestart of the "official" forms conversion, including the following: The vendor shall create project conversion standards for review with DEA. It is important to fitthe standards within the bounds of what works well both with InfoPath and withFormBridge. During a conversion of this nature, there will be issues and decisions that must be made on individual forms and it is expected that these standards will allow the vendor to make the correct choices in most of these cases without interrupting the conversion workflow. Project procedures will be developed to cover the conversion workflow between the vendor andDEA to ensure that the conversion is done efficiently and meets everyone's expectations. The duration of this phase of the project is expected to be about 60 days. This will not delaythe project but will actually speed up the overall process for converting the entire set ofDEA forms. During this phase, the vendor shall provide conversions of some forms as part of thediscussion. 10. The project duration is anticipated to be approximately 9 months for the entire conversion. Note that forms can be put into production before the entire set is completed. 11. A payment schedule will be worked out and agreed to between DEA and the vendor. 12. Some DEA forms are very complex and it is challenging to get precise printing for them withInfoPath browser based forms, even with FormBridge, due to the nature of the InfoPath technology.The vendor shall develop an add-on Print Engine product that will provide PDF like print accuracy.DEA may choose to use this product to get more precise printing on complexforms. Forms converted before the availability of this component can be easily upgraded to workwith the Print Engine. This will also make the forms easier to maintain if the design changes. 13. Due to the large number and variety of forms, it is possible that some forms will have unforeseenissues that require time to resolve. In this case, the vendor shall move on to the conversion of other formswhile the issues are being discussed and resolved. In some cases, the vendor may provide preliminaryversions of a form for review within DEA and DEA will provide feedback in a timely manner. 14. The vendor will not be held responsible for bugs or limitations in InfoPath that could affect the operation of a form or which may require design changes from the original JetForm forms. 15. DEA will review completed forms within 2 weeks and either approve the forms or inform the vendorof any problems. The vendor shall fix issues within the scope of the conversion and resend the forms toDEA for another review, which will be within 1 week. 16. During the time of the conversion project, it is possible that DEA, DOJ, or OPM could change thedesign of one or more of the original forms. If the vendor has done work on any forms that have beenchanged, then a conversion of the changed forms is considered out of scope. 17. The DEA6 form is not being addressed as part of this initial effort.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/54fb9f1aa9feaa416c4f3586b009d170)
- Record
- SN01947118-W 20090911/090910000842-54fb9f1aa9feaa416c4f3586b009d170 (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 |