State Software Redesign
Redesign Support Resources
- HCC USXS-R Documentation
- HCC USXS-R Fiscal Year End Documentation
- Redesign to Classic Report Crosswalk
- USAS-R On-line User Manual
- USPS-R On-line User Manual
- USPS Redesign vs Classic Terminology
- SSDT Redesign Newsletters
- Comparison USPS & USPS-R
- USAS-R Five Year Forecast
- USPS-R CYE Presentation
- USPS-R CYE Checklist
- USAS-R CYE Presentation
- USAS-R CYE Checklist
Redesign Public Demo Instance Login
Login information is the same for both public instances:
Please read below before beginning a session.
The Redesign’s Production Release is available for the public. The demo instances contain anonymized training data allowing you to experiment with the Redesign software! Just a reminder, these are shared public instances so you should not enter any sensitive data that you would not want others to see.
These databases will be periodically reset. In SSDT’s Redesign Support Resources (see above), the USAS Appendix includes ‘processing guides’ on how to create accounts, vendors, transactions, etc. The USPS Appendix includes steps on how to add a new employee and process a payroll, etc. You are more than welcome to use these processing guides to assist in experimenting with the demo instances.
Includes a list of recorded weekly webinars (in MP4 format) we have had with ITC Fiscal Support Staff the past couple of months.
It seems the word ‘conversion’ has been used frequently when discussing how districts are going to transition to the redesigned software. There is no conversion of your data that must be done ahead of time.. you don’t have to convert account codes, etc. in order to use the redesigned software. We prefer to call the redesign a migration or ‘upgrade’ of the existing software. We are importing 100% of your existing data from Classic into a ‘redesigned’ version of State Software. Our goal is for you to have a seamless transition moving from Classic to the redesign software in a very short time frame. Is there any clean-up that needs to be involved? Not really. For example, in USAS, we advise leaving old accounts and vendors on the database for historical purposes. If you have old accounts or vendors you no longer use, before migration, change them to an ‘inactive’ status. Classic has the ACCLOAD and VENLOAD programs that will allow you to mass inactivate old accounts and vendors.