FedBizOpps banner

Login to begin searching the FBO/CBD
Home Page
CBD/FBO Online
CBD/FBO Email
About Us
Contact Us
Privacy
Categories
No. Notes
Archives
Search
Help
Login
Register

Popular Searches

Popular Categories

Automated Point Cloud Feature Attribution for Synthetic Environments - Amendment 1

General Information

Document Type:MOD
Posted Date:Aug 31, 2017
Category: Training Aids and Devices
Set Aside:N/A

Contracting Office Address

Department of the Army, Army Contracting Command, ACC - Orlando (W900KK), 12211 Science Drive, Orlando, Florida, 32826-3224, United States

Description

RWP - Amendment 1 Request for White Papers: Automated Point Cloud Feature Attribution for Synthetic Environments Other Transaction AMENDMENT ONE *****Amendment 1 changes are incorporated below. The attached PDF file has all changes captured in highlighted and/or strikethrough text.***** 1.0 Purpose: This Request for White Papers (RWP) is issued to seek vendors capable of fulfilling the technology objective outlined below related to automated point cloud feature attribution for synthetic environments. 2.0 Summary: The U.S. Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI) is interested in using three-dimensional (3D) Point Clouds collected through photogrammetry, Light Detection and Ranging (LIDAR), or other similar sensors to rapidly generate synthetic terrain for current and emerging Training Aids, Devices, Simulators, and Simulations (TADSS). Current Government-sponsored research has successfully demonstrated that high-resolution visual representations of terrain can be generated through the automated processing of 3D Point Clouds; however, technical gaps still exist when automating the attribution of this data for direct application into TADSS. Improvements in processing 3D Point Cloud data are needed for better feature detection, classification, and segmentation so that the resulting terrain representation can more efficiently and effectively be used for training. This project will allow the Government to assess the technical feasibility of automating feature classification and segmenting 3D Point Clouds. The Army Contracting Command-Orlando intends to competitively issue this effort as an Other Transaction Agreement (OTA) in accordance with 10 U.S. Code § 2371b. The subject request, and resultant agreement, is not considered procurement contract and is not subject to Federal Acquisition Regulations. This effort is anticipated to be issued as W900KK-17-9-0001. The Government has $170,000 of funding available at this time to conduct this effort. While additional funding may become available in the future, responses should be submitted within the framework of the current $170,000 available. If your overall solution exceeds the current amount of funding available, we request that you still explain your total solution in the event that the Government is able to fund those additional features/capabilities beyond those which you are proposing within the $170,000 limitation. Paragraph 5.2 (c) requests pricing for any follow-on activities or additional paths. 3.0 Technical Objectives: Three major technical objectives will be assessed through this project. 3.1 Technical Objective #1: Accurate classification and differentiation between disparate terrain features /objects. Different classes of objects need to be processed differently to enhance visual quality of terrain (i.e. buildings, terrain formation, vegetation, atmospheric clutter). Identification of processing-intensive features for substitution by geo-typical models (e.g. substitute complex vegetation with geo-typical 3D tree models). 3.2 Technical Objective #2: Accurate classification and segmentation of terrain surfaces (i.e. roads, rivers, ground, etc.) Terrain surfaces must be classified properly based on their material composition in order for them to be attributed properly to ensure simulation entity trafficability and artificial intelligence (AI) path planning. 3.3 Technical Objective #3: Accurate identification of building elements. Building elements (i.e. building type, building materials, windows and doors) must be properly identified to promote accurate mission planning and rehearsal. 4.0 Technical Requirements: Please see RWP Attachment 1, 3D Point Cloud Technical Requirements. 5.0 White Paper Responses: 5.1 Interested parties are requested to provide white paper responses outlining possible technical solutions, capabilities, and critical cost/schedule drivers related to the technical objectives and requirements. 5.2 In addition to a full technical response, respondents shall address the following areas: a) Price and Schedule - provide a proposed total price and milestone payment and delivery schedule within the structure of the technical milestones outlined. b) Data Rights Assertions - please outline any restrictions related to intellectual property rights, to include a clear outline of technical data to be delivered to the Government with your solution. c) Follow-on Potential - please provide a short statement outlining the possibility and path forward to leverage your solution into broader use. This should include estimated pricing for any realistic short-term efforts that could be conducted as follow-on activities or additional paths forward. d) Issuance Eligibility - provide your nontraditional* business status or your ability to meet the eligibility requirements in 10 U.S. Code § 2371b. Within your response, please check the following box which applies - with appropriate justification if applicable.  There is at least one nontraditional defense contractor participating to a significant extent in the prototype project.  All significant participants in the transaction other than the Federal Government are small businesses or nontraditional defense contractors.  At least one third of the total cost of the prototype project is to be paid out of funds provided by parties to the transaction other than the Federal Government. *Nontraditional - an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense (DoD) for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section. 5.3 The cover page of the response shall include the company name, Commercial and Government Entity (CAGE) Code (if available), nontraditional DoD contractor status, address, point of contact including phone number and email address. Responses shall be submitted in Microsoft Word format and limited to no greater than 10 pages. 6.0 White Paper Evaluations: 6.1 Individual white paper responses will be evaluated with consideration given to the technical merit of the response, feasibility of implementation, and total project risk. The proposed project price, delivery schedule, and data rights assertions will be considered as aspects of the entire response when weighing risk and reward. Further, the Government will evaluate the degree to which the proposed concept provides an innovative, unique approach to meeting the technical objectives. 6.2 The Government will issue an OTA to the respondent(s) whose white paper will be most advantageous to the Government, price and other factors considered. 6.3 The Government may issue more than one OTA under this announcement. 7.0 Responses: The response shall be due no later than 12:00 PM Eastern Standard Time (EST) on 21 September 2017. The responses shall be emailed to Mr. Brian Serra, brian.d.serra.civ@mail.mil and Mr. Iain Skeete, iain.skeete.civ@mail.mil. 8.0 Additional Information: 8.1 It is generally desired that active R&D is underway for concepts submitted under this effort. Active R&D includes analytical studies and laboratory studies to physically validate the analytical predictions of separate elements of the technology, as well as software engineering and development. 8.2 The costs of preparing and submitting a white paper(s) is not considered an allowable direct charge to any contract or agreement. 8.3 Export controls: research findings and technology developments arising from the resulting White Paper may constitute a significant enhancement to the national defense and to the economic vitality of the United States. Any concerns related to compliance with International Traffic in Arms Regulation (22 CFR 120-130), the National Industrial Security Program Operating Manual (DoD 5220.22-M) and the Department of Commerce Export Regulation (15 CFR 730-774).shall specifically state so in their white paper response. If it is believed that an exception applies, please provide. 8.4 All submissions shall be unclassified. White papers containing data that is not to be disclosed to the public for any purpose or used by the Government except for evaluation purposes shall include the following sentences on the cover page: "This white paper includes data that shall not be disclosed outside the Government, except to non-Government personnel for evaluation purposes, and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this submission. If, however, an agreement is issued to this Company as a result of -- or in connection with - the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent agreed upon by both parties in the resulting agreement. This restriction does not limit the Governments right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]" 8.4.1 Each restricted data sheet should be marked as follows: "Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this white paper." 8.5 Follow-on contracts or transactions may be awarded/issued to the participants in this transaction without the use of competitive procedures, as competitive procedures are being used for the selection of parties in this selection, if the prototype project is successfully completed.

Original Point of Contact

POC Brian D Serra, Phone: 407-208-3357, Iain Skeete, Phone: 407-208-3347

Place of Performance

Link: FBO.gov Permalink
Bookmark This Notice
Print View