Skip to end of metadata
Go to start of metadata

This is the home page for the Acumos TSC Community (Product) Committee, as approved for formation by the TSC on 2018 03 27. See Community Committee for the charter of the committee.

The overall goal for this committee is to grow the community of Modelers contributing models and also growing the community of companies running Acumos instances, via  focus on these areas:

  • Release functionality
  • Model Management
  • Catalog growth
  • Policies


The Meetings page provides meeting schedule, agendas, minutes, etc.

Boreas Themes





Model Training Pipeline 
Training, onboarding improvement



Data Pipeline



Model Evaluation and Validation (Test/Harness) 
Model evaluation






Model Security

Security sub committee


Model Deployment
AWS, GCP, Cloud Native, K8S, Partner (openshift, whitebox), GPU



Cloud Native (MS arch)



Portal Architecture 
UX/UI hardening, Public Federation checks, CMS removal, Decouple/Distribute Dev to PTL’s



Standard Logging (platform/models)



Model Life Cycle Management
versioning notification, deletion/revoking, dashboard, composite public



Model Builder
Jupyter, RCloud, RapidMiner, AutoML, Zeppelin

Design studio


Data Management
Data stores, Data Lake access, Data broker, Data Movement, Data catalog



Design Studio/Model Interoperability
ONNX, PFA, etc.



Model Types (New)
Caffe, MXNet, Paddle, PyTorch, etc.

Model On-Boarding


LF DL Projects Integration
Tencent Angel, Baidu EDL, IBM FIDL



Integration with ONAP/Akraino/RIC
5G Use Cases



k8 tools for monitoring, metrics, backups, archival/purging, platform security



Serving Pipeline


Athena Features

Updated list of Athena release features. This list of features was approved by the TSC. High priority is targeted to Athena.


This section will describe the role of the Product committee in the overall Acumos release planning and implementation process. Below is a draft process for new feature planning:
1) The goal of an enhancement is brought before the Product committee in Acumos, and documented in this page (or a subpage)
2) The use cases are discussed and approved by the Product committee and handed off to the Architecture committee for design and implementation planning. 
3) Once the Architecture committee has developed a design/implementation plan, that is shared with the Product committee for confirmation that the plan meets the goals of the use case.
4) The Product committee incorporates the implementation plan into the release plan, assigns the implementation to project teams, and monitors the implementation.
A modification of the above is where a design issue or major bug is first discussed in the Architecture committee and referred to the Product committee once the Architecture committee has generally agreed on a high-level approach to implementing a solution. The Product committee needs to consider the impact (of delaying implementation) vs effort of implementing, in their release planning.



Recording of April 16th 2018 meeting.

Use Case Catalog

This section will provide a use case summary table, and links to specific use case documents/sections as drafted/published. The table columns are intended as:

  • Use Case: Unique name/identifier for this use case. Identifiers are recommended for mapping to test cases etc for coverage tracking.
  • Description: Short description of the use case in typical form (e.g. "as a <type of user>, I need <description of platform capability/experience>, to <description of rationale for the capability>", or something more high-level/abstract, but clearly scoped).
  • Status: drafting, proposed, approved
  • Proposed by: who initiated the use case proposal
  • Lead: contributors/SMEs for the use case

Note: the use cases below draw a distinction between the "Acumos platform" and "Acumos ecosystem", for clarity. The Acumos ecosystem represents a federated collection of Acumos platforms that as a group support the related use case's goals.

Use CaseDescriptionStatusProposed byLead
Model ProvenanceAs a modeler or model user, I need to ensure the provenance of models is preserved by the Acumos ecosystem as  models are published, federated, collaborated on, and republished with enhancements, so that my authorship/copyright is preserved and to ensure that I have clear/correct information on the authorship/copyright of models I might want to contribute to.Proposed
User Profile Tied to OrganizationAs an organization manager, I need to ensure that Acumos users who register when affiliated with my organization are associated in their user profile with that organization, and if they leave the organization their user profile within that organization can be marked as "inactive".Proposed
Distinct Roles for Model Author, Publisher, ManagerAs a user of an Acumos platform, I need to be able to take on various roles for models, including that of Author (author of a new Model or changes to a pre-existing Model), Publisher (user that has published a model to a marketplace, however acquired), or Manager (organization member responsible for managing models created by that organization's users).Proposed
Assignment of Author RoleAs author of a new model or changes to a pre-existing Model, I need to be automatically associated by the Acumos ecosystem in the Author role for that model version and any subsequent versions based upon it.Proposed
Assignment of Publisher RoleAs a user who publishes a model to a marketplace on behalf of myself or my organization, I need to be automatically associated by the Acumos ecosystem in the Publisher role for that Model version.Proposed
Restriction of Publisher RoleAs a user responsible for publishing models on behalf of my organization's model authors, I need the Acumos platform to enable restriction of the Publisher role to authorized users of my organization.Proposed
Assignment of Manager RoleAs a user who manages models on behalf of my organization (either as authored/published by organization users, or as subscribed to by my organization through Acumos federation), I need the ability to be manually associated to the model Manager role by the Acumos platform.Proposed
Notifications to Publishers and ManagersAs users in the role of Publishers and Managers, those users need to receive notifications when relevant events occur in the lifecycle of models for which the user has that role.Proposed
Actionable Error Messages for OnboardingAs a user onboarding a model, I need the Acumos platform to provide accessible, clear, actionable messages about the status of the onboarding process and any errors that occur during it.Proposed

Unpublish ModelAs a user who has published a model that I later decide needs to be removed, I need the ability to remove the model from the Acumos platform and ecosystem.Proposed

Replace Model and Remove Previous VersionAs a user who has published a model that I later decide needs to be replaced and the previous version made no longer available, I need the ability to replace the model and prevent the earlier version from being accessible through the Acumos platform and ecosystem.Proposed

Release Functionality

This section will provide a release plan summary table, and links to specific plan component documents as drafted/published, including

  • Use Case: Unique name/identifier for use cases as defined above
  • Description: Short description of the use case and reference to more detailed description if any (e.g. supporting documents / wiki pages)
  • Implementation: Short description of how the use case is to be implemented, e.g. referencing impacted components as defined by the Architecture Committee
  • Schedule: planned/actual start/end of implementation

Model Management

Catalog growth



Recent space activity

Space contributors



  • No labels