|
Track Classroom (Off-system) Training
Set to “Yes” or “No.” Set to "Yes" if you also
plan to track training classes that are not conducted on this training system.
In other words, "Classroom Training.” Set to "No" if you are
only tracking classes offered through FlexTraining.
Allow Item Analysis
Set to “Yes” or “No.” Set to "Yes" to activate
DETAILED logging of each test question and answer by each student, which is
necessary for Item Analysis Reporting. Use with caution as it creates MANY
database records.
Enable Time Logging
Set to “Yes” or “No.” Set to "Yes" to activate
DETAILED logging of student activity (i.e., access to course material and test
records).
Disable Right-Click
Set to “Yes” or “No.” Set to “Yes” to prevent students from
easily viewing the source code of their courses. This helps prevent theft of
course materials like SWF files that are meant to remain private.
Enable Management
Center Access Logging
If you wish to log all critical activity happening in your
Management Module, turn this feature on. If you have more than one Management
Center user, it is recommended that
this setting be turned on.
|
Training
Several comments were received related to the way the proposed rule referred to developing regional ITS architectures. Eight comments, from State agencies and metropolitan planning organizations, supported an incremental approach to developing regional ITS architectures, starting with project ITS architectures and building them together. Four other comments, from metropolitan planning organizations and industry associations, noted that an ad hoc regional ITS architecture developed incrementally through projects would result in an architecture less robust than if there were a single, initial effort to develop it.
Also, thirteen comments from the Association of American State Highway and Transportation Officials (AASHTO) and a number of States recommended extending the time for developing regional ITS architectures, as the proposed two year implementation would be too short. Ten of the commenters preferred four years in order to acquire the necessary resources for developing regional ITS architectures.
Most commenters were in agreement with the content of the regional ITS architecture as defined in the proposed rule. However, there were 19 comments that dealt with confusion over the definition of both ''conceptual design'' and ''concept of operations.'' In addition, there were 17 other comments on the makeup of the stakeholders, involvement of the private sector, and the need and desirability of ''agreements'' between stakeholders.
The comments indicated confusion regarding the development of regional ITS architectures, and especially so in discussing the period of time for their development. Therefore, the final rule has clarified the time period for developing regional ITS architectures by adopting the proposed extension to four years subsequent to beginning to deploy ITS projects (§ 940.9(c)), or four years from the effective date of this rule for those areas that are currently deploying ITS projects (§ 940.9(b)). In clarifying the time for development, this rule has eliminated any references to specific methods for developing regional ITS architectures. By not prescribing any methods, the rule provides flexibility to a region in deciding how it should develop its regional ITS architecture. Guidance and information related to developing regional ITS architectures is available from FHWA Division Offices and from the ITS web site, http:ll www.its.dot.gov, and will be expanded to provide assistance in meeting the intent of the rule.
|