Follow

Creating a Parent Document

Creating Parent Documents

Creating a New Parent Document

  1. Log in as the Parent Document Creator or a VPAT Administrator.
  2. Activate the "Create Parent Document" link from the Dashboard tab of AMP.
    • Parent Documents can also be created from the Parent Documents sub tab of the Organization tab.
  3. The Parent Document Builder dialog appears, the user then enters the Parent Document information. 
    • Name: This is the name that will identify the parent document within AMP. This will also be the name provided to the published (PDF) VPAT created from the parent document. Official Lenovo Naming Convention: <Official Product Name><Lenovo PN, for Options or saleable SW>
    • Target Project: This is the location where the parent document will be stored within AMP.
    • Parent Document Comments: This field provides an area where parent document / VPAT comments can be provided.
    • Enable General Announcement: If the VPAT is being created before its general announcement date, an email reminder can be sent when it is time to add the VPAT to the online request form. If activated, the user will provide the date (month, day, year) when the email reminder shall be sent.
  4. The user then selects the Make it happen button to create the parent document.

How to Create a Parent Document from an Existing Parent Document

This process is beneficial in the event that there will be several parent documents or VPATs that will share a similar group of checklists (i.e. pre-load). Parent Document Creators can complete the checklist bundling process once and re-use a base parent document several times. This is process is more efficient than repeatedly bundling the same large group of checklists when creating a parent document.

  1. Log in as the Parent Document Creator or a VPAT Administrator.
  2. The user opens an existing parent document.
    • Parent documents can be opened from the Parent Document Overview sub tab of the Organization tab.
    • Recent parent documents can also be found on the dashboard tab.
  3. The user selects Copy Parent Document from the Edit menu of the parent document overview tab. 
  4. Enter the following information:
    • Target Project: This is the desired location within AMP that the copy of the parent document will be stored.
    • Target Report Name: This is the desired name of the new parent document that is to be created from the original.
    • Description: A description of the new parent document can be entered at this time. This is not a requirement. The description can be added after the clone process if desired.
  5. Activate the Copy button.
  6. The user is then brought to the parent document overview tab of the newly created parent document.

Creating a Copy of a Parent Document to Remove an Offending Component

Think and Edge only, as of October 2012

If your Parent Document includes a software checklists which does not meet all of the Section 508 criteria, you will need to create a copy of it and remove the non-accessible checklists. You will need to rename the Parent Document to add "(Accessible Version)" to the end of the name. Here is an example:

  • ThinkPad T420 (Accessible Version)

This allows Lenovo to be able to bid a fully accessible product when needed. To fulfill the order, manufacturing add the Accessibility tag file module to the preload image. This tag file looks for any modules where it finds the complimenting tag and then deletes it from the preload image. If you own a software application which is not fully accessible, you will need to add this tag to your module. For more information about this, contact Accessibility Focal Point or Accessibility Coordinator.

Parent Document Overview

  • The Parent Document Overview displays basic details about the Parent Document under Parent Document Data, as well as access to the Edit menu.
  • Parent Document Data
    • Name: Name given to the Parent Document.
    • Parent Document Owner: Owner of the Parent Document, set to creator by default
    • Created: Date the Parent Document was created
    • State: What state of completion the Parent Document is in.
    • Criteria: The checklists attached to this document, and what state of completion they are in.
    • Parent Document Comments: Any comments on the Parent Document will be visible here

Editing a Parent Document

  1. Log in as the Parent Document Creator or a VPAT Administrator.
  2. The user opens an existing parent document.
    • Parent documents can be opened from the Parent Document sub tab of the Organization tab.
    • Recent parent documents can also be found on the dashboard tab.
  3. Navigate to the Parent Document Overview tab.
  4. Select Edit Parent Document Details from the Edit menu.
  5. Edit the desired parent document details within the Parent Document Builder dialog box.
    • Name: This is the name that will identify the parent document within AMP. This will also be the name provided to the published (PDF) VPAT created from the parent document.
    • Parent Document Owner: This will be the AMP user who owns the parent document. This defaults to the user creating the parent document.
    • Target Project: This is the location where the parent document will be stored within AMP.
    • Parent Document Comments: This field provides an area where parent document / VPAT comments can be provided.
    • Enable General Announcement: If the VPAT is being created before its general announcement date, an email reminder can be sent when it is time to add the VPAT to the online request form. If activated, the user will provide the date (month, day, year) when the email reminder shall be sent.
  6. Activate the Make it happen button to save the changes.

Checklist Selector

Checklist Bundling / Adding a Checklist(s) to the Parent Document

  1. Log in as the Parent Document Creator or a VPAT Administrator.
  2. A new parent document is created, or an existing parent document is opened.
    • Parent documents can be opened from the Parent Document sub tab of the Organization tab.
    • Recent parent documents can also be found on the dashboard tab.
  3. User navigates to the Checklist Selector sub tab of the parent document.
  4. The user provides the desired constraints to filter the master list of checklists.
    • Start Date: The earliest checklist creation date to be included.
    • End Date: The latest checklist creation date to be included.
    • The user must choose which checklist categories they want to load. the available choices are:
      • Software - Windows Software: Display all checklist categorized as Software - Windows Software
      • Software - Web: Display all checklist categorized as Software - Web
      • Software - Android OS: Display all checklist categorized as Software - Android OS
      • Hardware - Desktops, Notebooks, Workstations, Ultrabooks, Convertibles: Display all checklist categorized as Hardware - Desktops, Notebooks, Workstations, Ultrabooks, Convertibles
      • Hardware - Servers, Storage and Networking Products: Display all checklist categorized as Hardware - Servers, Storage and Networking Products
      • Hardware - Tablets: Display all checklist categorized as Hardware - Tablets:
      • Hardware - Smartphones: Display all checklist categorized as Hardware - Smartphones
      • Software: Display all available software checklists.
      • Hardware / Option: Display all available hardware / option checklists.
      • Third Party: Display all third party checklists.
  5. Activate the Show Checklists button.
  6. Select the check box next to each checklists that is to be bundled in the parent document.
    • Related Checklist Sections will be added and removed automatically when one of the related checklist sections is checked / un-checked.
  7. Activate the Bundle Checklists button to add the selected checklists to the parent document.
    • The bundled checklists will be displayed under the Parent Document Checklists sub tab of the current parent document.

Parent Document Checklists

  • The Parent Document Checklists sub tab is built around an eight column table;
    • Checkbox Column This column allows you to select multiple Checklists
    • Name: Name of the Cheklist attached to the Parent Document
    • Project: the Project that the Checklist is in
    • Checklist Type: Displays which type of checklist each attached checklist is. Such as: Hardware or Software
    • State: Provides the status of the checklist
    • Created: The Date that the attached checklist was created on
    • Status: Shows whether or not the checklist has a failed instance
    • Action: Provides icon based links to Edit and Delete a checklist

NOTE A warning message will be displayed above the table if any checklists attached to the parent document are not finalized.

Remove a Checklist from the Parent Document

  1. Log in as the Parent Document Creator or a VPAT Administrator.
  2. A new parent document is created, or an existing parent document is opened which contains at least one bundled checklist.
    • Parent documents can be opened from the Parent Document sub tab of the Organization tab.
    • Recent parent documents can also be found on the dashboard tab.
  3. Navigate to the Parent Document Checklists tab of the parent document.
  4. Select the remove checklist icon under the actions column for the checklist that is to be removed from the parent document.
  5. Activate the Make it happen button on the Remove Checklist dialog box.

Remove Multiple Checklist from the Parent Document

  1. Parent Document Creator or VPAT Administrator logs into AMP.
  2. A new parent document is created, or an existing parent document is opened which contains at least one bundled checklist.
    • Parent documents can be opened from the Parent Document sub tab of the Organization tab.
    • Recent parent documents can also be found on the Dashboard tab.
  3. Navigate to the Parent Document Checklists tab of the parent document.
  4. Activate the check boxes for each checklist that is to be removed from the parent document.
  5. Navigate to the actions menu and choose remove checklist.
  6. Activate the Make it happen button on the Remove Checklist dialog box.

Edit a Checklist from the Parent Document

  1. Parent Document Creator or VPAT Administrator logs into AMP.
  2. A new parent document is created, or an existing parent document is opened which contains at least one bundled checklist.
    • Parent documents can be opened from the Parent Document sub tab of the Organization tab.
    • Recent parent documents can also be found on the dashboard tab.
  3. Navigate to the Parent Document Checklists tab of the parent document.
  4. Select the edit checklist icon for the desired checklist.
  5. Edit the checklist information via the Edit Checklist dialog box.
    • Name - This will be the desired name for the checklists. This is commonly the name of the software application, hardware, component, etc. that is to be tested.
    • Checklist Owner - This is the user that will have ownership of the checklist. This defaults to the user creating the checklist, but can be assigned to another user within the VPAT Management System.
    • Target Project - This is the location within the VPAT Management System that the checklist will be stored. Checklists can be organized through the use of Projects.
    • Finalized - This check box allows the parent document creator to finalize or restore a checklist to draft status.
  6. Activate the Make it happen button to save the desired checklist changes

VPAT Builder

VPAT Summary

  • The “VPAT Summary” component provides an overview about how complete the VPAT is in the form of a table. The table consists of 4 columns:
    • Criteria – The subsection of 508 that is necessary to complete for a VPAT
    • Support Level – This is the level of support your product has for each subsection of 508
    • Actions – Provides details about what is necessary to complete the subsection of the VPAT
    • Complete – Provides a quick look at which subsections have been completed in the VPAT

508 Subsections

  • The remaining components on the VPAT builder will relate to each subsection of 508 that is a requirement for the VPAT. For each required 508 subsection there will be a table that consists of four columns:
    • Criteria – this column is made up of the individual criteria that together make up the 508 subsection
    • Support Level – This is the level of support your product has for each criteria of the 508 subsection
    • Remarks and Explanations – Displays any remarks or explanations made about how the product handles the specified criteria.
    • Actions – Provides a icon that will open a module that allows you to edit the “Support Level” and “Remarks and Explanations” fields for the criteria on the same row.

CVAA

  • The CVAA tab is comprised of a three column table.
    • The first Column is labelled completed, and will populate with a check mark icon when a relevant CVAA document has been uploaded.
    • The second column, labelled General Questions, provides the general question the CVAA document you will upload should answer
    • The third column, labelled Actions, contains an icon link to upload a document that provides the needed CVAA response to the General Question.
      • Allowed file types are:
        • .gif
        • .jpeg
        • .pjpeg
        • .pdf
        • .doc
        • .docx
        • .xls
        • .xlsx
        • .zip
        • .tar
        • .xml
        • .html
        • .txt
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Level Access Support
www.levelaccess.com | 800.889.9659
© 2005 - 2018 - Level Access All rights reserved.
Privacy | Security | Credits | License