For CBT Products:
For developing a new CBT Product, follow the steps below:
-
Designing Training
New CBT:
- EPRI Project Managers looking to create new training should
consult
with the Training Department before starting to develop a CBT.
Fill
out the
Basic Training Content Needs form to start the process.
Updating a CBT:
- EPRI staff looking to update an existing CBT should consult
with the
Training Department to learn about any new templates or
formatting
requirements. Please email
epriu@epri.com to start the
process.
- EPRI's Training Department 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.
-
Product Identification
- 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.
- EPRI project managers shall identify the new CBT using an
appropriate
material type.
| Material Type |
| Previous |
Current |
When to Use |
| Pre-Software CBT |
*Pre-Training CBT |
*Pre-Software CBT (Computer Based Training) has been removed
from
the dropdown list on the Material Creation/Update Form (AIF)
but has been retained in SAP Material Master. You will need to
contact your sector MoM (Master of Materials) to select this
option. this is option is very rarely selected, but when it is,
it is primarily used for testing the beta computer based (CBTs)
prior to creation in production (i.e. not for use externally
by members/funders/etc). |
| Software CBT |
Training CBT EXE |
Computer Based Training (CBT) using an executable file format
(EXECUTABLE)
will be compiled, tested and approved, the file is posted for
members/funders who have access to download if eligible from
an EPRI platform ONLY (member center or EPRI.com or though the
orders center). |
| N/A |
Training CBT 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. |
-
EPRI Branding Requirements
- CBT Developers shall ensure all CBTs comply with
EPRI's
branding requirements
- CBT Developers should comply with EPRI CBT Style Guides.
Note: The Style Guide will be available soon. Deviations from
the style guide should be discussed with the EPRI Training
Department
prior to finalizing the product.
-
Format Requirements
- CBT Developers shall create CBTs for EPRI in one or a combination of the following authoring tools::
- Adobe Captivate
- Articulate Storyline (preferred tool)
- Articulate Rise (preferred tool)
- Articulate Presenter
Note: Adobe Captivate, and the Articulate 360 suite were chosen because these are the programs that the EPRI Training Department uses. Consistent use of these tools allows us to make future edits or corrections to CBTs when needed.
- 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 Department
prior to finalizing the product.
CBT Development Templates
* Articulate Engage 360 is used to create
interactive content
that is imported into Articulate Storyline or Presenter courses.
It is not to be used as a stand-alone tool for course
development.
Layouts/slide for Articulate Engage 360 can be used in any
Storyline or Presenter course and are designed to complement
the Storyline and Presenter themes.
- CBT Developers shall publish output files for Adobe Captivate, Articulate Storyline or Articulate Presenter 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.
- CBT Developers shall use the EPRI Publishing Guidelines
Things included are items like:
CBT Publishing Guidelines
-
Files to Be Provided to EPRI
- CBT Developers shall provide to EPRI:
- All Adobe Captivate, Articulate Storyline or Articulate
Presenter
source files including the editable authoring tool files
(i.e .*.story, *.pptx, *.ppta, .cptx).
- All Adobe Captivate, Articulate Storyline or Articulate
Presenter
published SCORM files.
- All source file 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: CBT Developers can request a copy of the EPRI Copyright
release form from either their project manager or the Training
Department.
-
Legal Requirements
- 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. 
(This
URL is only accessible
by internal EPRI staff.)
- 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.
-
Accessibility Standards
- 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.
-
Optional Requirements
- Project Managers should consider having a Project Plan
including a
Quality
Plan.
- CBT Developers shall follow the
Installation & Checkout Phase step requirements for
software submittal
when submitting an executable CBT.
-
SQA Testing and Promotion
- CBT Developers shall submit the
Testing Submittal Package to request
an SQA test (e.g., Pre-Production (Beta) or Production
(Final)).
Note: Once the CBT Developer has submitted the files
and Testing Submittal Package, EPRI follows the
following path to complete the SQA testing.
CBT-LMS-Process
- The Project Manager shall assure accuracy of content.
Note: SQA and EPRI|U testing does not include peer
reviews or other checks for subject matter quality.
- The Project Manager is responsible to assure adequate
performance of the CBT.
Note 1: The SQA Team and EPRI only test for compliance
with EPRI requirements.
Note 2: If the CBT is non-linear, test-case documentation
should be provided so that all paths are explored.
- EPRI's SQA Team and Training Department will test
for the following:
- 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: More information on SQA Testing can be found
at the
Implementation
& Testing Phase