Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF FEBRUARY 27, 2011 FBO #3382
SOURCES SOUGHT

59 -- Parachute Navigation System for Military Free Fall

Notice Date
2/25/2011
 
Notice Type
Sources Sought
 
Contracting Office
RDECOM Contracting Center - Natick R&D (RDECOM-CC), ATTN: AMSRD-ACC-N, Natick Contracting Division (R and BaseOPS), Building 1, Kansas Street, Natick, MA 01760-5011
 
ZIP Code
01760-5011
 
Solicitation Number
W911QY-B2
 
Response Due
4/15/2011
 
Archive Date
6/14/2011
 
Point of Contact
Brian Huffman, 508-233-4098
 
E-Mail Address
RDECOM Contracting Center - Natick R&D (RDECOM-CC)
(brian.g.huffman@us.army.mil)
 
Small Business Set-Aside
N/A
 
Description
The Natick Soldier Research, Development and Engineering Center (NSRDEC), Product Manager Soldier Clothing and Individual Equipment (PM-SCIE), Personnel Airdrop Team, Fort Belvoir, VA is conducting a market survey to locate potential manufacturers or suppliers of a Parachute Navigation System (PARANAVSYS) for use during Military Freefall (MFF) operations. PARANAVSYS is a multipurpose navigation device designed for Military Free Fall (MFF) operations use pre-jump in aircraft, during infiltration and on-ground follow-on missions, and will allow for enhanced mission planning and improved MFF parachutist infiltration capabilities. The PARANAVSYS will consist of a Navigation Unit, mounting hardware and a GPS Retransmission Kit (GPS RTK). A description of each component is as follows: Navigation Unit. The Navigation Unit serves as the centerpiece of the PARANAVSYS and will consist of a portable ruggedized computer hardware platform capable of receiving GPS signals and supporting both navigation and mission planning software required to meet program requirements. The Navigation Unit will meet all performance parameters and system attributes as specified herein. The Navigation Unit may be either helmet or chest-mounted. A helmet mounted system will interface with the user through a goggle-mountable micro-display. A chest-mounted system will consist of a ruggedized laptop with a display that will be directly readable by the user. A chest-mounted system may also include a goggle-mountable micro-display. The Navigation Unit will acquire and process GPS data, control the micro-display, and communicate via a wireless or hardwired data link to a separate mission planning laptop computer as required, or if capable, each unit may also concurrently serve as a mission planner. The electronics package of the Navigation Unit will be comprised of a micro controller, memory, battery, control switches, GPS receiver/antenna, external PC interface port, wireless receiver/transmitter, and micro-display interface electronics. Mounting Hardware. Mounting hardware will be required to secure the Navigation Unit firmly to the jumper during MFF operations. Mounting hardware will interface directly with either standard military helmets in the case of a helmet-mounted unit, or the MOLLE vest and a support belt in the case of a chest-mounted system. Mounting hardware will not interfere in any way with standard MFF equipment. GPS Retransmission Kit (GPS RTK). A GPS RTK will be required to provide a GPS signal onboard all training and operational aircraft to take full advantage of the capabilities of the PARANAVSYS during MFF High Altitude High Opening (HAHO) operations. GPS availability prior to exit allows the jumpmaster to identify a pre-planned release point based on target information and weather data entered during the mission planning phase. GPS rebroadcast onboard the aircraft will also allow the system to reacquire satellites from a "warm start" with a pre-acquired almanac as opposed to a "cold start" with an empty almanac. Additionally, the PARANAVSYS shall have the following capabilities: (Threshold (T) = Objective (O) unless otherwise specified) 1.Network Ready. PARANAVSYS shall be Network Ready per CJCSI 6212.01E, 15 Dec 08, and USA TRADOC CPD Writing Guide, dated 16 Jun 09, IER Matrix/IT/NSS/GIG Rationale: PARANAVSYS must properly interface with joint and service enterprise systems comprising the Global Information Grid. 2.System GPS Accuracy. The PARANAVSYS must provide guidance for jumpers to successfully deploy to a designated target. Using system GPS guidance alone, jumpers must reach a pre-designated drop zone and verify that the system can successfully locate the impact point within 100 ft (T), and verify that the system can successfully locate the impact point within 50 ft (O). Rationale: Accuracy requirements less than those stated would jeopardize successful accomplishment of the airdrop mission and could provide an unsafe environment for the MFF jumper. 3.System Reliability. The system must provide a 95 percent probability of achieving a successful mission. A successful mission will be free from the occurrence of a system abort (SA) for a period of 3 hours (T) 6 hours (O). Rationale: Operators are required to conduct mission planning throughout a 96 hour timeframe and the system may be required to be in use for up to a 3 hour or more uninterrupted use during operation within that 96 hour period. System reliability less than those stated would jeopardize successful accomplishment of the airdrop mission and could provide an unsafe environment for the MFF jumper. The definition of a SA will be defined in the failure Definition and Scoring Criteria (FD&SC). 4.Operational Environmental Parameters. a.Altitude. Must operate at an altitude of up to 24,999 feet (MSL) (T) and 35,000 feet MSL (O). Rationale: The ability to achieve repeated on-ground accuracy, when aerially released from altitudes beyond the range of most threat weaponry, is the essence of a precision airdrop capability. High altitude release increases air carrier, aircrew and jumper survivability. b.Minimum and Maximum Temperature. Operate at a steady temperature of 40 F with a sudden drop to -30 F. Hold at -30 F for 2 minutes followed by a gradual temperature increase of 2 F/minute for 40 minutes (T), Provide operation at a steady temperature of 40 F with a sudden drop to -65 F. Hold at -65 F for 2 minutes followed by a sudden temperature increase of 35 F in 75 seconds then a gradual temperature increase of 2 F/minute for 40 minutes (O). Rationale: These temperature profiles model worst case exposure times for an exit from 24,999 ft MSL (T) and 35,000 ft MSL (O) based on the 1976 US Standard Atmosphere Temperature Profile. Temperature variations at altitude and on the DZ can vary greatly and put a high degree of stress on both the individual and equipment. c.Mechanical Shock: Unit to withstand 7g's shock with all accompanying attachments and remain functional (T). Unit to withstand 10g's and dropped from 36 inches onto concrete and remain functional (O). Rationale: The system will need to withstand any shock that is anticipated during an airborne operation. This includes any and all harness and restraint attachments required for system mounting. d.Light Conditions. The system shall work in day or night light conditions. Rationale: The system will not be limited to visual light conditions and will facilitate safe and effective use, as unit is required to be used during any and all conditions that the system will be doctrinally and operationally allowed. 5.System Storage Environmental Parameters. Minimum and Maximum Temperature in accordance with MIL STD 810-E. Rationale: The system will be stored in a wide variety of temperatures and requires a minimum and maximum parameter in accordance with MIL STD 810-E. 6.System Laptop Connection. Laptop connection must be hardwired and wireless. Rationale: The system must have a hardwired and wireless capability as both a threshold and objective. The contingency if the wireless fails will be hardwired. 7.System GPS Type. GPS type must be Commercial GPS (training mode), Military SAASM via attachable DAGR (operational) external to the system (T) and Military SAASM (internal to the system) (O). Rationale: Systems will have internal commercial GPS. A SAASM GPS capability may be provided via an attachable DAGR radio as a threshold. Internal Military SAASM GPS without a DAGR attachment is an objective. 8.System User Operated Buttons. a.Power. Manual power (on/off) control is required. Rationale: Buttons are required for simplicity and muscle memory. b.Landing Zone. User selectable Landing Zone option is required. Rationale: Buttons are required for switching from one screen to another. c.Brightness. Brightness adjustment is user-controlled (T), automatically adjusts based on ambient light (O). Rationale: Buttons are required to vary the brightness on the system display. Automatic brightness adjustment based on ambient light without user control is an objective. d.Multi-Display Page. Multi-Display Page user operated buttons are required to utilize and toggle between the other existing display screens. Rationale: One switch is required for simplicity and muscle memory. e.SAASM GPS Zeroization. SAASM GPS Zeroization shall be one hand multi-key zeroization. Rationale: SAASM GPS zeroization erases all data from memory for security purposes. Because of the result of this function, it must be difficult to perform to ensure the operation is intentional and not accidental. A required simultaneous three key activation will help to ensure that this is only intentional. 9.System Display Pages. a.Navigational Page. Navigation display page(s) are required (T). Standard and sharable geospatial data (O). Rationale: Display pages assist the jumper to properly navigate to the appropriate drop zone. All new systems require geospatial information as required by ASA (ALT) as of 21 Dec 2007. b.Jump Master Page. Jump master display page(s) are required. Rationale: The jump master display will be accessible to all jumpers and will greatly enhance the JM in correctly identifying the release point. It will also give real-time situational awareness in the aircraft prior to executing an airborne operation. c.Mission Planning Page. Mission planning software and display page(s) are required. Rationale: Mission planning software and display on all systems allows for redundancy in mission planning and system commonality for training. d.Deconfliction Page. Jumper and Cargo Bundle Deconfliction/Collision Avoidance display page(s) are required (O). Rationale: This technology and accompanying human factors considerations such as information over load are not yet mature enough to incorporate into the system. This capability will include the ability to track other jumpers' locations, both altitude and azimuth, and provide a warning if a mid-air collision is imminent. This capability will be a product improvement when the technology is available. e.Topographic Page. Topographic display page(s) are required (O). Rationale: This technology is not yet thought to be mature enough to incorporate into the system. This capability will include different topographical displays to aid jumper orientation. This capability will be a product improvement when the technology is available. f.Moving Maps. Moving maps are required (O). Rationale: This capability will be a product improvement when the technology is available. This will include AGE compliant map data including Raster product Format types, Common Imagery Baseline, Compressed Arc Digitized Raster Graphic, Vector format types, Vector Product Format and shapefile. g.Geospatial Data. Geospatial Information Officer approved Geospatial Data is required. Rationale: All new systems require geospatial information as required by ASA (ALT) as of 21 Dec 2007. 10.System Optical Parameters. a.Focus. Focus will be fixed (T) and adjustable (O). Rationale: Optical focus will be fixed as a threshold and adjustable as an objective. The objective capability will greatly enhance the optical interface by allowing a user to adjust focus to meet individual preference. b.Alignment. Alignment will be fixed (T) and adjustable (O). Rationale: Optical alignment will be fixed as a threshold and adjustable as an objective. The objective capability will greatly enhance the optical interface by allowing a user to adjust alignment to meet individual preference. 11.System Navigation Units. a.Speed. Speed will be displayed as knots (T) and miles per hour (mph), kilometers per hour (kph), and knots (O). Rationale: This will give the individual the choices needed in case different modes of speed are needed. b.Direction. Direction will be displayed as whole degrees. Rationale: This will give the individual the ability to track his or her direction in whole degrees. c.Distance. Distance will be displayed as kilometers (T) and miles (statute), kilometers, and nautical miles (O). Rationale: This will give the individual the choices needed in case different modes of distance are required. d.Altitude. Altitude will be displayed as feet (T) and feet and meters (O). Rationale: This will give the individual the options in case different modes of altitude are required. 12.Satellite Acquisition Parameters. a.GPS Lock. GPS lock required within 10 min of cold start provided a continuous GPS signal with no physical or environmental obstacles preventing satellite reception (T). GPS lock required within 20 seconds of warm start provided a continuous GPS signal with no physical or environmental obstacles preventing satellite reception (O). Rationale: GPS lock must be acquired quickly in order for the system to perform as needed. A warm start refers to a system start in which the GPS almanac has already been acquired. This allows for quick GPS lock reacquisition and is distinct from a "cold start" in which the almanac has not been acquired and may take much longer for GPS lock to be acquired given current technology. b.Speed. Speed will be determined by GPS signal quality. Rationale: The system has the ability to lock on to at least 5 satellites, however environmental effects may hinder the GPS signal quality. Having more satellites that are locked provides the best ability for accurate information. c.Direction. Direction will be determined by GPS signal quality. Rationale: The system has the ability to lock on to at least 5 satellites, however environmental effects may hinder the GPS signal quality. Having more satellites that are locked provides the best ability for accurate information. d.Distance. Distance will be determined by GPS signal quality. Rationale: The system has the ability to lock on to at least 5 satellites, however environmental effects may hinder the GPS signal quality. Having more satellites that are locked provides the best ability for accurate information. e.Altitude. Altitude will be determined by GPS elevation data (T) and a barometric altimeter (O). Rationale: GPS elevation data will be displayed as part of the Navigation and Jumpmaster pages. While reliable this information can occasionally be inconsistent with pressure altitude; as an objective it is desired to include a barometric altimeter as part of the system which is available on COTS/NDI GPS receivers. 13.System Battery Parameters. a.Duration. Battery duration will be 3 hours (T) and >6 hours (O). Rationale: The typical airborne operation is time consuming. Systems will be required to perform for at least 3 hours, but optimally, greater than 6 hours with the option of using multiple soldier power sources to supplement for follow-on use. To enable this, the unit will have a jack to accept a 12V DC power source. b.Rechargeable. Battery will be rechargeable and removable. Rationale: Battery to be rechargeable for economy and be removable for replacement. c.Warning. Low battery warning is required. Rationale: Low battery warning is essential for mission success. d.Hot Swappable. Battery will have 'hot swappable' capability to enable batteries to be swapped without loss of power (O). Rationale: The "hot swappable" capability will allow depleted batteries to be replaced with fully charged ones without the loss of any mission critical data such as the GPS almanac. 14.System Size. The system will be as small and sleek as possible and fit into a protective case equal to or less than 8 inches wide, 3 inches deep and 7 inches in height. Rationale: Size is always a consideration and prevention of line snags is critical. Restriction to the given size envelope is needed to mitigate the risk of equipment interference. 15.System Weight. System weight will be equal to or less than 5 lbs (T), 2.5 lbs (O). Rationale: Weight is an important consideration and should be kept to a minimum. Higher weight would be a hindrance to the jumper and possibly degrade the success of the airborne operations. 16.System Data Refresh/Update Rate. a.System. System refresh/update rate of one (1) Hertz required. Rationale: The one (1) hertz speed is recommended as it will adequately refresh and update the system. b.GPS Receiver. GPS receiver able to log data points at a rate of at least one (1) per second. Rationale: The one (1) hertz speed is recommended in order to record and post data in real time while in freefall and under canopy. 17.Helmet Interface. System must interface with Standard Military Gentex Parachutist, Gentex PM HALO, Commercial Pro-Tec, ACH (T) and Standard Military Gentex Parachutist, Gentex PM HALO, Commercial Pro-Tec & any Improved Ballistic Helmet Design (O). Rationale: This will allow the jumper to use the system with any helmet they are issued. 18.Goggle Interface. System must interface and attach to all goggles currently used for MFF operations (T) and Standard Gentex Parachutist Goggle, Gentex Wind Blast Face Shield, Custom Design Goggle with integrated display, compatible with night vision devices (O). Rationale: This will allow the jumper to use with any set of goggles they are issued. As an objective it is desired that the system interface with night vision devices to realize the full capability of the PARANAVSYS for night time operations. 19.Maintainability. The system will have maintainability of not more than 72 hours Mean Time To Repair (MTTR). Rationale: This will allow commanders to maintain operational capability, minimizing down time for maintenance. 20.Micro-display Connection to the Navigation Unit computer. The system micro-display will be hardwired to the Navigation Unit computer (T), connected via wireless communication (O). Rationale: Current COTS technology requires a hardwired connection to the Navigation Unit computer for utilizing the micro-display capability. A wireless connection is preferred as a P3I objective requirement in order to minimize the risk of equipment interference. 21.GPS Retransmission Kit. The system will include a GPS Retransmission Kit (RTK) to rebroadcast GPS signal onboard the operational aircraft prior to personnel exit. The GPS retransmission kit will have the following performance characteristics: a.L1/L2 Signals. The GPS RTK shall be able to receive and rebroadcast both L1 and L2 GPS signals with no interference to the aircraft. Rationale: GPS signal must be available onboard all training and operational aircraft to take full advantage of the capabilities of the PARANAVSYS. GPS availability prior to exit will allow the jumpmaster to use the jumpmaster display screen for release point identification. GPS rebroadcast onboard the aircraft will also allow the system to reacquire satellites from a "warm start" with a pre-acquired almanac as opposed to a "cold start" with an empty almanac which may take much longer. The GPS RTK shall rebroadcast both commercial and military GPS signals in the bands 1575.42 +/- 12 MHz (L1) and 1227.6 +/- 12MHz (L2). The RTK shall be designed to ensure that all efforts are taken to mitigate the rebroadcast of all signals outside of these bands. Any such emissions must be attenuated to a negligible level so that the GPS RTK will not interfere with the aircraft's navigational system. To mitigate the possibility of interference with other aircraft the maximum Effective Isotropic Radiated Power (EIRP) must be such that the calculated or measured emissions at 1575.42MHz (L1) and 1227.6 MHz (L2) are no greater than -141dB/24MHz as received by an isotropic antenna at a distance of 10 meters from the aircraft skin with all access doors open. b.Compatibility. The GPS RTK must be compatible with all aircraft that support military freefall operations such as CASA 212, C-23, C-130 Series (T), and C-17, CH-47, CH-53 and UH-60 (T=O). Rationale: The PARANAVSYS will be used on a variety of aircraft for both training and HAHO operations. The GPS RTK must be capable of installation onboard all potential aircraft and rebroadcast to an area containing up to 15 jumpers. A versatile RTK will be required which can be easily installed on each of these aircraft without a change in GPS signal rebroadcast performance or reliability. To account for the different sized aircraft which may be used the GPS RTK will have an Effective Isotropic Radiated Power (EIRP) level that can be adjusted based on aircraft type. The RTK will also be configurable to accommodate different aircraft sizes with one or several passive antennas as required. Power will be supplied through either a DC connection to the aircraft or through a BA5590 Lithium Sulfur Dioxide battery. Power interface and EMI will be tested in accordance with MIL STD 704, 461F and 464A. The GPS RTK will function in a rugged operational environment and be tested in accordance with MIL STD 810-G. c.Reliability. The GPS RTK will meet the system level reliability requirements specified in Capability 3 above. The RTK system must provide a 95 percent probability of achieving a successful mission. A successful mission will be free from the occurrence of a system abort (SA) for a period of 3 hours (T) 6 hours (O). Rationale: Operators are required to conduct mission planning throughout a 96 hour timeframe and the system may be required to be in use for a 6 hour uninterrupted use during operation within the 96 hour period, System reliability less than those stated would jeopardize successful accomplishment of the airdrop mission and could provide an unsafe environment for the MFF jumper. A system abort (SA) for the GPS RTK is defined as a failure to rebroadcast L1 and/or L2 signals onboard a required aircraft despite outside signal availability and proper GPS receiver functioning for the navigation unit. A SA is declared only after standard troubleshooting procedures have been followed and have failed to correct the problem. 22.Landing Zone. a.Quantity. Selectable Landing Zones will be three (T) and five (O). Rationale: The optional drop zones give the jumper the ability to select alternate drop zones in case primary drop zones cannot be reached. This provides additional means for mission success and force protection, as teams will have the ability to stay assembled. This will enhance their situational awareness. b.Entry Coordinate System. Entry coordinate system will be user selectable to Decimal Degrees, Degrees-Decimal Minutes, Degrees-Minutes-Seconds, UTM, and MGRS. Rationale: This gives the option to enter any method of information into the system for correct location monitoring. c.Coordinate Conversion. System shall conduct coordinate conversion from MGRS to Lat Long and Lat Long to MGRS. Rationale: Both coordinate systems are routinely used during HAHO operations. Conversions between the two coordinate systems are frequently needed. 23.Wind Data. a.Magnitude Entry. Magnitude entry will be whole number knots (T) and user selectable whole number mph, kph, and knots (O). Rationale: This gives the option to retrieve any method of measuring wind speed. b.Direction. Direction will be whole degrees. Rationale: Whole degrees are a standard means of articulating direction using a compass. c.Data Entry. Wind data will at a minimum be uploadable from the Joint Air Force and Army Weather Information Network (JAAWIN) forecast files with manual entry available as an alternative. Rationale: This provides the option of automatically uploading or manually entering wind data. d.Altitude. Altitude (MSL) will be from 0 ft, 3000 ft, 6000 ft, 9000 ft, 12000 ft, 18000 ft, 24000ft, 30000 ft (T) and user selectable between feet and meters (m) in 1000 ft increments (or metric equivalent) to 35,000 ft, and receive and interpolate sonde data (O). Rationale: This gives the option to use either standard measurements in feet or measurements in meters. Sonde data collection via the JPADS MP is an objective. 24.System Requirements. System shall be embedded with Windows based operating system. Rationale: Windows will be used as the operating system. The operating system will be compatible with Windows XP or a more recent Windows version. 25.Send/Confirmation. Mission Planning software capable of displaying on the Mission Planner screen information to send to each of the jumpers (15 minimum) and a screen showing that each GPS unit has received the data and has been updated with the latest information. Rationale: This gives the option to confirm the information being sent and verify that the information was received by all jumpers. 26.DATA stream to GPS unit. a.Mission Planning. Mission planning screen displays LZ locations, setup units, user ID, wind data (directions, magnitudes, and altitudes), and parachute characteristics (K factor, safety factor and glide ratio). Rationale: This setup information will insure that all jumpers have the right information pertaining to the parachute system that is being used and that key information needed has been received. b.Operational Mode. Operational mode screen displays LZ locations, setup units, wind data (directions, magnitudes, and altitudes), and parachute characteristics (T), and operational mode screen displays LZ locations, setup units, user ID, wind data (directions, magnitudes, and altitudes), parachute characteristics, IDs and locations of other jumpers and/or cargo bundles using line of sight or other enhanced communication technologies (O). Rationale: Threshold information provides mission planning considerations. Objective information, when available, will give all jumpers situational awareness to mitigate the risk of in-air collisions with cargo bundles and/or jumpers in the air. 27.Interface Display. a.Mission Planning. Mission planning displays user ID, confirmation of update of info. Rationale: The mission planning information will insure that all jumpers have the right information pertaining to the parachute system that is being used and that key information needed has been received. b.Operational Mode. Operational mode displays confirmation of update of info. Rationale: The operational mode will insure that all jumpers have the right information pertaining to the parachute system that is being used and that key information needed has been received. c.Operational Mode User ID/Location. Operational mode display will indicate user ID's and location (latitude, longitude, and altitude) (O). Rationale: This operational mode information will insure that all jumpers have the right information pertaining to the parachute system that is being used and that key information needed has been received. User ID and location will be sent from the GPS unit to facilitate situational awareness and collision avoidance. 28.DATA stream from other embedded GPS Units (Multi-jumper location mode). Operational mode will indicate user ID's and location of jumper (latitude, longitude, and altitude) using line of sight or other enhanced communication technologies. Rationale: This information, when available, will give all jumpers situational awareness of other jumpers and cargo and cargo update capabilities while both are under canopy. 29.Joint Precision Airdrop System Compatibility. a.Sonde Data. Ability to utilize JPADS sonde data when available. Rationale: The JPADS MP and accompanying kit also include a wind sonde data collection capability to feed in real winds to a mission file just prior to executing a jump. This will give jumpers the advantage of the most up to date wind data available to aid in accomplishing their intended mission. b.Mission Planner. The PARANAVSYS mission planning software will be fully compatible with the JPADS Mission Planner (O). Rationale: The JPADS system is the standard precision airdrop mission planner used on Air Force aircraft. It is desired that the PARANAVSYS be fully compatible with the JPADS Mission Planner to take advantage of this common system and its capabilities. The objective performance attribute is full compatibility with the JPADS MP. PARANAVSYS will have the ability to utilize JPADS sonde 'file' data when available. All interested firms and manufacturers, regardless of size, are encouraged to respond to this request for information. Information submissions should include available technology, product literature and illustrations, and relevant company background/experience. Available product pricing will also be provided as part of the information submission. If a company does not possess a commercial product currently capable of satisfying these requirements but is interested in developing this technology the POC for this Sources Sought notice will accept a white paper detailing development plans to include schedule and funding requirements. Information submissions must be received by 15 April 2011. Responses to this notice should be directed to: Natick Soldier Research, Development and Engineering Center, Product Manager Soldier Clothing and Individual Equipment, Personnel Airdrop Team, ATTN: Brian Huffman, Natick, MA 01760-5057 or e-mail to Brian.G.Huffman@us.army.mil. All information supplied will be considered confidential, unless otherwise specified by the firm or available from other sources without restriction. This Market Survey is for information and planning purposes only and does not constitute an Invitation for Bid (IFB) or a Request for Proposal (RFP) and is not to be taken as a future commitment by NSRDEC.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/dcfa9cf36d6fd33b17e8d48d08f18495)
 
Place of Performance
Address: RDECOM Contracting Center - Natick R&D (RDECOM-CC) ATTN: AMSRD-ACC-N, Natick Contracting Division (R and BaseOPS), Building 1, Kansas Street Natick MA
Zip Code: 01760-5011
 
Record
SN02388137-W 20110227/110225234540-dcfa9cf36d6fd33b17e8d48d08f18495 (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-2020, Loren Data Corp.