|
|
| (406 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | =OnePager 360 Import of Data from Oracle Primavera P6 for Version 7.1 (P371-4_0_1_6-71-09232021.docx)=
| |
| − |
| |
| | ==Introduction== | | ==Introduction== |
| | | | |
| − | The purpose of this article is to put in one place as much information as possible for Oracle Primavera P6 users about how OnePager 360 '''Standalone''' is used to create OnePager charts and how OnePager 360 '''Standalone''' handles data '''imported '''from Oracle Primavera P6.
| + | This article is focused on using the ''' Column Splitting''' feature with OnePager Bundle '''Standalone''' and '''imported''' Asana '''source plans'''. |
| | | | |
| − | This article focuses on two major topics:
| + | ==About Splitting and Parsing Fields== |
| | | | |
| − | :1) Importing Oracle Primavera P6 data into OnePager 360 '''Standalone'''.
| + | The OnePager '''column splitting''' feature allows you to '''duplicate task bars''' when a task in your Asana '''source plan''' is assigned to '''multiple resources''' (or anything else). Because assignments from Asana often are '''comma-delimited''', this feature enables OnePager to '''parse the comma-delimited list''' and '''create a unique task bar''' for each instance in the '''comma-separated''' list. |
| | | | |
| − | :2) OnePager 360 '''Standalone’s''' handling of specific Oracle Primavera P6 '''Column''' data once those data are imported.
| + | ===Split Resource Names Example=== |
| | | | |
| − | ==About Importing Oracle Primavera P6 Data to OnePager 360 Standalone==
| + | Say you want to use '''color-codes''' on task bars/milestone symbols based upon your Asana '''source plan’s Assigned to''' column as shown below: |
| | | | |
| − | OnePager 360 '''Standalone''' '''imports '''data from Oracle Primavera P6 '''source plans''' in three (3) formats: (1) '''XML formatted '''files (extracted from '''ZIP formatted''' files), (2) '''ZIP formatted '''files, and (3) '''XER formatted '''files. When processed by OnePager 360 '''Standalone''', OnePager looks for '''Activity names''', '''start dates''', and '''finish dates''' at a minimum and attempts to '''map''' any fields found in the Oracle Primavera P6 '''imported''' data to meaningful field names that can be used for the creation of OnePager charts.
| + | <center>[[File:P72-24_5_3-72-(1)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(1)-11022023.png</center> |
| | | | |
| − | ===Exported Oracle Primavera P6 XML Formatted, ZIP Formatted, or XER Formatted Files===
| + | Some of the entries in the '''Assigned to''' column consist of multiple, '''comma-separated''' items and some tasks only used one '''resource'''. Without the '''column splitting''' feature, a chart '''created''' from these data and assigned task bar/milestone symbol '''colors''' based upon the '''Assigned to''' column looks like this: |
| | | | |
| − | Before considering how OnePager 360 '''Standalone imports source plan''' data from Oracle Primavera P6, it may be efficient here to review how Oracle Primavera P6 '''exports source plan''' information. For the purposes of considering Oracle Primavera P6 '''imports '''to OnePager 360 '''Standalone''', OnePager 360 accepts three (3) formats: '''XML formatted''' files, '''ZIP formatted '''files, and '''XER formatted''' files.
| + | <center>[[File:P72-24_5_3-72-(5)-11272023.png]]</center> |
| | + | <center>P72-24_5_3-72-(5)-11272023.png</center> |
| | | | |
| − | ====Exported XML Formatted Files====
| + | OnePager, in this case, treats the '''entire string''' as an individual '''Assigned to''' value. To provide more flexibility in displaying task bars that have '''multiple resources''' assigned, OnePager supports the concept of a '''column splitting'''. This feature recognizes '''comma-separated''' values in a '''designated column''' and '''creates a separate task bar''' for each of the '''comma-separated''' values. |
| | | | |
| − | '''XML formatted''' files contain the greatest number of Oracle Primavera P6 column options and is typically the format most '''exported''' to OnePager 360 '''Standalone'''. You can '''export '''an '''XML formatted''' file directly to OnePager 360 by unchecking or turning '''OFF '''the '''Export all project level layouts''' checkbox in the '''Export '''form’s '''File Name''' control group. Then you can use the '''File Name '''dropdown button to access the list of previously created and saved '''XML formatted '''files as shown below:
| + | ===Enabling Splitting=== |
| | | | |
| − | <center>[[File:P71-4_0_1_6-71-(1H)-09212021.png]]</center>
| + | To use this feature requires turning '''ON''' the feature in the Asana '''Template Properties''' form you intend to use to make the chart. The setting must be turned '''ON''' before the chart is created so launch OnePager Bundle from the '''desktop icon''', click the '''NEW''' button on the '''OnePager Bundle Start''' form to access the '''OnePager choices''' form, '''select''' your Asana '''source plan''', and type in the chart's '''title''' as shown here: |
| − | <center>P71-4_0_1_6-71-(1H)-09212021.png</center>
| + | |
| | | | |
| − | Unchecking the '''Export all project level layouts''' checkbox to '''OFF''' assures that the '''exported '''file is in the '''XML format''' and the file name has the '''.xml''' suffix appended. Once the Oracle Primavera P6 '''export''' process is completed, OnePager 360 can '''import '''the file as an '''XML formatted '''file for use in creating your chart.
| + | <center>[[File:P72-24_5_3-72-(2A)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2A)-11022023.png</center> |
| | | | |
| − | ====Exported ZIP Formatted Files====
| + | When you click the '''Next>''' button at the bottom of the form, OnePager accesses the second page of the '''OnePager choices''' form shown below: |
| | | | |
| − | The '''default''' setting for the '''Export all project level layouts''' checkbox is checked '''ON''' meaning that Oracle Primavera P6 by '''default''' '''exports ZIP formatted '''files into a '''Save File''' area reserved for '''.ZIP formatted''' files. The option is shown in the example below:
| + | <center>[[File:P72-24_5_3-72-(2AA)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2AA)-11022023.png</center> |
| | | | |
| − | <center>[[File:P71-4_0_1_6-71-(1I)-09212021.png]]</center>
| + | Clicking the '''Edit current template''' button accesses the current '''Template Properties''' form. Navigate to the '''Field Mappings''' tab on the form, check the '''Enable splitting on:''' checkbox to '''ON''' and (in this example) select the '''Assigned To''' column from the dropdown list provided. The results are shown here: |
| − | <center>P71-4_0_1_6-71-(1I)-09212021.png</center>
| + | |
| | | | |
| − | Checking the '''Export all project level layouts''' checkbox '''ON''' assures that the '''exported '''file is in the '''ZIP format''' and the file name has the '''.zip''' suffix appended. Once the Oracle Primavera P6 '''export''' process is completed, OnePager 360 can '''import '''the file as a '''ZIP formatted '''file, '''extract '''the '''XML formatted '''file, and use the '''XML formatted data''' to create your chart.
| + | <center>[[File:P72-24_5_3-72-(2AAA)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2AAA)-11022023.png</center> |
| | | | |
| − | ====Exported XER Formatted Files====
| + | Click the '''Save and use''' button to complete the process and close the current '''Template Properties''' form returning you to the second page of the '''OnePager choices''' form show above. |
| | | | |
| − | Initiating the '''export '''of an '''XER formatted''' file has a different starting point in Oracle Primavera P6 but the '''export '''process follows similar steps as described above and arrives at the '''Export '''form shown below where the '''Export all project level layouts''' checkbox is '''not present''':
| + | ===Split Resources in the Chart=== |
| | | | |
| − | <center>[[File:P71-4_0_1_6-71-(1J)-09212021.png]]</center>
| + | Clicking the '''Create new chart''' button completes the process and creates the chart with the '''column splitting''' feature in use. The chart with '''splitting''' looks like this: |
| − | <center>P71-4_0_1_6-71-(1J)-09212021.png</center>
| + | |
| | | | |
| − | Following the '''XER format export '''process to the step shown above assures that the data are '''exported''' in the '''XER format'''. When the Oracle Primavera P6 '''export''' process is completed, OnePager 360 can '''import '''the file directly as a '''XER formatted '''file and use the '''XER formatted data''' to create your chart.
| + | <center>[[File:P72-24_5_3-72-(2)-11022023.png]]</center> |
| | + | <center>P72-24_5_3-72-(2)-11022023.png</center> |
| | | | |
| − | ====Reference Links to More Information on Exporting Oracle Primavera P6 Data to OnePager 360====
| + | In the chart with '''column splitting''' shown above, there are now several more task bars in the '''Chart Editor''' than there were before. The task bar for '''Plate Movement''' is now '''split into two (2) separate task bars''', one for each of the '''two resources assigned'''. The task bar for '''Centrifugal Barrier''' is now '''split into three (3) separate task bars''', one for each of the '''three resources''' that were assigned to this task in the Asana '''source plan'''. Each of the '''resources''' has a unique '''color''' assigned. Each of the '''resources''' appears by itself in the '''Legend'''. The '''Legend title''' shows the '''column name''' that is used for '''splitting the columns'''. |
| | | | |
| − | For detailed information on '''exporting XML formatted''', '''ZIP formatted''', and '''XER formatted '''files from Oracle Primavera P6, please see the sub-section in this article at: [[Using Oracle Primavera P6 Source Plans with OnePager 360 Version 7.1#Exporting XML Formatted, ZIP Formatted, and XER Formatted Files from Oracle Primavera P6 to OnePager 360 Standalone | Exporting XML Formatted, ZIP Formatted, and XER Formatted Files from Oracle Primavera P6 to OnePager 360 Standalone]] 3.0.3.1-71.
| + | With this feature, you can use '''column splitting''' just like any other column by using the dropdowns in the '''Template Properties''' form or '''Chart Properties''' form to assign '''colors, highlight task bars and milestone symbols, and to define and label rows and swimlanes'''. |
| | | | |
| − | ===Selecting Activities for Import into OnePager 360 Standalone=== | + | ==Splitting Resources and Task Links== |
| | | | |
| − | Once OnePager 360 '''Standalone '''has '''imported '''either one of the Oracle Primavera P6 file formats, OnePager 360 looks for an '''imported''' field (called a '''Flag field''') that can be used to control whether an '''Activity''' should be '''imported''' and subsequently used in the creation or update of a chart. The '''Flag field''' usually is a '''text field''' in Oracle Primavera P6 containing the word '''Yes''' if the '''Activity''' is to be '''imported''' or '''No''' or left '''blank''' if the '''Activity''' is not to be '''imported'''. Our recommendation is that you should refrain from importing more than 50 '''Activities''' from your Oracle Primavera P6 '''source plan''' to avoid cluttering the OnePager chart. Finally, OnePager 360 '''Standalone''' '''imports''' all '''WBS Element '''data found in an '''XML formatted''', '''ZIP formatted''', or '''XER formatted '''file.
| + | When task bars with '''Data-Driven''' or manual '''Task Links''' are '''split''', the '''Task Links''' ('''Data-Driven''' and manual) are '''not shown'''. Further, the '''Task Links''' that are now '''hidden''' and '''do not''' have entries in the '''Where are My Links?''' form. |
| − | | + | |
| − | An example of an Oracle Primavera P6 '''source plan''' based on the '''BlueGrass Project Plan''' used elsewhere in this '''Wiki''' is shown below with the column '''Flag20''' indicating the '''import Flag''' field:
| + | |
| − | | + | |
| − | <center>[[File:P71-3_0_3_2-71-(1)-06022021.png]]</center>
| + | |
| − | <center>P71-3_0_3_2-71-(1)-06022021.png</center>
| + | |
| − | | + | |
| − | To control which '''Activities''' are '''imported''' by OnePager 360 '''Standalone''' as task bars, specify the Oracle Primavera P6 '''User Defined Field (UDF) column''' as used above where the Oracle Primavera P6 '''User Defined field''' named '''Flag20 '''was added as a '''text column''' and the '''Activities''' that are to be '''import''' have this '''column’s''' contents set to '''Yes''' for each '''Activity''' to import.
| + | |
| − | | + | |
| − | Any '''UDF''' or text type column can be used for this purpose as long as the selected column’s contents are '''Yes''' or '''No'''. For the purpose of illustrations in this '''Wiki''', the '''Flag20 UDF''' is used and is incorporated into the Oracle Primavera P6 '''source plans''' as shown in the '''P6 Columns '''form shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(1G)-09202021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1G)-09202021.png </center>
| + | |
| − | | + | |
| − | When making your first chart, we strongly recommend that you select 50 or fewer '''Activities'''. Please note that OnePager 360 is shipped with a number of fully populated '''templates''' that are based on the Oracle Primavera P6 '''source plan''' used in the '''Tutorial''' also shipped with the product – BlueGrass Project Plan. Note that three field heading types must always be present: '''Activity Name''',''' Start''',''' and End'''.
| + | |
| − | | + | |
| − | This discussion continues at this link: [[Using Oracle Primavera P6 Source Plans with OnePager 360 Version 7.1#Launching OnePager 360 | Using Oracle Primavera P6 Source Plans with OnePager 360 - Launching OnePager 360]] 3.0.3.1-71.
| + | |
| − | | + | |
| − | ====Activity Selection Option (1): Select All Tasks====
| + | |
| − | | + | |
| − | Oracle Primavera P6 '''source plans''' like the one shown above with 73 '''Activities''' and a '''WBS Element''' structure, results in a very large OnePager chart usually not suitable for detailed schedule conversations. Accordingly, we do not recommend '''importing '''more than 50 '''Activities''' so that the resulting chart is a useful one page rendering of the '''source plan'''.
| + | |
| − | | + | |
| − | ====Activity Selection Option (2): Select Tasks with ‘Yes’ in field:====
| + | |
| − | | + | |
| − | As mentioned above, one method for telling OnePager 360 '''Standalone '''which '''Activities''' to '''import '''is to use a '''Flag''' '''column'''. As shown in the previous section, the Oracle Primavera P6 '''source plan''' has a '''User Defined Field '''named '''Flag20''' and the word '''Yes''' is typed into the contents of the '''Flag20 cell''' for each '''Activity''' '''imported '''into OnePager 360 '''Standalone'''. Here is an illustration of the '''OnePager choices''' form where a '''Flag column''' is used to select '''Activities''' from the '''source plan''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(1A)-06282021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1A)-06282021.png </center>
| + | |
| − | | + | |
| − | When this is done for the '''source plan '''shown above, and other appropriate settings are made for OnePager 360, the resulting chart looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P71-3_0_3_1-71-(11A)-06072021.png]]</center>
| + | |
| − | <center>P71-3_0_3_1-71-(11A)-06072021.png</center>
| + | |
| − | | + | |
| − | ====Using the Select task with ‘Yes’ in field: Activities (Non-Summary) Option:====
| + | |
| − | | + | |
| − | If you want to display all '''Non-Summary Activities''' in one chart, which may be very large, choose the '''Activities (Non-Summary) '''option in the '''OnePager choices '''form shown here:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(5)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(5)-06212021.png </center>
| + | |
| − | | + | |
| − | When this '''task selection''' option is selected the chart, as we mentioned, might be quite long as in the example shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(6)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(6)-06212021.png </center>
| + | |
| − | | + | |
| − | The above chart shows all '''Activities''' and the '''start''' and '''finish milestones''' defined in the '''source plan'''.
| + | |
| − | | + | |
| − | ====Using the Select task with ‘Yes’ in field: Critical Option:====
| + | |
| − | | + | |
| − | There is '''Critical''' option available in the '''Select task with ‘Yes’ in field''' radio button option as shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(3)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(3)-06212021.png </center>
| + | |
| − | | + | |
| − | When the '''Critical''' '''Task Selection''' option is used, OnePager 360 '''Standalone''' examines the '''imported '''Oracle Primavera P6 '''source plan''' and displays all '''Activities''' and '''WBS Elements '''that are on the '''Critical Path''' as shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(4)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(4)-06212021.png </center>
| + | |
| − | | + | |
| − | ===Selecting WBS Elements for Import into OnePager 360 Standalone===
| + | |
| − | | + | |
| − | You may want to create OnePager 360 charts that only display '''WBS Elements''' for the purpose of addressing the highest organization of your program or project. To do this, go to the '''Task Selection '''sub-section of the '''OnePager choices '''form, click the '''Select task with ‘Yes’ in field''' radio button, and click the dropdown button in the adjacent window to access the dropdown list as shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(1)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1)-06212021.png </center>
| + | |
| − | | + | |
| − | Now click the '''WBS Items (Summary) '''option in the above dropdown and continue with the process of creating the chart. When you create the chart using the '''WBS Elements '''for the '''swimlane labels''' the chart looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(2)-06212021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(2)-06212021.png </center>
| + | |
| − | | + | |
| − | ==Missing Fields, Field Headers, or Misspelled Field Headings==
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone''' also checks '''field headings''' when '''importing''' data in '''UPDATE''' mode. If the '''field''' was used in previous '''snapshots''' for any purpose, OnePager 360 '''Standalone''' checks to assure that the new '''import''' for the '''snapshot''' has those same '''fields'''. When OnePager 360 '''Standalone''' cannot find the expected '''fields''', one or more '''field heading''' names are missing or blank, the '''field heading''' is recognizably misspelled, or the '''data type''' is different from the previous snapshot, OnePager 360 provides a '''warning message''' as shown in the example below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_7-71-(4)-08302021.png]]</center>
| + | |
| − | <center>P71-4_0_1_7-71-(4)-08302021.png</center>
| + | |
| − | | + | |
| − | This can occur when you inadvertently attempt to '''update''' a chart from the incorrect Oracle Primavera P6 '''source plan''' file or the desired Oracle Primavera P6 '''source plan''' was altered to the extent that OnePager 360 '''Standalone''' cannot find the '''fields''' needed to accomplish the '''UPDATE''' functions. You are given two choices when the message above is displayed:
| + | |
| − | | + | |
| − | ===Continue with missing field(s)===
| + | |
| − | | + | |
| − | By selecting the '''Continue…''' button, the '''import''' proceeds. OnePager 360 '''Standalone''' blanks some values that it cannot find. '''Note:''' The results can be unexpected.
| + | |
| − | | + | |
| − | ===Go back and fix field(s)===
| + | |
| − | | + | |
| − | Selecting the '''Go back…''' button tells OnePager 360 '''Standalone''' to '''stop''' the '''import''' process. You can now correct the Oracle Primavera P6 '''source plan''' or select another one and start the '''UPDATE''' process again.
| + | |
| − | | + | |
| − | ==Using Conditional Import Rules to Make Selections of Activities and/or WBS Elements==
| + | |
| − | | + | |
| − | For OnePager users who '''import source plans '''from Microsoft Project, Microsoft Excel, and Smartsheet, the typical method for selecting tasks ('''Activities''') from the '''source plan '''is to define one or more '''Boolean fields''' in the '''source plan '''and code them with a '''Yes''' or '''No/blank '''to indicate whether the task ('''Activity''') should be '''imported'''. For Oracle Primavera P6 '''source plans''' there are no '''Boolean columns''' per se. This situation is overcome by the Oracle Primavera P6 user defining a '''User Defined Field '''('''UDF''') as a '''text type column''' and coding these '''text field/fields''' with '''Yes/No '''or '''1/0 '''or '''Yes/blank''' to indicate which task ('''Activity''') should be '''imported'''. This procedure is documented above.
| + | |
| − | | + | |
| − | The alternative to defining '''User Defined Fields''' described above is to use the OnePager 360 '''Conditional Import Feature'''. This feature is described in the following sub-sections with examples.
| + | |
| − | | + | |
| − | ===The Conditional Import Feature for Making Activity and/or WBS Element Selections===
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone '''has a feature which supports making '''Activity''' and/or '''WBS Element''' selections on the basis of various properties of '''Activities''' and '''WBS Elements'''. This is called the '''Conditional Import feature'''.
| + | |
| − | | + | |
| − | Before discussing the application of the '''Conditional Import feature''' to Oracle Primavera P6 '''Activity''' and '''WBS Element''' selection, we recommend that you read the article on this subject at: [[Conditional Import for Version 7.1 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-71.
| + | |
| − | | + | |
| − | ===Using the Select tasks by custom filter Option:===
| + | |
| − | | + | |
| − | You can use the '''Conditional Import feature''' to fine tune the '''Activities''' and/or '''WBS Elements''' you want to '''import'''. Assuming that you’re familiar with the concepts of '''Conditional Import''', the '''Conditional Import Rules '''form can be accessed by selecting the '''Select tasks by custom filter: '''radio button as shown in the illustration below. Using the '''Conditional Import Rules '''form as shown here, it is possible to select '''Activities''' between '''Planned Start''' and '''Planned Finish dates''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(9A)-06282021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(9A)-06282021.png </center>
| + | |
| − | | + | |
| − | When the above '''Conditional Import rules''' are used in the selection process, the resulting chart looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(9)-06282021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(9)-06282021.png </center>
| + | |
| − | | + | |
| − | The illustration created above includes '''Activities''' and '''WBS Elements''' within the '''Planned Start/Planned Finish dates''' included in the '''Conditional Import Rules''' form. To exclude '''WBS Elements''', an additional rule is needed. The '''Conditional Import Rules '''form below shows how this additional rule is constructed:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10)-06282021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10)-06282021.png</center>
| + | |
| − | | + | |
| − | Any Oracle Primavera P6 '''column''' found in your '''source plan '''can be used as a field in a '''Conditional Import rule'''.
| + | |
| − | | + | |
| − | Any field can be used to formulate a '''Conditional Import rule''' as shown in the example below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(7)-06282021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(7)-06282021.png</center>
| + | |
| − | | + | |
| − | In the illustration above, the first '''Conditional Import rule''' specifies that '''only WBS Items (Summary) Elements''' are to be '''imported'''. The two following '''Conditional Import rules''' assure that '''WBS Elements '''between the '''dates''' of 9/7/2018 and 12/12/2018 are only '''imported '''and used to create the chart. When the chart with only '''WBS Elements '''is created, it looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(8)-06282021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(8)-06282021.png</center>
| + | |
| − | | + | |
| − | ===Considerations When Using P6 Activity Columns with Conditional Import Rules===
| + | |
| − | | + | |
| − | OnePager 360 has a multitude of features that can easily take Oracle Primavera P6 '''source plan '''data and construct '''Gantt charts''' that are very suitable to support your schedule conversation needs. This section covers topics that you should know about when it is necessary to construct OnePager 360 charts using more than the '''Activity Name''', '''Start''', and '''Finish dates''' to create a '''Gantt chart'''. The sub-sections that follow cover these topics.
| + | |
| − | | + | |
| − | ====Oracle Primavera P6 Columns Imported Through XML Formatted and XER Formatted Files ====
| + | |
| − | | + | |
| − | '''Importing''' Oracle Primavera P6 information into OnePager 360 '''Standalone '''is done by first '''exporting''' either an Oracle Primavera P6 '''XER formatted '''file or '''XML formatted''' file which can then be processed by OnePager 360 '''Standalone'''. The two file types '''exported '''from Oracle Primavera P6 do not contain the same information. Therefore, it is important to know what information is contained in each file type so that your OnePager 360 chart can display what you need to communicate in your schedule conversations.
| + | |
| − | | + | |
| − | A list of Oracle Primavera P6 '''columns''' contained in the '''XML formatted''' and '''XER formatted '''file types can be found in the article at: [[Oracle Primavera P6 Columns Available to OnePager 360 for Version 7.1 | Oracle Primavera P6 Columns Available to OnePager 360]] 29.1.1-71.
| + | |
| − | | + | |
| − | ====Activity and WBS Element Selection Using the OnePager choices Form====
| + | |
| − | | + | |
| − | The first several major sections of this article covered in general how to select '''Activities''' and '''WBS Elements''' for inclusion in your chart. This section provides more detail on how this required step can be accomplished in the most efficient manner.
| + | |
| − | | + | |
| − | When OnePager 360 '''Standalone '''is '''importing Activities''' from an Oracle Primavera P6 '''XML formatted '''or''' XER formatted''' file, OnePager follows the options you selected in the '''OnePager choices''' form’s '''Task Selection '''section as shown below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(1A)-06282021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1A)-06282021.png</center>
| + | |
| − | | + | |
| − | Typically OnePager users define''' Boolean flag fields''' in their '''source plans''' and populate the cells for the '''Activities''' they wish to '''import '''with '''Boolean '''options such as '''Yes/No''', '''Yes/blank''', '''YES/NO''', '''TRUE/FALSE''', '''T/F''', or '''1/0'''. Oracle Primavera P6 does not support '''Boolean fields''' per se. That is, there is no '''Column''' in Oracle Primavera P6 that is a '''Boolean''' type '''column.''' To deal with this, OnePager 360 '''Standalone''' interprets '''text''', '''integer''', and '''numeric''' fields as '''Boolean '''fields for the purpose of '''Activity''' selection if the following conventions are followed.
| + | |
| − | | + | |
| − | ====Text Fields Used as Boolean Fields in Oracle Primavera P6====
| + | |
| − | | + | |
| − | In illustrations used in the first several sections in this article, the Oracle Primavera P6 '''text '''field '''Flag20''' is created as a '''User Defined Field''' of type '''text'''. OnePager 360 '''Standalone''' as it '''imports''' the '''XML formatted '''or''' XER formatted''' file interprets the '''Column headers''', their '''column''' type, and their cell contents to get an overall picture of the '''source plan'''. When it finds a '''text '''field whose contents are either '''Yes/No''', '''Yes/blank''', '''YES/NO''', '''TRUE/FALSE''', '''T/F''', or '''1/0''', OnePager 360 '''Standalone '''interprets the cell’s contents as '''Boolean'''.
| + | |
| − | | + | |
| − | In the illustration above, '''Flag20''' is an Oracle Primavera P6 '''text field''' whose contents happen to be populated with '''Yes/blank''' as shown in the first illustration at the beginning of this article. When OnePager 360 '''Standalone''' recognizes this configuration, it adds the '''Flag20 field '''to the dropdown list associated with the second radio button in the '''Task Selection '''sub-section of the '''OnePager choices''' form.
| + | |
| − | | + | |
| − | ====Integer Fields Used as Flag Fields in Oracle Primavera P6====
| + | |
| − | | + | |
| − | To use an Oracle Primavera P6 '''integer field''' as a '''flag '''field, its contents must have '''1’s''' in those cells that are intended to be '''imported '''as '''Activities'''. '''Activities''' that you do not wish to '''import''' can either be left '''blank''' or populated with '''0’s'''.
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone''' does not include the Oracle Primavera P6 '''integer field’s''' name in the dropdown list associated with the second radio button in the '''Task Selection '''sub-section of the '''OnePager choices''' form. Accordingly, if you choose to use an '''integer field''' for '''Activity''' selection purposes, you will need to use the '''Conditional Import Rules '''feature as described in the named sub-section in this article.
| + | |
| − | | + | |
| − | ====Numeric Fields Used as Flag Fields in Oracle Primavera P6====
| + | |
| − | | + | |
| − | '''Numeric fields''', fields with contents that contain an '''integer and decimal fraction''', are eligible to become '''flag''' fields when their contents are either '''1.0''' or '''0.0'''. However, such fields are not picked up by OnePager 360 '''Standalone''' as a '''flag field''' as discussed above for Oracle Primavera P6 '''text fields'''. Therefore, we do not recommend that '''Numeric fields''' be used for the purpose of general '''Activity''' selection. That said, it is still useful to consider '''Numeric fields''' for '''Activity''' selection if the values contained in these '''Numeric field’s''' cells need to be used for decision making on which '''Activities''' should be '''imported'''.
| + | |
| − | | + | |
| − | ==OnePager Chart Representation of Specific Oracle Primavera P6 XML Formatted and XER Formatted Data==
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone''' provides additional fields for use in your charts that are '''constructed from''' data '''imported '''from either your '''XML formatted '''or '''XER formatted''' files. These fields are provided in OnePager 360 '''Standalone '''for Oracle Primavera P6 '''source plans '''so that you can use all the features of OnePager when designing your charts.
| + | |
| − | | + | |
| − | There are eight (8) specific OnePager 360 '''Standalone '''fields that can be used with both '''XML formatted''' and '''XER formatted''' files. These fields are:
| + | |
| − | | + | |
| − | :* '''Activities (Non-Summary)'''
| + | |
| − | :* '''Activity % Complete'''
| + | |
| − | :* '''Duration (computed)'''
| + | |
| − | :* '''Level “x” summary ID'''
| + | |
| − | :* '''Level “x” summary name'''
| + | |
| − | :* '''ObjectID'''
| + | |
| − | :* '''Outline Level'''
| + | |
| − | :* '''WBS Item (Summary)'''
| + | |
| − | | + | |
| − | There are nine (9) specific OnePager 360 '''Standalone '''fields that can be used '''only''' with '''XML formatted '''files. These fields are:
| + | |
| − | | + | |
| − | :* '''BL Project Start '''– Project Baseline Start Date
| + | |
| − | :* '''BL Project Finish '''-- Project Baseline Finish Date
| + | |
| − | :* '''“[User Baseline Name1]” Finish''' – User Baseline 1 Finish Date
| + | |
| − | :* '''“[User Baseline Name1]” Start '''– User Baseline 1 Start Date
| + | |
| − | :* '''“[User Baseline Name2]” Finish '''– User Baseline 2 Finish Date
| + | |
| − | :* '''“[User Baseline Name2]” Start '''– User Baseline 2 Start Date
| + | |
| − | :* '''“[User Baseline Name3]” Finish '''– User Baseline 3 Finish Date
| + | |
| − | :* '''“[User Baseline Name3]” Start '''– User Baseline 3 Start Date
| + | |
| − | :* '''Primary Resource'''
| + | |
| − | | + | |
| − | In the above list there are two sets of '''XML formatted fields''' that apply to Oracle Primavera P6 '''baseline''' fields. The first two correspond to the names given to the '''Project Baseline Start/Finish '''dates. These two fields are always present in the various dropdown lists when an '''XML formatted '''file is '''imported'''. Oracle Primavera P6 supports up to three (3) '''User Baselines''' and OnePager 360 '''Standalone '''can recognize these '''start/finish '''date names and make them available for use in your charts. The '''User Baseline Name1''' through '''3 '''are placed in the dropdown lists when the corresponding '''baseline start/finish dates''' for these '''User Baselines '''are '''imported'''.
| + | |
| − | | + | |
| − | '''Baseline '''data are '''exported''' only in '''XML formatted files''' based on the selections made at the time of the '''export '''operation. OnePager 360 '''Standalone''' can access the '''Project Baseline Start/Finish '''dates as well as up to three (3) '''User Baseline Start/Finish Dates'''. OnePager 360 '''Standalone '''captures the '''Baseline Names''' from the '''XML formatted '''file '''export '''process as shown in the Oracle Primavera P6 forms below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(1C)-09132021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1C)-09132021.png</center>
| + | |
| − | | + | |
| − | The illustration above shows the '''Project Baseline '''with a name of '''BlueGrass Project Baseline''' and two '''User Baselines '''with names '''BlueGrass Project – B1''' and '''BlueGrass Project – B2''', respectively. It is these names that are available in OnePager for various uses such as in '''text columns''' or in '''mapping '''a particular '''baseline''' to graphics in the chart as shown below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34C)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34C)-09202021.png</center>
| + | |
| − | | + | |
| − | ===OnePager 360 Created Fields from Both XML Formatted and XER Formatted Source Plans===
| + | |
| − | | + | |
| − | As mentioned above there are eight (8) fields in OnePager 360 that are available in field dropdown menus that are '''calculated''' by OnePager 360 '''Standalone''' from Oracle Primavera P6 data '''imported '''from either '''XML formatted '''or '''XER formatted '''files. These fields and their uses are described in the sub-sections that follow.
| + | |
| − | | + | |
| − | ====Activities (Non-Summary) Field ====
| + | |
| − | | + | |
| − | When OnePager 360 '''Standalone imports '''an '''XML formatted '''or '''XER formatted''' file, it looks at each “row” of the '''import '''and determines if it is an '''Activity''' or a '''WBS Element'''. If the “row” is an '''Activity''' the software sets the '''Activity (Non-Summary) '''field for that '''Activity''' to a value of '''TRUE'''. Additionally, and as explained further on, OnePager also sets the '''WBS Item (Summary) '''field for the '''Activity''' to a value of '''FALSE'''. For each '''WBS Element''' OnePager finds in the '''import source plan '''file, the software sets the '''Activity (Non-Summary) '''field to '''FALSE''' and the '''WBS Item (Summary) '''field for the “row” to '''TRUE'''.
| + | |
| − | | + | |
| − | The '''Activity (Non-Summary) '''along with the '''WBS Item (Summary) '''field is useful when making '''Activity/WBS Element''' selection with the '''OnePager choices''' form as shown below:
| + | |
| − | <center>[[File: P71-4_0_1_6-71-(1B)-09092021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1B)-09092021.png</center>
| + | |
| − | | + | |
| − | Additionally, the '''Activities (Non-Summary) '''field can be used in '''Conditional Import Rules''' to either include or exclude '''Activities''' in conjunction with other rules needed to control the '''import '''to OnePager 360 '''Standalone'''.
| + | |
| − | | + | |
| − | For more information on '''Conditional Import Rules''', please see the article at: [[Conditional Import for Version 7.1 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-71.
| + | |
| − | | + | |
| − | ====Activity % Complete for WBS Elements ====
| + | |
| − | | + | |
| − | As shown in the illustration below, Oracle Primavera P6 does not display '''Activity % Complete''' values for '''WBS Elements''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10B)-07292021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(10B)-07292021.png </center>
| + | |
| − | | + | |
| − | OnePager 360 uses an '''earned-value percent complete''' calculation starting with '''Activity % Complete''' for each individual '''Sctivity''' under the '''WBS Element''' to compute the '''Activity % Complete''' values for each '''WBS Element '''shown in the chart below.
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10C)-08312021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10C)-08312021.png</center>
| + | |
| − | | + | |
| − | ====Duration (computed) Field ====
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone '''calculates a '''duration value''' called '''Duration (computed)''' which is based on the difference in '''days and parts of days''' between the Oracle Primavera P6 '''Finish date '''and '''Start date''' '''excluding weekends'''. The formula is as follows:
| + | |
| − | | + | |
| − | <center>'''Duration (computed) {in days and parts of days} = Finish date – Start date (excluding weekends)'''</center>
| + | |
| − | | + | |
| − | To use this feature, you must assure that your '''XML formatted '''file or '''XER formatted '''file contains the '''Start date '''and '''Finish date''' fields for each '''Activity '''you intend to display in the OnePager chart. The illustration below shows the OnePager 360 chart with '''text columns''' for the '''Start date''', '''Finish date''', and '''Duration (computed)''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10A)-09202021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(10A)-09202021.png </center>
| + | |
| − | | + | |
| − | ====Level “x” summary ID/name Fields ====
| + | |
| − | | + | |
| − | OnePager provides a feature that allows you to conveniently order or create '''levels of indention''' based upon the '''source plans Work Breakdown Structure'''. OnePager supports ten (10) '''levels of indention''' which can be based on the '''ID''' or the '''Name '''of the '''WBS Element'''.
| + | |
| − | | + | |
| − | As an example, take the portion of the Oracle Primavera P6 '''BlueGrass Project Plan''' shown below and note how OnePager interprets the '''WBS Elements''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10D)-09092021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(10D)-09092021.png </center>
| + | |
| − | | + | |
| − | When the OnePager 360 chart is created using the '''Flag20 =Yes''' to control the '''import '''of data and the '''Left#1 swimlane '''is set to '''Level 1 summary name''' and the '''Left#2 swimlane '''is set to '''Level 2 summary name''', the chart looks like this for the portion of the '''source plan''' above:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10E)-09092021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10E)-09092021.png</center>
| + | |
| − | | + | |
| − | ====Object ID Field ====
| + | |
| − | | + | |
| − | OnePager has the capability to '''add''' and '''modify snapshots''' within a chart as a project progresses through time. Additionally, OnePager supports the capability to create charts from '''multiple source plans''' in the '''import package'''. To manage the correspondence between '''Activities/WBS Elements''' as snapshots are '''added''' or '''modified''' and to assure that there is accounting for duplications of '''Activities''' when charts are built from '''multiple source plan''' files, OnePager needs to have a '''unique identifier''' for each '''Activity/WBS Element imported'''. This is accomplished by the OnePager 360 '''calculated field''' called '''Object ID''' where OnePager 360 assigns a '''unique integer''' to each '''Activity/WBS Element''' so that these elements can be consistently managed as snapshot are '''added''' or '''modified'''.
| + | |
| − | | + | |
| − | You have the option of changing the field used by OnePager 360 for this purpose in the '''Template Properties form’s Field Mappings''' tab as shown below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10G)-09142021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10G)-09142021.png</center>
| + | |
| − | | + | |
| − | Changing the '''Unique id''' field name to another field name comes with some risk in that you are responsible to assure that the field selected contains unique data for each '''Activity/WBS Element'''.
| + | |
| − | | + | |
| − | ====Outline Level Field ====
| + | |
| − | | + | |
| − | OnePager 360 provides a calculated field called '''Outline Level''' which is an integer field that tells you what '''WBS Element level''' is associated with each '''Activity imported''' into OnePager for both '''XML formatted '''and '''XER formatted '''files. For example, the Oracle Primavera P6 '''source plan''' shown below has two '''WBS Element levels''':
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10D)-09092021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10D)-09092021.png</center>
| + | |
| − | | + | |
| − | When the '''source plan '''is '''imported '''and the '''flagged Activities''' are displayed with the '''Outline Level '''field used as a '''text column''', the chart looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(10F)-09132021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(10F)-09132021.png</center>
| + | |
| − | | + | |
| − | ====WBS Items (Summary) Field ====
| + | |
| − | | + | |
| − | When OnePager 360 '''Standalone imports '''an '''XML formatted '''or '''XER formatted''' file, it looks at each “row” of the '''import '''and determines if it is an '''Activity''' or a '''WBS Element'''. If the “row” is a '''WBS Element''', the software sets the '''WBS Items (Summary) '''field for that '''Activity''' to a value of '''TRUE'''. If the “row” is not a '''WBS Element''' but is an '''Activity''', the '''WBS Items (Summary) '''field is set to '''FALSE'''.
| + | |
| − | | + | |
| − | This field along with the '''Activities (Non-Summary) '''field is useful when making '''Activity/WBS Element '''selection with the '''OnePager choices''' form as shown below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(1D)-09132021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1D)-09132021.png</center>
| + | |
| − | | + | |
| − | Additionally, the '''WBS Items (Summary) '''field can be used in '''Conditional Import Rules''' to either include or exclude '''WBS Elements''' in conjunction with other rules needed to control the '''import '''to OnePager 360 '''Standalone'''.
| + | |
| − | | + | |
| − | For more information on '''Conditional Import Rules''', please see the article at: [[Conditional Import for Version 7.1 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-71.OnePager 360 Created Fields from XML Imported Source Plans.
| + | |
| − | | + | |
| − | ====Resources Field ====
| + | |
| − | | + | |
| − | Oracle Primavera P6 has the capability to show '''multiple resources''' against any '''Activity'''. OnePager 360 '''Standalone '''can represent these '''multiple resources''' in the chart in various ways but more typically in a '''text column'''. '''Multiple resources''' which are present in the Oracle Primavera P6 '''source plan''' can be '''exported '''to OnePager 360 '''Standalone''' through the '''XML formatted''' and '''XER''' '''formatted '''files''' '''as shown in the illustration below:
| + | |
| − | | + | |
| − | <center>[[File:P71-4_0_1_6-71-(11)-07212021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(11)-07212021.png</center>
| + | |
| − | | + | |
| − | ====Primary Resource Field ====
| + | |
| − | | + | |
| − | Oracle Primavera P6 has the capability to assign '''multiple resources''' to an '''Activity'''. Additionally, among these '''multiple resources''', Oracle Primavera P6 has the capability for you to designate '''one resource''' as the '''Primary Resource'''. For example, in the Oracle Primavera P6 '''source plan''' below, '''Mechanical Engineers''' has three '''resources''' assigned of which '''Prime''' is designated as the '''Primary Resource''':
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(1E)-09132021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1E)-09132021.png</center>
| + | |
| − | | + | |
| − | For '''XML formatted '''files''' '''you have the option to use the OnePager calculated field called '''Primary Resource '''in your chart as shown in the following example:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(1F)-09132021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(1F)-09132021.png</center>
| + | |
| − | | + | |
| − | Oracle Primavera P6 '''XER formatted '''files do not contain '''Primary Resource''' '''export''' data allowing OnePager 360 '''Standalone''' to determine which among multiple '''resources''' for an '''Activity''' is the '''Primary Resource'''. Thus the '''Primary Resource '''field is not supported in OnePager 360 '''Standalone''' for '''XER formatted '''files.
| + | |
| − | | + | |
| − | ===Representing Baseline Data from Oracle Primavera P6 XML Formatted Files in OnePager Charts===
| + | |
| − | | + | |
| − | Oracle Primavera P6 support a '''Project baseline''' and up to three (3) '''User baselines'''. These '''baseline '''data can be '''exported '''to OnePager 360 '''Standalone''' via the '''XML formatted '''file or '''ZIP formatted''' files. '''XER format''' files do '''not''' contain any '''baseline''' related columns.
| + | |
| − | | + | |
| − | If you '''import''' an '''XER formatted '''file, OnePager 360 '''Standalone''' uses the '''Planned Start''' and '''Planned Finish '''columns from the '''XER formatted '''file''' '''for the purpose of representing '''baseline start/finish dates'''. You have some flexibility to change the columns that can be used for '''baseline start/finish''' when creating a '''NEW''' chart by going to the second page of the '''OnePager choices '''form and clicking on the '''Baseline start''' or '''Baseline finish''' windows as shown below for the '''Baseline start '''example:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(33)-08062021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(33)-08062021.png</center>
| + | |
| − | | + | |
| − | As shown above, there are no '''true baseline''' related columns available in the two dropdown lists for '''XER formatted '''file.
| + | |
| − | | + | |
| − | Looking at the second page of the '''OnePager choices''' form where an '''XML formatted''' file was '''imported''' and clicking the '''Baseline start '''dropdown; these are the Oracle Primavera P6 columns available for '''baseline start/finish''' use:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34)-09172021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34)-09172021.png</center>
| + | |
| − | | + | |
| − | In the illustration above for the case of the '''XML formatted '''file there is a greater selection of Oracle Primavera P6 columns from which to choose. As noted at the beginning of this section, OnePager 360 has nine (9) calculated columns where several pertain to '''baseline start/finish''' fields as shown in the following list for this example:
| + | |
| − | | + | |
| − | :* '''BL Project Start '''– Project Baseline Start Date
| + | |
| − | :* '''BL Project Finish '''-- Project Baseline Finish Date
| + | |
| − | :* '''“[User Baseline Name1]” Finish''' – User Baseline 1 Finish Date
| + | |
| − | :* '''“[User Baseline Name1]” Start '''– User Baseline 1 Start Date
| + | |
| − | :* '''“[User Baseline Name2]” Finish '''– User Baseline 2 Finish Date
| + | |
| − | :* '''“[User Baseline Name2]” Start '''– User Baseline 2 Start Date
| + | |
| − | :* '''“[User Baseline Name3]” Finish '''– User Baseline 3 Finish Date
| + | |
| − | :* '''“[User Baseline Name3]” Start '''– User Baseline 3 Start Date
| + | |
| − | :* '''“[User Baseline Name – Project Baseline]” Finish''' – Project Baseline Finish Date
| + | |
| − | :* '''“[User Baseline Name – Project Baseline]” Start '''– Project Baseline Start Date
| + | |
| − | | + | |
| − | For illustration, suppose that an Oracle Primavera P6 '''source plan''' has the '''project baseline''' and '''user baselines''' configured as shown below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34A)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34A)-09202021.png</center>
| + | |
| − | | + | |
| − | As mentioned earlier, OnePager 360 '''Standalone''' supports displaying one (1) Oracle Primavera P6 '''project baseline''' and up to three (3) '''user baselines'''. When an '''XML formatted '''file is '''imported''' with a '''project baseline '''and two (2) '''user baselines''', for example, the '''project baseline''' data is provided in two sets of fields: '''BL Project Start/Finish''' and '''[User Baseline Name – Project Baseline] Start/Finish''' as shown here:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34B)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34B)-09202021.png</center>
| + | |
| − | | + | |
| − | '''User baselines''' are represented in dropdown field name lists in the order they were '''imported '''as shown below in the '''Chart Properties '''form’s '''Rows/Swimlanes '''tab’s '''Text Columns '''sub-control section:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34C)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34C)-09202021.png</center>
| + | |
| − | | + | |
| − | There are two alternative methods for changing the '''baseline start/finish dates''': (1) '''Before''' creating the chart using the '''Template Properties''' form and (2) '''After''' the chart is created using the '''Chart Properties '''form.
| + | |
| − | | + | |
| − | ====Changing the Baseline Start/Finish Date Column Usage BEFORE Creating the OnePager Chart====
| + | |
| − | | + | |
| − | =====For XML Formatted Files Imported to OnePager 360 Standalone=====
| + | |
| − | | + | |
| − | When you select to '''import '''an '''XML formatted '''file using the '''OnePager choices '''form,''' '''the Template''' Properties '''forms distributed with OnePager 360 '''Standalone''' is reset to use '''BL Project Start '''and '''BL Project Finish '''for '''baseline start/finish '''representation in the chart as shown below in the '''Template Properties '''form’s '''Field Mapping '''tab accessed from the second page of the '''OnePager choices''' form:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(34D)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(34D)-09202021.png</center>
| + | |
| − | | + | |
| − | When the '''Template Properties''' form’s '''Field Mappings''' tab is accessed, clicking the '''Baseline start''' dropdown shows the list of '''XML formatted source plan import''' columns available for consideration as the '''Baseline Start date'''. Note that the list contains the '''baseline '''related columns for '''BlueGrass Project'''. Making an alternative selection for the '''baseline start/finish dates''' in the '''Template Properties '''form in this manner establishes the dates that OnePager 360 '''Standalone '''uses to create the chart from the '''XML formatted import '''data as shown here:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(35)-09172021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(35)-09172021.png</center>
| + | |
| − | | + | |
| − | Other properties of '''baselines''' in the chart can be made by accessing the '''Chart Properties '''form’s '''Task Bars''' or '''Milestones''' tabs and the associated '''Set baseline properties '''form.
| + | |
| − | | + | |
| − | =====For XER Formatted Files Imported to OnePager 360 Standalone=====
| + | |
| − | | + | |
| − | When you '''import '''an '''XER formatted '''file using the '''OnePager choices '''form,''' '''the '''Template Properties '''forms distributed with OnePager 360 '''Standalone''' is reset to use '''Actual Start '''and '''Actual Finish '''for '''baseline start/finish '''representation in the chart as shown below in the '''Template Properties '''form’s '''Field Mapping '''tab accessed from the second page of the '''OnePager choices''' form:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(35A)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(35A)-09202021.png</center>
| + | |
| − | | + | |
| − | When the '''Template Properties''' form’s '''Field Mappings''' tab is accessed, clicking the '''Baseline start''' dropdown shows the list of '''XER formatted source plan import''' columns available for consideration as the '''Baseline Start date'''. Note that the list contains various date columns for '''BlueGrass Project''' as there are no actual '''baseline related dates''' available in an '''XER formatted '''file. Making an alternative selection for the '''baseline start/finish dates''' in the '''Template Properties '''form in this manner establishes the dates that OnePager 360 '''Standalone '''uses to create the chart from the '''XER formatted import '''data as shown here:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(35B)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(35B)-09202021.png</center>
| + | |
| − | | + | |
| − | Since '''XER formatted''' files provide no specific '''baseline start/finish '''dates, care needs to be taken when representing these alternate date fields and their interpretation in a schedule discussion.
| + | |
| − | | + | |
| − | Other properties of '''baselines''' in the chart can be made by accessing the '''Chart Properties '''form’s '''Task Bars''' or '''Milestones''' tabs and the associated '''Set baseline properties '''form.
| + | |
| − | | + | |
| − | ====Changing the Baseline Start/Finish Date Column Usage AFTER Creating the OnePager Chart====
| + | |
| − | | + | |
| − | =====For XML Formatted Files =====
| + | |
| − | | + | |
| − | Once the OnePager 360 chart is created, you still have the option to change the Oracle Primavera P6 columns used for creating the '''baseline graphics '''in the chart. This is done by accessing the '''Chart Properties '''form and navigating to the '''Field Mappings '''tab, clicking the '''Baseline start '''dropdown, for example, and selecting the desired '''XML formatted import''' column you wish to use to represent '''baseline start/finish dates '''as is illustrated below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(36)-09172021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(36)-09172021.png</center>
| + | |
| − | | + | |
| − | When the '''Chart Properties''' form’s '''Field Mappings''' tab is accessed, clicking the '''Baseline start''' dropdown shows the list of '''XML formatted source plan import''' columns available for consideration as the '''Baseline Start date'''. Note that the list contains the '''baseline '''related columns for '''BlueGrass Project'''. Making an alternative selection for the '''baseline start/finish dates''' in the '''Chart Properties '''form in this manner changes the dates that OnePager 360 '''Standalone '''uses and updates the chart using the '''XML formatted source plan import '''data.
| + | |
| − | | + | |
| − | Other properties of '''baselines''' in the chart can be made by accessing the '''Template Properties '''form’s '''Task Bars''' or '''Milestones''' tabs and the associated '''Set baseline properties '''form.
| + | |
| − | | + | |
| − | =====For XER Formatted Files =====
| + | |
| − | | + | |
| − | For '''XER formatted '''files, after the OnePager 360 chart is created, you still have the option to change the Oracle Primavera P6 columns used for creating the '''baseline graphics '''in the chart. It must be understood, however, that no true '''baseline start/finish '''dates are available in '''XER formatted''' files. Altering the '''Template Properties '''form’s designated dates is done by accessing the '''Chart Properties '''form and navigating to the '''Field Mappings '''tab, clicking the '''Baseline start '''dropdown and selecting the desired '''XER formatted import''' column you wish to represent '''baseline start/finish '''dates''' '''is illustrated below:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(36A)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(36A)-09202021.png</center>
| + | |
| − | | + | |
| − | When the '''Chart Properties''' form’s '''Field Mappings''' tab is accessed, clicking the '''Baseline start''' dropdown shows the list of '''XER formatted source plan import''' columns available for consideration as the '''Baseline Start date'''. Note that the list contains the '''various date '''related columns for '''BlueGrass Project'''. Making an alternative selection for the '''baseline start/finish dates''' in the '''Chart Properties '''form in this manner changes the dates that OnePager 360 '''Standalone '''uses and updates the chart using the '''XER formatted source plan import '''data.
| + | |
| − | | + | |
| − | Other properties of '''baselines''' in the chart can be made by accessing the '''Template Properties '''form’s '''Task Bars''' or '''Milestones''' tabs and the associated '''Set baseline properties '''form.
| + | |
| − | | + | |
| − | ===Using the OnePager 360 Deadline Representation Feature with Oracle Primavera P6===
| + | |
| − | | + | |
| − | OnePager 360 has a feature that lets you display a '''deadline symbol '''in the chart that represents the '''latest finish''' date for the '''Activity''' or when the '''milestone''' must be met. A portion of a chart with '''deadline symbols''' looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P70-10_9_1-(2)-06032020.png]]</center>
| + | |
| − | <center>P70-10_9_1-70-(2)-09182019.png</center>
| + | |
| − | | + | |
| − | When '''deadlines''' are turned '''ON''', they appear (by default) as '''down-arrow symbols''' in each task bar's row at the '''deadline date''' position with respect to the '''time axis.''' Above, '''deadline symbols''' that are not contained within their respective task bar are shown with '''black dash-dot connecting lines''' to illustrate the capability.
| + | |
| − | | + | |
| − | Controls for displaying '''deadline symbols '''are provided in the '''Template Properties '''and '''Chart Properties '''form’s '''Task Bars '''and '''Milestones''' tabs where you can specify the Oracle Primavera P6 '''source plan''' field to represent '''deadline dates''' and specify their graphical representation in the chart.
| + | |
| − | | + | |
| − | For convenience, OnePager 360 assumes that the Oracle Primavera P6 '''XML formatted''' and '''XER formatted '''file’s '''Planned Finish''' date field is the '''default field''' that OnePager 360 '''Standalone''' uses to represent '''deadline symbols '''in the chart. This setting is established in all Oracle Primavera P6 '''distributed Template Properties '''forms.
| + | |
| − | | + | |
| − | The '''deadline''' setting is established in all Oracle Primavera P6 '''distributed Template Properties '''form’s '''Field Mappings '''tab as shown below for an '''XER formatted '''file being '''imported''':
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(36B)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(36B)-09202021.png</center>
| + | |
| − | | + | |
| − | As shown above, the '''Deadline''' date can be changed '''before''' the chart is created by using the '''Template Properties '''form’s '''Field Mappings''' tab to select another preferred '''XER formatted '''date column. Changing the '''Deadline '''date '''after '''the chart is created requires using the '''Field Mappings''' tab in the '''Chart Properties '''form.
| + | |
| − | | + | |
| − | The '''Template Properties '''form’s '''Field Mappings''' tab’s '''Deadline''' dropdown list for '''XML formatted''' files in most cases shows a more extensive list of dates from which to choose should you wish to change the '''default Deadline''' date field as shown here:
| + | |
| − | | + | |
| − | <center>[[File: P71-4_0_1_6-71-(36C)-09202021.png]]</center>
| + | |
| − | <center>P71-4_0_1_6-71-(36C)-09202021.png</center>
| + | |
| − | | + | |
| − | At your option, you can define a '''User Defined Field''' in Oracle Primavera P6 call '''Deadline''', for example,''' '''defined as a '''Date '''category field to serve this purpose. When this '''User Defined Field''' is populated with date data in your '''source plan''' OnePager 360 '''Standalone''' can use the '''Deadline '''field’s data to display '''deadline symbols '''in the chart.
| + | |
| − | | + | |
| − | For more information on using '''Deadline symbols''', please see the article at: [[Deadlines for OnePager for Version 7.1 | Deadlines for OnePager]] 10.9.1-71.
| + | |
| − | | + | |
| − | ===Using the OnePager 360 Endpoints Representation Feature with Oracle Primavera P6===
| + | |
| − | | + | |
| − | OnePager 360 also has a feature that lets you display a '''multiple endpoint symbols '''in the chart that represent potentially important dates for an '''Activity'''. A portion of a chart with four (4) '''endpoint symbols''' associated with each task bar looks like this:
| + | |
| − | | + | |
| − | <center>[[File:P70-10_11_1-(7-1)-06042020.png]]</center>
| + | |
| − | <center>P70-10_11_1-(7-1)-06042020.png</center>
| + | |
| − | | + | |
| − | When '''one or more endpoints''' are turned '''ON''', they appear (by default) as '''down-arrow symbols''' in each task bar's row at the '''endpoint’s date''' position'''.''' Above, '''endpoint symbols''' that are not contained within their respective task bar are shown with '''black dash-dot connecting lines''' to illustrate the capability.
| + | |
| − | | + | |
| − | Controls for displaying '''endpoint symbols '''are provided in the '''Template Properties '''and '''Chart Properties '''form’s '''Task Bars '''and '''Milestones''' tabs where you can specify the Oracle Primavera P6 '''source plan''' field to represent '''deadline dates''' and specify their graphical representation in the chart.
| + | |
| − | | + | |
| − | For convenience, OnePager 360 assumes that the following Oracle Primavera P6 '''XML format''' and '''XER format''' date fields are the '''default fields''' that OnePager 360 '''Standalone''' uses to represent '''endpoint symbols '''in the chart:
| + | |
| − | | + | |
| − | :* '''Endpoint 1''': '''Start'''
| + | |
| − | :* '''Endpoint 2''': '''Finish'''
| + | |
| − | :* '''Endpoint 3''': '''Planned Start'''
| + | |
| − | :* '''Endpoint 4''': '''Planned Finish'''
| + | |
| − | | + | |
| − | These setting are established in all Oracle Primavera P6 '''distributed Template Properties '''form’s '''Task Bars '''tab in the '''Task Bar Decorations''' sub-control group at the '''Endpoints '''button. ('''Milestones''' do not display '''Endpoint symbols'''.) Checking the '''Endpoints '''checkbox '''ON''' and clicking the '''Endpoints''' '''Properties… '''button accesses the '''Set endpoint properties''' form where the '''default endpoint dates''' can be changed '''before''' the chart is created. Following the same path in the '''Chart Properties '''form to the '''Set endpoint properties '''form can accomplish the same result '''after''' the chart is created.
| + | |
| − | | + | |
| − | For more information on using '''Endpoint symbols''', please see the article at: [[Endpoints for OnePager for Version 7.1 | Endpoints for OnePager]] 10.11.1-71.
| + | |
| − | | + | |
| − | ===Oracle Primavera P6 Columns Available to OnePager 360 Standalone===
| + | |
| − | | + | |
| − | OnePager 360 '''Standalone''' is able to '''import '''two types of files containing Oracle Primavera P6 column data. These are the '''XML formatted '''file and the '''XER formatted '''file. OnePager 360 '''Standalone''' is also capable of '''importing '''an '''XML formatted '''file that is '''compressed '''by Oracle Primavera P6 into a '''ZIP formatted''' file. When a '''ZIP formatted '''file is presented to OnePager, OnePager 360 '''Standalone''' first performs the '''UNZIP '''operation to '''extract '''the '''XML formatted data''',''' '''and '''imports '''the resulted decompressed '''XML formatted data'''.
| + | |
| − | | + | |
| − | The '''XML formatted '''file''' '''and the '''XER formatted '''file do '''not''' provide all the columns that are available in Oracle Primavera P6 nor do these two formats contain same columns. Generally speaking, the '''XML formatted '''file contains approximately twice as many Oracle Primavera P6 column options as does the '''XER formatted '''file. That is why we recommend using the '''XML formatted '''file over the '''XER formatted '''file as an '''import '''to OnePager 360 '''Standalone'''. Additionally, you may find it more efficient to '''export''' '''XML formatted''' files directly instead of '''exporting ZIP compressed formatted XML '''files since OnePager 360 '''Standalone''' must '''decompress ZIP formatted '''files before '''importing '''the data.
| + | |
| − | | + | |
| − | For more information on all the Oracle Primavera P6 data columns that are '''exported '''via '''XML formatted''' and '''XER formatted''' files, please see the article at: [[Oracle Primavera P6 Columns Available to OnePager 360 for Version 7.1 | Oracle Primavera P6 Columns Available to OnePager 360]] 29.1.1-71.
| + | |
| − | | + | |
| − | ===OnePager 360 Standalone Handling of Oracle Primavera P6 User Defined Fields (UDF)===
| + | |
| − | | + | |
| − | Oracle Primavera P6 provides a number of '''User Defined Fields (UDF) '''with the product. These '''UDF’s''' can be '''exported''' in both '''XML formatted '''and''' XER formatted''' files and '''imported''' into OnePager 360 '''Standalone'''. However, it is important to note that the '''UDF’s exported''' in an '''XML formatted''' file are different from the '''UDF’s exported''' from an '''XER formatted''' file. A list of '''UDF’s''' '''exported''' with each file type is shown in the illustrations below:
| + | |
| − | | + | |
| − | <center>'''XML Format User Defined Fields'''</center>
| + | |
| − | <center>[[File: P71-4_0_1_6-71-(32)-08062021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(32)-08062021.png</center>
| + | |
| − | | + | |
| − | <center>'''XER Format User Defined Fields'''</center>
| + | |
| − | <center>[[File: P71-4_0_1_6-71-(31)-08062021.png]]</center>
| + | |
| − | <center> P71-4_0_1_6-71-(31)-08062021.png</center>
| + | |
| − | | + | |
| − | In the illustrations above, '''EAM''' stands for '''Enterprise Asset Management'''.
| + | |
| − | | + | |
| − | For more information on all the Oracle Primavera P6 data columns that are '''exported '''via '''XML formatted''' and '''XER formatted''' files, please see the article at: [[Oracle Primavera P6 Columns Available to OnePager 360 for Version 7.1 | Oracle Primavera P6 Columns Available to OnePager 360]] 29.1.1-71.
| + | |
| | | | |
| | ==Related Links== | | ==Related Links== |
| | | | |
| − | [[What's New with OnePager Release 7.1?]] 0.4-71 | + | {| class="wikitable" |
| | + | | [[Templates versus Charts for Version 7.2 | Templates versus Charts]] 4.0.1.3-72 |
| | + | | [[Linking Task and Milestones Using Manual and Data-Driven Task Links for Version 7.2 | Linking Task and Milestone Using Manual and Data-Driven Task Links (Portal)]] 19.0.1-72 |
| | + | |- |
| | + | | [[Editing with the Chart Properties form for Version 7.2 (Portal) | Editing with the Chart Properties form (Portal)]] 21.0.1-72 |
| | + | | [[Template Only Features for OnePager Pro for Version 7.2 | Template Only Features for OnePager Pro]] 24.1.1-72 |
| | + | |- |
| | + | | [[Template Only Features for OnePager Express for Version 7.2 | Template Only Features for OnePager Express]] 24.2.1-72 |
| | + | | [[Template Only Features for Primavera P6 Source Plans in OnePager Version 7.2 | Template Only Features for Primavera P6 Source Plans in OnePager]] 24.2.2-72 |
| | + | |- |
| | + | | [[Template Only Features for Smartsheet Source Plans in OnePager Version 7.2 | Template Only Features for Smartsheet Source Plans in OnePager]] 24.2.3-72 |
| | + | | [[Splitting and Parsing Columns for OnePager Pro for Version 7.2 | Splitting and Parsing Fields for OnePager Pro]] 24.4.1-72 |
| | + | |- |
| | + | | [[Splitting and Parsing Columns for OnePager Express for Version 7.2 | Splitting and Parsing Fields for OnePager Express]] 24.5.1-72 |
| | + | | [[Splitting and Parsing Columns for Primavera P6 Source Plans in OnePager Version 7.2 | Splitting and Parsing Columns for Primavera P6 Source Plans in OnePager]] 24.5.2-72 |
| | + | |- |
| | + | | [[Splitting and Parsing Columns for Smartsheet Source Plans in OnePager Version 7.2 | Splitting and Parsing Columns for Smartsheet Source Plans in OnePager]] 24.5.3-72 |
| | + | | [[Splitting and Parsing Columns for Project for the Web Source Plans for Version 7.2 | Splitting and Parsing Columns for Project for the Web Source Plans]] 24.5.5-72 |
| | + | |- |
| | + | | [[Splitting and Parsing Columns for Planisware Enterprise Source Plans for Version 7.2 | Splitting and Parsing Columns for Planisware Enterprise Source Plans]] 24.5.7-72 |
| | + | | [[Splitting and Parsing Columns for Wrike in OnePager Version 7.2 | Splitting and Parsing Columns for Wrike in OnePager]] 24.5.11-72 |
| | + | |} |
| | | | |
| − | [[Installing and Activating OnePager 360 for Version 7.1 (Portal) | Installing and Activating OnePager 360 (Portal)]] 2.0.3-71
| + | (24.5.9-72) |
| | | | |
| − | [[Using Oracle Primavera P6 Source Plans with OnePager 360 Version 7.1 | Using Oracle Primavera P6 Source Plans with OnePager 360]] 3.0.3.1-71
| + | [[Category:Version 7.2]] |
| − | | + | [[Category:Editing the Chart]] |
| − | [[Using Rows and Swimlanes for OnePager Version 7.1 | Using Rows and Swimlanes]] 4.0.1.5-71
| + | [[Category:Task/Milestone Editing]] |
| − | | + | [[Category:Column Splitting]] |
| − | [[Basic Workflows for Version 7.1 (Portal) | Basic Workflows (Portal)]] 7.0.1-71
| + | [[Category:Charts]] |
| − | | + | [[Category:Task Links]] |
| − | [[Conditional Import for Version 7.1 (Portal) | Conditional Import Filters (Portal)]] 7.18.1-71
| + | [[Category:Ribbon]] |
| − | | + | |
| − | [[Merging the Wrong Tasks into a Chart for Version 7.1 - OnePager 360 Standalone - Primavera P6 | Merging the Wrong Tasks into a Chart - OnePager 360 Standalone - Primavera P6]] 7.20.1-71
| + | |
| − | | + | |
| − | [[Deadlines for OnePager for Version 7.1 | Deadlines for OnePager]] 10.9.1-71
| + | |
| − | | + | |
| − | [[Endpoints for OnePager for Version 7.1 | Endpoints for OnePager]] 10.11.1-71
| + | |
| − | | + | |
| − | [[Managing Chart Data for Version 7.1 | Managing Chart Data (Portal)]] 23.0.1-71
| + | |
| − | | + | |
| − | [[Managing Templates for Version 7.1 (Portal) | Managing Templates (Portal)]] 24.0.1-71
| + | |
| − | | + | |
| − | [[Oracle Primavera P6 Columns Available to OnePager 360 for Version 7.1 | Oracle Primavera P6 Columns Available to OnePager 360]] 29.1.1-71
| + | |
| − | | + | |
| − | (4.0.1.6-71)
| + | |
| − | | + | |
| − | [[Category:Version 7.1]] | + | |
| − | [[Category:Getting Started with Version 7.1]] | + | |
| − | [[Category:Add-in]]
| + | |
| − | [[Category:Standalone]]
| + | |
| − | [[Category:Launching From Microsoft Project]] | + | |
| − | [[Category:Launching From Microsoft Excel]] | + | |
| − | [[Category:Primavera]] | + | |
| − | [[Category:OnePager 360 Start Form]] | + | |
| − | [[Category:OnePager Choices Form]] | + | |
| | [[Category:Snapshots]] | | [[Category:Snapshots]] |
| − | [[Category:Charts]] | + | [[Category:Template Properties Form]] |
| − | [[Category:Templates]] | + | [[Category:Chart Properties Form]] |
| − | [[Category:Editing the Chart]]
| + | [[Category:Asana]] |
| − | [[Category:Deadlines]] | + | [[Category:OnePager Bundle]] |
| − | [[Category:Endpoints]]
| + | |
| − | [[Category:Sharing Output]]
| + | |
| − | [[Category:OnePager - Tool Bar]]
| + | |
| − | [[Category:Help]]
| + | |
| − | [[Category:OnePager Pro]]
| + | |
| − | [[Category:OnePager Express]]
| + | |
| − | [[Category:OnePager 360]] | + | |
-11022023.png)
-11272023.png)
-11022023.png)
-11022023.png)
-11022023.png)
-11022023.png)
