Project Codes and Project Reports
Posted: 230910 Sun 2309
Each issue the BWTT deals with is handled as a project, and gets a unique Project Code by which it can be referred to easily, starting with the two-digit year when the project was first introduced in the BWTT, followed directly by the one-digit month (using uppercase hexadecimal numbers for A=October, B=November, C=December). followed by a colon and then the shortest possible name that summarizes the topic/issue, which makes the Full Project Code, and there should also be created a unique Abbreviated Project Code that replaces the name with an abbreviation of it.
Projects are not handled on a national basis, even those which apply currently only to one specific country. Projects should be kept reusable and transferable, so while it can be part of the project to deal with the current national applicability and idiosyncracies, all projects should be treated equally as just specific aspects of the world, from which one can learn for other projects.
The BWTT publishes a Projects Report PDF (see https://ttpub.ftdm.org) wherein all projects are listed and described in detail per year, each year starting first with a list of all still open/unfinished projects, then a summary overview of the year, followed then by the detailed reports of the projects in the order of their Full Project Codes, with all the Workflow Steps that have been applied to them in the given year (referencing back to prior Workflow Steps where applicable).
Projects are not handled on a national basis, even those which apply currently only to one specific country. Projects should be kept reusable and transferable, so while it can be part of the project to deal with the current national applicability and idiosyncracies, all projects should be treated equally as just specific aspects of the world, from which one can learn for other projects.
The BWTT publishes a Projects Report PDF (see https://ttpub.ftdm.org) wherein all projects are listed and described in detail per year, each year starting first with a list of all still open/unfinished projects, then a summary overview of the year, followed then by the detailed reports of the projects in the order of their Full Project Codes, with all the Workflow Steps that have been applied to them in the given year (referencing back to prior Workflow Steps where applicable).