| Top Level: |
|
       |
| Peer Level: |
|
|
Child Level:
       |
Bookmark this page!Even though this web just a bunch of files on our M:/drive, you can add any page you're on to your Internet Explorer Favorites! Here's how to Create a desktop shortcut. Not in San Diego: SD Configuration for Outsiders. What's New?
Full info at News - Jan 9 Configuration Suggestion Box (it's a spreadsheet you can add to) Roadway Configuration Status:
Full details at Superset Status page. Hot Links
|
| Phase | Characteristics | Status |
| Expert-Led | Design the System | Good |
| Document the Plan | Reasonable | |
| Build the Skeleton | Good | |
| Personal role Well Known | Ok, for initial phase | |
| Full Participation | Flesh out the skeleton | Really good start on the infrastructure |
| Incorporate Major Improvements from discrete sources | Xini Manager: code "complete"; must adopt "frequent re-mastering" methods | |
| Self-Sustaining | All content experts take leadership in sphere of expertise | InRoads commands are owned. We need to assign areas of responsibility for "end results" (plotting, super, templates, etc.) |
| Major Processes Well Known by all | I need to document all processes, much to do, soon. | |
| All medium-to-large improvements easily incorporated (only minor efforts wasted) | Haven't initiated much | |
| Each "Process" in Entire Scope of Work is led by a content expert responsible for efficiency | not yet | |
| Optimum (Continuous Quality Improvement) | Universal attitude: "Can I make an improvement? Once done, how does everyone benefit?" | not yet |
| Universal ability: improvements very easily shared. | not yet | |
| Capture Minor and Disparate Contributions (very low wasted effort) | not yet |
There's been a modification to the v8.9 Implementation Goal: we're broadening our InRoads output from a strict 63-level CalTrans output to something broader (but that can be automatically put back to CT v7+ or CT v7).
InRoads Training Manuals available
Idea for your blind acceptance: Anyone working on a multi-user project should document things that other workers should know about. Let's put internal instruction documents in a "_readme_kha" subfolder in the project's main folder. For now document however you want (.txt, .doc. .xls, whatever) but give the file a descriptive name and stick it in the _readme_kha folder. As always, comments and suggestions welcome.
Valid reasons:
I set up MicroStation v8 to open v7 files w/o messing them up. So "my deliverable is ms/j, so I have to work in ms/j" is not a valid reason.
Enabling the New v8 Configuration (Work in Progress)
I am going to be setting up MicroStation v8 2004 and InRoads v8.9 for use throughout the department, initially specifically for Caltrans for the I-805 Managed Lanes Project. Click for additional info on the Software Upgrade Plan.
I'm a little behind on this, in format and presentation. I have about 600 pages of InRoads v8.9 Training Material (see http://civilxlr8.com/books/training_manuals.htm). This represents about 5 days of instructor led training for InRoads and 3 days for Hydraulics. We will have a bunch of small topical training, at most two hours at a pop. My current effort (off-clock) is to get this material atomized, electronicized and prioritized for appropriate sharing (the primary hold up is anti-piracy DRM, which is taking a lot of time, but is necessary).
|