CPT: Difference between revisions

From CIRPwiki
Jump to navigation Jump to search
*>Anonymous
m (34 revisions: Import from Fault)
(13 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Channel Portfolio Tool (CPT) ==
=''' Channel Portfolio Tool (CPT)'''=
 
[[Image:CPT-Wiki Main Page.png|500px|thumb|right|Channel Portfolio Tool]]
 
CPT is a web-based, decision-support tool designed to help USACE operations personnel analyze the extent to which maintained navigation channels are used by commercial shipping. Analyses can be conducted for individual channels, or for a grouping of channels treated as a single project. Additionally, USACE planning personnel can use CPT to extract historical data concerning region-to-region commodity movements and consolidated statements of traffic for arbitrary listings of projects and channels.
 




Line 13: Line 18:


CPT is developmental software that is updated frequently.
CPT is developmental software that is updated frequently.
br style=clear:both /


='''CPT User's Guide'''=  
='''CPT User's Guide'''=  


*[[CPT_General_Layout|General Layout]]
*[[CPT_General_Layout|General Layout]]
**[[CPT_General_Layout#Setting_the_level_of_analysis|Setting the Level of Analysis (Reach, Project, District, Division)]]
**[[CPT_General_Layout#Setting_the_level_of_analysis_(Reach,_Project,_District,_Division)|Setting the Level of Analysis (Reach, Project, District, Division)]]
**[[CPT_General_Layout#Selection_of_items_to_be_ranked_and/or_analyzed|Selection of Items to be Ranked and/or Analyzed]]
**[[CPT_General_Layout#Selection_of_items_to_be_ranked_and/or_analyzed|Selection of Items to be Ranked and/or Analyzed]]
**[[CPT_General_Layout#Explanation_of_preferences|Explanation of Preferences]]
**[[CPT_General_Layout#Explanation_of_preferences|Explanation of Preferences]]
**[[CPT_General_Layout#Viewing_of_Rankings_Roll-ups_and_Flow_Tables|Viewing of Rankings, Roll-ups, and Flow Tables]]
**[[CPT_General_Layout#Viewing_of_Rankings,_Roll-ups,_and_Flow_tables|Viewing of Rankings, Roll-ups, and Flow Tables]]
*[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project|Comparing Sub-reaches within a Single Navigation Project]]
*[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project|Comparing Sub-reaches within a Single Navigation Project]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Selecting_Sub-reaches|Selecting Sub-reaches]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Selecting_Sub-reaches|Selecting Sub-reaches]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Setting_Preferences|Setting Preferences]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Setting_Preferences|Setting Preferences]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Viewing_Ranking_Tables|Viewing Ranking Tables]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Viewing_Rankings_tables|Viewing Ranking Tables]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Exporting_Ranking_Tables_to_Microsoft_Excel|Exporting Ranking Tables to Microsoft Excel]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Exporting_Rankings_tables_to_Microsoft_Excel|Exporting Ranking Tables to Microsoft Excel]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Exporting_to_and_Viewing_of_Rankings_in_Google_Earth|Exporting to and Viewing of Rankings in Google Earth]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Exporting_to_and_Viewing_of_Rankings_in_Google_Earth|Exporting to and Viewing of Rankings in Google Earth]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Viewing_Rankings_Charts_and_Saving_to_File_or_to_Clipboard|Viewing Rankings Charts and Saving to File or to Clipboard]]
**[[CPT_Comparing_Sub-reaches_within_a_Single_Navigation_Project#Viewing_Rankings_Charts_and_Saving_to_File_or_to_Clipboard|Viewing Rankings Charts and Saving to File or to Clipboard]]
*[[Viewing_Details_of_a_Single_Sub-reach|Viewing Details of a Single Sub-reach]]
*[[Viewing_Details_of_a_Single_Sub-reach|Viewing Details of a Single Sub-reach]]
**[[Viewing_Details_of_a_Single_Sub-reach|Selection of Sub-reach from Rankings Table]]
**[[Viewing_Details_of_a_Single_Sub-reach#Selection_of_sub-reach_from_Rankings_table|Selection of Sub-reach from Rankings Table]]
**[[Viewing_Details_of_a_Single_Sub-reach|Explanation of Traffic Roll-up]]
**[[Viewing_Details_of_a_Single_Sub-reach#Explanation_of_Traffic_Rollup|Explanation of Traffic Roll-up]]
**[[Viewing_Details_of_a_Single_Sub-reach|Explanation of Reach Details]]
**[[Viewing_Details_of_a_Single_Sub-reach#Explanation_of_Reach_Details|Explanation of Reach Details]]
**[[Viewing_Details_of_a_Single_Sub-reach|Exporting to and Viewing in Microsoft Excel]]
**[[Viewing_Details_of_a_Single_Sub-reach#Exporting_to_and_viewing_in_Microsoft_Excel|Exporting to and Viewing in Microsoft Excel]]
**[[Viewing_Details_of_a_Single_Sub-reach|Draft Profiles of Tons and $-Value; Saving to File or Clipboard]]
**[[Viewing_Details_of_a_Single_Sub-reach#Draft_profiles_of_tons_and_$-value;_saving_to_file_or_clipboard|Draft Profiles of Tons and $-Value; Saving to File or Clipboard]]
*[[Viewing_and_Explanation_of_Flow_Tables|Viewing and Explanation of Flow Tables]]
*[[Viewing_and_Explanation_of_Flow_Tables|Viewing and Explanation of Flow Tables]]
**[[Viewing_and_Explanation_of_Flow_Tables|Selection of Single Sub-reach for Flow Analysis]]
**[[Viewing_and_Explanation_of_Flow_Tables#Selection_of_single_sub-reach_for_Flow_analysis|Selection of Single Sub-reach for Flow Analysis]]
**[[Viewing_and_Explanation_of_Flow_Tables|Tips for Faster Query Times and KML Settings]]
**[[Viewing_and_Explanation_of_Flow_Tables#Tips_for_faster_query_times_and_.kml_settings|Tips for Faster Query Times and KML Settings]]
**[[Viewing_and_Explanation_of_Flow_Tables|Exporting Flow Table to and Viewing in Google Earth]]
**[[Viewing_and_Explanation_of_Flow_Tables#Exporting_Flow_table_to_and_viewing_in_Google_Earth|Exporting Flow Table to and Viewing in Google Earth]]
**[[Viewing_and_Explanation_of_Flow_Tables|Exporting Flow Table to Microsoft Excel, Explanation of Fields]]
**[[Viewing_and_Explanation_of_Flow_Tables#Exporting_Flow_table_to_Microsoft_Excel,_explanation_of_fields|Exporting Flow Table to Microsoft Excel, Explanation of Fields]]
**[[Viewing_and_Explanation_of_Flow_Tables|Viewing Details for Entries in Flow Table, and Exporting to Microsoft Excel]]
**[[Viewing_and_Explanation_of_Flow_Tables#Viewing_details_for_entries_in_Flow_table,_and_exporting_to_Microsoft_Excel|Viewing Details for Entries in Flow Table, and Exporting to Microsoft Excel]]
*[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects|Comparing Sub-reaches Across Multiple Navigation Projects]]
*[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects|Comparing Sub-reaches Across Multiple Navigation Projects]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Selecting_sub-reachs_via_ITL_GEAR_portal|Selecting Sub-reaches via the ITL Gear Portal]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Selecting_sub-reaches_via_ITL_GEAR_portal|Selecting Sub-reaches via the ITL Gear Portal]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Removing_unwanted_sub_reaches_from_Reach_Selection_menu|Removing Unwanted Sub-Reaches from Reach Selection Munu]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Removing_unwanted_sub_reaches_from_Reach_Selection_menu|Removing Unwanted Sub-Reaches from Reach Selection Munu]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Tips_for_faster_query_times|Tips for Faster Query Times]]
**[[Comparing_Sub-reaches_Across_Multiple_Navigation_Projects#Tips_for_faster_query_times|Tips for Faster Query Times]]
Line 54: Line 60:
**[[Comparing_Projects,_Districts,_and_Divisions#Viewing_of_details_for_entries_in_Rankings_table|Viewing of Details for Entries in Rankings Table]]
**[[Comparing_Projects,_Districts,_and_Divisions#Viewing_of_details_for_entries_in_Rankings_table|Viewing of Details for Entries in Rankings Table]]
**[[Comparing_Projects,_Districts,_and_Divisions#Explanation_of_Details_tables_and_charts|Explanation of Details Tables and Charts]]
**[[Comparing_Projects,_Districts,_and_Divisions#Explanation_of_Details_tables_and_charts|Explanation of Details Tables and Charts]]
 
*[[Ranking_of_items_with_shoaling_effects_included|Ranking of Items with Shoaling Effects Included]]
='''Comparing Projects, Districts, and Divisions'''=
**[[Ranking_of_items_with_shoaling_effects_included#Explanation_of_Default_Shoaling|Explanation of Default Shoaling]]
==''Selection of entities to be ranked''==
**[[Ranking_of_items_with_shoaling_effects_included#Interpretation_of_Rankings|Interpretation of Rankings]]
As described in Section 2.2, the CPT user can specify the entities (Divisions, Districts, Projects, or Reaches) to be analyzed by selecting the respective tab on the CPT Home page.  This section will present several examples of using this feature to quickly compare waterborne commerce figures at the Project, District, and Division levels, respectively.
**[[Ranking_of_items_with_shoaling_effects_included#Using_Details_views_to_better_understand_final_Rankings|Using Details View to Better Understand Final Rankings]]
 
After choosing Project-level analysis from the CPT Home screen, choose LRD from the Division menu and then select the Buffalo District (LRB).  Next, select all LRB Projects, as shown in Figure 42.
 
[[Image:Figure42_ProjectSelection.jpg|400px|thumb|left|Fig. 42 – CPT Project Selection within Buffalo District]]
 
br style=clear:both /
 
==''Tips for faster query times''==
Under the Preferences tab, select 2007 only to help with query times.  When selecting Projects which much higher tonnage levels than those in LRB, it might be necessary to limit the query further by choosing a subset of traffic types and/or commodities.
 
==''Viewing of details for entries in Rankings table''==
Once Preferences have been saved, click the Rankings tab to see the LRB Projects compared to one another, as shown in Figure 43.
 
[[Image:Figure43_ProjectRankings.jpg|400px|thumb|left|Fig. 43 – LRB Project Rankings for 2007]]
 
br style=clear:both /
 
As indicated by the absence of tabs, the CPT Flow and Rollup features are not yet available for the Project, District, and Division levels.  Subsequent versions of CPT will likely incorporate the Rollup feature at these higher levels, while the Flow feature will remain at the Reach level of analysis for the foreseeable future.  As with other Rankings tables discussed in previous sections, any entry can be clicked on for further details.  Figures 44-46 show the tables and charts on the Details page for Cleveland, OH.
 
[[Image:Figure44_ProjectDetails.jpg|400px|thumb|left|Fig. 44 – Details tables for Cleveland, OH, 2007]]
 
br style=clear:both /
 
==''Explanation of Details tables and charts''==
The figures in these tables are equivalent to those that would be obtained were the user to perform a Rollup query on all of the individual sub-reaches within the Cleveland project.
 
The draft profile charts for the Cleveland Project in Figs. 45 and 46 are interesting because they show that most of the $-value of cargo uses the deeper drafts available at Cleveland (26 - 27 ft).  Furthermore, this high $-value is due to a comparably small amount of imported manufactured metals and flat-rolled iron and steel products, as can be determined by sorting the Harbor Details table by $-value.  This information places a higher degree of importance on the deeper drafts at Cleveland Harbor than might otherwise be given.
 
[[Image:Figure45_ProjectDraftProfile.jpg|400px|thumb|left|Fig. 45 – Draft Profile for Tonnage at Cleveland, OH, 2007]]
 
br style=clear:both /
 
[[Image:Figure46_ProjectDraft$-value.jpg|400px|thumb|left|Fig. 46 – Draft Profile for $-value at Cleveland, OH, 2007]]
 
br style=clear:both /
 
Just as a demonstration of the insights that can be quickly gleaned using CPT to analyze the USACE navigation portfolio at the Division level, Figures 47 – 49 show the draft profile charts for tonnage for SWD, NAD, and LRD, respectively.  Note that in each instance the Tonnage Mode under Preferences was set to Docked so as to get a better indication of cargo movements into, out of, and within each Division.
 
[[Image:Figure47_DivisionDraftProfileTons.jpg|400px|thumb|left|Fig. 47 – Division Draft Profile for Tonnage for SWD]]
 
br style=clear:both /
 
[[Image:Figure48_DivisionDraftProfileTons.jpg|400px|thumb|left|Fig. 48 – Division Draft Profile for Tonnage for NAD]]
 
br style=clear:both /
 
[[Image:Figure49_DivisionDraftProfileTons.jpg|400px|thumb|left|Fig. 49 – Division Draft Profile for Tonnage for LRD]]
 
br style=clear:both /
 
='''Ranking of items with shoaling effects included'''=
So far the examples presented in this guide have not included shoaling considerations, just to keep things straightforward while introducing the overall layout and functionality of CPT.  However, for practical decision-support applications of CPT towards OM budget development, shoaling information needs to be included to help achieve rational allocation of funding.  This section will describe how CPT can include shoaling considerations along with commerce data when ranking channels for maintenance dredge funding.
 
==''Explanation of Default Shoaling''==
Because controlling depths for the thousands of channel sub-reaches in the USACE navigation portfolio vary due to local hydraulic conditions, it is a significant information management challenge to include all of this data within comprehensive decision-support package for OM dredging.  The CPT development plan calls for several mechanisms to be employed for inclusion of up to date shoaling conditions and channel limiting depths, including linkages to automated channel survey analysis packages, online historical datasets, and manual user upload of channel conditions via the CPT interface. 
Until these additions have been developed, CPT allows for inclusion of shoaling effects through use of a default shoaling parameter.  As discussed in Section 2.3.1, the default shoaling feature assumes a uniform shoaling rate across the entire grouping of selected channels (or Projects, Districts, etc.).  The practical effect of employing this feature is that entities are now ranked in terms of the tons or $-value transiting at the deepest of maintained depths.
 
==''Interpretation of Rankings''==
To help demonstrate the effect of shoaling on the Rankings compiled by CPT, return to the Charleston Harbor, SC example used previously in Section 2.  Use the Reach level analysis tab and select all of the sub-reaches in Charleston Harbor.  Under the Preferences tab, uncheck the Ignore Shoaling box and set the Default Shoaling rate to 3 ft/yr by simply typing a “3” in the input box (do not enter units).  Select only year 2007 to ensure consistency with the previous example, and save Preferences.  The Rankings tab will reveal the table shown in Figure 50.  Comparison of this table with that shown in Fig. 13 shows significant differences in the rankings once the focus is shifted to the deepest 3-ft of maintained depth in each channel. 
 
[[Image:Figure50_RankingsWith3ftShoaling.jpg|400px|thumb|left|Fig. 50 – Rankings of Reaches in Charleston Harbor with 3 ft of shoaling assumed, 2007]]
 
br style=clear:both /
 
Another useful comparison to the previous example using Charleston Harbor is to generate .kml overlays for viewing in Google Earth.  Use the default KML Settings under Preferences and export the Rankings table to KML.  The resulting Google Earth view is shown in Fig. 51.
 
[[Image:Figure51_RankingsWith3ftShoalingGoogle.jpg|400px|thumb|left|Fig. 51 – Charleston Harbor Reach Rankings with 3 ft of shoaling assumed, 2007]]
 
br style=clear:both /
 
It is very interesting to note that the Entrance Channel and other sub-reaches that were prominently shown in Fig. 18 when all cargo was included are now of secondary importance, in terms of tons transiting in the deepest 3 feet of maintained depth.
 
==''Using Details views to better understand final Rankings''==
Selection of the entry for Shipyard River in the Rankings table in Fig. 50, which carries roughly 1.8 million tons of cargo that would be disrupted by 3-ft of shoaling, will reveal the draft profile shown in Fig. 52.
 
[[Image:Figure52_DraftProfile.jpg|400px|thumb|left|Fig. 52 – Draft profile for Shipyard River in Charleston Harbor, SC, 2007]]
 
br style=clear:both /

Revision as of 21:56, 8 September 2011

Channel Portfolio Tool (CPT)

File:CPT-Wiki Main Page.png
Channel Portfolio Tool

CPT is a web-based, decision-support tool designed to help USACE operations personnel analyze the extent to which maintained navigation channels are used by commercial shipping. Analyses can be conducted for individual channels, or for a grouping of channels treated as a single project. Additionally, USACE planning personnel can use CPT to extract historical data concerning region-to-region commodity movements and consolidated statements of traffic for arbitrary listings of projects and channels.


POC: Dr. Kenneth Ned Mitchell br\Kenneth.n.mitchell@usace.army.mil br\601-634-2022 br\US Army Engineer Research and Development Center (ERDC) br\Coastal and Hydraulics Lab (CHL)

Active URL (CAC authentication required): https://cpt.usace.army.mil/

Developmental URL (Corps machines only): https://itlgis01.usace.army.mil/CPTIWRWeb

CPT is developmental software that is updated frequently. br style=clear:both /

CPT User's Guide

Retrieved from "https://cirpwiki.info/index.php?title=CPT&oldid=7297"