Loren Data's FBO Daily™

fbodaily.com
Home Today's FBO Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF SEPTEMBER 13, 2008 FBO #2483
SOLICITATION NOTICE

A -- Correction to the Response Date within the Description Section of this requirement.

Notice Date
9/11/2008
 
Notice Type
Modification/Amendment
 
NAICS
541330 — Engineering Services
 
Contracting Office
Department of the Army, U. S. Army Materiel Command, RDECOM Acquisition Center - Aberdeen, RDECOM Acquisition Center - Aberdeen, ATTN: AMSSB-ACC-A, 4118 Susquehanna Avenue, Aberdeen Proving Ground, MD 21005-3013
 
ZIP Code
21005-3013
 
Solicitation Number
W91CRB-08-WP-003
 
Response Due
11/3/2008
 
Archive Date
1/2/2009
 
Point of Contact
Nikia Jelks, 407-384-5585<br />
 
Small Business Set-Aside
N/A
 
Description
Broad Agency Announcement (BAA) W91CRB-08-R-0073 was publicized on the Federal Business Opportunities on 11 August 2008 by the U.S. Army Research, Development and Engineering Command Simulation and Training Technology Center (RDECOM STTC). This notice calls for White Paper Submissions in reference to the research interest entitled, Predictive Analysis Research. Technical Points of Contact for this specific white paper submission: Mr. Jerry Speer, RDECOM STTC, (407)384-3835, jerry.speer@us.army.mil and Mr. Richard Pei, CERDEC, (732)-427-4820 richard.pei@us.army.mil (email contact preferred). Contractual Points of Contact: Ms. Nikia Jelks, Contract Specialist US Army RDECOM Acquisition Center, 12423 Research Parkway, Orlando, FL 32826 or Ms. Vanessa T. Dobson, Procuring Contracting Officer, 12423 Research Parkway, Orlando, FL 32826. OBJECTIVE: The Communications Electronics Research Development and Engineering Center, (CERDEC) and the RDECOM STTC are researching capabilities to extend the DARPA Real-time Adversarial Intelligence and Decision-making (RAID) system using High Performance Computing. Specific Research Areas: It would be undoubtedly valuable to scale RAID up to permit it to deal with battalion, or even brigade size units, but it is not immediately obvious that this is feasible. Such scaling would likely entail challenges in at least three research areas: "Additional types of rules/models. There is a clear need for additional types of rules or models to fully describe the breadth of operations above company level. While a company deals almost totally with tactical issues, a brigade must deal as well with logistical, ISR, medical, fire support, air defense, force structure, more complex forms of maneuver, and personnel concerns. In addition, a brigade must multi-task its operations (among its battalions and companies), control a more powerful weapons suite (e.g., NLOS missiles), and increased ISR capabilities (e.g., UAVs, UGVs, remote sensors, and UGS). Moreover, often equally important, a brigade must deal with the environmental impact of its operations, (i.e. Political, Economic, Social/Cultural, and Information/Media (PESI) impact of its actions). Also, RAID employs models to understand situations, to make estimates based on likely evolutions of the situation, and to employ these estimates in its planning process. As such, it constitutes a rudimentary model-predictive controller (MPC). The MPC capabilities of RAID may well be expanded/extended to provide hedging, multi-echelon coordination, etc. The first research question is; Can RAIDs current architecture and optimization approach handle or incorporate the new types of rules and PESI models? "Expanded Area of Interest (AoI). The larger AoI of higher level units requires more geographic information and, in turn, a larger Current Operational Picture (COP). In one FCS scenario, for instance, a BCT using air mobility for vertical maneuver has an AOR of as large as 300x400km, and there is no conventional Forward Line of Troops (FLOT) (the units being widely separated). The second research question is; Can the geographic and human terrain information needed for such scenarios be developed and provided in the time frames required? "Increased problem size. RAID employs several new technologies for its gaming and optimization computations. One technique, referred to by its creator as Linguistic Geometry, has served admirably for RAID problems at the company scale. But, insofar as we can tell, no one has yet determined how far the RAID technology can go before it is non-functional. There is a mitigating factor in this area of research we will be able to use substantial additional computational resources. However, its not clear exactly what this would entail e.g., large serial array, a GPGPU array, or both -- or even how much benefit this would provide. Therefore, the third research question is; What type of HPC enabled system architecture/configuration would be best suited to scale the RAID system to an increased problem size? Extension of scope of modeling. As mentioned with respect to rules, RAID currently deals with purely tactical problems; one of its showcase vignettes, in fact, involves a company supported by four Stryker vehicles and four attack helicopters attacking an urban insurgency force. (Contrast this with the scope of modeling needed to depict a BCT which has approximately 220 armored vehicles, 104 UAVs, 12 armed helicopters, 60 MCS guns, 24 mortars, and 18 cannon; and, the resulting scope and intensity of BCT tactical operations.) The current RAID tactical problems are realistic, at least insofar as company-level missions go. However, extension of RAID to brigade operations would require that it expand its realm of consideration to include other elements of its operating environment i.e., political, economic, infrastructure, and social/ cultural factors. A brigade version of RAID, for instance, should deal explicitly with the needs, attitudes, norms, and proclivities of the populace as well as the economics of the region. Moreover, it should be capable of employing attitudes and infrastructure to best advantage, and of ensuring that the adversary is denied the support it desires. A case in point is human terrain and leadership / personality modeling. This category of models employs a history of a groups activities and individuals past actions to forecast how they, he or she would likely act in a newly defined situation and how they would most likely exploit the resources available to them. Needless to say, such insights could be of immense value for brigade level operations. The planned method for accomplishing the research in these prospective areas is to utilize a phased approach. Therefore, White Papers submitted should be structured so that the technical approach/solution for the proposed research areas address a Basic Award (Phase I) and one (1) priced Option Effort (Phase II) as stated below. The White Paper must include the anticipated period of performance, a technical description of the proposed concepts, the technical objectives and a planned approach to accomplish the stated objectives as well as a rough order of magnitude (ROM) cost. The ROM cost consists of the total cost plus profit/fee, if any. PHASE I. The Phase I effort will research how relevant technology can be brought to fulfill the objectives as listed in the Research Area paragraphs above. This phase should include system architecture design, development and implementation into an Initial Prototype to be demonstrated in relevant environments (i.e., both interior and exterior operational & training environments.) Phase I will be a 12-month effort and funding will be approximately $10M. PHASE II. The Phase II effort will continue refining the prototype to improve realism, increase ruggedness, address any shortcomings identified in Phase I, and bring the system to at least TRL level 6 and be ready to be transitioned to the Army DCGS-A system. At this time, it is anticipated that Phase II will be a 18-month effort with funding of approximately $15M subject to budgeting constraints. An Industry Day is tentatively planned for October 21, 2008 in Orlando, FL. The Industry Day may, or may not, be held. A decision to do so will be based on the needs of the U.S. Army. Should the Government schedule a Program Industry Day, an announcement with applicable instructions will be published in FebBizOpps no later than 2 weeks prior to the event. Reference Documents are provided at http://www.rdecom.army.mil/STTC/baa.html THIS ANNOUNCEMENT CONSTITUTES THE ENTIRE SOLICITATION FOR THIS EFFORT. DO NOT SUBMIT A FORMAL PROPOSAL AT THIS TIME. WHITE PAPER SUBMISSION: Any responsible offeror capable of satisfying the objectives identified in this announcement may submit a white paper. White Paper submissions are encouraged as early as possible but must be received at RDECOM STTC no later than 1600 EDT 3 November 2008. No extensions will be granted. White papers must address the objectives for both Phases and shall not exceed 10 pages in length of computerized text at 12-pitch, excluding resumes. Only unclassified white papers will be accepted. All white papers must include Phase II as a priced option. The white papers will be reviewed to determine that the proposed effort is within the scope and interest of this solicitation. A proposal will only be solicited from white papers deemed to best meet the program objectives. White papers will be evaluated by a technical review board using the following criteria listed in descending order of importance: (1) Scientific and Technical Merit: Proposed efforts should create new, or apply existing technology in a new way, that is advantageous to the proposed research topic. The overall scientific and technical merit of the proposal must be clearly identifiable. The technical concept should be clearly defined and developed. Emphasis should be placed on the offeror's technical approach through a comprehensive, logical, orderly, concise, phased plan that indicates major milestones, critical paths, key events, capabilities that can be spun off, demonstration articles, etc. Consideration should be given to the extent which current State-of-the-Art technology is expanded. Offeror should discuss how their concept will be documented, demonstrated, or evaluated, and this discussion should be indicative of the understanding of what is required in this program. (2) Potential Contribution to Military Services Needs and Transition to other Programs: The offeror must adequately address how the proposed solution will meet the goal of the research topic. The proposal must show understanding of the potential approach and make a compelling case for the viability of the proposed effort. The relevance is further indicated by the offeror's understanding of the operating environment of the product or demonstration (current Military or Industrial technical problems/issues, limitations, etc.). The relationships of the proposed effort with other ongoing or anticipated initiatives (military or civilian) that are focused on improving HPC Modeling and Simulation should be considered. Offeror should recognize and identify potential strategies for transitioning technology within the DoD. Plans on how offeror intends to get developed technology, and information on these developments, to the user community should be considered. (3) Personnel: The qualifications, experience, capabilities, and demonstrated achievements of the proposed principal investigators and other key personnel for the primary and subcontractor organizations should be examined and assessed for the proposal objectives. (4) Corporate Capabilities and Facilities: Offerors are required to describe their relevant capabilities and accomplishments. The offeror must have a demonstrated capability to conceptualize, develop theories, identify concept deficiencies, analyze, and develop mature concepts for rapid application/ demonstration. Consider the offerors history of related work. Also consider any unique facilities or equipment that the offeror possesses. (5) Cost: The overall estimated cost to accomplish the effort should be considered as well as the substantiation of the costs for the technical complexity described. Evaluation should consider the extent to which the proposed management plan will effectively allocate and provide accounting of funds, equipment, and personnel, select subprojects, monitor and evaluate the program to achieve the proposed objectives, and respond to contingencies created by unanticipated technical barriers or breakthroughs. Cost reasonableness and realism will be assessed, but this assessment is of a lower priority than the technical evaluation. White Papers found to be consistent with the requirements of this announcement and deemed to best meet the program objectives may be invited to submit a technical and cost proposal. To be eligible for award a white paper must be submitted. Upon completion of white paper evaluations, Offerors will be notified whether or not their white paper was favorably received. Favorable review of a white paper does not constitute selection of the proposed effort for contract award and will not establish a binding commitment for the Government to fund the effort in whole or part. Upon notification, the Government will issue a request for proposal letter to the qualified offeror(s), who best meet the program objectives. If proposals are solicited, proposals are due NLT 1600 16 January 2009. The requirements for proposal preparation and submission can be found at http://www.rdecom.army.mil/STTC/baa.html This announcement is an expression of interest only and does not commit the government to reimburse any proposal preparation cost for responding. The cost of proposal preparation in response to this announcement is not considered an allowable expense to the normal bid and proposal indirect costs as specified in FAR 31.205-18. Any request for white paper or submission of a full proposal does not guarantee award. The Government reserves the right to cancel this requirement at any time and shall not be liable for any cost of proposal preparation or submission. Within the meaning of the Federal Acquisition Regulation (FAR) at 6.102 and 35.016, this announcement constitutes the Government's solicitation for this effort. There will be no other solicitation issued in regard to this requirement. Offerors should be alert for any BAA amendments that may be published. WHITE PAPER FORMAT: White Papers shall not exceed 10 pages of computerized text at 12 pitch (excluding resumes) Contractor format is acceptable. The white papers should be provided in hardcopy and CD electronic form no later than 1600 hrs EDT 3 November 2008. NOTE: Both the hardcopy as well as the electronic (CD) copy MUST BE received together, by the due date and time. MAIL WHITE PAPERS TO: US Army RDECOM Acquisition Center, Attn: Ms. Nikia Jelks, Contract Specialist, 12423 Research Parkway, Orlando, FL 32826. The administrative addresses are: Technical Points of Contact Technical Point of Contact is: Mr. Jerry Speer, (407)-384-3835, jerry.speer@us.army.mil or Mr. Richard Pei, CERDEC (732)-427-4280, richard.pei@us.army.mil Contracting Point of Contact: US Army RDECOM Acquisition center Attn: Ms. Nikia Jelks, Contract Specialist Phone: (407) 384-5585 ATTN: BAA W91CRB-08-R-0073
 
Web Link
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=b7111ea2b8dd18800fb12a4d47b1636f&tab=core&_cview=1)
 
Place of Performance
Address: RDECOM Acquisition Center - Aberdeen ATTN: AMSSB-ACC-A, 4118 Susquehanna Avenue Aberdeen Proving Ground MD<br />
Zip Code: 21005-3013<br />
 
Record
SN01668138-W 20080913/080911231549-b7111ea2b8dd18800fb12a4d47b1636f (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  © 1994-2013, Loren Data Corp.