Hi J***h, I’m J***e with E***t S***s. I came across your background leading microgrid and distributed energy projects at B***t P***r and E***d P***r,and I was impressed by how you’ve driven strategy, partnerships, and growth in that space. We’re currently looking for a Director of Microgrid Strategy and Development to shape our next phase of microgrid deployments. Would you be open to a quick chat to learn more about the role and see if it aligns with your career goals? Best regards, J***e HR Recruiter, E***t S***s

Hi J***h , great to hear you’re interested. I’m available for a 20-30 minute call this week on: • Tuesday, May 7th at 2:00 pm ET • Wednesday, May 8th at 10:00 am ET Let me know if one of those works for you or feel free to suggest another time. On the call, I’ll walk you through our Director of Microgrid Strategy and Development role,responsibilities, team structure, growth plans at E***t,and answer any questions you have. Looking forward to speaking! J***e

Hi J***h, Great,Wednesday, May 8th at 10:00 am ET is confirmed. I appreciate you flagging the alignment challenges at E***d P***r; that’s exactly one of the key issues this role is designed to solve. About the Director of Microgrid Strategy and Development at E***t: 1. Cross-Functional Alignment • You’ll lead our PMO-driven governance process, running regular design-to-deployment workshops that bring engineering, commercial, operations and permitting teams into sync. • We use a centralized project dashboard and clear RACI models to ensure every stakeholder,from site engineers to our utility partners,knows deliverables and timelines. 2. Strategic Partnerships & Scale • You’ll own relationships with technology vendors, EPC contractors, regulators and utilities to accelerate approvals and drive innovation. • By co-creating roadmaps with these partners, we’re able to pivot quickly on late-stage design changes and scale deployments more efficiently. 3. Market & Growth Focus • You’ll analyze emerging market trends and policy shifts to identify new service lines and cost-optimization opportunities across commercial, industrial and community microgrids. • This role reports directly to the COO and offers clear advancement into VP-level leadership as we expand nationally. 4. Team Leadership & Development • You’ll mentor and coach a growing team of project managers and engineers, embedding a high-performance, continuous-learning culture. • E***t invests in training stipends, certification programs and a collaborative “Tech Council” so you can upskill your team. 5. Compensation & Resources • We offer a competitive base salary, performance-based bonus and equity package. • You’ll have full access to our in-house project management tools, strategic marketing support and a dedicated finance liaison to ensure your initiatives hit revenue targets. Does this overview address your questions so far? Happy to dive deeper on any point when we speak. Looking forward to our conversation on Wednesday! Best, J***e HR Recruiter, E***t S***s

Hi J***h, Great questions,here’s a bit more color ahead of our call: 1. PMO Toolset • We run a cloud-based PMO backbone built on Microsoft Project Online integrated with Power BI for real-time dashboards. • Smartsheet handles live schedule and resource tracking, and we use Confluence for centralized documentation and version control. 2. Team Size • Our Microgrid Strategy & Development organization is currently about 10,12 professionals: a mix of project managers, design engineers, interconnection specialists and permitting experts. We’re set to grow further as we ramp new programs. 3. Toughest Cross-Functional Hurdle • Recently, the biggest challenge has been managing late-stage design changes when utility interconnection requirements shift mid-stream. Balancing engineering tweaks, vendor lead times and permit timelines forced us to stand up an accelerated change-control process,with daily stand-ups and an updated RACI,to get everyone back in sync. Happy to dive deeper on Wednesday at 10 am ET. If there’s anything else you’d like ahead of time, just let me know. Looking forward to our conversation! Best, J***e HR Recruiter, E***t S***s

Hi J***h, Great questions,here’s how we handle the integration and the top KPIs we watch: 1. Project Online ↔ Smartsheet Sync • We leverage Microsoft Power Automate (Flow) to push updates from Project Online into Smartsheet sheets in near real-time. Key fields (task names, start/finish dates, resource assignments, % complete) are mapped one-to-one so our PMO dashboard always reflects the latest schedule and capacity data. • On the Smartsheet side we use the Data Shuttle tool (API) to send any resource-level changes or risk flags back into Project Online, ensuring alignment across planning and execution views. 2. Power BI KPIs for Risk Flags • Schedule Performance Index (SPI): warns us when actual progress is slipping against the baseline plan (SPI < 0.95 triggers an alert). • Cost Performance Index (CPI): flags budget overruns early (CPI < 0.9). • Schedule Variance (SV) & Cost Variance (CV): displayed as traffic-light charts so you can instantly see which workstreams are behind or over budget. • Percent Complete vs. Forecast: highlights tasks trending over their planned duration or spend. • Milestone Adherence: monitors key gateway dates,any slippage feeds into our daily stand-up agenda. We’ll walk through a live demo of these integrations and dashboards in our call on Wednesday. Let me know if you’d like any deeper dive on a specific KPI or workflow beforehand. Looking forward to it, J***e

Hi J***h, Great question,here’s a deeper look at how we manage custom mappings and reconciliation in our Power Automate,driven sync, plus our alerting and logging approach: 1. Custom Field Mapping • We maintain a “Field Map” in a SharePoint list that links each Project Online custom field (by internal name) to the corresponding Smartsheet column ID. • At runtime, the flow retrieves that mapping table and dynamically builds the JSON payload so any new or renamed fields are picked up automatically. • For complex types (e.g. choice fields or resource lookups), we use expression functions within the flow to normalize values (e.g. splitting semicolon-delimited strings) before pushing into Smartsheet. 2. Error Reconciliation • Each sync step is wrapped in a “Configure run after” pattern: on failure or timeout, we capture the record’s unique ID, the attempted payload, and the API error message. • That data is written to a SharePoint-backed “Sync Audit Log” list, including timestamps and error categories (mapping mismatch, rate limit, schema change, etc.). • A nightly reconciliation job compares key hashes (task name + start date + % complete) across Project Online and Smartsheet. Any discrepancies generate a flag in the audit list for manual review or automated retry. 3. Automated Alerts & Audit Logs • On any critical error,mapping failure or reconciliation drift,the flow triggers: , An e-mail to the PMO distribution list with error details and a link to the audit record. , A message in our dedicated Teams channel, tagged to our operations lead for immediate attention. • All run histories are retained in Power Automate for 30 days by default; our audit list retains detailed logs for 12 months to support post-mortem and trending analysis. If you’d like to see the flow structure or walk through a real-time demo with our PMO lead, let me know,I’d be happy to set that up before our call. Best, J***e HR Recruiter, E***t S***s

Hi J***h, Great questions,here’s how we handle both performance tuning and schema governance at scale: 1. Flow Performance & Throttling • Batch & Parallelize: We group tasks into batches (usually 50,100 items) and leverage parallel branches in Power Automate with controlled concurrency (max 5,10 threads) to spread API calls evenly. • Adaptive Delay Policies: We dynamically insert small delays (200,500 ms) between batches when we detect 429 responses, then automatically retry with exponential back-off. • Off-Peak Scheduling: For very large rollouts, we split the sync into off-peak windows or overnight runs to keep within service limits. • Monitoring & Alerts: Built-in metrics in Flow let us track runtime, call volume and throttles. Any spike triggers an alert so we can adjust batch sizes or cadence in real time. 2. Field Map Versioning & Gating • Versioned Field Map: Our SharePoint “Field Map” list includes a version column. When we introduce schema changes, we create a new version entry and flag it as “staging” until approved. • Staging & Validation: New mappings are first deployed to a sandbox environment where a subset of tasks is synced. We run automated reconciliation jobs to verify no drift before promoting to “production.” • Approval Workflow: A simple Power Automate approval flow notifies the PMO lead and engineering stakeholders. Once they sign off on the new mapping version, the production sync picks it up. • Drift Detection: During each sync, we compare field hashes against the active version. Any unmapped or changed field fires an alert and pauses that batch until it’s reconciled. If you’d like to walk through our Flow configuration or see the versioning process in action, I’d be happy to loop in our PMO lead for a quick tech deep dive. Just let me know! Best, J***e HR Recruiter, E***t S***s