Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF NOVEMBER 05, 2016 FBO #5461
SOURCES SOUGHT

R -- Machine Foreign Language Translation System (MFLTS) – Rapid Development of Dari and/or Sorani Kurdish Speech-to-Speech Translation Language Packs

Notice Date
11/3/2016
 
Notice Type
Sources Sought
 
NAICS
541930 — Translation and Interpretation Services
 
Contracting Office
Department of the Army, Army Contracting Command, ACC - APG (W909MY) Belvoir, 2461 Eisenhower Avenue, Alexandria, Virginia, 22331, United States
 
ZIP Code
22331
 
Solicitation Number
W909MY-17-R-A002
 
Archive Date
12/20/2016
 
Point of Contact
Wanda Noblin, , Rosetta Wisdom-Russell,
 
E-Mail Address
wanda.m.noblin.civ@mail.mil, rosetta.wisdom-russell.civ@mail.mil
(wanda.m.noblin.civ@mail.mil, rosetta.wisdom-russell.civ@mail.mil)
 
Small Business Set-Aside
N/A
 
Description
REQUEST FOR INFORMATION: THIS IS NOT A SOLICITATION. No award will be made as a result of this request. This Request for Information (RFI) is for informational purposes only; this is not a Request for Proposals (RFP), or Request for Quotations (RFQ). No solicitation document exists and a formal solicitation may or may not be issued by the Government as a result of the responses to this RFI. The Government will not be liable for payment of any RFI response preparation expenses and is in no way obligated by the information received. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained in their response. NOTE: The use of RFI Number W909MY-17-R-A002 is for tracking purposes only. BACKGROUND/DESCRIPTION: Army Contracting Command-Aberdeen Proving Ground-Fort Belvoir (ACC-APG-Belvoir) is conducting market research on behalf of Program Executive Office Intelligence, Electronic Warfare and Sensors (PEO IEW&S), Product Director, Machine Foreign Language Translation System (PD, MFLTS) in accordance with Federal Acquisition Regulation (FAR) Part 10. MFLTS consists of open architecture software and language component software. MFLTS is a software only capability that provides an automated foreign speech and text translation capability in order to augment and complement limited human linguistic resources across all Army echelons in all environments. The MFLTS software application resides on portable, mobile and web-enabled host hardware. Initial MFLTS capability supports translation of two spoken languages (Pashto, Iraqi Arabic), one written language (Modern Standard Arabic), and two language domains (Checkpoint Operations & Base Security). In the future MFLTS will continue to be improved with new languages, additional language domains, and technical improvements throughout the product's Total Life Cycle. REQUIREMENT: MFLTS requires rapid development capability, given off-the-shelf linguistic resources (speech translations in defined domains and/or existing language components) and limited language data collection, in order to deliver a militarily useful translation capability to meet immediate operational needs. This RFI seeks to identify sources having an interest and capability to provide rapid development of Dari and/or Sorani Kurdish Speech to Speech (S2S) translation language packs within the Government owned MFLTS open software architecture, implemented for the portable configuration (i.e., standalone, Android based hand held computing device with no network connectivity) and supporting designated language domains. Vendors should refer to the following MFLTS software architecture documentation, which is available upon vendor request: 1. MFLTS Technical Requirements Document Volume 1: Architecture Specification; 2. MFLTS Technical Requirements Document Volume 2: CILABL Application and Language Component Development Guide; 3. MFLTS Software Development Kit (SDK) and Sample Language Components (LCs). 4. MLTS Data Corpora Guidelines Requests for MFLTS software architecture documentation must be sent via e-mail to Wanda Noblin, Contract Specialist, at wanda.m.noblin.civ@mail.mil, cc Rosetta Wisdom-Russell, Contracting Officer, at rosetta.wisdom-russell.civ@mail.mil, and George Smith, Technical POC, at george.w.smith306.civ@mail.mil. No request via telephone will be accepted. Include RFI number W909MY-17-R-A002 in the subject line and the following information: 1. Vendor Name: 2. Address: 3. CAGE Code: 4. POC Name, Phone # and email: RESPONSES: All responsible sources are requested to identify their interest and capabilities by submitting a White Paper response. White Papers must be no longer than five (5) pages and must be in a Microsoft Word compatible format or Portable Document Format (PDF), with the following parameters: 1. Font: Arial (All Text) 2. Font Size (Narrative): 12pt 3. Font Size (Figures & Tables): no less than 8pt 4. Font Color: Automatic (Body Text & Headings) 5. Line Spacing (minimum): Single (1.0) 6. Page Size: 8.5" x 11" 7. Page Margin (Word): 1" Left, right, top, bottom 8. Page Number Location: Bottom Center White Paper responses MUST include the following: Provide the following information about your company. If submitting a team response, please include the requested information for all companies on the team. a) Company Name b) Point of Contact, Phone Number, Email Address c) Company Address d) Website (if available) e) Contact Phone Number f) Business Type (e.g., Large Business (LB) Concern - Small Business (SB) Concern - 8(a) - Small Disadvantaged Business (SDB) - Woman-Owned Small Business (WOSB) - Historically Underutilized Business Zone (HUBZone) - Veteran-Owned Small Business (VOSB) - Service-Disabled Veteran-Owned Small Business(SDVOSB) g) Cage Code and DUNS Number Note: Please identify your company's small business size standard based on the primary North American Industrial Classification System (NAICS) code of 541930 and 1 secondary NAICS code of 334220. The Small Business Size Standard for NAICS code 541930 is $7.5 million and for NAICS code 334220 is 1,250 employees. For more information, refer to http://www.sba.gov/content/table-small-business-size-standards. 1. Brief summary of the company, limited to 3 paragraphs. 2. If you identify your company as any of the SB subcategories as stipulated above, then is your company interested in a prime contract for the above requirements? 3. Under the current SB recertification regulations, do you anticipate your company remaining a small business, under primary NAICS 334220? If you are a SB answer questions 3A & B. All others skip to Question #4. a) As a SB and your company is awarded the contract, will you be able to perform at least 50% (percent) of the work Also, does your company possess the capabilities to provide the entire range of these requirements? If not, please list which requirements your company can provide? b) If you are a small business, can you go without a payment for 90 days? 4. Does your firm possess an approved Defense Contract Audit Agency (DCAA) accounting system? 5. Does your company possess the capabilities to provide the entire range of services called for in the above requirements?______ YES _______ NO 6. If you answered YES to Question # 5, please provide specific capabilities and examples for how your company can provide these services. 7. Is your company planning on business arrangements with other companies, please list the process used in selecting the members? 8. Please provide details regarding proposed joint ventures, teaming arrangements, strategic alliances, or other business arrangements to satisfy the above requirements. Offerors are encouraged to identify teams, indicating each team member's size based upon the NAICS code of the work that the team member may be doing. 9. Is your company currently providing similar services to another government agency (you may also include contract #s for government) or other non-government customer? If so, please identify the agency or non-government customer. If you are unwilling to share your customer's identity, please address whether your company offers the same or similar services commercially. 10. Has your Company performed this type of effort or similar type effort (to include size and complexity) in the past, if so provide Contract Number, Point of Contact (POC), e-mail address, phone number, and a brief description of your direct support of the effort? 11. What are the core competencies of your employees that would support the above requirements? Also, provide the total number of individuals currently employed by your company that are capable of supporting the above requirements. 12. Does your company have a SECRET facility or access to one should it be required. 13. Do all the employees that would support the above requirements have a SECRET Clearance? 14. Existing Government Contracts: Indicate if vendor is currently on any Federal Supply Schedules, Government wide acquisition contracts, multi-agency contracts, and any other procurement instruments intended for use by multiple agencies. If yes, provide contract name(s) and number(s). 15. Discussion of vendor's approach to providing a Dari two way S2S translation language pack for MFLTS. In this section the vendor should address the following: 16. a. Identify and describe any pre-existing Dari language data the vendor possesses. 16. b. Identify and describe any previously vendor developed Dari two way S2S language application(s). 16. c. Describe the technical concept and provide the estimated schedule and Rough Order of Magnitude (ROM) cost for collecting additional language data (see note 1), developing the S2S language pack, integrating into the MFLTS software architecture, and providing one year of post-delivery software maintenance. The technical concept section should address, at a minimum, the following: 1) overview of planned data collection efforts, to include the total number of hours of general speech data, number of hours of domain-specific speech data per domain to be collected, and the total number of hours of speech data for ASR training (along with the target number of distinct voices to be used); 2) description of the proposed S2S language pack, to include the Automatic Speech Recognition (ASR), Machine Translation (MT), and Speech Synthesis (also referred to as text-to-speech) components; and 3) summary of the approach to develop and integrate the language pack. The schedule must include, at a minimum, the timeframes (in weeks) for: 1) language data collection; 2) S2S language pack development; and 3) integration into the MFLTS baseline. The ROM must, at a minimum, provide a breakdown by: 1) language data collection; 2) S2S language pack development and integration; 3) one year of software maintenance; and 4) any applicable software licensing fees. 16. d. Vendor's proposed Government data rights for language data and language pack software (see note 3) delivered under this effort. 17. Discussion of vendor's approach to providing a Sorani Kurdish two way S2S translation language pack for MFLTS. In this section the vendor should address the following: 17. a. Identify and describe any pre-existing Sorani Kurdish language data the vendor possesses. 17. b. Identify and describe any previously vendor developed Sorani Kurdish two way S2S language application(s). 17. c. Describe the technical concept and provide the estimated schedule and Rough Order of Magnitude (ROM) cost for collecting additional language data (see note 1), developing the S2S language pack integrating into the MFLTS baseline, and providing one year of post-delivery software maintenance. The technical concept section should address, at a minimum, the following: 1) overview of planned data collection efforts, to include the number of total hours of general speech data, number of hours of domain-specific speech data per domain to be collected, and the total number of hours of speech data for ASR training (along with the target number of distinct voices to be used); 2) description of the proposed S2S language pack, to include the Automatic Speech Recognition (ASR), Machine Translation (MT), and Speech Synthesis (also referred to as text-to-speech) components; and 3) summary of the approach to develop and integrate the language pack. The schedule must include, at a minimum, the timeframes (in weeks) for: 1) language data collection; 2) S2S language pack development; and 3) integration into the MFLTS baseline. The ROM must, at a minimum, provide a breakdown by: 1) language data collection; 2) S2S language pack development and integration; 3) one year of software maintenance; and 4) any applicable software licensing fees. 17. d. Vendor's proposed Government data rights for language data and language pack software (see note 3) delivered under this effort. Note 1: The Government will provide documentation in the form of task lists and scenarios for the vendor to use in collecting the domain-specific language data. Note 2: All proposed vendor solutions must be capable of being implemented within the MFLTS software architecture, for the portable configuration (i.e., standalone, Android based hand held computing device with no network connectivity). Note 3: The Government requires Unlimited Rights for all language data collected using Government funding. The vendor will provide copies of all language data collected using Government funding, to include annotation, transcriptions, and translations, separated by domain where applicable, to the Government. The Government desires Government Purpose Rights for language pack software. If proposing other than Government Purpose Rights for language pack software, provide the justification. NO TELEPHONIC INQUIRIES WILL BE HONORED. White Papers shall be submitted via email to Wanda Noblin, Contract Specialist, at wanda.m.noblin.civ@mail.mil, cc Rosetta Wisdom-Russell, Contracting Officer, at rosetta.wisdom-russell.civ@mail.mil, and George Smith, Technical POC, at george.w.smith306.civ@mail.mil within 30 calendar days of the date of this notice. Include RFI number W909MY-17-R-A002 in the subject line. SUPPLEMENTAL MATERIAL: Vendors may submit supplemental material, in the form of briefings, product descriptions, data sheets, information papers, etc. as desired. Supplemental material is not subject to page limitations or format restrictions. Supplemental material shall be submitted through one of the following: 1. In writing by e-mail to Wanda Noblin, Contract Specialist, at wanda.m.noblin.civ@mail.mil, cc Rosetta Wisdom-Russell, Contracting Officer, at rosetta.wisdom-russell.civ@mail.mil, and George Smith, Technical POC, at george.w.smith306.civ@mail.mil. Include RFI number W909MY-17-R-A002 in the subject line. 2. U.S. mail to ACC-APG - Washington, ATTN: Rosetta Wisdom-Russell, 10205 Burbeck Road, Fort Belvoir, VA 22060-5863; or 3. Facsimile to the attention of Rosetta Wisdom-Russell at 703-704-0800. Include RFI number W909MY-17-R-A002 in the subject line. All requests for additional information must be made in writing via e-mail to Wanda Noblin, Contract Specialist, at wanda.m.noblin.civ@mail.mil and Rosetta Wisdom-Russell, Contracting Officer, at rosetta.wisdom-russell.civ@mail.mil. Include RFI number W909MY-17-R-A002 in the subject line.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/e6aa56cc16c4b34fef88060b91a36c42)
 
Place of Performance
Address: ACC-APG - Belvoir, 10205 Burbeck Road, Fort Belvoir, Virginia, 22060-5863, United States
Zip Code: 22060-5863
 
Record
SN04319876-W 20161105/161103234522-e6aa56cc16c4b34fef88060b91a36c42 (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.