PPT - short for Phase Procedure and Task. PPT allows structuring, organizing applications and application elements, monitoring and controlling work and data flow. Its web based graphical interface allows designing and building applications and eliminates MINIMASING the need for preliminary flowcharts and diagrams. The design method is TOP-DOWN. You start from the big picture and drill down to a single taskS that can be very simple or very complex.

PPT is ams component that allows system architect, system designer, technical lead and developers to design and build application and application components by defining and structuring phases and procedures and procedure dependencies. It also allows to brake down complex procedures into a set of sequential tasks.

Basically PPT provides a development-time framework for deconstructing a complex application into manageable units of work that constitute a single, recoverable system.

Application defined and organized in such a way is called Phase. One System can have one or more phases. From an operational point of view a job can be associated with either a Phase or a Procedure depending on complexity and mutual dependency between procedures.The picture on the right shows details of one of the two phases. The phase/application/job has 13 procedures. Procedure dependencies and the data flow are represented by arrows connecting procedures. The list of a dependencies of a procedure can be accessed by clicking on the left end of the arrow. Some other details are also available trough this interface like, logs, run time mulitiplication, running time, average running time, etc. A clicking on a particular procedure opens up a window contaning tasks belonging to this procedure. In fact tasks are only executables in the system. A task can be anything runable and capable of returning success code. A particular task can be selected or not for a run. A job can be executed via phase window or can be scheduled using SCHEDULER .

SCHEDULER - provides: immediate, one off or repetitive, full day/time and/or event, scheduling capabilities. Multiple entries are allowed for both timing and event conditions so even the most complex and sophisticated requirements can be specified. The Scheduler interface is simple and easy to use.

The mechanism allows setting up the execution of a Phase (its Procedures and Tasks). Ams Server constantly reads the SCHEDULER and looks for flags, timing and event conditions in order to make decision what Phases whento execute.

Two methods available are:

• timing trigger and
• event trigger.

Both triggers are allowed at the same time and number of the triggers is virtualy unlimited.

MONITOR - Monitor provides a wide range of capabilities that are essential to daily operations in production environment, or providing practical support in development environment. These include job/phase scheduling, monitoring, alerting – and performing phase level actions such as starting, stopping, and rerunning. Across all applications/systems, the Operational Console collects, integrates, and manages the associated operational metadata, helping the operational team and business analysts in planning and maintaining efficient operations.

It all starts with the Monitor tab on the browser-based interface, as shownon on the right
The Monitor tab  provides a summary of all of currently defined jobs by system and phase, showing whether they are running (blue), completed (green), failed (red), waiting (yellow) or baypassed(grey).
From here  you may drill down to see all the procedures within a phase and all relevant types of information for any job in the environment – the reason for the failure, what a job is waiting on, when a job has completed, or when it is expected to complete, average running time, overall log or individual procedures and task logs, etc. For example, you may wish to see all the jobs related to a specific application/phase, internal relationship between procedures to understand how the job is progressing.
This monitoring screen shot on the right shows the dependencies between the different procedures within the selected phase (application) and the progress of each procedure.

At any stage operator can drill down further to see the details of the tasks within individual procedures.
Monitor also provides full day/time and event based scheduling capabilities, allowing applications to be scheduled without the need to write and maintain traditional scripts. 
Dependencies between tasks can become extremely complex in large applications, AMS also provides a fully graphical environment to organize application and help developers define advanced job control flow.
A control flow is a way of expressing detailed logic about the sequence of execution. It uses a collection of connected Procedures (essentially Tasks),  to describe what should be run – the connection between these procedures  specifies an execution dependency (run this before that, for example, or run this if that failed or the other if that was successfull). AMS provides mechanism for number of various dependency scenarious.
With this dependency mechanism AMS provides a development-time framework for deconstructing a complex application into manageable units of work that constitute a single, recoverable system. In AMS world an application defined and organized in such a way is called Phase. The Phase is then available to be scheduled, monitored, and managed trough Monitor tab. The result is a ophisticated end-to-end operational environment.

DQM - ams has two DQM areas where it can be applied. The first  consists of elements of Data Profiling and Data Validation and Correction.  Here, the DQM is used to specify Data Profiling requirements aswell as Data Validation rules in an user-friendly interface. The Data Profiler can be used as a starting point for a detailed Data Validation specification. DQM allows repeated testing of the specified Data Validation rules against real dataset before the integration into the actual proccessing. Both testing and Data Validation processing produce summary and detailed reports on items that failed validation containing enough information to pin-point the problem item. The detailed report can be used in further processing to eliminate bad records.

The second DQM option can be specified in a task as integral step in the data proccessing flow. This task is design by TD and it uses Lookup service. Such a task essentially allows multiple crossreference validation and data correction. It also produces two exception reports, summary and detailed with suficient information on bad data. Diferent decesions on proccessing flow can be setup deppending on the validation results.

All DQM reports are kept in a repository and can be used for long term data quality monitoring and reporting.
DQM specifications and validation/business rules are stored in meta tables

TD - Task Designer module is interactive web based graphical interface used to design various data processing tasks such as transforming inputs and creating outputs, executing SQL statements, executing system commands, etc. 

Input and output components in ams are called IO Objects and processing or transformation components are called services.

The types of IO objects and services are easily recognisable by their colours and icons. IO objects and services are connected with arrows that represent data flow. They connect IO objects with services.

IO objects can be dataset of any type and location which includes tables of almost all known DB types or vendors, and files of most formats.

TD Tasks can take environment variables defined on the calling procedure level or defined globaly.

The same TD task can be used in different procedures.

All the details relevant to a TD task are stored in Meta Tables and open for viewing.

The objects in the task pane can be moved around, and they retain their last position automatically.

IO types:

• Tables - Local, Remote, Most Vendors
• Files
  - All Common ASCI types
  - XML
  - XLSX
• API - JSON
• SharePoint

 Service types:

• M2O - Lookup, Funnel, Agregate
• O2M - Splitter, XL Splitter,
• Other - Non Select SQL, Select SQL, Time Variant

MEAS -My Edit Advanced Setup is a module developed as an extention to PHP My Edit Class used as an interface to ams and application metadata. It provides very rich mechanism for creating forms and functions which allow dinamic interactive DB access. The package is web based interface, highly parametrised and flexible. This package is part of this distribution and it is used to build Interface to ams metadata leyer. It is also very important mechanism for controling type of access to ams and application metadata for diferent user groups and users.
On the right is an example of the inteface to specify one form properties for a table.

Some of the features implemented in ams :
records created and/or altered using MEAS automaticaly get timestamp and user id of the initiator.
Each metadata object in the system can be assigned a help button ('?' symbol) which is linked to the Ams Manual, corresponding chapter. That makes documentation onlyne real-time available. The user can define and create custom/application manuals (project/system documentation) and link an object in the system and the corresponding description.
when populating certain fields a set of choices can be delivered aither from another table (lookup method) or with the list of predefined values,

each elemnt within an object can have a list of attributes which specify what can be done with the element.