OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

members message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Call for Participation: Computing Ecosystem Supply-Chain TC (CES-TC)

OASIS Members & Interested Parties:

A new OASIS technical committee is being formed.

The Computing Ecosystem Supply-Chain Technical Committee (CES-TC) has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode, and language specified in this proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.

The eligibility requirements for becoming a participant in the TC at the first meeting are:

To be considered a voting member at the first meeting:

Participants may also join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository, and public comments facility, which will be linked from the TC's public home page at [c].

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.


[a] https://www.oasis-open.org/apps/org/workgroup/ces-tc/

[b] See http://www.oasis-open.org/join/Â

[c] http://www.oasis-open.org/committees/ces-tc/



OASIS Computing Ecosystems Supply-Chain Technical Committee (CES-TC) Charter

The charter for this TC is as follows:

Section 1: TC Charter

(1)(a) TC Name

Computing Ecosystem Supply-Chain Technical Committee (CES-TC)

(1)(b) Statement of Purpose

Companies participating in ecosystems require standards to exchange and operationalize data beyond the current integration with existing suppliers and customers (1 up & 1 down). Ecosystem coordination today requires multi-tier (N to N) data relationships to foster better supply chain planning, enhanced visibility, as well as deeper traceability in order to build trusted, secure, and sustainable products and services. The computing ecosystem recognizes that as digital transformation drives more industries to build intelligent systems, standardizing the data exchanged by member companies across such a network will facilitate building resilient capacity, trusted hardware and software, secure systems and sustainable practices to benefit all customers and end users. To that end, we will define data schemas and ontologies, APIs, and smart contracts that allow the data exchange to be achieved on blockchain infrastructure (or other distributed data infrastructure) for use cases valued by the contributing members to the technical committee.

Business BenefitsÂ

Standardization & Productivity: the benefits from using common data assets, APIs for posting and getting data and smart contracts for developing logic that transforms, accesses, aggregates, and entitles information will accrue mainly to companies that use the standard methodologies to share data on a blockchain. Reusing data schemas, APIs & smart contracts reduces the resources required to develop, support, and maintain N to N connections. We believe this could be as much as a 10x improvement over today. It also fosters compatibility for new, innovative solutions to be created for the ecosystem.Â

Decision-making & Capital Allocation: The improvement in visibility of a company's products and services as they contribute to an overall value chain to an end customer or consumer will greatly increase the ability to plan capacity and more effectively employ working capital; will allow better inventory management and support to improve cash flow; and will improve demand signals to be able to call the current quarter and forecast the next more accurately. These benefits are sought after by executive stakeholders at every member company.

Data Foundation for New Revenue Services:Â With the ability to chain data together across companies delivering products and services in a value chain to an end customer; there is an opportunity to leverage the data in new revenue opportunities, such as through trust with certified components from authenticated providers; security to reduce vulnerabilities based upon authenticated providers maintaining software updated and secure; sustainability to improve and attest to the carbon footprint of a system while allowing for an attestable recycling model.Â

(1)(c) Scope

The scope of the work of the CES TC will be developing use cases, standards (data schemas, ontologies) and APIs that enable end-to-end visibility for supply chains. The computing ecosystem components addressed will include hardware, software, systems, platforms, and devices. Contributions will focus on the data schemas and ontologies that define the attributes and entities and a REST API model for putting the data into and getting the data from blockchain or other distributed infrastructure. Work will also focus on smart contracts that perform logic functions on the data on ingress or egress into the blockchain, perform process automation based on data, time or other triggers, and provide entitlement for roles and actors with regard to the data they are eligible to utilize.

(1)(d) Deliverables

The deliverables of the CES TC will include:

  • Committee Notes that define the use cases, value proposition, and technical solutions that form the business case for the prioritized work and identify a roadmap for deliverables.

  • Specifications for data schemas and ontologies that define the attributes and entities to be used along with their description and a blockchain agnostic REST API model for putting the data into and getting the data from blockchain or other distributed infrastructure;Â

  • Smart contract specifications that will perform logic functions on the data on ingress or egress into the blockchain as well as serve as process automation based on data, time, or other triggers and provide entitlements for roles and actors with regard to the data they are eligible to utilize.

(1)(e) IPR Mode

The TC will operate under the terms of the OASIS Non-Assertion IPR mode.

(1)(f) Audience

The profile for the types of contributors to the CES TC include:ÂBusiness Stakeholders responsible for delivery of their respective companyâs products and services; Technical Stakeholders who architect, engineer, and operate company-to-company integrations for supply chain, supply & demand planning, as well as inter-company transformation solutions; Product Management and Technical Subject Matter experts for companies that provide supply chain related information services to companies;Â Data Professionals with interests in developing industry ontologies for inter-company data integration; government representatives interested in computing industry traceability and, Industry Professionals outside of the computing ecosystem which are leading digital transformations or have computing ecosystem products and services in their critical path for delivery to end customers and users.

(1)(g) Language

The primary language used for CES TC meetings and documentation will be


Kelly Cullinane

Technical Community Program StewardÂ




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]