Answer: 

it can take a period of time from the moment that a new standard is made available to the public until it appears in AutoPIPE Vessel. See the following steps taken to add a new code to the program:

Step 1: A new standard / code is released / updated. 

The standard's governing body public announces that a new standard / code will be released in the future. Most existing standards / codes are released on an established timeline (every 1,2, 3. 4, etc.. years). There have been cases when a standard / code release scheduled date has been skipped. One does not truly know when a code is actually going to be released until it has actually been released. 

Step 2: Code / Update released in print version.

With the advent of the internet, most standard / codes are available electronically, but they are still printed in book form. In some cases an electronic copy maybe available for consumption months or years before a printed version. It is always best practice to wait for a printed version release date because changes can be easily made to the electronic version, and may contain errors that would be addressed before a printed version is released. Yes, the printed version may contain errors, but more time has been allotted to catch these errors and fixed before printing.

Step 3:  Industry has time to review and decide to adopt or reject the standard / code

Just because a new version of a standard / code has been released does not mean that the respective industry is going to immediately accept it. There have been cases where updates have been rejected by industry until a new revision has been released.

Most codes will have 2 important dates referenced, Date of issuance and effective date. The date of issuance is the date the standard / code was made available to the public. The effective date is the date before any one should reference / enforce a standard / code on a project construction or use in design.

Example: 

In most codes (Example ASME B31.3 - 2018) there is a page near the front of the document with copyright information (image below from ASME B31.3 - 2018)

 

Again, the time between the date of issuance and effective date is time allotted for industry stakeholders to evaluate and accept / reject the standard / code edition. 

Step 4: Add an enhancement for a new feature

At this point, an enhancement request must be logged. These are either logged based on Service Request submittals from end users or anyone involved with the product team. Only after being logged does the development team begin the process of adding the feature; evaluation based on importance, number of people requesting the code, effective date, development effort, etc..

Step 5: Add enhancement to schedule

After an enhancement has been logged and given approval to be added, now the development team and Program Manager determine based on existing workload / commitments, what project backlog the enhancement will be added too. Keep in mind that scheduling of defects and enhancement happens months ahead of the actual work.     

Step 6: Development time to add feature. 

One never truly knows how much development time will be needed until conducting a thorough review of the standard or changes made since the last edition was released. Furthermore, anyone who has read a standard / code and tried programing it's intent knows how difficult and time consuming this process can take.

Step 7: Testing

Only after the development team has completed their work, will a version build be sent for testing. The entire build is subjected to a huge battery of tests to confirm new features and defects have been properly vetted and performing as intended 

Whenever an item fails testing, it goes back to development for rework and then must be resubmitted in a new build to again undergo a complete battery of testing. Sometimes this is an iterative process until it passes and can be released in a new version of the program. Otherwise, all scheduled work that does not pass testing by the predetermined scheduled release date, will be completed in the next project plan. 

Step 8: Released in future version of AutoPIPE Vessel

How long does this all take? it all depends on publish date, enhancement request submitting date, number of people requesting, development time, QA testing, schedule release update project cycle, etc... Best case scenario, 4-6 months after publication effective date. However, if it failed testing and development is already in the middle of another project plan, it may take 6-9 months longer before it appears in the program. Again it all depends on factors mentioned above.

In summary, just because a code is available does not mean it is immediately put into the program. However, it all starts with submitting an official Service Request for an enhancement. The more people who ask for the same request and industry's acceptance will push development to get said feature into the program quicker.