Saturday, December 10, 2022

What are market mechanisms?

 When countries set a limit, or cap, on greenhouse gas emissions, they create something of value: the right to emit. What happens if we apply market principles and rules? The countries or companies that reduce emissions below their cap have something to sell, an unused right to emit, measured in tonnes of CO2 equivalent. Countries and companies that don’t meet their target can buy these one-tonne units to make up the shortfall. This is called emissions trading, or cap and trade. The net affect on the atmosphere is the same, provided measurements are accurate – ie each unit represents a true one-tonne reduction below the cap – and each unit is used only once. This requires clear rules and transparency.


There are a number of benefits to emissions trading. Flexibility is an important one. Companies can better plan their capital investments and climate action in the medium and long term, knowing that in some years they can buy units to help meet their reduction targets. In other years they might have units to sell. This is another benefit of emissions trading – it creates a monetary incentive to reduce emissions.


The Kyoto Protocol created three such “market mechanisms”. The first, emissions trading, as described above, has led to a growing number of emissions markets in countries around the world. Perhaps the best known is the European Union Emissions Trading System (EUETS). The other two market mechanisms are project-based: the Clean Development Mechanism (CDM) and joint implementation (JI).


Projects under CDM and JI don’t earn units by reducing emissions below a set cap. They earn units by reducing emissions below “business-as-usual” – the emissions that would occur without the project. Just like emissions trading, for such mechanisms to work a tonne reduction must represent a real tonne. This means that the calculation of the “business-as-usual” emissions must be based on good information, for example of past emissions, and accurate measurement of the emissions once the project is implemented. The project earns the difference between the two – the business-as-usual emissions and the post-project emissions, again, measured in tonnes of CO2 equivalent.


The units have a name. Under the CDM, the units are called certified emission reductions (CERs). Under JI they’re called emission reduction units (ERUs). Companies under the EUETS could use CERs and JI units to cover a part of their obligations. Likewise, countries with an emission reduction obligation under the Kyoto Protocol could use the units to cover a part of that obligation. The incentive thus created led to registration of more than 8000 projects in 111 developing countries eager to earn saleable CERs – spurring everything from wind power projects, to bus rapid transit schemes, to projects that spread the use of more efficient cook stoves. Likewise, JI incentivized projects, not in developing countries but in countries with an emission reduction commitment under the Kyoto Protocol.


Market and non-market based approaches in the Paris Agreement


Parties negotiating the Paris Climate Change Agreement decided they liked the benefits of countries cooperating to reduce emissions, like they can do under a market-based system. Under the Paris Agreement, cooperation should promote greater ambition (in terms of mitigation of emissions and adaptation to the effects of climate change), it should foster sustainable development and it should encourage broad participation in climate action from the private and public sectors. Parties also recognized that there are other ways to cooperate on climate action, and approaches other than market-based approaches.


Parties expressed all of this in Article 6 of the Paris Agreement, they recognizedthe possibility of cooperative implementation among Parties and agreed to create a new market mechanism, that should be built drawing on the lessons from what went before, such as the CDM and JI. They also agreed to create a framework for non-market approaches mechanism. Just as the details of the new market mechanism need to be hammered out, Parties need to agree on how their new framework of non-market approaches mechanism will function. Until they decide otherwise, the non-market approaches mechanism can be anything and everything, provided it’s not market- based. It’s a broad basket, but based on what Parties have expressed since Paris, the non-market approaches mechanism will focus on cooperation on climate policy, it could include fiscal measures, such as putting a price on carbon or applying taxes to discourage emissions. 

What Is Platform Engineering?

 Platform engineering is an emerging technology approach that can accelerate the delivery of applications and the pace at which they produce business value.

Platform engineering improves developer experience and productivity by providing self-service capabilities with automated infrastructure operations. Platform engineering is trending because of its promise to optimize the developer experience and accelerate product teams’ delivery of customer value.

“Platform engineering emerged in response to the increasing complexity of modern software architectures. Today, non-expert end users are often asked to operate an assembly of complicated arcane services,” says Paul Delory, VP Analyst at Gartner. “To help end users, and reduce friction for the valuable work they do, forward-thinking companies have begun to build operating platforms that sit between the end user and the backing services on which they rely.”

Gartner expects that by 2026, 80% of software engineering organizations will establish platform teams as internal providers of reusable services, components and tools for application delivery. Platform engineering will ultimately solve the central problem of cooperation between software developers and operators.

How platform engineering works?

Platform engineering is an emerging trend intended to modernize enterprise software delivery, particularly for digital transformation. The engineering platform is created and maintained by a dedicated product team, designed to support the needs of software developers and others by providing common, reusable tools and capabilities, and interfacing to complex infrastructure. 

The specific capabilities of an engineering platform depend entirely on the needs of its end users. The platform is a product, built by a dedicated team of experts and offered to customers, who may be developers, data scientists or end users. Platform teams need to understand the needs of their user groups, prioritize the work, and then build a platform that is useful to the target audience.

Initial platform-building efforts often begin with internal developer portals (IDPs), as these are most mature. IDPs provide a curated set of tools, capabilities and processes. They are selected by subject matter experts and packaged for easy consumption by development teams. The platform team, in close consultation with the developers they support, must determine which approach is best for their unique circumstances.

The goal is a frictionless, self-service developer experience that offers the right capabilities to enable developers and others to produce valuable software with as little overhead as possible. The platform should increase developer productivity, along with reducing the cognitive load. The platform should include everything development teams need and present it in whatever manner fits best with the team’s preferred workflow.

The development of a new generation of tools has made platform engineering one of the hottest topics of conversation within the DevOps community. These tools aim to make building and maintaining platforms easier.

What platform engineering is used for?

What the ideal development platform is for one company may be useless to another company. Even within the same company, different development teams may have entirely different needs. 

The overarching goal of the engineering platform is enhancing developer productivity. For the organization, such platforms encourage consistency and efficiency. For the developer, they provide a welcome relief from the management of delivery pipelines and low-level infrastructure.

In short:

Platform engineering implements reusable tools and self-service capabilities with automated infrastructure operations, improving the developer experience and productivity. 

This technology approach utilizes reusable configurable application components and services.

The benefit to users is in standardized tools, components and automated processes.

What Are Industry Cloud Platforms?

 In short:

Industry cloud platforms combine traditional cloud services with tailored, industry-specific functionality to address historically hard-to-tackle vertical challenges. 

Organizations turn to industry cloud platforms to accelerate time to value and benefit from cross-industry innovations.

Industry cloud platforms add value by using innovative supporting technologies and approaches, such as an integrated data fabric, a marketplace with packaged business capabilities and composability tooling, to provide organizations the agility needed to respond to accelerating change.

AI TRiSM

AI trust, risk and security management (AI TRiSM) ensures AI model governance, trustworthiness, fairness, reliability, robustness, efficacy and data protection. This includes solutions and techniques for model interpretability and explainability, AI data protection, model operations and adversarial attack resistance.

Applied observability defined

(a) Observability is the ability to understand what is happening inside a system based on the external data released by that system. Observability requires that actionable data from multiple sources is appropriately connected, optimized and enhanced for context. 

(b) Observable data refers to any variable that can be observed and directly measured. For an enterprise, it often comes from one or more existing IT systems. 

(c) Applied observability is the applied use of observable data in a highly orchestrated and integrated approach across business functions, applications, and infrastructure and operations teams. It enables shortening the time between stakeholder actions and organizational reactions, and so allows proactive planning of business decisions.

Six prerequisites for a strong digital immune system

When building digital immunity, start with a strong vision statement that helps to align the organization and smooth implementation. Then take account of the following six practices and technologies:

(a) Observability enables software and systems to be “seen.” Building observability into applications provides the necessary information to mitigate issues with reliability and resilience and — by observing user behavior — improve UX.

(b) AI-augmented testing enables organizations to make software testing activities increasingly independent from human intervention. It complements and extends conventional test automation and includes fully automated planning, creation, maintenance and analysis of tests. 

(c) Chaos engineering uses experimental testing to uncover vulnerabilities and weaknesses within a complex system. If used in preproduction environments, teams can safely master the practice in a nonintrusive and test-first manner — and then apply the lessons learned to normal operations and production hardening.

(d) Autoremediation focuses on building context-sensitive monitoring capabilities and automated remediation functions directly into an application. It monitors itself and corrects issues automatically when it detects them and returns to a normal working state without requiring the involvement of operations staff. It can also prevent issues by using observability in combination with chaos engineering to remediate a failing UX.

(e) Site reliability engineering (SRE) is a set of engineering principles and practices that focuses on improving CX and retention by leveraging service-level objectives to govern service management. It balances the need for velocity against stability and risk, and reduces the effort of development teams on remediation and tech debt, but allows for more focus on creating a compelling UX.

(f) Software supply chain security addresses the risk of software supply chain attacks. Software bills of materials improve the visibility, transparency, security and integrity of proprietary and open-source code in software supply chains. Strong version-control policies, the use of artifact repositories for trusted content and managing vendor risk throughout the delivery life cycle protect the integrity of internal and external code.