|
The Media Library feature lets you establish “Dynamic
Messages,” in one of several formats, to be used in your training content where
and when you choose. Each message you define may be used as many times as you
wish in your authored content and learner interactions.
A Dynamic Message may be a simple JavaScript “Alert” box, a
Flash movie or streaming video that you have created.
It may also be a text message (that you define) that pops up
in a separate window. Your Dynamic Message may be small enough to fit in a tiny
window or large enough to require a full frame.
View Records
Start by choosing “Media Library” from the Management Center
Menu. You may also click on any of the submenu items to see a filtered list of
messages.
A list view, displaying all currently defined messages,
appears in the right frame. The first time you access this screen, before you
have added any of your own messages, it will show just the sample messages that
ship with the FlexTraining system.
This screen is your gateway to message maintenance,
providing Add, Edit and Delete functions, as well as a “Show” link to display
the message in a popup window.
You may filter the list based on message type, based on
which course the item is assigned or both simultaneously.
|
Training
In addition to the comments on regional ITS architecture development noted above, the docket received 86 comments on systems engineering and project implementation. These comments revealed that the structure of the NPRM in discussing regional ITS architecture development, project systems engineering analysis, and project implementation was confusing and difficult to read.
To clarify these portions of the rule, the systems engineering and project implementation sections of the NPRM have been combined. Also, paragraphs that were in the regional ITS architecture section of the NPRM that discussed major ITS projects and the requirements for developing project level ITS architectures have been rewritten to clarify their applicability. Since these paragraphs deal with project development issues, they have been moved to § 940.11(e). A definition for ''project level ITS architecture'' was added in § 940.3 and a description of its contents provided in § 940.11(e).
The docket received 33 comments regarding systems engineering and the systems engineering analysis section of the proposed rule. Most of the comments related to the definition, the process not being necessary except for very large projects, and confusion as to how these requirements relate to existing FHWA policy.
In response to the docket comments, the definition of systems engineering has been clarified and is more consistent with accepted practice. In order to provide consistency in the regional ITS architecture process, the systems engineering analysis detailed in §§ 940.11(a) through 940.11(c) must apply to all ITS projects regardless of size or budget. However, the analysis should be on a scale commensurate with project scope. To allow for the greatest flexibility at the State and local level, in § 940.11(c), a minimum number of elements have been clearly identified for inclusion in the systems engineering analysis. Many of those elements are currently required as provided in 23 CFR 655.409, which this rule replaces. Recognizing the change in some current practices this type of analysis will require, the FHWA intends to issue guidance, training, and technical support in early 2001 to help stakeholders meet the requirements of the final rule.
|