Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!



 

Home > Tech Writers Hub > Knowledge Services Sandbox > Aria Media Publishing Suite > Aria Media and Publishing Suite (AMPS) - Overview - Version 2

Aria Media and Publishing Suite (AMPS) - Overview - Version 2

This article applies to:Aria Crescendo

Overview

The Aria Media and Publishing Suite (AMPS) is a set of components that are specifically designed for use with publishing and media companies. The suite complements Aria Core standard functionality with extensions that are required by media and publishing companies.  

AMPS is developed and maintained in Aria Workflow. The figure below provides a high-level view of the various service components that comprise the AMPS platform.   

Aria Media and Publishing Suite - High-Level Architecture

AMPS High-Level Architecture.jpg

 

Note: For AMPS to work as designed, several product fields and account fields must be created for products (plans, services, usage-types, non-subscription offerings) and for accounts (customers). See "Aria Media and Publishing Suite (AMPS) - Aria Core Configuration".

AMPS Core Functionality

As shown in the above figure, the AMPS suite consists of the following components. Click on the highlighted links for more information.

  • Access Management – this component provides functionality to manage the distribution of access rights for customer subscribing to digital media. When ever a subscriber changes their set of subscriptions (additions, cancellations, etc.) the details are transferred to the access control system in use. This system then provides the necessary access to newspapers, articles, etc. Integration with some access control systems are provided from the start, but new integrations can be added as required.
  • Account Management – this component is responsible for managing the customer account and initial subscription as well as the billing points and payment methods. 
  • Bundle Management – this component is responsible for managing the bundles that are offered by the client at any given time. The bundles are used to group products and if the configured limits are exceeded offer that bundle to the customer. The bundle usually provides full access to all titles once a certain number of subscriptions and subscription value has been reached. 
  • Campaign Management – this component is responsible for managing the campaigns that are offered by the client at any given time. The campaign provides exclusive offers for a period after which the subscription rolls into a standard subscription. 
  • Complaint Management – this component is responsible for managing complaints received from customers related to the services provided by the title. 
  • Discount Management – the component is responsible for managing the discounts that the client can apply to a customer's subscriptions. 
  • Distribution Management – this component provides functionality to manage the distribution of delivery addresses for customers subscribing to physical media (newspapers, magazines, etc.), and which must be delivered at a given address. Functions as the central hub for all delivery addresses maintained by a subscriber at any given time. Integration with some delivery companies are provided from the start, but new integrations can be added as required. 
  • Document Management – this component is responsible for managing documents to be sent to the end-customer. The documents are invoices, receipts, dunning notices, credit notes, etc. All documents are sent via a third-party document management system to the end-customer. 
  • Financial Management – this component is responsible for reporting revenue into the client ERP system. Information is transferred daily in a summarized manner based on the dimensions defined by the client. 
  • Payment Management – this component is responsible for managing payments made by customers. The component receives information from financial institutions (banks and payment gateways) and apply them to the customer account. The component also manages refunds. 
  • Product Management – this component is responsible for managing the cache of products offered by the client. The component exists primarily due to performance reasons. 
  • Subscription Management – this component is responsible for managing the customer's subscriptions, both active and inactive. It also provides functionality to retrieve and present the offerings that a given customer may be eligible for based on existing subscriptions and other parameters. 
  • Title Management – this component provides functionality to manage titles (newspapers, magazines, etc.) published and handled either digitally or via physical media that the CLIENT provides to customers. A title defines certain key attributes of the title, such as name, description, distribution system, distribution calendar, publishing days, revenue controls, access controls, etc. This information is used by other components in AMPS.

AMPS Management Functionality

The AMPS Management Functionality is a set of generic components that are designed for use within both standard AMPS implementations and customer-specific workflows. Several integration points have been defined. The integration points are fully managed by Aria Workflow and used by other external systems to access AMPS functionality. The integration points have been split into several folders based on the subject areas to which the API belong, namely:

  • Solution Management – this component provides functionality to manage the overall solution such as message authentication, event processing, locale translation, modulo-checking, etc.   
  • Log Management – this component provides functionality to log and report on error, informational, warning and other messages generated throughout the solution. This module is internal-only and has no externally available interfaces.
  • Tax Management – this component provides functionality to manage tax calculations based on the configuration of taxes within the Aria Core solution. This module is internal-only and has no externally available interfaces. 

WE NEED TO DETERMINE WHAT ELSE SHOULD BE DOCUMENTED FOR AMPS MANAGEMENT FUNCTIONALITY. WE ORIGINALLY HAD THIS TITLED AMPS FOUNDATION SUITE (see AMPS archived content), THEN AMPS EXTENDED SERVICES, AND THEN AMPS MANAGEMENT FUNCTIONALITY PER REQUEST FROM NIELS N. 

Solution Components 

The following figure shows the different components that comprise AMPS. Each of these components is detailed in separate documents per the highlighted links above.

Solution Components_2.jpg


Last modified

Tags

Classifications

This page has no classifications.