Here are a few examples of common tickets and what information we will need to answer your question.

CASA or Data Reduction/Analysis Issue:

Please submit your ticket to the Data Reduction department and please include information on the CASA version and Operating system you are using. It is also important to note if you are using CASA over ssh or VNC.

Please provide us information so that we may recreate the error on our machines. A minimum working example can be vital to finding a solution.
A good minimum working example includes:
– the relevant data set (reduced in size as appropriate)
– a succinct script containing only the commands needed to demonstrate the issue
– the expected result of the script
– the actual result of the script
– any error messages produced by CASA
– the log output from the script
– information on your overall computing setup (operating system, memory, disk space, whether jobs are being run locally or on a cluster)
– information on other approaches tried to resolve the issue (changes of task parameters, runs on machines with different amount of memory, etc).

Proposal Change request:

Please note the requirements in the chapter "Changes to ALMA Proposals" in the Users' Policy.

There is also an additional knowledge base article on the topic here: May I make changes to my project after the proposal review process?

Please submit change request tickets to the Proposal Change Request department. All major change requests must be self-contained. All relevant information for evaluation must be included in the submitted Helpdesk ticket.

At minimum, the justification must contain the following information:

–Clear description of the proposed change and its classification as a major change under Appendix B.

–Explanation of why the change is required, including whether it represents a correction, a response to new information, or a technical optimization necessary to achieve the approved science goals.

–Explicit description of any extra information that has become available since the time of the original proposal, if applicable.

–Full technical justification of the new request, including any specific detailed new calculations supporting the change.

Any figures, tables, or supplementary information provided will be treated with strict confidentiality. Change requests that do not provide sufficient information for evaluation may be rejected on the basis of insufficient

justification.

Please contact your Contact Scientist if you have any questions on the process.

Proprietary Extension Request:

Please see the knowledge base article May I request an extension to my observing program's proprietary period?
Please see the Extension of Proprietary Periods in the Users' Policy.
To start the request, submit a ticket to the Proprietary Extension request department. Please fill out the blanks with your Project code and the scheduling blocks you need an extension on if it is not for the whole proposal. Please include how long you would like the extension and provide a justification.

Any information given on these tickets is kept private with only those who need to see the justification able to access the ticket.

Requesting data not provided in the archive:

If you would like to request the QA0 pass (previously known as raw or stale) data of your project before QA2 is complete, please note the guidelines in Observational data access: QA0 access in the Users' Policy.
Please also see the knowledge base article Under what conditions can I request the raw data of my observing program be delivered before quality assurance is completed?.

Please submit a ticket to the Archive and Data Retrieval department with the sub-category Data request (calibrated MS, stale data, calibrator data, or suggestions) to begin the process.

For calibrated ms requests, please select the same department and sub-category. Please review the knowledge base articles
How do I obtain a file of calibrated visibilities ("measurement set") for ALMA data?
Interferometric Calibration and Imaging Regeneration
What Calibration and Imaging products will be delivered to me?

Requesting a QA3:

If there is something wrong with the QA2 of your project, please submit a QA3 request. More information on QA3 is found in the chapter Problems with delivered data in the Users' Policy.. Please also check the QA3 chapter in the Technical Handbook

The request is made by selecting the department Data reduction and checking the Quality Assurance Level 3 (QA3) Request checkbox. Please include a detailed description of the issue and why this is a QA3 request so that we have all the information needed to determine if the project should start the QA3 process.

If you would like to request data that is currently in QA3, please submit a ticket to the Archive and Data Retrieval department with the sub-category Data availability (during QA3, server down, or suggestions).