Use the Delivery Preferences page to define test delivery settings used in your ADAM environment. This page is only available to designated admin roles. 

  1. Go to System > Client Settings.
  2. Click the Delivery Preferences tab.
  3. Expand a category to define the appropriate delivery settings.
  4. Click Submit.

General Proctoring

  • Remote Proctoring: Allow remote proctoring, such as at a different school. When enabled, the test will have the option for remote proctoring.
  • Allow Late Add: Do not use with Eligibility assignments. Use Add Temporary Students instead if needed. See also: Create and Merge Temporary Students
  • Do not allow iFrame: When enabled, student should not be allowed to test in TestNav app iFrame mode.

Anonymous Proctoring

An anonymous proctor is a proctor accessing the proctor dashboard using a test code and proctor password vs Instant Proctoring where a proctor is accessing the proctor dashboard from the administration cards after logging into ADAM. This requires role permissions to Instant Proctoring.

  • Anonymous Proctors are allowed to create temporary students at test time. Instant Proctors need role permission to ‘Create Temporary Students’ to access this option. See also: Create and Merge Temporary Students.

  • Users are able to force submit a section for CAT tests from the proctor dashboard for students testing with TestNav. For multi-section CAT tests, when a student misses a day of testing, this allows proctors to move the student ahead in the test to begin the new section. This functionality does not apply to linear tests or CAT tests with only one section.  Additionally, the test configuration now includes ‘Allow Section Submit’ option.

  • Anonymous Proctors cannot submit student sessions from the proctor dashboard.

  • When True, the District and School is limited to the criteria defined in the administration.

  • Anonymous Proctors must accept the terms of the proctor agreement to proceed into the proctor dashboard. The text for the agreement is set using the Edit button to the right. 

Administrations

  • Sessions can be configured to be submitted at a certain time daily or after a period of inactivity. Be sure to consider if any tests will be administered over multiple days. This only submits sessions that were started and not submitted; students who have not started are not impacted.

  • Administrations can be configured to automatically rescan periodically.
  • When enabled, students' sessions will be created and assigned to the unassigned proctor group. Auto Rescan does not scan when this feature is disabled. As a best practice, always enable.
  • When enabled, a student with Language – (x) accommodation is added to the PNP in TestNav. The language is used to update the skin in the TestNav player.

Tests

  • Test Prerequisite: The test will have prerequisite tests. When enabled, a test option is allowed so that a student must first complete another test before starting this test.
  • When enabled, class-level data will be loaded for each school on the 'Report Assets'. See also: Report Assets.
  • Define the org types displayed in the Reporting Orgs field. Restrict a student’s reporting org to schools in the state, districts in the state or allow both schools and districts in the state.
  • When True, the District and School is limited to the Org Scope(s) of the user who is adding the Proctor Group.

These settings are needed only when working with paper processes in ADAM for tests delivered via TestNav.

  • When enabled, the accommodated form will have a checkbox during test creation to indicate if this form assignment should be included in the Pre-ID payload.
  • MOT Program: Used in the MOT paper order process. Order creation uses this program to define the available distributions and items. Select the appropriate program.

These options are rarely used as students should come through a sync with LaunchPad.

  • If a value is selected, it becomes a required field when using the Import User feature. 
  • When enabled, generate a random alphanumeric code, with a length of six (6) characters, when a student is created in ADAM. 

These codes are set per session. After a code has been applied to a student, you cannot edit or remove that code from this page. Once on a session, the session is removed from the administration rescan process.

Click Add to enter a code and its action:

  • Code: Enter an accountability code. For example, ME for Medical Excused. After codes have been applied to a student, they cannot be edited or removed from this page.
  • Label: Enter a label for the accountability code. For example, Medical Excused.
  • Prevent Test: Prevent the student from taking the test when this code is applied (such as for parent refusal). If the student attempts to start the test, a message will appear stating that they cannot take the test.
  • Allow Proctors: Allow proctors to assign accountability codes.
  • Do Not Report: Exclude student scores from reports and extracts when this accountability code is applied; however, the scores will be passed to Core Warehouse via the session API. If the test was not attempted by a student, the session will be treated as Do Not Report. Students with this accountability code will appear on reports with "Do Not Report" shown for their Test Progress.
  • Void: Void the session and exclude from reports and data extracts when this accountability code is applied. History for voided sessions will be retained in Session Explorer.
  • Void (Allow New Session): Void the session while allowing the student to start a new session after a rescan. History of voided sessions will be retained in Session Explorer.
  • Disable: Disable the accountability code. It will no longer appear in ADAM except in the Session Explorer accountability codes filter (so that you can search on disabled codes).
  • Admin Code: Make this code only available to roles with permission to add administrator-only codes.
  • Info Only: This code is intended to provide information only, rather than a code that triggers an action within the assessment management system. This code type will appear with the student’s information in the proctor dashboard, but it will not prevent sessions from being included in session updates (rescan, student movement, etc.). For example, some customers apply codes to mark a student’s session with information about a test irregularity that arose during testing, such as a student becoming ill during the session and not completing all questions. A session with such a code will still be included in admin rescan, and the student could still be moved to a new proctor group for a make-up session. 

For Pearson Use only.

Only applies to tests delivered via TestNav using content created external to ADAM. Define Admin Codes to set on tests if either PASS or CoW need to request data from ADAM based on that difference. Different codes are not needed to separate Operational, PV or Eagle Eye. Click Add to enter Admin Codes.

Admin codes are used when ordering paper test materials.

  • Admin Code: Enter an administration code.
  • Admin Code Description: Enter a description for the admin code.
  • Show in Ordering: Select to have the admin code available in paper ordering (Orders).

Enter student assignment tags to be used as criteria when creating an administration. This makes it easier to create administrations with out-of-level testing. Student assignment tags can be uploaded in Rostering > Users or in User Setup. Once assigned, students can be searched by these codes.  See also: Test Assignment Tags.

  • Assignment Tag: Enter a name for the tag, such as ALG1.
  • Assignment Tag Description: Enter a name for the tag, such as Algebra 1.


Tiny link: https://support.assessment.pearson.com/x/KoApBw