Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF OCTOBER 12, 2003 FBO #0684
SOLICITATION NOTICE

D -- RFI BATTLE GROUP METRICS

Notice Date
10/10/2003
 
Notice Type
Solicitation Notice
 
Contracting Office
4301 Pacific Highway Bldg OT4 Code 02, San Diego CA 92110-3127
 
ZIP Code
92110-3127
 
Solicitation Number
N00039-04-R-0002
 
Response Due
11/12/2003
 
Archive Date
12/12/2003
 
Point of Contact
Point of Contact - GILBERTO P PENSERGA, Contract Specialist, 858-537-0440; Pamela F Kibler, Contracting Officer, 619-524-7192
 
E-Mail Address
Email your questions to Contract Specialist
(gilberto.penserga@navy.mil)
 
Small Business Set-Aside
N/A
 
Description
1.0. DESCRIPTION 1.1. Space and Naval Warfare Systems Command (SPAWAR) is issuing this Request for Information announcement N00039-04-R-0002 on behalf of the Program Executive Officer ? Command, Control, Communications, Computers, Intelligence and Space (PEO-C4I), Program Management Warfare 176 (PMW 176). 1.2. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. The intent is to identify sources that can design and implement a method to collect and analyze battlegroup communications metrics. 1.3. This RFI is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the government to contract for any supply or service whatsoever. Further, the Navy is not at this time seeking proposals, and will not accept unsolicited proposals. Respondees are advised that the U.S. Government will not pay for any information or administrative cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested party?s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 1.4. If an RFP is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps) website and the SPAWAR E-Commerce Central website at https://e-commerce.spawar.navy.mil. It is the responsibility of potential offerors to monitor these sites for additional information pertaining to this requirement. 2.0. BACKGROUND 2.1. The PEO-C4I, PMW 176 is seeking sources capable of designing and producing a method of gathering and analyzing battlegroup communications information and developing metrics suitable for identifying efficiency issues. The metrics must have sufficient detail to allow them to be used to identify opportunities to improve warfighting capacity, including locating shortfalls or excess capacity. This request for information (RFI) seeks responses that will be used in developing a contract specification for battlegroup metrics development, installation, and execution. 2.2. The Navy desires to examine all wideband satellite communications (SATCOM) into or out of a battlegroup during a full deployment to determine actual communications usage. Wideband SATCOM Systems included in this metric are Commercial Wideband SATCOM Program (CWSP) (formerly known as the Challenge Athena Program), Extremely High Frequency (EHF), Global Broadcast System (GBS), International Maritime Satellite System (INMARSAT), Super High Frequency (SHF), and Television - Direct To Sailors (TV-DTS). It is anticipated that some applications will be employed so much that they will be bandwidth limited while others may not be used to capacity. The metrics are intended to capture this information to allow the Navy to realign communications plans to make optimum use of available resources and to plan rationally for future improvements. A battlegroup can be assumed to consist of one aircraft carrier (CVN), two cruisers (CG), two guided missile destroyers (DDG), two attack submarines (SSN), one amphibious helicopter carrier (LHA), and two amphibious docks (LHD). A battlegroup deployment is approximately six months long. The metrics should consider the following characteristics: 2.2.1. Type of Information ? For example: Voice, Video, Data, Imagery. 2.2.2. Applications ? For example: email, GCCS-M, LAWS, etc. 2.2.3. Users ? For example: CIC, JIC, CDC, TFCC, SUPPLOT, SACC, LFOC, JFACC, personal use by individual Sailors, etc. 2.2.4. Security Classification - For example: SCI, Top Secret, Secret, Confidential, FOUO, Unclassified. 3.0. REQUESTED INFORMATION 3.1. White Paper 3.1.1. Commercial companies and other organizations are hereby invited to provide a white paper, of no more than thirty (30) pages in length, on their satellite communications experience, Battlegroup Communications Metric concepts and technologies, and previous demonstrations of, and/or capabilities to develop technologies to support the capabilities desired for the Battlegroup Communications Metric. This information will be considered in developing the final contract specification for the Battlegroup Communications Metric. Proprietary information, if any, should be minimized and MUST BE MARKED. Please be advised that all submissions become government property and will not be returned. The white paper shall be in Microsoft Word for Office 2000 compatible format, shall not contain any classified information, and should address the following: 3.1.1.1. Concept and method to capture the metric data. 3.1.1.1.1. The Navy expects measurement of all wideband SATCOM communications to/from each ship in the battlegroup. 3.1.1.1.2. The data should be identifiable to which RF transmission path was used, the shipboard origin, the destination of the data, and other characteristics previously discussed. 3.1.1.2. Concept and method to conduct a Lab Demonstration (Proof of Concept). 3.1.1.3. Concept and method to Conduct Fleet Measurement. 3.1.1.3.1. Install & Test H/W and S/W; conduct end-to-end validation test. 3.1.1.3.2. Measure data during a six month deployment. 3.1.1.4. Concept and a method to provide analysis of the metric. 3.1.1.4.1. Retrieve data daily to check for continuity of data. 3.1.1.4.2. Process data at least weekly to provide quicklook feedback. 3.1.1.4.3. Provide a detailed analysis of aggregate data. 3.1.1.5. Provide a recommendation on how the metric could be used to help the Navy in the future. 3.2. White Paper Addendum. The white paper shall include the following information in a separate attachment. The number of pages in this addendum will not be included in the 30-page limitation for the white paper. 3.2.1. Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact. 3.2.2. Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS) code 541511, Custom Computer Programming Services. "Small business concern" means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121. A small business concern for the purposes of this procurement is generally defined as a business, including its affiliates, averaging no more than $21 million dollars in annual receipts. Annual receipts of a concern which has been in business for 3 or more complete fiscal years means the annual average gross revenue of the concern taken for the last 3 fiscal years. Annual receipts of a concern that has been in business for less than 3 complete fiscal years means its total receipts for the period it has been in business, divided by the number of weeks including fractions of a week that it has been in business, and multiplied by 52. Respondees are cautioned, however, that this is a general description only. Additional standards and conditions apply. Please refer to Federal Acquisition Regulation (FAR) Part 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://www.arnet.gov. 3.2.3. The facility security clearance of the offeror. 4.0. QUESTIONS Questions in regard to this announcement shall be submitted in writing by e-mail only to gilberto.penserga@navy.mil. Verbal questions will NOT be accepted. Questions will be answered via posting answers to the SPAWAR E-Commerce Central website; accordingly, questions shall NOT contain proprietary and/or classified information. The Government does not guarantee that questions received after 29 October 2003 will be answered. To access the SPAWAR E-Commerce Central website, go to https://e-commerce.spawar.navy.mil Click on Headquarters; then Future Opportunities; then click on the yellow folder to the left of N00039-04-R-0002 to view other important information related to this RFI. Interested parties are invited to subscribe to the SPAWAR website to ensure they receive any important information updates connected with this RFI. To subscribe, click on N00039-04-R-0002; then click on ?Subscribe? near the top of the screen, and follow the directions provided. 5.0. RESPONSE DATE White papers are due no later than 12 November 2003 at 14:00 Pacific Standard Time. Responses shall be submitted via e-mail only to gilberto.penserga@navy.mil. 6.0. SUMMARY THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can design and implement a method to collect and analyze battlegroup communications metrics. The information provided in the RFI is subject to change and is not binding on the Government. The Navy has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment, or as authorization to incur cost for which reimbursement would be required or sought. It is emphasized that this is a Request for Information. It is not a Request for Proposal (RFP) of any kind, and is not intended to guarantee procurement of these items/services. All submissions become government property and will not be returned.
 
Web Link
Click on this link to access the SPAWAR Solicitation Page
(https://e-commerce.spawar.navy.mil/command/02/acq/navhome.nsf/homepage?readform&db=navbusopor.nsf&whichdoc=4B934DB7EBF2962588256DBB0069ABB2&editflag=0)
 
Record
SN00451321-W 20031012/031010213235 (fbodaily.com)
 
Source
FedBizOpps.gov 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.