Appendix III Integrated Work Plan Version 0.2 - Joint Planning and ...
Appendix III Integrated Work Plan Version 0.2 - Joint Planning and ...
Appendix III Integrated Work Plan Version 0.2 - Joint Planning and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IWP COMMENT INSTRUCTIONS<br />
APPENDIX <strong>III</strong><br />
<strong>Appendix</strong> <strong>III</strong><br />
<strong>Integrated</strong> <strong>Work</strong> <strong>Plan</strong> <strong>Version</strong> <strong>0.2</strong><br />
Comment Instructions<br />
www.jpdo.gov/IWP<br />
The <strong>Joint</strong> <strong>Plan</strong>ning <strong>and</strong> Development Office (JPDO) was established by Congress to transform<br />
our air transportation system through the realization of the Next Generation Air Transportation<br />
System (NextGen). Congress understood that NextGen will only be achieved through the<br />
coordinated efforts of the government <strong>and</strong> the aviation industry.<br />
To this end, the JPDO with its partner departments, agencies <strong>and</strong> industry partners have been<br />
working collaboratively to develop a baseline NextGen <strong>Integrated</strong> <strong>Work</strong> <strong>Plan</strong> (IWP). The IWP<br />
is intended to become a master planning document representing the efforts of public <strong>and</strong> private<br />
aviation stakeholders to formulate needed changes <strong>and</strong> improvements. The IWP describes the<br />
current underst<strong>and</strong>ing of the research, development, <strong>and</strong> implementation results needed to<br />
achieve the NextGen vision.<br />
The JPDO released IWP <strong>Version</strong> <strong>0.2</strong> on February 15, 2008, for review by the public as well as<br />
by JPDO government partners <strong>and</strong> the aviation industry. Individuals <strong>and</strong> organizations are<br />
invited to provide comments about <strong>Version</strong> <strong>0.2</strong> using the formatted comment form described in<br />
this document <strong>and</strong> located on www.jpdo.gov/IWP . JPDO intends to review <strong>and</strong> adjudicate<br />
submitted comments as appropriate for future IWP versions.<br />
FILE DOWNLOAD, SAVING, AND E-MAILING INSTRUCTIONS<br />
Download:<br />
Save File:<br />
Download the preformatted Excel spreadsheet by clicking on<br />
www.jpdo.gov/IWP.<br />
Create a file name using the following naming convention:<br />
IWP <strong>0.2</strong> Comments.xls<br />
Example: Avionics Inc IWP <strong>0.2</strong> Comments.xls<br />
Email:<br />
After completing the comment form, e-mail the file to<br />
9-AWA-ATO-JPDO-Partnership@faa.gov<br />
Comments are due by March 28, 2008.<br />
<strong>Version</strong> <strong>0.2</strong> <strong>Appendix</strong> <strong>III</strong>-1 <strong>Joint</strong> <strong>Plan</strong>ning <strong>and</strong> Development Office
IWP COMMENT INSTRUCTIONS<br />
APPENDIX <strong>III</strong><br />
DATA ENTRY INSTRUCTIONS<br />
A sample comment form is provided below, followed by instructions.<br />
Commenter Information <br />
Name:<br />
Organization:<br />
Contact Information:<br />
Please review comment instructions prior to using this form.<br />
Originator IWP Chapter Element Type Element # Suggested Change <br />
John Doe ATO-W ES: Executive Summary Narr Line # 422 Sample Comment: Add a comma<br />
Jane Doe Ch 4: Weather Information Services Key Decision Points<br />
(KD)<br />
beside the word "<strong>and</strong>".<br />
80 Add DOC as an OCR.<br />
Commenter Information <br />
Enter the name, organization <strong>and</strong> contact information of the person who will serve as the main<br />
point of contact for an organization, or enter as an individual.<br />
Originator <br />
Enter the main originator of each comment into the Originator field. If the overall comment<br />
form is from an individual, the originator would the individual’s name (i.e., Jane Doe). If the<br />
form is from an organization, submit the originator’s name as well as their sub-organization (i.e.,<br />
John Doe, ATO-W). This identifier will be used in the adjudication of comments, <strong>and</strong> will be<br />
included in the posting of the comment adjudication document.<br />
IWP Chapter<br />
For each comment, enter the relevant IWP Chapter. Use the pull-down feature to select from<br />
available options.<br />
Element Type<br />
Comments can be submitted against specific types of information within the IWP:<br />
• Narrative line number (Narr #),<br />
• Operational Improvement (OI)<br />
• Enabler (EN)<br />
• Research (R)<br />
• Development (D)<br />
• Policy Issue or Need (PI)<br />
• Key Decision (KD)<br />
• <strong>Plan</strong>ned Investment (IN)<br />
<strong>Version</strong> <strong>0.2</strong> <strong>Appendix</strong> <strong>III</strong>-2 <strong>Joint</strong> <strong>Plan</strong>ning <strong>and</strong> Development Office
INTEGRATED WORK PLAN FOR THE<br />
NEXT GENERATION AIR TRANSPORTATION SYSTEM (NEXTGEN)<br />
APPENDIX <strong>III</strong><br />
For each comment, enter the relevant Element Type. Use the pull-down feature to select from<br />
available options.<br />
Element #<br />
For each comment, enter the relevant Element # that aligns with the Element Type. For<br />
each example, if a comment is concerning line number 1234, the Element Type would be Narr#<br />
<strong>and</strong> the Element # would be 1234. For a comment on OI-0321, the Element Type would be EN<br />
<strong>and</strong> the Element # would be 321. For planning data elements, it is not necessary to enter the<br />
prefix with the Element #.<br />
Suggested Change <br />
For each comment, submit a suggested change. A suggested change can be a modification to<br />
text, or an addition, deletion, or modification to an assignment, date or dependency.<br />
To suggest a change to the text, please submit the original text as stated in the document, as well<br />
as proposed specific wording <strong>and</strong> accompanying rationale. An example of a suggested text<br />
change comment is given below:<br />
Change the following statement “The future of our nation’s ability to<br />
move people <strong>and</strong> goods in a safe, secure, efficient <strong>and</strong> environmentally<br />
responsible manner depends upon the successful implementation of the<br />
Next Generation Air Transportation System (NextGen).” to “The future<br />
of our nation’s ability to move goods <strong>and</strong> people in an environmentally<br />
responsible, safe, secure <strong>and</strong> efficient manner depends upon the<br />
successful implementation of the Next Generation Air Transportation<br />
System (NextGen).” The rationale for this suggested change is based on<br />
the opinion that the environmental issues of NextGen must be<br />
considered before other goals.<br />
Suggested changes within a planning data element should follow a similar structure:<br />
“For OI-1900, delete EN–1234 <strong>and</strong> add EN–5678. The rationale for this<br />
change is that EN-1234 succeeds EN-5678.”<br />
or<br />
“For OI-5900, change the OPR from DOT to DHS. The rationale for<br />
this change is this Enabler is strategically aligned within the mission<br />
statement of the DHS more so than the DOT.”<br />
Each organization should provide a consolidated set of comments to prevent redundant <strong>and</strong><br />
conflicting comments. General editorial comments are discouraged.<br />
<strong>Version</strong> <strong>0.2</strong> <strong>Appendix</strong> <strong>III</strong>-3 <strong>Joint</strong> <strong>Plan</strong>ning <strong>and</strong> Development Office
INTEGRATED WORK PLAN FOR THE<br />
NEXT GENERATION AIR TRANSPORTATION SYSTEM (NEXTGEN)<br />
APPENDIX <strong>III</strong><br />
ADDITIONAL INSTRUCTIONS FOR JPDO PARTNER DEPARTMENTS AND AGENCIES<br />
AND THE NEXTGEN INSTITUTE<br />
Each organization listed in Table 1 is requested to provide a single point of contact (POC) to<br />
work with the JPDO IWP team. The POC is responsible for coordinating the response <strong>and</strong><br />
submitting a consolidated single set of comments from the organization. It is requested that<br />
the POCs be selected <strong>and</strong> names submitted to the JPDO IWP team (contact list is below) by<br />
February 22.<br />
• DOC<br />
• DOD<br />
• DOT<br />
• DHS<br />
Table 1 JPDO Organizations<br />
• FAA<br />
• NASA<br />
• OSTP<br />
• NextGen Institute<br />
The POCs will be contacted to attend a workshop to review <strong>and</strong> discuss the commenting process<br />
within their respective organization. In addition, the designated POC’s name <strong>and</strong> contact<br />
information will be posted to the Knowledge Sharing Network (KSN) in order to encourage<br />
interaction between organizations prior to submitting comments to the JPDO IWP team.<br />
IWP VERSION <strong>0.2</strong> COMMENT ADJUDICATION<br />
Comments will be reviewed <strong>and</strong> adjudicated by the JPDO according to the following categories:<br />
• Accepted: The comment is accepted <strong>and</strong> will be incorporated into a future version of the<br />
IWP.<br />
• Accepted with Change: The intent of the comment or a portion of the comment is<br />
accepted <strong>and</strong> will be partially incorporated into a future version of the IWP.<br />
• Hold for Analysis: The comment has a complex impact on the overall functions,<br />
schedule <strong>and</strong> dependencies of the IWP, <strong>and</strong> will require further analysis to determine the<br />
extent of the overall impact. The comment will be reviewed <strong>and</strong> maintained for potential<br />
consideration in future versions of the IWP.<br />
• Declined: Comments that do not provide specific guidance or do not fit within the overall<br />
scope, goals or objectives of the JPDO <strong>and</strong> NextGen programs will be declined.<br />
IWP VERSION <strong>0.2</strong> REVIEW TEAM CONTACT LIST<br />
If you have any questions about the comment form, please contact the following:<br />
Primary: Matt Clark Tel: 202 624 3244 clark_matthew@bah.com<br />
Secondary: Fern<strong>and</strong>o Pinzon Tel: 202 624 3229 pinzon_fern<strong>and</strong>o@bah.com<br />
Lacina Kone Tel: 301 996 7700 kone_lacina@bah.com<br />
Tonya Whitson Tel: 240 475 9000 whitson_tonya@bah.com<br />
Reminder: Email the completed comment form to<br />
9-AWA-ATO-JPDO-Partnership@faa.gov by March 28, 2008.<br />
Thank you.<br />
<strong>Version</strong> <strong>0.2</strong> <strong>Appendix</strong> <strong>III</strong>-4 <strong>Joint</strong> <strong>Plan</strong>ning <strong>and</strong> Development Office