2. To develop a data model to incorporate the
infrastructure components and management
Model flexible enough for extension to other
entities/facilities
Model capable of tracking changes and storing
historical data
Scope – confined to Purdue University Campus
3. • Asset Inventory and Management
• Bicycle Lane Maintenance
• Bicycle Route Development
• Bus Route Development
• Capacity Planning
• Construction
• Evacuation Planning
• Highway Traffic Management
• Location Referencing Systems
• Pavement Maintenance
• Sand and Salt Spreading
• Sanitation Services
• Street Lighting
• Street Signage
• Traffic Signaling and Control Devices
4. MaintainenceDatabase
Interesections
OBJECTID
RoadSegmentID
ProjectDatabaseID Buildings
Accident SHAPE Need/consists of
ProjectLocation
OBJECTID I1 IntersectionID ProLocate_X
Type Need maintenance/ of ProLocate_Y
ConstructionDate Bikepaths SHAPE
RID ProjectType
LastMaintainence I1 BuildingID
AccidentType ProjectStartDate FK1 OBJECTID
NextMainatainence BuildingName
Location ProjectEndDate
Description Need/consist of BLDGABBR
Accidentdate Cost SHAPE
Markings DesignDate
Location_X I1 ProjectID I1 SegmentID
SubTypeField ConstructionDate
Location_Y proUpdateon Owner LastMaintainence
I1 RoadSegmentID ProUpdatedby Material NextMainatainence
Need maintenance/of Length Owner
Occur on / have Width Address
Consist of / are beside the
ConstructionDate Area
Occur on/are cause of some Need maintenance/of LastMainatainence
Need database/ consist of details of Perimeter
Need maintenance/of NextMainatainence Purpose
Roads Incude /are on the Comments SHAPE_Length
BusStations SHAPE_Length SHAPE_Area
Street Sidewalks Updatedon SubtypeField
Updatedby Updatedon
SHAPE FK1 OBJECTID
BikeStatus Updatedby
Are part of / innclude I2 RoadSegmentID
StreetID SHAPE BikeCondition BLDGStatus
StreetName SHAPE
StreetName StationID
SpeedLimit I1 SidewalkID
I1 RoadSegmentID Capacity
Capacity Owner
DesignDate
DesignDate Have / are beside the Material
ConstructionDate
ConstructionDate Width
LastMaintainence
LastMaintainence Area
NextMainatainence
NextMaintainence LastMaintainence
Maintainedby
Transit OneWay NextMaintainence
SubTypeField
NoLanes SHAPE_Length
Updatedon
Width Updatedby
Occurs on / provide for Are part of/ include
Slope Status
TransitID Include construction of/are part of
Material
RouteName
SHAPE_Length Consist of constructing/are types of
RouteType
I1 RID
Updatedon ConstructionProjects
Are part of / include construction of
Updatedby
FK1,FK2 OBJECTID
Have / exist in intervals on different / travel on
Have
Have / are on the
SHAPE
PavementMarkings ProjectID
Mode
ProjectName
OBJECTID Location
OBJECTID
EstimatedStartDate
PavementID Signs EstimatedFinishDate
RID
Owner ActualStartDate
Car
DesignDate ActualFinishDate
Bus
ConstructionDate EstimatedCost
StudentVehicle
LastMaintainence SignID ActualCost
UniversityVehicle
NextMaintainence Owner Contractor
Truck
Condition DesignDate Length
FromCoordinate InstallationDate Area
ToCoordinate SignType SHAPE_Length
Type SignStatus SHAPE_Area
PaveStatus I1 RoadSegmentID RoadSegmentID
Location
Condition
Location_X
Location_Y
Are beside
5. • Entities- Infrastructure facilities
• Features- Polygons, Lines, Points
• Attributes- IDs, Dates, Descriptions,
Dimensions
• Developed model represented as an ER model
with the relations given on the links connecting
different entities and features. The ER model is
obtained from exporting the data from
developed model into Visio and linking them
manually.
6. Data like maintenance database maintained for
all the physical entities considered as
infrastructure.
7.
8. • Determines
whether the
facility needs
a
maintenance,
and from it
decides what
kind of
construction
is needed.
9. This set of fields
helps tracking
the progress of
the maintenance
of the facility.
10.
11.
12. Use of
JunctionID’s to
determine the
references of
junctions and
nodes.
13. • Network
structure
showing
closed
loops of
roads
around
some of
the
buildings
.