Where should we go next with EMS Architecture Scenarios? The original document (http://www.ogf.org/documents/GFD.106.pdf) considered scenarios relating to job execution at a known endpoint, an endpoint selected through RSS type mechanisms, and execution requiring post/pre deployment steps. Open Issues (as I see them!): 1. Progress on defining EPS (as part of RSS) has been slow and AFAIK there has not been much progress towards its submission into the document process. There is however a draft from April of the specification and from June of WSDL/XSD files - http://forge.gridforum.org/sf/go/projects.ogsa-rss-wg/docman.root.current_dr.... This may not matter as work has progressed on the content of RSS - namely the information model and the activity in the GLUE-WG. 2. Review of GLUE information model. The BES specification defined some minimal requirements we should ensure that these have been taken on board by the GLUE-WG team - see http://forge.ogf.org/sf/wiki/do/viewPage/projects.glue-wg/wiki/HomePage . Do we need more concrete scenarios from EMS to drive this... or are the GLUE scenarios sufficiently comprehensive? 3. Files (or more generally data?). The scenarios say nothing about file movement. The DMI-WG has progressed since then and has generated some scenarios that could for into a revision of this document. The latest draft (http://forge.gridforum.org/sf/docman/do/listDocuments/projects.ogsa-dmi-wg/d...) and the some use cases (http://forge.gridforum.org/sf/go/doc14666?nav=1 and http://www.ogf.org/OGF19/materials/505/Including%20Data%20in%20Simple%20Job%...) are a starting point. Even some sequence diagrams (see https://forge.gridforum.org/sf/sfmain/do/downloadAttachment/projects.rm-wg/w... and https://forge.gridforum.org/sf/sfmain/do/downloadAttachment/projects.rm-wg/w...) from RM/GLUE discussions that should be reviewed for diffs against the current scenarios. 4. Deployment and Provisioning. Are ACS and CDDLM dead? Should we refactor around work in the Reference Model WG and experience on lightweight deployment experience from UVa and GenesisII (BTW - I'm sure there are other groups who could contribute here). Generally, having scenarios in the current version of the document using specs that are not developing and/or not going to be adopted is a concern to me. There is IMHO a clear benefit in having these sequence diagrams to inform other groups & incorporate their thinking into a single cohesive document. This should be one of our principals for future versions - not to expand into a massive sequence diagram repository but to keep a narrow focus on incremental scenarios in the EMS space. This would be a useful reference for many groups and help to show how the work going on in individual WGs fits together. Steven PS - Many thanks to the those who's documents, emails and thoughts have been collected here!