OASIS Symptoms Automation Framework (SAF) TC

TC Page     Send a comment to this TC

Defining a catalog-based, knowledge framework that enables problem remediation and optimization of operational and business characteristics of complex systems


The Technical Committee was closed by TC Administration on 03 May 2021 and is no longer active. Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.

Table of Contents


The members of OASIS approved Symptoms Automation Framework (SAF) Version 1.0 as an OASIS Standard on 21 January 2014. See the announcement for details.

Participation in the OASIS Symptoms Automation Framework (SAF) Technical Committee is open to all interested parties, including:

  • Architects interested in enterprise management, autonomic computing, or cloud computing
  • Symptoms and protocol catalog implementers
  • Business analysts interested in the automatic resolution or optimization of business processes and environments

Contact join@oasis-open.org for more information on joining the TC.


Human experts in specific IT infrastructure and business domains possess substantial knowledge about prevention, remediation, and optimization of systems. However, there is a significant challenge in capturing, combining, and leveraging this siloed knowledge across domains.

SAF is a catalog-based XML collaborative knowledge framework that is designed to address these challenges by automating appropriate responses to changing business conditions and integrating contributions from diverse domains to provide competitive advantage. SAF has applicability in IT and business including cloud computing, service management, governance, security, energy, eGov, financial, emergency management, healthcare, and communications.

Cloud computing, in particular, exacerbates the separation between consumer-based business requirements and provider-supplied IT responses. SAF facilitates knowledge sharing across these domains, allowing consumer and provider to work cooperatively together to ensure adequate capacity, maximize quality of service, and reduce cost. The SAF technical committee considers cloud computing to be an area where the value of existing and developing standards could be significantly enhanced using SAF.

For more information on SAF, see the TC Charter, the FAQ, and the (working) Symptoms Automation Framework Documents.


No subcommittees have been formed for this TC.

TC Liaisons

No TC Liaisons have been announced for this TC.

Technical Work Produced by the Committee

Symptoms Automation Framework (SAF) Version 1.0 OASIS Standard approved by the members of OASIS on 21 January 2014.

Use Case (working draft): Automation of Increased Provisioning Precipitated by Consumer Business Conditions. Cloud consumer collaborates with the Cloud provider to map the consumer business level requirements to provider low level technical operations. For example, an increase in sales for the Cloud consumer has to be translated to a 20% more capacity, which in turn has to be mapped to concrete resource provisioning as only the Cloud provider knows how to do it

Unmarked documents or documents marked as Working Drafts do not necessarily reflect the views of OASIS or the OASIS SAF TC. Documents marked as Committee Drafts do not necessarily reflect the views of OASIS.

Expository Work Produced by the Committee

An FAQ is available.

External Resources

No external resources for SAF exist yet

Mailing Lists and Comments

SAF: the list used by TC members to conduct Committee work. TC membership is required to post. TC members are automatically subscribed; the public may view archives.

SAF-comment: a public mail list for providing input to the OASIS SAF TC members. Send a comment or view archives.

Additional Information

Please note that unmarked documents or documents marked as Working Drafts do not necessarily reflect the views of OASIS or the OASIS SAF TC. Documents marked as Committee Drafts do not necessarily reflect the views of OASIS.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.