Procedures for Fugaku Usage

As of June 9, 2025, procedures for Fugaku usage have changed to those through the Fugaku Account Application System (“FAAS”) for all projects using Fugaku.

• Previously, after a project was accepted, the project representative conducted the usage initiation procedures. Once the procedures were completed, a local account for Fugaku (“Fugaku Account”) was issued. However, individuals will apply for and obtain their own Fugaku Accounts moving forward. Once a project they participate in is accepted and the necessary procedures are completed, their account will be linked to the project, allowing them to use the allocated resources. (See the diagram below)
• Identity Verification for users will be conducted individually as part of the Fugaku Account application process via FAAS. Therefore, the conventional in-person Identity Verification procedure by the project representative (or deputy representative) is no longer required.
• The procedures for documents required for using Fugaku (pledge, security export control checklist) will generally change to those online. (However, for some documents, such as the pledge for fee-based access projects that require a seal, submission via PDF will still be required.)
• Upon completing the review in the Fugaku Account application procedure by FAAS, individuals will automatically be enrolled in a separate startup project*1, independent of the accepted project. The Identity Verification status is maintained for the Fugaku Account validity period (5 years), allowing seamless access after the next project is accepted.

Relationship Between Fugaku Account Issuance via FAAS and Accepted Project Execution

• *1 Startup projects are the default project for account issuance (Project ID: rs2xzzzz) that individuals automatically participate in when a Fugaku Account is issued via processes such as completing Identity Verification by eKYC and agreeing to the pledge after obtaining an account for using FAAS ("FAAS Account").
  The secretariat will handle all the procedures related to participation in this project, so there is no need for both project representatives and project participants to follow these procedures.
  

FAAS (Fugaku Account Application System) is a system operated by the RIKEN Center for Computational Science (R-CCS), the organization responsible for managing Fugaku, and is used for necessary procedures to utilize Fugaku.

The procedures carried out via FAAS include those to be completed by users, as well as those to be completed by the project representative (or deputy representative) of a Fugaku access project.

• Procedures to Be Completed by Users (Applicable to all users, including project representatives, deputy representatives, and members)
  • These procedures must be completed by all individuals who will use Fugaku or who plan to do so in the future.
  • First, users must obtain an account to use FAAS (FAAS Account). They must then complete Identity Verification, security review entry for individuals, and agreement to pledge (for individuals) on FAAS.
  • If the user’s affiliated institution, residential information, or other attributes change, the above procedures (Identity Verification, security review entry for individuals, and agreement to pledge for individuals) must be completed again.
  • Once the operating organization completes its review, a Fugaku account will be issued.
• Procedures to Be Completed by the Project Representative (or Deputy Representative)
  • These procedures include usage initiation procedures conducted after a Fugaku access project is accepted, as well as those required when changes (such as additions) to project members occur during the project period.
  • During the usage initiation procedure, the representative must complete the security review entry for the project and the agreement to pledge (for project use).
    If any project member's affiliated institution, residential information, or other attributes change, the security review entry for the project must be resubmitted after that individual has completed their security review entry for individuals.
  • These procedures must be completed by the project representative (or by the deputy representative acting on their behalf).

For detailed workflows and key points, please refer to the tabs on the right:
“User procedures,” “Procedures for Project,” “Procedure for change members,” and “Change of affiliation, etc.”

FAAS Screen Image after Login

The procedure flow for users (applicable to representatives, deputy representatives, and project members) is shown below.

FAAS procedures are primarily conducted online (some conditions require PDF submission).
Please check the following points and complete the necessary procedures.
For detailed FAAS operation instructions, refer to the manual available on the login page.

• Those without an HPCI-ID should newly register an HPCI-ID via the HPCI online application system.
  * This is required when obtaining a FAAS account.
  

• Access the FAAS login page and create an account using the link, “First-time users click here to create an account.”
  
• Please confirm in advance that you will need your HPCI-ID and verification code.
  (You can check your HPCI-ID and verification code via "HPCI-ID Registration Details Confirmation" in the HPCI online application system.)
  
• After obtaining an FAAS Account, the following procedures will be available.
  

• Identity Verification and affiliation verification are typically conducted via eKYC service (using your smartphone or other device). If completing the procedure via eKYC is difficult, the process can also be completed by uploading the necessary Identity Verification documents on FAAS.
  
• The documents that can be used for Identity Verification via eKYC are as follows. Please prepare one of the following respectively in advance.
  
  • Identity Verification Procedure
    Each document must be a Japanese government-issued ID.
    Passport (must include an address page), Driver’s license, My Number Card, Basic Resident Registration Card with photo, Residence Card
    
  • Affiliation Verification Procedure
    ID issued by the affiliated institution (employee ID, student ID)*, Certificate of enrollment (issued within the last 3 months)
    *Both sides are required (When taking photos of the ID, set the number of shots to “2” and capture both the front and back sides.)
    
• If Identity Verification has already been completed in the HPCI online application system, eKYC Identity Verification is not required.
  （You can check this via the "Others" -> “Inquiry on the issuance status of your HPCI Account” in the HPCI online application system.）
  

• The checklist for individual security reviews is completed via FAAS online.
  
• Please answer questions regarding your place of residence and the countries where you will be using the system, then submit the form.
  (If there is a change in residence, resubmission is required.)
  

• Agreement to the pledge (for individuals) is completed via FAAS online.
  Check the contents of the “Account Pledge” displayed on the FAAS screen, enter the necessary details, and submit it.
  
• This procedure is not required if you have already agreed to it (submitted).
  

• After completion of the examination, etc. concerning security export control by the operating agency, a Fugaku account (single account) will be issued.
  A single account is an account that allows multiple issues (groups) to be used with one account. New “Fugaku” local accounts issued after April 2022 will be this single account.
  
• If you already have a single account, you can use it as-is.
  
• If you have a traditional account (“traditional account”), you will be issued a new single account, which will be linked to the adopted issue.
  In addition, account information that can be referenced on FAAS is for a single account, so if you have both a traditional account and a single account, we recommend that you merge them into a single account.
  Please contact the Help Desk for more information.
  

The following diagram outlines the flow of usage initiation procedures after a Fugaku access project has been accepted.
These procedures must be carried out by the project representative (or by the deputy representative on their behalf).
Also, Procedures must be completed for each accepted project.

FAAS procedures are primarily conducted online (some conditions require PDF submission).
Please check the following points and complete the necessary procedures.
For detailed FAAS operation instructions, refer to the manual available on the login page.

• Project representatives are also required to complete the “Procedures for Users.”
  Please refer to the “User procedures” tab on the left and complete the necessary steps.
  Note: If the project representative has not completed the procedures, the Fugaku account setup for project members cannot proceed.
  
• Please ensure all project participants (including deputy representatives) complete the same procedures.
• Additionally, the following procedures as a project representative can be conducted simultaneously:

• For the entry of “Security Review Checklist for the Project (a),” the entry results of the “Security Review Checklist for Individuals (b),” separately input by project participants (including representatives and deputy representatives), are reflected, so verify its contents before submission.
  
• If project participants have not yet entered (b), prompt them to do so immediately.
  Submission of (a) is possible even if all the project participants have not completed entries in (b).
  (However, (a) must be resubmitted after entries in (b) are completed.)
  

• For Free Access Projects
  # For Periodic Call Projects (Period A and B), Fugaku Small Scale Projects, and Fugaku Trial Access Projects (including the First-Touch and Seminar Option)
  
  • FAAS allows online procedures.
    
  • Deputy representatives can submit the pledge on behalf of the project representative.
    In such cases, download the pledge PDF from the FAAS pledge submission screen, complete the required details, and upload and submit it via FAAS. The Office will review the submission.
    

• For Fee-based Access Projects
  # Fugaku Fee-based Access Projects, Fugaku Fee-based Trial Access Projects, and Fugaku Application Service Projects
  
  • Fee-based access projects require documents relating to the cost of Fugaku usage (Pledge Form 1 or Form 2), so submission via PDF is required.
    
  • Download the pledge PDF from the FAAS pledge submission screen, complete the required details, and upload and submit it via FAAS.　The Office will review the submission.
    
  • If the recipient of the Fugaku usage fee invoice differs from the project representative’s affiliated institution, Pledge Form 2 must be stamped and submitted in its original form via mail.
    
    

    [Mailing Address for Original Documents] HPCI Operations Office, RIST Kobe Center, Kobe KIMEC Center Building 6F, 1-5-2 Minatojima-minamimachi, Chuo-ku, Kobe-shi, 650-0047 Japan

The procedures via FAAS and key points related to changes in project members (additions or removals) are outlined below.
Applications for member changes should continue to be submitted through the Application Support System as before. For details, please refer to the following page on the HPCI Portal Site.
Procedures for Project’s Start/ Finish/ Membership Update（Link to HPCI Portal Site）

After the application for adding or removing a member has been approved, please complete the following procedures via FAAS.

• To be completed by the member being added:
  • The additional member must first obtain an account for using FAAS (FAAS Account), then complete Identity Verification, security review entry for individuals, and agreement to pledge (for individuals) on FAAS.
  • These procedures can be completed at any time, regardless of when the member change application is submitted.
  • Please refer to the “User procedures” tab on the left for further details.

  Identity Verification	security review Entry for individuals	Agreement to the Pledge (For Individuals)
  Necessary	Necessary	Necessary

  
  


• To be completed by the project representative (or deputy representative):
  • Please instruct the additional member to complete the above “Procedures for Users.”
  • After the application for member addition has been approved, confirm the status of the procedures completed by the new member.
  • Once the new member has completed the security review entry for individuals, the project representative (or their deputy) must resubmit the security review entry for the project.

  Security Review Entry for the project	Agreement to Pledge (for Project Use)
  Necessary (Resubmission)	－

After the application for member removal has been approved, no further procedures are required via FAAS.

If there are any changes to the email address, affiliated institution, residential information, or other details of a project member (including the representative and deputy representative), please update the HPCI-ID registration information promptly. For details on how to make these changes, please refer to this instruction manual [PDF].

If the project representative of a periodic or year-round application project changes their affiliated institution, the confirmation process must be conducted again by the head of the new institution. The URL for the procedure page will be sent via email to the new institution head. Please contact the helpdesk with the project number and the new institution head’s information (institution name, department, title, name, and email address). Once the HPCI-ID registration information is updated, the changes will be reflected in FAAS. If the affiliated institution or residential information is updated, the following procedures must be completed via FAAS.

• To be completed by the affected project member:
  • If there is a change to the affiliated institution or residential information, the individual concerned must complete Identity Verification, security review entry for individuals, and agreement to pledge (for individuals) again via FAAS.
  • Please refer to the “User procedures” tab on the left for further details.

  Identity Verification	security review Entry for individuals	Agreement to the Pledge (For Individuals)
  Necessary	Necessary (Resubmission)	Necessary (Resubmission)

  
  


• To be completed by the project representative (or deputy representative):
  • The project representative (or deputy representative) should instruct the affected member to complete the above “Procedures for Users.”
  • Once the member has completed the security review entry for individuals, the project representative (or their deputy) must resubmit the security review entry for the project via FAAS.

  Security Review Entry for the project	Agreement to Pledge (for Project Use)
  Necessary (Resubmission)	－

• To be completed by the affected project representative:
  • If there is a change to the affiliated institution or residential information, the individual concerned must complete Identity Verification, security review entry for individuals, and agreement to pledge (for individuals) again via FAAS.
  • Please refer to the “User procedures” tab on the left for further details.

  Identity Verification	security review Entry for individuals	Agreement to the Pledge (For Individuals)
  Necessary	Necessary (Resubmission)	Necessary (Resubmission)

  
  


• To be completed by the project representative (or deputy representative):
  • Once the member has completed the security review entry for individuals, the project representative (or their deputy) must resubmit the security review entry for the project via FAAS.

  Security Review Entry for the project	Agreement to Pledge (for Project Use)
  Necessary (Resubmission)	If the affiliated institution has changed, resubmission is required.