Waiting for Alliant

After much delay, GSA vows to roll out its governmentwide contract for technology purchases next year.

Alliant, the $65 billion contract to provide the government with private-sector information technology services, is coming, promises the General Services Administration. It didn't come yesterday or today, but messengers say it surely will be ready soon. In the meantime, agencies and companies wait.

Alliant was supposed to be in the final stretch of development by now. GSA came up with the idea in mid-2003, announcing the contract in January 2004. Now the agency projects that a final request for proposals will be ready by October, with awards made by summer 2007. Probably just in time to miss the annual end-of-fiscal-year buying frenzy, predicts John Okay, a former GSA senior official, now a partner at Vienna, Va.-based Topside Consulting.

But the wait is necessary, says John Johnson, GSA's executive in charge of overseeing the contract. All the delays prior to his watch, which began in September 2005, added up to a critical mass of postponement, requiring a rethink of the entire procurement, Johnson contends. "Because it had been under way for so long, it required a second look," he says. It took about two months for the new Alliant team to prepare a revised approach and just as long to get intergovernmental approval to launch it, according to a GSA timeline.

On Feb. 21, GSA went public with its new strategy, though by the end of the day it became apparent that details remain to be worked out.

That morning, GSA posted a 20-minute online video featuring Johnson and Alliant Project Manager Jim Ghiloni. In it, Ghiloni said Alliant will be modified to feature a mechanism to certify and decertify Alliant vendors. The contract's statement of work will change to align with the federal enterprise architecture, an Office of Management and Budget effort to classify and control government IT expenditures. The number of functional areas in the contract's $15 billion small business set-aside might increase from two to four, potentially increasing the number of vendors awarded a slot on the contract.

"That information was less detailed, less specific than everybody in industry was hoping for," says Okay. The video "raised about as many questions as it answered."

For example, what does GSA mean by aligning the statement of work with the federal enterprise architecture? In the video, Ghiloni explained that a typical statement of work resembles a grocery list, with specific products, when it should resemble a directory of food categories. The enterprise architecture approach posits that agencies will always go grocery shopping, but that brands and tastes could change over time. Rather than list all the cereals that agencies could buy, Alliant should allow agencies to pick the best cereal possible at the moment of buying breakfast. This is especially important since over the probable life of the contract-five years with a five-year option to extend-the services likely will change.

But the federal enterprise architecture isn't a monolith; it consists of five documents called reference models and an additional three documents called profiles. Ghiloni says further details on how the statement of work will align with that strategic plan will be revealed in next draft RFP, due for release in June.

Certification and recertification is a matter of particular interest, too. GSA will periodically review vendors' performance and ability to meet the contract's requirements. Low- and poor-performing vendors will be given the boot. Small companies no longer certified as small also will be eased from their Alliant spots. Ghiloni says that "off-ramping" a company won't necessarily trigger a competition for replacement. That will depend on cost-benefit analyses.

But will new competitions simply replace lost vendors to keep the number of contractors stable, or could new slots open up? "That is one of the issues we're examining," Ghiloni says.

Johnson stresses that a goal of the online video is to initiate dialogue and receive feedback. "We are doing our best to move it forward as quickly as possible," he says. In the meantime, however, the market isn't standing still.

Interested companies' bid and proposal costs are mounting, to the point that some might be reconsidering whether Alliant is worth the expense, Okay says. Other federal agencies have come out with their own IT contracts, notably the Homeland Security Department and the Defense Information Systems Agency. The longer GSA waits to complete Alliant, the more incentive agencies have to shop elsewhere.

"Is GSA at a competitive disadvantage because it took so long? Yes," says Phil Kiviat, a government information technology market consultant. At the same time, agony over the delays is misplaced, he insists: "What has happened has happened, and we're looking forward."

Alliant is the replacement for two existing GSA contracts-Applications 'n Support for Widely Diverse EndUser Requirements, known as ANSWER, which expires in December 2008, and Millennia, which ends in April 2009.

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.


When you download a report, your information may be shared with the underwriters of that document.