Technology Coordinator Training for PARCC and DC Science

1. Technology Coordinator Trainingfor PARCC and DC Science Office of the State Superintendent of Education Assessment Team

2. Agenda • Technology Coordinator Role • Preparing student devices for testing • Precaching test content • Troubleshooting during testing • Resources to learn more and where to find assistance

3. Materials for this training • All materials and resources for this training are posted at http://osse.dc.gov/page/test-coordinators-training

4. Technology Coordinator Role • May support one school or multiple schools • Assists the LEA or school test coordinator in preparing administrator and student devices for secure testing according to vendor directions • e.g. Downloading and setting up Test Nav Apps on student devices, precaching test content to a designated device • Troubleshoots any technology problems that may arise

5. Definitions • TestNav 8: The Pearson secure test platform on which all students taking computer-based tests will take PARCC and DC Science. There are both bowser-based and app-based versions of TestNav 8 • Pearson Access Next: The web-based administrative system for PARCC and DC Science where technology coordinators, LEA and school test coordinators, and test administrators will login to perform administrative tasks for testing • PARCC.Pearson.com: The hub for PARCC resources, including guidelines, manuals and technology bulletins. • Student device: Any device a student uses for testing – e.g. a laptop, iPad, chromebook, desktop

6. Experienced Technology Coordinators • For a summary of anything new in PARCC technology this year, watch Pearson’s technology crosswalk webinar here: http://parcc.pearson.com/resources/technology-setup/Spring%202016%20Technology%20Crosswalk.mp4 • Read the crosswalk document here: http://avocet.pearson.com/PARCC/Home#14673

7. Tech Coordinator Checklist 1 month before testing • Identify compatible student devices needed for testing • Download and setup TestNav app or configure browsers for TestNav on each device • Configure your network for secure testing • Identify a computer in a secure location (not a student device) to be used for precaching • Schedule infrastructure trial 1-2 weeks before testing • Create a TestNav configuration in Pearson Access Next • After all students are placed in sessions and all accommodations are correct, precache test content • Conduct infrastructure trial 48 hrs prior to testing • Refresh/update proctor cache • Double check all student computers ready for testing (software up-to-date, apps installed, privacy setting/kiosk modes configured) • Gather any ancillary technology materials needed in a secure location for distribution During Testing • Assist test coordinator in troubleshooting any technology difficulties, working with to Pearson tech support to resolve, reporting large irregularities to OSSE After Testing • Purge cached test content

8. Preparing student Devices for Testing

9. Technology Guidelines for PARCC • Most information in this training is drawn from the PARCC technology guidelines and PARCC training modules. These are located here: http://parcc.pearson.com/technology-setup • PARCC technology guidelines give both minimum specifications for technology and recommended specifications for top performance of technology during testing

10. Technology capacity planning tool • If you are unsure how many devices you need to use for testing, or how many to use at once, the PARCC Technology Capacity planning tool can help assess your needs: http://www.parcconline.org/assessments/administration/technology

11. Compatible Student Devices • See full list of devices compatible with TestNav 8 here: https://support.assessment.pearson.com/display/TN/TestNav • Includes Chromebooks, iPads, most laptop and desktop devices running recent versions of Windows and Mac operating systems

12. TestNav Apps • Last year, Chromebooks and iPads had a TestNav app that made for a smoother test experience in most cases. This year, a similar app is also available for Windows and Mac OS. • Java problems seen last year do not apply to the app • OSSE recommends use of the new TestNav Desktop apps, except in cases where a student needs screen reader assistive technology (this is not the same as text-to-speech) • Learn more about the apps and installation here: https://support.assessment.pearson.com/display/TN/Installable+TestNav+Setup+Overview • Apps must be set to “kiosk” mode in most cases for secure testing

13. Browser-based TestNav • Running TestNav on a browser (Firefox, Internet Explorer, Safari) is still available, but we strongly recommend looking into the app. • This year, Chrome browser is no longer compatible with TestNav. This is different from Chromebooks. Chromebooks are still compatible with PARCC, using the app, and are still a great choice. • Find information on installing browser-based TestNav here: https://support.assessment.pearson.com/display/TN/TestNav

14. What is Proctor Caching/precaching? • Proctor caching/precaching allows you to download encrypted versions of the tests to a local computer, which allows tests to load faster and use less bandwidth • See ”Use ProctorCache” in the PearsonAccessnext Online User’s Guide for directions.

15. Configure your network Implement these configurations in your network, so that network security devices such as content filters and firewalls allow connectivity with PearsonAccessnext, TestNav, proctor caching, and email communication with Pearson. Network Configurations: • TestNav 8 Domains and Ports: • *.testnav.com:80, 443 • *.pearsontestcontent.com:80 • *.thawte.com:80 • Pre-caching Local Network Ports: • 4480, 4481 • PearsonAccessnext Domain and Ports: • *.pearsonaccessnext.com:80, 443 • PearsonAccessnext emails: • @support.pearson.com

16. Configure TestNav (1/2) Configuration only need to be done once, and should ideally be done prior to creating test sessions. • Login to Pearson Access Next to configure TestNav and Proctor Caching. Your School/LEA test coordinator can create a login for you. • The TestNav configuration screen can be accessed by selecting Setup > TestNavConfigurations • Select Create/Edit TestNav Configurations from the tasks menu to launch the configuration screen. • Press Start. • You will be prompted to name your configuration. Configuration names must be unique within the PearsonAccessnext website for your state. • Next, using the Organizations drop-down menu, select the appropriate school or LEA from the menu. Regardless of the organization, you will have the ability to add multiple settings (and proctor caching machines) to the configuration.

17. Configure TestNav (2/2) • Identify the proctor caching machine. In the “Default Precaching Computer” section, enter a computer name, the computer’s IP address, and port information. • Provide the internal network IP address of the caching machine and the port number, which unless modified is 4480 for Pearson-supplied proctor caching. The IP address should be a static address to ensure students can access content during testing. Also note, the computer selected for proctor caching should not be a student’s testing device. • Check “Uses Pearson Precaching Software.” • For Response File Backup Locations, it is recommended that a Secondary Location be specified for Windows and Macintosh computers. The Secondary Location must be writeable by students and can be a network share on school network or a shared location on the local computer. • Press Create • A green success message will display after successful configuration. An error will appear if there are issues.

18. Proctor Cache/precache Once TestNav is configured and students are in sessions (ensure all PNP data is up-to-date), you can precache. • Recommended 1-2 weeks prior to testing. • Make sure all test sessions are created before the first test session begins. This will ensure that you cache all of the content needed. This feature requires the use of a Java applet, so the computer from which you perform the action must have Java installed and you must allow the Java applet to run in your browser in order for this to work.  • Go to Testing > Sessions • Search and select the session(s) set up to use proctor caching. • Open the task list and select Precaching Test Content and click Start. • Click Precache. • An information screen will appear to let you know that caching is in progress and the parameters being used. At the same time, the ProctorCache application will open. From that application you can view caching progress. See Use ProctorCache in the PearsonAccessnext Online User’s Guide for directions. This guide is found in PearsonAccessnext under Support > Documentation.

19. Update Proctor Cache If student tests are updated after you initially cache content but before testing actually begins, Pearson recommends refreshing cached content on the proctor caching computer 48 hours prior to the start of a test session. To update or refresh cached content, follow these steps: • From Testing > Sessions • Search and select the test session(s) that you want to update or refresh. • Open the task list and select Precaching Test Content and click Start. • Click Precache • This will open the ProctorCache application in a new window. From that application you can refresh downloaded content for that test, reload the content, or purge content from the cache.

20. Use System Check as a quick check • Use SystemCheck to: • Test Bandwidth Capacity of your environment. • Validate proctor caching machine is functional from lab environment. • Use SystemCheckTestNav 8 login credentials to validate devices. (turning off screen saver, proper screen size, turning off auto updates, antivirus updates, etc.) • Reference the SystemCheck and SystemCheck User Guide at http://parcc.pearson.com/technology-setup

21. Infrastructure Trials • Infrastructure trials are a dress rehearsal of testing for students, staff and technology • You’ll need to configure, precache, print tickets, etc., all the steps for live testing • If you encounter tech errors during an infrastructure trial, you can take time to fix them in a low-stakes environment, and prevent the issue during live testing • Infrastructure trials are administered using the Pearson Access Next training site (trng.pearsonaccessnext.com) • Find more details in the Infrastructure Trial Guide

22. Technology to consider in addition to devices • In addition to student devices, consider the following technology needs in your planning: • Devices for teachers to administer the test (no app or installation needed to run Pearson Access Next) • Mouse, keyboard recommended, depending on device and what students are used to using • Any external assistive technology needed for student accommodations* • Headphones are required for all ELA tests, and any student receiving a text-to-speech accommodation* • Calculators are provided in TestNav, but students needing calculators as an accommodation will need an external calculator* *may be provided by students

23. Troubleshooting During Testing (1/2) • Contact PARCC Customer Support with PARCC TestNav, precaching and PearsonAccess Next PARCC Customer Support1-888-493-9888 Monday – Friday: 6:30 am - 7:30 pm (EST) Live chat available at dc.pearsonaccessnext.com PARCC E-mail: parcc@support.pearson.com • TestNavError Codes and troubleshooting guide • Example: 1013, test content failed to load. The student should exit the test and login again. • Some of the most common errors come from the TestNavEarly Warning System. This system stops a test and displays an error if there are network connectivity issues or backup save issues that may put student responses at risk • For TestNav errors that require Pearson support, locate your student response file (SRF) and log file

24. Troubleshooting During Testing (2/2) • If there is an error you are unable to resolve, be sure to note the device the student tested on, and the location of the SRF and log file • If a technology problem lasts for more than 15 minutes or affects large numbers of students, file an incident report • Tech coordinators are allowed cell phones to get support on tech issues, but photographing test screens is a violation of test integrity, and tech coordinators should be mindful not to disrupt the test environment • Most tech issues will crop up in the first few days of testing, plan staffing accordingly • If a question is not answered/resolved by Pearson in a timely manner, alert OSSE so we can escalate the ticket

25. After Testing: Purge Proctor Cache After all testing is complete, purge cached test content. To purge cached content, follow these steps: • From Testing > Sessions • Search and select the test session(s) that you want to purge. • Open the task list and select Precaching Test Content and click Start. • Click View Status. This will open the ProctorCache application in a new window. • From that application you can refresh downloaded content for that test, reload the content, or purge content from the cache. • Depending on your browser setting, you may not see the View Status button. This failed due to a script that needs to execute that may be blocked. Please check your settings to allow the script, re-enter your information, and restart your connection. • To filter your list, enter search criteria and select a value from the drop-down list. Click Clear to reset your search criteria. • Select the test to purge, and click Purge. • The test content will then be purged.

26. Learn more and get assistance PARCC Customer Support1-888-493-9888 Monday - Friday, 6:30 am - 7:30 pm (EST) Live chat available at dc.pearsonaccessnext.com PARCC E-mail: parcc@support.pearson.com • Contact OSSE via OSSE Support Tool (OST) and at 202-304-3269 for policy questions, general guidance and to escalate Pearson tickets • PARCC resources: http://parcc.pearson.com/technology-setup/ • OSSE resources: http://osse.dc.gov/parcc/leas/2015-16resources