Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JANUARY 07, 2006 FBO #1503
MODIFICATION

A -- Requirements Development and Rapid Prototyping Testbed (RDRaPT) Request for Information (RFI)

Notice Date
1/5/2006
 
Notice Type
Modification
 
NAICS
541519 — Other Computer Related Services
 
Contracting Office
ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
 
ZIP Code
22331-0700
 
Solicitation Number
W91QUZ06R0XXX
 
Response Due
2/20/2006
 
Archive Date
4/21/2006
 
Small Business Set-Aside
N/A
 
Description
Requirements Development and Rapid Prototyping Testbed (RDRaPT) Request for Information (RFI) Closing Date: 20 February 2006. The Program Executive Office for Enterprise Information Systems (PEO EIS); Project Officer for the Acquisition Domain (PO AD) Combat Development Integration Cell (CDIC) in partnership with the Office of the Assistant Secretary of the Army Acquisition, Logi stics, and Technology (OASA(ALT)) is seeking industry information on available protocols, products, and technologies to facilitate the rapid defining of processes, requirements, and technologies to improve the way the Army acquisition domain conducts its b usiness. Sources sought are requested to address available, processes, products, and technologies to provide a complete capability to rapidly define requirements within the Army Acquisition business process domain, and to prototype technologies that can offer significant improvement. The proposed solution must have the capability to produce data to help quantify the value improvement of those technologies or process changes. The analysis may cover the current policies, procedures, and tools used through out the acquisition lifecycle, from cradle to grave. The ultimate goal of this RFI is to identify expertise and knowledge in rapid prototyping processes and tools that can be utilized to facilitate requirements definization, technology exploration, and cost benefit analysis. The optimum response will provid e useful information about state of the art technologies and tools, a high level implementation plan, and a proven track record in delivering this capability to industry or government organizations. Background: In an effort to streamline the current acquisition processes and to posture the Army for continued transformation, the OASA (ALT) and related activities have undertaken a review of their current business practices and supporting technologies. This effort is concurrent with the Business Management Modernization Program, the Department of Defenses overarching initiative to assess business areas for efficiency and effectiveness, associated portfolio management activities, and the ability to meet and support the transformation requirements as defined in Joint vision 2020. The ASA(ALT) and PEO EIS have been directed to implement a Service Oriented Architecture (SOA) as the framework for enhancing the business of Army Acquisition. This SOA will provide the infrastructure through which enterprise net-centric business systems will enable domain elements to create, manage and share the information and information management resources necessary to enable more efficient and effective business processes. The Acquisition Domain will soon establish the Future Business System (FBS) Program responsible for developing and fielding the SOA and the suite of enterprise net-centric business tools that will continuously evolve to provide improving and more efficient business support to the domain. However, the Acquisition community has little experience with Service Oriented Architectures, net-centric systems, and shared data spaces. Although there is a clear requirement for secure information, interoperable systems, agile business processes and pr actices, and greater efficiency in the creation, management and sharing of information, there is no clarity in what improvements are possible, what technology can enable, or how to state clear requirements for enhanced business capabilities. Description: To overcome this problem, the domain is seeking to explore the use of a requirements development and technology prototyping test-bed. This test-bed will provide a mechanism to bring users together with state-of-the-art information management technologies in a mock SOA environment to enable rapid prototyping of process changes and exploration of technology options. PEO EIS is looking for industry ideas on how such a requirements development and material prototypin g test-bed could be accomplished. The PEO is seeking information on how such a test-bed might be designed, operated and/or matured so as to provide the desired support to the Future Business System Program. Information sought would include technical appr oaches, information on previous experience with similar approaches, and draft scenarios that can be used to validate each proposed approach. This requirement applies to all elements of the acquisition domain. It applies directly to the Assistant Secretary of the Army for Acquisition, Logistics, and Technology (ASA (ALT)), its Field Operating Agencies (FOAs), Direct Reporting Program Managers ( DPMs), Program Executive Officers (PEOs) and subordinate PMs. It also applies to those organizations not directly reporting to the ASA (ALT), but which have a substantial role in the planning, management, and/or execution of the life-cycle management proc ess defined by DoD Directive 5000.2. This includes but is not limited to Test & Evaluation (T&E) Organizations; Army Materiel Command (AMC), Army Laboratories; Research, Development and Engineering Command (RDECOM); and the Army Materiel Systems Analysis Activity (AMSAA). Additionally, the requirement should address the interface between the anticipated Future Business System and the other enterprise systems across the Army and DoD. The goal is to establish the requirements for the FBS program so that it takes advantage of and works seamlessly with evolving enterprise systems across domain and Service lines and with evolving Net-Centric Enterprise Services and other enterprise services such as AKO. The RDRaPT will be required to support the emulation, manipulation, and experimentation of the following acquisition domain functions; policy management, program management, earned value management, contract management, funds management, systems engineerin g, software acquisition management, test and evaluation, manufacturing and production, and logistics management and other acquisition functions across the life-cycle. Capabilities: a. Hardware: The requirement is for computer hardware and associated peripheral equipment necessary to support the RDRaPT environment. The proposed solution must explain how DoD information Technology Security Certification requirements will be satisfi ed b. Software: The requirement is for the requisite software to simulate, stimulate and emulate acquisition business processes in a service oriented architecture. This software must be fully supported by the proposed hardware and provide an automated envi ronment to experiment with improved business processes and differing technologies. c. Documentation: Relevant documentation of the results, feedback, and data from the RDRaPT is required to document requirements and provide information to perform relevant analysis. The information should be presented in an easily understood format and should not require significant data reduction efforts. d. Data: All data flowing through the RDRaPT should be in accordance with industry best standards and the government financial data standard or other government data standards. e. Interfaces/Edge resources: The RDRaPT must take into account edge resources and domain interfaces. It must provide the ability to show the interface points and have the ability to provide full duplex data exchanges at these points. PEO EIS is looking for suppliers who can provide an integrated capability that incorporates the above capabilities. All respondents are asked to provide the following: 1. A technical description of potential solution(s) or complete capability. The description should answer the following questions: a. What part of the overall capability your solution addresses? b. How does your solution work? What are its limits? c. What are the physical dimensions of the environment d. How effectively has your solution been used in the past or related applications? e. What evidence exists that your solution is applicable if it has not been specifically used for this type of work? f. How mature is your system? Is it new development? Does a prototype exist? Is it similar to previous successful developments? Is it an extension or evolution of an existing product? g. A schedule estimate from contract award to operational capability for each proposed solution. 2. A high level cost estimate of establishing the environment and any associated costs with running the RDRaPT . 3. Recommendations where outcomes can be traded for reduced costs or where enhancements can be added for little or no cost. RFI Purpose and Limitations: The Governments intention is to better understand the current state-of-the-art and to determine the best acquisition approach. Industry feedback is vitally important and the Government will be receptive to any and all ideas received from industry. This RFI is an expression of the Governments interest only and does not obligate the Government to pay for the requested information nor respond to any submissions. Proprietary information is not being solicited; however, if it is submitted, it should be appr opriately marked. Please limit your formal white paper submission to no more than 20 pages to include cover letter and white paper. In addition, you may include up to five attachments that consist of briefing slides, pre-printed commercial brochures or s ales literature. Electronic submissions are strongly encouraged. All items must be in Microsoft? Office 2000 or Adobe PDF format and should be free of all computer viruses. All applicable NAIC and FSC codes are subject to change. Please submit responses to Dirk Robinson, (703) 325-3308, ITEC4, 2461 Eisenhower Ave., Hoffman I, Alexandria, VA 22331-1700 or e-mail: dirk.a.robinson@us.army.mil, Information must be received no later than 2:00 PM Eastern Standard Time on 20 February 20 06. Points of Contact: Technical: Joe Klumpp, Project Officer Acquisition Domain, joseph.klumpp@us.army.mil, 703-806-3656. Contractual: Dirk Robinson, ACA-ITEC4, Div-A, Branch Chief, dirk.a.robinson@us.army.mil, 703-325-3308 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY This RFI is issued as Market Research, solely for information and planning purposes. It shall not be considered as an Invitation for Bid (IFB), Request for Quotation (RFQ), Request For Proposal (RFP), or as an obligation on the part of the Government to ac quire any products or services. Any response to this synopsis will be treated as information only. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this syn opsis or the Government for use of such information. The information provided may be used by the Army in developing its acquisition strategy and in its Statement of Work/Statement of Objectives and Performance Specifications. Not responding to this RFI d oes not preclude participation in any future RFP, if issued. If a solicitation is issued, it will be synopsized on the Federal Business Opportunities (FedBizOpps) website. It is the responsibility of any potential offeror to monitor these sites for additi onal information pertaining to this requirement.
 
Place of Performance
Address: ACA, ITEC4 Directorate of Contracting , 2461 Eisenhower Avenue Alexandria VA
Zip Code: 22331-0700
Country: US
 
Record
SN00961706-W 20060107/060105212046 (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.