Structure PPM
بواسطة Tempo Software
The typical implementation process for Structure PPM follows a structured, phased approach that focuses on integration with existing workflows, clear setup, and user adoption:
Deployment and Integration: Structure PPM is quickly deployed with minimal setup, especially for organizations using Jira, since it integrates directly and requires no code for configuration.
Configuration and Customization: The platform is tailored to match organizational hierarchies, project structures, and strategic goals, often with drag-and-drop modeling and flexible templates.
User Onboarding and Training: Non-technical users can start using the platform with minimal training, and real-time dashboards are accessible through Jira and Confluence, making adoption straightforward.
Structure PPM is highly customizable and is designed specifically to be tailored to fit a wide range of specific business and organizational needs, primarily through its flexible use of Jira data.
Custom Hierarchy Levels: Unlike native Jira, which is limited, Structure allows you to build any custom issue hierarchy you need. You can create as many hierarchy levels as required (e.g., initiatives, programs, epics, stories, sub-tasks) to accurately map your organization's work breakdown structure (WBS) or product lines.
Dynamic Structure Building (Automation): You can use Automation Rules (called "Generators") to build and maintain these hierarchies dynamically. This allows you to:
Insert issues based on JQL queries (e.g., project = XYZ and issuetype = Epic).
Extend the structure by automatically adding child issues based on Jira relationships (like issue links, epic links, sub-tasks) or any other field/criteria.
Group and Filter: You can group or filter issues using almost any Jira field or link to create different views for various stakeholders (e.g., group by Assignee, Priority, or Team).
Custom Formula Columns: Structure allows you to add Excel-like formula columns to calculate complex metrics in real-time within the structure hierarchy. This is one of the most powerful customization features, enabling you to:
Aggregate Data: Sum up values from child issues to the parent level (e.g., calculating the total Story Points, Time Spent, or Remaining Estimate for an entire program).
Custom Metrics: Write formulas to calculate unique business metrics like sprint velocity, cycle time, or an overdue epic count. The Structure Formula Assistant simplifies formula creation, even for non-technical users.
Visual Formatting: Formulas can also be used for conditional formatting (using Wiki markup language) to add color, icons, or text to quickly highlight specific conditions, such as:
Highlighting issues that are overdue or blocked.
Displaying a color indication for the calculation of Story Points based on a custom condition.
Custom Columns: You can configure the columns to display any Jira field (standard or custom fields) as well as Structure's own specialized columns, including:
Progress Columns: Display progress based on custom criteria (e.g., time tracking, status, or resolution).
Totals Columns: Show the aggregated totals of numeric fields (like time or story points) for all issues under a parent.
Saved Views: Once customized, you can save and share these unique configurations as "Views" to ensure all stakeholders see the same tailored data. You can also create personal views for individual work management.
Structure's functionality can be extended to support specific business processes through integration with other Tempo products:
Tempo Timesheets: Integrates time tracking data for precise cost allocation and budget reporting (e.g., translating time spent into development costs).
Tempo Capacity Planner: Integrates resource data to perform portfolio-wide capacity planning, ensuring resource allocation aligns with priorities.
Structure PPM offers vendor-supported help via the Tempo Help Center and support portal, plus in-app help, getting-started webinars, and extensive product documentation for both Cloud and Data Center deployments. Atlassian also directs Jira Cloud customers using Tempo apps to contact Tempo for assistance, confirming vendor-provided support as the primary channel.
Structure PPM protects data through encrypted AWS cloud hosting, GDPR-aligned processing, a published Cloud Security Statement, SOC 2 Type 1 assurance, configurable data residency, and strict operational access controls with 24/7 incident response procedures. For Data Center, customers control the hosting environment, with Tempo recommending TLS for encryption in transit and restricted database access as part of a shared-responsibility model.
Structure PPM Cloud receives updates frequently, with the vendor Tempo issuing new features, improvements, and bug fixes on a rolling release schedule—typically multiple times per month for Cloud, and several times per year for Data Center editions. All Cloud app updates are managed by Tempo and deployed automatically to customer instances, requiring no manual user intervention or downtime, ensuring customers always have the latest version and security patches.
For Data Center deployments, updates are managed by the customer: new Structure versions are published to the Atlassian Marketplace several times per year, with release notes indicating milestone versions and compatibility updates (such as adding support for new Jira versions). Administrators can choose when to apply these updates, which requires following standard Jira Data Center app upgrade procedures—including updating Structure itself and any installed extensions (such as Gantt or Pages) that may affect core functionality.
Tempo maintains detailed release notes and a public roadmap for Structure PPM, outlining new features, enhancements, and update cadence for both Cloud and Data Center. The roadmap is updated periodically and lists upcoming prioritized work so customers can track future changes and prepare for new capabilities or migration impacts. The Product Release Notes hub covers all Tempo products, including Structure Cloud and Gantt Charts, with changelogs and guides for each release.
Structure PPM’s data ownership and portability policies are set by Tempo and formalized through the End User License Agreement (EULA), Privacy Policy, and GDPR Data Processing Amendment. Customers own their Jira business data and retain rights to export, move, and delete their project, portfolio, and configuration data subject to platform and contractual requirements. Tempo, as a cloud service provider, processes and hosts this data under customers’ instructions and only for permitted business purposes.
The EULA confirms that data entered into Structure PPM (hosted by Tempo) remains the property of the customer, and upon contract termination, customers can request deletion or destruction of their data, or may themselves export their portfolio data at any time during active service. Tempo is obligated to return, delete, or destroy customer data upon request at contract end, supporting the right to data erasure as mandated by GDPR and referenced in the Privacy Notice.
Export and portability are built into Structure PPM: business data in Jira (including project, issue, structure hierarchies, and configurations managed by Structure) can be exported through CSV, JSON, or API access in line with Atlassian platform capabilities. Customers can export structure and hierarchy views for backup or migration, and can also move their cloud data residency between AWS US and EU regions using documented migration procedures, supporting data portability in geographically distributed organizations. Tempo’s policies confirm users’ rights to data portability, rectification, and deletion so long as the retention period or legal requirements do not preclude such action.
Structure PPM’s contract renewal and cancellation terms are based on the Atlassian Marketplace model and Tempo’s own EULA, encompassing auto-renewal options, advance written notice requirements, cancellation policies, refund eligibility, and post-termination data procedures. Subscriptions—monthly or annual—typically auto-renew unless cancelled, with the operative terms managed through Atlassian’s billing portal for Cloud deployments or the Data Center licensing workflow for on-premises.
Subscriptions auto-renew at the frequency specified in your order (monthly or annual), unless you provide written notice of cancellation at least 30 days prior to the renewal date. You may terminate your subscription at any time; cancellation is scheduled to occur at the end of the current subscription cycle, after which recurring charges stop and access continues until the paid period is complete. No refunds are issued for unused periods after cancellation unless you cancel within the first 30 days of purchase, in which case a full refund is available via Atlassian’s Marketplace policy for Cloud apps. After the subscription period ends and your site is deactivated, product data is retained for a period dictated by your plan or marketplace policy, and you may export or request deletion during this window.
If you breach material terms (such as reverse-engineering, decompilation, or confidentiality), Tempo may terminate immediately, retain any fees already paid, and require you to delete the app and all data associated with it. In the event of standard contract expiration or voluntary cancellation, your right to use the software will end, and Tempo will delete any confidential information from its servers unless otherwise agreed. Renewal invoices and notifications are provided via Atlassian’s billing portal, which allows admin teams to track and manage upcoming payment cycles, contract status, and undo scheduled cancellations if renewal is intended after a cancel action is issued.
Structure PPM software adheres to leading compliance standards, including GDPR, SOC 2, and ISO 27001, supporting enterprise requirements for data protection, privacy, and security controls across its cloud SaaS and Data Center offerings. Tempo (the vendor) regularly audits its practices against these standards to bolster enterprise readiness, with independent assurance and integration into Atlassian’s Marketplace security programs.
GDPR compliance is maintained for all processing of personal data from EU customers, with legal documentation supporting data subject rights, regulated transfer mechanisms, and a Data Processing Amendment for contractual adherence. SOC 2 compliance is achieved through third-party auditing of security and availability controls for Tempo’s cloud services, providing clients with documented evidence of control design and effectiveness for vendor risk programs and regulatory reporting. ISO 27001 compliance is implemented within Tempo’s security objectives and operating policies, with initiatives for certification by Q4 2026 and ongoing improvements in risk management practice, access controls, and incident response.
