OK, I think I understand it better; the cmp XSD is helping me to get to grips with this. to be MUWS, we appear to need 0. properties as WSRF properties 1. an identity (URI) 2. some XML document declaring our capabilities (how this gets to the system is out of band) 3. an operational status attribute 4. optional: a state derived from the muws state stuff 5. events for changes in (3) and (4) that are derived from the muws events I am thinking that I must describe the state of the systems using the cmp: lifecycle, and have matching events, but declare that transition operations are queued requests -it isnt an error to send >1 state changing operation to a system EPR, when it is in a valid state for that request -it is an error to send a state changing operation to a system EPR when it isnt in a valid state for it -you can send terminate requests to terminated systems. -The OperationalState of a system is "operational" only when in the running state. I'll then purge all MOWS stuff (GetManageabilityReferences &c). is this right? -steve