The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 3... ...
3 2 Task 2 – Conduct Interviews with State DOTs This chapter describes the work performed in Task 2 of NCHRP Project 20‐103, "Guidance for Development and Management of Sustainable Information Portals." Task 2 was the first step in supporting the research team's top‐down, bottom‐up approach to the design of sustainable enterprise information portals (EIPs) . The top‐down part of the approach started with defining, at a high level, the Department of Transportation (DOT)
|
From page 4... ...
4 External Users – Topics pertaining to DOT EIP external stakeholders' interactions such as search and discovery, upload, and download. Executive Level, Future Trend, Security Concerns – Topics pertaining to the executive view of the understood purpose of the DOT EIP, the current funding challenges, internal and external communication, enterprise culture and processes, future requirements, and funding. Asset Management, Engineering, and Maintenance Services – Services pertaining to the development, deployment, maintenance, and retirement of DOT assets. Operations and Performance – Services pertaining to the operation of DOT systems and the measure of their performance and efficiency using such indicators as traffic speed, volume, occupancy, and incident information. Photo and Video Services – Services pertaining to the collection, storage, search, and archiving of DOT photo and video of infrastructure from drone, satellite, or ground, as well as operation and asset pictures or video, such as inspection images or incident videos. Based on the recommendations provided by the panel during the kickoff meeting and experience and contacts within state DOTs, the research team identified the leading DOTs/EIPs in the country. The Research Team used the Interview Topics as a guide to identify interviewees. With the help of the NCHRP 20‐103 Project panel members, the research team identified over 16 different interviewees. The 16 interviewees included: 14 internal DOT EIP stakeholders from Caltrans, Nevada DOT, the Regional Transportation Commission of Southern Nevada, and North Carolina DOT and 2 external DOT EIP stakeholders from Parsons Brinckerhoff and AECOM. Each internal DOT interviewee was associated with one or more interview topics. Primary and secondary interviewees were identified for some of the topics to be prepared for cases in which the primary interviewee might no longer be available for interview. In order to narrow down the focus areas and potential interviewees to the 10 interviews that the research team intended to conduct, the team used an online survey tool and asked the panel to rank the interview topics and focuses developed in Task 2.2 by order of interest. Once the survey was completed, the votes were summarized and a priority list was established for the interview topics, focuses, and interviewees. Figure 1 and Figure 2 show the results of the online survey and the interview topics and focuses ranking. The higher the score, the lower the rank of the topic/focus to be emphasized in the interview. For example, in Figure 1, financial services is a low‐priority topic whereas asset management, engineering, and maintenance services are of high priority. Similarly, in Figure 2, the search and discovery focus is of high priority whereas funding is the lowest priority focus.
|
From page 5... ...
F Figure 1. Ran igure 2. Ran ked interview ked interview topics. focuses. 5
|
From page 6... ...
6 The list below shows the top 10 topics of expertise that were selected for interviews based on the panel ranking: 1. Asset Management, Engineering, and Maintenance Services 2.
|
From page 7... ...
7 2.2.3 Characterize End‐Users In this section of the discussion, the interviewee was asked to describe the key users of the EIP(s) and, if applicable, to prioritize user groups or user goals from an institutional perspective. Questions in this area focused on users who were internal or external to the organization and the types of tasks they need to accomplish. Questions were also used to understand the interface and other mechanisms used to access the portals. 2.2.4 Technical Topics Next, the interviewer drilled down into various technical areas based on the knowledge of the interviewee and the types of portals and users with which they had experience. Not all questions in this section were appropriate for all interviewees, and relevant questions were selected to provide the most value during the discussion. The various technical areas are presented in approximate order of importance based on the panel input described above and are as follows: Search and Discovery. Explores the DOT EIP needs for search and discovery and helps define how content organization and search will need to be implemented. Data and Metadata. Explores the data needs of DOT EIPs and helps identify how portal data need to be collected, refined, explored, organized, and maintained. Reliability. Explores how reliable DOT EIPs need to be and helps identify the various failures and potential failures that portals/services could be subject to and what is needed to minimize their impact. Business Objectives. Focuses on extracting the business objectives and business requirements of DOT EIPs because it is important to understand objectives and requirements early to avoid erroneous assumptions that could affect the accuracy of future deployments. Performance. Explores the performance that will need to be delivered by DOT EIPs and helps understand scalability, capacity, and high availability. Maintainability. Explores how DOT EIPs will need to be administered and maintained and how portal/services are currently being managed and helps identify DOT EIP maintainability requirements. Front‐End Systems. Explores the front‐end systems that will be used for access to DOT EIPs, helping to identify how users will connect to the portal and what kinds of devices they will use. Availability. Explores the availability needs of DOT EIPs and identifies the portal needs in order to successfully provide DOT EIP services over time and understand the availability requirements for each of these services. Different services might require different levels of availability. Security. Helps determine the security needs of DOT EIPs. Back‐End Systems. Examines the current and future DOT EIP back‐end systems to assess what will be needed to support the current and future needs of the DOT EIPs. Scalability, performance, and data center organization are among the factors explored. User Behaviors and Patterns. Focuses on extracting information related to the people who will use the portal, such as when they will use the portal, how they will access it, and how they have used previous portals. This information is key to identifying new requirements. Technical Goals. Focuses on how a portal is implemented. It is used to define target population, performance standards, and other factors related to goals more precisely. Future Growth. Focuses on assessing what capacity will be needed in the future, establishing DOT EIP growth expectations, upcoming changes, and the needs to accommodate them.
|
From page 8... ...
8 Funding. Explores the funding and acquisition of DOT EIPs, helping to identify the ways sustainable DOT EIPs need to be funded, acquired, and retired. 2.2.5 Vision Interviewees were asked to take a step back and envision how they would like to see the portals they work with evolve in the next 5 years. They were asked to describe an idealized vision by assuming there were no financial, technical, or resource barriers. Following this, the interviewees were asked about the feasibility of this vision for their own organization and/or in general across other similar organizations. Interviewees were provided probe questions related to (a) what currently works well and might facilitate the future vision and (b)
|
From page 9... ...
9 Table 1. Interviewees' area of expertise, job title, and institution. Area of Expertise Title Institution Asset Management, Engineering, and Maintenance Services Engineering Services Manager Nevada DOT Knowledge Management and Data Governance Knowledge Strategist Washington State DOT GIS and Mapping Services Caltrans Earth Coordinator Caltrans Director of FAST Regional Transportation Commission of Southern Nevada Operations and Performance Management Services Statewide Manager Connected Corridors Caltrans Documents and Library Services Torts, Claims, and Records Management Washington State DOT Bid and Contract Services Program Manager of Sustainable Purchasing and Intellectual Property Programs Caltrans IT Services Data Processing Manager III Caltrans IT Coordinator and Traveler Information Caltrans External Portal Users Supervising Traffic Engineer Parsons Brinckerhoff Environmental Services Senior Research Engineer Caltrans Executive Level, Future Trend, Security Former Chief Information Officer North Carolina DOT
|
From page 10... ...
10 On several occasions, the research team reached out to a wide variety of DOTs and contractors. The most expedient response was from Caltrans, which is why the majority of the interviews were conducted with Caltrans staff. While the research team acknowledges that this majority may raise concerns, Caltrans is one of the largest DOTs in the nation, spanning a huge geographic area. Because of this, Caltrans implements functions and encounters issues similar to the ones found in many other DOTs, particularly large DOTs such as Texas DOT, Florida DOT, and Illinois DOT. There are 12 districts in California, and to a large extent, each one was built out differently and uses a different IT architecture and different metadata. Because of this heterogeneity, there is a wide variety in the EIPs throughout the agency, allowing the research team to gain insight into both aged systems and new ideas and varying sizes and dynamics of end user groups. Caltrans is also mandated by the State of California to make its data public, making it easier for the research team to discuss data and portals with the interviewees. In addition, the team believes that the processes used by Caltrans are very similar to the ones in place at most DOTs and can provide good insight into the various components of the DOT EIP framework. To visualize the project's progress and ensure that the research team touched on each of the interview focuses during the interviews, an interview completeness table, or matrix, was used. The interview completeness matrix lists all 10 interview topics as rows and all interview focuses as columns. For each interview, whenever the team discussed and obtained information for a certain focus area, the corresponding cell was checked in the matrix that was used to rank the interview focuses (shown in Figure 2) . Table 2 shows the number of focuses the team was able to discuss during all interviews.
|
From page 11... ...
11 Table 2. Interview completeness matrix. Focuses Topics Bu si ne ss O bj ec tiv es Te ch ni ca l G oa ls U se r B eh av io rs a nd Pa tt er ns Ba ck ‐E nd S ys te m s Fr on t‐ En d Sy st em s Da ta a nd M et ad at a Fu tu re G ro w th Se cu rit y Se ar ch a nd D is co ve ry Pe rf or m an ce Av ai la bi lit y M ai nt ai na bi lit y Re lia bi lit y Fu nd in g Documents and Library Services 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Knowledge Management and Data Governance 1 1 1 1 1 1 1 0 1 1 1 1 1 1 IT Services 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Bid and Contract Services 1 1 1 1 1 1 1 0 1 1 1 1 1 1 GIS and Mapping Services 1 1 1 1 1 1 1 1 1 1 1 1 1 0 Environmental Services 1 1 1 1 1 1 1 1 1 1 1 1 1 1 External Portal Users 1 1 1 1 1 1 1 0 1 1 1 1 1 0 Executive Level, Future Trends 1 1 1 0 0 1 1 1 1 0 0 1 0 1 Asset Management, Engineering, and Maintenance Services 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Operations and Performance Management Services 1 1 1 1 1 1 1 1 1 1 1 1 1 1
|
From page 12... ...
12 2.4 Task 2.4 Transcribe and Analyze Annotated Interview Data The research team performed a text‐mining analysis on both the transcription and notes of each interview. The intent was to use text analysis to identify terms used by interviewees and possible additional elements not revealed during the review. To prepare the text for analysis, the recording of each interview was transcribed using a crowdsourcing transcription service called CastingWords. We requested to the transcription service was requested to transcribe only the interviewee's answer in order to avoid capturing terms used by the interviewer. Then, the collected interview notes were added to the generated text. The textual content of each interview was analyzed using the statistical software R to assess the words used during the interview, their frequency, and their co‐occurrence. Each of these analyses generated three visualizations: A histogram of the most frequent terms used by the interviewee. This plot shows the terms that were used often by the interviewee when responding to the interview questions. This plot can reveal what the vocabulary for a specific topic should be and the current or future focus of a specific topic such as "mobile" or "security," which can reveal new DOT EIP functions or framework components. Discovery of new vocabulary, functions, or components is not guaranteed, especially if the interviewee responses were vague or lacked vision. A wordcloud to represent graphically the most prominent term being used. Wordclouds are an alternative way to display word frequency. They allow for more terms to be displayed than a histogram and, therefore, allow more terms to be found. A hierarchical cluster visualization representing the group of words that occurred together during the interview. Hierarchical cluster plots are a way to discover co‐occurring terms in an interviewee's response. Co‐occurrence of terms in a specific topic can sometimes reveal DOT EIP functions, issues, or problems. Issues can be detected by looking at terms correlated with negative words, but the analysis is not guaranteed to find all possible functions or issues mentioned in an interview. When there is little text to analyze and a limited amount of words, strong terms can be difficult to identify. These visualizations were used to support and orient the research team in the identification of functions, activities, actors, and requirements of each of the interviewees' portals. The text‐mining analysis represents a minor part of Task 2. It was not intended to replace the interview and elicitation process but to support and enhance it by allowing researchers to identify terms, patterns, and correlations that may not have been detected during the conversations. The text‐mining analysis was also a way to start building a basis for the development of a domain language or a controlled vocabulary and taxonomy specific to the DOT EIP and its various functions. Controlled vocabularies and taxonomies are essential to the integration and discoverability of portal content and services. While the text analysis plots presented in this report show only the most frequent terms used by the interviewee, the analysis generated a list of all terms used by each interviewee that could be leveraged to create a controlled vocabulary. Without a controlled vocabulary, improving, searching, and controlling EIP content would be nearly impossible. To be discoverable, EIP content needs to be tagged and classified using specific metadata. These metadata need to be understandable by the users of the portal regardless of age, culture, or specialty. Prior to classifying content, DOT EIP metadata need to be defined, developed, and organized. Interview text analysis and visualization, such as word frequency (wordclouds) and term clustering charts, allowed the research team to identify candidate and predominant terms for each of the EIP topics. In addition, they helped the team identify
|
From page 13... ...
13 how these terms are correlated, providing a basis for how to organize terms with respect to each other (the basis of taxonomy development) . During the text analysis, the research team attempted to use TRB's Transportation Research Thesaurus (TRT)
|
From page 14... ...
2 O .4.1 Asse F bservations: Inform high p "resea Unive INRIX such a Futur the N Mobi to rev log as t Managem igure 3. Asse ation, acces riority for as rch" relates rsity of South : Reveals the s INRIX, in th e and camera evada DOT in le and device iew Nevada a set informati ent, Engine t manageme s, managem set managem to the Nevad ern Nevada need for the e case of the s: Refer to t terview. s: Refer to tw sset data, su on using mob ering and M nt, engineeri ent, and rese ent, enginee a DOT's need in Las Vegas. DOT EIP to s Nevada DOT he desire to a o different u ch as traffic ile devices in aintenance ng, and main arch: Manag ring, and ma to share ass hare DOT ass . rchive stream ses expresse camera video the field. Services tenance serv ing user acce intenance se et informatio et data with ing video fr d in the inte and speed s ices most use ss to inform rvices. In thi n with the r external thir om traffic ca rviews: the u ensors, and t d terms. ation appear s instance, th esearchers at d‐party consu meras, expre se of mobile he desire to 14 s to be a e term the mers, ssed in devices audit and
|
From page 15... ...
Observations: Addit traffic Figure 4. A ional terms, s camera vide sset manage uch as reten os. ment, engine tion and med ering, and m ia files, emph aintenance s asize the de ervices word sire of the Ne cloud. vada DOT to 15 archive
|
From page 16... ...
O bservations: Cluste asset Cluste and th Cluste interf Cluste for a D Figure 5. As r (mobile, ti tracking or m r (don't and e lack of sup r (provide, c ace providing r (people, tra OT to mana set managem me, departm anagement a resources) : R port for traff ameras, INR video from t nsportation, ge the conte ent, enginee ent, applicat pplications u efer to the i ic sensor net IX, portal, de he camera to business, re nt it makes av ring, and ma ion and asse sing mobile nability to de work expans vices, and re external thi search, conte ailable to bu intenance se t)
|
From page 17... ...
2 O .4.2 Know bservations: Contr DOT, searc Conte interv mana they a Impro State and im ledge Mana Figure olled, vocabu to research a h and discove nt, managem iewee about ge content gl re not able t ve, search, a DOT to deve prove DOT gement an 6. Knowledge lary, search nd develop a rability. ent, data, d the lack of p obally, have o search effic nd technolo lop technolog EIP search ca d Data Gove managemen and research stable and c ot, and don't redictable inf a shared voca iently across gy: Refer to t y to automa pability for d rnance t and data g : Refer to th onsistent con : Refer to the ormation fro bulary, or co multiple dat he desire exp te the taggin eveloping and overnance m e need, expre trolled voca point made m DOT porta ordinate am a sources. ressed in the g of new con maintaining ost used term ssed by the bulary for DO by the Wash ls. Most stat ong business interview w tent being lo efficient me s. Washington T content to ington State e DOTs do n areas. Addit ith the Wash aded into DO tadata. 17 State improve DOT ot ionally, ington T EIPs
|
From page 18... ...
Observations: Langu interv and c Regul interv and c Figu age, synony iewee, to de ultures existi atory, funde iewee, for bo ompliance re re 7. Knowle ms, and desc velop a contr ng within a D d, and guidan th state and quirements t dge managem ribe: Refer to olled vocabu OT. ce: Refer to federal regu o support the ent and dat the difficult lary understa the need, ex latory suppor developme a governance y, expressed ndable by th pressed by th t to help obt nt of sustaina wordcloud. by the Wash e various lan e Washingto ain funding a ble DOT EIPs ington State guages, gene n State DOT nd generate . 18 DOT rations, guidance
|
From page 19... ...
O bservations: Cluste inform incorp Cluste the W Cluste need that D Cluste the on searc DOT c Figur r (user, chan ation (mobi orating new r (don't, dat ashington St r (business, for research OT informat r (WSDOT, v going effort hability of the ontent using e 8. Knowled ge, portals) : le, web, text ways to sear a, resources)
|
From page 20... ...
2 O .4.3 GIS a bservations: Porta and d Lot, m the Ca featu previo Image by the the im more nd Mapping l, dashboard ashboards. W ake, things, ltrans interv res were not us GIS serve ry, analysis: portal interf agery data n difficult to m Services Figure 9. : Reveal that eb map serv don't, work, iewee when ready to use r setup becau Refer to the aces and ser eed to take p ove between GIS and map the primary G ices were m time, softwa deploying a n and required se of a lack o need express vices. This ra lace (client o clients and s ping services IS interfaces entioned, bu re, Google, i ew GIS serve additional sc f time and re ed by the int ises a questi r server) as t ervers. most used te used by our t not as one o ssues: Refer r in‐house an ript develop sources to d erviewees fo on as to whe he imagery d rms. interviewee f the primar to the difficu d discoverin ment. Caltra evelop these r imagery an re the analys ata get more s were web p y interfaces. lties encount g that many ns rolled bac scripts. alysis to be s is and render precise, larg 20 ortals ered by of its k to its upported ing of er, and
|
From page 21... ...
Observations: Secur interv enhan KML, used Beta: chang ity, incident, iewee after d cements the Google, beta by the intervi Also refers to ing rapidly a Figure beta, update eploying the y needed to , ESRI, ArcGI ewees as the the difficult nd never real 10. GIS and m , enhancem new GIS ent develop in‐ho S: Refer to th y develop GI ies encounte ly reached a apping serv ents: Refer to erprise serve use to reme e GIS enterp S services wit red by the in stable stage. ices wordclou the security r, the securit dy them. rise solutions hin their DO terviewee wh d. issues encou y issues they deployed an Ts. en dealing w ntered by th encountered d the GIS sta ith software 21 e and the ndard that was
|
From page 22... ...
O bservations: Cluste the D exper Cluste resou Cluste deplo r (work , don OT was not a ience. r (time, issu rces to imple r (dashboard y, and mainta Figure 1 't , things) : ble to develo es, Google, s ment the Go , lot, make)
|
From page 23... ...
2 O .4.4 Oper bservations: PeMS move Unive Lot, is sever and fo PeMS Caltra datas Plann by pla ations and Figure 12. , Berkeley, c of an experim rsity of Califo sues, party: al sources (Ca rmats. , real, time, d ns does not p et every mon ing, traffic: R nners. Performanc Operations a hallenge, yea ental traffic rnia, Berkele May refer to ltrans, distin on't: Refer t rocess the t th. efer to the fa e Managem nd performa rs: Refer to t operation p y, to the Calt the difficultie ct, CHP and t o the fact, ex raffic operati ct, expressed ent Service nce manage he lessons le ortal (PeMS)
|
From page 24... ...
O bservations: Push, capab INRIX ICM, a mana the cu Figure search: Reve ilities. , agencies, p nalysis, pilo gement of co rrent Caltran 13. Operation al that the P ublic, provide t: Refer to th rridor based s ICM pilot in s and perfor eMS system i rs: Reveal so e next gener on operation San Diego. mance mana s pushing dat me of the en ation of PeM s data feed ( gement serv a out to its u tities interac S, including p Integrated Co ices wordclou sers and offe ting with the latforms foc rridor Mana d. ring search PeMS system used on the r gement or IC 24 s. eal‐time M)
|
From page 25... ...
O bservations: Cluste provid Cluste sever Cluste forma Figure 1 r (don't, rea e data to its r (years, pla al years of ar r (traffic, pe t standards a 4. Operation l, Caltrans, P users in real nning, worki chived traffic ople, party, i cross the var s and perform eMS, time) : R time. ng)
|
From page 26... ...
2 O .4.5 Docu bservations: Docum system Public system Active are or Oracl relatio ments and ent(s) , plan and their in , engineers: . , directory, u ganized in gr e, records, st nal database Library Serv Figure 15. Do s, projects, y tended arch Refer to two ser, group: oups with va orage: Refer system (Ora ices cuments and ears: Refer t ival time, wh of the types Refer to the f rious access to the fact, e cle)
|
From page 27... ...
O bservations: Tiffs: Quest system Searc direct Reveals one o ions, public: was to prov h, interface, ly from the p Figure 16 f the format Refer to the ide docume displayed: Re ortal interfac . Documents s (i.e., tiff im fact, express nts in respon fer to the ab e without ha and library se age) used to ed by the int se to public i ility in the sy ving to down rvices wordc store docum erviewee, tha nquiry or que stem to sear load them.
|
From page 28... ...
O N bservations: Cluste provid ote that add r (people, ac e people wit itional cluste Figure 17. cess, docum h access to d rs contain to Documents a ent) : Refer to ocuments. o many or to nd library ser the fact tha o few terms t vices word c t the describ o be interpre luster. ed system's m ted. ain function 28 is to
|
From page 29... ...
2 O .4.6 Bid a bservations: Docum mana reque BidSy the re Bid, e intera nd Contract ents, datab ges request f st submitted nc, post, pro quests receiv mail, interac cts with its D Services Figure 18 ase, request orms, related . cess, public, ed are poste t, intranet, u OT users prim . Bid and con s: Refer to th documents, solicitation: d and tracke ser: Refer to arily throug tract services e fact, expres and a log an Refer to the f d on a statew the fact, exp h email and o most used te sed by the in d records in act, expresse ide bid syste ressed by the n the DOT in rms. terviewee, t a database th d by the inte m called Bid interviewee tranet. hat the syste e status of e rviewee, tha Sync. , that the sys 29 m ach t some of tem
|
From page 30... ...
Observations: Sprea using Files: to sup as ind dsheet: Refe spreadsheet Refers to the port the pur ividual files i Figure rs to the fact s in parallel w fact, express chase or bid n a folder. 19. Bid and c , expressed b ith the datab ed by the int request that ontract servi y the intervie ase due to t erviewees, t are managed ces wordclou wees, that s he dated nat hat requests independen d. ome of the re ure of the lat can contain a tly from the quests are t ter. dditional do requests and 30 racked cuments stored
|
From page 31... ...
O bservations: Cluste intera Cluste the re Cluste interv succe r (user, intra ctions with b r (document quests are n r (solicitatio iewee, that t ssful (e.g., no Figure 2 net, interact id or purchas s, don't) : Re ot attached d n, reports, p here is a nee one bid on a 0. Bid and co , bid, email)
|
From page 32... ...
2 O .4.7 IT Se bservations: Big, lo datas datab Don't use of Busin issues of res rvices t, issues: Ref ets) are beco ase due to th , cloud: Refe cloud servic ess, user, iss using IT syst ources to im Fig er to the fac ming larger a e dated natu r to the fact, es. ues: Refer to ems, and the prove the per ure 21. IT se t, expressed nd the reque re of the latt expressed by the fact, exp issues are of formance of rvices most u by the interv sts are track er. the interview ressed by the ten related t a specific sys sed terms. iewees, that ed using spre ees, that th interviewee o lack of trai tem. some of the d adsheets in p e DOT does n s, that some ning on a spe atasets (i.e., arallel with t ot currently users are hav cific software 32 GIS he allow the ing or lack
|
From page 33... ...
O bservations: GIS: R mode Image stream handl efers to the f rnization wit s: Refers to t s of images ing camera o act, expresse hin the DOT. he fact, expr and do not c r streaming f Figure 22. IT d by the inte essed by the urrently allow ailures. services wor rviewees, th interviewees the use of c dcloud. at GIS is curre , that the DO loud service ntly the mai T IT systems s, which pres n factor push manage larg ents challeng 33 ing for IT e es when
|
From page 34... ...
O bservations: Cluste not cu Cluste happe email Cluste interv betwe Note that r (don't, clou rrently feasi r (security, b ning by the t link that is n r (storage, s iewees, that en DOTs acr additional cl d) : Refer to ble due to leg ig, people)
|
From page 35... ...
2 O .4.8 Exter bservations: Acces with a down Roadw files c File, i such a throu nal Portal U s, files, basic DOT portal loads or FTP. ay: Refers t ontaining roa ssues: Refer t s corrupted gh the DOT w sers Figure 2 , typically: Re is to exchang o the fact, ex dway inform o the fact, ex files, mislabe eb portal tha 4. External p fer to the fa e files betwe pressed by th ation to supp pressed by t led files, outd t need to be ortal users m ct, expressed en contracto e interviewe ort design a he interviewe ated files, o sent by mail ost used term by the interv rs and DOTs t e, that the c nd impact an e, that there r documents on a flash dr s. iewee, that hrough serv ontractor is p alysis. are sometim too large to b ive. the main inte ices such as w rimarily look es file‐relate e transferre 35 raction eb ing for d issues, d
|
From page 36... ...
O bservations: Crash porta GIS, e extern Count the fil , issue: Refer ls are corrupt xcel, maps, d al user. y, area, spec es requested Figu to the fact, e ed or incomp ataset, form ific, entire, s are specific re 25. Extern xpressed by lete and cra at: Refer to t tatewide: Re to an area at al portal user the interview sh the tools t he type of co fer to the fac the county le s wordcloud. ees, that som hey are open ntent exchan t, expressed vel and rare e of the file ed with. ged betwee by the interv ly at a statew s obtained fr n the DOT an iewees, that ide level. 36 om DOT d the most of
|
From page 37... ...
O N e c t bservations: Cluste porta Cluste the in the po Note that ote: In the h ncoding used haracter in h ext analysis. r (user, secu l security rest r (storage, p terviewee, th rtal and forc additional cl ierarchical cl during the t exadecimal ( Figur rity, make, p rictions ofte ortal, media at storage lim e external us usters contai uster plot, "d ranscription d5) , which sh e 26. Externa eople)
|
From page 38... ...
2 O .4.9 Envir bservations: Fault, interv Map: Users USGS third onmental S information iewee. Reveals the p , bridges, eng : Refers to th party and use ervices Figure 27 : Refer to the resence of m ineers: Refe e need descr d to perform . Environme data ingeste apping capa r to the main ibed by the in analyses (i.e ntal services d, analyzed a bilities as pa users of the terviewee to ., the U.S. Ge most used te nd displayed rt of the port web portal d ingest data ological Surv rms. by the syste al. escribed by t files generat ey [USGS]
|
From page 39... ...
O bservations: Sprea and a Mode and m by the Locat searc Stude was d design dsheet, table ccessible on t ls, criteria, c aintain mod portal user. ion, time: Re hable using b nt, develop, esigned using and security Figure s: Reveal a w he web port alculations, d els that perfo fer to the nee oth space an change, code students as . 28. Environm ay, other tha al using table ataset, form rm calculatio d, expressed d time. : Refer to th developers a ental servic n the use of or spreadsh at: Refer to t ns on ingest by the inter e fact, expres nd had to be es wordcloud maps, that t eet formats.
|
From page 40... ...
O bservations: Cluste they e Cluste interv inform and m Note that r (things, pe ncountered r (USGS, ma iewee, that t ation aroun aintenance. additional cl Figure ople, design, difficulty dev p, lot, inform he system co d various fau usters contai 29. Environm interface) : M eloping the w ation, fault, llects a large lts, and displ n too many o ental service ay refer to t eb portal int bridge, engin amount of in ays analysis r r too few ter s word cluste he fact, expr erface using eers)
|
From page 41... ...
2 O .4.10 Execu bservations: Data, the D Busin refere perfo Data, gover the lif tive Level, Fig access, auth OT level rega ess, model, r nce models rm its tasks. governance: nance group e of a datase Future Tren ure 30. Execu entication: R rding authen eference: Re including fun Refer to the that defines t. d, Security tive level, fu efer to the n tication and d fer to the ne ctions, proce need, expres and manages ture trend, se eed, expresse ata access r ed, expressed sses, services sed by the in DOT data us curity most u d by the inte ights for all D by the inter , and actors terviewee, to er roles, dat sed terms. rviewee, to e OT data user viewee, to d needed for e establish a a access right stablish con s. evelop busine ach business centralized d s, and metad 41 trol at ss area to ata ata over
|
From page 42... ...
O bservations: Archit interv Secur appea Feder DOTs Fi ecture, mod iewee, to mo ity, cloud, em r to be more al: Refers to regarding da gure 31. Exec el, capabilitie del the archi ployees: Re secure than the need, exp ta governanc utive level, fu s, services, r tecture of a D fer to the opi most DOT on ressed by th e. ture trend, a eference: Re OT prior to nion, express ‐premise IT i e interviewe nd security w inforce the n attempting to ed by the int nfrastructure e, for federal ordcloud. eed, express control its d erviewee, th s. support to d ed by the ata. at most clou evelop guida 42 ds nce for
|
From page 43... ...
O N bservations: Cluste future to be Cluste of a D Cluste interv ote that add Fig r (system, p of DOT syst developed to r (access, bu OT portal ne r (dot, authe iewee, of bo itional cluste ure 32. Execu eople, cloud, ems includes redefine the siness) : May eds to correc ntication, st th DOT and s rs contain to tive level, fu model)
|
From page 44... ...
44 2.5 Task 2.5 Review and Analyze Sitemaps The interview content revealed many of the services, functions, requirements, and issues found within DOT portals. However, it did not give too much insight on the DOT public portals outside of traveler information. Public end‐users were found in services such as the "Bid and Contract Services" or "Documents and Library Services," but often these services do not publish their public data directly. Instead, their public data are relayed to another part of the DOT that deals with public communication -- a part that the research team did not interview. To augment the Task 2.4 findings and discover more about what DOTs expose to the public through their public portals, the sitemaps of 41 DOT public websites were analyzed. Table 3 shows a list of the DOT websites analyzed. The analysis performed is similar to the text analysis performed in Task 2.4; however, instead of analyzing the interview transcripts and notes, the titles and descriptions of DOT website pages were used. It should be noted that the results of this analysis may be vague due to the limited amount of text present in some of the DOT pages. A web crawler application, ScreamingFrog, was used to collect the titles and descriptions of all first‐ and second‐ level webpages of each DOT website. Next, the titles and descriptions were analyzed as a whole using the statistical software R. Finally, text analyses similar to the ones found in Task 2.4 were performed -- namely, term frequency analysis and term co‐occurrence analysis -- and the same visualizations were generated: A histogram of the most frequent terms used by the websites A wordcloud to represent the most prominent term being used in the websites A hierarchical cluster visualization representing the groups of words that occurred together on the websites Much like the interview text analysis, this evaluation was performed to enhance the findings of the interview analysis. In particular, it was used to capture the external (or public) functions performed and vocabulary used that were not mentioned in the interviews. Similar to the interview text mining, the analysis and visualizations were generated primarily to identify candidate terms, predominant terms, and the relationships among these terms. Instead of using common stopwords, the research team designed a list of stopwords to include terms such as "511" that would have been removed otherwise. This analysis was used to reveal existing DOT public portal requirements and functions that were not necessarily mentioned during the interviews. The analysis includes the integration of DOT portals with various social media websites such as YouTube, Twitter, Flickr, WordPress, or Facebook; the presence of rail, aviation, and transit travel information; and the publication of reports tracking the progress of large, publicly funded projects. To verify the findings, the team conducted a term correlation analysis on some of the discovered terms and assessed potential functions using the related terms found. The research team then proceeded to search our DOT public website index for the DOT web pages containing the presence of these correlated terms. Once a list of web pages containing the terms was obtained, the research team opened the web pages to confirm the presence of the discovered functions. An example of this process is described below. Figure 33, Figure 34, Figure 35, Figure 36 and Figure 37 show the visualizations generated during this task.
|
From page 45... ...
45 Table 3. List of DOT websites analyzed. DOT Link Alabama DOT http://www.dot.state.al.us/ Alaska DOT http://www.dot.state.ak.us/ Arizona DOT http://www.azdot.gov/ Arkansas DOT http://www.arkansashighways.com/ California DOT http://www.dot.ca.gov/ Colorado DOT https://www.codot.gov/ Connecticut DOT http://www.ct.gov/dot/site/ District of Columbia DOT http://ddot.dc.gov/ Florida DOT http://www.dot.state.fl.us/ Georgia DOT http://www.dot.ga.gov/ Idaho DOT http://itd.idaho.gov/ Illinois DOT http://www.idot.illinois.gov/ Indiana DOT http://www.in.gov/indot/ Kansas DOT http://www.ksdot.org/ Kentucky DOT http://transportation.ky.gov/Pages/default.aspx Maine DOT http://www.maine.gov/mdot/ Maryland DOT http://www.mdot.maryland.gov/ Massachusetts DOT http://www.massdot.state.ma.us/ Michigan DOT http://www.michigan.gov/mdot/ Minnesota DOT http://www.dot.state.mn.us/ Missouri DOT http://www.modot.org/ Montana DOT http://www.mdt.mt.gov/ Nebraska DOT http://www.transportation.nebraska.gov/ Nevada DOT http://www.nevadadot.com/ New Hampshire DOT http://www.nh.gov/dot/ New Jersey DOT http://www.state.nj.us/transportation/ North Carolina DOT http://www.ncdot.gov/ Oklahoma DOT http://www.okladot.state.ok.us/ Oregon DOT http://www.oregon.gov/odot/pages/index.aspx Pennsylvania DOT http://www.penndot.gov/Pages/default.aspx Rhode Island DOT http://www.dot.ri.gov/ South Carolina DOT http://www.dot.state.sc.us/ South Dakota DOT http://www.sddot.com/ Tennessee DOT http://www.tn.gov/tdot Texas DOT http://www.txdot.gov/ Utah DOT http://www.udot.utah.gov/ Vermont DOT http://vtrans.vermont.gov Virginia DOT http://www.virginiadot.org/ Washington State DOT http://www.wsdot.wa.gov/ Wisconsin DOT http://wisconsindot.gov/Pages/home.aspx Wyoming DOT http://www.dot.state.wy.us/home.html
|
From page 46... ...
F s s igure 33 show tate projects ocial media ( s that the m , traffic safet e.g., Faceboo Figu ost frequent y, bridges, co k, Twitter) . re 33. DOT w content pub nstruction in ebsites most lished on DO formation, co used terms.
|
From page 47... ...
47 Table 4. Most common words found on DOT public websites. 511 design info photo safety access development information plan search accessibility district license planning service act drive link plans site action driver local policy state adopt employment maintenance privacy system aviation engineering management program traffic bicycle environmental map project transit bridge Facebook media public transportation business find motor publications travel center freight new rail twitter commission gov news report vehicle construction government office request weather contact governor online research web county highway pedestrian resources website data home performance road work department improvement permits route YouTube
|
From page 48... ...
F f t 5 igure 34 show unctions. Th ransportation 11 Travel Inf s additiona e terms "rail" modes othe ormation Tel F l terms not di and "aviatio r than roadw ephone Serv igure 34. DO splayed in th n" reveal the ays. The ter ices, which w T websites w e Figure 33 h presence of m "511" refe ere discovere ordcloud. istogram and travel or pro rs to the pre d in 20 of th reveals add ject informat sence of page e 41 website itional portal ion pertainin s relating to s reviewed.
|
From page 49... ...
T t t O N T t w p t he hierarchic o the lack of erms across a bservations: Clust Exam Freew Clust exam Acces ote that oth o understand erm "rail" sh ebsite pages ercentages. his corpus. al cluster plo descriptive c ll the review er (freeway, ples of such ay Travel Ti er (accessible ple of such a sible Parking er clusters ar the process own in Figure with the ter The team no Fi t of the DOT ontent on som ed websites travel) : Reve pages are the mes," and "S , parking)
|
From page 50... ...
50 Table 5. Terms associated with the term "rail" in DOT public website pages. Terms Associated with "Rail" Correlation Percentage passenger 27% enhancements 14% corridor 13% commuter 12% tunnel 12% intercity 10% transit 10% issues 10% times 7% ride 6% announces 6% freight 6% station 5% funding 4% free 3% info 1% projects 1% The research team saw that the term "rail" co‐occurred in some DOT website pages with the terms "passenger," "commuter," "intercity," "transit," and "times." This co‐occurrence reveals the presence of rail traveler information content on some DOT public web pages. To verify this claim, the team proceeded to identify which DOT public website pages contained two or more of these correlated terms by querying the website index. Table 6 provides a list of DOT public websites where two or more of the correlated terms were found.
|
From page 51... ...
T v e v f w T he research erify that the ach provide erify the pre eatures prov ebsite. able 6. DOT p Massac Washin Illinois D Connec New Je Wiscon Californ Indiana Alaska D Virginia Arkansa District team then br discovered a screenshot sence of rail t ided by the M ublic websit DOT husetts DOT gton State DO OT ticut DOT rsey DOT sin DOT ia DOT DOT OT DOT s DOT of Columbia owsed the D portal functio of a page fro raveler infor assDOT page Figure 36. M es where the http T http http http http http http http http http http DOT http OT public we n was really m the Massa mation funct are linked t assDOT ligh term "rail" a ://www.mass ://www.wsdo ://www.idot. ://www.ct.go ://www.state ://wisconsind ://www.dot.c ://www.in.go ://www.dot.s ://www.virgi ://www.arka ://ddot.dc.go bsite pages w provided by t chusetts DOT ion on some o features of t rail travele ppears sorte Website dot.state.ma t.wa.gov/ illinois.gov/ v/dot/site/ .nj.us/transp ot.gov/Page a.gov/ v/indot/ tate.ak.us/ niadot.org/ nsashighway v/ here correla he DOT pub (MassDOT)
|
From page 52... ...
2 I i u c i t ( a o c 2 T i p E .6 Task 2 Requi n this task, th nterviews, an se of a DOT p ases identifie nterviewees' he research t e.g., the auth ssociated wit f the derived ases, but wil .6.1 Busin his section d nterview and articular. ach of the bu Busin users Archit the po Vision term obsta F .6 Summa rements D e findings of d DOT public ortal to fulfi d and merge vision. From eam derived entication ne h a compone functions, su l result in onl ess Cases ocuments th text analysis siness cases ess Goals. W ? What are u ectural Fram rtal?
|
From page 53... ...
T la i E 2 2 S p d i o lo e T IT c R p d t he architectu yers of the f nto three ma ach layer is s .6.1.1 Asset M .6.1.1.1 Bu tate DOTs pr artners. Use ocument the nclude other wn assets on cal universit nforcement he asset man S componen ompletely in egardless of erformance ata. Historic rends and va ral framewo ramework de in layers: (1) eparated by anagement siness Goals ovide asset m rs are intern state of the agencies, wh high‐order f ies and engin and lawyers. agement of ts. In other dependent o the method require the a al data can b rious conditio rk section fo fined in the a presentatio a logic servic Fig and Engineer anagement al agency em system, mak ich often use acilities and o eering firms physical asse cases, state D f the surveilla adopted, the bility to acce e used to cre ns. Real‐tim r each busine Interview Gu n or interfac e abstraction ure 38. DOT ing Services and engineer ployees who ing decisions the DOT ass n their own conducting w ts is often co OTs have est nce and con managemen ss, archive, a ate an under e asset data ss case ident ide (See Figu e layer, (2)
|
From page 54... ...
54 immediately to remedy failure and avoid major system disruption. In general, crash data are excluded from this work, but the analysis of crash data often falls within the realm of asset management and engineering services since it is used to determine system performance. Case A: Pavement condition and serviceability indices are collected on the system and enable data‐driven decisions regarding pavement maintenance activities. These data are used by both the planning and operations staff in the agency. Case B: An inventory of available devices (e.g., traffic signal equipment cabinets and the devices contained inside) can help the DOT study the budgetary impacts of systemic and systematic upgrades to hardware and equipment. Case C: A roadside inventory, which could be LIDAR‐based, allows for spatial analysis of point‐cloud elements, particularly to identify deficiencies in geometric design. Case D: Immediate access and control of live assets, such as surveillance video feeds and surveillance systems, can be provided to authorized users (e.g., law enforcement)
|
From page 55... ...
55 Table 7. Asset management and engineering services components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication for internal and external users Interface access and privileges established for each role. Standardized format and taxonomy to organize and visualize asset data User manual and training Format and standard documentation Bulk asset import interface Automated asset inspection and audit interface Automated asset report generation interface Asset performance alert interface Asset data streaming interface Public asset information interface Asset search and review interface DOT asset management interface DOT asset auditing interface DOT mobile field asset audit interface DOT asset creation interface DOT asset administration interface Business Services Non‐Real‐Time Real‐Time Authentication for service internal and external users Service access and privileges established for each role. Standardized input and output format for each service User manual and training Format and standard documentation Ownership and responsibility of services Asset performance analysis service Asset inspection service Asset data archival service Traffic video archiving service Asset data logging service LIDAR ingestion service GIS layers ingestion service Asset search and review service Asset web mapping service Traffic video streaming service Traffic video search service Asset performance data streaming service Asset audit ingestion service Asset status reporting service Asset web mapping service Data Sources Internal External Authentication for internal and external users Interface access and privileges established for each role. Standardized format and taxonomy to organize, search asset data Asset data, audit logs and video retention policies Ownership and responsibility of datasets Asset inventory activities log Asset inventory Asset documentation archive Asset performance data and log Surveillance systems, including traffic data and video data and log LIDAR data archive Other agencies data such as law enforcement crash data Vendor traffic data and fixed‐asset data Crowdsourced asset data Vendor LIDAR data
|
From page 56... ...
2 P t s r le T s c t c s i c i r T s m t u p p 2 2 W k g i o t P t c ( .6.1.1.3 Vis roviding for t he location, c ystem perfor eal‐time data gacy portals he fixed‐asse ystem data, i ontrol system he operation ollection, and ystem that p nvolve sensit ollection whi n order to en ules. he long‐term treaming dat ultiple data ime, with ret nauthenticat articipation, rotection. Kno.6.1.2 .6.1.2.1 Bu hile DOTs a nowledge m roups. Porta nformation a f strong know ime. roper knowl axonomies th urrently cons http://trbkm TRB's Tran TRB's Spe (http://on NCHRP Pr (http://on ion he inventory ondition, an mance, often that are like . t manageme ncluding roa s; and the c of these syst convention ermits access ive transport le also auditi sure complia goal of tran a is to allow sources, and ention of ma ed user acce and use of th wledge Mana siness Goals re frequently anagement (o ls are develo ccessibility. P ledge mana edge manage at maximize idering this i .org/) . Addit sportation R cial Report 28 linepubs.trb oject 20‐68A linepubs.trb and manage d functionalit relying on t ly being distr nt systems n dside appurte abinets, hard ems. The us al user‐based at a variety ation data. T ng external u nce with ope sportation da system integ the dissemin ny data sourc ss is already ird‐party dat gement Activ focused on d r lack thereo ped in respo ortal develo gement prac ment practic discoverabili ssue. Also, th ional resourc esearch Thes 4: Transport .org/onlinepu , Scan 12‐04, .org/onlinepu ment of tran y of fixed ass hose fixed as ibuted to tho eed to provid nances; traf ware, comm e of extensiv condition ra of levels, whi he entire sys ser data requ n records act ta managem ration with in ation of raw es provided a trend in sev a and proces ities eveloping to f)
|
From page 57... ...
57 Ongoing pooled fund study project producing a scan of research databases at DOTs in an effort to create common taxonomies and potentially automate resource management activities. Case A: DOT executive supports the development and management of data governance across the entire agency. Case B: DOT IT employees, DOT business leaders and DOT content management teams collaborate to improve the development of a shared language across the agency and increase DOT content discoverability by DOT end users, leveraging ongoing efforts from FHWA and AASHTO. Case C: DOT business teams and DOT IT leader teams design portal components following the guidance established by DOT knowledge management and data governance teams. 2.6.1.2.2 Architectural Framework This section lists desirable elements of knowledge management that should be considered in a portal architecture. Table 8 shows the basic architectural elements affected by knowledge management processes according to the DOT EIP conceptual framework.
|
From page 58... ...
58 Table 8. Knowledge management and data governance components. Architectural Elements and Policies Interface Portal interface needs to capture user interests by identifying the way that users search (through search monitoring, tagging, note taking) to refine the portal indexing and metadata Portal interface needs to enable both search capabilities and incremental filtering of search results Portal interface needs to allow personalization of search and display features Business Services Search and review services need to utilize control vocabulary and taxonomies established by knowledge management and data governance team Search and review services need to provide user search statistics to knowledge management and data governance team to help define a common language for DOT business areas; account for variability in technical language and identify terms used by users and stakeholders not capable of objectively characterizing their searches and vocabularies. Business areas, IT specialists, and knowledge management experts see systems in different ways and should work together to define and describe the portal services, taking into account regulatory requirements, data creator and maintainers. They should also collaborate in establishing portal services discoverability to avoid duplication and replication of services across the agency. Portal user generating data should be the owner and maintainer of this data. Data Sources Portal needs to leverage the content (controlled vocabulary, taxonomies, thesauri)
|
From page 59... ...
a e c r la G a e B a t 2 2 G v a S d is f a t a 2 T t ddress this a fficiently and apabilities so esearch and nguage and uidance is n nd content m nd users, but usiness area ppreciate the echnology to GIS .6.1.3 .6.1.3.1 Bu IS services a ariety of DOT nd a few ext ometimes G ownload or, leading the ormats and m nd quickly m o break down nd visualize Case A constr Case B to pla Case C Case D citizen .6.1.3.2 Ar able 9 shows he DOT EIP c nd have been more reliab that executi implementat common app eeded to help anagement. experts in th experts shou broad conte provide usef and Mapping siness Goals re now becom user groups ernal users (e IS services are more rarely, merging of s ade accessib ake use of da established DOT location : Technical s uction data. : Technical e ce a model o : News repo : Public‐faci s who want chitectural Fr the basic arc onceptual fra gaining atte ly used. How ves and infor ion. This foc roaches to c coordinate Each area b ese areas fre ld be respon xt in which t ul and/or usa Services ing a prefer including DO .g., contracto also offered through GIS iloed DOT dat le through a ta they wou barriers betw ‐based data. taff input an Staff also pre xperts -- such n a certain sp rters utilize in ng website h to know wha amework hitectural el mework. ntion in the t ever, there n mation owne us may lead t ontent mana across three rings specific quently don sible for dete he informati ble informat red way to se T staff (e.g., rs, news rep on the publ web mapping asets. This i common DO ld not traditio een DOT dis d monitor inc pare regular as engineer ot on a highw cident image as inquiries fr t's going on n ements of po ransportatio eeds to be m rs can wisely o coordinatio gement. separate are knowledge a 't understand rmining wha on might be u ion. arch, visualiz planners, en orters, emer ic‐facing port services. W s allowing tra T EIP that en nally use to ciplines or lo ident data in performance s, consulting ay system.
|
From page 60... ...
60 Table 9. GIS and mapping services components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external service users Service access and privileges for each role Geospatial visualization standards Standardized format, metadata for geospatial data GIS layer search interface Multi‐layer GIS analysis interface LIDAR sharing interface GIS rendering interface GIS data ingestion interface LIDAR data ingestion interface GIS based alert interface GIS search and review interface GIS data visualization interface GIS data analysis interface GIS based mobile alerts GIS data administration interface Business Services Non‐Real‐Time Real‐Time Authentication and roles for internal and external service users Service access and privileges for each role Geospatial data quality standards GIS analysis standards Standardized input and output format geospatial service GIS data audit service GIS search and discovery service GIS and LIDAR analysis service GIS and LIDAR ingestion service GIS based alerts service GIS rendering service GIS search service GIS analysis service GIS reporting service Data Sources Internal External Authentication and roles for internal and external data users Data access and privileges for each role Standardized format, metadata and taxonomies for geospatial data Geospatial data retention policies GIS data library or database including performance data, asset data, terrain data, etc. LIDAR data library or database GIS data archive GIS data ingestion and maintenance log GIS data audit log GIS data querying and analysis log Vendor imagery Vendor LIDAR data State or local GIS data layers such as active fire Federal Agencies GIS data such as USGS Earthquake or flood risks GIS layers. 2.6.1.3.3 Vision GIS services will become an integral part of DOT EIPs. Most location‐based DOT datasets will become part of GIS data repositories and will be available through DOT EIPs' GIS web services, allowing internal and external users to search, combine, visualize, and analyze datasets that are currently managed and stored independently in
|
From page 61... ...
d a s d la T l d e p M s r N e d s o T m O lo r t 2 2 S i w p E r o la ifferent form n asset critic uch as averag ata such as a yer (which i his type of as iability covera ata collectio ither on a de roject or ass any GIS serv tandards and etention per ew GIS data xtremely larg ata presents toring, and s r a contracto he increasing anagement verall, future cation‐base egions/distri ime GIS analy Ope.6.1.4 .6.1.4.1 Bu tate DOTs pr nternal agenc ell as emplo rojects. xternal users esearchers, p rganizations wyers. Case A condi agenc Case B DOT s ats. An exam ality analysis e annual da sset replacem ncludes the p set criticality ge, and the n side by allo sktop or a m ets and their ices are avai portal GIS in iods. , such as LIDA e and could difficulties re haring of new r using a por use of dron of many add iterations o d datasets to cts to produc sis involving rations and P siness Goals ovide portals y employees yees who wa also rely on ublic safety o that utilize th : Operations tions and resp ies/organiza : Corridor op taff decision‐ ple of such using a GIS o ily traffic [AA ent cost, as robability of analysis wo performance wing GIS data obile device i effect on the lable, but DO terfaces to p R, are also o be used to pe garding stor GIS dataset table data sto es to monito itional DOT G f GIS and ma GIS format, t e GIS data, th many GIS lay erformance M to support t that utilize d nt to underst these portals fficials, and e data to me staff rely on ond to incid tions. erations staf making. applications w perations lay DT]
|
From page 62... ...
62 Case C: DOT operations employees perform regular performance reporting activities to describe operation of freeways in the region. Case D: DOT planners research and use warehoused traffic data as a resource to develop new projects and resolve performance problems. Case E: Lawyers occasionally inquire about specific traffic data, generally related to the location of specific vehicles on a route. Case F: News media representatives use traffic and incident data for specific stories and traffic reporting, such as incorporating the camera feeds in their productions or relaying information to the public about travel times related to construction activities. Case G: The general public uses the portal, maps, interactive voice system and alerts of DOT travel data and 511 services to review delays, construction zones, and traffic cameras. Case H: Researchers from around the world search and download traffic and incidents to study traffic behavior or develop new traffic management methods. 2.6.1.4.2 Architectural Framework Table 10 shows the basic architectural elements of portals' servicing planning and operations goals according to the DOT EIP conceptual framework.
|
From page 63... ...
63 Table 10. Operations and performance management service components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external users Interface access privileges established for each role Standardized format and taxonomy to organize and index traffic data, video and images User manual and training Format and standard documentation Traffic data, video and image search interface Traffic data and video streaming interface Alerts registration interface (social media, SMS, etc.) Traffic real‐time alerts interface Traffic data, video and image downloading interface Traffic data, video and image search interface Traffic data, video and image mapping interface Traffic alerts registration interface Traffic data real‐time and historical visualization interface Video and image real‐time and historical playback interface Business Services Non‐Real‐Time Real‐Time Authentication and roles for internal and external users Service access privileges established for each role Standardized format and taxonomy to organize and index traffic data, video and images Traffic data, video and image quality control standards Traffic sensor data query and analysis service Automated traffic Reporting and performance analysis tools (forecasting)
|
From page 64... ...
u p B a a s i F w C i 2 2 D e m r f m a 2 T D rgency to pr rogram may ureaucracy a re slowing do re arising wh haring/using n difficulties HWA or IEEE ith hardwar urrently, diff mporting and Doc.6.1.5 .6.1.5.1 Bu OTs maintai ngineering d ay need to a equests. The requent and illions. Ofte nd respondin Case A correc Case B Case C public Case D Case E emplo Case F are co .6.1.5.2 Ar able 11 show OT EIP conce epare for the change over nd legal requ wn the need en sharing d data or using establishing e , could be be e and softwa erent functio displaying d uments and L siness Goals n written doc rawings) con ccess these number of D occasional us n, librarians g to request : DOT engin tions or mod : DOT plann : The gener or a surveyo : DOT librar : DOT librari yees. : DOT librari rrupted, inde chitectural Fr s the basic a ptual framew se data; how time. Techn irements are ed transform ata among ag external dat fficiency and neficial in ad re choices. It nal areas are ata in the po ibrary Service uments and taining inform materials for OT employe ers. The num are charged w s from the pu eering emplo ifications or ing employee al public requ r may see ne ians ingest an ans receive d ans analyze t xed inapprop amework rchitectural e ork. ever, there is ology decisio not keeping ation. Fund encies and v a services (e scalability in dressing thes will be more using compl rtal. s other kinds o ation about engineering es who use t ber of store ith processi blic. yees want a to perform m s will use exi ests informa w highway p d index new ocument req he content of riately, or ha lements of p also some u ns must be su up with ope ing can be slo endors acros .g., cloud sto the future. e challenges important to etely unique f document r their equipm or planning p his system m d documents ng and index ccess to plan aintenance a sting docume tion through rojects and h and old docu uests and sea the DOT doc ve the wrong ortals servici ncertainty w stainable ov rations decis w and challe s state borde rage)
|
From page 65... ...
65 Table 11. Documents and library services components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external users Data access privileges established for each role Standardized format and taxonomy to organize and index repository documents User manual and training Format and standard document ingestion and conversion Automated ingestion and metadata tagging interface Automated repository analysis and reporting interface Document repository search interface Document download interface Document repository search and review interface Document scanning/ image capture interface Document ingestion and tagging interface Document repository analysis interface Mobile document search, review and capture interface Business Services Non‐Real‐Time Real‐Time Authentication and roles for internal and external users Data access privileges established for each role Standardized format and taxonomy to organize and index repository documents Document quality control standards Legacy documents ingestion and indexing service New documents ingestion and indexing service Document inspection and repository analysis service Repository backup/replication service Repository document search service Repository document rendering service Authentication service Document inspection service Document editing service User activity logging service Data Sources Internal External Standardized format and taxonomy to organize and index repository documents Document migration policy Document retention policy Electronic written documents such as PDF or Word indexed archive Scanned images indexed archive Electronic documents such as JSON or XML indexed archive User activity logs Electronic documents from external agencies, legal firm and contractors. 2.6.1.5.3 Vision Documents and library services portals will benefit from the automation of document capture and indexing. Large projects in particular can produce a large number of documents that become backlogged in the import
|
From page 66... ...
p t c a U b d d O e p d 2 2 T a a m a B u c p w a rocesses. Of herefore, can onstantly be vailability (i.e ser interface e applied to ocument wh ocument res n the data‐c ngineers will roduced and ata types or Bid a.6.1.6 .6.1.6.1 Bu he provision ccomplished dvertisemen yriad of lega dministered idding and c sers of varyin ontracting pr urposes of d hat can be a nalysts, whic Case A transp sourc agenc Case B activi inform cost o acquis Case C inform officia Case D autom DOT e ten, paper do not be adde ing added, an ., funding) . design and d enhance usa en searching ults for each apture side, be creating d how docum document fo nd Contract siness Goals of design, co by means of t to bid and e l code admin by general se ontract porta g size and lo ocess. In ma ocument rev ccessed follo h limits auto : DOT acqu ortation age e for project i ies and optim : The DOT a ties, such as n ation, remo f ensuring bi ition deman : DOT acqui ation submi ls are anticip : DOT emplo atically insp mployee as t cuments tha d to the repo d the ability This backlog ocument tag bility for occa . User activit user. DOTs are mov ocuments a ents are crea rmats and ho Services nstruction, p contracted s xecution, is a istrative rule rvices perso ls must be re cation, while ny cases, no iew, often in wing a solicit mation for ce isition emplo ncy projects nformation t izing the use cquisition ma umber of req ving the need d compliance d. sition employ tted and proc ating includi yees submit ected for com he request p t need to be sitory. The c to keep up w ultimately aff ging are also sional users y data can be ing toward m nd associated ted and store w they can b olicy, operat ervices. Adm process tha s. Within lar nnel that may adily accessi also permitt n‐bidders wil the public int ation or bid r rtain types o yees manage to provide a c hat is compli of transport nager analyz uests, reque for manual a , and allowin ee users gen essed, allow ng in the pro an acquisitio pleteness an rogresses thr retained hav ost of doing s ith the captu ects service t important c and to maxim leveraged to obile tools f information d. Thus, libr e stored and ions, and ma inistering th t is highly do ger agencies service all s ble and secur ing internal u l access contr erest. Some esponse, eve f requests. a bidding po onsistent int ant and cons ation funding es the biddin st provenanc udits by DO g adjustment erate reports ing policy ana cess, particul n request to d compliance ough the acq e not been d o manually i re process is o users. onsideration ize the odds optimize se or their engi in new ways ary services p searched. nagement se ese contracts cumented, ti , bidding and tate agencies e, providing sers access a act documen department n requiring t rtal that can erface to all istent across . g portal's da e, unit prices T acquisition of DOT reso on bidding i lysts to iden arly WBE and the acquisitio and the ale uisition proce igitized and i s prohibitive.
|
From page 67... ...
67 Case E: A new acquisition request is matched with a DOT acquisition team member based on its expertise. Case F: A DOT acquisition team member tracks, updates, and completes requests with drawings and engineering documents as the requests progress through the acquisition process. Case G: A DOT employee communicates with DOT acquisition staff to remedy errors, non‐compliant of request. Case H: The DOT acquisition manager tracks overall request processing and manages the performance of the DOT acquisition team. 2.6.1.6.2 Architectural Framework Table 12 shows the basic architectural elements of portals servicing bid and contract services goals according to the DOT EIP conceptual framework.
|
From page 68... ...
68 Table 12. Bid and contract services components. Architectural Element Policy Components Interface Application Programming Interface User Interface Authentication and roles for internal and external interface users Interface access and privileges for each role Standardized format and taxonomy to organized bid and request interface User manual and training State bids service interface Bids and request search and review interface Bids and request reporting interface Bids and request analysis interface Bids and request alert interface Bids and requests input interface Bids and requests analysis interface Bids and requests search, review and tracking interface Bids and requests Requester communication interface Bid and requests administration interface Services Non‐Real‐time Real‐time Authentication and roles for internal and external service users Service access and privileges for each role Standard input and output for each service Bid and request compliance standards Bid documents batch ingestion and indexing Bid and request report service Facilitate questions with portal, with meta‐tagged tracking system for analysis Bids and requests audit/inspection service Bids and requests analysis service Secure bid upload service Bid response alert service Bid and request analysis service Bid and request visualization service Bid and requests administration service Data Sources Internal External Authentication and roles for internal and external data users Data access and privileges for each role Bids and requests archive retention policies Standard formats and taxonomies to organize and index bids and requests Bid and request datastore Vendor and contractor performance log Vendors list Purchase log Secure bid datastore Bid and request log Correspondence log State preferred vendors list Third party vendor and contractor information State and local agencies vendor and contractor information 2.6.1.6.3 Vision Agencies are seeking to streamline operations for both clerical and IT administrative needs, particularly in the case of data‐intense operations (i.e., contract development, cost estimates, and bidding) . The integration of automated or semi‐automated advertisement, bid, and contracting compliance systems can reduce the need for
|
From page 69... ...
d e b i R m a i d 2 2 D b i r s e T i r d uplicated eff xternal users idding docum ncluding plan eal‐time req ilestones, co cquisition pr ntegrity, with ocuments. IT Se.6.1.7 .6.1.7.1 Bu OT IT service roader DOT nfrastructure egard to resp ecurity typica xtensive test he joint goal n procureme ange of equip ifficult with l Case A develo hardw chang Case B open instru Case C from equip Case D signif were Case E real‐t feed f Case F new p ort in data en and analysis ents could i preparation uest inspecti mmunicatin ocess. Data a long‐term re rvices siness Goals s typically br and state gov of modern D onsiveness t lly require st ing and deplo s of security a nt and reduc ment) . Ach imited fundin : An externa pment and p are and the e needs. : An interna up some DOT ctions in a sp : The GIS op internal users ment for the : Updates t icantly increa validated in a : An interna ime data inpu laws, while a : An internal roject and us try and track of requester ncorporate a , reviews, est on and taggin g with all rele nalysis of bid tention and idge multiple ernment pol OTs can som o new techno rict adheren yment work nd system re ing costs)
|
From page 70... ...
70 Case G: The DOT IT team responds to cyber security alerts by re‐routing suspicious traffic and shutting down suspicious servers. 2.6.1.7.2 Architectural Framework Table 13 shows the basic architectural elements of portals servicing IT goals according to the DOT EIP conceptual framework. Table 13. IT services components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external interface users Interface access and privileges for each role Standard formats and taxonomies to search and organize IT assets Management of data centers, servers, backups interface Management of user pool, security, permissions, and policies interface Management of planning and load testing interface IT assets performance management dashboard interface IT assets user alert registration interface IT asset reporting interface IT template catalog interface Business Services Non‐Real‐time Real‐time Authentication and roles for internal and external service users Service access and privileges for each role Standard formats and taxonomies to organize and index IT services Audits standards for both IT data and IT assets auditing and inspection Maintenance management service Data archival, auditing and migration service IT security audit service IT performance reporting service IT cost reporting service IT security reporting service IT assets provisioning service IT asset monitoring and tracking service IT capacity management and planning service IT resource usage and optimization service Quota enforcement and usage service Automated provision service Data Sources Internal External Authentication and roles for internal and external data users Data access and privileges for each role Standard formats and taxonomies to organize and index IT assets data IT template catalog IT resources inventory IT assets performance log Network activities log Cloud service costs Vulnerability and threat data 2.6.1.7.3 Vision DOTs need to change the IT services' mindset and build reusable, integrable, loosely coupled layers of business logic that are well documented and discoverable. DOTs will need to develop and maintain services that will be highly dependent on each other and rely on similar data. New IT services will need to be able to interact with each other and be easily and rapidly assembled into a workflow to adjust to new user needs, threats, and changing data.
|
From page 71... ...
T IT w c T c c T h T t m 2 2 T o r h 2 T E he middle‐te services acr ill allow IT se loud. he long‐term an impose si loud services o support th ardware will hese change he agency an ost function Exte.6.1.8 .6.1.8.1 Bu he provision perations. W educe the sta as the poten Case A timing acces Case B conge that a Case DOT a inform Case D area a Case E progr develo .6.1.8.2 Ar able 14 show IP conceptua rm objective oss the agen rvices to be goal of IT se gnificant cost . e long‐term v be necessary s will be cons d state level. s of the DOT rnal Portal Us siness Goals of informatio hen done w ffing require tial to signific : A contract analysis. In s the data an : The local t stion manag re made acce C: Public age pportionmen ation to con : A local com nd accesses : That same ammed for fu pment activ chitectural Fr s the basic a l framework for IT service cy so that the more easily s rvices will be s for mainten iew, quick an to meet the trained by tr The most re and limit the ers n access to e ell, external a ments relate antly improv ed consultan stead of wor d download t ransit agency ement. A tra ssible to out ncy oversigh t of motor fu duct their ow munity con the DOT's cra commission ture constru ities. amework rchitectural e . s will be to m y can be late calable, rem to eliminate ance/upgrad d efficient d needs of int aditional IT p sponsive age ir developme xternal user ccess can cre d to informat e departmen t wishes to a king with a D he data in a f is interested nsit agency o side users. t groups, bot el tax funds n analysis of venes a trans sh records p examines the ction, funding lements of p odularize an r integrated ain managea in‐house dev es of system eployment of eractive IT se olicy models ncies will mo nt of portal s by a DOT ca ate user con ion access, a t operations ccess DOT tra OT project m ormat that i in understa fficial is able h formal and on projects co raw data. portation saf ortal to learn DOT's plans sources, an ortals servici d standardiz and dynamic ble, and be d elopment of s, and replac structural n rvices and la and data dis ve toward b interfaces by n have a sign fidence in de nd result in a and project ffic data for anager and r s immediatel nding the DO to access do informal, ar mpares to n ety commiss about crash and projects d progress of ng external u e the various ally managed eployed eithe proprietary e them with etwork syste rge dataset t semination re ecoming data relying on th ificant impac partment po dditional pu outcomes. a project rela eferrals, the y usable. T's strategic cuments from e interested i ational trend ion to study c trends. website to s environmen sers goals ac IT compone . This transf r on premise architectures quickly deplo ms and netw ransfers. strictions im provider AP ird parties. t on its busin licies and pra blic involvem ted to traffic user is able t initiatives rel the DOT int n understand s and use DO rash reductio ee which pro tal review an cording to th 71 nts and ormation or on , which yable ork posed at Is for ess ctices, ent that signal o directly ated to ranet ing how T project n in the jects are d plan e DOT
|
From page 72... ...
72 Table 14. External portal users components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external interface users Interface access and privileges for each role User manual and training Format and standard documentation GIS based shared DOT data search and review interface Shared DOT data search and review interface GIS based External data ingestion interface External users data ingestion interface GIS based DOT data search and review interface DOT data search and review interface Mobile DOT data search and review interface DOT data administrative interface Business Services Non‐Real‐Time Real‐Time Authentication and roles for internal and external service users Service access and privileges for each role Standard format and taxonomy to search shared DOT content Standard input and output for shared data service Standard input for external user data External users' data inspection standards Shared DOT data audits policies Shared DOT data inspection service External users' data inspection service Shared DOT data audit GIS based shared DOT data search and review service GIS based shared DOT data reporting service External users' data ingestion service Alert service Data Sources Internal External Authentication and roles for internal and external data users Data access and privileges for each role Shared DOT and External data retention policies Shared DOT data store including asset data, system condition and performance data, asset data, and information related to the programming, planning, design and construction of projects External users data to be delivered to or made accessible to the DOT
|
From page 73... ...
2 T a o T s g m e la p m d a 2 2 E d w o c E i n t ( .6.1.8.3 Vis he vision for s those both n the simplic he continuin ubdivisions. ain an under apping tool, xplore the G yers and inf roviding dire apping tool ata; system c nd construct Envi.6.1.9 .6.1.9.1 Bu nvironmenta ata, flood da hich are mo n both deter odes. nvironmenta n acute situat ews media u ransit agenci e.g., design) . Case A loadin will th Case B check Case C Case D Case E interf Case F porta ion external use rely heavily o ity and speed g evolution o External use standing of d will allow im IS mapping to ormation to d ct access to a is to discover ondition and ion of projec ronmental Se siness Goals l services en ta, and so fo dels that des ministic and l data have p ions (e.g., m se these data es)
|
From page 74... ...
74 Case G: The general public registers for DOT environmental service alerts, such pavement freezing or flooded road alerts. 2.6.1.9.2 Architectural Framework Table 15 shows the basic architectural elements of portals providing environmental services according to the DOT EIP conceptual framework. Table 15. Environmental services components. Architectural Element Policy Components Interface Applications Programming Interface User Interface Authentication and roles for internal and external interface users Interface access and privileges for each role User manual and training Format and standard documentation Federal agencies, research group data ingestion interface Environmental data sensor data quality audits interface Automatic uploading of pre‐formatted spreadsheet files Data and models search and review interface Data analysis interface GIS/Data visualization interface Business Services Non‐Real‐Time Real‐Time Authentication and roles for internal and external service Service access and privileges for each role Standard format and taxonomy to search shared environmental data and analysis results Standard input and output for analysis and visualization services Model upgrade/addition service Automated data analysis service Dataset addition service Dataset audit service Data update alert service Model update alert service GIS/Data Visualization service Ad‐hoc analysis service Data Sources Internal External Authentication and roles for internal and external service Service access and privileges for each role Standard format and taxonomy to organize environmental data and analysis results Environmental data and analysis results retention policies Environmental sensors DOT infrastructure data Analysis results log Activity logs Federal or research datasets
|
From page 75... ...
2 D m w p T t s D E d a R n s w u A o c i c L s m 2 2 D w c s t .6.1.9.3 Vis OT portals c igrate non‐w ithout much erformance o remedy th urnkey modu uch as the en OTs should f ngineers, som ata, or updat nd upgrade e esearch is on eed to be av pecify hazard ith seismic a pgraded usin dditionally, p r come from urrent produ ncomplete in ontrols and a ong‐term po taffing for op ore efficient Exec.6.1.10 .6.1.10.1 Bu OT portal us ho do busin ontent owne ervices. The o different us Case A as da Case B roles ion urrently integ eb‐based da knowledge o time, data sto ese issues, DO les that will vironmental ocus on usin e of whom e models dir ach service m going and ne ailable in the s that affect nalysis. Thes g a modular ortal infrast different ven ction; existin formation to utomated so rtal performa eration and performanc utive Level, F siness Goals ers may inclu ess with DOT rs for differe main busines ers. : The DOT d ta and service : DOT IT sta to ensure the rate environ ta analysis o f what it ent rage, and m T portals wi make it easie services prev g simple, mo are still used ectly onto th odule. w data, mod portal. For i near‐fault pe e will have t approach. ructure must dors. All pla g and new te users. This m ftware devel nce is more maintenance e in the futur uture Trend a de DOT emp s (e.g., contra nt functional s goal from t ata governa privileges fo ff leverage st security and ment service r prediction m ails. This res anagement o ll have to mo r, faster, and iously descri dular, and ea to paper and e portal. Por els, and anal nstance, in ge rformance. o be account account for p tforms must chnologies m ay be achiev opment tool important th must be con e. nd Security loyees and co ct firms) . Ot areas, data g he executive nce team esta r each of the ate and DOT efficiency of s portals in ra odels on po ults in challe f models. ve toward a more secure bed. sy‐to‐custom pencil appro tal administr ysis will pote otechnical p Similarly, USG ed for in port ossible chan be able to ad ust be integ able using a s. an getting a s sidered. Add ntractors, m her users co overnance te perspective blishes and se roles. authenticati the DOT EIP p ther traditio rtals to simp nges pertaini more modula to migrate a ize user inte aches, shoul ative tools ne ntially affect ortals, it mig S will be dev al developm ges in sensor opt new dat rated withou modular stru ystem up an itionally, pro embers of th nsist of those ams, public is ensuring th maintains the on services in ortal. nal ways. Of lify and share ng to scalabi r architectur nd manage t rfaces for the d not be exp ed to be dev the kind of in ht be helpful eloping othe ent and could s or models a sources wit t creating lag cture in com d operationa per administ e public, and who manag information o e right level various por combination ten DOTs try their capabi lity, model e and be able raditional ser se services. ected to code eloped to m formation th to allow use r tools that w be more ea that utilize ne hout interrup s or providin bination with l quickly. Ade rative tools l other extern e the portal, fficers, and of informatio tal user roles with establi 75 to lities to offer vices, , input anage at will rs to ill help sily w code ting g version quate ead to al users including IT n access as well shed
|
From page 76... ...
76 2.6.1.10.2 Architectural Framework A key consideration from the executive point of view is the role and evolution of authentication in the portal life cycle. Data governance programs are considered a powerful aspect of portal development and use. DOTs can classify all data that the DOT uses in the course of performing its functions. Data governance classifications provide an understanding of the nature of the data, where data live, how to gain access, and who needs access. The architecture behind these programs can be quite advanced, but data governance can simplify the user experience. These are known as reference models. Table 16. Executive level, future trend, and security components. Architectural Elements and Policies Interface Portal interfaces need to use a universal authentication interface (API and UI) Portal interfaces authentication needs to be both attribute and role based. Business Services Portal service need to use a universal authentication interface (real‐time and non‐real‐ time)
|
From page 77... ...
a d 2 T 2 2 D T T 2 I B S D S uthenticatio etermine acc DOT .6.1.11 his section d .5 and is inte .6.1.11.1 Bu OT public po witter, Flickr he DMV pub DMV Rail tr Trans Aviati Mand DOT s .6.1.11.2 Ar nterface usiness ervices ata ources ns, that unde ess and qual Public Websi escribes the nded to com siness Goals rtals appear , and YouTub lic portals an services aveler inform it traveler inf on traveler in atory project trategic plan chitectural Fr Po Po info Po and Po Po Po Po lice Po Po Po Po rstand the at ity of experie te Analysis information t plete the bus to be integra e) to support alysis reveale ation service ormation ser formation se and program and vision do amework Tabl A rtal interface rtal interface rmation rtal interface information rtal may need rtal service ne rtal service ne rtal services m nse applicati rtal needs to rtal needs to rtal needs to rtal needs to tributes of th nce. hat was extra iness cases id ted with man their comm d the presen s vices rvices progress an cuments e 17. DOT pu rchitectural needs to inte needs to allo needs to allo to provided eds to captu eds to captu ay need to i on. store major p log social me store and arc store and arc e role that a cted from th entified dur y social med unication wit ce of the foll d expenditur blic website c Elements an ract with soc w search and w general pu DMV service re user inter re user inter nclude DMV roject progr dia activities hive DOT str hive DMV us person is pla e website co ing the interv ia websites ( h the genera owing: e reporting s omponents.
|
From page 78... ...
78 2.6.1.11.3 Vision Since there was no interview completed on this topic, it is difficult to extrapolate on the future of these DOT services; however, interviewees of the previous 10 topics assumed that social media services will be the predominant way to communicate both inside and outside the DOT. Table 18 shows the list of identified DOT EIP users. These users will be utilized to design the various portal user roles. Table 18. Identified DOT EIP users. DOT EIP users Category Commercial traffic data providers External Construction Contractors External Counties employees External DOT Acquisition Internal DOT Business leaders Internal DOT Content Owners Internal DOT Contractors External DOT Data Governance Team Internal DOT Employees Internal DOT Engineering Internal DOT Executive Internal DOT General Services Personnel Internal DOT Operations Internal DOT Planners Internal DOT Policy team Internal Emergency responders External Engineering Firms External Federal Agencies External General Public External Highway Patrol External Lawyers and Law Firms External Local Law Enforcement External Local Transportation Agencies External News Media External Public Safety Officials External State Employees External University Researchers External
|
From page 79... ...
79 2.6.2 Functional Requirements Table 19 provides a list of DOT EIP functional requirements derived from the previously identified business cases and architectural components. Functional requirements are essentially a way to describe "what the DOT EIP should do." For example, "The DOT EIP shall archive engineering documents." Functional requirements should not be confused with non‐functional requirements that describe "how the DOT EIP should work." For example, "The DOT EIP shall retain engineering documents for 75 years." Functional requirements will be used to establish the goals of a sustainable DOT EIP and assess technologies or approaches to DOT EIP design by reviewing their ability to fulfill the DOT EIP functional requirements (see Task 3) . These functional requirements can later be used as a way to measure progress in the development of a sustainable architecture by reviewing the ability of a DOT EIP to fulfill them. In this section, the DOT EIP is referred to as the "the system" for simplification. Table 19 shows a list of the functional requirements identified. Each functional requirement is traced to one or more of the business cases in a topic. Also, the functional requirements were organized according to the six layers of the DOT EIP framework shown in Figure 38: data layer, data abstraction layer, business services layer, service abstraction layer, interface layer, and policies and management layer. Prioritizing the functional requirements at this stage while assessing DOT EIPs at a very general level would be difficult. Prioritization will mostly depend on a DOT's approach and its needs; these will determine whether certain DOT EIP functions are implemented more quickly than others. Also, sustainable DOT EIPs allow early‐ stage interfaces, services, or data to be stored within the same infrastructure, which makes it challenging to establish which components or functions should be deployed first. Nonetheless, policies and data management requirements (as well as the presence of data, data abstraction, and service abstraction requirements)
|
From page 80... ...
80 Table 19. DOT EIP functional requirements. ID Sustainable DOT EIP functional requirement Business Case Priority Data Layer 1 The system shall allow the ingestion of asset performance data Asset Management and Engineering Services 1 2 The system shall allow the ingestion of new asset data Asset Management and Engineering Services 1 3 The system shall allow the search and review of asset performance data Asset Management and Engineering Services 1 4 The system shall allow the addition of new DOT assets Asset Management and Engineering Services 1 5 The system shall import asset vendor information Asset Management and Engineering Services 1 6 The system shall store and organize asset information according to data governance requirements Asset Management and Engineering Services 1 7 The system shall store and organize asset performance data according to data governance requirements Asset Management and Engineering Services 1 8 The system shall allow the ingestion of external crash data (law enforcement) Asset Management and Engineering Services 1 9 The system shall implement with DOT data governance established roles and privileges Knowledge Management 1 10 The system shall implement the DOT data governance controlled vocabularies and taxonomies Knowledge Management 1 11 The system shall allow the sharing of DOT GIS data GIS and Mapping Services 1 12 The system shall allow the sharing of DOT LIDAR data GIS and Mapping Services 1 13 The system shall ingest vendors imagery data GIS and Mapping Services 1 14 The system shall archive old GIS and LIDAR data according to DOT data governance retention policies GIS and Mapping Services 1 15 The system shall provide real‐time traffic data from traffic sensors Operations and Performance Management 1 16 The system shall provide access traffic sensors data archive Operations and Performance Management 1 17 The system shall archive traffic sensor data Operations and Performance Management 1 18 The system shall cache real‐time traffic sensor data Operations and Performance Management 1 19 The system shall use standardized format to exchange and store traffic sensor data Operations and Performance Management 1 20 The system shall use standardized format to exchange and store traffic camera video and images Operations and Performance Management 1 21 The system shall ingest DOT documents Document and Library Services 1 22 The system shall allow DOT documents to be converted into standard format Document and Library Services 1 23 The system shall allow DOT documents to be inspected automatically to detect indexing, privilege errors or quality issues Document and Library Services 1 24 The system shall use standardized format to exchange and store traffic sensor data Document and Library Services 1
|
From page 81... ...
81 ID Sustainable DOT EIP functional requirement Business Case Priority 25 The system shall log acquisition related communication Bid and Contract Services 1 26 The system shall keep an historical records of successful acquisitions Bid and Contract Services 1 27 The system shall maintain a list of preferred vendors and their information Bid and Contract Services 1 28 The system shall allow details of ongoing bids to be stored and accessed securely Bid and Contract Services 1 29 The system shall log portal network activities IT Services 1 30 The system shall record IT assets performance IT Services 1 31 The system shall store IT assets inventory IT Services 1 32 The system shall log and archive all external users activities External Portal Users 1 33 The portal shall log environmental data analysis results Environmental Services 1 34 The system shall store and display major project progress and expenditure data to the general public DOT public website 1 35 The system shall store and analyze social media activities DOT public website 1 36 The system shall store and archive DOT strategic and vision documents DOT public website 1 37 The system shall store and archive DMV users data, vehicles data and user activity data DOT public website 1 38 The system shall log its user activities All 1 39 The system shall follow DOT Data governance retention policies All 1 40 The system shall allow the ingestion of LIDAR data Asset Management and Engineering Services, GIS and Mapping Services 1 41 The system shall allow the ingestion of GIS data Asset Management and Engineering Services, GIS and Mapping Services, Environmental Services 1 42 The system shall store and organize all DOT asset information Asset Management and Engineering Services, Environmental Services 1 43 The system shall archive traffic camera video and image feed Asset Management and Engineering Services, Operations and Performance Management 1 44 The system shall maintain a catalog of IT assets and component modules IT Services, Environmental Services 1 Service Layer 45 The system shall archive old asset information according to retention policies and maintain searchability Asset Management and Engineering Services 1 46 The system shall allow the creation of asset performance and compliance reports Asset Management and Engineering Services 1 47 The system shall allow the compliance audit of GIS datasets GIS and Mapping Services 1 48 The system shall allow DOT documents to be archived Document and Library Services 1
|
From page 82... ...
82 ID Sustainable DOT EIP functional requirement Business Case Priority 49 The system shall allow the tagging of acquisition request according to DOT data governance requirements Bid and Contract Services 1 50 The system shall perform automatic IT assets security audits IT Services 1 51 The system shall provide tools to easily migrate and convert large amount of data IT Services 1 52 The system shall provide automated IT assets scaling tools IT Services 1 53 The system shall provide a compliance enforcement service IT Services 1 54 The system shall provide a IT resources optimization service IT Services 1 55 The system shall provide an automated provisioning of new or additional IT assets IT Services 1 56 The system shall automatically audit shared DOT content for compliance External Portal Users 1 57 The system shall automatically assess the quality of ingested data Environmental Services 1 58 The system shall support the ingestion of new datasets Environmental Services 1 59 The system shall allow the use of State level authentication Executive Level 1 60 The system shall provide both role based and attribute based authentication service Executive Level 1 61 The system shall provide authentication services All 1 62 The system shall make use of modular IT assets and components IT Services, Environmental Services 1 63 The system shall allow DOT asset information audits Asset Management and Engineering Services 2 64 The system shall log asset modification activities Asset Management and Engineering Services 2 65 The system shall generate GIS layers showing Asset information and asset performance data Asset Management and Engineering Services 2 66 The system shall allow the analysis of multiple GIS datasets GIS and Mapping Services 2 67 The system shall interact with GIS web mapping service from vendors and other agencies GIS and Mapping Services 2 68 The system shall store GIS data while maintaining searchability and analysis capabilities GIS and Mapping Services 2 69 The system shall allow traffic sensor data to be searched using both time and location Operations and Performance Management 2 70 The system shall allow traffic video and camera to be search using both location and time Operations and Performance Management 2 71 The system shall maintain searchability of archived traffic sensor and traffic camera content Operations and Performance Management 2 72 The system shall allow legacy documents to be ingested into DOT document repository automatically Document and Library Services 2 73 The system shall allow archived DOT documents to remain searchable over time Document and Library Services 2 74 The system shall archive acquisition request and activities Bid and Contract Services 2 75 The system shall allow acquisition activities log to be searched and analyzed for compliance Bid and Contract Services 2
|
From page 83... ...
83 ID Sustainable DOT EIP functional requirement Business Case Priority 76 The system shall support communication between acquisition requester and DOT acquisition team Bid and Contract Services 2 77 The system shall allow acquisition request to be augmented with various additional documents Bid and Contract Services 2 78 The system shall generate detailed IT assets cost reports IT Services 2 79 The system shall allow the ingestion of scientific data for Universities or Federal Agencies (USGS seismic data) Environmental Services 2 80 The system shall automatically audit environmental datasets for compliance Environmental Services 2 81 The portal shall provide both automated and ad‐hoc environmental data analysis service Environmental Services 2 82 The portal shall incorporate analytics model in a modular and interchangeable way Environmental Services 2 83 The portal shall support the versioning of model modules Environmental Services 2 84 The system shall provide a service to capture user interests by identifying the way that users navigate public portal DOT public website 2 85 The system shall provide a service to capture user interests by identifying the way that users search public portal DOT public website 2 86 The system shall provide a service to manage DMV services such a vehicle registration and driver license application. DOT public website 2 Interface Layer 87 The system shall allow the search and review of DOT assets information Asset Management and Engineering Services 2 88 The system shall allow its users to receive asset performance based alerts Asset Management and Engineering Services 2 89 The system shall allow asset information to be update using mobile devices Asset Management and Engineering Services 2 90 The system shall stream live asset performance data Asset Management and Engineering Services 2 91 The system shall implement search interfaces using the DOT data governance controlled vocabularies and taxonomies Knowledge Management 2 92 The system shall allow user to personalize their search and review interface Knowledge Management 2 93 The system shall allow GIS based alert messages to be sent GIS and Mapping Services 2 94 The system shall provide a geographical visualization of traffic sensor data Operations and Performance Management 2 95 The system shall provide a geographical visualization of traffic camera Operations and Performance Management 2 96 The system shall provide an interface to register for traffic alerts Operations and Performance Management 2 97 The system shall send traffic alerts to registered users Operations and Performance Management 2 98 The system shall allow DOT documents to be searched by users Document and Library Services 2 99 The system shall allow DOT documents to be searched and reviewed using mobile devices Document and Library Services 2 100 The system shall allow DOT documents to be captured using mobile devices Document and Library Services 2
|
From page 84... ...
84 ID Sustainable DOT EIP functional requirement Business Case Priority 101 The system shall allow DOT user to interface with state bid portal Bid and Contract Services 2 102 The system shall provide a bid advertising interface Bid and Contract Services 2 103 The system shall provide an acquisition request tracking interface Bid and Contract Services 2 104 The system shall provide an acquisition tracking alert service Bid and Contract Services 2 105 The system shall allow for acquisition request status reporting Bid and Contract Services 2 106 The system shall allow acquisition requests to be analyzed and visualized over a period of time Bid and Contract Services 2 107 The system shall allow acquisition requests to be searched and reviews by DOT acquisition team member Bid and Contract Services 2 108 The system shall allow the historical acquisition records to be searched and analyzed Bid and Contract Services 2 109 The system shall provide a IT asset performance management interface IT Services 2 110 The system shall interface with vendor cloud services IT Services 2 111 The system shall provide a IT asset registration interface IT Services 2 112 The system shall provide an IT asset monitoring and alert service IT Services 2 113 The system shall allow external user to search and discover DOT content External Portal Users 2 114 The system shall allow external user to visualize discovered content using GIS interfaces External Portal Users 2 115 The system shall allow external users to search and review DOT content using mobile devices External Portal Users 2 116 The system shall allow GIS DOT content to be downloaded or use directly through web services External Portal Users 2 117 The system shall allow for external users to be alerted when new or updated DOT content is posted External Portal Users 2 118 The portal shall provide alerts whenever new environmental datasets and analytic models are added Environmental Services 2 119 The system shall allow the visualization of GIS data GIS and Mapping Services, Environmental Services 2 120 The system shall provide live video or image feeds from traffic camera Asset Management and Engineering Services, Operations and Performance Management 2 121 The system shall provide access to archived video or image from traffic camera Asset Management and Engineering Services, Operations and Performance Management 2 122 The system shall provide a DMV service interface DOT public website 2 123 The system shall provide an interface to allow general public to access public funded projects progress and information DOT public website 2 124 The system shall provide an interface to allow search and display of rail, transit, aviation and ferry travel information DOT public website 2 125 The system shall provide an interface to interact with social media websites DOT public website 2
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.