Purpose: This questionnaire gathers what we need to design and build the custom sync connector between your scheduling tool (Primavera P6 / MS Project) and Agentic PMO. Your answers scope the work, drive the field mappings, and set the sync cadence. It is also why this connector is custom-built — your custom fields and workflow are unique, so a generic off-the-shelf connector won't fit.
Time to complete: ~30–45 minutes. Some questions are best answered by your PMO/scheduling lead and your IT/API owner together.
Confidentiality: Responses are used only to scope and build your integration. API credentials, when shared later, are stored in environment variables — never hardcoded in source.
About You
Client / organisation
Primary contact (name, role)
Email / phone
Target project(s) or portfolio
Date completed
Completed by (name, role)
1. Your PMO / Scheduling Tool Stack
1Which tool is your schedule of record?
2Version & deployment
3Is REST API access available?
4Authentication method, and who manages the credentials?
5Do you also use a separate cost/ERP or resource system that you'd eventually want synced?
2. Scope
6Which projects should be synced?
7Roughly how many projects, and how many tasks per project?
This drives pagination and the sync interval.
8Which fields should be synced?
9Milestones — do you use milestones and want them tracked?
10Sync direction?
11Conflict policy — when the same field is edited in both systems, who wins?
3. Custom Fields — the #1 driver of build effort
Why we ask: Custom fields are the main reason a generic connector won't work and the biggest variable in build time. Thorough answers here save the most effort downstream.
12List all custom fields / UDFs used on the target projects.
13For each custom field: name, data type, which discipline/team uses it, and what it tracks.
4. Schedule & Cadence
14Acceptable sync cadence?
15Blackout windows?
16Is this a new project starting fresh in Agentic PMO, or existing data in both systems?
5. Infrastructure & Network
17Where should the sync engine run?
18Does the sync engine need to traverse a corporate proxy, VPN, or firewall?
19Is there a test/staging environment for your scheduling tool?
6. Notifications & Alerts
20Where should sync-failure alerts be sent?
21Want a daily sync summary of what changed?
7. Document / CDE Integration — optional
22Do you use a Common Data Environment (CDE)?
23Which document milestones should Agentic PMO monitor?
24Does the CDE have API access, and is it enabled?
What Happens Next
1
Discovery
Review answers, validate API access, map fields
2
Build
Build connector, test against sample data
3
Deploy
Initial full sync, 48-hour monitoring
4
Handover
Source code and documentation
8–12
Days Total
After questionnaire complete
Estimated build effort: 8–12 days after this questionnaire is complete and API access is confirmed. The integration-layer code is owned by you.
Complete this form in your browser, then save as PDF or print.