With so many moving targets, you can say, «Why bother» when it comes to releasing an updated DCR or 8100.04 DoDI? The fact is that the DoD still needs IT policies and technical specifications so that the industry clearly understands the IT requirements of our war fighters and sets a clear direction within the DoD so that the future DoDIN does not break down into silos of capabilities that do not interact with each other. Rest assured that these two important documents have not fallen through the cracks, and I expect both to be released before the end of 2021. This publication specifies the technical requirements for the certification of approved products for use in DoD networks to provide end-to-end unified functionality (CPU). This document replaces Amendment 3 to the UCR 2008 Regulations. The UCR is based on the capabilities of Standard Commercial Products (COTS), the standards listed in the DoD`s Register of Information Technology Standards (DISR), and the unique requirements required to support critical DoD requirements. In September 2020, the DoD signed the C3 Modernization Strategy Paper, which included as one of the main objectives the establishment of a public safety communications program and increasing the importance of public safety communication on an equal footing with other DoD C3 capabilities and networks. This new policy prompted the Ministry of Defense to start planning to upgrade the existing 911/E911 features to NG911. This becomes a further elimination of legacy technologies that require the introduction of new IP-based Session Initialion Protocol (SIP) technologies to provide NG911-compliant services within the DoD. This had a significant impact on the DoDI 8100.04 and DCR update, as the NG911`s underlying technologies require location-based routing of SIP 9-1-1 calls over the IP network, which the current DoDIN cannot support. As 2019 drew to a close, the DoD set up an IPv6 Transition Working Group led by the DoD CIO Office.
As early as 2019, the Office of Management and Budget (OMB) issued a policy requirement requiring the entire federal government to begin upgrading its networks to run on IPv6. Ucr has long required «dual-stack» IPv4/IPv6 capabilities from products as a condition of inclusion in the DoDIN APL, but they have never had to «enable» IPv6 functionality. Through some of the first pilots conducted in 2020, it was determined that it will be difficult for the DoD to fully transition to IPv6, and these lessons learned also needed to be captured and documented in the DCR. Working with IPv6, the Department of Defense is also testing Zero Trust Architecture (ZTA) strategies, which will also have a significant impact on future cybersecurity policies and strategy papers that will impact both the updated DoD 8100.04 and the DCR. Finally, the DoD also assigned several 5G wireless «pilot» commands that enabled the early adoption of 5G technologies to support DoD installation communications. Once the results of these early adoption initiatives are available, they should also be included in the future DCR. End-to-end support that guides you through the COVID-19 enrollment process has clearly had a direct impact on the progress of the DoDI 8100.04 update as well as the DCR. With the requirement to allow much of the DoD to telework, and with DEOS not yet operational, the DoD was urged to get a Commercial Virtual Remote (CVR) preliminary function call. This attempted fire provided an office collaboration tool accessible from employees` personal computers on the commercial Internet. While it wasn`t a secure solution from the Department of Defense, it offered a two-factor authentication feature that allowed unclassified work of employees and contractors to be performed from the home office.
Many lessons have been learned from this experience that could be applied to the DEOS program and captured for inclusion in the future DCR. 31. January 2021 – Winchester, Virginia: As we enter a new year, it`s no secret that 2020 brought a whole host of challenges and not all of them were related to COVID-19. Within the Department of Defense, concentrated efforts have been made to update the Unified Capabilities Requirements (UCR) technical specification used by the Joint Interoperability Test Command (JITC) to certify a wide range of products for the DoD Information Network (DoDIN) Approved Product List (APL). Work began in 2016, and here we are in early 2021 and still no updated specifications. What is going on? One thing was the decision to update the DoD Instruction policy document 8100.04 Unified Capabilities. With the name change from UCR to DoDIN Capabilities Requirements (DCR) and with the creation of the Enterprise Collaboration and Productivity Suite (ECAPS) working group at the DoD CIO office, it was decided to update DODI 8100.04 to update the Enterprise End User Services (EUES) policy. ECAPS is divided into three (3) sets of capabilities: 1) Defense Enterprise Office Solution (DEOS); (2) Unclassified telephony and videoconferencing; and (3) Classified telephony and videoconferencing. DEOS was formulated in an acquisition that was requested, assigned, contested and reallocated. The energy consumed to bring the DEOS efforts to a point where they were operational really affected the progress of completing the strategy for Skill Sets 2 and 3, which subsequently delayed the ability to complete the DCR. U.
Department of Defense, Office of the DoD Chief Information Officer, Unified Capabilities Requirements 2013 (UCR 2013) (January 2013) (full text). Design consulting to strengthen your product against DoDIN APL requirements An evaluation of your business and product to identify an effective enrollment path.