The Preliminary Specification Part LXVII (S&AC Part VI)
This post discusses the manner in which authorizations, roles and responsibilities are handled in the Security & Access Control module of the Preliminary Specification. Although we have moved beyond vacation season, we should also discuss, the topic of delegating the authority and responsibility during absences, which is something that can come up at any time.
As background we should recall that each individual would have different access levels and authorizations in terms of access to the People, Ideas & Objects systems. Assuming different roles and responsibilities would impute different access levels to data, information, processes and functionality. On top of that, the Security & Access Control module is the key module for imposing the Military Command & Control Metaphor throughout the People, Ideas & Objects application modules. This structure, particularly in a Joint Operating Committee, would work to weave the multiple producer firms under one chain of command. It also provides an interface to ensure the coverage of all the processes were “manned” to ensure compliance, governance and overall completeness of the process.
Throughout the Preliminary Specification there is the perception of a heightened role for technology in terms of enabling the authorization to conduct operations within the system. That is to say the ability to do things and get things done is through the collaborations with partners and to authorize actions through participation in the processes managed by the systems. This participation dictates that the designation of the roles in the Security & Access Control module “means” more then just data access; but also imputes authority and responsibility to undertake actions on behalf Joint Operating Committees and / or producer firms.
Consideration should be given for whom has authorization to sign an AFE or who can sign for a payment. In a system such as People, Ideas & Objects, will there be the need for any paper? In order for the system to operate it must respect a chain of command or structure that imposes some authority and responsibility to those within the organization who have that authority. I know, (he says sarcastically) we’ll use the Military Command & Control Metaphor (MCCM). As it has been stated here before the MCCM is to be used throughout the Joint Operating Committee and the producer firm for these reasons.
It would also be necessary to be able to assign this authority within the Security & Access Control module during any absence. If someone with authority and responsibility were to be away for whatever reason, or for a short period of time, they should be able to assign their authority to another person to fill that role while they are away. This will ensure that the process isn’t held up during their absence. Delegations of authority have been used for years in larger firms and with a system that imposes the authorizations and responsibilities on specific roles, the ability to temporarily move them down, across or up the chain of command is a necessity to keep the organization functioning.
Lastly we should talk about the interface that helps to identify the missing elements of a process. It would simply show the command structure of the people who are assigned to a Joint Operating Committee or to a process and their related role, authorizations and responsibilities. If someone was to be away then it would show who was taking over their role. It would also help to identify how you could impose the chain of command to fill the void of any vacancies. This would be particularly important if the role or process was needed to be documented for compliance purposes.
For the industry to successfully provide for the consumers energy demands, it’s necessary to build the systems that identify and support the Joint Operating Committee. Building the Preliminary Specification is the focus of People, Ideas & Objects. Producers are encouraged to contact me in order to support our Revenue Model and begin their participation in these communities. Those individuals that are interested in joining People, Ideas & Objects can join me here and begin building the software necessary for the successful and innovative oil and gas industry.
Please note what Google+ provides us is the opportunity to prove that People, Ideas & Objects are committed to developing this community. That this is user developed software, not change that is driven from the top down. Join me on the People, Ideas & Objects Google+ Circle and begin building the community for the development of the Preliminary Specification.