Planview Test Page

Last updated
Save as PDF

PRM Interfaces

Introduction

Documentation Templates

Core Architecture & components

All interfaces are deployed with a common set of components offering standard functionalities, which can be activated and/or configured individually.

Name	Description	Links
Configuration parameters	Default list of interface parameters used in various places (ex: data retention logs). Option: Maintenance of interface configuration parameters within PVE, i.e. self-maintenance by customer possible.	Details CSC
Monitoring	Option: Overview of last interface run & previous run, with access to run information within PVE, i.e. direct customer access. Mail notification in case of issues.	Details CSC
Logging	Log file stored Content Management (i.e. accessible from PVE directly) and/or in shared location. Log archiving (default 90 days). Option: Standard Logging or Extended Logging.	Details CSC
Data Source	Source “data” stored in Content Management (i.e. accessible from PVE directly) and/or in shared location. Option: Source data archived in dedicated DB Table (for reporting) – recommended for complex interfaces that need detailed debugging.	Details CSC

Best practices (Standard) Interfaces - Imports

All our standard interfaces provide by default the services mentioned above, as defined by the customer

Template for Interface SOWs can be found under the following location: SoW

A Blank Specification Template can be found under the following location: GIS Interface Specification Template.

When available, links to the Interface Specification template, the Customer Success Center Page, and the CSC internal page for that specific interface are provided. Links to additional documentation might be provided as well.

Import	Description	Links	Main Functionalities
Financial	Import of Actual/Forecasted costs into PVE Financial Plans.	Spec CSC	Standard: Pre-deletion of costs before imports (Full Import). Aggregation of data from multiple sources. Aggregation of data on existing accounts (Delta Load).
Resource	Creation and maintenance of resources, users and Resource Breakdown Structure in PVE. Creation and maintenance of resource and user attributes.	Spec CSC	Standard: Maintenance of the RBS (no deletion). Maintenance of resource attributes List of Values (no deletion). Creation, update, de-activation, re-activation of resources (no deletion). Creation, update, de-activation, re-activation of users (no deletion). Association of resources to users. Assignment of user roles. Non-Standard: Maintenance of Resource grants following given line management hierarchy. Assignment of Lifecycle Roles to users (attributes).
	Coming soon ...
Structure
Project

Best practices (Standard) Interfaces - Exports

Data Importers

What is New ?

A new generation of Data Importers is currently being worked on, to get rid of the Actian legacy and make best use of the latest version of the Web Services.

Configuration / Deployment / Installation

• One configuration file to be deployed on Customer/Environment, then all data importers can be used right away.
• Consultant gets individual access to his Data Importer, which can be used on all Customers/Environments (that have been configured).
• Consultant to install one application locally in order to run the Data Importer.

Processing

• A Data Importer Generator (Excel) is provided with instructions, that will generate a formatted data importer file and the configuration parameters to import that file.
• Live eMail notifications on import start and completion, live access to log files on shared FTP server.
• Self-Service: The Consultant can run and re-run the importer, by himself, at any point and time, no idle time between import creation, run and validation.

Import Scenario Capability

The use of unique and automatically generated external keys during the process allows to create a “Set” of importer files which can be used on any environment without any (manual) adjustment(s).

Example of scenario:
• Create a project.
• Create 10 tasks under this project.
• Create 30 reservations under those tasks.
-> Create a project with ekey:/2//upload524/Project123.
-> Create 10 tasks with ekey:/2/Upload524/Task 1- 10 under that project with this reference, which will never change.
-> Create 30 reservations under those tasks with ekey:/2/Upload524/Reserv1-30, also linked to the task ekey that will never change !

Re-run the same file as an update at any point and time by just changing the wrong data point, thanks to the unique reference, on any environment.

Once the process has been assessed on pre-prod, re-run the exact same files to production, without manual re-work needed
• Increased efficiency
• Decreased risk for man-mistake
• Simplified maintenance

Note: Previously you would have had to export sequence ID from the specific environment where the item would have been created, or even after each import / re-import, to regenerate the files with a significant possibility to indicate the wrong parent ID, for example when multiple parents are used...

Importers

Importer	Description	Links	Main Standard Functionalities	Out of Scope / Not supported
Project (In Progress - version available)	Creation and update of projects and project attributes.	Generator Instructions	• Create a project if it does not exist. • Update a project if it exists. • Update Project Attributes as: + Custom Fields (all types: date, text, long text, date, currency) + Alternate Structures - Single-Selection, passed by Description - Single-Selection, passed by Sequence ID - Multi-Selection, passed by Description, with/out Primary Value	• Deletion of projects. • Update of Project Status. • Update of Associated Values for the Multi-Selection alternate structures. • Update of Multi-Selection alternate structure by Sequence ID. • Creation/Maintenance of Alternate Structure values.
Coming soon...
Structure (In Progress)	Creation and updates of structure values			• Creation of structure. • Update of structure definition.
Resource (Backlog)

Custom Interfaces between our own Solutions.

Product Management is in charge for connections (integrations) between our solutions.

Letting PS create custom interfaces between our products will sooner or later lead to issues between the standard connectors and the custom integrations.

When there is high pressure from the customer or prospect, we should follow the following process:

Have a discussion what they want to achieve with the interface => much more a Business discussion than a technical discussion.
- This should be lead by the Managing Consultant (and maybe the Solution Architect / Functional Consultant).
- If needed GIS can help, but that should be a rare exception.
Understand if the Business Goal(s) can be achieved with the OOTB connectors that Product Management provide.
- Again, Managing Consultant / Core Team take the Lead.
- Potentially checking back with Product Management.
- Push back on things that are on the Roadmap.
If understood that neither current nor future Product functionality has the desired outcome, and the customer is still pushing for it.
- Make clear that the Customer understands that ...
  - this is a CUSTOM interface just for them.
  - it is NOT intended to work in parallel to the standard connector between the two impacted solutions.
  - there is a desire to replace this custom interface by the standard connector as soon as the standard connector has the desired functionality.
- Have a call with GIS / Managing Consultant to understand the scope and what could theoretically be done and estimate effort / cost.
Before we give any estimate or do anything:so that we can decide together, if we really want to go down the route of custom interfaces.
- Check with Product Management again to get their Approval to offer this exception.
- Have a call with:
  - The Managing Consultant.
  - The person from the GIS who understands the use case best (Tim, Udo, Don...)
  - Product Management (Marcus Klein / Jon High) if not clarified before
  - Laurie or Henrik (depending on if this is a US or EMEA owned customer)
Make sure to include wording to cover the points above (3.) in the Specifications, get the Customer Sign-off, start the normal Integration process.