GovWin
 
 
Agencies Reach 34% of Data Center Consolidation Goals

The 24 agencies participating in the Federal Data Center Consolidation Initiative (FDCCI) have achieved close to 34% of their goals for the number of data center closures. However, despite this progress, it appears that agencies will not hit the 2015 target. On top of that challenge, the Office of Management and Budget (OMB) has yet to assess agency efforts in terms of cost savings.
 
The consolidation initiative set a target to close 1,253 of the 3,133 federal data centers (roughly 40%). planned data center to be closed. By the end of December 2012, agencies had closed over 400 data centers. Close to another 400 are planned to be closed by the end of September 2013, followed by another 150 before the end of 2015. Despite this progress, it looks as though they’ll fall short of the target goals by over 280 closures.

According to testimony delivered to the House Committee on Oversight and Government Reform, OMB has not identified a consistent and repeatable method for measuring agency savings resulting from data center consolidation efforts. While agency data center consolidation will be reported to OMB as part of PortfolioStat reviews, agencies would provide information through an information resources management strategic plan, an enterprise roadmap, and a data collection channel. This shift removes the previous requirement for agencies to submit consolidation plans and it does not call out cost savings goals. PortfolioStat is expected to result in $2.5 billion in savings through 2015 but it’s unclear whether a new savings goal has been established for FDCCI.
 
Agencies were tasked with a goal of achieving $3 billion in savings through data center consolidation by 2015. When agencies reported expected cost savings in their 2011 consolidation plans, the Government Accountability Office (GAO) found that collectively agencies expected to save $2.4 billion by 2015, but they noted that the projections were incomplete and unreliable. At that time, many agencies were still completing inventories and identifying additional targets for closure. Since closing facilities are a major driver for the savings associated with these efforts, it’s likely that the full extent of savings will not be realized until after 2015. As of November 2012, savings were not being tracked but thought to be minimal, due to the upfront investments for new facilities and upgraded systems and reinvestment of savings into ongoing consolidation efforts. Currently, a timeframe has not been established for when tracking cost savings may begin.
 
 
Originally published for Federal Idustry Analysis: Analysts Perspectives Blog. Stay ahead of them competition by discovering more about GovWinIQ. Follow me on twitter @FIAGovWin.

Continuous Monitoring as a Service Award on the Horizon

 Improved cybersecurity was called out as one of three administrative priorities for FY 2014. Agencies have been inching towards cybersecurity targets, and an upcoming award may ease agency pains of implementing continuous monitoring solutions.
 
As described in the 2012 FISMA report, continuous monitoring covers three categories: assets, configuration and vulnerability. According to the report, all CFO Act agencies demonstrated the ability to successfully report data feeds to Cyberscope. While agency implementation of automated continuous monitoring increased in FY 2012, 7 out of 24 civilian agencies did not have monitoring programs in place.
 
 According to the agency capability implementation, scores often appear lopsided. Overall, agency implementation would need a 7% improvement in FY 2013 to meet the implementation target. Perhaps, DHS’s continuous monitoring program will provide the boost lagging agencies have needed.
 
 
 Last year, The Department of Homeland Security’s National Protection and Programs Directorate (NPPD) announced that it’s developing a Continuous Monitoring as a Service (CMaaS) capability. The result of this effort would be an array of sensors that collects data about agency cyber security risks and presents that information in an automated and continually updated dashboard. This display will allow technical workers and managers to improve an agencies’ view of security, to counter recurring threats more effectively, and to support a data-driven approach to agency risk management.

 
As we previous explored, the core capabilities for DHS’s continuous monitoring fell into five areas: hardware asset management, software asset management, vulnerability management, configuration management, and anti-virus. The continuous monitoring program outlined several approaches, including a service-based solution.CMaaS solutions will be based upon NIST standards including a number of guidelines set out in NIST’s 800 series of special publications:
  •  “Guide for Conducting Risk Assessments” (SP 800-30)
  •  “Guide for Applying the Risk Management Framework to Federal Information Systems” (SP 800-37)
  •  “Guide for Managing Information Security Risk” (SP 800-39)
  •  “Recommended Security Controls for Federal Information Systems and Organizations” (SP 800-53)
  • “Guide for Assessing the Security Controls in Federal Information Systems and Organizations”   (SP 800-53A)

 
DHS plans to shoulder the financial responsibility for this continuous monitoring effort because many agencies lack the resources and expertise.  In December 2012, the contracting office released a request for quote (RFQ) that covers both the CMaaS and tools portions of Continuous Diagnostics and Mitigation (CDM). Responses to the RFQ were due in February 2013. Strategic sourcing is expected to be leveraged using DHS funds to implement sensors (where missing), a federal dashboard, and operating services. The General Services Administration (GSA) will be charging a 2 percent fee to agencies using the broad purchase agreement (BPA). Over 40 vendors have expressed interest in the $6 billion opportunity. The performance period is set for five years. Officials have stated that they expect to issue awards before October 2013. Deltek analysts currently estimate the announcement of the awards in June 2013.
 
Updates regarding the CMaaS award can be found on GovWin under Opportunity ID 89183 (log in required).
 
 Originally published for Federal Idustry Analysis: Analysts Perspectives Blog. Stay ahead of them competition by discovering more about GovWinIQ. Follow me on twitter @FIAGovWin.

Lessening the Blow of Sequestration

OMB may have found a way to bring $5 billion of the $85 billion sequestration price tag, back into play.  The recalculations would free up $4 billion from the Pentagon and $1 billion from other agencies such as NASA and DHS.

When Congress moved money around among various accounts in the Continuing Resolution which took effect in March, it restored $5 billion of the sequestration cuts due to accounting rules that govern the different accounts.  According to a quote from a government official in a recent Government Executive article, “Under the law, if [lawmakers] cut those accounts below their post –sequester level, there is a provision that credits back some of the funds.”  A 1985 budget law prescribes that funds be restored to accounts that had been deeply cut via sequestration.

Much of the specific calculations and data behind the restoration of funds is still hush hush.  According to Associated Press article that broke the story, the process is ongoing and public officials they contacted spoke under the guise of anonymity. 

Although much of the dire consequences of sequestration are yet to be felt by most American citizens, public pressure is mounting to decrease the impact of sequestration cuts.   Agency budget officials have been working with Congress to permit the transfer of funds between accounts to lessen the blow of the cuts.  Some agencies have been able to avoid or shorten furloughs due to this process, such as Department of State, Department of Justice, and Department of Homeland Security.  Department of Defense will benefit the most from the new calculations by being able to avoid $4 billion cuts.  

 

OMB Report Charts Growth in Discretionary Spending

The Office of Management and Budget’s (OMB) submitted its reports on discretionary spending cuts to the President and Congress just ahead of the release of the President’s Budget Request. Along with a the review of spending caps, OMB also released a preview of sequestration in the spending plans for fiscal year (FY) 2014, which looks at discretionary spending out to 2023.
 
The Final 2013 Sequestration Report provides estimates of discretionary spending limits for each category in the Balanced Budget and Emergency Deficit Control Act of 1985 (BBEDCA), OMB’s scoring of the enacted 2013 discretionary appropriations bill, and comparisons with estimates from the Congressional Budget Office (CBO) in its Final Sequestration Report for Fiscal Year 2013. Examining appropriations legislations enacted through April 4, 2013, OMB found that the enacted appropriations are within the discretionary spending limits for 2013 and a sequestration of discretionary budget authority is not required. (Note: The assessment by OMB is distinct from the Joint Committee sequestration.) The chart below shows the caps after various re-categorization adjustments.

BBEDCA provides caps for discretionary program spending each year through 2021. Originally, discretionary programs were separated into “security” and “non-security” categories, which are shown above in the funding levels for fiscal years 2012 and 2013.
·          The security category included budget accounts for the Departments of Defense, Homeland Security, Veterans Affairs, the National Nuclear Security Administration (NNSA), the Intelligence Community Management Account, and all accounts in the international affairs budget function.
·          The nonsecurity category covered everything else. After 2013, BBEDCA provided a single category for all discretionary spending.
 
The Budget Control Act (BCA) allowed for revision of the spending caps if the Joint Select Committee on Deficit Reduction proposed legislation to reduce the deficit by $1.2 trillion was not enacted by January 15, 2012. Since legislation was neither proposed nor enacted, the caps were revised in OMB’s Final Sequestration Report of Fiscal Year 2012, which was issued January 18, 2012.
·          The revised security (“defense”) category included only funding for discretionary programs in the national defense budget function: Department of Defense, portions of Department of Energy (including NNSA), and the Federal Bureau of Investigation.
·          The revised nonsecurity (“non-defense”) category covered all other discretionary programs.
·          The discretionary category for 2014 to 2021 was replaced by caps for the defense and non-defense categories. While the budget caps were adjusted to reflect the redefined categories, the overall discretionary spending limits were not changed.
 
The spending caps were changed again, under the American Taxpayer Relief Act of 2012 (ATRA), which reinstated the security and non-security categories for 2013 and reduced the limits by $4 billion, split evenly across the two categories. The limits for defense and non-defense spending were left in place for 2014 to 2021. However, the 2014 levels were lowered by $8 billion, split evenly across the defense and non-defense categories.

The preview report sheds light on several proposed revisions to the spending caps in the President’s Budget. The 2014  Budget includes savings in the mandatory and revenue categories, reducing the discretionary limits, restoring the 2013 sequestration amount, cancelling the 2014 mandatory sequestration order, and increasing the 2014 discretionary levels to those agreed to by Congress in ATRA. The Budget Request also proposes extending the spending caps through 2023. The reductions continue to be split between defense and nondefense categories and are set to take effect in 2017.
 
While discretionary spending at the budget proposal levels shows less growth, the levels are higher overall. According to the FY2014 Budget Proposal figures in OMB’s Sequestration Preview Report for FY 2014, the discretionary funding levels from 2013 to 2012 average $25.9 billion above those in the Final Sequestration Report for FY 2013.

The gap between the two plans for FY 2014 leaps out as a notable difference in the two series. The $97 billion increase from the Final 2013 Sequestration report is comprised of several changes. In the budget proposal, both the discretionary categories see an increase from restoring limits from ATRA. The revised security category receives an additional $54 billion, and the revised nonsecurity category receives $37 billion. While the proposed budget shows less of a drop than the Final Sequestration figures, spending rebounds a year later. If the proposed budget is accepted (though, there's ample reason to doubt that it will be), spending would approach 2013 spending levels in 2019.
 
Originally published for Federal Industry Analysis: Analysts Perspectives Blog. Stay ahead of the competition by discovering more about GovWin IQ. Follow me on twitter @FIAGovWin.

Federal FY 2014 IT Budget to Grow, but there’s Winners and Losers

Steven VanRoekel, U.S. Chief Information Officer at the Office of Management and Budget (OMB) released a presentation yesterday outlining the Obama Administration’s FY 2014 Information Technology priorities and budget numbers. The bottom line is that they are seeking 2% growth in the overall IT budget year-over-year, but individual department budget changes vary widely, meaning that there are “winners” and “losers.”
 
Preceding the public release of his presentation, VanRoekel posted a series of tweets on Twitter under the theme: All you need to know about the IT budget in 10 tweets. You can find the series under #FedITx10, but here they are in the descending order in which they appeared:
 
10-Flat or declining. IT=$82B in the 2014 Budget 2.1% increase from FY12, flat, 0.78% CAGR since 09, negative adjusted for inflation
9-Cut & Reinvest: Now more than ever we must use IT to drive savings to fund innovations that change how govt works
8-Priorities: IT priorities in 2014Budget: Innovate. Deliver. Protect. Evidence
7-Innovate: 2014 Budget enables the Digital Gov Strategy to build a 21st century govt, increase mobile services and Open Data
6-Deliver: PortfolioStat = +$2.5B in savings through IT consolidations and upgrades (over 3yrs)
5-Protect: Over $15B of the IT 2014 Budget is going to enhance our Nation’s cybersecurity
4-Evidence: 2014 Budget NEW evidence-based innovation initiative in my office to strengthen evaluations & drive results, beyond IT
3-Innovate with Less: Since 09 we flattened IT $ while FY01-FY09 IT increased ~2x At that rate, we’d be at +$110B on IT today
2-Dogfood: For geeks (like me!) interested in an Open Data 2014 Budget, key tables in XML here:
1-Progress: 2014 Budget enables strategic IT investment for a 21st century govt, drives innovation & protects our national assets
 
IT Budget “Winners” and “Losers”
 
The budget submission information included in VanRoekel’s presentation contains some top-line budget numbers which allows for some initial analysis. The IT budget summary table in the presentation calculates the amount and percentage change for FY 2014 based on FY 2012 budgets, even though he provides FY 2013 Continuing Resolution (CR) budget estimates that are different. To provide a more detailed perspective I ran the numbers comparing the dollar and percentage change for all scenarios. 
 
The tables below are grouped by the “Winners” and “Losers” based on the percentage change from FY 2012 to FY 2014. The third table provides a comparison between Defense and Civilian segments, along with total federal IT.
 
 
 
 
 
 
Conclusion
 
While we are still waiting for the release of detailed IT budget information from OMB the proposed $1.4 or $1.7 billion increase for FY 2014, depending on which baseline year you use, is sure to surprise many who watch this market. Certainly, a 2% yearly growth rate is anemic compared to the growth rates we have seen over the last decade or so. (OMB reports a 7.09% compound annual growth rate (CAGR) between FY 2001 and FY 2009 and they are projecting a 0.78% CAGR between FY 2009 and FY 2014) Yet, many expected lower growth – if not an outright decline – in the federal IT budget for this coming fiscal year.  

Now the budget is in the hands of Congress, which has historically appropriated more for IT than what the President requests. With fiscal priorities clashing and sequestration impacts now being felt across the market, federal IT could weather the current fiscal storm in relatively good shape.

---
Originally published for Federal Industry Analysis: Analysts Perspectives Blog. Stay ahead of the competition by discovering more about GovWin FIA
. Follow me on Twitter @GovWinSlye.

Highlights of the President’s FY2014 Budget Request

Today President Obama delivered a $3.8 trillion spending plan to Congress which includes a $1.2 trillion request in discretionary funding levels and nearly $82 billion for information technology for FY2014.  The budget focuses on jobs creation, economic growth and to strengthen the American middle class.

The budget proposal also includes $1.8 trillion in additional deficit reduction measures over 10 years to reach a total deficit reduction of $4.3 trillion.   The proposed deficit actions would reduce the deficit to 2.8%of GDP by 2016.

Additionally, the budget proposes $400 billion in cuts to health programs including Medicare.  Savings and cuts would come from negotiating better prescription drug prices, fighting waste and fraud, and requiring the wealthiest seniors to pay more.

The table below shows the FY2013 enacted budget levels and the proposed FY2014 levels.

 

Other budget highlights:

  • Includes $50 billion for upfront infrastructure investments to invest in repairs to highways, bridges, airports, transit systems, and to encourage innovative infrastructure projects 
  • Invests in in education reforms and training with a commitment to early childhood education
  • Simplifies the tax code and raises $580 billion for deficit reduction by limiting tax benefits, but not raising tax rates
  • Creates new “ladders of opportunity” to ensure that hard work leads to a decent living by developing pathways to jobs and partnering with communities to rebuild after the recession 
  • Includes $200 billion in savings from other mandatory programs, such as reductions to farm subsidies and reforms to retirement benefits 
  • Proposes $200 billion in discretionary savings from both defense and non-defense programs 
  • Offers $230 billion in savings from changes in the way the government calculates inflation for annual cost-of-living adjustments for benefits programs

Information Technology

The president’s budget proposes nearly $82 billion in IT funding, a 1.8% increase from the FY 2013 CR and a 2.1% increase over FY 2012 estimated level.

IT-related budget highlights:

  • $575 million in savings is anticipated from DoD Data Center Closures. 
  • $324 million is being cut from the DoD’s Global Hawk UAV program. 
  • $22 million is being cut from Computer and Information Science and Engineering Research Programs at the National Science Foundation; CISE is the organization responsible for promoting R&D on big data.  NSF’s budget takes big hits for its small size, which will affect grant spending on technology R&D.  
  • $81 million is being cut from the DoD’s Precision Tracking and Space System, which is part of Ballistic Missile Defense at the Missile Defense Agency. 
  • $38 million in savings related to the Joint Polar Satellite System is anticipated at the Department of Commerce. 
  • $29 million in savings is anticipated from IRS Business Systems Modernization at the Treasury. 

All told, the president’s budget request includes 215 cuts, consolidations, and savings proposals, which according to the administration, are projected to save more than $25 billion in FY2014.  The budget proposal outlines the administration’s priorities and proposed methods for generating more revenue, cutting costs, and reducing the deficit.  However, it joins competing budget plans in the House and Senate.  Serious Capitol Hill budget negotiations are not likely to take place until this summer.

 

 

 

 

OMB Mandates Shared Services for Financial Systems

On March 25, the Office of Management and Budget (OMB) released a memo directing all executive agencies to use shared service solutions for future modernizations of financial systems. The guidance outlines the evaluation process the Treasury Department will use to assess existing Federal Shared Service Providers (FSSP). It also describes the steps the Treasury’s Office of Financial Innovation and Transformation (FIT) will take to review new agency proposals for aligning with this mandate.
Building on the Federal Information TechnologyShared Services Strategy (as well as OMB’s review of financial systems from June 2010), the memo from federal controller Danny Werfel explains that “the cost, quality and performance of Federal financial systems can be improved by focusing government resources on fewer, more standardized solutions that are implemented and operated by experienced staff.” In addition to streamlining the variety of solutions currently deployed across the government, the use of FSSPs will help to reduce the time it takes to implement systems and to improve data quality. As part of this guidance, OMB is encouraging agencies complete market research to evaluate solutions and complete analysis of alternatives from both FSSPs and commercial SSPs. Werfel suggests taking vendor past performance and advantages of existing partnerships into consideration when assessing solutions.
The guidance makes it clear that agency-specific solutions will be discouraged. Still, there is some room for “rare” exceptions. Agencies would need to demonstrate exceptional circumstances (e.g. unique requirements or adequate scale) through alternatives analysis that establish the agency-specific approach is clearly preferable in terms of best value for the Federal Government. Should an agency be approved for an agency-specific solution, they still need to participate in government-wide benchmarking and governance. 
Moving forward, OMB will work with agencies to explore modular updates for financial system, to target enhancements and to prioritize funding for modernization proposals. OMB will be working with agency Chief Financial Officers (CFOs), Chief Information Officers (CIOs) and FSSPs to identify common standards and requirements. Two offices within OMB, the Office of Federal Financial Management and the Office of Federal Procurement Policy, will work with agencies to align acquisition strategies to promote the Cloud First policy and strategic sourcing goals. Agencies with near-term modernization needs are advised to plan for adopting a shared services approach. In the coming months, OMB will issue new guidance on technology and business requirements for financial systems.
This mandate from OMB comes on the heels of the Government Accountability Office removing management of interagency contracts from its 2013 High Risk List. This list calls attention to agencies and program areas that are particularly vulnerable to fraud, waste, abuse and mismanagement. GAO removed the high risk designation for interagency contract due to improvements in several areas including: progress addressing identified deficiencies, adding management controls, creating a policy framework for new contracts, and taking steps to provide better data.

While agencies aim to improve efficiency and deliver greater return on investments, they are looking increasingly to strategic sourcing and shared services a means of leveraging the government's buying power.  Tracking spending through agency mandated contract vehicles, we tend to end up with piecemeal impression of the impact these acquisition trends are having on the market. As luck would have it, the Office of Federal Procurement Policy (OFPP) has a registry of interagency contracts. However, according to Jack Kelly, Senior Policy Analyst for OFPP, the status has not been recently updated.  The current extent to which agencies are leveraging shared service contract vehicles isn’t entirely clear, but Kelly suggested that the Strategic Sourcing Leadership Council (SSLC) is likely to get engaged in activities to review and update the interagency contract registry. In short, we can expect strategic sourcing and shared services to continue shaping federal spending.

Latest FISMA Report Reveals Federal Cyber Challenges are Mostly Internal

The current season of federal budget uncertainty, exacerbated by sequestration, raises concerns of how federal departments and agencies will allocate funds to implement and improve their information security. As OMB describes in the latest Federal Information Security Management Act (FISMA) report to Congress, agencies continue to be the target of increased attacks. But digging a little deeper reveals that many of the challenges may stem from internal practices rather than external attacks.
 
The latest OMB FY 2012 FISMA report provides OMB’s FY 2012 assessment on what agencies have achieved in FISMA-related information security in the previous fiscal year. Of particular interest is the number of security incidents that are being reported to the US Computer Emergency Readiness Team (US-CERT). (See chart below.) 
 
 
 
  
From FY 2011 to FY 2012 agencies report an increase of 11%, which is more than the 5% increase they reported from 2010 to 2011 but less than the 40% reported from 2009 to 2010. Reported incidents are up 200% since FY 2008. In an earlier blog I mentioned comments by a former CIA CISO who noted that the counting method used by FISMA actually understates the threat levels, so these numbers are more like baselines than actualities.
 
A deeper look into the specific types of security incidents and their frequency reveals that the vast majority of these incidents fall into 5 categories:
 
  • Non Cyber – Non Cyber is used for filing all reports of Personally Identifiable Information (PII) spillages or possible mishandling of PII which involve hard copies or printed material as opposed to digital records.

  • Policy Violation – This subset of Improper Usage is primarily used to categorize incidents of mishandling data in storage or transit, such as digital PII records or procurement sensitive information found unsecured or PII being emailed without proper encryption.

  • Malicious Code – Used for all successful executions or installations of malicious software which are not immediately quarantined and cleaned by preventative measures such as anti-virus tools.

  • Equipment – This subset of Unauthorized Access is used for all incidents involving lost, stolen or confiscated equipment, including mobile devices, laptops, backup disks or removable media.

  • Suspicious Network Activity – This category is primarily utilized for incident reports and notifications created from EINSTEIN and EINSTEIN 2 data analyzed by US-CERT.

These top 5 categories account for 87% of all incidents reported by federal agencies. Factoring out the Non Cyber category, the remaining top 4 make up nearly 60% of all reported federal security incidents. (See chart below.) 

 

 

Delving into the data a bit further shows where these incidents are most widely occurring among the 15 departments spending the most on their IT security, according to their FISMA submissions. (See table below.)

 

Implications

While a data comparison among categories and agencies has its limitations, it does lead us to ask further questions and draw some possible conclusions. The most obvious to me is noticing the clustering of incidents within categories that relate to internal behaviors.

Combining the frequency of Policy Violations, lost or stolen Equipment, and Non-Cyber (non-digital) incidents consisting of the physical spillage or mishandling of PII in paper form drives home that there appears to be much left to do in the area of cybersecurity training for IT users at these departments. If the Malicious Code category accounts for much in the way of code insertion through unsafe user practices then that incident frequency too underscores the ongoing training need. OMB notes in the report that federal agencies spent less than 1% of their IT security budgets in FY 2012 on training. In previous FISMA reports training accounted for roughly 2.5% in FY 2010 and FY 2011, but according to OMB, the DOD portion of the data for those years was incomplete so adjusting for DOD might show that 1% is consistent across all of these years.

The sheer number of departments in the top 15 above that list Policy Violations and/or Equipment incidents in their top 2 or 3 for frequency suggests that some of the greatest information security challenges facing federal agencies are internal – whether through lack of awareness or training or through outright disregard for approved security practices. In a fiscally constrained environment where return on investment for each dollar is scrutinized agencies might actually save money that they would spend on cleaning up security mistakes by users if they could more effectively prevent many of these incidents in the first place.

---
Originally published for Federal Industry Analysis: Analysts Perspectives Blog. Stay ahead of the competition by discovering more about 
GovWin FIA. Follow me on Twitter @GovWinSlye.

Updated FITARA Legislation Strengthens Some Proposed Reforms and Waters Down Others

The updated Federal Information Technology Acquisition Reform Act (FITARA), first proposed by Congressman Darryl Issa (R-CA) in September, now incorporates suggestions and comments from industry which strengthen the role of CIO, but limit requirements for centralized IT purchasing.

By some estimates, the legislation could save taxpayers as much as $20 billion annually by fundamentally reforming the way federal agencies purchase IT.  If passed, the FITARA would be the most significant reform to the IT acquisition landscape since the 2002 E-Government Act and the 1996 Clinger Cohen Act, which created the agency CIO function.  

Below is a brief summary of the updated legislation:

The Act would give more responsibility to agency CIOs by making them presidential appointees or designees, granting them greater budget authority and limiting agencies to one CIO for the whole agency; bureaus, offices, and subordinate agency organizations could not have their own CIO.

The updated bill promotes the use of “fixed price technical competition” or “bid to price” contracts, in which agencies would specify the price they planned to pay for IT products and/or services and contractors would compete to offer the best solution or service at that price.

After backlash from acquisition experts, the legislation was modified to eliminate plans for a government-wide IT Acquisition Center fearing that it might duplication services already provided by GSA.  Instead, the bill now calls for the establishment of the Federal Infrastructure and Common Application Collaboration Center to develop centralized program and technical management expertise to coordinate IT acquisition best practices.  The new Collaboration Center located within OMB, will assist agencies with challenging IT projects and support the CIO Council with TechStat reviews.

Congressman Issa plans to formally introduce the updated legislation soon.  According to NextGov, the legislation was likely discussed at a March 20th House Oversight and Government Reform Committee business meeting. 

Originally published for Federal Industry Analysis: Analysts Perspectives Blog. Stay ahead of the competition by discovering more about GovWin FIA. Follow on twitter @FIAGovWin.

 

 

 

 

House FY ’13 Continuing Resolution Gives DoD and VA Flexibility, Has Select IT Implications

On March 6, the House passed H.R. 933 which would appropriate funding for the Departments of Defense (DoD) and Veterans Affairs (VA) and fund military construction projects (MilCon) for fiscal year (FY) 2013. The bill will also avert a potential government shut-down near the end of March by funding the remaining departments at their FY 2012 levels under a continuing resolution (CR) effective until the end of the fiscal year. How the bill fares in the Senate is yet to be seen.
Passage of appropriations for the DOD and VA would mean that those departments can allocate funds to new programs, which is not permitted under a continuing resolution which essentially funds the previous year’s programs at the same levels and schedules.
Specifics of H.R. 933, the Department of Defense, Military Construction and Veterans Affairs, and Full-Year Continuing Appropriations Act, 2013 include:
  • Total discretionary budget authority of nearly $1.2 trillion, including
  • Full-year appropriations for Defense and Military Construction/Veterans Affairs committees
  • Defense – $518 billion in non-war funding for the DoD, $87 billion for overseas contingency operations (OCO)
  • MilCon/VA – $72 billion in discretionary funding for military construction and the Department of Veterans Affairs, with some shifting of funds away from military construction to support increase in veterans’ programs, which are exempt from sequestration
  • The remaining federal agencies would be funded at fiscal 2012 levels under a continuing resolution covering the remaining 6 months of fiscal 2013
Sequestration 
 
Citing the Office of Management and Budget’s (OMB) March 1st Sequestration report, the Congressional Budget Office (CBO) noted In a letter to House Budget Committee Chairman Paul Ryan that impact of sequestration on the $1.2 trillion appropriations would be a $68 billion reduction, lowering the overall budget authority for FY 2013 to $1.13 trillion. (An additional $17 billion reduction in mandatory spending brings the total sequestered amount to $85 billion.)
 
Agency-specific Provisions – Select Details
Although not comprehensive or complete, a quick review of the text of the bill looking for information technology and related acquisition provisions provides the following agency-specific examples.
Veterans Affairs
 
  • Veterans Benefits Administration – Provides $3.3 billion for information technology, including $1 billion for staff pay, $1.8 billion for operations and maintenance, and $494 million for systems development, modernization, and enhancement. This DME funding is 2-year money available through FY 2014 but requires the VA Secretary or CIO to submit to Congress a certification of the amounts to be obligated for each project. Further, Congress requires approval of any transfers between the three funding sub-accounts or individual project funding increases/decreases of more than $1 million.
  • No more than 25% of any joint DoD-VA integrated electronic health record (iEHR) may be obligated until the DOD–VA Interagency Program Office gets the approval of both Congressional Appropriations Committees on the planned costs, timelines, acquisition, etc.
  • Of the $60.5 billion appropriated for veterans compensation and pension benefits programs no more than $9.2 million “shall be reimbursed to ‘General operating expenses, Veterans Benefits Administration’, ‘Medical support and compliance’, and ‘Information technology systems.’”
  • $115 million for the VA’s the Office of Inspector General, to include information technology costs and for constructing, altering, extending, and improving any of the facilities.
  • Only upon approval of Congress may the VA Secretary transfer funds to/from the VA’s ‘‘Information technology systems’’ account to/from the ‘‘Medical services’’, ‘‘Medical support and compliance’’, ‘‘Medical facilities’’, ‘‘General operating expenses, Veterans Benefits Administration’’, ‘‘General administration’’, and ‘‘National Cemetery Administration’’ accounts.
  • Department of Justice, General Administration, Justice Information Sharing Technology receives $22 million, the National Protection and Programs Directorate, United States Visitor and Immigrant Status Indicator Technology receives $279 million, and the Office of Health Affairs receives $132.5 million, of which $85 million is for the BioWatch program.
 
Defense   
 
  • None of the DoD appropriation can be used for new multiyear procurement contracts for any systems or components if the value of the multiyear contract would exceed $500 million, unless specifically provided in the bill. A cursory review finds these are predominantly weapons systems, with some mention of commercial SatCom for naval vessels.
  • The DoD provisions further stipulate that no multiyear procurement contract can be terminated without 10-day prior notification to the congressional defense committees.
  • Defense Intelligence Agency funds may be used for the design, development, and deployment of General Defense Intelligence Program intelligence communications and intelligence information systems for the Services, the Unified and Specified Commands, and the component commands, unless otherwise stated.
  • $12 million for mitigation of environmental impacts on Indian lands resulting from DoD activities, including training and technical assistance, related administrative support, the gathering of information, documenting of environmental damage, and developing a system for prioritization of mitigation and cost to complete estimates for mitigation.
  • None of the funds in the Act may be used for research, development, test, evaluation, procurement or deployment of nuclear armed interceptors of a missile defense system. 
  • $519 million in multi-year funds for  Cooperative Threat Reduction for the elimination and secure transportation/ storage of nuclear, chemical and other weapons; to prevent the proliferation of weapons, weapons components, and weapon-related technologies, etc.
  • RDT&E New Starts Justification – Funds appropriated under ‘‘Research, Development, Test and Evaluation, Defense-Wide’’ for any new start advanced concept technology demonstration project or joint capability demonstration project may only be obligated 45 days after a report, including a description of the project, the planned acquisition and transition strategy and its estimated annual and total cost, has been provided in writing to the congressional defense committees. (The Secretary of Defense may waive this restriction on a case-by-case basis.)
  • Funds appropriated for research and technology for programs of the Office of the Director of National Intelligence shall remain available until the end of fiscal year 2014.
 
Homeland Security
 
  • Federal Emergency Management Agency receives $35 million for the National Urban Search and Rescue Response System, $22 million shall be for capital improvements at the Mount Weather Emergency Operations Center, and not less than $5 million directed to the modernization of automated systems. 
  • United States Citizenship and Immigration Services (USCIS) receives $112 million for the E-Verify Program. 
  • DHS’s National Protection and Programs Directorate, Infrastructure Protection and Information Security receives $1.1 billion, with $328 million slated for Network Security Deployment and $218 million for Federal Network Security to establish and sustain essential cybersecurity activities, including procurement and operations of continuous monitoring and diagnostics systems and intrusion detection systems for civilian federal computer networks. $213 million (40%) of the combined $546 million is tagged as multi-year funding through FY 2014.
On to the Senate
 
According to recent media reports, the Senate leadership will go along with the House leadership’s decision to set fiscal 2013 spending at levels reflecting the $85 billion in spending cuts through sequestration. Time will tell whether anyone in the Senate will seek to shift money for agencies within the top-line spending number specified by sequestration.  Top agencies on the Senate list to receive similar funding flexibilities include Homeland Security, Justice, State and Transportation, according to reports.
 
If enacted, H.R. 933’s funding of the DoD would put dollars behind the priorities and policies outlined in the FY 2013 National Defense Authorization Act signed in January. For more details on the acquisition and IT implications of the Defense Authorization bill check out our NDAA analysis report.
 
---
Originally published for Federal Industry Analysis: Analysts Perspectives Blog. Stay ahead of the competition by discovering more about GovWin FIAFollow me on Twitter @GovWinSlye.

More Entries