Department Of Defense SharePoint Architecture Guide (DSAG) Part 12 Understanding NetOps Agility

There are business rules and principles that have to be followed. They are in place to make sure help with reducing the complexity of the set up. They also work to help reduce the overall cost. Yet you have a system that is very reliable and that can accommodate future changes that need to be implemented into the GIG technical direction.

NetOps Agility NetOps offers a vision for changing the existing capabilities into a multiplier. It offers a way for the Department of Defense to be able to use the power of the GIG. The mission is to offer a unified GIG that is:

Oriented for the mission The information has to be processed in a way that will always support the mission.
User friendly The users need to be able to access the necessary information from anywhere. The GIG should offer this quickly even if the needs of the user happen to be unanticipated.

Global access The mission needs to offer plenty of agility regardless of the user being local or globally positioned.

The GIG NetOps has to be delivered to the organization in a way that varies based on function. It also depends on the type of information to be accessed. The independent management systems of them rarely share information about the status of the managing domain.

The Joint NetOps Concept of Operations allows the Department of Defense to improve the way in which the GIG operated as well as how to secure it. The NetOps is very effective when it comes to the role for net centric operations to be completed. The major changes that have to be addressed include:

Awareness of the information available to commanders.

GIG command and control that can offer quick decision making.

Policies for operating the NetOps have to be clear.

The electromagnetic spectrum of the NetOps needs to be addressed.

The metrics should measure the health and mission readiness of the GIG.

The development of the capabilities needs to have a central governing location
Coordinating the independent NetOps and field activities.

The challenges offer improvement for the operations of the defenses within the GIG. This is completely supported with the ongoing efforts of the mission. There is also a multi partner environment in place.

The NetOps has an environment that allows for the organizational and geographic boundaries to be put in place. For this to work though the Department has to embrace a new method of thinking. They also have to accept new processes which means some new polices. To help with this process the NetOps agility has several goals:

Enable trusted information for the enterprise the premise is for NetOps to be seamless and for the information to flow from one end to the other of the enterprise. This is all in response to what the needs of the user happens to be with the GIG resources in place and allocated parallel with the mission requirements.

To achieve this goal there are two things that have to be considered. First, the NetOps data must be visible and it needs to be accessible for all of the authorized users. Second, the NetOps needs to be understood and then shared for that information to cover all of the missions of the Department of Defense.

Command & Control of the GIG is united The Department of Defense will have a strong dependence on the GIG. This means that it has be able to deliver a variety of commands and controls to all levels of those responsible for making decisions. It is crucial that the Department of Defense is able to take the NetOps and increase the speed of it. At the same time they can take the policy based structure of the GIG domains to coordinate them.

Evolution of the NetOps Time phasing will have to define and develop the net centric portfolio. The policies will help with the overall structure and implementing of plans for a very effective transformation in the beginning as well as additional needs emerge.

There are several rules and principles that need to be established for the foundation of the NetOps to work for the department. These guidelines are very important so it is vital that all of them are implemented successfully for the Department of Defense IT investment to be one that will offer the best benefits.

The Department of Defense needs to operate and defense the GIG as an end to end information resource. They need to create a structure that offers centralized directions so that unanticipated needs can be addressed. This includes but isn’t limited to the possibility of cyber attacks.

The function of the enterprise needs to be integrated across the many management domains. This will allow for the GIG NetOps functions to be operational at different levels. They include operations, tactics, and strategies. The program has to address training and leadership materials.

The application of the GIG program will require the services to offer automation in many areas. At the same time though it has to account for an adjustment to be made so that the resources are fully allocated based on such configurations.

The vision of shared NetOps is one that calls for shared awareness to be in place. All of the applications should be visible and accessible. This allows for the various authorized users to be able to understand all of it. The GIG resources need to have an infrastructure for computing and communication that will be centralized.

Both performance and security are key issues that have to be addressed. The information system has to make it possible for situational awareness and the management of performance to be possible. The NetOps is allows to make the health and readiness of the Department of Defense the opportunity for the services and applications to be supported by the missions of the department.

Next >> Department Of Defense SharePoint Architecture Guide (DSAG) Part 13 Understanding How DIEA Will Evolve

Share

Department Of Defense SharePoint Architecture Guide (DSAG) Part 2 – Accountability, EL Scope, And DIEA Customers

It is up to the Secretary of Defense to determine the holisitic strategy that will be followed. Obviously this is not in an under-branch organization, however ultimate directives do follow a trickle down effect. They set the stage for the management and overseeing of the integration for all of the components of the DoD. Keep in mind that each of the components will have their own framework that they adhere to. They have their own ways of doing work and for carrying out tasks that they have been assigned to.

The fact that there will be many times when they have to be part of joint operations though across different components is central. The objective is to make sure that information is capable to flow like it should across the complete enterprise. It won’t get held up based on the processing for any of the specific components that are involved.

The process is one that is effectively integrated due to the tiered levels of accountability that are within it. There is a leveraging system in place too that determines the services as well as the decision making abilities of the other tiers. It all comes down to the title authority that is used for the functioning.

Each tier involved is able to tender governing power over specific areas. There is a way to preserve consistency that way too through the different tiers from lower to higher. The Department of Defense allows for a solid understanding of all the tiers involved. The rules and constraints that are in place allows for a specific mission to be carried out in regards to the different program levels. The solution is one that allows the higher tiers to control the rules and constraints that all with be under the umbrella of.

The DoD has many reasons for the enterprise level architectures that are in place. This allows the functions and capabilities of the system to be created. This gives those that are responsible for guiding and for decision making to have a way to communicate that information. The scope of all of this is to offer information in the following areas:

What has to be done there is a list of principles and rules that are in common. In order for all to reach those common goals then everyone has to conform to what is being set to follow.

How to do it The right information about how to reach those goals needs to be in place. When that context is arranged with the right practices to follow and the principles to conform to it will be easier for that end result to occur.

When will it happen There is a plan of action implemented that allows for the transition to take place. It will occur with ease so that there isn’t a huge change overnight. Along the way that plan of action has various checkpoints so that everything can be evaluated for being on track. There also needs to be the right resources in place so that various strategies can be mapped out.

It is significant to understand that the DoD enterprise level architecture isn’t’ going to provide a way for implementing or detailing individual systems or possible solutions. Therefore human managers will still be needed on the IT end of things. This shouldn’t be viewed as a replacement for them.

Even so, the ability is there for those managers to provide necessary information to all of those that are part of the overall enterprise. They can make the decisions they need to and then also offer those solutions so that everyone is well aware of what will be implemented based on them.

There are three distinct types of customers that the DIEA 1.0 is geared for. The first is compiled of several types including Investment Review Boards, IT investors, and Capability Portfolio Investors. They will be able to use it for investment values and for identifying various business solutions that can be implemented.

That information will allow them to determine if the capabilities from the service of the enterprises should be used solely. The other option is for them to be delivered with the component specific services.

The second group of customers are the IT architects that have various capability portfolios in Federal agencies. They will have the ability to use the architectures to help them get touch points and boundaries aligned among them. They can also use it to take care of various wholes found in their Federation guidelines and requirements.

The last group of customers is the Department of Defense and Component Program Executive Officers. They are going to have principles designed to help with each of the programs. The idea is for them to be filtered so that the right laws that apply to them can be regulated and enforced. This is also true for the different policies, regulations, and even the framework to consider. It applies both to the internal and to the external aspects of the programs.

With an enterprise architecture, there is as vision about what will be in the future. This is used to motivate and to influence what will occur in the future. The systems that will be designed and used have to be a goal that includes them not affecting what is already in place with these systems. That way they don’t have to spend large amounts of money from the budget for overhauling. They can simply upgrade when it is necessary to do so.

Money can be allocated though to modernize new enterprises if it is deemed that there is a need for it. The DIEA guides for these types of solutions make the information easy to access. There are decisions made about how will be able to access various forms of information with in the system. This is all determined as part of the leadership and command roles within the Department of Defense.

Next >> Department Of Defense SharePoint Architecture Guide (DSAG) Part 3 Global Principles, Rules and Priorities

Share