3 Replies Latest reply on Jul 24, 2018 3:00 PM by sherif.eisa

    Required information for datalink reports

    sherif.eisa

      What the important data which I should get it from end user to build a good report and connecting to PI server or PI-AF

        • Re: Required information for datalink reports
          Sidh

          Hello Sherif,

           

          Your question is very generic I will try to answer.

           

          If you have to do a requirement gathering related to a report you have to ask following -

           

          1. What data\asset user is looking for, accordingly you will select the server ( In case you have many servers)

          2. What function\calculation he want to see as result in the report.

          3. Format of the report.

          4. Update frequency etc.

           

          Rgds

          1 of 1 people found this helpful
          • Re: Required information for datalink reports
            aredding

            Hi Sherif,

             

            Provided below are key items to consider when creating a report for an end user.  While this guidance is geared for complex reports, these items can also help build smaller reports:

            • Identify who the target audience is.  If its for personnel who receive numerous reports, for example executives or team leads, consider adding a sheet containing an executive summary.  If the report will also be shared with peers, consider providing enough details so they build a similar report and establish best practices.
            • Build reports so that ownership can be easily transferred in the future.  Including column headers, column sizing, colors/shading, and formatting are all important.
            • When using Multiple Value or Calculated Data queries, add the name of the variable at the top of the column.  This helps users navigate the PI DataLink report.
            • The left column and top row can be reserved for bookmarks or notes.  Pressing keys CTRL + Down Arrow will jump to the next cell containing text in a column.
            • Consider utilizing one large Excel workbook to spin-off a bunch of smaller reports.  It can help to include shared parameters, for example Start/End time or a list of variables, in one sheet that are then referenced elsewhere in the report.
            • Include supporting information.  If there's information coming from another source, for example a constant in a calculation, consider adding a reference within the sheet.  Avoid "black box" calculation inputs.
            • Ask where all the information is coming from.  For large PI DataLink reports, consider separate groups of information into separate sheets to minimize maintenance of the report.  This can include separating operating data, calculation constants, design info, and financial data, and then combining this data together in other sheets.

             

            Best regards,

            Aaron

            1 of 1 people found this helpful