From the Skills Menu, choose Assign Learners. Here is where
you may add, edit or delete profile records. Remember that each combination of
learner and Skill Group is represented by one record on the skills table.
When you first click on the Assign Learners button, you will
be presented with a list of existing profiles as illustrated below:
Click on the "Assign Skill Groups" button. A
separate window will open for you to add the new record. Select from the
various filters listed, or simply click the “Choose Skill Group” button to
proceed to the next page. Next, select from the list of available Skill Groups,
and then check next to the student(s) that require a skill. Finally, click on
the “Submit” button. To remove a student from the list, simply un-check the box
next to the student you wish to remove.
Warning Days: FlexTraining contains a feature that
automatically notifies a learner and/or the system administrator (via e-mail)
when a Skill Group that a student has not completed approaches its deadline.
“Warning Days” defines how far ahead of the “Next Required Date” the warning
message is sent.
Next Required Date: The date you enter here in (mm/dd/yyyy
format) sets a deadline for completion of the Skill Group for this learner.
For example, if you set the deadline to December 30, 2008, and you have set the
"Warning Days" field to 10, the student (or administrator) may start
to receive warning messages on December
20, 2008.
Editing a skill is very similar to adding one, except that
instead of adding a new profile, you are modifying an existing one.
Training
The FHWA did not define the responsibility for either creating or maintaining the regional ITS architecture to a specific entity because of the diversity of transportation agencies and their roles across the country. It is recognized that in some regions traditional State and MPO boundaries may not meet the needs of the traveling public or the transportation community. This is also why the FHWA did not rigidly define a region. The FHWA encourages MPOs and States to include the development of their regional ITS architectures as part of their transportation planning processes. However, the decision is best left to the region to determine the approach that best reflects their needs, as indicated in § 940.9. It is clear that the value of a regional ITS architecture will only be realized if that architecture is maintained through time. However, in accepting Federal funds under title 23, U.S.C., the State is ultimately responsible for complying with Federal requirements, as provided in 23 U.S.C. 106 and 133.
Four commenters noted that the proposed rule did not adequately address planning for, or committing to, a defined level of operations and maintenance.
The final rule addresses this concern on two primary levels, in the development of the regional ITS architecture and the development of individual projects. Section 940.9(d)(4) specifies that in the development of the regional ITS architecture, it shall include ''any agreements (existing or new) required for operations.'' The formalization of these types of agreements is at the discretion of the region and participating stakeholders.
Also, relative to operations and management at a project level, § 940.11(c)(7) specifies that the systems engineering analysis (required of all ITS projects) includes ''procedures and resources necessary for the operations and management of the system.''