This working group will focus on defining staged requirements for a service catalog and make recommendations as to how to implement such a utility and where it should be hosted. Use cases to inform the service catalog should consider the needs of management (e.g., reporting), operators, and end users.


The following terms apply to all REFEDS Working Groups:

  1. When a working group is agreed, REFEDS Participants will be asked if they wish to participate. Working Groups tend to be small, so consensus can be achieved quickly between participants.
  2. A chair for the group is chosen from the REFEDS Participants.
  3. GÉANT provides facilities for the working group, including meeting support, wiki space, mailing lists and, where appropriate, funding.
  4. An appropriate output from the group is produced. Currently, this is typically a draft white paper or a wiki page.
  5. When the Working Group is in agreement, the chair shares the outputs with the wider REFEDS community with an open period for discussion and comment. This is typically a period of 4 weeks, but may be longer if appropriate.
  6. After this period of time, the REFEDS Steering Committee signs off on the work item. Work is either written up as a formal white paper, left on the wiki but promoted as finished work or occasionally submitted as an Internet Draft.


Heather Flanagan (REFEDS)
Heath Marks (AAF)

Work Items

Implementation & Operation



Problem areas




ACAMP 2016 notes: https://docs.google.com/document/d/1GHerhDYfwlgjN5-pQEryJF0RqOp7R_tWuHiuW5gTdjQ/edit Guide to creating a service catalog: https://www.cherwell.com/products/it-service-management/itil-processes/essential-guide-to-creating-an-it-service-catalog

Product Catalog Management API REST Specification (TMF620) R14.5.1 https://projects.tmforum.org/wiki/display/API/Product+Catalog+Management+API+REST+Specification+%28TMF620%29+R14.5.1