AMS in ITS Components
AMS in ITS Components Glossary
When processing AMS in ITS tickets in JIRA, the Assignee must select a Component which describes the nature of the ticket and keep this up to date. This provides useful information on the types of tickets that are being processed.
The Assignee must select a Component from the below list:
Component | Definition/scope |
|---|---|
Permissions / Access Requests for Member | Any scenario which involves a user requesting AMS permissions for a Member Office. |
Permissions / Access Requests for SCI | Any scenario which involves a user requesting AMS permissions for an SCI Office. |
Permissions / Access Requests for SCI Centre | Any scenario which involves a user requesting AMS permissions for SCI Centre. |
Any scenario where a user cannot log in to AMSu, but where the remediation does not involve a change in user permissions. Examples include:
| |
Any request to open or close an Award or Partner Agreement. | |
Task delegation / auto delegation set-up | Task delegation - any request to bulk delegate tasks/roles or delegate an individual task for a user. |
General query | General information requests, which do not fall into any other Component category, for example:
If any ticket does not fall into any other Component, it should be categorised as General query. This category should be reviewed periodically to assess if new Components should be considered. |
Data modification - changing Donor | Any request to change a donor, originating donor or both in one or multiple Awards. |
Data modification - changing Start Date | Any request to change the Start Date in one or multiple Awards. |
Data modification - changing Award Class | Any request to change one or multiple Award Classes. |
Data modification - Funding streams | Any request to apply a change in a Funding stream. |
Data Modification - linking/archiving of PRIME projects | There are certain stages/statuses of an award and phase/status of a Project in which editors and super-users are prohibited to link/archive PRIME projects to awards. Therefore tickets maybe submitted requesting AMS support to do so. |
Data modification - other | Any request to modify capture data which does not fit into any other Data modification category. For example;
|
Donor or Partner creation/update | Any request or issues related to setting up a new Donor or modifying an existing one. |
Office creation/update |
|
Notifications | Any issues/set-up requests relating to notifications sent out by AMS including in-app, email, or weekly digest notifications. |
Workflow issues | Any issues related to workflow malfunction. |
Budget table | Any request or issue related to the manipulation of a Budget table in one or multiple Awards, Budget codes and DRCs. |
Match functionality | Any request or issue related to match functionality including Award Requiring Match, Match Plans, or Match Algorithm. |
CAM | Any request or issue related to Cost Allocation Methodology (CAM). |
Pooled funding | Any issues related to the Non-humanitarian pooled funding mechanism. |
Reporting schedules | Any request or issue related to the modification of reporting schedules in an Award or Partner Agreement. |
AMS-PRIME Integration | SOF-PRIME project relationship is mastered in AMS. When new projects are created in PRIME, these transfer over to AMS via an integration. Users then link these PRIME projects to respective SOFs in AMS and the relationship(s) are then sent to PRIME (and Agresso). AMS-PRIME integration tickets involve: |
System bug/defect/outage | Any notification of a system bug, defect, or outage.
Note: Notifications of system bugs should be linked with a Bug ticket in the AMS Project? |
AMS-Agresso Integration | Any request or issue which relates to both systems and where the resolution affects one or both systems. |
AMS- TIM Interface | Any request or issue which relates to both systems and where the resolution affects one or both systems. |
FlexOM | Any request or issue related to FlexOM. For example:
*This would change once the FlexOM project transitions to BAU |
PAL/TEA | which relates to a |
Humanitarian Response Code | Creating, updating or deleting Humanitarian Codes in AMS |
AMS Reports | Any issues with the existing reports on AMS under the reports section, bugs related to them, improvement requests to them etc |
BI Reports | Any requests related to BI Reporting/KPIs, AM Dashboard, enhancement requests for new type of reports, |
Changing Currency |
|
Data Creation | Requests related to creation of data on AMS, example Project creation, award creation, test data creation, etc. |
AMS Enhancements |
|
General query: TD BAU | Request coming from TD Projects BAU Any request from users for guidance or training on AMS This category should be reviewed periodically to assess if new Components should be considered.
|
CAPP | Support Request received to support CAPP Transition (Data creation, Award update, Org unit updates, Budget uploader etc) or Process queries to support the transition process. |
OHT | Support Request received to support OHT Transition (Data creation, Award update, Org unit updates, Budget uploader etc) or Process queries to support the transition process. |