InvestorsHub Logo
icon url

24601

11/03/11 7:44 PM

#217378 RE: goin fishn #217376

The Department of Defense comprises more than just the military departments and "a few smaller specialty services." (By the way, the Coast Guard operates under the Department of Transportation most of the time.)

In any case, one poster seemed to indicate that the Air Force data-at-rest procurement depends on some discrete eligibility requirement.

The question is not whether anybody knows the composition of the DoD. The question is whether Wave has taken the steps necessary to be in a position to compete for the AF DAR business. I'm pretty sure that saying they're "about to sign the entire DoD" doesn't do it.








.
icon url

mjan112

11/03/11 7:49 PM

#217379 RE: goin fishn #217376

There is no way they sign a DoD contract, such a thing doesn't even exist - DoD contract. There are 100s of contract vehicle and mini domains within in branch of the Armed Forces. The Office of SecDef can set requirements and the Exec office has overall jurisdiction but there will be lots of mini contracts. They will probably each need a systems integrator as well . Each one meets a set of requirements. The requirements will be set this spring, and Wave may be the only company that can supply these future reqs.

How to become an ESI

http://www.esi.mil/download.aspx?id=527


VQ1. How does a company become an ESI Agreement holder?

Under ESI, the DoD leverages its aggregate buying power to establish enterprise agreements with information technology (IT) manufacturers and resellers for high demand, commercial off-the-shelf IT products and services. The ESI does not determine requirements for specific software products and services. Rather, it provides a service to the customer (program office, etc.) after they selected the most appropriate solution based on functionality, architecture, technical requirements, etc.

The process of becoming a vendor under the ESI program can be initiated by either the customer or the vendor. Either party may propose establishing an enterprise agreement. Vendor motivations are numerous and include a desire to consolidate existing agreements or group product and service offerings into more marketable packages.

To work effectively, ESI takes the time to understand the vendor’s business model and to provide education regarding the ESI process. The DoD is motivated to create a strategic vendor relationship and uses the following general criteria for establishing enterprise agreements:

? ?The vendor provides DoD with improved terms, conditions and prices over those available under GSA schedule and similar contracts.

? ?There is sufficient demand for the product(s) and demand can be forecast with a relative degree of confidence. We also consider the product’s existing usage or install base. The install base includes all DoD users, the U.S. Coast Guard, the Intelligence Community, and authorized Defense Contractors.

? ?Products are available under a GSA schedule. While this is not a firm requirement, it is desired for a streamlined acquisition process. ESI’s preferred approach is to place a blanket purchase agreement (BPA) against a vendor’s GSA schedule.

? ?The vendor agrees to our standard terms and conditions. This includes providing monthly sales and activity reports, attending semiannual program reviews, actively marketing the agreement, granting the right to deploy and reuse the license, home use, etc. (BPA samples may be downloaded from the ESI website to see examples of our terms and conditions.)

? ?Necessary fees are included in the product’s prices and are collected and paid by the vendor on a regular basis. These fees are currently a .75% GSA industrial funding fee (IFF) and a 2% administrative, contracting and technical (ACT) fee.

? ?Products are compliant with appropriate standards including the DoD Joint Technical Architecture and Section 508 of the Rehabilitation Act related to accessibility by disabled persons.

In summary, there must be a business case established to justify the cost of awarding and maintaining an enterprise agreement. Generally, these are not mandatory contract vehicles; however, customers must follow the process described in the Defense Federal Acquisition Regulation Part 208.74, the DoD policy on SmartBUY, and any Defense Component unique policies. In addition, if the DoD ESI has Co-branded an Enterprise Software Agreement under the SmartBUY program, a specific Federal-wide policy on use will be issued. In all cases, the success of the agreement depends on most favorable pricing and high demand for the products and services. Vendors interested in initiating this process with the DoD ESI may contact the DoD ESI Working Group Co-Chairs or any of the other DoD ESI Working Group members listed in the ESI brochure. The brochure may be found under the "About ESI" tab located on the home page of the ESI web site http://www.esi.mil/download.aspx?id=525 (scroll down the page and open the document labeled "ESI Points of Contact".)

Additional information may be obtained by selecting the “Vendor’s Tool Kit” link on the ESI home page under “Vendor Information”.
icon url

Workingcapital

11/04/11 1:41 AM

#217394 RE: goin fishn #217376

ICBW, but I think Cyber is part of the 24th AF.