PICON
Formula: Parties_Inside_Type_Others-cat_Numbered
More specifically
Involved-Parties_DocName_DocType_PE-Category_NumReference
OR
1.[ReceivingParty-Sender]_2.[DocumentName]_3.[DocumentType]_4.[Primary-Entity-Category]_5.[Numbered reference OR Ref. OR RefID OR Document Version and most commonly Date]
Name will has several elements, elements are ordered by importance.
Examples. : please observe from the name you get a clear indication of the content :)
Tesla-ABJD_memorandum-of-understanding_CNTR_CLNT_v2303 00-ABJD_2024-general-price-table_MSRP_DISTI_2401 Etisalat-ABJAD_mobile-internet-invoice_INV_SVP_2107 Etisalat-ABJAD_mobile-internet-invoice_RCPT_SVP_2107 00-ABJD_general-employment-agreement_CNTR_EMPL_v21 HusamABBOUD-ABJD_Brazilian-Passport_ID_EMPL_v21 00-ABJAD_Naming-Convention_HowTO_EMPL_v2107 HusamZAMMAR-ABJD_UAE-Driving-License_ID_EMPL_v22
Participants / Parties / People, Entities, Agent Involved: Who is involved in this document, usually there is [receiving party] and [sender or issuer], such as client-company, employee-employer etc ReceivingParty: Typically is the sub-folder name or primary entity (e.g. Client Name, employee, service provider..) for which the document will be filed. Sender: or Owners or maker of the documents usually us the company (e.g. ABJAD, .. etc) Inside / Content / Name / DocName is a free segment used to provide specific information on the document content, or purpose. (e.g. invoice date, years term. ) Type / DocType / Type of the Inside: is selected from a user-defined smart list. (e.g. LTR: Letter; INV: Invoice; LFINS: Life insurance) Other Party Category, Sort, Group / Receiving Entity Classification: is a smart list of possibilities that can logically categorize the primary entity or perhaps the type of documents involved. (e.g. for such as employees: department; for Insurance: insurance companies, more used as CLNT, PRSP, EMPL) Numbered / Sequential reference OR DocVersion OR ReferenceID YYMMDD as needed: We DON’T use incremental or auto-increment (such as 1,2,3 etc) but we use Date as versioning/sequential/numerical control, we using ISO 8601 time as versioning, time without separations YYMMDD So you can do YY or YYMM or YYMMDD as (OR YYMMDDHHMMSS)
For Invoicing, receipts it represent Year, Month: as _2108
For versioning it represent Date() month of last revision, Ex. 00-ABJAD_Expense-Management-System_APP_FNNC_v21
For Reference ID you start with “r”: is a free-text segment used to help identify a specific document or a group of related documents. (e.g. a contract no., a policy number, or a date)
Note that doc version be used as date (the most important date of the file, or date of last revision or due date if invoice)
so for example: 00-ABJAD_2024-general-price-table_MSRP_DISTI_24 (the general price table as first revision of 2024)
00-ABJAD_2024-general-price-table_MSRP_DISTI_2402 (the general price table as revision of 2024 month #2)
00-ABJAD_2024-general-price-table_MSRP_DISTI_240215 (the general price table as a revision of 2024 month #2 day 15)
Chinacom-ABJAD_May-SoF_INV_CLNT_240520 (statement of fee and invoice of May due in 2024 -05 - 20)