Appendix III Integrated Work Plan Version 0.2 - Joint Planning and ...

IWP COMMENT INSTRUCTIONS
APPENDIX III
Appendix III
Integrated Work Plan Version 0.2
Comment Instructions
www.jpdo.gov/IWP
The Joint Planning and Development Office (JPDO) was established by Congress to transform
our air transportation system through the realization of the Next Generation Air Transportation
System (NextGen). Congress understood that NextGen will only be achieved through the
coordinated efforts of the government and the aviation industry.
To this end, the JPDO with its partner departments, agencies and industry partners have been
working collaboratively to develop a baseline NextGen Integrated Work Plan (IWP). The IWP
is intended to become a master planning document representing the efforts of public and private
aviation stakeholders to formulate needed changes and improvements. The IWP describes the
current understanding of the research, development, and implementation results needed to
achieve the NextGen vision.
The JPDO released IWP Version 0.2 on February 15, 2008, for review by the public as well as
by JPDO government partners and the aviation industry. Individuals and organizations are
invited to provide comments about Version 0.2 using the formatted comment form described in
this document and located on www.jpdo.gov/IWP . JPDO intends to review and adjudicate
submitted comments as appropriate for future IWP versions.
FILE DOWNLOAD, SAVING, AND E-MAILING INSTRUCTIONS
Download:
Save File:
Download the preformatted Excel spreadsheet by clicking on
www.jpdo.gov/IWP.
Create a file name using the following naming convention:
IWP 0.2 Comments.xls
Example: Avionics Inc IWP 0.2 Comments.xls
Email:
After completing the comment form, e-mail the file to
9-AWA-ATO-JPDO-Partnership@faa.gov
Comments are due by March 28, 2008.
Version 0.2 Appendix III-1 Joint Planning and Development Office

IWP COMMENT INSTRUCTIONS
APPENDIX III
DATA ENTRY INSTRUCTIONS
A sample comment form is provided below, followed by instructions.
Commenter Information
Name:
Organization:
Contact Information:
Please review comment instructions prior to using this form.
Originator IWP Chapter Element Type Element # Suggested Change
John Doe ATO-W ES: Executive Summary Narr Line # 422 Sample Comment: Add a comma
Jane Doe Ch 4: Weather Information Services Key Decision Points
(KD)
beside the word "and".
80 Add DOC as an OCR.
Commenter Information
Enter the name, organization and contact information of the person who will serve as the main
point of contact for an organization, or enter as an individual.
Originator
Enter the main originator of each comment into the Originator field. If the overall comment
form is from an individual, the originator would the individual’s name (i.e., Jane Doe). If the
form is from an organization, submit the originator’s name as well as their sub-organization (i.e.,
John Doe, ATO-W). This identifier will be used in the adjudication of comments, and will be
included in the posting of the comment adjudication document.
IWP Chapter
For each comment, enter the relevant IWP Chapter. Use the pull-down feature to select from
available options.
Element Type
Comments can be submitted against specific types of information within the IWP:
• Narrative line number (Narr #),
• Operational Improvement (OI)
• Enabler (EN)
• Research (R)
• Development (D)
• Policy Issue or Need (PI)
• Key Decision (KD)
• Planned Investment (IN)
Version 0.2 Appendix III-2 Joint Planning and Development Office

INTEGRATED WORK PLAN FOR THE
NEXT GENERATION AIR TRANSPORTATION SYSTEM (NEXTGEN)
APPENDIX III
For each comment, enter the relevant Element Type. Use the pull-down feature to select from
available options.
Element #
For each comment, enter the relevant Element # that aligns with the Element Type. For
each example, if a comment is concerning line number 1234, the Element Type would be Narr#
and the Element # would be 1234. For a comment on OI-0321, the Element Type would be EN
and the Element # would be 321. For planning data elements, it is not necessary to enter the
prefix with the Element #.
Suggested Change
For each comment, submit a suggested change. A suggested change can be a modification to
text, or an addition, deletion, or modification to an assignment, date or dependency.
To suggest a change to the text, please submit the original text as stated in the document, as well
as proposed specific wording and accompanying rationale. An example of a suggested text
change comment is given below:
Change the following statement “The future of our nation’s ability to
move people and goods in a safe, secure, efficient and environmentally
responsible manner depends upon the successful implementation of the
Next Generation Air Transportation System (NextGen).” to “The future
of our nation’s ability to move goods and people in an environmentally
responsible, safe, secure and efficient manner depends upon the
successful implementation of the Next Generation Air Transportation
System (NextGen).” The rationale for this suggested change is based on
the opinion that the environmental issues of NextGen must be
considered before other goals.
Suggested changes within a planning data element should follow a similar structure:
“For OI-1900, delete EN–1234 and add EN–5678. The rationale for this
change is that EN-1234 succeeds EN-5678.”
or
“For OI-5900, change the OPR from DOT to DHS. The rationale for
this change is this Enabler is strategically aligned within the mission
statement of the DHS more so than the DOT.”
Each organization should provide a consolidated set of comments to prevent redundant and
conflicting comments. General editorial comments are discouraged.
Version 0.2 Appendix III-3 Joint Planning and Development Office

INTEGRATED WORK PLAN FOR THE
NEXT GENERATION AIR TRANSPORTATION SYSTEM (NEXTGEN)
APPENDIX III
ADDITIONAL INSTRUCTIONS FOR JPDO PARTNER DEPARTMENTS AND AGENCIES
AND THE NEXTGEN INSTITUTE
Each organization listed in Table 1 is requested to provide a single point of contact (POC) to
work with the JPDO IWP team. The POC is responsible for coordinating the response and
submitting a consolidated single set of comments from the organization. It is requested that
the POCs be selected and names submitted to the JPDO IWP team (contact list is below) by
February 22.
• DOC
• DOD
• DOT
• DHS
Table 1 JPDO Organizations
• FAA
• NASA
• OSTP
• NextGen Institute
The POCs will be contacted to attend a workshop to review and discuss the commenting process
within their respective organization. In addition, the designated POC’s name and contact
information will be posted to the Knowledge Sharing Network (KSN) in order to encourage
interaction between organizations prior to submitting comments to the JPDO IWP team.
IWP VERSION 0.2 COMMENT ADJUDICATION
Comments will be reviewed and adjudicated by the JPDO according to the following categories:
• Accepted: The comment is accepted and will be incorporated into a future version of the
IWP.
• Accepted with Change: The intent of the comment or a portion of the comment is
accepted and will be partially incorporated into a future version of the IWP.
• Hold for Analysis: The comment has a complex impact on the overall functions,
schedule and dependencies of the IWP, and will require further analysis to determine the
extent of the overall impact. The comment will be reviewed and maintained for potential
consideration in future versions of the IWP.
• Declined: Comments that do not provide specific guidance or do not fit within the overall
scope, goals or objectives of the JPDO and NextGen programs will be declined.
IWP VERSION 0.2 REVIEW TEAM CONTACT LIST
If you have any questions about the comment form, please contact the following:
Primary: Matt Clark Tel: 202 624 3244 clark_matthew@bah.com
Secondary: Fernando Pinzon Tel: 202 624 3229 pinzon_fernando@bah.com
Lacina Kone Tel: 301 996 7700 kone_lacina@bah.com
Tonya Whitson Tel: 240 475 9000 whitson_tonya@bah.com
Reminder: Email the completed comment form to
9-AWA-ATO-JPDO-Partnership@faa.gov by March 28, 2008.
Thank you.
Version 0.2 Appendix III-4 Joint Planning and Development Office