GovWin
 
 
A Look at the Defense Agencies Initiative (DAI) ERP Program

Since Congress first mandated in 1994 that the Department of Defense achieve full auditability of its financial statements, the DoD has engaged in multiple lengthy and costly efforts to implement Enterprise Resource Planning (ERP) Systems. Former Defense Secretary Leon Panetta recently pushed up the date by which the DoD is supposed to be ready for full auditability from FY 2017 to September 2014. Congress then adopted this date into the National Defense Authorization Act (NDAA) for FY 2013, a development that put considerable pressure on the DoD to accelerate the pace of its ERP deployments. The date changes are beneficial for the contracting community because the DoD is unlikely to meet its updated deployment schedule. This suggests that despite the difficult fiscal climate the DoD will continue funding ERP deployments and all of the related work associated with these systems. Funding means contracts and contracts mean business opportunity.
 
One of the many systems being implemented is the Defense Agencies Initiative (DAI). Per the FY 2014 Exhibit 300 for the DAI, the program leverages the Oracle E-Business Suite, version 11i, to modernize Defense agency financial management capabilities in 7 process areas: Procure to Pay, Acquire to Retire, Order to Fulfill, Time & Attendance, Budget to Report, Cost Accounting, and Grants Accounting. The DAI is a holdover project from the Business Transformation Agency that is now under the purview of the Defense Logistics Agency. Work on the various elements of the DAI is directed by the DAI Program Management Office (J623) which resides under the Information Operations (J6) Program Executive Office (J62) at DLA.
 
Background
 
Implementation of the DAI began at the BTA in 2006-2007 with the award of a 5 year contract to Computer Science Corporation (CSC) for the DAI Financial Business Management Solution. Since that initial award DAI implementation efforts have also commenced at the Defense Threat Reduction Agency (DTRA), TRICARE Management Agency (TMA), Defense Technology Security Administration (DTSA), Defense Prisoner of War Missing Personnel Office (DPMO), and Washington Headquarters Service (WHS). Readers should keep in mind that this list is limited to those customers for DAI which could be confirmed. According to the DAI PMO, the Defense Applied Research Project Agency (DARPA) and the Office of Economic Adjustment (OEA), Defense Security Service (DSS), and Defense Media Activity (DMA) also have been prepped for the implementation of DAI.
 
Assuming it is the DoD’s intention to eventually implement DAI across all of the Defense agencies, the following agencies remain potential candidates for DAI deployment, implying that further contract support may be planned.
 
 
Contract Support
 
The following contracts have been identified as related to DAI implementation efforts over the period from FY 2007 to FY 2013. As we can see, a number of these are expiring in FY 2014, 2015, and beyond, providing the potential for follow-on work to be procured, or for new contracts to be competed to perform deployment services and support for the agencies listed above. In addition, the possibility exists that more contractor support for DAI sustainment will be required.
 
 
Historical Spending
 
Historical spending to date on the contracts listed above is as follows. Curiously, there is a considerable discrepancy between the reported base and all options value of these contracts. Likely this is because many of the contracts have remaining option years on them to be exercised. Also, it is possible that spending on many of the contracts remains unreported.
 
 
 
Lastly, the chart below depicts spending on these contracts over the period from FY 2010 to FY 2013. Obligations on these contracts began ramping up in fiscal 2010 to reach a high point in fiscal 2012. Now, in fiscal 2013 it looks as if spending is slowing, probably due to the uncertainty surrounding Sequestration.
 

Conclusions
 
Wrapping up, there is good news and bad news. The bad news for the DoD is that much like the challenges facing Army ERP implementations, the Defense Agencies Initiative will likely struggle to hit full deployment milestones for all of the participating agencies by the September 2014 deadline mandated in the FY 2013 NDAA. The challenge of meeting the deadline becomes even more daunting when potential cuts from Sequestration are taken into account. Should Sequestration be imposed in its current form, funding for many of the DoD’s ERP deployments would undoubtedly take a hit. This does not mean that funding will dry up. It will simply be reduced.
The good news is that in chaos there is opportunity. Given the legislative mandates, the DoD is likely to continue spending on ERP implementation. In FY 2014 the budget for DAI is $99M, out of which $52M (52%) is for development, so funding for DAI this fiscal year is not a problem, assuming an FY 2014 budget is passed. Even if the DoD is forced to operate under another Continuing Resolution at FY 2013 baseline numbers, the funding for DAI will be similar (DAI DME funding in FY 2013 is $63M). In short, DoD ERP implementations like the DAI are likely to remain excellent places in the next few years to seek out business opportunity in trying economic times.

 

 

The Joint Information Environment (JIE) Begins Taking Shape

Over the last two years, the Department of Defense’s effort to create a new Joint Information Environment (JIE) has been in the news a lot. The JIE is mentioned in practically every briefing and interview with DoD officials, but details concerning what the JIE is and where work related to the JIE is being done are hard to come by. In this post I will attempt to provide some substance to the elusive JIE and in the process point out a few areas where I see work happening.

First, what is the JIE? My rudimentary understanding is that the JIE is a common set of technology standards, products, and open architectural approaches that are being implemented to enable system interoperability, enhance security, and make capabilities available to any DoD end-user on any approved device. In short, the JIE is the DoD-wide version of common operating environments/pictures that many federal agencies are currently implementing. In the DoD’s case, work toward the JIE is going on at all levels. The Military Departments are working on it in their own network convergences (e.g., LandWarNet, NMCI/NextGen, and AFNET) and, generally speaking, work at the Defense agency level is being directed by the Defense Information Systems Agency (DISA). Given the size of this topic, this discussion will be limited to outlining some of the work going on at DISA.

DISA’s JIE Strategy

Back in August 2012, DISA released its Global Information Grid (GIG) Convergence Master Plan (GCMP), a strategy document that outlined the agency’s vision for the JIE. GCMP sections 2.1 through 2.3 described the following objectives that DISA is seeking to achieve. Readers please note I’ve changed a little of the language in the DISA document to cut down the amount of text:
Short-term objectives
  1. Provide common user services and platform services through consolidation of infrastructure and existing software licenses.
  2. Provide two private clouds: an unclassified DoD cloud and a classified DoD cloud.
  3. Improve end-user device access by migrating end-user applications to the cloud and migrating end-users to a Virtual Desktop Interface (VDI) environment.
Mid-term objectives
  1. Develop methods, when using commercial cloud service providers, which protect data in transit and at rest, authenticate users, and apply appropriate access controls.
  2. Provide virtual container technologies supporting secure unclassified operating environments on a wider variety of approved end-user devices.
Long-term objectives
  1. Move to a commercial-government hybrid cloud computing environment with DoD retaining the identity provider role.
  2. Improve service interoperability across core, intermediate and tactical edge environments.
Achieving the Short-Term Objectives

Although DISA laid out these objectives in short, mid, and long terms, each stage is interrelated and in some cases DISA appears to be working toward all terms simultaneously. Starting with Short-Term Objective #1, DISA, the Air Force, and the Army awarded the 3 year, $617 million Joint Enterprise License Agreement for Microsoft products last December. Meanwhile, as mentioned above, infrastructure consolidation efforts are ongoing at both the Defense agencies and in the Military Departments. An example of this would be the ongoing effort to integrate the networks of U.S. Africa Command (AFRICOM) and U.S. European Command (EUCOM).

As for the effort to establish the private clouds mentioned as Short-Term Objective #2, this is proceeding at a slower pace. DISA announced just last month that it has developed a process for gathering and assessing mission partner requirements and establishing contract evaluation criteria for an Enterprise Cloud Service Catalog. This suggests that competitions for cloud computing contracts by DISA are likely to be coming in FY 2014. DISA also began laying the groundwork to address Short-Term Objective #3 by awarding a sole source contract in April 2013 to Jackpine Technologies. Under this contract, Jackpine will continue developing combined milCloud and Infrastructure-as-a-Service capabilities resulting in the delivery of an ALVE (Application Lifecycle Virtualization Environment) that will support DISA's Agile, Rapid Development and Deployment Model. The migration of users to a Virtual Desktop Interface (VDI) is the one area of this plan that seems to be moving ahead at the slowest pace. One potential area of progress is the Broad Agency Announcement (BAA) for a Mobile Device Common-Access-Card-Enabled Thin Client solution that DISA released in September 2012. Under this BAA multiple vendors will provide innovative solutions for Common Access Card (CAC)-enabled virtual thin client solutions for managed and unmanaged mobile devices. Presumably, these solutions would also address the requirement for virtual container technologies listed as Mid-Term Objective #2.

Achieving the Mid-Term Objectives

Regarding Mid-Term Objective #1, work to be performed under the mobile device CAC enabled thin client BAA discussed above would address these requirements. Similarly, DISA’s Program Executive Office Mission Assurance and Network Operations recently released a Sources Sought Notice for Community Data Center (CDC) and Sensor Operations. Under this contract, the industry partner will support Centaur Operations within the Community Data Center. Centaur Operations protects and defends the JIE, DoD Enterprise Services, and the GIG through the maintenance of network sensors and tools that gather terabytes of data. Fulfilling this requirement entails designing, building, and maintaining cloud based multi-petabyte parallel distributed files systems and “big data” analytics.

Achieving the Long-Term Objectives

Concerning the longer-term objectives, it appears DISA will fulfill these by building on solutions that it acquires in the short and mid-term. For example, achieving Long-Term Objective #1 is fulfilled by DISA’s efforts to stand up commercial cloud and cloud broker offerings, as well as through the CDC and Sensor Operations acquisition. This leaves Long-Term Objective #2, enabling interoperability across core, intermediate and tactical edge environments. This goal will only be achieved when work being done across the Military Departments’ networks reaches a sufficient level of maturity. In DISA’s case, however, the agency recently took a big step in this direction by awarding a $45 million sole source Blanket Purchasing Agreement to Alliance Technology Group for Large Data Object Storage. The LDOS capability will provide the foundation for an ISR Storage Cloud that enables the sharing and analysis of ISR data across all components of the DoD.

In conclusion, work on the JIE is just getting started. Mobile computing and communication solutions, for example, will also be part of the JIE. However, DISA is expected to award contracts for this requirement soon. Industry can remain confident that more requirements are sure to come.

 

The Outlook for Defense Health Programs in FY 2013-FY 2014

Since February 2013 the media has focused considerable attention on the cancellation of the DoD-VA joint effort to develop a new Integrated Electronic Health Record (iEHR). Focusing on iEHR, however, misses the point that out of the $1.3B proposed FY 2014 development budget for the Military Health System (MHS), the iEHR represents a paltry $64M. Approximately $423M will be spent on medical technology development, advanced concepts development, and medical products support, making those the true areas of business opportunity.

In today’s climate of ongoing federal budget cuts, government contractors can be forgiven for feeling unsettled.  The good news is that the fiscal climate has stabilized somewhat, allowing us to peer ahead for potential business opportunities.  One of the areas attracting vendor interest is in military health.  Both the DoD and Department of Veterans Affairs have made the creation of an Integrated Electronic Health Record (iEHR) a priority.  Therefore, iEHR gets the lion’s share of media attention.  The iEHR initiative is only one aspect of Defense Health Programs (DHP), however, so this post will provide a high-level look at the shape of the DHP budget situation and where vendors might want to focus their business development efforts in the months ahead.

Starting with what remains of FY 2013, funding for the DoD’s Military Health System (MHS) in the 2013 Consolidated Appropriations Act (CAA) provided $32.7 billion, a $16 billion drop from the $48.7 billion called for in the President’s FY 2013 Budget Request.  The funding in the 2013 CAA represented a stunning 38% cut in the MHS’ budget, which received $52.8 billion in fiscal 2012.

Despite these cuts, the 2013 CAA also provided up to $16 billion for contracts for the remaining 5½ months of fiscal 2013.  This includes $522 million for TRICARE/MilHealth procurement until the end of September 2015 and $1.3 billion for TRICARE/MilHealth RDT&E until the end of September 2014.  Digging into the RDT&E number we find the following top 10 priorities outlined in the FY 2014 DoD Budget Request.

As we can see from this list, proposed RDT&E funding for iEHR in fiscal 2014 amounts to $64 million.  This is the issue that everyone is so narrowly focused on.  Meanwhile, there are potentially several larger pools of money that very few people are paying attention to.  For example, the proposed budgets for Medical Technology Development and Medical Products Support/Advanced Concept Development equal approximately $423 million.  Then there is the $43 million budget for basic IT Development not related to TMIP-J.

These budget areas are where opportunity at MHS can be found.  For the last few years $2.4 billion worth of MHS/TRICARE IT and concept development requirements have flowed through the Defense Systems Integration, Design, Development, Operation, and Maintenance Support (D/SIDDOMS) III contracts.  These contracts expire in December 2013 and the MHS has already stated that a follow-on contract vehicle will not be put into place.  This means that contracts for IT and concept development requirements like those listed on the TRICARE Acquisition Forecast will be competed in other ways, providing opportunities for large and small businesses alike. The TMA acquisition forecast for FY 2013 shows $225.4 million in planned procurements, equivalent to 43% of the procurement budget provided through FY 2014.  This suggests that ample procurement dollars have been provided to move ahead with a number of the technology acquisitions that are listed in the forecast.

Lastly, readers will notice that in my focus on the procurement of technology requirements I have not mentioned the $72.5 million budgeted for Medical Program-Wide Activities.  Assuming these activities comprise program management, acquisition support, and other professional services, I believe most of those budget dollars will find their way into task and delivery order contracts competed among holders of the Tricare Evaluation Analysis and Management Support (TEAMS) contracts.  A quick look through the TMA Acquisition Forecast for FY 2013 shows that the projected value of requirements which fall under the TEAMS scope of work equals $201 million out of $225 million.  This leaves $24 million in pure IT requirements available for competition in FY 2013.  Keep in mind that these are just the requirements listed on the TMA acquisition forecast.  More IT efforts are likely in the pipeline.

 

DISA’s ISR Storage Cloud Award Points the Way Ahead for DoD Big Data/Cloud Market

By now everyone has probably read about the recent $45 million sole source award that the Defense Information Systems Agency (DISA) recently made to the Alliance Technology Group for Large Data Object Storage (LDOS).  The Justification and Approval (J&A) notice for the award states that ATG will provide DISA with a scalable storage solution the development of an intelligence, surveillance, reconnaissance (ISR) cloud.  The resources ATG will provide can store hundreds of billions of objects for ISR uses across DoD networks, including “Wide-Area Motion Imagery (WAMI), Standard and High-Definition (HD) Full-Motion Video (FMV), HyperSpectral, Laser Imaging Detection and Ranging (LIDAR), Electro-Optical/Infra-Red (EO/IR) and Synthetic Aperture Radar (SAR) data formats.”  The breadth of data objects to be stored is interesting, as is the fact that DISA is building an ISR cloud, but to me the real importance of this notice lies in what it says about the challenges the DoD faces in trying to handle big data.  Many of these challenges are themes that have appeared in FIA’s blog posts and reports for the last year.

The Strain of Big Data

In a moment of candor, DISA admits in the notice that it “cannot provide the Storage Cloud in its Defense Enterprise Computing Centers (DECCs) due to the physical size of the necessary hardware” required.  Similarly, DISA states that “it does not have the funding … to purchase the required hardware or storage facility.”  DISA also admits in the notice that the new ISR cloud requires increased bandwidth that the agency cannot provide: “Alliance Technology Group is the only contractor with the ability to provide the ISR Cloud Solution with bandwidth at a secure and accessible location.”

Here is the crux of the challenge in three short sentences.  DISA lacks the physical space it needs for a large investment in hardware, it lacks the money to buy the hardware, and it lacks the bandwidth capacity required for ISR data analysis.  In this blog post from October 2012, I made the case that big data is a game changer in the federal IT market, not because of the technologies that will be used to exploit it, but because it acknowledges that the exponentially growing demands of data management have outstripped the limited resources agencies have to handle it.

Visualize if you will all of the data that the DoD accumulates as a large sea.  The level of the water is rising.  Then picture the resources the DoD has to handle that data as a system of dikes used to hold back the sea.  Occasionally the dikes are opened to relieve the pressure.  Nevertheless, the sea level beyond continues to grow.  This is the big data challenge facing the DoD and other federal agencies and the timing could not be worse.  The challenge is rising at precisely the moment when the fiscal resources required are not available.  The challenge of big data is not an “efficiency” problem, it is an overwhelming volume, variety, and complexity problem that requires smart governance and, more importantly, increased investment in infrastructure (commercial or government), analytical capabilities, and trained personnel.

Turning to the Cloud

Having recognized the challenge, DISA is doing the only thing that it can – it is turning to commercial cloud providers to provide the capacity it requires.  In this case the capacity is storage and bandwidth.  The J&A makes clear that DISA anticipates the LDOS ISR Cloud will exceed 1 Exabyte within one year and may exceed 3-4 Exabytes in three to four years.  DISA is being optimistic here.  Neither the DoD nor the Intelligence Community have any intention of limiting the amount of data taken in.  Go to any DoD event on big data and you will hear speakers say that they want to keep every bit and byte because they never know what will be important in the future.

Takeaways

All of this means the following.  Vendors need to offer secure cloud storage solutions, big data analytics (preferably as a cloud service), and related cloud service solutions that meet the DoD’s security requirements.   A recent memo issued by Navy CIO Terry Halvorsen makes this latter point explicitly.  This J&A award to Alliance Technology Group is the tip of the iceberg.  There is a tsunami of contract dollars building to address the DoD’s big data needs.  These contract dollars will flow into modernized and optimized infrastructure – like the new DISN Optical Backbone that DISA intends to build – as well as new database software called out in the FY 2013 National Defense Authorization Act (NDAA), new processing capacity, new storage capacity, and the personnel services required to make all of this go.  The only thing holding back the big data spending tsunami is the fiscal crisis.  This is causing procurement to dribble out in small awards here and there.  However, even with imposed fiscal restraint the path ahead is clear.  The DoD and all federal agencies eventually will be forced by necessity to contract out the big data services they require to cloud providers.  The call has gone out in this DISA J&A.  Can you hear it?

 

 

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.

 

 

 

 

Is Pursuing Work on Army Business Systems Still Worth It?

In February 2013, the Defense Department’s Office of the Inspector General (DODIG) published Report No. DoDIG-2013-045 entitled Army Business Systems Information Technology Strategy Needs Improvement. This report concluded that the Army Office of Business Transformation (OBT) had not developed and implemented a comprehensive strategy for “adequate governance and program management” of its four large Enterprise Resource Planning (ERP) systems: the Global Combat Support System-Army (GCSS-A), General Fund Enterprise Business System (GFEBS), Integrated Personnel and Pay System-Army (IPPS-A), and Logistics Modernization Program (LMP). The estimated life cycle cost of implementing these systems is $10.1 billion and during its investigation the DODIG concluded that the lack of a comprehensive ERP implementation strategy puts the Army at risk of not being able to achieve full financial statement audit readiness by fiscal 2017.
 
The DODIG’s report got me wondering if there might still be business related to Army ERPs that is worth pursuing. On one hand, these are mature systems the development and deployment of which has been underway for a long time. On the other hand, $10 billion is a lot of money and vendors are always searching for more work. As I pondered the worthiness of dedicating scarce bid and proposal dollars to competing for ERP related work, I ran across this chart illustrating the upcoming milestones for each of the four ERP systems:
 
This chart prompted me to go back to last year’s Exhibit 300 Business Cases for the four systems in question. Reading these made me realize there are some potential gaps between the deployment dates and the major contracts in place supporting the systems. For example:
  • GFEBS – Accenture’s GFEBS Support Contract # N0010404AZF12 officially expires in June 2015
  • GCSS-A – Northrop Grumman IT’s, GCSS-A Support Task Order # 1, ITES-2S Contract # W91QUZ07D0005 officially expires in September 2017
  • IPPS-A – Booz Allen Hamilton’s System Integration Services for IPPS-A Task Order # 2Y09, ITES-2S Contract # W91QUZ06D0019 officially expires in June 2013. A follow-on contract for Increment II is being competed now.
  • LMP – CSC’s Wholesale Logistics Modernization Contract # DAAB0700DE252 officially expires in December 2016.
The impending expiration of the Accenture contract for GFEBS support and the current competition of a follow-on for IPPS-A illustrate the potential here. There are of course no guarantees that sustainment contracts for these systems will be competed in the future, but given the size and complexity of these systems I think it is reasonable to expect that follow-ons will be needed. Take LMP as an example. LMP has been deployed, but sustainment services for some posts and installations are still required. In fact, the Telesto Group provides these services for LMP at Anniston Army Depot (#W911KF12C0020).
 
Army program managers also have an ongoing need for Independent Verification and Validation (IV&V) work and program management support for these systems. Program offices across the DoD have been shedding government personnel for years in favor of contract personnel. Continually frozen federal salaries and efforts to shrink government should continue that trend, meaning contract personnel will be hired to step into the breach.
 
Finally, there is an ongoing need for work related to the Army Enterprise Systems Integration Program (AESIP), which converges all of these ERP systems. SAP’s Contract # W91QUZ10F0012 for AESIP Hub Services & Common Operating Environment Convergence just expired in March and recently two awards for AESIP enterprise infrastructure services were made. More are expected.
 
Wrapping up, my point is to illustrate that even though the Army has been implementing its ERPs for decades it is not too late to get in the game. Ten billion dollars is a lot of money and dedicating some of your scarce bid and proposal dollars to compete for it could be well worth the expense.

Surviving Sequestration: The 2nd Half of FY 2013 Could See $300 Billion in Federal Contract Dollars

Increasingly, we hear from companies in the federal marketplace that they struggle to plan and forecast their business prospects. There have been so many delays, false starts, and misaligned priorities that it is sometimes hard to know what opportunities are real and how to position your firm to compete. Now, the impacts of sequestration are beginning to ripple through an already skittish market, adding to the uncertainty. Yet, there are some things to consider that might indicate the contracting potential for the rest of fiscal 2013 and beyond.
Whenever things get unbearably uncertain it is important to have access to good data and information, plus a little creative thinking. It is the only way I know how to keep from making reactionary decisions and to get into proactive mode. So when it comes to thinking about the business prospects for the remainder of fiscal year (FY) 2013 it helps to build some historical context.
To get a sense of the historical pace and relative magnitude of federal spending for the remaining two fiscal quarters of 2013 I looked at the reported quarterly contract obligations across the federal government for the last five years. As I have noted in the past, we have seen a shift in federal spending to later and later in the fiscal year. Spending in Q1 and Q2 (in varying degrees) has shifted to Q3 and Q4. Even with some yearly fluctuation, the trend has been fairly stable. (See chart below.)
These shifts have occurred during a period where we have seen increasing use of continuing resolutions (CR), omnibus appropriations and other delays to funding federal agencies. FY 2013 is not particularly unique in this respect, so it does not seem unreasonable to conclude that the trend will hold this year as well. 
Projected Spending for the Rest of FY 2013 – a Possible Scenario
Now that we have received data for the first two quarters of FY 2013 it becomes possible to perform some rough projections of what might be still on the table for Q3 and Q4. I used FY 2012 data as a basis to make these projections. For FY 2012, adding together Q1 and Q2 departmental obligations and then dividing that sum by the department’s total obligations gave me the relative percentage of total obligations that occurred in Q1 and Q2. (See the table below for the top 20 federal departments and agencies.)
Assuming that agency contracted spending in FY 2013 will be at least 90% of what it was in FY 2012 (sequestration may represent about a 7% cut, so this 10% difference seemed reasonable to me) I followed a similar approach to calculate estimates for Q1 and Q2 percentages and potential remaining obligations for the remainder of FY 2013. 
For example, in the table below the Army had combined FY 2012 Q1 and Q2 obligations of $41.6 billion, which was 38% of their total FY 2012 obligations. The Army had a total of $17.8 billion in contract obligations for Q1 and Q2 of FY 2013, which represents 18% of the projected potential total FY 2013 spend, using my 90% of FY’12 assumption. Applying the percentage left over (i.e. 82%) to my total FY 2013 estimate results in a potential remaining obligation balance for Q3 and Q4 of $79.6 billion for the Army.
 
Granted, performing estimates at this macro level has its limitations and it requires certain broad assumptions for consistency, like a comparable year-over-year obligation rate and that, to some degree, these expenditures are for recurring needs. Some departments have a measure of cyclicality that is underrepresented in a chart covering just a few years. For example, Energy tends to run cyclically between 40% and 68% for Q1 and Q2 every other year or so like a pendulum. Further analysis into the specific contracts is needed to understand why.
Implications
Comparing the 2012 and 2013 percentages reveals that nearly all of the top 20 departments are behind in obligating funds, even with an assumed 10% reduction in spending from FY 2012. While the one-two punch of delayed budgets and sequestration might explain much of this it still remains that these agencies will need to obligate their remaining budgets by the end of the fiscal year. Even (or especially) in this uncertain budgetary environment, agencies will not likely leave money unspent. It is still a “use it or lose it” world out there. So there may likely be some significant pent-up demand that we could see play out in the remaining two quarters.

If this simple analysis holds even close to reality the potential remaining total contract obligations across all federal departments and agencies could be over $300 billion in Q3 and Q4, or 70% of total FY 2013 contract obligations. The second half of fiscal 2013 could potentially see federal contract dollars really flow.

Surviving Sequestration: Is a Flood of Federal Contract Dollars Coming?

At a luncheon I attended recently, Ms. Kathy Cutler, Director and Chief Information Officer at the Defense Logistics Agency (DLA) mentioned that her agency’s sales to DoD customers had been slow in the first half of fiscal 2013 due to the uncertainty surrounding Sequestration.  Ms. Cutler did not say what her expectations are for the remainder of FY 2013, but her comment made me wonder if the trend at DLA is visible in the contract spending at other federal agencies.  To analyze the question I used data from the Federal Procurement Data System (FPDS) showing federal obligations reported as of  March 31, the end of Q2 FY 2013, under the top 10 Product Service Codes (PSCs).  I chose to look at spending under the PSCs because of the visibility it provides into both the rate of federal spending in fiscal 2013 and the kinds of things agencies are buying.  Finally, I took the fiscal 2013 numbers and compared them with data from fiscal 2011 and fiscal 2012 to gauge the rate of spending to date versus recent historical norms.
 
Due to the funding bottleneck we like to call Sequestration, agencies still have a large percentage of their average contracting dollars to spend in the last 6 months of FY 2013.  Add to this the fact that agencies have obligated far fewer contract dollars to date than is typical and the outlook for vendors in the federal market over the next 6 months is rosy.
 
Federal Spending by Top 10 PSCs – Civilian Market Segment
 
 
Taking a look at the Civilian agencies first, the dark blue columns in this chart show the 10 PSCs under which Civilian agencies spent the highest dollar amounts in FYs 2011 and 2012.  The totals for both years have been averaged to provide a single number for comparison.  The light blue columns show the total number of dollars obligated under these PSCs as of March 31.  This analysis yields several insights:
  • FY 2013 dollars obligated under PSC M181 Operation of Government-Owned/Contractor Operated Facilities is equal to 42% of the total average dollars obligated in FYs 2011 and 2012.
  • The lowest percentage of FY 2013 dollars obligated so far is under PSC R499 Other Professional Services.  This is equal to 23.5% of the total average dollars obligated in FYs 2011 and 2012.
  • The highest percentage of FY 2013 dollars obligated so far is under PSC 9660 Precious Metals Primary Forms.  This is equal to 57% of the total average dollars obligated in FYs 2011 and 2012.
  • The percentage of dollars obligated to date under technology PSCs D399 Other ADP & Telecommunications Services, R425 Engineering & Technical Services, and 7030 ADP Software equal 31%, 25%, and 50% respectively, suggesting that spending on technology solutions will remain robust.
Federal Spending by Top 10 PSCs – Defense Market Segment
 
 
Analysis of PSC data over the same timespan at Defense agencies shows similar trends.  Readers should note that the totals in the red columns are underestimates given that the DoD is typically weeks, if not months late in reporting obligated contract dollars.  Also note that some of the Product Service Codes are different from those in the Civilian segment.  A few of the trends worth highlighting include:
  • The DoD has obligated only 15% of the contract dollars that it historically spends under PSC R425 Engineering & Technical Services.
  • Defense agencies have obligated only 13% of the contract dollars that they historically spend under PSC D399 Other ADP & Telecommunications Services.
  • Defense agencies have obligated only 31% of the contract dollars that they historically spend under PSC R499 Other Professional Services.
  • Defense agencies have obligated only 19% of the contract dollars that they historically spend under PSC R706 Logistics Support Services.
Deltek’s Take
 
The media has been saturated with stories of budget cuts and falling federal spending, but the reality is that agencies were hesitant to spend contract dollars during the first half of FY 2013 due to policy uncertainty from Congress and the White House.  Now that agencies have budgets for the remaining six months of FY 2013, we expect agency spending will be significantly higher through the end of September.  Agencies are likely to be very aggressive in trying to obligate as many dollars as possible before the end of the fiscal year.  With the exception of some multi-year appropriations and funding authorized for reprogramming, agencies must expend their funding within the fiscal year or risk losing it. The challenge will be speed.  Overworked contracting shops catching up on stalled procurements and getting a late start on coming acquisitions will struggle, but the fact remains that the federal Government has tens of billions of dollars to spend on vendor-provided goods and services.  Is your company ready to capture some of this business?

Surviving Sequestration: Over $116 Billion in Contracting Opportunities on the Horizon

Despite the emphasis the tighter budgets agencies face under sequestration, major contract opportunities are continuing to move forward. The sum total for 28 upcoming contracts is $116.142 billion. Of course, small businesses won’t be left out in the cold. Of that total, close to some $17 billion will for be small businesses awards.

Contract Status Key

Moving Forward

On Hold

X

Cancelled

Contracting Office Not Commenting

*

Small Business Opportunity

Note: GovWin IQ login is required to view the reports at the Opportunity ID hyperlinks below. 

Agency

Program/Account

Value

Opportunity ID

Status

Air Force

Training System Acquisition Program (TSA III)

$20.9 B

37291

 Air Force

* Engineering Professional Administrative Support Services (EPASS)

$5.0 B

93515

Air Force

*Network-Centric Solutions (NETCENTS II A&AS)

$710 M

48254

Air Force

* Technical Data Support Services (TDSS(e))

$467 M

78427

Air Force

*Follow On Third Party Logistics Services for Support Equipment Commodity Council (3PL SECC)

$288 M

92288

Army

Train Educate and Coach (TEACH)

$8.0 B

69254

Army

Space and Missile Defense Technology Design Development Demonstration and Integration (D3I)

$4.9 B

54159

Army

Strategic Service Solutions (S3)

$4.0 B

86280

Army

Utility Monitoring and Control Systems for Heating Venting and Air Conditioning

(UMCS IV) (HVAC)

$2.5 B

80441

Army

Technical Information Engineering Services (TIES)

$995 M

69356

Army

Energy Savings Performance Contracts (ESPC III)

$1.5 B

78525

Army

*Information Management Communications Services (IMCS 3)

$500 M

72006

Commerce

* Patent Office Support Services (PTOSS IV)

$252 M

32547

Education

Common Services for Borrowers (CSB)

$2.3 B

33550

X

GSA

One Acquisition Solution for Integrated Services (OASIS)

$12.0 B

90928

HHS

Health Marketing Communications Services (HMCS)

$870 M

67831

HHS

Chief Information Officer Commodity Solutions

(CIO-CS)

$10.0 B

47886

NASA

Solutions for Enterprisewide Procurement (SEWP V)

$20.0 B

82396

NASA

Center Maintenance Operations and Engineering (CMOE)

$971 M

53636

NASA

* Marshall Engineering Technicians and Trade Support Services (METTS)

$151 M

53603

State

Passport Support Services (PSP)

$570 M

64443

State

 * Hybrid Information Technology Services for State (HITSS II)

$2.1 B

49544

USAID

Encouraging Global Anticorruption and Good Governance Efforts (ENGAGE)

$750 M

83090

Defense

Global Network Services (GNS)

---

86970

Defense

Defense Systems Technical Area Tasks (DS) (TATs)

$3.0 B

48780

Defense

Homeland Defense and Security Technical Area Tasks (HD TATs)

$900 M

48776

Defense

* Special Operational Equipment Tailored Vendor Logistics Support Program

$5.7 B

70506

DHS

BiowatchGen 3

$3.1 B

68486

Navy

Rapid Response Irregular Warfare (RR/IW)

$5.0 B

67883

Navy

Consolidated Afloat Network and Enterprise Services Full Deployment Production Units (CANES)

$1.0 B

50287

Source: Deltek

Many of Deltek’s opportunity analysts have reported that contracting offices have been unable to comment on the precise impact of sequestration their programs. Contractors will want to monitor changes in requirements and scheduling as the precise impact of sequestration becomes clearer.

In some cases, agency officials indicated that sequestration is not expected to have an immediate impact on their contract. Future delays in funding, however, could be a possibility. Certainly, agencies are prioritizing programs, complying with mandates and, in some cases, restructuring their efforts. Program cancellations, however, seem to be in the minority.

More Entries