Enterprise Project Management, Microsoft Project Professional and Microsoft Project Server
- April 2014
- March 2014
- February 2014
- November 2013
- October 2013
- August 2013
- July 2013
- June 2013
- March 2013
- February 2013
- December 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- January 2012
- December 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- October 2008
- September 2008
- August 2008
By: Collin Quiring
For those using or setting up PWA task updates the question often comes up as to whether or not the Team Members should be updating by percentage or by entering work. There are a couple of questions that come up in relation to this to help decide which to use.
The first question is:
Do you care about hours of work or do you just care about how long the job took?
As in, does it matter that a job took 10 hours to do? Does it matter for your organization’s needs (for projects or accounting or pay or billing) that you know how much time it actually took to do the work? Or, do you just care that a task took five days to complete? Whether the person(s) assigned to the task worked for 1 hour or 100 hours, do you still just want to know that it took a certain number of days to complete?
The answer to the first question will determine the accuracy of hours that you are trying to track.
If you just care about how many days a task takes to complete, rather than the exact hours, then you want to enter the percentage. And, more specifically, you want to enter the % Complete field. There is also a % Work Complete field that is available but that is in relation to hours and so that wouldn’t apply to your need. The % Complete field would be the easiest to use because it is based on Actual Duration divided by Duration. So, if a three day task is one-and-a-half days into the schedule, then it is 50% complete. And note, that is 50% complete whether one minute of actual work is done or not (although we would hope that folks are only updating tasks that have work completed against them.
If you care about hours, and you care about getting accurate hours, then you should have the % Work Complete and % Complete fields where they can’t be edited by Team Members. You should allow the system to calculate those fields for you. What you should have Team Members update is the Actual Work and Remaining Work fields. When the Actual Work field is updated, the Remaining Work field will be calculated. If the Remaining Work field doesn’t match the work that the Team Member thinks it should, then they should update it so as to allow for the dates to better align with the amount of work.
And, the second question is:
Do you care when the work is done?
If your organization has accounting, billing, pay or other reasons to know when work is occurring (whether you are tracking in duration or hours) then there is one other update the Team Member should do – enter the date.
If your organization cares about when work happens, BEFORE entering hours the Team Member should enter the Actual Start Date. Entering the Actual Start Date will set the timeframe properly. Then, the Team Member should enter the % Complete or the Actual Hours – depending on the method you are using. If the Team Member only enters the % Complete or Actual Hours then the Actual Start Date will be calculated for you. Which, in most cases, will be the date was assigned. And, that is where you can get Actual Dates that are nowhere near the real calendar date – because it uses the originally assigned date (whether that date is in the future or in the past).
BY: Collin Quiring
When installing Project Server 2013 in house and installing all the required components (like SQL Server 2012 and SharePoint Server 2013), a Web Application and a Top Level Site and Site Collection have to be created along with the Project Site (PWA). While other documents exist to explain the how to part of the installation, this article is about the definitions for SharePoint web and sites and how Project ties into them. Definitions and then some examples are provided below.
For those using Project Online the ability to modify and setup Web Applications and Site Collections is different and in the SharePoint administration it is slightly different wording. That is outlined at the bottom of this article.
First, the definitions:
Web Application: In SharePoint Server 2013 a Web Application is the container (I am trying to avoid the word “site” since it is sometimes used incorrectly here) that holds the Top Level site and any Site Collections and corresponding Sites. The key parts to the Web Application is that it is the IIS Web Site; which for those like me who aren’t extremely technical is where the main URL comes from (yeah, I know you can do things with Alternate Access Mapping and I know that a fancy-pants IIS/Networking guru can use all sorts of things like bindings to make URL’s other things but for our purposes, this is the URL).
Site Collection: This is the place that has the Top Level Site and any other Subsites. The key point here is that the Site Collection has a Content Database. You can use one Content Database for multiple Site Collections but the important piece to remember is that a Site Collection must have a Content Database.
Top Level Site: This is the site at the top of the site collection. It is the first site in the collection and it may or may not have subsites. (Often, but not always, during setup, this site is just given the “/” designation by the administrator. The other common designation is “/sites/” for the top level site.)
Subsites (often just called Sites): This is a bit confusing because Top Level site and site may be used interchangeably because the Top Level site is a site by itself. But, a subsite is a site below a Top Level site.
Content Database: This is the database that holds the SharePoint information for a Site Collection. It has both the documents and the setting customizations for that Site Collection.
Project Web App Site: For our purposes, Project Web App Site is often called PWA, sometimes also called the Project Site and is a subsite below the Top Level site.
Instance: In the Project Web App Site each site is called an Instance. Many organizations have at least two instances in their production environment, a production level development/testing instance and production version on the same web application (this is different than a development or test server or a separate system for development). Commonly, the main production instance is called just “PWA”. Each instance has a separate database table structure, separate schedules on the site, separate resources and so on. For example, an organization that has an IT department that runs projects totally differently than a PMO department may have two instances – one called “IT_PWA” and the other “PMO_PWA”.
Now for some examples:
The first one is a basic example – a Web Application, Top Level site, and two subsites with the Site Collection in the red boxed area.
From the perspective of Project Server this is what that diagram might look like.
One more example diagram – this time with sample URL’s for two separate PWA instances. The first instance is just called “PWA” and the second one is for a separate department called “ITPWA”. The Web Application is often just the servername so it would be something like http://servername. The Top Level Site in this example is just “/” and therefore the two PWA instances would be: http://servername/PWA and http://servername/ITPWA .
In the Project Online, Office 365 and SharePoint Online world the terminology is a bit different because the setup is a bit different. The main terms to know here are:
Tenant: This is your online (or cloud version) subscription of the service you have purchased. It can be a bit confusing since context is everything. You can have a SharePoint Online Tenant or an Office 265 Tenant or a Project Online Tenant. In our case, thinking from the Project Online perspective, you would most likely have a SharePoint Online Tenant and Project Online would be a part of that Tenant. In a non-techy description, basically it means that Microsoft has the uber-Wep Applications and they give us a small piece of the pie. I am not sure who to credit this to since I see lots of websites that explain it something like this – In the United States a person can rent an apartment in a large apartment building. They are a “tenant” of that apartment building. They can modify their own apartment as much as they want but they can’t modify the common areas of the building that are outside of their apartment.
The default in the SharePoint Online administration screen for those of using it only for Project Online purposes is to have three Site Collections – one for the Website (usually the Tenant), one with the Project Web App Site and one for search. (And, apparently, they use the “/sites/” for the Top Level site for the PWA and “/” for the Search site). And, for the MY Sites (if being used) portion of the SharePoint Online it is using the Site Collection with a “-my” in the URL. In the My Sites section, you would have many potential subsites – one for each person that creates one.
For example, my Project Online Tenant using SharePoint Online administration looks like this:
Based on this information, this means that I have three Site Collections and PWA is a subsite in the sites Top Level site. Using the type of diagram we have above for the On Site version, this means that the Site Collection piece would look similar to this:
I hope this helps to clear up some of the definitions!
BY: Tim Gryder
Practical use of Microsoft Project Server or Project Online 2013 for Issues Management and Collaboration
If you’re a project manager running any project of scope, duration and complexity then you know that much of project management constantly deals with Murphy’s law…”What can go wrong will go wrong and at the worst possible time”. These events or “Issues” are often documented, assigned, and managed by the project manager in order to address the issue and keep the project moving. But how can we really drive issue resolution and ensure that nothing is falling thru the cracks?
A simple solution to keeping up with, and collaborating on Issues can be found in the Microsoft Project Server Platform
Take for example the image below…a simple project managed in Project Server (PWA-Project View), to build a storage building. As is typical, as tasks are being completed, I have now run into an issue related to the “Budget” task…More funds must be Secured!
Use Project Server (or Project Online) to document; assign the issue to a task and person, against the task “Budget”. Here is how to assign an Issue to a Task!
Open the Projects view in PWA and select your project and then Select Issues from the Project tab for the Project.
Select New Item and create your issue.
Fill out the issues form to define due dates and assignments and dialog on the issue etc.
Then Save the Issue.
Navigate back to your project site and select Tasks and then select your task “Budget” to open.
This is where we now associate the Issue we created above with the task from the project.
Select “Show More” and then “Add Related Item”
Select Issues from the left side of the assets available to add which will be underneath your project.
Take note that each project has its own list of objects that can be associated with a task…
I could also associate Deliverables and Risks etc…
Choose the Issue you created from the Issues List and then select Insert.
We now have a Task with an issue assigned to it. This can be seen in the task details view in PWA.
We are also now made aware at the Projects Portfolio View in PWA that this project has an unresolved Issue.
So now instead of collecting issues into a spreadsheet and hoping you have the latest issues and their status…You can manage these issues in an environment that is collaborative, real time and reportable.
If this doesn’t get your cats walking in a straight line then I don’t know what does!
Connecting Excel 2013 to Project Online using Odata
By Collin Quiring
We have seen issues for some folks when connecting Excel 2013 to Project Online using an Odata connection. This blog is to give an example of how to get data from that connection without ever connecting to Project Online directly.
Start by opening Excel 2013 and going to the DATA tab. Then, select From Other Sources in the ribbon. On the drop-down, select From Odata Data Feed.
This will bring a Data Connection Wizard popup. Put in the Link to your Project Online site followed by
THIS IS CRITICAL. So, in our sample, with our Project Online site being at “https://PMPSpecialists.com/sites/Demo7PWA” the link to enter in the Link option is: “https://PMPSpecialists.com/sites/Demo7PWA/_api/ProjectData/ “ You may or may not need to enter a sign-in at this point, in this example, we do not need one.
NOTE: Be careful when copy/pasting the URL link. We have seen where the link will duplicate in the Link of File box (it is hidden at first so we recommend you place your cursor at the far left of the box and do NOT select the entire box but use your arrow key and scroll over to confirm that the URL is only in place one time).
If the URL (URI) is incorrect, or you don’t have permissions, you may get any of the following error messages:
(We couldn’t get data from the Data Model. Here’s the error message we got:
Invalid URI: The URI Scheme is not valid.)
(Unable to obtain list of tables from the data source.)
(We couldn’t get data from the Data Model. Here’s the error message we got:
The remote server returned an error: (400) Bad Request.)
(We couldn’t access the data feed server because the URL is invalid.)
Once you have connected, after entering the link in the Data Connection Wizard, the second popup titled Data Connection Wizard with the option to Select Tables will appear.
For our example, we scrolled down and selected Projects as the table to bring back.
The third box for the Data Connection Wizard appears that allows us to Save our Data Connection. Note – we are not saving the results, we are saving the .odc file only. Results are saved from Excel as you would normally save any file.
gives us the option of which type of Excel workbook we want (Table, Pivot, etc.). And, we can select the Existing Worksheet or a New Worksheet.
Clicking OK brings back the Excel file and the data.
And, here is a small piece of one item from the Project file in a normal worksheet from our Project Online instance:
And, as an example, the Data Source we saved earlier, is now sitting on our PC for us to be able to use in the future. The default location is “This PC / Documents / My Data Sources”
As further proof that the Data Connection now exists, the next time you want to use it, Select the DATA tab from Excel, the Existing Connection option in the ribbon and the data connection you created will be there for you to use!
PMP Specialists is coordinating with the Microsoft Project Users Group (MPUG) to start a new chapter in the Northwest Arkansas area. MPUG is the official user group for Microsoft Project and provides weekly web events, chapters, deep-dive certificates, articles, resources, and community forum. This chapter will start out meeting once a quarter.
There is no fee to attend a chapter meeting.
Before officially beginning this chapter we are trying to determine the community interest in having a Microsoft Project User Group in our area. We know that there are many users of Project in our area and we know that these users range from beginners to experts. The benefit of having a chapter in our area is the MPUG support for everybody as we become better at using the tools that make our work life more productive.
MPUG meetings will also provide free PDU’s for PMI certifications.
MPUG chapter meetings are a great way for members to come together to share knowledge, network, expand professional development and have fun. Only at MPUG Chapter meetings can you enjoy engaging presentations from Project experts, share your own Project experiences with other professionals in your field, and enjoy good food and conversations with peers in your local community.
If you are interested, please send your name and email address to Info@PMPSpecialists.com
By: Collin Quiring
With the advent of Project 2013 there are a few different versions available and this little post is an attempt to help clarify those differences. Also, to help clarify things, only 2013 Project works with 2013 (it does not allow 2010 or 2007 connectivity). You can still open a previous version’s project file in 2013, but only 2013 Professional connects with Project Online 2013 and Project Server 2013.
The first group we are going to cover are the versions that are installed and used in-house. This is the more common version that has been used by organizations up until this point. The server version of the software is called Project Server 2013. This is the software that has requirements like SharePoint Server 2013 and SQL Server (2012 SP1 if you want SSRS [which we strongly recommend]) to be installed in-house as well.
To access Project Server 2013 to edit or create schedules you will need to use Project Professional 2013. This is the client software that allows access to the server. The only people that really need Project Professional 2013 are those that interact with the schedules as a whole and directly. There is also a tool that can be used by scheduling professionals that does not use Project Server, and that is Project Standard 2013. This is the “stand-alone” version of the Project for the client. At the bottom of this entry is a brief comparison of the Project Professional and Standard versions.
To access Project Server 2013 in a web-enabled environment you use the PWA (Project Web App) interface. This is a web page and can be accessed by almost every browser now but is still part of the local organization’s network.
To clarify, here is a diagram that Darin Brazile worked up to represent how it works:
The second set of versions that we are going to cover are the Online versions. These are the Microsoft online versions where the software is somewhere in the world and you access it by your web browser. This is called Project Online. This is the web-enabled version of PWA and is called PWA just like the in-house version is called PWA. This is a fully functional version of PWA and is based on a monthly licensing fee. There is also a product for users in your organization that are Team Members (the ones that don’t use PWA much and really want to only deal with Task Updates) that is called Project Lite. This is a monthly fee as well but is less expensive than Project Online.
Now is when it gets interesting. To access PWA for Project Online, you only need a browser (just like the way you do it in-house). However, there are a couple of options if you want to use Project Professional. You can not use Project Standard so that is not part of the Project Online discussion. You can purchase a copy of Project Professional 2013 and have it installed on the client machine. This means that you will use only that client machine (or another one that has Project Professional 2013 on it) to access the Project Online scheduling information if PWA isn’t sufficient to meet your needs.
The second option is to purchase Project Pro for Office 365 with Project Online. This is a great solution that allows you to stay in a “web-enabled/cloud” environment and not have to worry about having Project Professional 2013 on your local client machine. Basically, from a non-technical perspective, the way it works is that when you sign in from a client machine and need Project Professional capabilities you can temporarily “download and install” the Project Pro product. This allows you to work on any client machine with your Project Online tenant and when you are done the Project Pro is “deleted” from that client machine. See the table below that explains some of the capability/functional differences between Project Standard 2013, Project Professional 2013 and Project Pro for Office 365.
And, then there are varied methods on how to make this work as well. You can have a hosted tenant of Project Online. You can have a hosted tenant of Project Server that can be a shared or dedicated tenant. And, the options go on and on about the exact methodology about how you get to those instances but the basic differences of Online and in-house are laid out above.
The following is the brief comparison from the three Project client versions. This is directly from the www.Microsoft.com/Project site as of February 12, 2014, for the Project Management options tab on the Choose Project page. From the Project Management perspective, the recommendation is to have Project Professional 2013.
Project Standard 2013
Project Pro for Office 365
Quickly start projects
Quickly focus on what matters with an enhanced visual experience and an array of new project templates.
Keep projects on track
Proactively discover critical task paths and resolve potential scheduling problems.
Easily find and create great looking reports
Quickly share progress with easily customizable, out-of-the-box reports.
Explore the Office Store
Extend out-of-the-box capabilities with flexible apps.
Easily manage resources
Visually create the right mix of resources using drag and drop.
Call or instant message team members from within Project1
Collaborate with real time file and screen sharing via Lync integration.
Collaborate with others from virtually anywhere2
Stay connected to your team and projects no matter where work takes you.
Realize the power of unified project and portfolio management.3
Flexible plans and service updates keep you always up-to-date so you can deliver your best results
Enjoy seamless updates to always have the latest version of Project.
Access virtually anywhere with Project on Demand
Stream the rich Project desktop client onto almost any PC through Office 365 services.
1 Requires Microsoft Lync Online or Microsoft Lync 2013 (sold separately).
2 Requires SharePoint Online or SharePoint 2013, Project Online or Project Server 2013 (all sold separately).
3 Requires Project Online or Project Server 2013 (sold separately).
And, since we are copying the table from Microsoft, here is their table for which version works best for Project Portfolio Management. This is directly from the www.Microsoft.com/Project site as of February 12, 2014, for the Project Portfolio Management options tab on the Choose Project page. From the Project Portfolio Management perspective, the recommendation is to have Project Online with Project Pro for Office 365.
Project Online with Project Pro for Office 365
Project Server 2013 and Project Professional 2013
Flexible online solution
Easily sign up for flexible online plans that meet your PPM and work management needs.
Get your team up and running quickly with the latest technology and industry standards to separate PMO functionality from IT functionality.
Get started quickly
Focus on what matters most – easily aggregating everyday work, project tasks, important details and timelines.
Take action from more places and on more devices
Extend PPM and work management to virtually any device.
Align vision and effort
Extend PPM and work management to virtually any device.
Effectively manage resources
Enhance resource allocation and decision making to by seeing– even when they are managing everyday work or ad hoc projects in SharePoint task lists.
Strengthen everyday collaboration
Take advantage of new social capabilities to facilitate discussions, information sharing and your team’s ability to get work done.
Improve team communication with Lync, SharePoint, and Exchange integration.
Make data-driven decisions
Discover insights and make better decisions with summary dashboards and self-service reports in Excel.
Act and innovate with apps from the Office Store or SharePoint Store
Extend and customize Project with apps to fit your business needs.
Includes all of the features of Project Pro for Office 365 or Project Professional 20131
Stream Project Pro for Office 365 directly from the web.
1 Project Professional 2013 sold separately.
By: Collin Quiring
Three of us from PMP Specialists went to the Microsoft Project Conference 2014 in Anaheim, California. It was a great time for all of us. We met and got to know some new folks and we got re-acquainted with some friends in the Project community. There were around 136 sessions and, as always seems to happen to me, I usually wanted to go to two or three in every time slot. Thankfully, Microsoft is providing “video” from all the sessions from the event for attendees. (It isn’t really “video” as much as it is “audio with the slide deck/demos” – which is what we really want to see anyway.) So, I have my work cut out for me in the next couple of weeks as I make time to go back and view some of the presentations that I missed.
Tim Gryder and I presented on OPM3 (Organizational Project Management Maturity Model) and how Project Online, Project Server, Project Professional was a great tool that tied into OPM3 constructs and actually help to enable more organizational maturity. We had some great feedback and questions from the attendees and enjoyed our time presenting immensely.
A couple big announcements were made during the keynote session. The biggest one, from my perspective, was the ability to use SSRS (SQL Server Reporting Services) with Odata. Odata is the methodology by which reporting is enabled with Project Online and having the ability to use the power of SSRS is a HUGE step forward. There have been some struggles with getting Odata to work properly and consistently in the past but I am hopeful that Microsoft continues to improve its reliability. Another big announcement was the pricing change coming up for Project Online for what they Project Lite users. That is a big deal for some of our clients and better matches their needs!
As always, the evening event was great and Darin Brazile, from our group, tried his voice at karaoke at the House of Blues (thanks Project Hosts for sponsoring)! (http://ow.ly/i/4zd5a) He did a great job!
One of the overarching themes from the conference is that everything is moving online and that the future of Project is in Project Online (whether coupled with Office 365 or not).
By: Collin Quiring
Tim Gryder and I are honored to be presenting OPM3 concepts in relationship to Microsoft Project Server 2013 at the Microsoft Project Conference in California in 2014! Here is the abstract for our session.
The Organizational Project Management Maturity Model (OPM3) from the Project Management Institute (PMI) is a globally recognized best-practice standard for assessing and developing capabilities in Portfolio Management, Program Management, and Project Management. It is a wonderful tool and process to help understand where an organization ranks in maturity, capability, understanding and capability in regards to Project, Program and Portfolio Management. This provides an assessment that an organization can use to determine where they should focus future efforts to increase their ability and maturity. The results from the assessment can point to many different areas of the organization that might need some work. many of those involve business processes that can be directly assisted through the use of Project Server.
This presentation is an overview of how Project Server accomplishes the implementation of the assessment results of OPM3. Project Server is a powerful tool that can provide the necessary technology and process so that an organization can implement standardization and processes for improved organizational management. OPM3 is a great assessment tool and can show an organization areas for improvement but combining that assessment with Project Server capabilities and technology an organization can quickly realize improvement.
Project Server has the ability to help an organization with all three aspects of the maturity model – Portfolio, Programs and Projects. By tying together the results from the OPM3 Assessment with the functionality of Project Server an organization can quickly realize positive results. Project Server allows an organization to set up Portfolio information with drivers and other analysis tools which helps pick the right Programs and Projects to act upon. And then Project Server allows for the execution, analysis and reporting of the work in the chosen Projects and Programs.
Part of the OPM3 Assessment is about the documentation from the business process perspective. This is about having the appropriate documentation that corresponds to a Project or Program. Project Server is linked tightly with SharePoint Server which allows for the documentation, issues and risks to be maintained. With the integration of SharePoint and Project Server an organization can be more effective and can become more mature in their organizational abilities.
We believe that combining the capabilities of Project Server and SharePoint Server with the OPM3 assessment results is a natural fit of technology and process.
This presentation is an overview of how Project Server accomplishes the implementation of the assessment results of OPM3.
By: Collin Quiring
There is already a blog post that we periodically update with the information for Project Professional 2010 and Project Server 2010 – that can be found here.
But, we decided to start a new entry for the 2013 information. This is the information for Project Server and Project Professional 2013 as of October 24, 2013.
As a reminder, to check on your version from the SQL database for Proejct Server run this query:
Run SELECT * FROM Versions WHERE VersionId =’00000000-0000-0000-0000-000000000000′
Project Server 2013 :
Date Version KB
March 2013 (CU) 15.0.4481.1000 KB2768001
April 2013 (CU) 15.0.4505.1005 KB2737990
June 2013 (CU) 15.0.4517.1005 KB2817415
August 2013 (CU) 15.0.4535.1000 KB2817615
Project Professional 2013:
Date Version KB
March 2013 (CU) 15.0.4481.1000 KB2738031
April 2013 (CU) 15.0.4505.1000 KB2768336
June 2013 (CU) 15.0.4517.1001 KB2817338
August 2013 (CU) 15.0.4535.1000 KB2817502
By Collin Quiring
Microsoft support tells me that they are not taking bug reports on Project Server 2010 and 2013 and/or Project Web App (PWA) 2010 and 2013. They also wanted me to use a client support ticket to try and resolve this but apparently this bug has been around a long time in previous versions and Microsoft is aware of it so a support ticket wasn’t an actual resolution. Therefore, I share it here only to point it out and give you the few annoying workarounds that are available to you. They are annoying only in that they shouldn’t have to be used – not that they don’t work for some user’s purposes.
Here is the problem. When in the 2010 or 2013 version and in PWA in the Assignment Work by Project view in the Resource Availability screen the color coding from the legend disappears when you print (to file or printer). Or, more appropriately, becomes blank or clear.
NOTE – I am talking about when you print from the browser and not from the ribbon. The Print and Export to Excel in the ribbon do NOT display the graph when using the ribbon.
For example, this is what the graph and legend look like when in the view itself. This view is fine and the legend works great.
So, now, the user wants to print this out or otherwise to a PDF or other file for distribution. Unfortunately, when trying to do this the Legend becomes quite useless as it clears out and now the user has no idea which color belongs to which project. It now looks like this:
Unfortunately, there is no Microsoft fix that I am aware of that will be coming out for this issue (it still exists in 2013).
Therefore, the user is now forced to a workaround. The only workaround is to take a screenshot (Print Screen keyboard button, Snagit or Snipit or whatever other method) and put it into their document (as long as it is an editable document) that they are trying to send to other people. And, that is why I said it was annoying earlier in this post – wouldn’t it be nice to hit the Print icon in the ribbon and have it all there (because we want the graph and data part as well)? Or, at least use Print from the browser and have it work? And, while we are at it, wouldn’t it be nice for the Export to Excel button have the graph as well? So, the user now has to decide how they are going to get the image into the document they are using. They can export to file in the first place and then reformat the document to allow space for the image of the graph and then go back to the image in PWA and screenshot in whatever method and then go back to their document and paste it in.