The Philippine Identification System (PhilSys) aims to provide a valid proof of identity for all citizens and resident aliens as a means of increasing access to and simplifying public and private transactions, as well as accelerating the digital transformation of service delivery.
The PhilSys, through the Use Case Development and Management Service (UCDMS) - PhilSys Advocacy Unit (PAU) conducts advocacy activities, such as webinars, to provide information on the salient features of the Republic Act No. 11055, otherwise known as the Philippine Identification System Act of 2017, the different PhilSys authentication services, and the onboarding procedures should the relying party (RP) wishes to avail the services.
Implementing the PhilSys advocacy activities will result in the familiarization of the RPs with the PhilSys services, recognition of PhilID and ePhilID as valid proofs of identity and age, and the reduction, if not elimination, of the non-acceptance of PhilID and ePhilID.
Office or Division: | Use Case Development and Management Service | |
Classification: | Complex | |
Type of Transaction: | G2G – Government to Government; G2B – Government to Business | |
Who may avail: | All Government Agencies, LGUs, GOCCs, and other Government and Social Protection Instrumentalities Financial, Business, and Private Institutions | |
CHECKLIST OF REQUIREMENTS | WHERE TO SECURE | |
Formal request letter addressed to the Assistant National Statistician (ANS) of the UCDMS with the following details: Subject: Request for the Conduct of PhilSys Advocacy Activities (i.e., webinar, face-to-face activity, other advocacy activities). Address: PhilSys Registry Office 12/F Cyberpod 5 Eton Centris, EDSA Quezon City Email: ucdms.staff@psa.gov.ph | Requesting Government Agencies, LGUs, GOCCs, and other Government and Social Protection Instrumentalities Financial, Business, and Private Institutions |
CLIENT STEPS | AGENCY ACTIONS | FEES TO BE PAID | PROCESSING TIME | PERSON RESPONSIBLE |
1. Submit a formal request letter. | 1.1. Receive the formal request letter. | None | 1 day | Project Development Officers IV, III, II and I |
None | 1.2. Schedule a meeting with the RP. | None | 1 day | Project Development Officers IV, III, II and I |
2. Provide decision to proceed with the advocacy activity based on the agreed date. | 2.1. Conduct preparatory activities for the implementation of the advocacy activity once RP agrees on the advocacy activity date. | None | 3 days | Project Development Officers III, II and I |
3. Receive the online registration form/link. | 3.1. Send the online registration form to the RP. | None | 4 hours | Project Development Officer II/I |
4. Distribute the online registration form to target participants for accomplishment before the targeted deadline. | 4.1. Send the calendar invitation with the online conference application link to the registered participants. | None | 4 hours | Project Development Officer I |
5. Attend the advocacy activity. | 5.1. Conduct the requested advocacy activity. | None | 1 day | Project Development Officers IV, III, II and I |
TOTAL: | None | 7 days |