<?xml version="1.0"?>
<mods xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mods="http://www.loc.gov/mods/v3" version="3.7" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-7.xsd">
  <titleInfo>
    <title>Simply Park (Semester Unknown) IPRO 365: SimplyParkIPRO365Poster1Sp11</title>
  </titleInfo>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Bredau, Jason</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Bryski, Timothy</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Bubert, Casey</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Bukowska, Angelika</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Byrne, Matthew</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Coates, Allan</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Gonzalez, Julia</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Huynh, Alex</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Ko, Hyunseok</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Mui, Danny</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Ritchie-smith, Robert</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Sahagun, Benjamin</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Shah, Malav</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Trudo, Michelle</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>White, Kenny</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Wicker, Nathan</namePart>
  </name>
  <name>
    <role>
      <roleTerm type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators" valueURI="http://id.loc.gov/vocabulary/relators/cre">creator</roleTerm>
    </role>
    <namePart>Winstanley, Sam</namePart>
  </name>
  <abstract>Efficiency in parking facilities has been set to low standards since self-parking was introduced in the 1950s1. As technology has developed, parking has been left in the past. Drivers are increasingly realizing the problem as they become accustomed to other technology, which increases the efficiency of their lives (eg smartphones). While driving around searching for an open lot, circling a garage for an parking spot, or wandering through garage a looking for a parked car, people have time to ponder the many improvements that should be made to the parking experience. Simply Park: IPRO 365 is taking initiative to seize the possibilities new technologies offer the parking industry. The result should be improved driver experience as well as increased efficiency and profitability of parking facilities. The system will include signs visible to passersby that display the number of vacancies within a parking facility. Once in the parking facility, additional signs will direct drivers to sections of the facility with vacancies. Colored lights above each parking spot will indicate the state of occupancy for quick reference when looking down an aisle. When a driver parks, the ticket they receive at the entrance gate will associate their ticket to the spot they parked in, so when the driver returns to the facility he/she can present his/her ticket to a kiosk which will notify him/her how to get back to his/her car. As the vehicle leaves the ticket association will be reset and displays will update to show one more spot available. Additional interfaces through mobile and internet applications will further expedite the parking process. 1National</abstract>
  <note type="provenance">Submitted by Vishal Patel (vpatel87@iit.edu) on 2011-05-23T15:11:42Z No. of bitstreams: 12 SimplyParkIPRO365BrochureSp11.pdf: 12030561 bytes, checksum: 13052faa41998cef3611d418069433c2 (MD5) SimplyParkIPRO365FinalPresentationSp11.pdf: 977579 bytes, checksum: 464a07a7e9a86ca393b644b8ffbcf58c (MD5) SimplyParkIPRO365MidTermPresentationSp11.pdf: 375780 bytes, checksum: d81379098c050171e5d928c71de405a9 (MD5) SimplyParkIPRO365Poster1Sp11.pdf: 1167762 bytes, checksum: 66005f810108f9957037538a4d9065fc (MD5) SimplyParkIPRO365Poster2Sp11.pdf: 840498 bytes, checksum: 0154827bdacb2615dd5a11575c29ef60 (MD5) SimplyParkIPRO365Poster3Sp11.pdf: 9890750 bytes, checksum: 25134526f3aa622bb2daa59b8673fd0c (MD5) SimplyParkIPRO365Poster4Sp11.pdf: 1814325 bytes, checksum: 03ae52e88eae8be050d2ea77271b6c5a (MD5) SimplyParkIPRO365Poster5Sp11.pdf: 942902 bytes, checksum: 6b82d38c3c20905e7969a4ffcd772d2a (MD5) SimplyParkIPRO365Poster6Sp11.pdf: 129379 bytes, checksum: b44bcb953a3530cf8a1c9b7bb02a23cc (MD5) SimplyParkIPRO365Poster7Sp11.pdf: 466508 bytes, checksum: fffff535e1cd98a62fd1e69f79907a01 (MD5) SimplyParkIPRO365Poster8Sp11.pdf: 127575 bytes, checksum: d0c3eca059ccfb2b76ecdcefbc1b3928 (MD5) SimplyParkIPRO365ProjectPlanSp11.pdf: 606655 bytes, checksum: 9b0b8b8ed9ce52338659cbf0501e2a46 (MD5)</note>
  <note type="provenance">Made available in DSpace on 2011-05-23T15:11:42Z (GMT). No. of bitstreams: 12 SimplyParkIPRO365BrochureSp11.pdf: 12030561 bytes, checksum: 13052faa41998cef3611d418069433c2 (MD5) SimplyParkIPRO365FinalPresentationSp11.pdf: 977579 bytes, checksum: 464a07a7e9a86ca393b644b8ffbcf58c (MD5) SimplyParkIPRO365MidTermPresentationSp11.pdf: 375780 bytes, checksum: d81379098c050171e5d928c71de405a9 (MD5) SimplyParkIPRO365Poster1Sp11.pdf: 1167762 bytes, checksum: 66005f810108f9957037538a4d9065fc (MD5) SimplyParkIPRO365Poster2Sp11.pdf: 840498 bytes, checksum: 0154827bdacb2615dd5a11575c29ef60 (MD5) SimplyParkIPRO365Poster3Sp11.pdf: 9890750 bytes, checksum: 25134526f3aa622bb2daa59b8673fd0c (MD5) SimplyParkIPRO365Poster4Sp11.pdf: 1814325 bytes, checksum: 03ae52e88eae8be050d2ea77271b6c5a (MD5) SimplyParkIPRO365Poster5Sp11.pdf: 942902 bytes, checksum: 6b82d38c3c20905e7969a4ffcd772d2a (MD5) SimplyParkIPRO365Poster6Sp11.pdf: 129379 bytes, checksum: b44bcb953a3530cf8a1c9b7bb02a23cc (MD5) SimplyParkIPRO365Poster7Sp11.pdf: 466508 bytes, checksum: fffff535e1cd98a62fd1e69f79907a01 (MD5) SimplyParkIPRO365Poster8Sp11.pdf: 127575 bytes, checksum: d0c3eca059ccfb2b76ecdcefbc1b3928 (MD5) SimplyParkIPRO365ProjectPlanSp11.pdf: 606655 bytes, checksum: 9b0b8b8ed9ce52338659cbf0501e2a46 (MD5) Previous issue date: 2011-05</note>
  <abstract>Deliverables</abstract>
  <originInfo>
    <dateCreated keyDate="yes">2011</dateCreated>
  </originInfo>
  <originInfo>
    <dateIssued>2011-05</dateIssued>
  </originInfo>
  <identifier type="hdl">http://hdl.handle.net/10560/1948</identifier>
  <language>
    <languageTerm type="code" authority="rfc3066">en</languageTerm>
  </language>
  <subject>
    <topic>Simply Park</topic>
  </subject>
  <typeOfResource authority="coar" valueURI="http://purl.org/coar/resource_type/c_18op">Project deliverable</typeOfResource>
  <physicalDescription>
    <digitalOrigin>born digital</digitalOrigin>
    <internetMediaType>application/pdf</internetMediaType>
  </physicalDescription>
  <accessCondition type="useAndReproduction" displayLabel="rightsstatements.org">In Copyright</accessCondition>
  <accessCondition type="useAndReproduction" displayLabel="rightsstatements.orgURI">http://rightsstatements.org/page/InC/1.0/</accessCondition>
  <accessCondition type="restrictionOnAccess">Open Access</accessCondition>
  <name type="corporate">
    <namePart>IPRO / Interprofessional Projects Program</namePart>
    <affiliation>Illinois Institute of Technology</affiliation>
    <role>
      <roleTerm type="text">Affiliated department</roleTerm>
    </role>
  </name>
</mods>
