Contract Awards by US Department of Defense - February 12, 2019

On the same subject

• 

  November 10, 2024 | International, C4ISR, Security

  CISA Alerts to Active Exploitation of Critical Palo Alto Networks Vulnerability

  CISA alerts to active exploits in Palo Alto, CyberPanel, and Android, urging urgent fixes

• 

  February 4, 2021 | International, Aerospace, Naval, Land, C4ISR, Security

  As mission-capable rates languish, Pentagon should embrace digital engineering

  Ben Kassel and Bruce Kaplan While many Pentagon initiatives face a change of course under new Defense Secretary Lloyd Austin, its digital engineering strategy deserves a push forward. The strategy, issued in 2018 by then-Under Secretary of Defense for Research and Engineering Michael Griffin, aimed to help military services harness modern sustainment methods like additive manufacturing, digital twin and augmented reality. For the Department of Defense, enterprisewide implementation of these techniques would lower costs, increase weapon systems' mission-capable rates and afford flexibility in fleet modernization. But digital engineering requires digital, 3D data — and the DoD doesn't have enough. Modern sustainment practices hinge on the availability of what's known as the model-based definition, 3D models and digitized descriptive information for a system or component. Using computer-aided design programs, engineers can manipulate the data to enable practices like condition-based maintenance, eliminating weapon systems' unnecessary downtime. Digital data can facilitate seamless transit from original equipment manufacturers, or OEM, to procurers and sustainers in the field and at maintenance depots worldwide. However, the technical data for most weapons systems remains elusive to the services and their program management offices, or PMO, or the datasets are available only in 2D documentation, such as blueprints. Meanwhile, readiness suffers. Of 46 weapons systems reviewed by the Government Accountability Office, only three achieved annual mission-capable targets at least five times between 2011 and 2019. More than half (24) failed to meet their goal even once, according to GAO's November 2020 report. The KC-13OJ Super Hercules air refueler and the MV-22B Osprey tiltrotor were among the programs to miss their target all nine years. GAO cited inaccessible technical data as a contributing factor for both programs. Of the Super Hercules, the report says: “The Navy and Marine Corps were unable to obtain the technical data of the aircraft ... the lack of the technical data compromises [their] ability to analyze and resolve sustainment issues.” Similar concerns were raised about the P-8A Poseidon anti-submarine aircraft, saying “technical data needed for maintenance has not been readily available to the Navy.” Dozens of systems, including the F-35 fighter jet, face similar obstacles. Notably, the GAO report referred not to 3D, model-based data but rather legacy incarnations: blueprints and documents that may have been converted “digitally” into PDFs. This is a far cry from the machine-readable formats required to use digital engineering technologies across the enterprise. The GAO cited the production of 170 “structural repair manuals” as a means of narrowing the Osprey's technical data gaps. The labor-intensive replication of physical documents — the PMO projected five years to deliver all of them — is a piecemeal solution, at best. Troublingly, modern sustainment methods seem beyond the reasonable expectation of not just PMOs but even forward-looking organizations like the GAO. To foster its DoD-wide implementation, the digital engineering strategy needs reinforcement, which could take the following forms: Champion the availability of model-based technical data in policy. Modern sustainment requires a shift from decadesold practices. Paper data that supports secondhand manuals and haphazard 2D-to-3D conversion should no longer be the norm. Services cannot lead this transition on their own, however. Federal guidance on the acquisition, creation, use and management of authentic, model-based technical data would jump-start the movement toward digital sustainment. Educate PMOs to acquire technical data rights strategically. Policy must be partnered by the right mindset. One reason PMOs don't have technical data is that sometimes they never asked for it. An afterthought at the time of procurement, technical data is often overlooked until maintenance is needed. Then it's too late — or too expensive — to acquire the needed rights. Leadership can encourage PMOs to identify potential sustainment solutions — and the technical data rights needed to execute them — at the time of acquisition. Assert the government's rights to model-based technical data. A sea change in sustainment depends on building unprecedented trust between OEMs and PMOs. OEMs understandably need to protect intellectual property, but their grip on model-based technical data must loosen for digital sustainment to flourish at scale. This can be accomplished without OEMs surrendering their competitive advantage. In many cases, OEMs need not transfer custody of the data itself for sustainment activities. Limited-rights agreements and trusted third-party arrangements can be tailored to enable data availability only when needed or to execute specific solutions. Giving OEMs confidence in these approaches will entail extensive dialogue and commitment by DoD leaders. Given the GAO's assessment, seeking a breakthrough is worth the attempt. Operationalizing the DoD strategy requires work in other areas as well, particularly in removing intra- and inter-organizational stovepipes, and securing the data's transmission and storage. But the first step toward a model-based sustainment enterprise is ensuring the availability of modern technical data. This need will only grow more crucial. Today's sustainment practices too closely resemble those of 30 years ago, not what they should be 30 years from now. We're already playing catch up. It's time to view sustainment with 3D glasses. Ben Kassel is a senior consultant at LMI. He previously worked with the U.S. government on defining and exchanging technical data used for naval architecture, marine and mechanical engineering, and manufacturing. Bruce Kaplan is a fellow at LMI. He previously served as technical director of logistics for research and development at the Defense Logistics Agency. https://www.c4isrnet.com/opinion/2021/02/03/as-mission-capable-rates-languish-pentagon-should-embrace-digital-engineering/

• 

  December 2, 2020 | International, C4ISR

  5 questions with the deputy director of DISA’s contracting arm

  WASHINGTON — Mass telework brought on by the coronavirus pandemic has made 2020 a busy year for the Defense Information Systems Agency. Throughout the year, the Pentagon's top IT organization has had a hand in the department's Commercial Virtual Remote Environment, which provides collaboration tools for more than 1 million users. DISA has also helped set up IT capabilities for the Navy's two hospital ships as they docked in New York City and Los Angeles to assist with the COVID-19 response. As a result, it has also been a busy year for Debra Daniels, DISA's vice procurement services executive and deputy director of the Defense Information Technology Contracting Organization. Daniels started at DISA in March, right as workers were being sent home. She joined from the Small Business Administration after about 30 years with the Army and now helps oversee a $17 billion portfolio at DISA. C4ISRNET interviewed Daniels about her new position, the unexpected tool she uses to communicate and meeting small business goals. This interview has been edited for length and clarity. What is it like to take over a massive IT portfolio during a pandemic? It makes you think differently and do things differently. It definitely increases communication as DISA provides IT and cybersecurity support. One of the most basic things that I use to make sure to communicate and get on board is the telephone. It works well on picking up and introducing yourself to not only the workforce but the mission partners themselves, stakeholders, small business, in order to do the job. It just makes you reach out more. But I'm going to tell you: DISA has all of the tools in place that allow us to stay in and keep connected so far. DISA never shut down during the pandemic. We just moved from a federal workspace to our own home workspaces and kept going. And what I can say about the contracting force is they never lost momentum, they never lost focus on the priorities at all in doing that. How have your first six months gone? As our contracting operations moved to a home space, it never shut down, never closed, it never lost a beat. I would say probably the momentum increased with the contracting force on just what they were doing in reaching out, making sure that the war fighter had the capability. I'm proud of the fact that, again, we definitely met or exceeded our small business goals. [Specifically], there's about five new records that were [recently] set that continue to build the small business industrial base. This fiscal year, we did $7.6 billion in obligations, which was about a billion dollars more than they did in FY19, I would say just with increasing requirements in the need for the IT and cyber solutions across the Department of Defense but also probably related to some of the pandemic-related urgent and emerging requirements that we provided in that. This is a very difficult time for small business. What should small businesses expect when interacting with your office? What I would want small businesses to know is they're definitely vital to us meeting our goals and our demands and capabilities for the war fighter. And they help us meet those demands. More often, as you know, we get great support — even greater support from them. We could not do it without them. So for industry I would like to say they always want to know how can they participate in the request for information. I would definitely say to continue to reach out, but I would ask them [to] definitely do [your] homework [related to] whatever product or solution they're seeking to provide to make sure that it fits within DISA's capability and its needs. We also partner right now in contracting; definitely a key member at the table at the beginning of acquisition planning is our Office of Small Business Programs here in DISA. Definitely reach out to them, I would say, particularly if [you] want to partner with us to be invited to one of the DISA one-on-one small business orientation offerings that says how you can partner with us. I'll also say that as we get ready in this season to prepare for the DISA Forecast to Industry virtual conference, we will give our industry partners, particularly to include small business, our forecasts. I would say if you want to, you can probably see on the DISA website the forecast from fiscal 2019, and we actually updated that forecast of offerings for the upcoming years. We posted that earlier this summer. So you get an indication of what we're looking for. I would also say a biggie for industry to participate with us is answer requests for information and attend the industry days so you can definitely learn about DISA's mission and what it's seeking, particularly war fighter-specific [needs] and the capability we're looking for. What do small businesses need to know about the cybersecurity requirements at DISA? That is one of the main focuses of DISA as the premier IT support agency and [a trusted provider that] connects and protects the war fighter in cyberspace. So cybersecurity is very important to us, and also should be important to our industry and our small business partners. I think they want to protect their intellectual property and capital just as much as we do. So if you're wanting to work with DISA and the DoD, be accountable also for cybersecurity throughout the life cycle of the capability you're providing. What is DISA doing in relation to the new Cybersecurity Maturity Model Certification — the new cybersecurity audit standards? As we're tracking right now, we do have new requirements that are coming out [because of] the Cybersecurity Maturity Model Certification in the DoD. So as that starts in its implementation process, the Procurement Services Directorate is definitely working to understand these new interim rules — and following [those rules] so we can implement that cybersecurity process once we have the application and accreditation requirements. So we definitely know it will impact all of our industry partners. It will not impact or affect our cybersecurity posture. So if you're going to work with us, cybersecurity is definitely a key. There's a perception that we want to prioritize speed of delivery in deployment over cybersecurity. No. In DISA, in the department — again, I can't harp on [enough] — cybersecurity is one of our utmost priorities, and that is something that we will not diminish or lower the standard on. So it's important that while we deliver with speed and relevance to meet the needs, we're also maintaining our cybersecurity. https://www.c4isrnet.com/show-reporter/disa-forecast-industry/2020/12/01/5-questions-with-the-deputy-director-of-disas-contracting-arm