<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><PerformancePlanOrReport>   <Name>FACA Committee Purpose &amp; Justification</Name>   <Description>   The information in this plan was imported from the Federal Advisory Committee Act (FACA) database   and transformed into StratML Part 1, Strategic Plan, format.   </Description>   <OtherInformation> Fiscal Year:2011 Committee Type: Scientific Technical Program Advisory Board</OtherInformation>   <StrategicPlanCore>      <Organization>         <Name>Technical Pipeline Safety Standards Committee</Name>         <Acronym>DOT</Acronym>         <Identifier>0a1e033b-5563-44c7-aaa8-abced7fe8f88</Identifier>         <Description>[ Location : (http://stratml.fido.gov/dick/DOTFACA703.xml) ][ Federated Name : (urn:www.dot.gov:agency:19:committee:703:) ][ Agency Name : (Department of Transportation) ][ Agency Acronym : (DOT) ][ Agency Domain : (www.dot.gov) ] [ Agency Web Site : (http://www.dot.gov) ][ Committee Name : (Technical Pipeline Safety Standards Committee) ][ Committee Type : (Scientific Technical Program Advisory Board) ][ Committee Web Site : (http://www.phmsa.dot.gov/pipeline/regs/technical-advisory-comm/TPSSC) ][ Goal? : (yes) ][ Vision? : (yes) ][ Mission? : (yes) ]         </Description>         <Stakeholder>            <Name>Department of Transportation</Name>            <Description>http://www.dot.gov	http://www.phmsa.dot.gov/pipeline/regs/technical-advisory-comm/TPSSC</Description>            <Role>               <Name/>               <Description/>               <RoleType/>            </Role>         </Stakeholder>         <Stakeholder>            <Name>Membership of the Committee is a unique diverse group composed of government, industry, and public members. This mix provides a balance of views reflecting varying interests in pipeline safety. The Committee provides a valuable, independent base of technical knowledge and practicable experience.</Name>            <Description/>            <Role>               <Name/>               <Description/>               <RoleType/>            </Role>         </Stakeholder>      </Organization>      <Vision>         <Description>The Technical Pipeline Safety Committee (TPSSC) was mandated by Section 60115 of Title 49 United States Code to review natural gas pipeline safety standards for technical feasibility, cost effectiveness, reasonableness, and practicability. The Committee provides a valuable, independent, base of technical knowledge and practical experience to supplement limited staff resources at relatively low cost. Since it is composed of government, industry, and public members, the committee serves as a unique forum for give and take, facilitating discussion of complex and often controversial issues. Given the balance of views on the Committee, it can be used as an aid in evaluating conflicting demands placed on us by NTSB, GAO, Congress, and other external stakeholders.</Description>         <Identifier>78d4c946-cfc5-4b4f-b238-3d1061ea24f8</Identifier>      </Vision>      <Mission>         <Description>The Technical Pipeline Safety Standards Committee (TPSSC) advises PHMSA/OPS on porposed safety standards on gas pipelines. Federal law requires PHMSA/OPS to submit cost-benefit analyses and riskassessment information on proposed safety standards to the advisory committees. The TPSSC evaluates the merits of the data provided and the methods used. The Committee reviews each proposed safety standards to determin the technical feasibility and cost effectiveness of the proposal.</Description>         <Identifier>e03f8581-f210-404a-9dfb-f65a80c555e3</Identifier>      </Mission>      <Value>         <Name/>         <Description/>      </Value>      <Goal>         <Name/>         <Description>The Committee provides a mechanism for bringing together experts with technical knowledge and practical experience who represent all constituent groups (government, industry, public) having an interest in pipeline safety. Discussing proposed standards and pipeline safety issues with these experts convened at the same time in an open and frank forum is both economical and productive, leading to a stronger, more proactive pipeline safety program. No other readily available source of similar advice exists within the governmentor industry.</Description>         <Identifier>e3102b97-0297-4551-bb9c-b9919bee5c3b</Identifier>         <SequenceIndicator/>         <OtherInformation/>         <Stakeholder>            <Name/>            <Description/>            <Role>               <Name/>               <Description/>               <RoleType/>            </Role>         </Stakeholder>         <Objective>            <Name/>            <Description/>            <Identifier>43e72a74-837d-4f4e-adc4-ee1d15ceea64</Identifier>            <SequenceIndicator/>            <OtherInformation/>            <Stakeholder>               <Name/>               <Description/>               <Role>                  <Name/>                  <Description/>                  <RoleType/>               </Role>            </Stakeholder>            <PerformanceIndicator IndicatorType="" ValueChainStage="">               <Identifier>42e274b8-285d-4f13-b684-423a77380273</Identifier>               <MeasurementDimension/>               <UnitOfMeasurement/>               <OtherInformation/>               <Relationship RelationshipType="">                  <Identifier/>                  <Name/>                  <Description/>               </Relationship>               <MeasurementInstance>                  <TargetResult>                     <Description/>                     <NumberOfUnits/>                     <StartDate/>                     <EndDate/>                  </TargetResult>                  <ActualResult>                     <Description/>                     <NumberOfUnits/>                     <StartDate/>                     <EndDate/>                  </ActualResult>               </MeasurementInstance>            </PerformanceIndicator>         </Objective>      </Goal>   </StrategicPlanCore>   <AdministrativeInformation>      <StartDate>2010-10-01</StartDate>      <EndDate>2011-09-30</EndDate>      <PublicationDate>2013-07-09</PublicationDate>      <Source>http://explore.data.gov/resource/datasets/c5i3-bb9j</Source>   </AdministrativeInformation>   <Submitter>      <FirstName>Gannon (J.)</FirstName>      <LastName>Dick</LastName>      <PhoneNumber/>      <EmailAddress>gannon_dick@yahoo.com</EmailAddress>   </Submitter></PerformancePlanOrReport>
