Detailed Overview

1. Data Handling & Security

1.1 What Data PACT Uses

PACT works with Jira issue data that represents your contractual obligations. It utilizes data already living in your AGC Jira site:

  • Contract Hierarchy: Issue types representing Contracts, Requirements, and Negotiations.

  • Financial Data: Custom fields for Budget, Cost, and Actuals.

  • Timelines: Start dates, End dates, and Renewal deadlines.

  • Issue Links: Relationships (e.g., blocks, relates to) that define the breakdown between a Master Agreement and specific Requirements.

1.2 Where Data Lives

  • Contract Content: Stored as Jira Issues within your AGC Jira environment, inside Atlassian’s FedRAMP Moderate boundary.

  • App Configuration: Stored in Atlassian-hosted app storage (Forge Storage) tied to your site; there is no separate Optimizory database that holds AGC customer contract data.

  • Optimizory holds only standard commercial data (e.g., billing and admin contact information) via Atlassian Marketplace and your support interactions, as outlined in our privacy policy. We do not store contract terms or financial values.

1.3 Data Flows Relative to the AGC Boundary

For runtime behavior, the flow is entirely inside AGC:

  1. Jira UI on AGC loads the PACT dashboard.

  2. The front-end calls Jira REST APIs and Forge functions to calculate burndown charts and financial totals.

  3. Forge returns processed results back to the UI.

Because this is a Runs on Atlassian Forge app:

  • All compute and storage for runtime data is on Atlassian-managed infrastructure.

  • There is no app-level requirement to send Contract data outside the AGC environment.

2. Architecture Overview on AGC

2.1 Components

  • Jira Cloud on AGC: Your contract issues, financial fields, and permissions live entirely here.

  • PACT UI inside Jira: Dashboards and Issue Views appear in Jira’s Apps menu and Issue Glance. The UI is rendered by Atlassian.

  • PACT Forge Backend: Stateless serverless functions run on the Forge runtime (Atlassian-hosted). They read Jira data to generate "Budget vs. Actuals" reports and "Contract Burndown" charts in memory.

2.2 What Isn't There

  • No Customer-managed server component.

  • No Optimizory-hosted data store containing contract terms or costs.

  • No Direct inbound connectivity into AGC from Optimizory infrastructure.

  1. Operations & Support for AGC Customers

3.1 Day-to-Day Operations The platform (AGC, Jira, Forge) is operated and monitored by Atlassian. PACT features (app logic, UI rendering) are owned by Optimizory releases via the Marketplace. AGC admins can use Atlassian’s organization audit logs to track when PACT is installed or configured.

3.2 Support & Incidents

  • Product-level support (e.g., "How do I configure a custom cost field?") is handled via the Optimizory support channel.

  • Platform-level incidents (AGC availability, SSO) are handled by Atlassian Support.