You are here

PIA

PIA - Everbridge Mass Notification System (EMNS)

The Everbridge Mass Notification System (EMNS), through Everbridge Inc., will provide mass communication to Volpe Center employees in the event of a crisis, emergency, or issue which necessitates mass notification (weather, power, etc). The methods of communication may include email, telephone, cellular phone, and paging device numbers. The system is located at multiple hosting facilities and is managed and secured by Everbridge, Inc.

PIA - Volpe Centralized Data Repository (VCDR)

The Volpe Centralized Data Repository (VCDR) will provide a consolidated, secured, data storage system that Volpe Center employees and contractors can use to store and generate sensitive records. Volpe Center employees and contractors will transfer their sensitive LAN records to VCDR and, going forward, will create any such records in VCDR. Among other improvements, this will eliminate the need for employees and contractors to individually encrypt each LAN record that contains personally identifiable information (PII).   

The VCDR will be managed by Federal Employees within the Information Technology Division (ITD), and Contractor Support Staff. VCDR accounts will be created based on need; only those employees and contractor personnel who have LAN accounts and handle sensitive information will be VCDR account holders. 

PIA - Volpe Local Area Network (LAN) GS

The Volpe LAN GSS system provides access to required local systems and Wide Area Network (WAN) access to both the Internet and other Government Agencies. The LAN is used by Volpe Center employees and contractors.  

The Volpe LAN is defined as the infrastructure required to support mission functionality including network and security devices, electronic mail resources, and intranet resources to include file servers, workstations, printers, etc. The Volpe LAN is managed by Federal Employees within the Information Technology Division (ITD), and Contractor Support Staff. The ITD is responsible for LAN oversight, while contractor staff provides day to day support under guidance of ITD.

PIA - Pipeline and Hazardous Materials Safety Administration (PHMSA)

The Pipeline and Hazardous Materials Safety Administration (PHMSA), within the Department of Transportation (DOT), is the federal agency charged with the safe and secure movement of almost 1 million daily shipments of hazardous materials by all modes of transportation. The agency also overseas the nation's pipeline infrastructure which accounts for 64 percent of the energy commodities consumed in the United States. The Office of Hazardous Materials Safety (OHMS) is the federal safety authority for the transportation of hazardous materials by air, rail, highway and water.

This website includes OHMS guidance documents, hazmat carriers' special permits and approvals information, reports and incidents summaries, penalty action reports, registration information and forms, the Emergency Response Guidebook for First Responders, Freedom of Information Act requests, and the Hazardous Materials Emergency Preparedness (HMEP) grants program. This site also provides the ability for the public to use electronic filing to reduce the amount of data entered manually from paper submissions, improve data quality, and speed the process for requests for information.

PIA - Third-Party Web Sites and Applications (STD-TP-WEB)

Within the Department of Transportation (DOT), DOT's Office of Chief Information Officer (OCIO), within the Office of the Secretary of Transportation (OST), is responsible for leading DOT's compliance with the Open Government Directive issued by the Office of Management and Budget on December 8, 2009 (OMB Memorandum M-10-06). OCIO and other OST offices (principally, the Office of Public Affairs (OPA) and the Office of General Counsel (OGC)) provide technical, programmatic and legal support for DOT-wide compliance with the Open Government Directive. OMB's Open Government Directive requires agencies to take specific actions to implement the principles of transparency, participation, and collaboration as set forth in the President's Memorandum on Transparency and Open Government, issued January 21, 2009. 

As part of its support function for Open Government, OCIO issued policies (DOT Order 1351.24 "Departmental Web Policy" and DOT Order 1351.33 "Departmental Web-Based Interactive Technologies Policy") regarding use of third-party web sites and applications. These policies permit DOT public engagement and public affairs offices and Information Technology (IT) support personnel to use third-party web sites and applications (i.e., "non-.gov" sites,[1]  such as Facebook, YouTube and Twitter) to provide information and services to the public and to provide social media tools (such as blogs) for members of the public to use to engage with DOT regarding DOT programs. On a "non-.gov" site, the third party that operates the site collects certain mandatory information about users of the site as necessary to operate the social media tools (for example, to register or enroll users to submit comments to the site or to receive information alerts from the site). The third party may also solicit and collect optional information about users of the site for the third party's own commercial purposes. The mandatory and optional information collected by the third party could include personally identifiable information (PII) about individual users. The third party could make some of this PII publicly available to other users of the site (for example, a user's personal email address may appear on the site if the user is using it as his or her public ID; "friending" may reveal some of the user's personal profile information to the user who is "friended"). In addition, individual members of the public may include other PII in their public interactions with the site (such as, by including PII in comments they submit to the site).

PIA - Tiger Collector Reporting Tool (TCRT)

The privacy management process is built upon a methodology that has been developed and implemented in leading companies around the country and globally. The methodology is designed to help ensure that DOT and OST will have the information, tools and technology necessary to manage privacy effectively and employ the highest level of fair information practices while allowing OST to achieve its mission of protecting and enhancing the U.S. transportation system. The methodology is based upon the following steps: 

  •     Establish priority, authority, and responsibility. Appointing a cross-functional privacy management team to ensure input from systems architecture, technology, security, legal, and other disciplines necessary to ensure that an effective privacy management program is developed.
  •     Assess the current privacy environment. This involves interviews with key individuals involved in the WCIS system to ensure that privacy risks are identified, addressed and documented.
  •     Organize the resources necessary for the project's goals. Internal OST resources, along with outside experts, are involved in reviewing the technology, data uses, and associated risks. They are also involved in developing the necessary redress systems and training programs.
  •     Develop the policies, practices, and procedures. The resources identified in the paragraph above work to develop effective policies, practices, and procedures to ensure that fair information practices are complied with. The policies are designed to protect privacy effectively while allowing OST to achieve its mission.
  •     Implement the policies, practices, and procedures. Once the policies, practices, and procedures are developed, they must be implemented. This involves training all individuals who will have access to and/or process personally identifiable information (PII). It also entails working with vendors to ensure that they maintain the highest standard for privacy while providing services to the OST project.
  •     Maintain policies, practices, and procedures. Due to changes in technology, personnel and other aspects of any program, effective privacy management requires that technology and information be available to the privacy management team to ensure that privacy policies, practices, and procedures continue to reflect actual practices. Regular monitoring of compliance is required.
  •     Manage exceptions and/or problems with the policies, practices, and procedures. This step involves the development and implementation of an effective redress and audit system to ensure that any complaints are effectively addressed and corrections made, if necessary.

Pages

Submit Feedback >