“It can’t find my
file”
While adding content files to
FlexTraining, FlexTraining may occasionally fail to locate your files – and yet
you are sure you placed them on the web server in the right place.
When you see the "Error 404"
message, it means the browser is looking for something that is not there.
Right-click on the page or frame with the error message and click on Properties.
It will give you the address of what it's looking for. Almost always, the
second you look at the address, you know what's wrong with it. Perhaps the
filename was misspelled, or you forgot to enter the name of the directory it
lives in along with the filename.
For people who are using Microsoft IE
5: They get a useless "Friendly" Error page that has no information.
That’s bad. A solution for that:
1.
Click on Tools/Options on the Menu in IE.
2.
Click the Advanced tab.
3.
Find the checkbox for "Show Friendly HTTP
Error Messages."
4.
Clear that checkbox (make sure it's not
checked).
From that point on,
you’ll get a standard "Error 404" message, and you can right click on
it as described above.
If you have material you wish to use as a Course Guide, you
can establish a course guide with as many chapters (one per document/file) as
you wish.
|
Training
Both the terms ''conceptual design'' and ''concept of operations'' have been deleted from the final rule. In their stead are descriptions of the content that is expected to form the basis for a regional ITS architecture. This content has not significantly changed from that defined in the NPRM but is now contained in § 940.9(d). The level of detail required is to the architecture flow level as defined in the National ITS Architecture. The regional ITS architecture must identify how agencies, modes, and systems will interact and operate if the architecture is to fulfill the objective of promoting ITS integration within a region.
The relevant stakeholders for a region will vary from region to region. The list is representative only and not meant to be inclusive or exclusive. On the specific issue of private sector participation, if the private sector is deploying ITS systems in a region or otherwise providing an ITS-based service, it would be appropriate to engage them in the development of a regional ITS architecture. Because of these variations from region to region, the FHWA felt it inappropriate to attempt to define an all inclusive list of stakeholders. The group of relevant stakeholders will be a function of how the region is defined and how transportation services are provided to the public. 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.
There were 14 comments from a broad range of organizations questioning how existing regional ITS architectures, strategic plans or ITS Early Deployment Plans would be treated under this rule.
It is the intent of the FHWA that any existing ITS planning documents should be used to the extent practical to meet the requirements of this rule. If a regional ITS architecture is in place, is up to date, and addresses all the requirements of a regional ITS architecture as described in this rule, there is no requirement to develop a ''new'' one. If the existing regional ITS architecture does not address all the requirements of the rule, it may be possible to update it so that it meets the regional ITS architecture requirements of this rule. What is necessary is that the end result is an architecture that meets the requirements of this rule and properly addresses the ITS deployments and integration opportunities of that region. This issue is specifically addressed in § 940.9(e) of this rule.
|