RFQ_Amendment_000005,_NIHES201800013,_Language_Translation_Scientific_Services.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICAITON NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicble)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICIATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a)By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPIRATION DATA (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc. ) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION ( Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

NIHES201800013 - EHP Language Translation Scientific Services

000005

.No. Reference Questions Answers

Attachment

V – Sample

Task Order

Statement of

Work

We have just completed the translation sample as part of our bid and would like to request the DTD file and documentation so we can complete this part of the submission. Is this something that will be provided to all bidders?

The necessary DTD is specified in the sample XML file (and the SOW), and the files are publicly available (from the NLM). Vendors who are skilled in working with XML should have no problem retrieving this.

Additionally, as stated in RFQ Amendment 000003, response to question 9, instructions on how to format the metadata (specific ISSNs, journal titles, etc.) will be provided to the awardee. It’s still in development and not yet available. The only requirement there is that the provided XML file be valid and free from parsing errors, as stated in the SOW.

Attachment

V – Sample

Task Order

Statement of

Work

I am now a bit confused based on the 3rd Amendment to the solicitation. Item 7 specially states “The deliverable XML file should contain only one language, which is the language specified in the Task Order. “

We delivered a Simplified Chinese XML file and were given the feedback that our inability to preserve the English content in the

XML somehow suggests we were not able to follow the instructions.

Can you clarify which is the correct way to send the XML file back? Should we leave the English and Add the other language(s), or just send back a translated XML file into one target language?

NOTE: The capability statements and sample translation texts received as a result of the sources sought notice under NIEHS201800013 was used to support market research efforts for this acquisition. Any feedback provided to vendors from the review of the capability statements is not meant to facilitate exchanges or discussions or negotiations relative to the

RFQ NIHES201800013.

The questions indicate that the vendor probably did not read or thoroughly read the draft SOW that was included with the sources sought notice. The draft SOW (page 2 of 15), Section 4.1 stated in broad terms what was entailed in the Government’s requirement for Translation

Support Services. Relative to the Simplified Chinese XML file delivered with the capability statement for which feedback was given, here’s the relevant text from that draft SOW, with the parts (bordered in bold red) most relevant to this question:

NIHES201800013 - EHP Language Translation Scientific Services

000005

First, the instructions indicate that the vendor should “add” the translation to the XML, not replace (or subtract) the English (that language is clear). It also indicates that the vendor needs to make use of the translated elements in the DTD, which specially provides a model for both languages to be present. If they’ve done translations in XML before, this shouldn’t be a new requirement. Second, why would we require that the vendor ensure no errors would be introduced in the English content if it was to be removed? We wouldn’t care what that XML looked like if it didn’t need to be there. Some vendors payed attention and got this right. For those that didn’t, it was pointed out in the review.

Relative to Attachment V – Sample Task Order Statement of Work released with the actual

RFQ, the following instructions were included:

The answer is that the file should have contained both the original English and the new

Chinese. Basically, the structure of the original XML file will be completely preserved during the translation process.

NIHES201800013 - Government's Responses to Industry Questions

National Institute of Environmental Health Sciences Research Triangle Park, NC 27709

National Institute of Environmental Health Sciences Research Triangle Park, NC 27709

The purpose of this Amendment is to provide the Government's FINAL responses to additional Industry questions. See pages 2 and 3 of the Amendment. Note the following:

(1) The period for questions has really closed; and

(2) The RFQ closing date remains Monday, September 10, 2018 at 10:00 AM ET.