Procurement Archives

Foreigners who aspire to work for federal contractors can now use a Spanish-language website to make sure their correct immigration status is on file with the government before their employers are required to do so -- avoiding potential unemployment.

All personnel doing business with the government must pass muster with e-Verify, an online system that U.S. businesses use to check the employment eligibility of new hires. In March, U.S. Citizenship and Immigration Services, an arm of the Homeland Security Department, began offering an English-version of the system - e-Verify Self Check -- in a few states for foreign jobseekers to check that their personal information is accurate.

On Tuesday, USCIS announced a Spanish version is now available and the service has been expanded to 16 additional states. Nationwide rollout is expected by the spring.

Federal vendors often complain e-Verify contains errors such as missing Social Security numbers that generate messages showing a hire has no legal documentation. If that happens, the employee only has eight days to start working with the Social Security Administration to resolve the mistake. Otherwise, the staffer could lose his or her job.

You can try e-Verify Self Check if you live in California, Louisiana, Maine, Maryland, Massachusetts, Minnesota, Missouri, Nebraska, Nevada, New Jersey, New York, Ohio, South Carolina, Texas, Utah, Washington, Arizona, Colorado, Idaho, Mississippi, Virginia and the District of Columbia.

It's all cloud, all the time in federal IT these days, especially since the Office of Management and Budget ordered agencies to take a cloud-first approach to IT projects. Mary Davie, assistant commissioner for the Office of Integrated Technology Services in the General Services Administration's Federal Acquisition Service, provides a reality check on cloud mania today, with a blog post aimed at busting four myths about cloud computing in the federal sector.

Those myths, according to Davie, are:

• Cloud can be anything.
• Public clouds are not secure, and agencies can't control security requirements.
• Agencies will lose control of their data.
• Moving to the cloud is difficult.

White House officials on Wednesday circulated a memo, obtained by Nextgov, that encourages procurement officers to communicate with contractors before finalizing solicitations, in an effort to dispel misperceptions about conflicts of interest.

The idea is that companies know the costs and features of current technology better than the government so potential bidders should be consulted early in the process of drawing up system requirements for contracts.

"Although industry may have had their best technical representatives engaged with the program manager, the contracting officer should communicate to vendors as much information as possible about the government's needs as early as possible," states a copy of the guidance, signed by Federal Procurement Policy Administrator Daniel Gordon. "As a result of early communication, the contracting officer may learn some things that suggest that an approach somewhat different than planned may cause increased competition, more small business participation, lower prices, or even a better definition of the government's technical requirements."

Fears of contract protests or signing unauthorized deals have prevented some acquisition officers from talking to vendors, according to the memo. At the same time, industry may stay away -- out of concern that stepping over boundaries may bar them from future government business.

The document requires agencies by June 30 to develop plans for communicating with contractors. After the plans are reviewed by the White House, they must be made publicly available within a month.

Wednesday's memo takes pains to stress that nothing within the guidelines should be interpreted to "alter, or authorize violations of, applicable ethics rules, procurement integrity requirements, or other statutes or regulations that govern communication and information sharing."

After discussions with company representatives and agency staff, the White House identified the 10 most frequently-mentioned misconceptions about contractor-government fraternization:

1. "We can't meet one-on-one with a potential offeror." Fact: Government officials can generally meet one-on-one with potential offerors as long as no vendor receives preferential treatment.
2. "Since communication with contractors is like communication with registered lobbyists, and since contact with lobbyists must be disclosed, additional communication with contractors will involve a substantial additional disclosure burden, so we should avoid these meetings." Fact: Disclosure is required only in certain circumstances, such as for meetings with registered lobbyists. Many contractors do not fall into this category, and even when disclosure is required, it is normally a minimal burden that should not prevent a useful meeting from taking place.
3. "A protest is something to be avoided at all costs -- even if it means the government limits conversations with industry." Fact: Restricting communication won't prevent a protest, and limiting communication might actually increase the chance of a protest, in addition to depriving the government of potentially useful information.
4. "Conducting discussions or negotiations after receipt of proposals will add too much time to the schedule." Fact: Whether discussions should be conducted is a key decision for contracting officers to make. Avoiding discussions solely because of schedule concerns may be counter-productive, and may cause delays and other problems during contract performance.
5. "If the government meets with vendors, that may cause them to submit an unsolicited proposal and that will delay the procurement process." Fact: Submission of an unsolicited proposal should not affect the schedule. Generally, the unsolicited proposal process is separate from the process for a known agency requirement that can be acquired using competitive methods.
6. "When the government awards a task or delivery order using the Federal Supply Schedules, debriefing the offerors isn't required so it shouldn't be done." Fact: Providing feedback is important, both for offerors and the government, so agencies should generally provide feedback whenever possible.
7. "Industry days and similar events attended by multiple vendors are of low value to industry and the government because industry won't provide useful information in front of competitors, and the government doesn't release new information." Fact: Well-organized industry days, as well as pre-solicitation and pre-proposal conferences, are valuable opportunities for the government and for potential vendors -- both prime contractors and subcontractors, many of whom are small businesses.
8. "The program manager already talked to industry to develop the technical requirements, so the contracting officer doesn't need to do anything else before issuing the RFP." Fact: The technical requirements are only part of the acquisition; getting feedback on terms and conditions, pricing structure, performance metrics, evaluation criteria, and contract administration matters will improve the award and implementation process.
9. "Giving industry only a few days to respond to an RFP is OK since the government has been talking to industry about this procurement for over a year." Fact: Providing only short response times may result in the government receiving fewer proposals and the ones received may not be as well-developed -- which can lead to a flawed contract. This approach signals that the government isn't really interested in competition.
10. "Getting broad participation by many different vendors is too difficult; we're better off dealing with the established companies we know." Fact: The government loses when we limit ourselves to the companies we already work with. Instead, we need to look for opportunities to increase competition and ensure that all vendors, including small businesses, get fair consideration.

The Homeland Security Department has begun the process of contracting to replace the border security network it scrapped last week, by issuing a request for information on interconnected surveillance towers, department officials said on Wednesday.

The market research is part of the department's new plan to acquire proven, ready-made technology tailored to the terrain of each border region, as opposed to the now-defunct $1 billion Secure Border Initiative network. The SBInet program ran into cost, schedule and performance problems in an unsuccessful attempt to install a one-size-fits-all virtual fence composed of monitoring devices, intelligence databases and communication links.

Depending on budget decisions, a formal request for bids on the project might be issued late this fiscal year, with contracts awarded several months after that, DHS spokesman Matthew Chandler said.

The RFI for so-called integrated fixed towers, which was posted Tuesday on the contracting bulletin board FedBizOpps, asks vendors for comments on market conditions and scientific advances to help shape "an acquisition strategy for technology solutions that detect, track, identify and classify illegal incursions." The technology is intended to provide border agents with a full view of activity between ports of entry to stop drug smuggling, illegal immigration and terrorist-related activities. Comments are due Feb. 8.

"The RFI approach is one tool available to us to involve industry at an early stage in our process," Chandler said.

Department officials will start procuring stand-alone tower parts this fiscal year, Chandler added. He said the decision to move ahead with the non-integrated tower elements was based on the priorities of DHS' Customs and Border Protection bureau.

DHS is looking for tools that will offer automatic, continuous wide-area surveillance that are largely open, or not tied to any one brand's proprietary technology, according to Tuesday's notice. Contracting officers envision a system consisting of several towers, where each one is equipped with a suite of sensors for constant surveillance; supporting power; and communications.

The applications will instantly identify humans, animals, vehicles and other suspicious items, as well as provide agents with video to inspect the scene manually for backpackers or people carrying certain weapons. The video will enable border personnel "to classify the threat in terms of group size, whether they are migrant workers, smugglers, etc, and whether they are armed," the RFI states.

The system will display the precise location, speed and direction of suspicious activity, according to the notice. The technology also will draw from pre-existing data feeds that were launched during the SBInet program. The tower equipment and network connectivity must withstand extreme weather conditions and harsh environments, such as the Arizona deserts and mountains where DHS initially had begun deploying SBInet.

White House officials on Friday sent agency chief information officers and senior procurement executives a memo directing them to weigh open source options when buying technology.

Open source refers to technology based on nonproprietary parts, which allow third-party developers to improve and modify the product without having to pay the technology's maker. Advocates have said a move toward open source in the government could save taxpayer dollars and bolster security.

For example, in planning software purchases, "agencies should analyze alternatives that include proprietary, open source and mixed source technologies," states the policy, co-signed by Federal CIO Vivek Kundra, Dan Gordon --- Office of Federal Procurement Policy administrator, and Victoria Espinel, U.S. Intellectual Property Enforcement Coordinator.

The guidance reminds agencies that, according to existing policies, buying decisions should "be free of preconceived preferences based on how the technology is developed, licensed or distributed."

Agency officials "should follow technology neutral principles and practices," which include selecting suitable technology on a case-by-case basis by considering factors such as performance, cost, security, compatibility, ability to share or re-use and availability of quality support, the one-page document states.

Hewlett Packard has nabbed a 10-year NASA megadeal potentially worth $2.5 billion to manage employees' personal computers and peripheral technology, space agency officials announced on Monday.

The job entails providing, securing and servicing most staff computers, agency software, mobile technology services, printers and other supporting infrastructure. Herndon, Va.-based HP Enterprise Services, formerly EDS, will be responsible for outsourcing some of the tasks to other commercial vendors under the contract known as "ACES," for Agency Consolidated End-user Services.

The fixed-price pact covers four base years of work, with two three-year option periods. Program managers will be based at NASA's shared services center in Mississippi.

ACES is part of a larger NASA effort, the IT Infrastructure Integration Program, intended to save money by consolidating procurements and centralizing information technology services. The new HP deal will replace an older long-term contract currently held by Lockheed Martin Corp. called the Outsourced Desktop Initiative (ODIN).

In February, Lockheed, one of the most established NASA business partners, announced the space agency had awarded the company a $230 contract extension for ODIN that ends in Oct. 2011.

The Mississippi facility where ACES will be managed -- operated by NASA, Computer Sciences Corp. and the states of Mississippi and Louisiana -- supports operations at all 10 NASA space centers.

White House officials on Thursday morning released a 25-point implementation plan to execute one of the biggest information technology contracting overhauls since the 1996 Clinger-Cohen Act.

The problem the plan aims to tackle: Productivity gains in the private sector have outpaced government performance even though federal agencies spent about $600 billion during the past decade on technology to boost efficiency. The Obama administration's policy roadmap aims to dismantle the old way of installing new technology - which has been to design overly-ambitious systems that fall years behind in development - and create new procedures for quickly and cheaply upgrading machinery.

Here are some of the standouts on the to-do list:

• Reshape or terminate at least one-third of underperforming projects in the government's $80 billion IT portfolio within the next 18 months.
• Shift to a "cloud first" policy, where agencies consider moving to Web-based software and hardware before spending money on new systems. Each agency will identify three must-move services within three months, shift one of those services to the cloud within 12 months and then transition the remaining two within 18 months.
• Within 12 months, establish a tech fellows program modeled after the Presidential Management Fellows program to recruit graduate students with in-demand talents into IT program management.
• By mid-June, launch a website where industry and agency contracting officials can collaborate prior to the issuance of requests for proposals.

During a webcast next Thursday morning, Office of Management and Budget officials will flesh out the Obama administration's recently-announced strategy to update the way agencies acquire and access information technology. The Dec. 9 Forum on IT Management Reform will be held at the White House at 8:30 a.m. and streamed live here, according to an administration official.

Federal Chief Performance Officer Jeffrey Zients and federal Chief Information Officer Vivek Kundra will discuss detailed execution plans for the initiative and take questions from government IT managers and contracting officials, as well as IT vendors.

The thrust of the strategy -- which was unveiled Nov. 19 -- is to expedite the process of upgrading IT systems by moving equipment online to the cloud; matching the technology refresh cycle with the congressional appropriations cycle; cultivating a cadre of professional program managers; encouraging communication between agency managers and the IT community; and holding in-person meetings with senior executives and program managers to review projects.

GSA predicts its move to a cloud-based e-mail system for all employees will be a good thing in the long run, but the agency's chief information officer acknowledged some immediate challenges on Thursday.

Information security is the paramount concern with the switch to the system that will use the Google Apps for Government platform, said CIO Casey Coleman during a Thursday afternoon call with reporters.

Anytime a switch in a critical business platform occurs, other problems are bound to crop up as well, she said. Those include management challenges such as making sure everybody understands the process and the plan, as well as training issues.

Another problem that could pop up is ensuring that all information contained in the current platform is migrated successfully to the cloud, Coleman said.

Nevertheless, "I believe everyone is excited and looking forward to [the] change," Coleman added.

It was also critical that GSA make the switch now, according to Coleman. Current e-mail systems run on some servers that are as old as six years, and GSA has come close to an outage, Coleman said, adding there was an "urgency on [the] sense of timing." The agency plans to fully transition in fiscal year 2011.

The White House this morning announced much-anticipated contracting reforms that propose changing the budget cycle for information technology projects and developing a path to promotion for IT program managers.

The details of the plan -- announced by Office of Management and Budget Chief Performance Officer Jeff Zients -- are explained in a Nextgov column by Pratap Chatterjee, who is a visiting fellow at the Center for American Progress, a progressive think tank with close ties to the Obama administration.

We'll have more information and perspective on Nextgov later today.