Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF AUGUST 22, 2010 FBO #3193
MODIFICATION

B -- DLNR-DAR Data Entry

Notice Date
8/20/2010
 
Notice Type
Modification/Amendment
 
NAICS
518210 — Data Processing, Hosting, and Related Services
 
Contracting Office
Department of Commerce, National Oceanic and Atmospheric Administration (NOAA), NOAA-Pacific Islands Fisheries Science Center, 2570 Dole Street, Honolulu, Hawaii, 96822-2396, United States
 
ZIP Code
96822-2396
 
Solicitation Number
PIFSC-10-052
 
Archive Date
9/11/2010
 
Point of Contact
Bonnie Oshiro, Phone: 8089835356
 
E-Mail Address
bonnie.oshiro@noaa.gov
(bonnie.oshiro@noaa.gov)
 
Small Business Set-Aside
Total Small Business
 
Description
Q1: On page 2 at the bottom of the first paragraph of the Statement of Work it states, "out of state processing of data entry restrictions apply." Can you provide specific details about these restrictions? A1: The awarded contractor is required to sign a non-disclosure of Confidential Data agreement (NAO 216-100). Q2: Can the work be completed outside of the State of Hawaii? A2: Yes. Q3. Output coded (key-punched) records with Multi Value Fields within the same documents or coded with each value coded as a separate document? What is the format of the output record? A3. As stated in the RFQ, the output record is a flat record format. All header (and footer) data fields will be repeated for each of the detail (body) catch records. For example, if a report contains three lines of detail catch data, header information such as "Licensee Name" will be repeated for each of the three detail catch records. See attached example of one the output file Q4: Also, I notice your pricing is set up not by the record or I am not sure how you want it priced. Could you clarify that please? Do you want pricing by unit form or by unit keystroke or by unit labor hour ? A4: We are requesting pricing by unit record as it relates to the entire job of 730,000 records. Q5: Can you tell us the estimated volume of records that have to be keyed and verified? A5: As stated on the RFQ, it is an estimated total of 730,000 (flat) records; however, payment will be based on the total number of records processed (punch-verified) that meet quality control standards set by DAR staff. Q6: Will you provide all the scanned Tiff images at one time to us or by batch and transmit X images every day or week or month? A6: Scanned TIFF images will be provided to the contractor in batches. Each batch may contain 1,000 to 4,000 images. Each batch may contain one or more type of forms. It is the contractor's responsibility to provide punched-verified data by form level when submitting the data. Batches will be transmitted to the contractor depending on: 1) the volume of key-punching that can be completed by the contractor; 2) the number of scanned images available to be compiled by DAR staff; and 3) the quality of records submitted by the contractor. In general, we are expecting a daily delivery of the punched-verified data files and the contractor should have enough images to key punch the data for the next day. However, depending on the performance of the conversion of the images (see RFQ PIFSC-10-053 contract), images may not be available in a timely manner. Q7: In the sample forms provided, there could be more or less keystrokes (characters) than in the sample database field list (Records Layout by Form Type). Is the "Total Key Strokes Per Record" that is on the bottom of every form type table an average of what is on the actual forms? If this is not an average, is there an average that we can use and what does this number actually represent? For example, in the FISH CATCH REPORT FORM C-2 sample, the sample database field list lists 284 keystrokes per records, however the sample form actually has 234 keystrokes plus the "Image file name" field and the "Data is not Clear" field. This would be very close to the 284 keystrokes per record, and is conceivable to be either an average or an actual count for this sample (if the path is long). A7: The total number of key stroke at the end of each form is the maximum possible keystrokes required per record. The number of the actual per record key strokes is less than this number and should not exceed this number. You can use this number to estimate the per-record cost pricing. Q8: Can you please define "Punch-Verify"? Is this the same as "double key entry" or "Key, Key, Compare"? A8: Punch Verify method - data is entered first by worker A and then re-enter again by worker B (from the same form). If values entered by worker B is different than A (for each record), than someone must verify the record and correct the data. Q9: Is it possible to get sample images from the actual collection for quality inspection purposes? A9: State of Hawaii, DAR office will not release the actual image unless contractor has sign the non- disclosure statement. Q10: Will the images be delivered to the contractor grouped by data collection category, chronologically, mixed or other? A10: Most likely just by month and form type. Q11: Should the batches be sent to DLNR-DAR on a daily basis via electronic transmission or on physical media? A11: By physical media is required, as it is proof of delivery of the products. Q12: Will the winning contractor be able to receive all of the images at once, or will they be released over time? A12: Please refer to answer to question #6 above. Q13: If the images will be released over time, what volume level can be expected per month? A13: Please refer to answer to question #6 above. Q14: Can the contractor submit an invoice monthly instead of every 30,000 records? A14: No. Invoice is based on each 30K records submitted and passes the QC as described in the contract. Q15: Will this be a best price or best value award? A15: Technically accepted lowest price. Q16: Is this a new procurement or a follow on procurement? If a follow on, who is the incumbent contractor and what is the contract #? A16: This is a new procurement. Q17: In the SOW, paragraph 1 references a "record". Based on the description it seems a record is all the data elements within a form and that there several form types. Can you confirm a record is a whole form? A17: A "record" is not the form, it parts that make up the form. Each species caught on the form is considered one record. Ie. Looking at microfishe sample form-1 in the FBO attachments - First page Hapuupuu would be considered record 1, Kahala would be record 2, etc.... Q18: If this collection has 730,000 records does that mean it is 730,000 images? A18: It is an estimated of total number of records. See Q17 for definition of "record". Q19: Last sentence, paragraph 1, SOW: What does "additional non-disclosure agreement and out-of-state processing of data entry restrictions apply" mean? A19: The awarded contractor and any subcontractors are required to sign a non-disclosure of Confidential Data agreement (NAO 216-100). Q20: #2a, paragraph 3, SOW: What is the batch size referenced? A20: Refer to question # 6 for this information. Q21: Can the images be sent to Mexico or India for keying? A21: Yes, but if the primary contractor is subcontracting the work, the primary must do at least 51% of work. Q22: I just noticed there are only 5 record layouts provided with the bid information but the SOW refers to A22: Sample has 6 records. Q23: What is the required response to the RFQ? In the Synopsis/Solicitation Cover Page is says to provide detailed information concerning capability including references and details as to knowledge and ability. Can you elaborate on what is needed to be compliant? A23: List of capabilities stating knowledge and ability to accomplish the work, and a list of references for projects completed that were of a similar nature to the work described in the SOW. Q24: How will responses be evaluated? A24: See Q23.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/7d74c3f536cc1d64dbe35d16421eebba)
 
Record
SN02248514-W 20100822/100820234912-7d74c3f536cc1d64dbe35d16421eebba (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.