Perusall

Document Last Update: August 5, 2021

Product: Perusall

Name
Product Name

Perusall
Description
Vendors description of the product

Perusall is a social annotation tool that integrates with Canvas via LTI assignments. Perusall allows students and their instructors to collaboratively annotate documents. Instead of reading a document and discussing it, Perusall brings the discussions to the text. 

Purpose
Requester intended use of the product. What will the tool accomplish? What benefits to the university, students, others?

Helps you master readings faster, understand the material better, and get more out of your classes. To achieve this goal, you will be collaboratively annotating the textbook with others in your class. 

ASE Product Report Card
Product Report Card URL
 
Installation Type
Only one will apply
  • Approved - Campus
  • Approved - Online
  • Approved - Campus & Online
  • Semi Approved - Individual only 
Approved- campus

Tool Information

Communication Path
Communication paths for product changes and emergencies,…
  • When do the owner, stakeholders, employees and students need to be notified?
  • Path for back end issue - upgrades, bugs, ...
  • Path for Interface issue - upgrades, bugs, ...
  • Emergencies (major, minor)

Involved in determining this - Corey Moore, Ben Wilson, Dane Bohman, Dean Allen

 

The process for incident/maintenance communication for I-Learn products and the roles of portfolio managers and system owners is highlighted in the IT Incident Management and IT Change Management documents which are linked here.  

Product Owner
The person who can make the ultimate decisions for the product - funding, road map, vision, governance and retirement.
  • Please include name, email, phone, job title.

David Ashby 

ashbyd@byui.edu 

208-496-1536 

Director of Learning Innovation & Technology
Stakeholders
A person or group of people who have an interest in the product and its success. Can influence product decisions. Are impacted (directly or indirectly) by the product. e.g. requester, department, developer, ASE, portfolio manager, product manager
  • Please include name, email, phone, job title.

Stakeholders: 

  • History/Political Science/Geography Department Chair  

    Duane Adamson 

    adamsond@byui.edu 

    208-496-4226 

  • Front Office Contact  

    Angela Donnelly 

    donnellya@byui.edu 

    208-496 4220 

  • Teacher Education Department Chair  

    Karla Laorange 

    laorangek@byui.edu 

    208-496-4128 

  • Front Office Contact  

    Kaisa Werner

     wernerk@byui.edu 

     (208) 496-4101

 

Platform Services Director   

Director, Software Engineering  

Portfolio Management

Academics Product Manager  

  • Dean Allen - allende@byui.edu/(208) 496-7211   

ASE List:  

  • Dane Bohman - bohmand@byui.edu / 208-496-7217  
  • Ben Wilson - wilsonbe@byui.edu / 208-496-1550  
  • Amber Gneiting - gneitinga@byui.edu / 208-496-7015
Audience
Who will use the product? (campus, online, pathway, Ensign, employees - more specific like - nursing students, specific department or course(s))
 
  • Online and Campus 

Purchasing

  • Purchaser and requester information - name, email, phone
  • Licensing (description of the license agreement - site license, per user, per computer, ...)
  • How is the license renewed?
  • Next renewal date?
  • When should this product be reviewed again for purpose and outcome? Usually, this happens every 3-5 years.
  • BYUI Purchasing Agent  - name, email, phone

Licensing Contract (How many licenses were purchased for the product?) 

No contract. This is a free product. Working on SLA which will cost. 

Who is the contract contact? (Purchasing Department) 

N/A 

What is the technology use cap of this product? 

N/A

Other
  • Product documentation (URL)
  • Support and/or training documentation (URL)
  • ASE - maintenance needs and yearly maintenance estimate
  • Any custom code developed? (where can it be found)
  • Is this ADA compliant (URL to their official vendor statement)
  • Other
 
Data
  • Give description of all data and how it interacts with the university systems.
  • List all university systems used.
  • Installation instructions - URL or direction how to find the instructions.
  • Who is responsible for installation - please include email, phone, job title.

Push Destination 

  • Canvas course 

Pull Source 

  • Canvas course 

 

Course id 

User id 

User login id 

Primary email 

Full name 

Roles

Vendor Information

Product Name Perusall
Product URL https://perusall.com/
Company Name Perusall

Vendor Account/Sales Rep
Please include Name, email, phone, job title.

Perusall Support Articles, https://support.perusall.com/help
 

Vendor Support Rep
Please include Name, email, phone, job title.