{"id":862,"date":"2023-01-12T22:54:25","date_gmt":"2023-01-12T22:54:25","guid":{"rendered":"https:\/\/webresources-uat.com\/nchrp1918\/?page_id=862"},"modified":"2023-01-12T22:54:25","modified_gmt":"2023-01-12T22:54:25","slug":"66-state-and-vendor-system-updates","status":"publish","type":"page","link":"https:\/\/crp.trb.org\/nchrpwebresource2\/transitioning-growing-stage\/66-state-and-vendor-system-updates\/","title":{"rendered":"(66) State and Vendor System Updates"},"content":{"rendered":"\n
\n
\n
\n
RESEARCH AND PLANNING<\/a>  |   SETUP<\/a>  |   ONGOING OPERATIONS<\/a>  | TRANSITIONING AND GROWING<\/a><\/div><\/div>\n \n
\n\n

State and Vendor System Updates (66)<\/h1>\n \n

Description:<\/strong><\/h3> \n\n

\n \n \n<\/p>

State and vendor technology systems will need to be updated to allow for program growth, corresponding to changes in law or rulemaking. To further support growth and transition, correct any technology issues discovered during small-scale operations. It is possible that a new system or technology procurement will be required. <\/p> \n\n

\n \n
\n

Details:<\/strong><\/h3>\n

The implementing RUC agency updates specification documents to allow the systems to support the new law, rulemaking, and operational procedures. To make such updates, the implementing RUC agency follows systems engineering procedures and leverages lessons learned during the implementation of the original system. Depending on system architecture, specification documents may be separate for state and vendor systems. After the specification documents have been updated, the agency should determine whether a new procurement is necessary, or whether the changes can be handled under existing contracts, possibly with a change order. \n <\/p>\n <\/div>\n

\n
\n

Primary Use:<\/strong><\/h3>\n

Update state and vendor systems for growth\/transition.<\/p>\n <\/div>\n \n

\n \n
\n

Best Practices\/Lessons Learned:<\/strong><\/h3>\n