Deployments that Hide or Split Aerie Activity Planning and Sequence Development (Phoenix) Capabilities

[ewferg]

Checked for duplicates

Yes - I've already checked

Alternatives considered

No - I haven't considered

Related problems

Currently, Aerie activity planning and sequence development capabilities are tied together. There is no way to just deploy the sequence development capabilities without bringing along all of the activity planning functionality and vice versa. As an example, if a mission wants to pick up new sequence development capabilities, but has a stable activity planning mission model, this is not really possible because bringing in new sequence development capabilities also means bringing in updates to the activity planning functionality, which could include updates that require mission model tweaks.

Moreover, there are missions that want to pick up Aerie for only its activity planning or sequence development capabilities. Right now, missions have no way to hide functionality within Aerie that they do not plan to use, which adds some mental tax to users as they have to learn to ignore all views that are not applicable to their mission.

Describe the feature request

Have a way to configure the deployment of Aerie to only deploy (or at least hide) either the activity planning capabilities or the sequence development environment (SDE) capabilities. Some potential questions related to this issue include:

• If a customer wants both capabilities deployed, but still wants control to upgrade only one capability at a time, what does that look like?
• When deploying either activity planning or SDE capabilities, is the UI simply hiding backend capabilities that still exist or does the deployment not include those backend capabilities at all?
• How are permissions manages in deployments with a single capability deployed?