Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JULY 16, 2008 FBO #2424
SOLICITATION NOTICE

C -- INDEFINITE DELIVERY TYPE CONTRACT FOR HYDROLOGIC ENGINEERING SERVICES, FOR THE OMAHA DISTRICT CORPS OF ENGINEERS.

Notice Date
7/14/2008
 
Notice Type
Modification/Amendment
 
NAICS
541330 — Engineering Services
 
Contracting Office
Department of the Army, U.S. Army Corps of Engineers, U.S. Army Engineer District, Omaha, US Army Corps of Engineer - Omaha District, 106 S. 15th Street, Omaha, NE 68102-1618
 
ZIP Code
68102-1618
 
Solicitation Number
W9128F-08-R-0005
 
Response Due
7/31/2008
 
Archive Date
8/15/2008
 
Point of Contact
Jan M Cook,, Phone: 402-995-2052
 
E-Mail Address
jan.m.cook@usace.army.mil
 
Small Business Set-Aside
Total Small Business
 
Description
The following information is added to provide clarification information for parties interested in Contractor Teaming Arrangements under the Small Business program. Contractor Team Arrangements 1. Contractor Team Arrangements as used in this solicitation, resultant proposals and contracts means an arrangement in which (1) Two or more companies form a partnership or joint venture to act as a potential prime contractor; or (2) A potential prime contractor agrees with one or more other companies to have them as its subcontractor for the requirement indicated in this solicitation. 2. Joint-Venture, for the purpose of this solicitation, is an association of individuals and/or concerns with interests in any degree or proportion by way of contract, express or implied, consorting to engage in and carry on more than three specific or limited-purpose business ventures for joint profit over a two year period, for which purpose they combine their efforts, property, money, skill, or knowledge, but not on a continuing or permanent basis for conducting business generally. 3. The Contracting Officer will recognize the integrity and validity of contractor team arrangements; provided, the arrangements are identified and company relationship are fully disclosed and validation of formal agreements and relationships (i.e., Mentor-Protégé agreements, joint-ventures, partnerships, etc) are provided in the offer and submitted with the proposal responding to the solicitation. 4. Nothing in the solicitation authorizes contractor team arrangements in violation of antitrust statutes or limits the Government’s rights to: (1)Require consent to subcontracts (FAR Subpart 44.2). (2)Determine, on the basis of the stated contractor team arrangement, the responsibilities of the prime contractor. (3)Provide to the prime contractor data rights owned or controlled by the Government. (4)Pursue its policies on competitive contracting, subcontracting, and component breakout and initial production or any other time; and (5)Hold the prime contractor fully responsible for contract performance, regardless of any team arrangement between the prime contractor and its subcontractors. Joint Ventures and Affiliation 1. The joint venture is viewed as a business entity in determining power to control its management. For the purpose of this solicitation, a joint venture entity cannot submit more than three offers over a two year period, starting from the date of the submission of the first offer. 2. The Contracting Officer may determine if the relationship between a prime contractor and its subcontractor is a joint venture, and that affiliation between the two exists. 3. A joint venture of two or more business concerns may submit an offer as a small business in response to this solicitation without regard to affiliation so long as each concern is small under the size standard corresponding to the NAICS code assigned. 4. Parties to a joint venture are affiliates if any one of them seeks SBA financial assistance for use in connection with the joint venture. 5. A joint venture of two or more business concerns may submit an offer as a small business for a Federal procurement without regard to affiliation as long as each concern is small under the size standard corresponding to the NAICS code assigned to the solicitation. 6. A joint venture of at least one 8(a) Participant and one or more other business concerns may submit an offer for a competitive Section 8(a) procurement without regard to affiliation so long as the size requirements depicted in the paragraph below (Section 8(a)) are met. 7. The completed approved joint venture agreement must be submitted with the initial offer to the solicitation. Include a list (by agency name and solicitation number) of the proposals you have submitted to the federal government within the last two year utilizing the approved joint-venture agreement you plan to submit in response to this solicitation. Section 8(a) Joint Venture Requirements 1. A joint venture of at least one Section 8(a) Participant and one or more other business concerns may submit an offer as a small business for a competitive Section 8(a) acquisition so long as each concern is small under the NAICS code assigned to the solicitation, provided at least one of the Section 8(a) Participants to the joint venture is less than one half size standard corresponding to the NAICS code assigned to the solicitation. The joint-venture agreement must be provided with submission of the initial offer to the solicitation. 2. A joint venture between a Section 8(a) Participant and its approved Mentor will be deemed to be small provided the Protégé qualifies as small for the size standard corresponding to the NAICS code assigned to the solicitation. The Mentor-Protégé Agreement and Joint-Venture must be approved by the Small Business Administration. The approved Mentor-Protégé Agreement and Joint-Venture Agreement must be provided with submission of the initial offer to the solicitation. 3. The Joint-Venture Entity must be registered in Central Contract Registration database at www.ccr.gov. 4. Contract your assigned Business Opportunities Specialist, Business Development Division at your Servicing SBA District Office for detailed information regarding SBA’s Mentor-Protégé Program and participation requirements. HUBZone Joint Venture Requirements A joint venture may submit an offer of a HUBZone set-aside if the joint venture meets all of the following requirements. 1. A qualified HUBZone small business may enter into a joint venture with another qualified HUBZone small business for the purpose of submitting an offer for a HUBZone contract. The joint venture itself need not be certified as a qualified HUBZone. 2. A joint venture of two of more qualified HUBZones may submit an offer fora HUBZone contract so long as each concern is small under the size standard corresponding to the NAICS code assigned to the contract. The HUBZone joint venture, in the aggregate, may exceed the size standard provided the procurement (i) for a procurement having a revenue-based size standard, the procurement exceeds half the size standard corresponding to the NAICS code assigned to the contract; and, (ii) for a procurement having an employee-based size standard, the procurement exceeds $10 million. 3. For a procurement that does not exceed the applicable dollar amount specified in paragraph above, a joint venture of two or more qualified HUBZones may submit an offer for a HUBZone contract so long as the qualified HUBZones in the aggregate are small under the size standard corresponding to the NAICS code assigned to the contract. 4. The aggregate of the qualified HUBZones to the joint venture, not each concern separately, must perform the required percentage of work. 5. A qualified HUZone may not joint venture with its approved Mentor in a Mentor-Protégé agreement (relationship) unless the Mentor is also a qualified HUBZone small business concern. Service Disabled Veteran Owned SB Joint-Venture Requirements At time of initial offer, the Service-Disabled Veteran Owned (SDVOSB) must be small within the size standard corresponding to the NAICS code assigned to the solicitation. A joint venture of at least one SDVOSB and one or more business concerns may submit an offer as a small business for a competitive SDVOSB procurement so long as each concern is small under the size standard corresponding to the NAICS code assigned to the contract provided: 1. For a procurement having a revenue-based size standard, the procurement exceeds half the size standard corresponding to the NAICS code assigned to the contract. 2. For a procurement having an employee-based size standard, the procurement exceeds $10 million. 3. For sole source and competitive SDVOSB procurements that do not exceed the dollar levels identified in 1 and 2 above, an SDVOSB entering into a joint venture agreement with another concerns is considered to be affiliated for size purposes with the other concern with respect to performance of the SDVOSB contract. The combined annual receipts or employees of the concerns entering into the joint venture must meet the size standard for the NAICS code assigned to the SDVOSB solicitation. 4. Every joint venture agreement to perform a SDVOSB contract must contain provisions (i) setting forth the purpose of the joint venture (ii) designating the SDVOSB as the managing venture and its employee as the responsible project manager for performance (iii) designating 51% of the net profit earned by the joint venture will be distributed to the SDVOSB. 5. The Joint-Venture Entity must be registered in Central Contract Registration database at www.ccr.gov. 6. The resultant contract will be executed in the name of the joint venture entity. 7. The joint-venture agreement must be provided with submission of the initial offer to the solicitation. All other information previously submitted remains unchanged.
 
Web Link
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=f6b7cdb3c972281dc445d5ab4b343498&tab=core&_cview=1)
 
Place of Performance
Address: US Army Corps of Engineer - Omaha District 1616 Capitol Avenue Omaha NE
Zip Code: 68102
 
Record
SN01613697-W 20080716/080714223250-f6b7cdb3c972281dc445d5ab4b343498 (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.