Number used in software development

After several years of software development, a small project has become a big project. One of the deepest problems I feel is the use of serial numbers.
For large projects, it is best to specify numbers to manage documents, variables, projects ....
Conventions
01 feasibility analysis report
02 project development plan
03 Software Requirement Specification
04 summary Design Manual
05 detailed design manual
06 User Manual
07 test plan
08 test analysis report
09 monthly development progress report
10 monthly development progress report
11 Software Maintenance Manual
12 software issue report
13 software modification report
Note that the above files are encoded at the beginning.
Then, for the document number:
01 ~ 20: left to the canonicalized document
21 ~ 50: reserved for non-normalized supplementary documents
51 ~ 99: Leave it to the auxiliary document or reference document
Binary conventions
Global g_sys (26) As String 'parameters used to collect regular reports
'G _ sys (0): gClientName variant
'G _ sys (1): variantname
'G _ sys (2): SavePath
'G _ sys (3): modlepath
'G _ sys (4): gColumnCondition horizonewhere
'G _ sys (5): gAttribCondition horizonewhere
'G _ sys (6): gHnList str0 h1, h2, h3,
'G _ sys (7): gLastShowName lastitem unbranded
'G _ sys (8): gWhereCondition abcabcooooooooooooooooo
'G _ sys (9): sorting method 1
'G _ sys (10): gHnListCount 3
'G _ sys (11): gShowIt (0) BRAND
'G _ sys (12): gShowIt (1) VARIANT
'G _ sys (13): gShowIt (2) PACKSIZE
'G _ sys (14): gShowIt (3)
'G _ sys (15): gShowIt (4)
'G _ sys (16): gShowIt (5)
'G _ sys (17): gShowIt (6)
'G _ sys (18): gShowIt (7)
'G _ sys (19): gAttribCount 3
'G _ sys (20): gShowAttrib (0) a1 (custom)