Copyright © 2015 Pearson Education, Inc. or its affiliate(s)

WebEx Tips Use the Webex chat feature to ask questions during the presentation. At the top of your screen, click the Webex toolbar. Click the chat bubble. Select Host as the recipient. Type your question in the field.

Agenda Online Resources Technology Setup Introduction
Computer-Based Testing Components Preparing for Testing TestNav 8 Desktop app vs/ web browser Proctor Caching Create a TestNav Configuration SystemCheck for TestNav Conducting an Infrastructure Trial PearsonAccessnext Questions – Reminder that this is a high-level overview, but there will be step-by-step instructions in the CBT TAM and PANext User Guide to assist users. This presentation will cover A brief overview of PearsonAccess Next Using online resources for information to prepare and administer assessments Preparing for testing and monitoring sessions We’ll end with contact information for our customer service team And if during this presentation you have questions, make a note and we’ll take time to answer questions at the end. This training is being recorded and will be made available as a PPT and recording after the 2nd session on Thursday.

Moving to PearsonAccessnext
The PearsonAccessnext online user guide can be found at The online user guide contains a “Moving to PearsonAccess Next” section. The Pearson Access Next online user guide contains a “Moving to PearsonAccess Next” section. This section outlines how each task is performed in the new user interface and where it was done previously. While you will be doing many of the same tasks you performed before in order to set up your online environment, this section identifies how to perform tasks, where it is located and compares it to the locations in PearsonAccess. The sample shown here illustrates the differences between the layouts and then breaks it down by topic and tasks.

Support Customer Support: Call Customer Support:

Technology Readiness Welcome to the Technology Readiness presentation. Before we begin, I would like to remind everyone that all lines have been muted to avoid audio interruption during the presentation. I will pause at the end of each section to answer questions via the chat box. Feel free to input your questions during the presentation, and I will pause to answer questions at the end of each section. At the end of the presentation, you will also receive contact information for Florida Customer Service, so if you forget to ask a question or think of a question after the presentation, you can contact Florida Customer Service for additional support. This training addresses the technical setup to prepare for online assessments and is provided for district technology staff.

Computer-based Testing Components
PearsonAccessnext Assessment administration portal Manage student data, test sessions, access reports TestNav 8 Student test delivery engine Early Warning System SystemCheck for TestNav Web-based tool for assessing readiness Computer-based testing components are comprised of PearsonAccess Next, TestNav 8, SystemCheck, and ProctorCache. PearsonAccess Next is a system that administrators will use to manage student data, set up and schedule computer-based tests, and manage test sessions. The site is role-based, and users can be prescribed specific roles that will control the functions they have access to, and what they can do in the site . [CLICK] TestNav 8 is the secure testing engine that students will use to interact with test items. In today’s presentation we will discuss the different methods to access TestNav, either using an installable or browser-based version, and we will discuss the various devices that you may use for online testing. Behind the scenes, an inner-component of TestNav, called the Early Warning System, maintains test security, and checks for connectivity or content issues. The Early Warning System maintains student responses and monitors the network connection. While a student is testing, the Early Warning System will record student responses in a local encrypted saved response file. After a few questions are answered, TestNav will bundle the answers into a packet and transmit them to our servers. TestNav will then wait for a handshake acknowledgement that verifies that we have successfully captured all of the responses on our side. This means that we control and verify the transmission of student responses to our servers, and this also gives the added benefit of students being able to resume where they left off in the case of a connectivity or network failure. It is also important to note that when students submit their final answers, TestNav will not completely finalize the student’s test until it has received confirmation that the responses have been captured on our side. We want to be absolutely sure that we have all of the student’s answers before a test can be submitted for scoring. [CLICK] SystemCheck is a tool that is used to determine system readiness. No installation is necessary; users simply visit the website with a testing workstation; there they can perform quick tests to verify that the workstation meets the minimum browser, OS, and Java requirements to run TestNav 8. Users can also perform a connectivity test that allows them to see if the student workstation can retrieve sample test content successfully. SystemCheck also helps determine how many students can test at the same time, which will help technology coordinators know how many students can test while using proctor caching. Later in the presentation, we will discuss how to use SystemCheck. This tool can be used to calculate bandwidth speeds. [CLICK] ProctorCache is Pearson supplied, free software that works with TestNav to reduce the overall bandwidth requirement for computer-based testing by pre-downloading the entire test content that your students need, and storing it locally in an encrypted format, allowing you to serve test content at local speeds versus Internet download speeds. The requirements are very flexible. This does not have to be installed on a server class operating system or very robust computer. In most cases, a single proctor cache machine can be used to service many students. If you have questions before we begin the next section, please take a moment to enter them into the chat box, and we will read and respond to your questions as they are received. ProctorCache Works with TestNav to reduce bandwidth requirements Technology Readiness, Proctor Caching, and SystemCheck

TestNav 8 First, we will discuss TestNav 8, the student test delivery platform.

Technology Readiness, Proctor Caching, and SystemCheck
TestNav 8 – Setup Two Setup Methods Installable Browser-based Download from the landing page or device app store Desktop, iPad, Android, and Chromebook Completely browser-based Requires Java 1.8 or higher Network Configuration Let’s talk about the setup details. [CLICK] There are two options for setting up TestNav. There is a TestNav Desktop app that can be installed by downloading the application directly from the downloads landing page. The TestNav Desktop app is supported for Windows, Mac, and Linux operating systems. The Installable TestNav 8 app is also available for Android, iPad, and Chromebook devices, and the application can be downloaded from the respective device app store. [CLICK] TestNav can also be accessed in browser-based mode for Windows and Mac workstations. This means there is no individual system configuration required, beyond confirming the system requirements, including Java, are met, and running SystemCheck on the images to validate they will launch TestNav. Note that the browser-based method is not available for Linux systems, so for Linux users, your only option is to use the TestNav Desktop installed method. [CLICK] Here are the URLs and ports that need to be set to allow TestNav to access. These configuration settings apply for all setup methods and all device types. Firewalls, content filters, spam filters, and any other routing or blocking systems should be set to allow access to the following: *.testnav.com: 80 – *.testnav.com: 443 *.thawte.com – *.pearsontestcontent.com google-analytics.com (optional) Technology Readiness, Proctor Caching, and SystemCheck

TestNav App Installers http://download.testnav.com
If your district is downloading the TestNav 8 app, it is accessible at If you are using a device that requires an application installation, or if you are planning to use the TestNav Desktop application for laptops and desktops, you can download the app or apps that you will need from this site, or you can go to the applicable device store for Chromebooks, iPads, and Android devices. We will talk more about these device types shortly. For now, if you are installing TestNav Desktop, there are options for Mac, Windows, and Linux. There are two options for Microsoft Window: .msi and .exe. The .msi file is optimized for network installation as a group and pushing out to multiple computers. The .exe file is for downloading onto individual computers. The Desktop installation generally only takes a few minutes on an individual computer; network installations will vary depending on your environment. Technology Readiness, Proctor Caching, and SystemCheck

TestNav 8 Support Site https://support.assessment.pearson.com/x/iQAqAQ
Includes: Requirements Setup instructions Troubleshooting Technical Bulletins Recently Updated tracks historical log of changes The TestNav 8 Support Site contains all of the information necessary to setup and manage your testing environment. This site is designed to provide instructions, video demonstrations, and links to important information for setting up your testing environment and troubleshooting any issues you may encounter. The site includes the most up-to-date system requirements, setup instructions, troubleshooting support, and technical bulletins. The site also contains a Recently Updated page to help you track historical changes applied to the site. Technology Readiness, Proctor Caching, and SystemCheck 12

TestNav 8 Getting Started & Demonstration
This site is a user-friendly informational site that contains hyperlinks to more detailed information indicated in blue. Technology Readiness, Proctor Caching, and SystemCheck

Windows, OS X, and Linux System Requirements
Mac OS X 10.7–10.10 Windows 7–Windows 8.1, 10 Linux: Fedora 21–22 and Ubuntu or 14.04 Most major browsers supported Internet Explorer 11+, Firefox 38+, Safari 6+ Version number is dependent on operating system Chrome browser no longer supported TestNav Desktop application provides installable solution Even though TestNav can be installed, the application still has a few minimum technology requirements. We will cover Windows, Mac OS X, and Linux now, and then discuss Chromebooks, iPads, and Android devices separately. [CLICK] Mac OSX, Windows, and Linux are supported; Mac OS X 10.7–10.10 and Windows 7–Windows 8.1 and Windows 10. Linux is supported on Fedora 21–22 and Ubuntu (pronounced oo-boon-too) or for the TestNav Desktop app only. Linux is only supported using the TestNav Desktop app. [CLICK] For browser-based TestNav, most major browsers are supported; the exact browser version will depend on the operating system being used. Please note, the Chrome browser is not supported due to its lack of support for the Java plug in. As a result, districts can choose to use the installable solution over browser-based if they do not want to use the alternative supported browsers available for browser-based TestNav. TestNav Desktop supports all item interaction types, tools, proctor caching, accessibility features, and accommodations as browser-based TestNav. Technology Readiness, Proctor Caching, and SystemCheck

Chromebook System Requirements
Hardware and software requirements Memory requirements Operating system No Java or browser dependencies Must use the Installable TestNav application for Chromebook and not a browser Before we go into the actual setup steps, let’s have a look at the system requirements. It’s important to note some highlights for the Chromebooks. Listed on the slide and also found on the TestNav 8 support pages are the minimum and recommended memory requirements. TestNav requires at least Chrome OS 44 or higher. There are no Java or browser requirements for Chromebooks, as students will use the TestNav 8 App to access their test content. It is important to note that TestNav cannot be launched using a browser on a Chromebook. Technology Readiness, Proctor Caching, and SystemCheck

Chromebooks – Setup Overview
Two Setup Methods Managed Chromebooks Unmanaged Chromebooks Set each device settings to keep local data to avoid losing in-transit student response files Before testing, enable Single App Kiosk mode by adjusting the Kiosk Settings After testing, disable Single App Kiosk mode by adjusting Kiosk Settings Steps have to be performed on each Chromebook Enable Single App Kiosk mode through Chrome browser Requires access to the administrator/owner account for device Device will be backed up to cloud storage and wiped if you do not have access to the administrator account for the device Now let’s move into the setup details. Chromebooks can either be managed or unmanaged, which presents us with two different setup methods. [CLICK] For managed devices, all of the setup steps will be performed through the central administration, so all Chromebooks in a domain can be configured at once. When using managed devices, there are two main steps you will need to complete – install the TestNav 8 App and set it to run in Single App Kiosk mode, and preserve the local data on the Chromebook to retain Saved Response File (SRF) and log files on the device. [CLICK] For unmanaged devices, the setup steps will have to be performed on each device individually. This requires access to the administrator account for the device. If you don’t have access to the administrator account, the Chromebook will need to be backed up to cloud storage and wiped clean before you can continue. After testing, it can be restored from the cloud. You will also need to enable the Single App Kiosk mode using the Chrome browser. Technology Readiness, Proctor Caching, and SystemCheck

iPad System Requirements
Hardware and software requirements Memory requirements Operating system No Java or browser dependencies Must use the Installable TestNav application for iPad and not a browser Now let’s look at iPads. Before we go into the actual setup steps, let’s have a look at the system requirements. It’s important to note some highlights for the iPad. Listed on the slide and also found on the TestNav 8 support pages are the minimum and recommended memory requirements. TestNav requires at least iOS 9 and higher. There are no Java or browser requirements for iPads, as students will use the TestNav 8 App to access their test content. Again, like Chromebooks, TestNav cannot be launched using a browser on an iPad. Technology Readiness, Proctor Caching, and SystemCheck

iPads – Setup Overview Apple Configurator Apple Profile Manager
Multiple Setup Methods Apple Configurator Apple Profile Manager Install TestNav 8 app Enable Supervised mode Lock iPad to TestNav 8 app Install TestNav 8 app Create testing profile Push testing profile to devices wirelessly Guided Access Autonomous Single App Mode - ASAM Install TestNav 8 app Configure each iPad for Guided Access Lock iPad to TestNav 8 app Now let’s move into the setup details. As we talked about before, iPads have several setup options. [CLICK] Administrators can use the Apple Configurator to manage multiple devices at once. Using this method, you will enable Supervised mode on the iPad and then lock the iPad to the TestNav 8 application for testing. [CLICK] Profile Manager is Apple's Mobile Device Management or MDM solution for iOS devices. You can select the TestNav app from the Lock to App menu and push the profile to supervised devices. [CLICK] Individual iPad devices can be configured using Guided Access. This set of steps will be done on each iPad to secure the device and lock it to the TestNav 8 app. [CLICK] Autonomous Single App Mode allows the Single App mode to be turned on dynamically when the TestNav 8 application is launched. This method requires both a Mobile Device Manager (MDM) and an iPad that is in Supervised mode. Install TestNav 8 app Enable Supervised mode Use MDM to enable ASAM mode TestNav 8 initiates Single App mode Technology Readiness, Proctor Caching, and SystemCheck

Android Device System Requirements
Hardware and software requirements Memory requirements Operating system No Java or browser dependencies Must use the Installable TestNav application for Android and not a browser Now l’d like to discuss Android devices. Before we go into the actual setup steps, let’s look at the system requirements. Listed on the page and also found on the TestNav 8 support pages are the minimum and recommended memory requirements, and TestNav requires at least Android 5.0, Lollipop, or higher. Again like Chromebooks and iPads, there are no Java or browser requirements for Android devices, as students will use the TestNav 8 App to access the test content, and TestNav cannot be accessed from a browser on an Android tablet. Technology Readiness, Proctor Caching, and SystemCheck

Android Devices – Setup Overview
Two Setup Methods Google Play for Education Mobile Device Manager (MDM) Install app using your Google Play for Education account Add names or addresses of those you want to access TestNav Can also use Google Group or contact group Google tips: edu/play/answer/ TestNav app can be installed using an MDM that supports Device Owner Now let’s move into the setup details. Android devices can be installed with a Google Play for Education account, or by using a mobile device manager that supports Device Owner. [CLICK] To install on Android devices, you can use your Google Play for Education account to download the app. You will need to add the names or addresses of those you want to access the TestNav app; alternatively, you can use Google Group addresses or a contact group. You can find tips for sending content to students on the Google support site. [CLICK] You also have the ability to install the TestNav app using a mobile device management (or MDM) system that supports Device Owner. Technology Readiness, Proctor Caching, and SystemCheck

TestNav 8 Browser-based Software Requirements and Dependencies
All browsers: Java 1.8 required Enable pop-ups for TestNav 1024 x 768 screen resolution Read/write access to home directory Firefox and IE: Create javaw.exe exception in Windows firewall Firefox (Windows 7): Disable Skype plugins Browser-based software requirements and other dependencies for TestNav 8 include the following, regardless of the browser used: Java 1.8 must be installed on Windows and Mac OS X computers Pop-ups must be allowed in the browser for Pearson sites – this allows TestNav 8 to go into full-screen mode There is a minimum screen resolution of 1024 x 768 While the test is running, TestNav will write to an encrypted temporary file and could create log files on the local student machine. For that reason, students must have read/write access to the home directory. Later in today’s presentation, we will discuss the process of how TestNav writes log files and saves temporary student response files during testing, and this is why students need to have the appropriate permissions to allow this process to work. For Firefox and Internet Explorer, you also need to create a javaw.exe exception in the Windows firewall. And with Firefox on a Windows 7 computer, you must disable any Skype plugins. Technology Readiness, Proctor Caching, and SystemCheck

Wireless Testing – Best Practices
Wireless access points – more is better Limit number of computers per wireless access point Distance – closer is better Limit obstructions Use SystemCheck to verify that you have the appropriate amount of bandwidth for online testing Wireless testing is acceptable for computer-based testing. Schools can test both wired and wireless at the same time. These are some best practices when testing wirelessly: [CLICK] Ensure sufficient wireless access points and [CLICK] limit the number of computers per wireless access point for better performance. [CLICK] Computers located closer to wireless access points perform better than those that are farther away. [CLICK] Obstructions, such as walls and equipment, between testing workstations and wireless access points can disrupt connection and negatively affect performance. [CLICK] SystemCheck can be used to assess the number of students that can be tested using a wireless network. [CLICK] Set up a small number of workstations to measure performance on a wireless network before setting up a large number of workstations. If you have questions before we begin the next section, please take a moment to enter them into the chat box, and we will read and respond to your questions as they are received. Test performance before scaling Technology Readiness Overview

ProctorCache Next, we will cover ProctorCache, the Pearson-supplied software to help you manage your bandwidth usage.

ProctorCache Overview
ProctorCache is Pearson- supplied software that is used in conjunction with TestNav to reduce bandwidth requirements and accelerate the delivery of test content. Proctor caching: allows you to pre-cache test content to your local network before a test; reduces the burden on your Internet service provider (ISP) by eliminating redundancy in requests for test content; and stores an encrypted local copy of all pre-cached tests. Proctor caching provides many benefits and is required. ProctorCache is Pearson-supplied software that is used in conjunction with TestNav to reduce bandwidth requirements and accelerate the delivery of test content. [CLICK] So what can you do with ProctorCache? You can pre-cache content before the test to your local network. You can reduce or eliminate redundant downloads of test content, which will reduce the burden on your Internet service provider (ISP). And you can store an encrypted local copy of all pre-cached tests and serve them at LAN speeds to students. [CLICK] Proctor caching provides many benefits and is required. Technology Readiness, Proctor Caching, and SystemCheck

ProctorCache System Requirements
Runs on Windows and Mac OS X Utilizes TCP Ports 80, 443, 4480, and 4481 Requires a fixed internal IP address Use SystemCheck to test connectivity Devices and proctor caching Students testing on iPads, Chromebooks, and Android tablets can access cached content from a ProctorCache machine But, these devices cannot be used as ProctorCache machines Links to software downloads are available at: The ProctorCache software must be installed, and it has a set of minimum requirements. The requirements are not robust, which gives districts flexibility on what machines they use for proctor caching. It does not require an underlying server-based operating system, and can run on desktop class hardware and operating system. Also note, that when choosing a computer for proctor caching, you will get the best performance from your best performing workstation or server, depending on what you may have available. Even though there are minimum system requirements, you should choose a computer that has the best processing speed and most memory of those computers you have available since you will have many student computers reaching out to the proctor caching machine to access the locally stored test content. Proctor caching can run on both Windows and Mac OS X operating systems. [Macintosh OS X 10.7, 10.8, 10.9, or or Windows 7, Windows 8, Windows Server 2008, or Windows Server 2012.] Proctor caching uses TCP Ports 80 and 443 for communication between the proctor caching machine and the Pearson servers, and ports 4480 and 4481 for communication between testing workstations and the proctor caching machine. Please note that port 4481 is new for proctor caching this year. This means TCP ports 80, 443, 4480, and 4481 must be opened. 80 and 443 are also listed in the URL and ports configuration. You do not have to perform this step twice. It is possible to set custom ports for ProctorCache; in this case, those specific ports should be opened and not 4480 and 4481. Because testing workstations must be set to a pre-determined network location for the proctor caching machine, proctor caching requires a fixed internal IP address. Those districts which require internet traffic to pass through an upstream proxy server will have to configure proctor caching to point to their proxy server. For details on setting up an upstream proxy, refer to the “Upstream Proxy Configuration” on the Set up and Use ProctorCache page. After ProctorCache is installed, SystemCheck can be used to test connectivity and throughput between the student workstations and the proctor caching machine. Also, students testing on iPads, Chromebooks and Android tablets can access cached content from a ProctorCache machine, but these devices cannot be used as ProctorCache machines. Technology Readiness, Proctor Caching, and SystemCheck

Proctor Caching Diagram
This diagram illustrates two network scenarios. The scenario on the left illustrates a network setup that does not use proctor caching. Each student is downloading a unique copy of the test content directly from the Pearson servers. The diagram shows that redundant test copies are being downloaded simultaneously over the district’s ISP connection, while students are waiting to test. This heavy use of bandwidth not only affects how quickly the test loads for students, but also the available bandwidth for all other internet-related activities. The right side of the diagram shows the network traffic for a test environment successfully using proctor caching. The test content is pre-cached once in an encrypted format to a local workstation designated in the TestNav configuration setup as the proctor caching computer. Students that are assigned to the proctor caching computer will locally access the test content without utilizing your Internet bandwidth, thus decreasing overall network traffic for your district. The closer the configured computers are to the proctor caching workstation, the faster the delivery of content. Districts have the flexibility to decide where to implement proctor caching in the network environment. Based on local network considerations, districts can implement proctor caching machines at the district, school, or classroom-level. If implementing at a district-level, we recommend considering the added complexity of the connection between the school and the central location. If proctor caching computers are housed at the school where students are testing, then you do not have to be concerned about an outside connection. Without ProctorCache, each testing computer must individually connect across the Internet to download test content. With ProctorCache, test content is mirrored on a local computer from which the testing computers download test content. Technology Readiness, Proctor Caching, and SystemCheck

ProctorCache – Setup Download installer ProctorCache installers can be found on the downloads page: Run installer and start service Service is normally started by default Shortcuts exist to start or stop the service if necessary Verify service is running Installing and verifying the ProctorCache service is very simple and only takes a few minutes. First, technology coordinators will download the ProctorCache installer for their system. [CLICK] Run the installer; the InstallAnywhere wizard will prompt you through the minimal installation process. After the installation is complete, start the service. This is normally started by default, but there are shortcuts available to start or stop the service, if needed. [CLICK] Next, verify that the service is running by visiting the ProctorCache Diagnostics page; we will cover the Diagnostics page in more detail shortly. The ProctorCache software is only installed on the designated proctor caching machine and not on each of the student workstations. Also, the content only needs to be pre-cached once during the test window. You can purge the content after the test window has ended and directions for how to purge test content are available on the TestNav 8 Support page on the “Set Up and Use ProctorCache” page. Open ProctorCache Diagnostics screen Technology Readiness, Proctor Caching, and SystemCheck

ProctorCache Diagnostics Screen
IP Address>:4480 Tests: Provides information about test content and caching status Content Details displays status of individual test items Clients: Displays clients by IP address that have connected to TestNav Client Details displays details by computer Settings: Allows you to set a custom password to refresh, reload, or purge cached content You can verify the status of the cached content by using the Proctor Caching Diagnostics page. Depending on your installation preferences, you can access the diagnostics screen from your start menu on Windows machines, finder on a Mac, or through desktop shortcuts. [CLICK] You can also directly navigate to the ProctorCache diagnostics page by typing then the Static IP address of the caching machine followed by a colon and the port 4480 in your browser. Select Enter to view the proctor caching diagnostics page. [CLICK] You will see three tabs: [CLICK] Select the Tests tab for information about test content and caching status. [CLICK] Selecting the Clients tab will allow you to monitor client connectivity. [CLICK] Finally, the Settings tab allows you to set a custom password in order to refresh, reload, or purge cached content. Technology Readiness, Proctor Caching, and SystemCheck

Diagnostics Screen – Tests Tab
Content is displayed at Test and Form levels Functionality to Refresh, Reload or Purge selected content Clicking on a test name displays the Test Details screen, which shows cached content by item On the Tests Tab, you will see content displayed at the Test and Form level. Please note, the screen capture displayed is for training purposes and does not represent actual Florida content. During the test window, the content downloaded will be identified with the appropriate Florida assessment name. [CLICK] Functionality is available to Refresh, Reload, or Purge selected test content if necessary, and requires a password. The initial password is available in the Proctor Caching User Guide to protect against unauthorized deletion of cached content. We will cover how to change the password, if desired, shortly. [CLICK] You will also see status indicators for each row of cached test content. [CLICK] Clicking on a test name will display the Test Details screen, which displays individual items cached for the test. There, status indicators will appear next to each item. Technology Readiness, Proctor Caching, and SystemCheck

Tests Tab Status OK – Content is successfully cached Not Loaded – Content is not cached Waiting… – Content is waiting to be loaded Loading… – Content is currently loading Failed to load content – There was a failure to load content MD5 Check Invalid – MD5 comparison could not be completed MD5 Mismatch – MD5 comparison was completed but files did not match An OK status means the content is successfully cached. [CLICK] The yellow status indicators usually appear when the content is in the process of being cached. Not Loaded means the content is not cached Waiting… means the content is in the queue, waiting to be loaded and Loading… means the content is currently loading [CLICK] Red status indicators indicate problems with cached content. Failed to load content means there was a failure to load content. Proctor caching also performs an MD5 check once an item has been cached to compare the test content on the Pearson servers with the cached item. The MD5 check should show that the items are identical. MD5 Check Invalid means the MD5 comparison could not be completed successfully. MD5 Mismatch means the MD5 comparison was completed but the files did not match. In general, any status in red is a critical problem. Any content with a red status should be checked and reloaded. If the problem is not resolved, contact Florida Customer Service for technical assistance. Note: In general, any status in red is a critical problem. Any content with a red status should be checked and reloaded. If the problem is not resolved, contact Florida Customer Service. Technology Readiness, Proctor Caching, and SystemCheck

Diagnostics Screen – Clients Tab
The Clients tab provides visibility to which testing workstations have requested test content from proctor caching. [CLICK] Each testing workstation on the Clients tab also has a status indicator. [CLICK] Clicking on an IP address or name of a computer will show the details of the computer that connected to the proctor cache machine to fetch test content. Clients that have connected to TestNav are listed by IP address Clicking on a computer displays a details screen, which shows information regarding a particular computer Technology Readiness, Proctor Caching, and SystemCheck

Clients Tab Status OK – Client is active Idle – 5 to 30 minutes since client was active Long Idle – 30 minutes to 12 hours since client was active Note: Clients are removed after 12 hours of inactivity. An OK status means the client is currently active [CLICK] The yellow status indicators appear when the clients have gone idle. Idle means 5 to 30 minutes have passed since the client was last active, such as when a student takes a bathroom break. Long Idle means 30 minutes to 12 hours have passed since the client was last active, such as a lunch break. Please note, clients are removed after 12 hours of inactivity, but will reappear on the list once the test content is requested again. Technology Readiness, Proctor Caching, and SystemCheck

Diagnostics Screen – Settings Tab
Allows setting a custom ProctorCache password Can only be accessed when visiting the Diagnostics screen from the proctor caching machine The Settings tab allows technology coordinators to set a custom ProctorCache password to perform the tasks of refreshing, reloading, or purging cached content. The default password is in the Proctor Caching User Guide. You can change the default password at any time, but only from the Diagnostics screen from the proctor caching machine. [CLICK] Enter the current password and then provide a new password and confirm your entry. Then click Submit to save the password. If you forget your password, the administrator can reset it following the directions in the Proctor Caching User Guide. If you have questions before we begin the next section, please take a moment to enter them into the chat box, and we will read and respond to your questions as they are received. Technology Readiness, Proctor Caching, and SystemCheck

Create a TestNav Configuration
Now it is time to take a look at building a TestNav Configuration in PearsonAccessnext to indicate the IP addresses of your proctor caching work stations and your save locations for SRF files. The TestNav Configuration is linked to the online sessions. During the login process, information contained in the TestNav Configuration is passed to the student workstation so that the workstation knows where to retrieve cached content and, for students testing on laptops and desktops, where to save the student response files.

Configure TestNav Setup
Enter the Computer Name, IP Address, Port information, and check “Uses Pearson Precaching Software.” Then specify student response file backup locations, and click Create. The Configuration for each Organization can have multiple Precaching Computers specified, if desired. Click Add to enter the details for additional servers. In PearsonAccessNext you can identify the Proctor Caching computer or computers you plan to use for testing. [CLICK] In the “Default Precaching Computer” section, enter a computer name, the computer’s IP address, and port information. The computer name will be the name that displays when selecting a Caching machine during the step to create a test session. Next, you will provide the internal static IP address of the caching machine and use the port number of 4480 for Pearson-supplied Proctor Caching. The default setting “Uses Pearson Precaching Software” is selected. You can deselect this option if you have a third party caching solution other than the proctor caching software supplied by Pearson and make sure the port is the correct port for the caching solution you will be using. [CLICK] Next, you can specify locations for storing saved response files. For Response File Backup Locations, it is recommended that a Secondary Location be specified for Windows and Mac computers. This Secondary Location must have create/modify/read/write/delete access for students and it can be a network share on school network or a shared location on the local computer. [CLICK] Also note that you can select the Test Connection button to test your connection to the specified caching machine. This is helpful to ensure that you have entered the correct IP address and that the caching machine is up and running the proctor caching software.

Early Warning System Next, we will discuss the Early Warning System, the integrated functionality that monitors network connection and student response data submission.

Early Warning System (EWS)
The Early Warning System (EWS) is integrated functionality in TestNav that provides additional fail-safes in the event of unexpected network disruptions during computer-based testing. The Early Warning System (EWS) is integrated functionality in TestNav that runs silently in the background and will alert you to any issues that arise during the test administration, such as an interruption in network connectivity or other applications attempting to take control of the desktop. Early Warning System notifications often involve IT staff, so it is important for technical staff, as well as school assessment coordinators and test administrators, to have an idea of how it works, and what will trigger an on-screen message. Technology Readiness Overview

Saved Response File (SRF)
EWS writes continuously in the background to the saved response file (SRF). A combination of the test ticket ID and the test session is used to uniquely identify an SRF. The SRF has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. Uploading of response data is continuous. If an upload to the Pearson servers fails, student responses continue to be saved locally while TestNav cycles and attempts another upload. If the response data upload is successful, TestNav creates a new empty SRF and begins the process again. TestNav only deletes an SRF once it is successfully uploaded to the Pearson servers. TestNav can identify the correct SRF if a test is successfully resumed. Only the SRF from the student’s last test attempt can be used when the student resumes a test. [CLICK] The Early Warning System writes continuously in the background to the student response file (SRF). Some districts may be concerned about students overwriting each other’s files, but TestNav ensures this will not happen by using a unique file name for each student’s test attempt. [CLICK] A combination of the test ticket ID and the test session is used to uniquely identify an SRF. [CLICK] The SRF has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. This means that TestNav does not upload each individual response immediately, but writes responses to the SRF until it has a batch of responses to upload. [CLICK] The uploading of response data is continuous. If an upload to the Pearson servers fails, student responses will continue to be saved locally. TestNav will continue to cycle and attempt another upload. [CLICK] If the data upload is successful, TestNav will create a new empty SRF and begin the process again. TestNav will only delete an SRF once it has been successfully uploaded to the Pearson servers. [CLICK] TestNav uses the student's unique login information to identify the correct SRF if a test is successfully resumed. [CLICK] TestNav will only use the SRF from the student’s last test attempt when a student resumes a test. Technology Readiness Overview

Early Warning System – Triggers
The following will result in Test Proctor – Click Here notification Problems writing to save location: EWS will trigger if… student does have read/write access to save location. TestNav cannot locate the save location. Problems downloading test content: TestNav cannot connect to proctor caching workstation to retrieve test content; or student workstation is no longer connected to the Internet. Problems with saved response files (SRF): the SRF file is moved while the student is testing and TestNav can no longer locate the active SRF file. an aggressive content filter corrupts the save response file. a technology coordinator attempts to load an incorrect save response file for the student. Now let’s review the specific events that trigger the Early Warning System. We’ll touch on each of the triggers briefly. TestNav determines that the Saved Response File location is not viable when: - students do not have the proper read/write access to either of the designated save locations - or TestNav cannot locate the save location. If save location is on a network drive and the student is not connected to Internet, TestNav cannot launch the test. TestNav may be unable to download portions of the test. - If TestNav cannot connect to a proctor caching workstation to retrieve test content. or a student workstation is no longer connected to the Internet while the student is testing and has reached the last item previously downloaded when the student was connected to the Internet. TestNav is unable to upload student responses to Pearson. - If the SRF file is moved while the student is testing and TestNav can no longer locate the active SRF file. - If an aggressive content filter corrupts the saved response file. Some content filters are very aggressive in filtering data, such as Lightspeed. To avoid this error message, you need to include the static IP address of your proctor caching workstation in your content filter’s exception list to allow full pass through without data corruption. If you have any questions about this process, please contact the support desk. Contact information for Florida Customer Service will be provided at the end of today’s presentation. - If a technology coordinator attempts to load an incorrect saved response file for the student. TestNav keeps track of the student’s current SRF file so you cannot load a previously stored SRF for the student or any other student’s SRF using the current login credentials. Technology Readiness Overview

SystemCheck for TestNav 8
Next, we will discuss the SystemCheck tool that you will use to verify your device and bandwidth readiness.

SystemCheck Overview SystemCheck: validates testing workstations meet the minimum system requirements needed to run TestNav 8; provides the ability to run bandwidth speed checks to help plan for online testing capacity; and estimates the number of concurrent testers that could be supported at the time the check is performed. Florida Customer Service may also use SystemCheck results to assist customers in trouble shooting. SystemCheck was developed to help you prepare for online testing requirements in two significant areas – student workstations and Internet bandwidth. This allows you to make any necessary updates prior to testing windows. SystemCheck validates testing workstations meet the minimum system requirements needed to run TestNav 8 by checking the browser, Java version, and operating system for the browser-based method of TestNav and checks the operating system for TestNav Desktop. On a Chromebook or tablet device, SystemCheck will only verify if the Operating System meets the minimum system requirements. SystemCheck helps you identify computers that may need updates in order to be fully ready for computer-based testing. Additionally, it helps you plan for online testing with bandwidth speed checks. To gather realistic results, speed checks should be run from a student testing workstation on the same day of the week/time of day that you anticipate performing online testing. These results enable SystemCheck to estimate the number of concurrent testers that can be supported. Florida Customer Service may also use SystemCheck results to assist in trouble shooting. At the end of today’s presentation, we will talk about where you can find additional resources for using “SystemCheck for TestNav.” Technology Readiness, Proctor Caching, and SystemCheck

Accessing SystemCheck
SystemCheck is an online tool which can be accessed at systemcheck.fl.testnav.com. You do not need to install any special software to use SystemCheck. However, SystemCheck is browser-based and relies on the Java plugin, so you will need to have Java installed when running SystemCheck on a traditional workstation. When you visit the site, you will be asked to accept and run a Java applet. Supported Java versions are listed on the TestNav 8 system requirements page. Launch SystemCheck at Technology Readiness, Proctor Caching, and SystemCheck

SystemCheck – Check Your System
Validates system requirements are met on testing workstations Checks OS only on mobile devices Provides steps to verify whether TestNav can run on the workstation To check your student workstation, visit SystemCheck from a browser on the workstation that you want to check. [CLICK] On the Check Your System Tab, select the Start button. The test will begin, verifying that the workstation meets the minimum Browser, Java, and Operating System requirements for the browser-based method of TestNav and the operating system only for TestNav desktop. On a Chromebook or tablet, SystemCheck will only verify if the Operating System meets the minimum system requirements. [CLICK] If all of the checks pass, you will see a green checkmark and a Passed indicator next to the message for each TestNav launch method. You will also see checkmarks next to each item that the test has checked for both TestNav methods. This will provide you with system requirement information for both methods of accessing TestNav for desktops and laptops regardless of which version you plan to use for online testing. [CLICK] The specific items that were detected on the machine will appear in the Results section. If any of the tested items did not pass, you will see a red X next to the line that did not pass, and the Results column will list what was detected on the workstation, and what the minimum requirement is. This will help you to identify any gaps in individual system readiness and assist you in addressing them before participating in the live operational test. Technology Readiness, Proctor Caching, and SystemCheck

Check Your System Tablets and Chromebooks
Here is an example of running SystemCheck on a Chromebook. You can see that the only available option is to check the OS to confirm it meets the system requirements. This same style of messaging will be displayed for iPads and Android tablets since, like the Chromebook, these devices utilize the installable method of accessing TestNav, and the installed application includes the appropriate Java and browser versions within the application. On a tablet or Chromebook, only the OS is checked Technology Readiness, Proctor Caching, and SystemCheck

Check Your System App Check in TestNav apps
You may also use the new App Check functionality in the new TestNav apps. By clicking on App Check TestNav will quickly check the device to determine if there is a condition which prevents TestNav from delivering a secure online test. App Check will check the device to determine if it can be secured for online testing Technology Readiness, Proctor Caching, and SystemCheck

Check Your System- TestNav Verification
One more step that you can take to check the readiness of the student workstation is Verification. [CLICK] On the Check Your System tab, beneath the “Checks Performed” area, you will see a section titled “Verification.” [CLICK] By following these steps, you can launch a sample test in TestNav to verify that it will run on the student workstation. To test your connection for browser-based access to TestNav, go to in your browser and enter the supplied login information, which is “username” for the username and “password” for the password. Select “Sign In” and then “Start Test Now.” If you see the congratulations screen, you have correctly configured TestNav on the tested workstation. For mobile devices and installed TestNav Desktop, launch the TestNav application after installation and begin on step 3 to launch the congratulations confirmation test. Provides steps to verify whether TestNav can run on the workstation Technology Readiness, Proctor Caching, and SystemCheck

SystemCheck – Testing Capacity
Bandwidth testing for Internet and proctor caching connections Volume estimates for capacity planning Click Add Caching Computer to add your potential proctor caching machine for a local network bandwidth test The Testing Capacity tab will allow you to perform a real time speed check between the workstation and the Pearson servers. This provides an assessment of the data transfer speeds and will return an estimate of the number of simultaneous testers that could be supported at the time that the test was conducted. Keep in mind that this result is an estimate and it might not represent the actual transfer speeds during student testing, especially if network conditions will be significantly different. [CLICK] By default, this test is going to check the connection between the student workstation that you are running the test on, and the Pearson servers. You can see this by the “Direct to Pearson” connection that is listed in the Server/Computer column. [CLICK] You can also model a network that includes one or more proctor cache computers. This will simulate the connection between the workstation and the proctor cache machine and provide you with a speed test and student estimation counts for that connection. [CLICK] To add a proctor cache computer, install the proctor cache software if you haven’t done so already, and select the Add Caching Computer button. You will be prompted to enter the information for the proctor cache computer you would like to test. [CLICK] Once you have entered that information, the proctor cache computer will appear at the bottom of the screen in the list of connections to be tested. This process can be completed multiple times if you would like to test the connection to multiple proctor cache computers. Technology Readiness, Proctor Caching, and SystemCheck

SystemCheck – Testing Capacity
To begin the speed check, click on the Testing Capacity tab, and then [CLICK] click Start. [CLICK] If one or more of the connections fail, or the test is stopped before it has completed, you will see a large red X towards the top of the screen, and a smaller x next to the connection that failed. [CLICK] On the row of the connection that failed, you can click the I icon next to “Connection Error” to see more details about why the connection failed. [CLICK] In most cases, your connections will be successful and you will see a green check and the message “Test Complete”. [CLICK] Based on this bandwidth test, you will be provided with an estimated testing capacity. This is calculated using the download/upload speeds and the average test size selected from the drop-down menu. This will show you the benefits of using proctor caching. If you add or remove any proctor cache machines, you can run the test again by clicking the “Start” button. SystemCheck will provide you with the necessary speed check results. The calculation is based on an algorithm using a sample data packet so it does not consume a large amount of bandwidth while processing. SystemCheck should be run during typical testing times to get the best simulation of the testing capacity estimates. Just like on the Check Your System tab, a print function is also available if you would like to print the results of the test. If you have questions before we begin the next section, please take a moment to enter them into the chat box, and we will read and respond to your questions as they are received. Tests bandwidth between the workstation and Pearson servers Click Add Caching Computer to add your potential proctor caching machine for a local network bandwidth test Speed test does not require high bandwidth consumption to run and should be run during typical testing times to get the best results Technology Readiness, Proctor Caching, and SystemCheck

PearsonAccess Next Now, we will discuss PearsonAccess Next, the new management system Florida will begin using for Spring 2016 Pearson testing.

Training Center Training Center URL: The Training center will be used for the Infrastructure Trial tasks to assess your readiness Training center – brown theme Operational site – blue theme You can access the Training Center directly through the above URL or by accessing the link on the operational site PearsonAccess Next includes both the ‘Live’ Production site and the Training Center Site. The Training center allows you to do hands-on practice without using “live” data. Encourage staff to use this site to practice learning tasks needed to administer tests.

What is an Infrastructure Trial?
An Infrastructure Trial is a “dress rehearsal” of a computer-based assessment. It does not use real student information. This is a low-stakes, dry run for final confirmation that: TestNav is configured correctly Devices can successfully run TestNav Network will bear the full load Participating staff know what to do for an online assessment What is an Infrastructure Trial? An Infrastructure Trial is a local “dress rehearsal” of a computer-based assessment. The local infrastructure trial enables you to prepare for spring online testing. Unlike a live assessment, you will not use real student information; instead “dummy” student information is used. During this low-stakes, dry run, you will confirm that: TestNav is configured correctly Devices can successfully run TestNav Network will bear the full load Participating staff know what to do for an online assessment An Infrastructure Trial provides an opportunity to review your device, network, and staff readiness in a low-stakes assessment and most importantly, has minimal impact on students. Performing an Infrastructure Trial helps you prepare for online testing. If you have questions before we begin the next section, please take a moment to enter them into the chat box, and we will read and respond to your questions as they are received. Technology Readiness, Proctor Caching, and SystemCheck

Quick Overview Web-based Comprehensive user interface
Responsive design PearsonAccessnext is a web-based technology platform used to manage student data, paper and online test delivery, user roles and permissions, and scoring and reporting services. With PearsonAccessnext you can perform all your test administration duties, from ordering materials and submitting student data to setting up online tests and viewing student results. Functionality between the versions of PearsonAccess is similar, however the latest version enables assessments to be delivered via a comprehensive, all inclusive user interface. It is one interface that all actions can be completed from. It uses responsive design principles making the interface flexible, efficient, intuitive and scalable on both desktops and tablets. PearsonAccess Next is ready for Next Generation – it’s mobile ready and is Cloud hosted.

PearsonAccess Next User Guide
The PearsonAccess Next User Guide is a generic guide that will assist users in learning the functionalities of PearsonAccess Next. The Test Administration Manual will still be the best location to find communications from FDOE for the latest policy and instructions for PearsonAccess Next for Florida users.

Performing Tasks Set-up and Manage Users (Pearson will import current user accounts) Create and Manage Student Records Configure TestNav Create and Manage Test Sessions Start and Monitor Online Tests Generally tasks are performed in chronological order and set-up workflow does not change. However, steps will need to be completed for each test administration. Today we will briefly navigate through the system, highlighting where to go to add new students (for students that were not included in the PreID file), how to configure TestNav after ProctorCache has been set up, as well as provide information on creating test sessions, starting and monitoring test sessions.

The Layout The menu bar contains a return to home page (by clicking on logo). Changes to the color of the flag indicate system warnings or errors to be resolved, the next three areas indicate: the test administration, your organization and user icon to view your account details. It is important you are aware of which test administration and organization you are working in before you begin performing tasks. Also note the color distinctions between the “live” and “training center” sites. Live site has a blue theme, and Training Center uses a brown theme. The layout contains two menu options for selecting tasks. The contents within the menus are identical. Whether you select a task from the ribbon dropdown or the center section, you will be taken to the task page. Note: Some features are only available to some user accounts depending on your access level and some are only available during a specific window of time.

Navigating Set-up tasks – these are the initial preparation tasks such as creating users, students, entering test configurations, etc. Testing tasks – this area is where you will manage testing. Like creating or editing test sessions, monitoring students in sessions, etc. Reports – operational reports are on pre-designed templates. Published reports are available here. Mention Related Links: PANext User Guide FAQs System Status Knowledge Base Avocet

Support Page - Resources
The Support page has two options, Resources and Support Requests. The Resources option allows you to search for support topics based on your need. You can also use the filters on the left to search for resources in a specific area or administration.

Creating Students

Create/Edit Students The Create / Edit Students functionality will walk you through the steps of creating, registering, assigning tests, adding classes and moving the student into a session. This process is the same as the New Student Wizard process in PearsonAccess Now. (Click) Registering students through PearsonAccessnext requires you to complete the following steps: Create a Student Confirm Enrollment Register a Student Manage Student Tests Manage Classes (if using classes to organize students) Setup tasks must be completed before students can test, including enrollment, registration, test assignments and, for some testing programs, class assignments.

Creating Test Sessions

Creating Test Sessions
To create test sessions, go to the Testing tab and click Sessions. From the Select Tasks pull-down menu select Create/Edit Sessions and click Start. Sessions are automatically created during the PreID upload until the deadline date specified for the administration.

Managing Test Sessions

Add, Remove or Move When test sessions are created in PearsonAccessnext, you can select tasks to add students to sessions, remove students from sessions and move students between sessions. To make changes to existing test sessions, you can select Add, Remove or Move students using the tasks within Students in Sessions. Example of this could be for make-up sessions – moving a student to a different session or if you need to add a new student to a session.

Adding a Student to a Test Session
(Animations) From Testing > Students in Sessions, search to find the student(s) you want to add or click the down arrow next to the Search button to reveal and select the option to show all results. Select the student(s) you want to add.

Monitoring Test Sessions

Sessions To monitor students currently testing in sessions, you will have to choose which sessions to monitor first Select Testing>Sessions. Click the down arrow next to the Search button to reveal and select the option to show all results.

Sessions Cont. Select the session(s) you want to view or edit.
Go back to Select Tasks>Click Show Students in Sessions

Sessions Cont. From here you can see the students in the session you chose and the test status they are currently in.

Students in Sessions (Animations) Click once:
In the Students in Sessions screen you can click on the ADD field to add more sessions to the Session List. This will allow you to manage multiple sessions and switch between them easily. You can also go back to “Sessions” to view and select one or more sessions you would like to view. Click twice then read: When multiple sessions are added to the Session List, you can click Combined View to display all session details on one page. This allows you to easily monitor students and to start and stop all sessions at once. Click once then read: You can also search for Students using the Search function. Note the filter for Find Students is set to search for students in the selected sessions. You can switch this filter to search for other students within the administration.

Starting Test Sessions
This slide demonstrates the combined session view where you can start multiple sessions at once. Once a session is started this button will change to a red Stop button. Do not stop a session until all students in that session have submitted their tests!

Monitoring Test Sessions – Students in Sessions
When students begin testing you can monitor how they are progressing by using the status information. Test sessions can be monitored individually or through a combined view of multiple test sessions

Resuming Student Tests
(Animations) Click Once: If a student is exited from the test and needs to resume, the Test Administrator can use the Resume Students Tests task to resume the student’s test. Be sure to first select the student’s name then select Resume Student Tests. Once resumed a student can log in with their ticket to complete the test. In the Students in Sessions screen, the student’s status will update to an orange indicator, which shows that they are in Resumed status.

Download Resources The Download Resources dropdown is where you can find seal code information and can print student authorization tickets in different formats. Note you can only Download Resources for a single session. There are 4 different views for the Student Authorization Tickets: Grid View, List View, Detail View 4 per page and Detail View 1 per page. The Refresh button allows you to refresh content on the session screen.

After Testing

Reports Operational reports
Pre-designed report templates that include information on test-related materials You may download a Security Checklist or Session Roster report from PearsonAccess. All reports have all been moved to the Operational Reports screen located in the Reports section.

Reports Published Reports Information about assessment results
When available they can be viewed online, downloaded and printed Published Reports is where you will find your assessment results. Reports will be identifiable by the same report names as in the past and report access will match the role assignments that you are familiar with in PearsonAccess.

ePATS Access ePATs at or by clicking “Practice Tests on the TestNav App. ePATs can be accessed through a web browser or through the TestNav app. Click on the ePAT you want to launch and it will take you to the login page for that ePAT.

Support Customer Support: Call Customer Support: Just a reminder..

Questions?

Copyright © 2015 Pearson Education, Inc. or its affiliate(s)

Similar presentations

Presentation on theme: "Copyright © 2015 Pearson Education, Inc. or its affiliate(s)"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Copyright © 2015 Pearson Education, Inc. or its affiliate(s)

Similar presentations

Presentation on theme: "Copyright © 2015 Pearson Education, Inc. or its affiliate(s)"— Presentation transcript:

Similar presentations

About project

Feedback