SOURCES SOUGHT
58 -- Advanced Time Division Multiple Access (TDMA) Interface Processor (ATIP)
- Notice Date
- 5/20/2010
- Notice Type
- Sources Sought
- Contracting Office
- 4301 Pacific Highway Bldg OT4 Code 02, San Diego CA 92110-3127
- ZIP Code
- 92110-3127
- Solicitation Number
- SPAWAR_Headquarters_MKTSVY_81F82
- Response Due
- 6/3/2010
- Archive Date
- 6/18/2010
- Point of Contact
- Point of Contact - Sarah S Ahn, Contract Specialist, 858-537-0288
- E-Mail Address
-
Contract Specialist
(sarah.ahn@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- 1.0 DESCRIPTION: 1.1 The Space and Naval Warfare Systems Command (SPAWAR) is seeking sources for the potential development of Advanced Time Division Multiple Access (TDMA) Interface Processor (ATIP). The ATIP is an advancement of the Navys TDMA Interface Processor (TIP), which operates on legacy Navy Extremely High Frequency (EHF) MDR capable terminals. ATIP will include support for IPv6/IPv4 packet forwarding, Advanced Extremely High Frequency (AEHF) XDR data rates (up to 8 Mbps), improved QoS, advances in dynamic TDMA slot assignment, and include backward compatibility to the TIP. The architecture will implement Layer-2 Ethernet bridging among users that are geographically dispersed and connected via Milstar Medium Data Rate (MDR), Advanced EHF Backward Compatible MDR and XDR, or Enhanced Polar System XDR satellite links. ATIP will also allow users within each beam area to share on an EHF/AEHF service the uplink on a dynamic TDMA basis and receive from other beam areas (other EHF/AEHF services) to provide a full duplex connectivity using half duplex EHF/AEHF services. Each individual service is denoted as a TDMA Subnet and the collection of these for the full duplex connectivity is denoted as a Supernet in ATIP terminology (and as used herein). The ATIP is functionally divided into two elements: (1) the ATIP Processor (AP) and (2) the Terminal Interface (TIF). It is anticipated that the AP will be a Commercial Off The Shelf (COTS) processor(s) circuit card assembly (CCA) with appropriate software development and that the TIF may be implemented by a Field Programmable Gate Array (FPGA) hardware/firmware CCA(s). The AP and TIF are connected via Ethernet to support variable installation configurations and each element will be rack mountable and meet Navy platform environmental requirements. Within the ATIP architecture, the AP interfaces to up to six (6) physical user network devices and the TIF interfaces with up to eight (8) EHF/AEHF services. The ATIP includes the following functional architecture components: Network Interface Function, Quality of Service (QoS) Function, Forwarding Function, TDMA Transmit and Receive (Rx) Processing Functions, Control/Status Monitoring Function and Terminal Interface Function. The first six functional capabilities are intended to be implemented in software within the AP COTS CCA. The following paragraphs summarize the ATIP capabilities by functional architecture component. 1.1.1 The Network Interface function provides the connection to local network devices to support the Layer-2 Ethernet bridging function implemented by the ATIP. ATIP assigns a single Ethernet interface per Supernet, supporting 10Base-T/100Base TX/1000Base-T operation. 1.1.2 The QoS and Forwarding functions are used to provide layer-2 frame forwarding behavior in accordance with user application delivery needs as identified in a Subnet QoS policy. QoS-based frame forwarding is performed separately by each TDMA Subnet member in coordination with direction from the TDMA Net Controller (NC). Using in- band protocols, members inform the NC of their traffic flows and the NC allocates bandwidth accordingly. 1.1.3 TDMA Subnet Management functions support establishment of the TDMA Subnet structure by the NC, member join/exit processing, member status reporting to the NC, NC dynamic bandwidth assignment, and Subnet NC management handover. Subnet activation and join are operator activated, but once Subnets are active, the member and NC autonomously coordinate status and dynamic resource allocation. The TDMA subnet structure (# timeslots per cycle, max # members, etc.) is established through NC periodic transmission of a Sequence Order List (SOL) message which contains the TDMA Subnet parameters as well as TDMA timeslot assignments for each Subnet member. Timeslots are assigned to members by the NC in response to member traffic flow reports and the configured ATIP QoS policy. 1.1.4 The TDMA Tx Processing functions support formation of TDMA Transmission Units (TUs) based on the QoS / Forwarding policy, and transmission of the TUs in the timeslot (s) designated for the member in the NC SOL message. These packets include both data packets and TIP/ATIP protocol messages between the TDMA Subnet members and the NC managing the TDMA Subnet. TUs will be formed on a just-in-time basis, using TDMA slot timing information from the TIF, and provided to the TIF for transmission in the NC-assigned timeslots. 1.1.5 TDMA Rx Processing functions support extraction of data and protocol packets from TUs provided by the TIF which were received over-the air, filtering out packets destined for the current ATIP, and delivery of the packet contents to the appropriate interface. 1.1.6 The Control/Status Monitoring function provides the operator interface to the ATIP. Status Monitoring provides ATIP operating status to the operator, including hardware status, interface status, Supernet/Subnet operation status, packet processing status, and ATIP event status (e.g. Subnet Join/Exit, NC handover, etc). ATIP Control supports receipt of ATIP configuration and operating parameters from the operator, performing input parameter consistency checks, and implementing the specified configuration on the ATIP. The ATIP Control/Status Monitoring function will use a browser-based user interface with Transport Layer Security protocol, eliminating the need for a separate ATIP Operator Interface application program and specially- configured PC. In addition, the ATIP Control and Status Monitoring function will support an Operator orderwire capability. 1.1.7 The Terminal Interface function (TIF) is responsible for exchanging ATIP TU data with the crypto/EHF terminal in synchronization with the timeslots allocated to the member ATIP on transmit and for all timeslots on receive. Timeslot boundaries are identified through receipt of TDMA timing signals from the terminal which are multiples of Subnet TDMA timeslots. TIF processing includes two key sub-functions: (a) identification of timeslot boundary for both uplink and downlink and (b) serial exchange of TU data with the crypto/EHF terminal using standard synchronous serial protocols. The TIF provides serial interface status, including the detection of EHF/AEHF service activation, to the AP to support control/status monitoring of ATIP Subnets. 2.0 SYNPOSIS TERMS - THIS IS A SOURCES SOUGHT SYNOPSIS ONLY. THIS IS NOT A NOTICE OF SOLICITATION ISSUANCE. This synopsis 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 synopsis does not commit the government to contract for any supply or service whatsoever. If a solicitation 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 the potential respondents to monitor these sites for additional information pertaining to this potential requirement. The information provided in this Sources Sought Synopsis is subject to change and is not binding on the Government. Further, the release of the Sources Sought Synopsis should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. Respondents are advised that the U.S. Government will not pay for any information or administrative cost incurred in response to this Sources Sought Synopsis. All costs associated with responding to this Sources Sought Synopsis will be solely at the interested party's expense. Failure to respond to this Sources Sought Synopsis will not preclude participation in any future RFP, if issued. 3.0 REQUESTED INFORMATION - Responses to this synopsis shall provide the name, phone number, fax number, and e-mail address of the designated point of contact of the respondent. Respondents shall indicate their business size, socio- economic status and the extent for which they can include Small Business, Small Disadvantaged Business, HUBZone Small Business, Women- owned, Veteran-owned, or 8(a) participation in any potential resulting procurement. The North American Industry Classification System (NAICS) code for this requirement is 541511 and the small business size standard is $25 million. Respondents are requested to provide a corporate capability statement that explains: 1) their technical capability to meet the Government's requirements, 2) availability of staff with the expertise required, 3) past performance in similar software development, and 4) any potential subcontracting arrangements that may be used in a requirement such as this. The capability statement shall also include the respondents website address, all applicable NAICS codes, number of employees, and annual revenue for the last three fiscal years. 4.0 RESPONSES 4.1 Responses to this synopsis in Microsoft Office 2000 compatible or Adobe PDF format are due no later than 03 June 2010 and should not exceed five pages excluding any advertising materials such as company brochures or comments on the acquisition strategy. Unclassified responses shall be submitted via e- mail only to cindy.lawson@navy.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become government property and will not be returned. Industry respondents should also include a statement that the respondent has a signed Proprietary Data Protection Agreement (PDPA) with LinQuest, Booz Allen Hamilton (BAH), and Tele-Consultants Inc. (TCI), that would permit these support contractors to review and evaluate responses submitted in response to this synopsis. If no such PDPA exists, respondents should execute a PDPA with the aforementioned contractors supporting SPAWAR in technical evaluations. For information on how to contact support contractors e-mail Sarah Ahn at sarah.ahn@navy.mil. 4.2 Questions regarding this announcement shall be submitted in writing by e-mail only to sarah.ahn@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 or classified information. The Government does not guarantee that questions submitted after 1 June 2010, 5:00 PM PST would be answered. To access the SPAWAR E- Commerce Central website, go to https://e-commerce.spawar.navy.mil. Click on Headquarters; then Market Survey. Interested parties are invited to subscribe to the SPAWAR website to ensure they receive any important information updates connected with this Sources Sought.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/SPAWAR/SPAWARHQ/SPAWAR_Headquarters_MKTSVY_81F82/listing.html)
- Record
- SN02155868-W 20100522/100520235556-753479fa4bff833ccc0303545b0908a8 (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 |