kamagra how much to take

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

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>