University of Virginia
Process Development and Integration for the Six-Year
Program and the Statewide Transportation
Improvement Plan
Progress Summary
James H. Lambert <lambert@virginia.edu> (434) 982-2072
www.virginia.edu/crmes/stip
Center for Risk Management of Engineering Systems and Department of
Systems and Information Engineering
University of Virginia
September 10, 2004
Center for Risk Management of Engineering Systems
1
University of Virginia
Preface
• SYIP/STIP business process spans many divisions and
activities across VDOT
• Need to focus and bound SYIP/STIP business process
modeling that is supportive of current FHWA-VDOT
initiatives
• IDEF documentation should provide a basis for action
and remedies to current process deficiencies
Center for Risk Management of Engineering Systems
2
University of Virginia
Abstract
• The capstone team will develop business process
models of Virginia’s highway and transit construction
program with the integrated definition (IDEF) standard
that is used across diverse applications of systems
engineering. The team will interact with agency
managers who are involved in process reengineering.
The team will test and evaluate commercial software
including Process Modeler ™ of Computer Associates,
Inc. The effort of the team will have impact to the
financial management of over 1500 construction
projects and over a billion dollars of annual investment
in transportation.
Center for Risk Management of Engineering Systems
3
University of Virginia
Process Modeling Methodology - IDEF3
• Capture description of a process and the network of
relations that exists between processes
• Record the raw data resulting from fact-finding
interviews in systems analysis activities
• Document the decision procedures affecting the states
and life-cycle of critical shared data, particularly
manufacturing, engineering, and maintenance product
definition data
• Manage data configuration and change control policy
definition
• Make system design and design trade-off analysis
Center for Risk Management of Engineering Systems
4
Background – IDEF0
Example
Center for Risk Management of Engineering Systems
University of Virginia
5
University of Virginia
Data Needs for IDEF3
•
•
•
•
•
•
•
•
•
•
•
Activities
Objective
Title of responsible department/s
Inputs
Controls - consist of legislation, regulations, and policies related to
the system
Mechanisms - refer to the elements that accomplish the actions of
the process, such as people, manual or automated tools, established
procedures for holding hearings, etc
Outputs
Key decisions
Impacted activities
Estimated duration
Related models/diagrams
Center for Risk Management of Engineering Systems
6
Background – IDEF3
Example
University of Virginia
Source: http://www.idef.com/Downloads/pdf/Idef3_fn.pdf
Center for Risk Management of Engineering Systems
7
University of Virginia
Task 1
BPWin* Process Model of SYIP and STIP
Development
* Software Application of IDEF
Center for Risk Management of Engineering Systems
8
University of Virginia
Discussion of Process Models
• Created Several Process
Models
– Used IDEF3
– Merged into one large
process model
– Some of activities had
sub-activities
Above: STIP Process Model
Left: IDEF3 Description
Center for Risk Management of Engineering Systems
10
University of Virginia
STIP Development Process – Flow Diagram
Revenue
Estimates
Six Year
Budget
Project Cost
Estimates
Draft Program
Agency/CTB
Review
Preallocation
Hearings
Tentative
Program
Final Public
Hearing
CTB Approval
of Final
Program
MPO’s develop
Draft TIP
Non-Attainment
Final SYP
Program
Air Quality
Demonstrate
Conformity
Attainment
Financial
Constraint &
Self Cert.
MPO’s adopt
Final TIP
STIP sent to
Federal
Agencies
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
11
University of Virginia
STIP Development Process: IDEF Example
- Tree Diagram View
1
2
Center for Risk Management of Engineering Systems
12
University of Virginia
STIP Development Process – IDEF Example –
Sub-Process View
Center for Risk Management of Engineering Systems
13
University of Virginia
Revenue Forecasts – Flow Diagram
Budget Bill
Amendments
1
State Police For
Toll Roads
2
Capital Outlay
from Admin.
Services
4
Toll Facilities
3
Street Payments 6 Yr Estimates
5
STP for STP
Formula to Urban
& Sec.
22
Federal Revenue
6
Secondary
Factors from SRD
21
Estimate of
State & Local
Revenue Sources
7
Secondary
Urban Worksheet
23
Urban Population
Urban Div.
20
Modal Interest
from Letter to DMV
8
Revenue Forecast
FTA Section
8 Planning Funds
to DRPT
19
Indirect Costs
Worksheet
18
State Forecast
from DMV
9
To P&S Breakdown by
District
Rte 28 Revenue
10
Interstate/NHS
Worksheet
17
Regional Set
Asides
11
Basis Points
16
Maintenance and
Salary Adjustment
15
Salary Adjustment
for other Prog.
14
Comparison of
April to Dec
Revenue
13
Support for other
State Agencies
12
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
14
University of Virginia
Revenue Forecasts: IDEF Example – IDEF View
Center for Risk Management of Engineering Systems
15
University of Virginia
Other Processes Modeled
–
–
–
–
–
–
–
–
–
–
STIP Development Process
Revenue Forecast
Highway Maintenance and Operating Fund
Transportation Trust Fund/Priority Transportation Fund
Planning and Engineering Estimates
Drafting of the SYIP
Tentative Program
Secondary Roads **
Urban Programs **
MPO Process **
**Done by previous capstone group. Cannot find at moment.
Center for Risk Management of Engineering Systems
16
University of Virginia
Task 2
Case Study of Public Involvement
Center for Risk Management of Engineering Systems
17
University of Virginia
Mapping the Public Involvement Process
• Using the joint process review by FHWA, FTA, VDOT, and
VDRPT entitled Development and Financial Constraint of
Virginia’s STIP, the processes central to public involvement are
identified
– November 2002
• Each road system has a differing process of public involvement
–
–
–
–
–
Tentative SYP Program
Secondary Roads
Urban Programs
MPO Planning
STIP Development Process
Center for Risk Management of Engineering Systems
18
University of Virginia
STIP Development Process
Revenue
Estimates
Six Year
Budget
Project Cost
Estimates
Draft Program
Agency/CTB
Review
Preallocation
Hearings
Tentative
Program
Final Public
Hearing
CTB Approval
of Final
Program
MPO’s develop
Draft TIP
Non-Attainment
Final SYP
Program
Air Quality
Demonstrate
Conformity
Attainment
Financial
Constraint &
Self Cert.
MPO’s adopt
Final TIP
STIP sent to
Federal
Agencies
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
19
University of Virginia
Tentative Program
Public Input from
Regional Finance
Planning Meetings
Special Programs
Section
Draft Program
Input from Agency and
CTB Review Board
Final Revenue Estimates
Statewide & District
Summaries Prepared
CTB Approval
Tentative Program
Tentative Program Made
Available to Public
Comment
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
20
University of Virginia
Secondary Roads
Federal and State
Agencies
Public Requests
County Staff
Board of
Supervisors
VDOT
Resident
Engineer
Other VDOT Staff
Preliminary Priority List
of Improvements
Work Session With
Board of Supervisors
General Public
Draft Budget
Priority List
Public Comment
VDOT District Office
and Secondary Roads
Division
Draft Six Year Plan
Revision
Public Hearing (Draft
Six Year Plan Revision
and Draft Budget
Priority List)
VDOT Staff Comment
Board of Supervisors
and Resident Engineer
Jointly Finalize and
Adopt Six Year Plan
Revision
Board of Supervisors
and Resident Engineer
Jointly Finalize and
Adopt Six Year Budget
Priority List
Resident Engineer
Prepares Annual
Budget Based Upon
Adopted Budgeted
Priority List
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
21
University of Virginia
Urban Programs
Input From Municipalities
Cost Estimates Received
from PPMS
Population Data requested
from Weldon Cooper
Center (UVA)
Working Draft Six Year
Plan
Reconcile Previous
Funding
Receive Preliminary
Figures from Financial
Planning
Preliminary Funding for
Special Programs CMAQ,
etc.
Information from Financial
Regional Planning &
Programming Meetings
Internal VDOT Review/
Review with CTB
Final Revenue Figures are
Received from Financial
Planning
Program Sent to
Municipalities for Review
and Comment
Tentative Program
CTB Approves Tentative
Final Public HEaring
Final Approval
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
22
University of Virginia
MPO Planning
Prepare Preliminary
draft TIP
Public Announcement
of The Availability of
Preliminary TIP
Distribution of
Preliminary TIP
Public Hearing & MPO
Meeting
Input from VDOT/CTB
(Pre-allocation
Hearings)
Initiate Final TIP
Development
Input from MPO, City,
County, and Planning
District
Input from Approved
Six Year Program
Assemble Draft Final
TIP
Public Announcement
of Availability of Final
Draft of TIP
Distribution of Final TIP
Public Hearing & MPO
Meeting
TIP Adopted by MPO
TIP Transmitted to
VDOT
The TIP is Submitted
with an adopting
resolution and annual
self-certification
statement.
Source: Development and Financial Constraint of Virginia's STIP (2002). Joint FHWA/FTA/VDOT/VDRPT Process Review
Center for Risk Management of Engineering Systems
23
Public Involvement
Workbook
Center for Risk Management of Engineering Systems
University of Virginia
24
University of Virginia
Public Involvement Toolkit
A Public Involvement Toolkit should be implemented for the selection of Public
Outreach techniques.
Minnesota’s Public Involvement
Toolkit
VTRC’s Proposed Toolkit
Source: VDOT and VTRC 2003 Phase II Report
Center for Risk Management of Engineering Systems
25
University of Virginia
Task 3
Case Study of STIP Amendments
Center for Risk Management of Engineering Systems
26
University of Virginia
Tracking of STIP Amendments
• Hundreds of amendments are processed each year to
revise a current project in the STIP or to add a new
project
• The amendment process has no documented structure
• We developed an IDEF model and associated flowchart
to document all activities
Center for Risk Management of Engineering Systems
27
University of Virginia
Amendment Process Workbook
Center for Risk Management of Engineering Systems
28
University of Virginia
Flowchart of Amendment Process
Center for Risk Management of Engineering Systems
29
University of Virginia
Task 4
IDEF Placement at VDOT
Center for Risk Management of Engineering Systems
30
University of Virginia
Data Management Division
• According to the Data Administration website, under Data Modeling
Requirements for COTS Systems there is a requirement for what
Business Process Models would be acceptable into the Data
Management Division
– Business Process Model
Business process models (BPM) provide a framework for
identifying, defining, and organizing the functional strategies, rules
and activities needed to manage and support the way an organization
does, or wants to do business. It provides a graphical and textual
framework for organizing activities into manageable groupings to
facilitate their shared use and control throughout the agency. The
BPM is required by PMLG “Redesign Core Business Process 2.5”.
• The Computer Associate’s AllFusion program would fulfill these
requirements and is an acceptable Business Process Model to be used by
the Data Management Division
Center for Risk Management of Engineering Systems
31
Management Services Division
University of Virginia
• The Concurrent Engineering
Process Flowchart to the right
shows how the IDEF modeling
could be used in the Management
Services Division
• Found in Instruction and
Information Memorandum on the
fifth page at:
– http://www.extranet.vdot.state.va.us/l
ocdes/electronic%20pubs/iim/IIM22
6.pdf
Center for Risk Management of Engineering Systems
32
University of Virginia
Progress since Initiation of Contract
• Built hypertext Excel workbook according to IDEF
standard
• UVa extended the standard to accommodate additional
graphical types of data that we are obtaining
• Populated the above workbooks with text, timelines,
interview transcripts, organizational charts; with initial
focus on public involvement and amendment activities
Center for Risk Management of Engineering Systems
33
University of Virginia
Progress since Initiation of Contract (Cont.)
• Loaded BPWin software (IDEF) to a UVa workstation,
entered sample of data from hypertext spreadsheet
• Interviewed Ben Mannell in Richmond, obtained STIP
timeline and his description of activities
• Interviewed Rob Walters at Biotech Center, obtained his
description of certain activities
• Interviewed Gene Wells in Richmond, obtained his
description of the STIP amendment process
• Attended Ben Mannell’s training session for VDOT
employees and MPO staff, morning and afternoon
sessions
Center for Risk Management of Engineering Systems
34
University of Virginia
Progress since Initiation of Contract (Cont.)
• Made phone interview with Utah DOT staff who
developed process model of interaction with MPO’s on
their STIP, learned that they benefited from negotiated
agreement of what activities would be performed by
whom and by what calendar dates
• In related activity, met with Chad Tucker (VDOT staff)
et al. in Charlottesville regarding prioritization system
for state highway plan
• Interviewed Craig Ahlin, obtained his description of
different controls on STIP amendments
Center for Risk Management of Engineering Systems
35
University of Virginia
Progress since Initiation of Contract (Cont.)
• Made phone interview with Deborah Grant. Discussed the FMIS
system and project approval.
• Deborah Grant sent templates for the narratives of the STIP process
and forms for the FMIS system, which have been posted to our
website.
• Conducted interview with Donald Silies, Administrator for the
Scheduling and Contract Division with respect to the
Advertisement Schedule.
• Presented project at SIEDS Conference on April 16, 04
• Interviewed Jennifer DeBruhl in Richmond, obtained her
experience with the November 2002 document
• Jennifer DeBruhl sent the Financial Planning and Programming
Sections from the National Highway Institute/National Transit
Institute class
Center for Risk Management of Engineering Systems
36
University of Virginia
Progress since Initiation of Contract (Cont.)
• Interviewed Ahmet Anday and Amy Costello in Richmond,
obtained their description of the STIP Environmental Process
• Amy Costello sent the VDOT Project Level Air Quality Study
Program and the VDOT Transportation/Air Quality Conformity
Process
• Amy Costello also mailed the Richmond, Virginia Ozone
Maintenance Area Transportation Conformity Analysis
• Interviewed Michael Hester, obtained his description of the STIP
Environmental Process
• Michael Hester sent the Transportation & Mobility Planning
Division STIP schedule as of June 1, 2004
• Meet with John Nahm, Dick Jones, Ellett Pollard, and Rob Walters
at BioTech in Richmond, VA to discuss the project to date and its
relevance to BioTech’s work.
Center for Risk Management of Engineering Systems
37
University of Virginia
Progress since Initiation of Contract (Cont.)
• Interviewed Frank Dunn via phone on Project
Development
• Dick Jones emailed Data Modeling Requirements for
COTS Systems
• Interviewed Dick Jones via phone on how to navigate
the Data Administration's website
• Interviewed Bill Pulkowski via phone on document
tracking systems used by SCC that might be useful for
VDOT
• Created a draft of the final report
Center for Risk Management of Engineering Systems
38
University of Virginia
Ongoing Future Efforts
• Develop recommendations to improve the current
modeled processes
• Continue data collection for IDEF model
• Model more of the STIP/SYIP processes
• Integrate IDEF model with data models of IT Division
Center for Risk Management of Engineering Systems
39
University of Virginia
Project Website (www.virginia.edu/crmes/stip)
Source: www.virginia.edu/crmes/stip
Center for Risk Management of Engineering Systems
40
University of Virginia
Process Development and Integration for the Six-Year Program and the
Statewide Transportation Improvement Program
Materials
Updated Final Report for this Project (9-07-04) - RKJ
DRAFT of the Final Report for this Project (7-14-04) - RKJ *Updated 9-03-04
AllFusion Program Screenshots (9-02-04) - RKJ
DCC Work Flow Diagram sent by Bill Pulkowski (9-01-04) - RKJ
Bill Pulkowski Phone Interview and email from SCC (9-01-04) - RKJ
Concurrent Engineering Process Flowchart for Capstone Team to turn into IDEF (8-30-04) - RKJ
Original Document
Data Modeling Requirements for COTS Systems (8-30-04) - RKJ
Project Development Chart created from Dick Jones 8/13 Interview (8-27-04) - RKJ
Dick Jones Phone Interview (8-23-04) - RKJ
Action Items to do after Monday August 23rd (8-13-04) - RKJ
Dick Jones Email, Data Modeling Requirements for COTS Systems (8-13-04) - RKJ
Amy Costello Email, Project Life Cycle, Links (8-13-04) - RKJ
Frank Dunn Interview on Project Development (8-13-04) - RKJ
Progress Since Initiation of Contract (8-12-04) - RKJ
Action Items from July 21st Meeting with BioTech (7-26-04) - RKJ
Progress Report presented to BioTech (7-23-04) - RKJ
Notes from meeting with BioTech (7-22-04) - RKJ *Updated 7-27-04
Center for Risk Management of Engineering Systems
41
University of Virginia
Process Development and Integration for the Six-Year Program and the
Statewide Transportation Improvement Program
Materials (Cont.)
Transportation & Mobility Planning Division STIP schedule as of June 1, 2004 (Draft) (6-28-04) - RKJ
STIP Development Process in AllFusion Program (6-24-04) - RKJ *Need CA AllFusion Program to
open document
Ahmet Anday and Amy Costello Interview (6-23-04) - RKJ
IDEF Worksheet Questions asked during Interviews (6-14-04) - RKJ
Financial Planning Section from the National Highway Institute/National Transit Institute class taught
by Jennifer DeBruhl (6-11-04) - RKJ
Programming Section from the National Highway Institute/National Transit Institute class taught by
Jennifer DeBruhl (6-11-04) - RKJ
Jennifer DeBruhl Interview (6-09-04) - RKJ
IDEF Worksheet Update - Compilation of Previous Worksheets (6-04-04) - RKJ *Updated 6-25-04
Success with CA AllFusion- Document describing SRAs success with the AllFusion Program (6-03-04)
- RKJ
Example of AllFusion Project - Created by Voluntary Interindustry Commerce Standards (6-03-04) RKJ
Information on AllFusion Process Modeler - (6-03-04) - RKJ
IDEF Worksheet Update - Construction Process - RTS - 5/6/04
Craig Ahlin Interview (05-06-04)
Progress Report Presentation - April 27th meeting (4-27-04)
SIEDS 2003 - Conference Presentation (4-16-04)
Center for Risk Management of Engineering Systems
42
University of Virginia
Process Development and Integration for the Six-Year Program and the
Statewide Transportation Improvement Program
Materials (Cont.)
Notes from Deborah Grant Interview - 4/14/04 - ELI
Deborah Grant Interview - Federal Aid FMIS (4-13-04) - ELI
Deborah Grant Interview - Right of Way Template (4-13-04) - ELI
Deborah Grant Interview - Preliminary Engineering Estimate Template (4-13-04) - ELI
Deborah Grant Interview - Team District Assignments (4-13-04) - ELI
Deborah Grant Interview - Blank Construction FMIS Document - (4-13-04) - ELI
Deborah Grant Interview - Blank PE-1 Template - (4-13-04) - ELI
Deborah Grant Interview - Blank RW-201 Template - (4/13/04) - ELI
SIEDS 2004 - Conference Poster (4-12-04)
SIEDS 2004 - Conference Paper (4-12-04)
Notes from March 24th meeting with VDOT (4-4-04)
Progress Report Presentation - March 24th meeting (3-24-04)
Vision for Integrated STIP - Charlie Rasnick Email Transcript (03-19-04)
Supplementary Emails Explaining the Vision for an Integrated STIP (03-19-04)
Progress Report, University of Virginia (02-24-04)
IDEF Worksheet - STIP Process (02-23-04)
IDEF Worksheet - STIP Process (03-04-04)
IDEF Worksheet - Amendment Process (02-24-04)
IDEF Worksheet - Amendment Process (03-09-04)
Center for Risk Management of Engineering Systems
43
University of Virginia
Process Development and Integration for the Six-Year Program and the
Statewide Transportation Improvement Program
Materials (Cont.)
Progress Report, University of Virginia (01-23-04)
Progress Report, University of Virginia (11-19-03)
Revised STIP Proposal (11-18-03)
Materials from Joint FHWA,VTRC and VDOT meeting (11-17-03)
STIP Procedures Memorandum of Agreement
Evaluation of Public Participation in Virginia, Review by FHWA, 2002
Public Involvement Techniques for Transportation Decision-making-1996 (FHWA site)
Assessment of VDOT's Public Involvement Practices -- Final Report, June 2003
Materials from STIP Committee Meeting (10-21-03)
STIP-04 TimeLine
FY04-06 STIP
FY04-09 SYIP
Meeting with Mr. Murali Rao (Current STIP Poster, Current STIP Sub-Processes, Recommended STIP ) (1015-2003)
Culpeper Public Hearing Meeting (10-09-2003)
Six Year Program - Report on Development, Monitoring, Implementation and Best Practices (10-07-2003)
STIP - Massachusetts (10-06-2003)
Lynchburg Public Hearing Meeting (09-30-2003)
Presentation by James H. Lambert (09-15-2003)
Changes In Work Plan (07-07-2003)
Center for Risk Management of Engineering Systems
44
University of Virginia
Process Development and Integration for the Six-Year Program and the
Statewide Transportation Improvement Program
Materials (Cont.)
VDOT Home
VDOT Organization Chart
Projects and Plans
Public Hearings Meetings and Events
Fall 2003 Hearing Schedule
SYIP
SYIP Public Hearings Powerpoint
SYIP 2004-2009 Report
SYIP Update Public Hearings Fall 2003 Information
Projects in the SYIP
STIP
Citizen's Guide
STIP Amendment Process Draft Letters (provided by Gene Wells 03-03-04) 1 2 3
CAPSTONE Team Readings
STIP FY-05 Timeline
STIP and TIP Development Process, Utah DOT - Coordination with MPO, UTA, FHWA and UDOT, September 2001
AllFusion Process Getting Started Guide
AllFusion Process Modeler Methods Guide
FAQ on TIP
Development and Financial Constraint of Virginia's STIP - Joint FHWA/FTA/VDOT/VDRPT Process Review,
November 2002
Center for Risk Management of Engineering Systems
45
University of Virginia
Interviews Conducted since Initiation of Contract
• Interviewed Ben Mannell in Richmond, obtained STIP timeline and his
description of activities
• Interviewed Rob Walters at Biotech Center, obtained his description of certain
activities
• Interviewed Gene Wells in Richmond, obtained his description of the STIP
amendment process
• Attended Ben Mannell’s training session for VDOT employees and MPO staff,
morning and afternoon sessions
• Made phone interview with Utah DOT staff who developed process model of
interaction with MPO’s on their STIP, learned that they benefited from negotiated
agreement of what activities would be performed by whom and by what calendar
dates
• In related activity, met with Chad Tucker (VDOT staff) et al. in Charlottesville
regarding prioritization system for state highway plan
• Interviewed Craig Ahlin, obtained his description of different controls on STIP
amendments
• Made phone interview with Deborah Grant. Discussed the FMIS system and
project approval.
Center for Risk Management of Engineering Systems
46
University of Virginia
Interviews Conducted since Initiation of Contract
(Cont.)
• Conducted interview with Donald Silies, Administrator for the Scheduling and
Contract Division with respect to the Advertisement Schedule.
• Interviewed Jennifer DeBruhl in Richmond, obtained her experience with the
November 2002 document
• Interviewed Ahmet Anday and Amy Costello in Richmond, obtained their
description of the STIP Environmental Process
• Interviewed Michael Hester, obtained his description of the STIP
Environmental Process
•
•
•
•
Meet with John Nahm, Dick Jones, Ellett Pollard, and Rob Walters at BioTech in
Richmond, VA to discuss the project to date and its relevance to BioTech’s work.
Interviewed Frank Dunn via phone on Project Development
Interviewed Dick Jones via phone on how to navigate the Data Administration's website
Interviewed Bill Pulkowski via phone on document tracking systems used by SCC that
might be useful for VDOT
Center for Risk Management of Engineering Systems
47
University of Virginia
IDEF Worksheet Questions Webpage
www.virginia.edu/crmes/stip/IDEFform.htm
Center for Risk Management of Engineering Systems
48
University of Virginia
IDEF Worksheet Questions Coding
<HTML>
<HEAD>
<TITLE>IDEF Worksheet Questions</TITLE>
</HEAD>
<BODY>
<H1>IDEF Worksheet Questions</H1>
<BASE HREF="http://www.virginia.edu/crmes/stip/">
<p>The purpose of this document is to describe what parameters we need from you about each of your activities
<br>
and/or roles that go into the STIP/SYIP integration. Please
<br>
complete one of these forms for each of your activites and/or roles.</p>
<p>Each row on the worksheet represents a new IDEF0 (Integrated Definition for
Function Modeling) activity. <br>
IDEF0 is the technique that breaks down the activities or functions of the organization or system into its
<br>
component parts. It is a graphical language that assists in identifying the functions that are performed, the
<br>
various elements needed to perform those functions, and what is efficient and
inefficient about the system <br>
under study. (i.e. What are the roles you have in generating the STIP?)
<br>
Center for Risk Management of Engineering Systems
49
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
For more information on IDEF please go to <a href="http://www.idef.org">www.idef.org</a></p>
<p><img src="idef.gif" width="351" height="176">
<br>
<strong><font size="2">Figure 1: IDEF0 Description - Description of IDEF0 Format of Mapping</font></strong></p>
<p>The columns contain the IDEF0 standards as well as supplementary material.
<br> <hr width="600" align="left"><FORM action="http://www.virginia.edu/crmes/stip/cgi-bin/uploadform.pl"
METHOD="post" enctype="multipart/form-data">
<P> <b>Your name:</b> <font size="1">First</font>
<INPUT TYPE="text" NAME="firstname" >
<font size="1" face="Times New Roman, Times, serif">Last</font>
<input type="text" name="lastname">
</P>
<P>
<b>Your email address:</b>
<INPUT TYPE="text" NAME="from" >
</P>
<P>
<b>Title of your position:</b>
<INPUT TYPE="text" NAME="position" >
</P>
<P> <b>Field 1: Name of Activity</b>
<br><font size ="2">Name or title for activity or function.</font>
<br>
<INPUT TYPE="text" NAME="activity"></p>
Center for Risk Management of Engineering Systems
50
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
<P><b>Field 2: Inputs</b> <br>
<font size="2">Something consumed or modified in the process. (i.e. schedules, costs, drafts)</font> <br>
<TEXTAREA NAME="inputs" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<b>Field 3: Controls</b> <br>
<font size="2">A constraint on the operation of the process. Represents the objects that govern the manner <br>
in which inputs are transformed yet are not themselves transformed by the activity. Consists <br>
of legislation, regulations, and policies related to the system. (i.e. codes, restrictions)</font> <br>
<TEXTAREA NAME="controls" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<b>Field 4: Mechanisms</b> <br>
<font size="2">Something used to perform the process, but is not itself consumed.
The elements that accomplish <br>
the actions of the process, such as people, manual or automated tools, established procedures for <br>
holding hearings, etc. (i.e. software applications, email exchange, etc.)</font>
<br>
<TEXTAREA NAME="mechanisms" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<b>Field 5: Outputs</b> <br>
<font size="2">Something resulting from the process. Shows what an activity produces or creates.</font> <br>
Center for Risk Management of Engineering Systems
51
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
<TEXTAREA NAME="outputs" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<b>Field 6: Objective</b><br>
<font size="2">The goal of the function or activity.</font> <br>
<TEXTAREA NAME="objective" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<b>Field 7: BPwin Diagrams</b> <br>
<font size="2">Link to the activity in BPwin format.</font> <br>
<INPUT TYPE="file" NAME="bpwinfile">
<br>
<br>
<b>Field 8: Title of Responsible Person(s)</b> <br>
<font size="2">Person(s) in charge of the function or activity. <br>
<INPUT TYPE="text" NAME="responsible">
</font> <br>
<br>
<b>Field 9: Key Decisions</b> <br>
<font size="2">Possible choices for the outcome of the activity or function.
<br>
Center for Risk Management of Engineering Systems
52
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
<TEXTAREA NAME="decisions" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
</font> <b>Field 10: Duration</b> <br>
<font size="2">Time/length of the activity.</font> <br>
<INPUT TYPE="textarea" NAME="duration" VALUE="">
<br>
<br>
<b>Field 11: Transcripts/Interviews</b> <br>
<font size="2">Link to a document that shows an outline description of the
activity, interview, or a memo on the activity.</font> <br>
<INPUT TYPE="file" NAME="transcriptsfile">
<br>
<br>
<b>Field 12: External Links</b><br>
<font size="2">Links to sites outside the CRMES website that are pertinent to the activity.<br>
<TEXTAREA NAME="links" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
</font> <br>
<br>
<b>Field 13: Diagrams/Models</b> <br>
<font size="2">Diagram showing detail of the activity.</font> <br>
<INPUT TYPE="file" NAME="diagramsfile">
<br>
Center for Risk Management of Engineering Systems
53
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
<br>
<b>Field 14: Reviews</b> <br>
<font size="2">Notes or reports available on the activity.</font> <br>
<INPUT TYPE="file" NAME="reviewsfile">
<br>
<br>
<b>Field 15: Potential Recommendation</b> <br>
<font size="2">Any recommendations on how to improve the activity.<br>
<TEXTAREA NAME="recommendations" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
</font> <br>
<br>
<b>Field 16: Miscellaneous</b><br>
<font size="2">Any other information or files available on the activity that did not fit into the fields above.<br>
<TEXTAREA NAME="miscellaneous" WRAP="physical" ROWS=5 COLS=70></TEXTAREA>
<br>
<br>
<input type="file" name="miscellaneousfile">
</font>
<p></p>
<input type="submit" value="Submit Questionnaire">
</form>
Center for Risk Management of Engineering Systems
54
University of Virginia
IDEF Worksheet Questions Coding (Cont.)
<p>Please contact Professor Lambert with any further questions:
</p>
<ul>
<li>Email: <a href="mailto:lambert@virginia.edu">lambert@virginia.edu</a></li>
<li>Office Phone: 434-982-2072</li>
<li>Office Assistant Phone: 434-924-0960</li>
</ul></BODY>
</HTML>
</html>
Center for Risk Management of Engineering Systems
55
University of Virginia
Using the IDEF Model to Improve Business Processes of the Transportation Agencies:
Methodology for Transferring the Six-Year Improvement Program (SYIP) into the Statewide
Transportation Improvement Program (STIP) on the State Level: A continuation of the Development
and Financial Constraint of Virginia’s STIP
Outline (DRAFT)
Abstract: A quick review of what the document is presenting.
Introduction: A review of Development and Financial Constraint of the Virginia’s STIP and the role that the University
of Virginia plays in this project by transferring the previous document into IDEF format.
Background on IDEF: A detailed review on the literature written on IDEF modeling and a review on other projects that
have used the IDEF modeling for their business.
Development of Methodology:
IDEF Worksheet: A description of the IDEF worksheet and its purpose.
AllFusion Program: Description of the program created by CA and its purpose in this project.
Application: Description of the project and how VDOT will apply this project to their STIP.
Review of Jennifer DeBruhl’s interview: A detailed description of why the Development and Financial
Constraint of the Virginia’s STIP was written and for what purpose.
Focus on Sub-Processes (Environmental, Construction, etc.)
Conclusions: Overall review of what this document presented.
Recommendations: Recommendations for VDOT.
References: Any documents, websites, or books used in this document.
Appendix A: Methodology of Web-Page: Description of how the IDEF Worksheet Questions webpage was created and
the code that went into creating it.
Appendix B: IDEF Worksheet: Print out of the worksheet used.
Appendix C: AllFusion Program: Print out of the IDEF models created.
Center for Risk Management of Engineering Systems
56
University of Virginia
IDEF Worksheet
www.virginia.edu/crmes/stip/IDEF Worksheet.xls
Center for Risk Management of Engineering Systems
57
University of Virginia
Action Items
• Upload of Computer Associate’s AllFusion program onto
Capstone computers
• Learn the AllFusion program
• Continue to take activities both from the IDEF Worksheet and
from the November 2002 report and inserting them into IDEF
models
• Create IDEF models for the project development in the STIP
• Possible action: Simulate, using Arena or similar software, the
project development in the STIP
Center for Risk Management of Engineering Systems
58