For developing a new CBT Product, follow the steps below:
1. Designing Training
New CBT:
A. EPRI staff looking to create new training courses should consult with the Training and Learning Design team before starting to develop a CBT. Visit the Training and Learning Design SharePoint site (URL Internal to EPRI only) to begin the process. EPRI Instructional Designers and Developers can work directly with you to create new courses or serve as consultants on projects being designed and/or developed by a vendor.
Updating a CBT:
B. EPRI staff looking to update an existing CBT should consult with the Training and Learning Design team to learn about any new templates or formatting requirements. Please visit the Training and Learning Design SharePoint site (URL Internal to EPRI only) to begin the process.
C. EPRI's Training and Learning Design team will schedule a kick-off meeting to go through the goals and desired outcomes for the new training once step A or B is completed.
2. Product Identification
A. EPRI Project Manager shall obtain a materials number for each CBT that will be hosted on the Learning Management System (LMS).
Note 1: The material number for a CBT hosted on the LMS must be unique from a material number for the executable file.
Note 2: CBTs in multiple languages must obtain a separate material number for each language version.
B. EPRI Project Managers shall identify the new CBT using an appropriate content type and delivery method.
- Self-Paced Training; Training LMS
Note: Failure to do this will prohibit EPRI from tying the access model to the product.
| Content Type | |||
|---|---|---|---|
| Previous | Current Content Type | Delivery Method | When to Use |
| Training CBT LMS | Self-Paced Learning | Training LMS | Computer Based Training (CBT) using an SCORM file format (SCORM), will be created, tested and approved, the CBT will be posted to the LMS for use by our members and/or the public, depending on how access to the CBT is classified. All files on the LMS will have the export control value of EAR99 or below. |
3. EPRI Branding Requirements
A. CBT Developers shall ensure all CBTs comply with EPRI's branding requirements
B. CBT Developers should comply with EPRI CBT Style Guides in the CBT Development Template table below.
Note: EPRI Project Managers should discuss deviations from the style guide with the EPRI Training and Learning Design Manager prior to finalizing the product.
4. Format Requirements
A. CBT Developers shall create CBTs for EPRI in one or a combination of the following authoring tools:
- Articulate Storyline
- Articulate Rise
Notes:
- Articulate 360 suite was chosen because these are the programs that the EPRI Training and Learning Design team uses. Consistent use of these tools allows us to make future edits or corrections to CBTs when needed.
B. CBT Developers should use EPRI's templates to create the CBTs.
Note: Deviations from the templates and/or style guide should be discussed with the EPRI Training and Learning Design Manager prior to finalizing the product.
Updated CBT Development Templates
| Instructions | Player/Skin | Themes (colors and fonts) | Templates/Layouts/Slides | |
|---|---|---|---|---|
| Articulate Storyline 360 | 2025-EPRI - Template v0.story | |||
| Articulate Rise 360 | The player/skin is shared with any team member in Rise360 | Authoring Tools Templates 2025.pptx | The template is shared with any team member is Rise360 |
C. CBT Developers shall publish output files for Articulate Storyline in SCORM 2004 3rd edition. SCORM 2.1 and earlier editions of SCORM 2004 also work, but SCORM 2004 3rd edition is preferred.
Note: CBTs must be published in SCORM to launch in the LMS.
D. Instructional Developers shall use the EPRI Publishing guidelines provided in the table below. Please note that the SCORM zip file must be smaller than 750 megabytes.
E. Vendor Testing and QA, all courses should go through a complete quality assurance check prior to submitting to EPRI's SQA department for final testing. These checks should include testing the course in SCORM cloud or directly on EPRI's test LMS Pilot. EPRI Project Managers should request access to Pilot for testing by using the LMS Product Review Form, located on the Training and Learning Design SharePoint site (URL Internal to EPRI only). In addition to testing functionality, content accuracy, and correct copy (proofreading including closed captioning), the course should be tested to be sure that it sends completion messages to the LMS. Test completion as a reasonable learner might progress through the course. For example, if there are slides that do not show up in the course navigation menu but are only accessible through a link on the player or through an optional to click link on a slide, they should not count against successful completion. Completing an internal QA check and LMS reporting test will help eliminate the need to make these changes after SQA completes their testing.
5. Files to Be Provided to EPRI
A. CBT Developers shall provide to EPRI:
- Articulate Storyline source files including the editable authoring tool files (i.e .*.story, *.pptx, *.ppta, .cptx).
- Articulate Storyline published SCORM files.
- All source files for all custom-built graphics. (such as the Photoshop .PSD file)
- All raw footage for all custom-built video embedded in the CBT shall be turned over to EPRI.
- A log of all multi-media used, where it was obtained from and how the intellectual property rights were obtained. See Media Log Template.
- All copyright release forms.
Note: The EPRI Project Manager can provide a copy of the EPRI Copyright release form.
B. Legal Requirements
A. Program Managers shall ensure that all photographs and video copyrights are obtained for the CBT.
Note: An EPRI Copyright Release form giving EPRI the photo or video shall be turned over to EPRI. Link to EPRI's Copyright Release Reminder information and Release Form. (URL Internal to EPRI only.)
B. Program Managers shall coordinate with their CBT Developers and ensure all copyright release forms are submitted to copyright@epri.com and to EPRI along with the source files for the project.
C. Accessibility Standards
A. CBT Developers shall incorporate Web Content Accessibility Guideline (WCAG) 2.0 Level A accessibility standards into the CBTs.
Note: EPRI has adopted WCAG 2.0 Level A to ensure all CBTs are usable for learners with various abilities.
Note 2: Accessibility standards ensure a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss and other ailments can fully participate in a web content like computer-based trainings.
D. Optional Requirements
A. Project Managers should consider having a Project Plan including a Quality Plan.
E. SQA Testing and Promotion
A. Complete an internal QA test including a test of completion on SCORM cloud or in the EPRI LMS Pilot system prior to submitting to SQA.
B. Instructional developers shall submit the SCORM file and all additional files outlined in section 5A above to the EPRI Project Manager.
C. Project Managers will submit the files and the LMS Product Review Form located on the Training and Learning Design SharePoint site (URL Internal to EPRI only) for upload to Pilot LMS, then SQA will be notified to begin testing.
D. The Project Manager shall assure accuracy of content.
Note: SQA testing does not include peer reviews or other checks for subject matter quality.
- Testing of functionality and flow (i.e., Do slides progress, does media run, do quizzes and other interactions work, etc.)
- Test upload to the Learning Management System.
- Testing of SCORM reporting (i.e., shows as complete in the LMS, quiz results reported to LMS, etc.)
- Cross-platform testing on multiple devices and web browsers.
- Regression testing when updates are made to the CBT.
- Alignment to EPRI branding and formatting requirements.
Note: SQA testing does not include peer reviews or other checks for subject matter quality.