RpReports More

More about RpReports

RpReports Toolbar

Note: This is a sample toolbar for the demonstration. The OEM Partner can create a custom toolbar for the RpReports Client .

• - Settings - Options, help, etc.
• - Demonstration - Load the demonstration model.
• - Select component - The component placement wizard will be replaced by, or augmented by, the components for the OEM Client's custom application.
• - Attributes - view and edit attributes for the selected component.
• - Reports - Generate a component report.
• - Attribute Levels - Select the level of components displayed and reported.

Attributes

RpReports makes it easy to predefine attributes for components and modify the attributes for Component Instances and groups once placed in SketchUp.

There are two ways to predefine components:

1. Save the attributes on the component definition, so they are automatically assigned when the component is placed.
2. Store the attributes for each component in an external database, keyed by component name.

Both methods may be used at once at the same time, depending on the application you set up.

Attribute Editor

After placing components into you SketchUp model, you can override the attributes for a component instance. For example, Manufacturer and Part Number may be preassigned (and not changeable), but Cost, Building, Floor and Department may be set for each component instance.

Groups

Note: You can also produce reports for top-level groups (not sub-groups of components or other groups). There is no way to predefine attributes for groups.

If you are running an indented Bill of Materials, any components withing a top-level group assembly will be aggregat4ed into the group for reporting purposes.

Levels

The OEM Partner defines levels of attributes for editing and reports.

All attributes are defined for all components. The levels of attributes allow different viewing of attributes and different reports. This is valuable for creating reports which included different levels of costing and pricing. (See #Cost and Price)

Cost and Price

Cost and Price require some thought. For example, Cost may be the cost for the component from the supplier, and Price would be the client price. In this case, you may want two or more levels or reports. For example:

1. Parts list with no pricing - for initial client presentations
2. Parts list with pricing - for final client presentation
3. Parts list with price and costs - for dealer's internal use
4. Parts list with cost only - for placement of the order with manufacturer.

These will be handled by defining different levels of reporting.

Reports

A simple report is provided for the components placed. This include totals of some fields, such as quantity and extended cost, and automatic calculation of extended cost (quantity x cost).

In addition to the PDF reports, the user can export the report data to a .CSV file for use with Excel format to allow further customization.

See: RpReports Report Settings

Customization

Customization is performed by modifying three external database files:

1. Project Settings - such as the name of the project and client settings.
2. Attribute Definitions - define sach attribute, type, whether the user can modify it, and whether it appears on the reports.
3. Default Attributes - assign the initial attributes for each component based on component name.

See: RpReports Customization

Bill of Materials

RpReports can produce an indented Bill of Materials , which shows the sub-components of a component and calculates the cost of the component

See Bill of Materials for information on how to setup RpReports for an indented Bill of Materials.

SQL and RpReports

There are two parts of the SQL interface.

1. SQL attributes for component definitions
2. SQL as a receiver for the entire .CSV file of the report.

SQL Attributes

Regarding SQL attributes - we can store them in SQL, or in both the database and SQL. In the former case you can easily modify them in SQL - but the SQL database needs to be available when querying the database or making reports. In the latter case (both), you can also update them using SQL - we can update the database to match the SQL as you suggest.

In neither case is it possible for the user to modify the SQL attributes from RpReports. (Similarly, the user cannot modify the attributes stored on a component definition using RpReports. The user can override the attributes by assigning an attribute to the component instance, but cannot change the base attributes.)

SQL update from report

RpReports can also create or modify an SQL table at the time of the report.

This data would then be read and processed directly by your other SQL applications.

Walls and RpReports

Wall Groups

What we have done in our wall system - RpWallMaker is to make each wall a group. One potential user has said this makes it too hard to edit the walls, since you have to open the group to edit it. (We feel it makes it easier to work with walls - because everything about the wall is stored in a group.)

If you place your walls in groups or components, then you can assign attributes to them and include them in the report.

Walls as individual faces

When you just draw walls as faces and extrude them to make them wide walls, then it can become more difficult to identify the walls. (For instance, an exterior wall may be thought of as a single outside wall, but be different inside walls)

We could try assigning attributes to each side of the wall, separately, or even to the material, if that would help identify age of paint, etc. We could offer a right click on faces to identify the face as a wall.

Getting started

1. Download the latest version of RpReports from: Download Page
2. Run through the RpReports Tutorial to see how a smaple application works for a typical End-user Client .
3. Read through the Customization document.
4. Modify some of the RpReports_Demo project files.
5. Load the RpReports_Demo project.
6. See if your modifications worked.

If you have any problems or suggestions, post your comments on the RPS Forum.

Layers and hidden components

Hidden components and components in layers which are not visible do not appear in the reports.

When performing an indented Bill of Materials, hidden sub-components and sub-components in invisible layers are included in the report. This allows you to include sub-components which are available for cost calculations, but which to not appear in your model.

Features in development

The first version includes the ability to define your own attributes, and preset the attributes for components. (as well as reporting and placement as part of SpaceDesign )

Here is what is planned for future versions:

• ability to update existing attributes for a master file (for example if there has been a price change.)
• ability for the OEM Client to implement its own ruby scripts to be called at various parts of the process
• ability for the OEM Client to create modal dialog boxes which use, change and set variables for its ruby scripts.
• other things as they are suggested by OEM Clients.

Be sure to let us know what improvements you would like on the RPS Forum

Pricing

You may purchase OEM Licenses of RpReports for personal, or one-user applications.

You may purchase multiple copies at a greatly reduced price for applications which are deployed to multiple users - either within you firm - or by your sales representatives or clients.

See: RpReports Pricing for pricing information.

Downloads and Installation

There is a 30 day Trial Version for RPS products. This is a fully functional version, with watermarks or other text added to indicate that it is a trial version.

Follow the links from the Downloads Page to download the latest version.

• See: How to Download and Install

See also

• RpReports
• RpReports Customization
• Bill of Materials
• RpTools