Back to news

March 7, 2024 | International, Land

Moldova signs defence pact with France amid Russia fears

On the same subject

  • Too many cooks in the DoD: New policy may suppress rapid acquisition

    January 2, 2020 | International, Aerospace, Naval, Land, C4ISR, Security

    Too many cooks in the DoD: New policy may suppress rapid acquisition

    By: Eric Lofgren In 2015, Congress passed middle tier acquisition, or MTA, authorities for rapid prototyping and rapid fielding. Lawmakers expected detailed guidance to follow shortly after. By June 2019, the Government Accountability Office found little clarity on documentation and authority. Congress reacted by threatening to withhold 75 percent of MTA funding in 2020 until the Pentagon released guidance. Dangle the purse strings and compliance follows. The undersecretary for acquisition and sustainment, or USD(A&S), released Department of Defense Instruction 5000.80 on Dec. 30, 2019. The MTA guidance, however, is more likely to pump the brakes on rapid acquisition than propel it forward. Programs designated “middle tier” do not have to follow regulatory processes for requirements and milestone reviews. That can shave years off a program schedule. In return, the prototype must be completed — or system fully fielded — within five years. As of March 2019, there were 35 middle tier programs. The term “middle tier” is perhaps misleading considering nearly half of them exceed the cost thresholds for major weapon systems — roughly $200 million for prototyping or $1 billion for fielding. Many questions remained unanswered until the new policy. How big was a middle tier? What documentation does it require? What is the role of oversight and USD(A&S)? Authority For several years, acquisition authority had been delegated down to the services. While the services only managed 48 percent of major programs in 2014, the figure grew to 90 percent in 2019. DoDI 5000.80 reverses the trend. While the services can approve MTA for non-major programs, only USD(A&S) may approve major programs. Moreover, major programs have far more entrance documentation than non-majors, including approved requirements, an acquisition strategy and a cost estimate. The services may avoid some documentation by disaggregating major systems into multiple MTA programs. For example, two of the Navy's non-major programs are components to Standard Missile-6 Block 1B. The same is true of the Air Force's Airborne Warning and Control System. USD(A&S), however, can still disapprove any MTA program, whether major or non-major. With advisers from all around the Office of the Secretary of Defense, there will be will numerous potential veto points. Each official may extract concessions from MTA programs managed by the services. Even though 31 out of 35 MTA programs are rapid prototyping efforts, the undersecretary for research and engineering, or USD(R&E), has been relegated to a secondary position. All MTA authority rests with USD(A&S). Almost as an affront to USD(R&E), he was given control over a rapid prototyping fund that Congress stopped funding. The outcome reflects a broader weakening of USD(R&E). Congress has reacted negatively to the undersecretary's effort to move fast and reallocate funds to higher value uses. USD(R&E) may lose control of the Missile Defense Agency to USD(A&S). Documentation While MTA exempts programs from traditional requirements and milestone processes, documentation abounds. Each service must create its own requirements process with approval in six months. Joint service requirements are discouraged from using MTA pathways. MTA requirements, however, must still meet the needs determined by four-star generals in the Joint Chiefs of Staff and combatant commands. This may in effect bring the same approvals from the Joint Capabilities Integration and Development System process back into MTA. Many of the DoDI 5000.02 processes also apply. Still required are system analyses, sustainment plans, test strategies, cybersecurity, risk assessments, cost estimates and more. Contractors performing on MTA programs must still report cost data. No exemption was made for earned value management systems. Sidestepping many contract regulations — for example, with other transactions authorities — remains a separate process. Most importantly, Congress requires detailed justification in the budget for every MTA program. That means the services must start justifying MTAs at least two years in advance of funding receipt. Many of today's MTA programs spun off existing, budgeted line items. New programs may find a hard time finding funds. The present situation is reminiscent of the time David Packard attempted rapid acquisition between 1969 and 1971. A couple years later, new layers of bureaucracy descended. Similarly, MTA has built within it the seeds of another slow-paced bureaucratic order. Adm. Hyman Rickover's skepticism to the reforms nearly 50 years ago rings true today. As Rickover wrote to Packard in a memo: “My experience has been that when a directive such as the one you propose is issued, most of the effort goes into the creation of additional management systems and reports and the preparation of large numbers of documents within the Service to ‘prove' that the requirements of the directive are being met in order to justify funds for the Service. “So long as the bureaucracy consists of a large number of people who consider that they are properly performing their function of approval and evaluation by requiring detailed information to be submitted through the bureaucracy, program managers will never be found who can in fact effectively manage their jobs.” https://www.defensenews.com/opinion/commentary/2020/01/02/too-many-cooks-in-the-dod-new-policy-may-suppress-rapid-acquisition/

  • How the Army plans to improve its friendly force tracking

    April 24, 2018 | International, Land, C4ISR

    How the Army plans to improve its friendly force tracking

    By: Mark Pomerleau The Army is upgrading how it tracks friendly forces to increase readiness. During the fiscal 2019 budget roll out in February, Army officials at the Pentagon indicated that the service would be accelerating its Joint Battle Command-Platform, which provides friendly forces awareness information known as blue force tracking, as well as encrypted data and faster satellite network connectivity. The change is intended to solve mounted mission command problems across all formations. The new budget request shows the service is serious about the issue. The Army asked for $431 million for the program in FY2019. That's up from a total of $283 million during the FY2018 budget. Moreover, the Army plans to procure 26,355 systems as opposed to 16,552 from the FY2018 budget. However, officials in the program office were careful to note this was not a “plus-up, so to speak,” but an effort to accelerate the fielding of the tracking systems. C4ISRNET's Mark Pomerleau recently spoke about the program's modernization efforts with Col. Troy Crosby, project manager for Mission Command, alongside Lt. Col. Shane Sims, product manager for JBC-P, assigned to Project Mission Command. C4ISRNET: How should we interpret the FY2019 budget request for this program? COL. TROY CROSBY: It's important to understand that there wasn't necessarily a plus-up. Really what happened is we shifted already approved authorizations to the left. We're just expediting sooner. The Army asked us what we could do to modernize faster ... essentially, we went back to them and said give us the funding and the resources to move a lot of those units to the left because every year the G-3/5/7 comes out with this priority list and we weren't able to get down to that priority list because of funding. That's really what you're seeing with that movement of money from the out years closer in to the left. C4ISRNET: What led to the decision to baseline the program across formations? CROSBY: The Army's looking to standardize their baselines not only on the platforms like JBC-P, but also a similar effort in the command post with software baseline reduction. Moving to the standard baseline on the platform-side helps with training, readiness and the physical constraints as we can depreciate the older versions of FBCB2/BFT [Force XXI Battle Command Brigade and Below/Blue Force Tracking] out of sustainment. C4ISRNET: How does standardization help the Army? CROSBY: Any time you're greatly standardized in a organization the size of the Army, you're going to get easier interoperability down at the tactical level. If Lt. Col. Sims is Sgt. Sims and he is in a unit at Fort Stewart and we were trained on the current systems in the force and then he gets [a permanent change of station] out to Fort Riley, he already has a base of knowledge when he hits the ground on what those systems are because they're the same across the force. So, the training burden for his new units greatly reduced. I think it also helps in readiness as units and soldiers move around the battlespace. The other reason the Army really wants to standardize on JBC-P is, like with all systems in the tactical network, we're always looking to improve cyber posture, and there were multiple improvements in our cyber posturing that the department felt were relevant to try to accelerate so we could get that capability to the entire force as quickly as possible. C4ISRNET: In terms of cyber, what are some modernization efforts you're undertaking to help this platform perform in the more dynamic environments? CROSBY: I think the best way that we can characterize it is looking to ... achieve a cyber posture that allows us to operate both in a counter-insurgency/counterterrorism role and a near-peer adversary role. We're looking to answer both sides of that coin. Yes, current fight, but we're also looking to make sure we're cyber postured for a near-peer. LT. COL. SHANE SIMS: You can probably draw some conclusions from what you know on the commercial side. Imagine having a computer that's over 20 years old — that's where some of our platforms are right now when you're talking about the FBCB2 that was fielded almost two decades ago. C4ISRNET: In terms of your FY19 funding, could it be characterized as investing in standards to help increase readiness and lethality? CROSBY: Very much so. The plus-up kind of touched a couple of areas. On the research and development side, the plus-up helps us in looking at ways to modernize and bring new capability for the blue force tracking network side. We're really looking to expedite that fielding for better cyber posture. C4ISRNET: It sounds like standardization is very important from an Army readiness and lethality perspective. SIMS: When talking JBC-P, there are really three components: the software, the hardware and then the network. Really, what we're doing on a couple fronts [is] we're expediting the fielding to get the hardware out there but that's going to set the conditions for what we're doing in the command post with the infrastructure. That same infrastructure is going to reside on our hardware that's in the platform. The commanders are in environments where they experience something completely different in the command post than you experience on the platforms. You hear repeatedly from the commanders, “Can I have the same type of user experience?” Data's really what we're addressing with the modernization of the command post and the mounted computing environment. That user experience is going to be one and the same for the commander when he or she is in the command post and then when they get in the vehicle. That is really what we're doing with modernization for JBC-P. C4ISRNET: The National Defense Strategy has stressed prioritization on great power competition. How does JBC-P modernization and standardization fit into that strategy? CROSBY: The first one is looking to modernize JBC-P mission command on the move at the platform level. How we continue to modernize and field as fast as we can so that we can maintain both that counter-insurgency/counterterrorism fight and near-peer adversaries is one piece of this. https://www.c4isrnet.com/thought-leadership/2018/04/13/how-the-army-plans-to-improve-its-friendly-force-tracking/

  • L3Harris selected for F-16 electronic warfare protection system

    March 23, 2021 | International, Aerospace

    L3Harris selected for F-16 electronic warfare protection system

    The company's electronic shield will protect the fighters sold to foreign militaries.

All news