Skip to main content

Platform

The Platform group in the Agentic Transformation Platform (ATP) sidebar holds 5 assessment pages. Each page is run by the same agent, The Director (deterministic agent for platform assessments). Use this page to choose the right assessment and prepare the evidence it asks for.

Before you start​

  • Every page in this group uses the same assessment workspace. To learn how to upload evidence, run an analysis and ask follow-up questions, read Run an assessment.
  • Upload metadata and exports only. Each page's Instructions panel says what not to upload.

Open a page in this group​

  1. In ATP, open the menu at the left of the navigation bar.
  2. Expand Platform.
  3. Select the page you need.

When a page from this group is open, the navigation bar shows the group's pages as tabs, so you can move between them. Pages that don't fit are under More.

Pages in this group​

PageWhat it covers
Service CatalogCloud service catalog and provisioning.
Configuration ManagementConfiguration management and automation.
AMI Management & Patch ManagementAMI and patch management processes.
Database ManagementDatabase administration and optimization.
Batch ManagementBatch job scheduling and management.

Service catalog​

Select Service Catalog to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with The Director. The sidebar describes it as: Cloud service catalog and provisioning.

The Instructions panel is titled How to Generate Your Service Catalog Provisioning Assessment. It says:

To generate your service catalog report, The Director only needs metadata (catalog definitions and usage patterns) — not business data. Upload raw exports from your service catalog platform, no JSON wrapping or special formatting is required.

It lists the evidence to upload:

  • Service Catalog Definitions: Service offerings, service definitions, fulfillment workflows, SLA & compliance requirements, and standard service specifications.
  • Request Fulfillment Data: Service requests, fulfillment records, service delivery timelines, approval workflows, and request intake data.
  • Service Performance Data: Service availability metrics, fulfillment SLAs, SLA breach records, and service quality indicators.
  • Service Portfolio Data: Catalog governance documentation, service categories, catalog naming conventions, and target state definitions.
  • Provisioning Automation: Infrastructure-as-code templates, automation workflows, self-service provisioning configurations, and pipeline integration data.

The panel also shows this note:

Important: Do not upload customer data, PII, or sensitive records — The Director analyzes catalog patterns and provisioning workflows, not customer content.

Configuration management​

Select Configuration Management to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with The Director. The sidebar describes it as: Configuration management and automation.

The Instructions panel is titled How to Generate Your Configuration Management Report. It says:

To generate your configuration management report, The Director only needs metadata (configuration baselines and change history) — not business data. Upload raw exports from your configuration management tools, no JSON wrapping or special formatting is required.

It lists the evidence to upload:

  • CMDB Schemas & CI Data: Approved CI types and categories, CMDB configurations, relationship types, CI reference data, and discovery rules.
  • Configuration Baseline Data: Baseline configurations, approved configuration states, drift history, and rollback information.
  • CI Relationships & Patterns: CI dependency maps, change impact analysis records, relationship mappings, and configuration topology data.
  • Change & Config Deltas: Configuration change records, audit trails, change frequency data, and delta analysis reports.
  • Toolchain & Systems Integration: Automation tool configurations, discovery system setups, ITSM integrations, and deployment workflow data.

The panel also shows this note:

Important: Do not upload sensitive infrastructure configurations or live system credentials — The Director analyzes configuration patterns and baselines, not live system data.

AMI management and patch management​

Select AMI Management & Patch Management to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with The Director. The sidebar describes it as: AMI and patch management processes.

The Instructions panel is titled How to Generate Your AMI & Patch Management Report. It says:

To generate your AMI and patch management report, The Director only needs metadata (AMI inventory and patch status) — not business data. Upload raw exports from your AMI management systems, no JSON wrapping or special formatting is required.

It lists the evidence to upload:

  • AMI Inventory & Metadata: AMI catalog, owner information, creation dates, OS types, deprecation status, and compliance classification.
  • Patch Compliance Data: Patch windows, missing patches, criticality ratings, compliance statements, and exception records.
  • Vulnerability Data: CVE findings, vulnerability scan reports, risk severity ratings, remediation timelines, and patch coverage data.
  • Patching Workflows: CI/CD pipeline configurations, software change request records, patch standard workflows, and approval processes.
  • Patching Performance Metrics: Patch deployment success rates, mean-time-to-patch metrics, rollback occurrences, and compliance trend data.

The panel also shows this note:

Important: Do not upload sensitive security configurations or live infrastructure credentials — The Director analyzes patch patterns and AMI compliance, not infrastructure configurations.

Database management​

Select Database Management to open this page. The page header shows the badge Database operational readiness and the line Expert Consultation with The Director. The sidebar describes it as: Database administration and optimization.

The upload area on this page accepts these file types: .txt,.csv,.xlsx,.pdf,.json,.xml,.zip,.sql.

The Instructions panel is titled Teradata Metadata Package for Migration & Optimization. It says:

To produce the migration and optimization report, The Director only needs metadata and workload telemetry. Do not upload table data. Export the items below from Teradata Studio, SQL Assistant, BTEQ, Viewpoint, or equivalent tooling and upload them as plain text, SQL, CSV, spreadsheet, or zip files.

It lists the evidence to upload:

  • DDL for all objects in scope: Tables, views, join indexes, macros, stored procedures/UDFs, and triggers. Preferred exports include SHOW TABLE, SHOW VIEW, SHOW JOIN INDEX, SHOW MACRO, and SHOW PROCEDURE output. For large estates, include object lists from HELP DATABASE or DBC.TablesV.
  • Table size, skew, and space usage: Export DBC.TableSizeV and, where available, DBC.AllSpaceV or DBC.DiskSpaceV. Include database name, table name, current perm, peak perm, and row counts when available.
  • Column definitions and data types: Export DBC.ColumnsV or DBC.ColumnsVX so datatype mapping, nullability, defaults, compression, and migration compatibility can be assessed.
  • Indexes, constraints, partitioning, and statistics: Include index metadata from DBC.IndicesV, RI metadata from DBC.AllRIChildrenV and DBC.AllRIParentsV, partitioning from SHOW TABLE or DBC.PartitioningConstraintsV, and statistics coverage from DBC.StatsV, DBC.StatsTbl, or HELP STATISTICS.
  • Workload sample and query telemetry: Provide a time-bounded 7-30 day sample from DBC.DBQLogTbl plus, if possible, DBC.DBQLObjTbl, DBC.DBQLStepTbl, and DBC.DBQLSqlTbl. Include top queries by CPU, I/O, elapsed time, SQL text, masked user/account strings, error codes, and explain plans for the top 20-50 queries where available.

The panel also shows this note:

Data Safety: Do not upload raw table data, PII, customer records, credentials, or regulated content. This process analyzes architecture, metadata, and workload patterns only.

Batch management​

Select Batch Management to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with The Director. The sidebar describes it as: Batch job scheduling and management.

The Instructions panel is titled How to Generate Your Batch Management Report. It says:

To generate your batch management report, The Director only needs metadata (job definitions and scheduling data) — not business data. Upload raw exports from your batch scheduling systems, no JSON wrapping or special formatting is required.

It lists the evidence to upload:

  • Job Definitions & Metrics: Batch job definitions, schedules, execution records, job parameters, dependency chains, and resource requirements.
  • Execution History & Metrics: Run outcomes, duration data, resource utilization per job, failure rates, and retry configuration.
  • Dependency Mapping: Inter-job dependencies, upstream/downstream relationships, critical path data, and scheduling conflict records.
  • Performance & Analytics: Execution throughput metrics, error rate trends, SLA adherence data, and capacity utilization analytics.
  • Workload Processes: Automation workflow configurations, scheduling policies, alerting configurations, and operational runbooks.

The panel also shows this note:

Important: Do not upload sensitive data, PII, or sensitive records — The Director analyzes batch job patterns and scheduling workflows, not business transaction data.