Quick orientation so we start aligned

• How often does your planning organization face a study backlog that exceeds six months? Options: Multiple times a year, Once a year, Every few years, This is the first time
• Describe the last time you escalated a backlog issue to executive leadership and the outcome they required
• When you say 'study capacity constraints', who on your team is most directly impacted day to day? Options: Transmission planning, Operations, NERC/compliance, Interconnection queue management, Project controls/PMO, Other
• Estimate how many outstanding interconnection studies in your queue are currently at risk of missing RTO deadlines Options: 1-10, 11-25, 26-50, 51-100, 100+
• Could your executive sponsor commit to a decision briefing within two weeks if the initial SOW matches priorities? Options: Yes, Maybe with conditions, No

Where the backlog hurts most

• If you lost a single major interconnection customer because a study missed an RTO deadline, what immediate financial or operational impact would that create?
• How often over the last 12 months have you received formal notices or threats from interconnection customers about leaving the queue? Options: Never, Once, 2-5 times, More than 5 times
• Tell me about the most recent study the RTO sent back for revision, what specifically triggered the rework?
• Which single failure mode, if not addressed, would guarantee a missed deadline or audit finding within the next 6 months? Options: Model inaccuracies, Missing or mis-scoped study work, Insufficient staffing, Data access delays, Regulatory interpretation dispute, Other

Who's accountable and who moves first

• Who has final sign off for study acceptance and who signs the paperwork that commits your team to RTO timelines? Options: VP Engineering, Transmission Planning Manager, NERC Compliance Officer, Project Controls/PMO, Procurement, Other
• Name the roles that must be available from your side during the engagement and the realistic full-time equivalent availability for each
• Do you have a single point of contact authorized to approve deliverables and accept invoices? Options: Yes, No, multiple approvers, No, authority varies by deliverable
• If your nominated lead engineer became unavailable, who could step in immediately without delaying deliverables?

Regulatory deadlines that will make or break this

• Which RTO or NERC deadlines are binding for the studies in your queue over the next 12 weeks? Options: Interconnection study completion, NERC compliance deliverable, Resource adequacy filing, Other
• By when must each of those deliverables be submitted to avoid penalties or loss of queue position, list dates or weeks if known
• Are there pending audits or compliance reviews tied to these studies that a late delivery would jeopardize? Options: Yes, NERC audit, Yes, RTO compliance check, Possibly, internal audit, No
• What single regulatory consequence would make you pause engaging an external vendor today? Options: Risk of audit finding, Material monetary penalties, Loss of queue rights for customers, Executive refusal to proceed, Other

Model, data, and toolchain readiness

• Walk me through the model files, scenario definitions, and tool versions you treat as the authoritative source for interconnection studies
• List the data owners and the secure transfer methods currently approved for sharing system models and market data Options: Named internal data owner(s), SFTP or secure file transfer, VPN with role based access, Platform API with tokens, Not yet defined, Other
• Confirm whether your primary study platform versions match the RTO versions used for official review Options: Yes, fully aligned, No, versions differ, Some tools align, some do not, Unknown
• Describe the highest probability data or model gap that could force a study re-run after initial delivery
• Identify who on your team can approve a model change or accept residual model risk so work can proceed on schedule Options: Transmission Planning Manager, NERC Compliance Officer, Senior Engineer, Project Controls, No authorized approver yet

Known risks and blockers

• Identify the single operational risk that most often caused study delays in the last 12 months Options: Data delivery delays, Staff turnover, Scope disagreements, RTO rework requests, Tool incompatibility, Other
• Explain how change orders or scope creep are currently processed and how long approvals typically take
• Estimate the average number of business days added to a study schedule when rework is required Options: 0-5 days, 6-15 days, 16-30 days, More than 30 days
• Share which internal approvals most commonly create the longest delays and why
• Would you be able to authorize a fast track fix that keeps the schedule if a critical data handoff failed in week one? Options: Yes, authority in place, Yes, but needs executive sign off, No, would delay the schedule

The alternative paths you are weighing

• What alternatives to hiring external study relief have you evaluated, including incumbents, in house options, or other consultants? Options: Keep internal team, Hire large multi discipline firm, Offshore provider, Temporary contractors, Other consultants, No alternatives evaluated
• Have any internal teams proposed absorbing the backlog without outside help and what trade offs did they estimate? Options: Yes, with overtime, Yes, by reprioritizing projects, Yes, with contractors, No internal proposal
• List the specific criteria that would make you prefer the incumbent or an internal fix over bringing in a new partner Options: Lower cost, Existing model knowledge, Faster ramp up, Contractual familiarity, Political considerations, Other
• Is there a single condition under which you would cancel vendor selection and keep your current approach? Options: Yes, No
• Name the stakeholders in procurement or legal who will need to approve third party access to models and why

Clear acceptance signals and how we measure success

• Assuming we proved study results to the RTO's satisfaction, what would make you sign acceptance and trigger billing within a week?
• Rank the acceptance artifacts that matter most: validated model, run logs and scripts, RTO ready analysis package, executive summary Options: Validated model, Run logs and scripts, RTO ready analysis package, Executive summary and impact statement, Knowledge transfer session
• Specify the maximum number of formal review cycles you will accept before you consider the deliverable rejected Options: 1, 2, 3, More than 3, Depends on deliverable
• Would an executive level assurance of senior engineer time and named replacements accelerate your decision to proceed? Options: Yes, definitely, Possibly, No
• Share any procurement or audit criteria that would prevent acceptance even if the technical work meets specifications

Commitment timing and immediate next steps

• By when would your team need a signed mutual commit and SOW to hit the critical RTO dates? Options: Within 2 weeks, Within 4 weeks, Within 6-8 weeks, Longer than 8 weeks, No firm date
• Clarify the approval path and estimated time each approver needs once you receive a proposed SOW
• Are there budget gating items or capital approvals that would block signing within your needed window? Options: Yes, require capital approval, Yes, operating budget only, Budget in place, Unsure
• Could your executive team commit to a pilot or fixed scope tranche that shortens procurement timelines? Options: Yes, Maybe, No
• Will any single missing element on our readiness checklist, for example named data owners or an approved secure transfer method, stop you from signing an SOW this month? Options: Yes, list the elements in the comment, No, we can proceed without one or two items, Not sure

• Assumption and Scope Clarification, Study Prioritization
• Per-Study Model and Data Inventory
• Technical Assumptions Validation and Acceptance Criteria
• Study Sequencing, Resource Commitment, and Run Schedule
• Deliverable Acceptance Checklist and RTO Submission Readiness

• Publish the final study schedule with milestone definitions and review points.
• Confirm the reporting template and file format to be used for acceptance reviews.
• Propose sequence and parallelization options
• A final study execution schedule with milestone dates and sequencing agreed.
• A documented staffing commitment including senior-engineer review points and expected turnaround times.
• A contingency plan listing actions and timeline adjustments if model or data gaps appear during execution.
• Confirm engagement constraints and deadlines
• Record the committed senior-engineer availability windows and escalate any conflicts prior to the first run.
• Prepare the contingency triggers and adjustment procedure to be used if delays occur.
• Review deliverable components against acceptance criteria
• A completed deliverable acceptance checklist that will be used to verify each study deliverable.
• A documented RTO submission package template and a clear go/no-go condition for submission readiness.
• A defined sign-off workflow and timeline that triggers billing and formal handoff.
• Publish the acceptance checklist and the RTO submission package template.
• Confirm the sign-off workflow participants and the timing that triggers billing.
• Record the post-acceptance support scope and response time commitments for audit evidence.
• A finalized prioritized list of up to three interconnection studies with documented rationale for the rankings.
• A per-study list of required deliverables and whether RTO-ready artifacts are required, recorded for follow-up sessions.
• A constraints checklist identifying hard deadlines and gating risks to enforce during planning.
• Publish the prioritized study list with rationale and deliverable summary for each study.
• Collect and share the queue metadata and regulatory deadlines that informed prioritization.
• Flag any studies requiring immediate escalation due to imminent RTO deadlines.
• Confirm study scope and required model types
• A completed model and data inventory record listing files, versions, locations, and owners for the study.
• A prioritized gap list with estimated effort and acceptance criteria for model validation.
• A confirmed secure transfer method and timeline for any missing artifacts.
• Publish the model inventory record and gap list for the study.
• Provide access credentials or initiate the secure transfer for listed model files by the agreed deadline.
• Schedule model validation tasks for each identified gap with estimated completion dates.
• Review proposed technical assumptions per study
• A signed list of validated technical assumptions and scenario definitions for each study.
• A finalized set of quantitative acceptance criteria and required artifact formats for deliverables.
• A documented list of disputed assumptions with required evidence and resolution deadlines.
• Publish the validated assumptions document and acceptance criteria for each study.
• Provide the evidence or data items required to resolve disputed assumptions by the agreed dates.
• Present candidate study inventory
• Confirm milestone definitions and acceptance gates
• Assemble the RTO submission package template
• Validate or revise contingency and scenario lists
• Walk the existing model artifact register
• Agree senior-engineer review cadence and availability window
• Define quantitative acceptance criteria
• Define the sign-off workflow and timing
• Prioritize studies using agreed criteria
• Identify gaps and validation needs
• Define required deliverables per prioritized study
• Confirm post-acceptance support scope
• Record data ownership and transfer method
• Log disputed assumptions and evidence required
• Finalize turnaround times and contingency plan

• Update Network Model to Study-Ready State
• Execute Steady-State Power Flow Studies
• Run Contingency (N-1/N-2) Security Analyses
• Perform Short‑Circuit and Fault Current Studies
• Run Dynamic and Transient Stability Simulations
• Develop Detailed Renewable and Inverter Models
• Deliver Interconnection Impact Study Reports
• Provide Costed Mitigation and Funding Options
• Prepare NERC Compliance Documentation Package
• Participate in RTO/ISO Planning and Stakeholder Meetings
• Handover Study Models and Staff Technical Training
• Expedited Turnaround Block for High‑Priority Studies
• Protection Coordination and Relay Setting Updates
• Support Field Implementation and Commissioning Assistance

Update Network Model to Study-Ready State

• Provide the list of case files and one-line diagrams (SLD) you will supply (file names and formats, e.g., .raw, .sav, .xlsx).
• List the system snapshots (season, peak/light load, contingency cases) that must be prepared for studies. Options: Summer peak, Winter peak, Light load, Seasonal off-peak, Custom snapshot
• Do you have recent verified equipment nameplate and thermal ratings for transformers and lines (yes/no)? Options: Yes, No
• Which specific RTO/ISO study procedure section governs your network model requirements (cite section or upload reference)?
• Identify existing data gaps we should remediate (e.g., missing relay zone boundaries, incomplete breaker statuses, inaccurate bus coordinates).
• When should the study-ready model be delivered to our team relative to the study start date (days before start)? Options: 14 days, 7 days, 3 days, Same day

Execute Steady-State Power Flow Studies

• Describe the target steady-state outputs you need (e.g., node voltages, branch loading percent of rating, MW/Mvar injections) and file format for results.
• Specify the thermal rating basis we should use for branch limits (e.g., summer emergency rating C0/C1, seasonal nameplate, RTO posted rating). Options: Seasonal emergency ratings, Nameplate ratings, RTO posted ratings, Custom provided ratings
• Are there submitted interconnection queue IDs or generator IDs that must be included in the base-case injections? Options: Yes, No
• Indicate any locational transfer limits or posting constraints to enforce during power flow runs (MW thresholds, interface boundaries).
• Estimate the number of distinct scenario permutations (load levels x resource dispatch x outages) you expect us to run. Options: <10, 10-25, 26-50, >50
• Identify the solver convergence tolerances your acceptance requires (e.g., mismatch < 1e-3 pu, power mismatch < 0.5 MW).

Run Contingency (N-1/N-2) Security Analyses

• List the contingency categories to include (single line outages, bus faults leading to breaker trips, generator trips) and reference the RTO contingency list if applicable.
• Which N-1 and N-2 performance thresholds govern violations (e.g., overload >100% rating, voltage outside ±5%)?
• Do you require contingency screening by sensitivity (e.g., only study contingencies that produce >X% change at monitored buses)? Options: Yes, No
• Identify the monitored buses, interfaces, and equipment tags that must trigger automated reporting when limits are exceeded.
• When reporting contingency outcomes, which deliverable format do you prefer (summary dashboard, CSV contingency list, annotated SLDs)? Options: Dashboard, CSV, Annotated SLD (PDF), Full case files
• Are probabilistic or sensitivity studies required for N-2 rare-event screening (yes/no)? Options: Yes, No

Perform Short‑Circuit and Fault Current Studies

• Provide the fault types and locations to model (three-phase bolted, SLG, LLG, specified buses or substations).
• Which standard or threshold should we reference for short-circuit results (e.g., manufacturer trip limits, protective device interrupting rating)?
• Identify the equipment for which you need interrupting rating verification (transformers, breakers, switchgear) by tag or substation.
• Do you want steady-state fault current, peak asymmetrical current, and x/R ratio reported for each bus (select)? Options: Steady-state fault current, Peak asymmetrical current, x/R ratio, All of the above
• Estimate whether existing protection device databases (relay models and settings) are complete for fault duty assessment. Options: Complete, Partially complete, Missing
• Are arc flash calculation outputs required alongside short-circuit results (yes/no)? Options: Yes, No

Run Dynamic and Transient Stability Simulations

• Describe the dynamic scenarios to simulate (loss of large generator, loss of major tie-line, inverter tripping, fault-clearing delays).
• Which model fidelity do you require for synchronous machines and controls (detailed governor/exciter vs aggregated models)? Options: Detailed machine models, Aggregated equivalents, Mixed
• Identify required dynamic performance metrics (ROCOF, frequency nadir, damping ratios, voltage recovery time) and pass/fail thresholds.
• Do you require time-domain replay files and plots for each run (select output types)? Options: Time-series plots (CSV), Replay case files, Animated plot PDF
• Are hardware-in-the-loop or controller model-in-the-loop interactions needed for inverter behavior validation (yes/no)? Options: Yes, No
• When performing stability runs, which simulation time step and total run time do you prefer (e.g., 10 ms step for 20 s)?

Develop Detailed Renewable and Inverter Models

• Specify the inverter-based resource types and control modes to model (PV plant with low-voltage ride-through, battery with synthetic inertia).
• Provide the manufacturer model files or parameters you can supply for site inverters, turbines, and plant controllers (file names/formats).
• Are IEEE 1547 response modes and setpoints (ride-through curves, reactive capability) mandated for these resources? Options: Yes, No, Partial / site-specific
• Identify the plant-level aggregation approach you prefer for large fleets (detailed per-unit vs aggregated single-machine equivalent). Options: Per-unit detailed, Aggregated equivalent, Hybrid
• Do you require hardware/firmware version tracking for deployed inverters as part of the model (yes/no)? Options: Yes, No
• Explain any site commissioning constraints that affect model parameter validation (limited access windows, restricted data telemetry).

Deliver Interconnection Impact Study Reports

• List the mandatory sections your RTO or internal review requires in the interconnection report (executive summary, thermal/voltage analysis, mitigation list).
• Which file formats and templates are required for report submission to your RTO (PDF, Excel contingency tables, annotated SLDs)? Options: PDF, Excel, Annotated SLD (PDF), Case files
• Identify the review cycle expectations (number of internal review rounds, turnaround days per round) for draft and final reports. Options: 1 round (standard), 2 rounds, 3+ rounds
• Specify any regulatory artifacts that must accompany the report (traceability matrix to RTO study procedure sections, queue application cross-reference).
• How will you accept the interconnection impact study deliverable (signed acceptance checklist, RTO submission-ready package, or formal meeting sign-off)? Options: Signed acceptance checklist against deliverable template, RTO submission-ready package confirmed, Formal acceptance via review meeting minutes
• Are there external reviewers (e.g., developer technical reps) who must be included in the report review loop (yes/no)? Options: Yes, No

Provide Costed Mitigation and Funding Options

• Describe the level of cost estimate accuracy you require for mitigation options (order of magnitude, budgetary ±30%, detailed estimate). Options: Order of magnitude, Budgetary ±30%, Detailed estimate
• Identify the mitigation categories to cost (network upgrades, reactive compensation, generation redispatch agreements, protection device replacements). Options: Network upgrades, Reactive compensation, Generation redispatch, Protection device replacements, Other
• Do you require alternatives for funding models (customer-funded upgrades, system-funded, cost-sharing scenarios)? Options: Customer-funded, System-funded, Cost-sharing, Need recommendation
• Specify any capital approval thresholds or cost caps that constrain mitigation options (e.g., projects >$1M require board approval).
• Are construction schedule estimates and permitting risk notes required alongside cost estimates (yes/no)? Options: Yes, No
• Estimate whether site-specific geotechnical or right-of-way studies will be needed to validate cost assumptions. Options: Not required, Likely required, Required

Prepare NERC Compliance Documentation Package

• List the specific NERC standards and clauses this documentation must address (e.g., PRC, FAC, TPL clauses and clause numbers).
• Which evidentiary artifacts do you require in the package (model cases, run logs, signed checklists, RTO correspondence mapping)? Options: Model case files, Run logs, Signed checklists, RTO correspondence, Other
• Identify the audit timeline we must satisfy (date of next NERC audit or internal compliance review).
• Do you require a compliance traceability matrix mapping each study result to specific NERC requirement language? Options: Yes, No
• How will you accept the compliance documentation package (signed evidence checklist and traceability matrix acceptable for audit)? Options: Signed evidence checklist and traceability matrix, Formal acceptance meeting minutes, Upload to compliance repository confirmed
• Are there internal compliance reviewers or external consultants who must review the package before finalization? Options: Internal reviewers only, External reviewers included, No external reviewers

Participate in RTO/ISO Planning and Stakeholder Meetings

• Which RTO/ISO meeting types should we attend on your behalf (planning working group, stakeholder forum, queue meetings)? Options: Planning working group, Stakeholder forum, Queue meeting, Other
• Provide the expected frequency and timing of meetings we must support (weekly, biweekly, monthly and typical time windows). Options: Weekly, Biweekly, Monthly, Ad hoc
• Identify the level of representation required at each meeting (senior engineer presentation, technical note author, Q&A support). Options: Senior engineer presentation, Technical note author, Q&A support, Observer
• Are pre-meeting deliverables required (slide decks, summary memos) and in what lead time before the meeting? Options: Yes, 5 business days, Yes, 2 business days, No pre-meeting deliverables
• Do you require meeting minutes and action-item tracking uploaded to your shared repository after each meeting (yes/no)? Options: Yes, No
• Identify any confidentiality or data-sharing constraints that limit our speaking points at public stakeholder sessions.

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Confidentiality & Data Access Agreement
• Pricing Annex & Order Form
• Resource Assignment Addendum
• Acceptance Criteria & Sign-off Checklist
• Model Ownership & Transfer Agreement
• Change Order Agreement
• Invoicing & Payment Terms
• Data Processing Agreement (DPA)
• NERC Compliance Addendum (conditional)

• Go-live health check
• First measurement review
• Compliance evidence and audit channel review
• Knowledge transfer and staff enablement review
• Quarterly sustain and enhancement review

• Complete remaining runbooks and publish them in the agreed repository with version control.
• Update and publish the audit evidence retention and access policy documentation.
• Schedule monthly evidence-sync checkpoints until completeness targets are met.
• Documentation and runbook completeness review
• Achieve the target percentage of deliverables with completed transfer documentation as recorded in Engagement Scope.
• Internal staff proficiency meets the agreed assessment threshold, or a remediation plan is in place.
• A final documentation handover checklist and storage location are confirmed.
• Reconfirm agreed deliverables and owners
• Schedule additional hands-on shadow sessions for staff who did not meet proficiency targets.
• Run a reassessment of staff proficiency after remediation is complete and report results.
• Quarterly metrics review
• Maintain or improve the RTO study deadline compliance rate toward Mutual Commit targets.
• Reduce average turnaround time per study quarter over quarter, or document a corrective plan.
• Agree a prioritized enhancement backlog and owners for next quarter.
• Owner to close or advance the top five backlog items before the next quarterly review.
• Publish prioritized enhancement backlog with acceptance criteria and estimated effort.
• Refresh any audit evidence items older than six months and confirm via the evidence channel.
• All delivered artifacts and their owners are confirmed and accessible.
• Critical operational blockers are identified and assigned remediation actions with dates.
• Audit evidence channel and access controls are validated for initial usage.
• Publish an access matrix listing model files, evidence repository locations, and named data owners.
• Resolve any critical blockers preventing model runs or evidence uploads within the agreed short-term remediation window.
• Schedule the first knowledge-transfer workshop for internal staff within two weeks.
• Confirm metric reporting sources and next review date.
• Assign corrective actions with owners and firm completion dates to address identified gaps.
• Determine whether backlog count and average turnaround time are trending toward Mutual Commit targets and document any shortfalls.
• Present first-period metrics vs Mutual Commit targets
• Deliver a root-cause findings memo with recommended fixes and an updated timeline to return to Mutual Commit targets.
• Implement the top-priority remediation tasks and report status in weekly updates until the next measurement review.
• Publish the metric feed definition and owner for automated reporting.
• Audit evidence repository completeness check
• Achieve a documented path to reach the audit evidence completeness rate required by Engagement Scope.
• All open compliance issues have named owners and agreed resolution dates.
• The audit evidence channel and retention policy are confirmed and accessible to auditors on request.
• Populate missing audit artifacts in the evidence repository and mark completion status.
• Validate access and evidence channels
• Backlog burn-down and high-severity issues
• Open compliance issues review
• Review staff proficiency assessment results
• Root-cause diagnosis for any variance
• Plan targeted enablement to close gaps
• Enhancement requests and prioritization
• Agree corrective actions and recovery timeline
• Confirm the shared audit channel and retention policy
• Early operational signals and ingestion checks
• Assign owners and remediation schedule for open items
• Finalize documentation handover checklist
• Audit readiness and documentation freshness
• Confirm measurement cadence and data sources
• Blockers and open issues triage
• Agree immediate remediation actions