Leadership Profile
Summary
The ten leadership actions taken from the role description (Define, Assess, Align, Delegate, Oversee, Authorize, Mentor, Hire, Report, Evangelize) and the evidence behind each: weekly-report entries, deliverables, risks, sessions led, meeting hours and colleague reviews. Every other page in this report carries the same actions as chips.
Key insights
Ten actions describe how this work was led: Define, Assess, Align, Delegate, Oversee, Authorize, Mentor, Hire, Report, Evangelize.
They come from the role and responsibilities document (supervisory role). Every weekly entry, deliverable, risk, session and meeting in this report carries up to three of them. 263 of the 371 weekly entries show at least one action, 177 of them in my own contribution text. 794 of 921 meeting hours carry an action; the rest are learning, company events and untitled meetings. The tags describe the type of action, not how well it was performed.
The ten actions
choose one to see what stands behind itDefine
Sets the strategy, standards, frameworks and KPIs that other people execute against.
In the role description: Defines strategy and KPIs for the transformation programs, the software-quality approach, the capability-building framework and the inner-source vision.
| Weekly-report entries | 30 | 24 in my contribution text, 6 inferred from the entry Recorded |
| Deliverables | 114 | artefacts whose title or role shows this action |
| Risks handled | 11 | entries in the risk registers |
| Meeting hours | 42 | 32 meetings, from the calendar Recorded |
| Colleague reviews | 1 | of 16 written reviews describe this action |
| Viva Engage posts | 1 | of the 16 posts by me or featuring the work |
Against the goals and commitments
By body of work
Examples from the weekly reports
Requested a clear priority list and business liaison so delivery could begin. - Received confirmation that Sastry would act as liaison and that Manu would remain the primary budgeting contact. - Proposed a conservative resource…
I prepared and delivered 62304 Standard, why is it essential to you, and how to leverage AI to become compliant?, including presentation content, facilitator material, interactive exercises, standards resources, participant…
I had previously helped define the access participants and supported the onboarding path. During Week 21, the deployment issue was escalated, the environment setup was completed, and the business was asked to test it.
I delivered the session, provided a standards overview and AI compliance-verification technique, and distributed the presentation, recording, two AI requirements checker approaches, and a feedback form afterward.
Where each action shows up
Weekly entries by action, under the goals (G) and commitments (M) they support
Meeting time by action
Hours per month, each meeting counted once under its strongest action (*November to the 8th)
Executive Summary
Summary
A one-page account of the year: the figures that matter most (utilization, sessions with their NPS, Medallia, estimated time saved by AI defect-triage assistant, AI requirements checker at a business unit, the product quality review work), the actions behind the work, and what came of the main projects.
Key insights
Work delivered against the five 2026 goals and three commitments. 16 colleagues wrote full reviews of it, and 76 people left feedback in chats.
Widely used by-products: AI requirements checker, AI traceability platform, AI assessment tool. A deep-dive assessment: 2 months to 2 weeks.
AI requirements checker and AI assessment tool made automation its own product quality review activity, budgeted for 2027.
Sponsor and endorser: Steve, Chief Patient Quality & Safety Officer. His AI requirements checker post reached 29,102
Utilization: 1,775 billed of 1,879 worked hours; 1,959 h booked in 47 weeks
In their words
word for word, with the source; tinted tiles are leadership, plain tiles are colleagues and customers“Previously, reviewing software requirements was done manually. These are long documents that traditionally require multiple rounds of back and forth. Now a business unit and Innovation Engineering teams are using requirements-review programme, where Requirements and Software Quality engineers upload requirements and AI does the first heavy lift to inventory the requirements including checking them against INCOSE guidelines/IEC 62304 / FDA expectations and flagging gaps, ambiguities, and compliance risks. requirements-review programme completes this work in roughly half the time with more consistency and fewer surprises later. In other words, requirements-review programme is helping us shift left.”
“If you review requirements and want to see how requirements-review programme could work for you, please contact Datta () who can help you create prompts and try requirements-review programme in your application.”
“I liked it a lot. Are you including regulators in the development process?”
“His domain expertise and structured approach transformed ambiguity into an actionable, transparent roadmap.”
Ten leadership actions
entries and hours behind eachThe year
hours, entries, sessions, milestones and recognition on one axis- 123 Jan · AI traceability platform first release, 3 businesses
- 223 Feb · Impact Assessment live
- 38 Mar · Test-scenario generation live
- 415 Apr · AI traceability platform graduates from AI compliance platform
- 528 Apr · AI defect-triage assistant funded
- 626 May · AI defect-triage assistant kickoff
- 71 Oct · Impact Showcase
- 826 Oct · AI defect-triage assistant knowledge transfer
- 94 Nov · AI traceability platform live in a business unit
What came of it
AI traceability platform, in use
AI traceability and compliance evidence for software V&V
Time returned
Elapsed time before and after, in weeks
Taught
Learners per quarter, bars coloured by who the session was for
Strategic Goals Delivery
Summary
The five goals and three commitments for 2026, in the wording of the goal-setting document: the weekly-report entries behind each success measure, the results that came of them, and the leadership actions each goal shows. "Beyond the goals" lists the work that serves no single goal, including hiring.
Key insights
Where the 1,959 hours went
timesheet project codes to goalsEach band is one timesheet project code, drawn to the goal or commitment it serves. Band thickness is hours booked.
When each goal was active
impact entries per weekly report, by goalThe five goals
Deliver AI compliance platform milestone with stronger quality readiness
Deliver the committed 2026 AI compliance platform milestone on time for the agreed end-to-end workflow and release scope, while improving delivery readiness through AI-enabled traceability and stronger execution confidence.
AI traceability platform is deployed in five business contexts and scored an NPS of 10 from two customers. AI defect-triage assistant, an AI compliance platform Cohort 5 project still in delivery: by 19 November, its KPI dashboard recorded 2,946 successful events and 12,204 agent runs, and estimated 505 hours saved. On 18 November the Ultrasound customer gave AI defect-triage assistant an NPS of 10.
- AI traceability platform is now deployed in a business unit, a business unit, a business unit, SRC and a business unit. In a business unit the team deployed it with APIs integrated for AI features, and rolling it out to a business unit stakeholders as a pilot is the next step.
- On a business unit thread an AI upskilling programme colleague wrote “Fantastic, thank you for confirming! And great work.” and asked for the AI traceability platform impacts to be added to the AI upskilling programme impact tracker and signed off, and the engineering group leadership thanked everyone for the successful deployment.
- Two business customers each gave the AI compliance platform AI-powered V&V compliance work, which is AI traceability platform, an NPS of 10: the EI Image Informatics a business unit business on 29 May and a business unit on 2 June.
- The Golden Thread Traceability milestone was delivered in week 4, and the milestone review confirmed the project stayed on track for its other milestones.
- Questions raised in review made traceability-data gaps visible before incorrect mappings were built into the solution, and the ingestion process surfaced gaps in the business data that were being addressed.
- Before deployment, teams beyond the original delivery took steps with AI traceability platform: an AI orchestration programme chose traceability as its first use case, a business unit set up AI traceability platform in its own AWS account, Ultrasound R&D worked through a setup path for a separate evaluation, and the Dhruv project asked to use it to review a UTS document.
- Leaders asked for the work: one leader asked to share the AI traceability platform work with the VPC team, and I&D leadership-team members asked for the deck and for access.
- The Inside AI compliance platform Special Edition spotlighted AI-powered end-to-end traceability for software verification and validation; its author puts the audience at more than 400 attendees.
By 19 November, the KPI dashboard recorded 2,946 successful events and 12,204 agent runs, and estimated 505 hours saved (an undisclosed amount) Estimate.
The savings are the AI defect-triage assistant KPI dashboard's own gross estimate (19 Nov 2026); per-item minutes are not shown and the figure has not been checked against timesheets.
“Datta's leadership and coordination has had a significant positive impact on AI defect-triage assistant by helping keep the team aligned, informed, and focused on delivering meaningful outcomes.”
“When the AST team requested new feature additions, Datta strategically evaluated each request rather than reacting impulsively.”
“to get 1300 failed test records triaged in a matter of minutes, versus a matter of hours.”
Establish a reusable AI-agent delivery pattern for software teams
Create a reusable AI-agent pattern for the engineering group by applying it in one BU-facing greenfield project and using it to accelerate delivery of a production-ready increment, while enabling broader reuse across teams.
The defect-triage project was funded as a six-month engagement, and by 19 November its KPI dashboard recorded 2,946 successful events and 12,204 agent runs, and estimated 505 hours saved. On 18 November the Ultrasound customer gave it an NPS of 10.
- The Ultrasound defect-triage project moved from proposal to a funded, scoped six-month engagement in week 18, with business-owned requirements and milestone governance agreed.
- AI defect-triage assistant entered delivery in week 23. Milestone 1 was completed across three sprints and 26 working days, with architecture sign-off, an end-to-end proof of concept on real data, and clearance to proceed to Milestone 2.
- By 19 November, the AI defect-triage assistant KPI dashboard recorded 2,946 successful events (dashboard solution) and 12,204 runs of the AI-Triage Agent, and estimated 505 hours saved.
- On 19 November the I&D Chief of Staff replied to the forwarded NPS 10 for AI defect-triage assistant: “Great content for us to take along as a reference and perhaps feature next year.” She also asked the business stakeholders to share the news with other BU stakeholders.
- On 18 November an Ultrasound customer gave AI defect-triage assistant a Medallia NPS of 10, with 10 out of 10 on all four segment scores. His comment says: “They approached the project as true partners, and their contributions were instrumental in helping us successfully move AI defect-triage assistant forward.”
- Milestone 2.1 was completed in week 39, with Azure DevOps story-creation integration, wider accuracy evaluation, and AI accuracy-feedback tracking added.
- A project colleague reported that the combined tools triaged 1,300 failed test records in minutes instead of hours.
- I set up a reusable KPI and value-measurement framework covering triage volume, automation coverage, labor-hour reduction, defect-identification latency, cycle time and adoption.
- Another business group asked for an applicability review of the defect-triage capability.
- I taught 20 colleagues to build agents with GitHub Copilot, rated 9.3 out of 10.
Improve BU delivery capacity through AI upskilling programme
Enable one BU-facing project to deliver more scope with the same team capacity through the AI upskilling programme approach and AI-enabled ways of working.
AI upskilling programme activities scored NPS 10, 10 and 9, and participants rated 7 of 15 sessions 9 out of 10 or higher.
- I led 16 AI upskilling programme sessions between 26 March and 12 November, reaching 854 participants in the register.
- Participants rated 7 of the 15 AI upskilling programme sessions that have a feedback score 9 out of 10 or higher.
- AI upskilling programme activities I ran or set up scored an NPS of 10 from the North America Analytics community (an AI learning series that reached 267 employees at 9.44 out of 10 satisfaction, surveyed in Medallia), 10 from a business unit for the AI requirements checker deployment, and 9 from a business unit for AI skills at scale.
- a business unit AI upskilling programme activity received an NPS of 9, and the sponsor recognized my role in setting up the engagement with a business unit.
- The AI upskilling programme impact slide, which thanks me by name, reports 13 of 14 BUs engaged, 11 BUs adopting the Business Case AI Agent, and up to 50% shorter development cycle in one pilot. These are program-level figures.
- Participants of the AI upskilling programme session on building practical agents thanked me in the chat.
- The AI traceability platform impacts are being added to the AI upskilling programme impact tracker for sign-off (4 Nov).
Make delivery improvement decisions more evidence-based with DORA
Improve delivery decisions by making DORA-based insights visible and usable in team improvement discussions across selected software contexts.
SRC asked for a follow-up on the DORA wireframe, program nominations followed, and the DORA session was rated 9 out of 10.
- I created the DORA dashboard wireframe, described as a strong starting point (week 3), and shared it with SRC with team and program views and a proposed single the engineering group KPI (week 5).
- SRC asked for a follow-up discussion on the wireframe, to understand what installation would mean for its environment (week 5).
- Leadership asked which 2026 programs would set DORA improvement targets and track them to closure, and program nominations followed (weeks 8 and 9).
- I consolidated the DORA program information into a single workbook (week 11).
- A leader said they liked the wireframe. Another colleague built on the dashboard for their team, adding detail on software delivery and quality, and wrote that the summary for PMs and executives was one they loved.
- I demonstrated the wireframe repository to participants of the DORA sessions, and passed it to a colleague, who used the concept to enhance his own DORA dashboard.
- I taught DORA to 27 colleagues, rated 9.0 out of 10.
- My prior-context evidence on the existing repository and hosted implementation helped the Software Excellence team judge overlap and reuse, supporting a shared scalable direction rather than parallel implementations (weeks 39 and 40).
Reduce turnaround time for product quality review software assessments without compromising quality
Reduce turnaround time for software assessments in product quality review by improving how assessment evidence is gathered and processed, while maintaining assessment quality and reviewer confidence.
Expert validation stopped unreliable check results from being treated as validated, and Patient Safety and Quality leadership featured requirements-review programme to 29,101 colleagues.
- For the product quality review Design Checklist automation, I produced the standards-basis documents and an updated assessment report for internal testing and reran the solution (week 39); the feasibility package had explicit evidence, standards interpretations and decision logic. I am a named co-author of the feasibility report, completed and circulated for a decision (week 42).
- The updated tool output I supplied went through expert validation, which set out correction areas and prevented unreliable check results from being treated as validated conclusions (weeks 37 and 38).
- Across a business unit, Ultrasound VM13 and a business unit Allegro, SMEs and the project lead validated a reduction from about two months to two weeks for the deep-dive assessment and remediation, using AI requirements checker, AI traceability platform and AI assessment tool.
- Patient Safety and Quality leadership featured requirements-review programme in a post seen by 29,101 colleagues, and my own requirements-review programme testimonial post drew 10 comments.
- The PS&Q Regions AI community invited me to speak on AI validation, a colleague asked to keep the recording of my requirements session, and another colleague asked for my help with a requirements-review programme project.
Three commitments
how the work was doneBuild capability by enabling others
I will scale impact by mentoring others, enabling adoption through workshops and collaboration, and turning lessons learned into reusable methods and practices that help teams perform with greater confidence, consistency, and ownership.
- I led 33 training sessions for 1,144 participants in the register.
- Participants rated the sessions 8.60 out of 10 on average across 26 feedback forms with 297 written responses.
- Mentoring cohort participants thanked me and the other mentor at the kickoff, and a colleague called me a mentor.
- An IT colleague wrote that the prompt to summarize the week's activities, from the training I gave IT, was extremely useful and that they used it to create their 30-day report.
- My January post announcing AI-first learning was seen by 4,112 people.
Drive execution through evidence
I will create clarity through measurable outcomes, visible progress, and data-informed improvement loops, using the right metrics and feedback mechanisms to strengthen decision-making, increase accountability, and ensure commitments translate into practical results.
- I wrote 47 weekly impact reports, each recording the objective, my contribution, the outcome and the next step.
- I built measurement into the work: a KPI and value framework for AI defect-triage assistant, a consolidated DORA program workbook, and AI accuracy-feedback tracking for the triage tool.
- I kept the evidence trail for leaders: week-by-week records that tie each outcome to the emails that support it.
Use AI responsibly
I will use AI-enabled methods and tools responsibly to simplify engineering workflows, improve traceability and decision quality, and reduce avoidable manual effort, while keeping patient safety, quality, security, and integrity at the center of how solutions are designed and applied.
- Expert review stopped unreliable AI check results from being treated as validated, and the proof of concept was to reduce black-box risk without presenting it as production-ready.
- The traceability work exposed data gaps before they were embedded in the solution.
- My 2026 AI competency evidence puts me at Expert level (my own assessment). Foundation and Practitioner rest on the Gen AI Ninja White and Yellow Belt certifications; Expert rests on architecture, retrieval, deterministic-guardrail, evaluation and lifecycle work across AI defect-triage assistant, AI requirements checker, AI traceability platform and the Knowledge Layer.
Beyond the goals
42 entries and 184 hours that serve no single goalHiring insights
Interviews conducted in 2026 and what came of them. This work serves no single goal; it adds delivery capacity to several.
13.5 h: 10 on the calendar, 1 event from the weekly reports and 1 from the Outlook mailbox (90 minutes each), across 5 roles Recorded
One full-stack contributor (January) and one contract AI engineer (from week 35)
On feedback I gave: one AI Solution Architect no-hire, three software development engineer candidates discarded on feedback, one contract AI engineer declined on competency
I organised 6 check-ins, 3.0 h, 8 Jun to 10 Aug
Interviews by month
Calendar entries, weekly reports and mailbox combined
What came of the interviews
By role. Hire Individual judgments are not reproduced.
A recommendation from the evaluations led to an onboarding decision for added full-stack capacity, with a planned start of 27 January. By week 5 a newly onboarded full-stack contributor had a time-entry account on the AI compliance platform project, with time entry enabled from 2 February.
I completed the 4th-round and the 2nd-round interviews and sent written feedback through the recruiting thread. The recruiting team planned an in-person discussion for 22 April. The sources I could search record no final decision.
I joined the interview panel in March and interviewed in the first round on 1 April. In the panel's wrap-up the second interviewer reported a clear no-hire, which confirmed my earlier assessment and that of the other first-round interviewer.
· also from Outlook mailI asked for a 90-minute conversation with each candidate and interviewed in round 1 on 27 and 29 April. By 28 April three candidates had been discarded on my and the talent partner's feedback, and a new batch went to CV screening. Round 1 interviews continued into June.
· also from Outlook mailI wrote the role description, declined one candidate whose competency did not meet the need, and joined the panel for two AI-engineer positions. I interviewed a candidate on 29 July, and onboarding of a contract AI engineer began in week 35.
· also from Outlook mailAll interviews and hiring meetings
The calendar, the weekly reports and the Outlook mailbox combined: 12 interviews, 3 planning, resource and supplier meetings, and 6 hiring check-ins. The two interviews found outside the calendar are counted as 90-minute events.
| Date | Kind | Role | Round | Minutes | Found in | Detail |
|---|---|---|---|---|---|---|
| 14 Jan | Interview | Full-stack engineer (AI compliance platform capacity) | 30 | Calendar | ||
| 20 Jan | Interview | Senior DevOps / Staff Software Developer | 4 | 60 | Calendar | |
| 20 Jan | Interview | Full-stack engineer (AI compliance platform capacity) | 30 | Calendar | ||
| 11 Feb | Interview | Full-stack engineer (AI compliance platform capacity) | 60 | Calendar | ||
| 17 Feb | Interview | Full-stack engineer (AI compliance platform capacity) | 60 | Calendar | ||
| 17 Mar | Planning meeting | 25 | Calendar | Align on the AI Solution Architect interviews | ||
| 30 Mar | Interview | AI Solution Architect | 90 | Weekly report | AI Solution Architect interview scheduled for 30 March | |
| 1 Apr | Interview | AI Solution Architect | 1 | 60 | Calendar | |
| 15 Apr | Interview | Senior DevOps / Staff Software Developer | 2 | 60 | Calendar | |
| 27 Apr | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Calendar | |
| 29 Apr | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Calendar | |
| 8 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 11 Jun | Resource request | 90 | Calendar | Request for supplier resources | ||
| 16 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 18 Jun | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Mailbox | Round 1 interview invitation for the software development engineer role |
| 22 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 29 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 6 Jul | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 29 Jul | Interview | AI engineer (contract, Bangalore) | 90 | Calendar | ||
| 4 Aug | Supplier introduction | 30 | Calendar | Introduction with the supplier | ||
| 10 Aug | Hiring check-in | 30 | Calendar | Hiring check-in I organised |
The calendar, the weekly reports and the Outlook mailbox are combined into one list. Candidate names and individual judgments are not reproduced.
Anytime Feedback & Session Feedback
Summary
What other people said about the work: 16 written reviews from colleagues (Anytime Feedback), ratings and comments from 33 sessions led (Session Feedback), and unprompted messages in chats and posts.
Key insights
Everyone who gave Anytime Feedback
16 colleagues| # | From | Role | Site | Words |
|---|---|---|---|---|
| 1 | Pothula | Associate AI Engineer - I | Bangalore, India | 266 |
| 2 | Jegan | Senior Software Architect | Bangalore, India | 253 |
| 3 | Luke | Software Development Engineer | Bothell, US | 419 |
| 4 | Ravindra | Senior Architect Devops | Bangalore, India | 345 |
| 5 | Nok | Senior Systems Engineer | Eindhoven, Netherlands | 150 |
| 6 | Claudia | Business Intelligence Pod Lead | Nashville, US | 267 |
| 7 | Feras | Systems Test Architect | Bothell, US | 625 |
| 8 | Bas | Quality Program Manager | Amsterdam, Netherlands | 208 |
| 9 | Hemang | Associate AI Engineer II | Bangalore, India | 2,422 |
| 10 | A colleague | Test Automation Specialist | Bangalore, India | 323 |
| 11 | Vidya | Learning Product Portfolio Manager | Chennai, India | 247 |
| 12 | Cecilia | Innovation Engineering Bus Partner, I&S | US remote, US | 465 |
| 13 | Sundaresan | Software Excellence Program Leader | Bangalore, India | 306 |
| 14 | A colleague | Service Operations Manager | Mexico City, Mexico | 354 |
| 15 | Eby | Group Leader a business unit R&D SW Engineering | Plymouth, US | 240 |
| 16 | Vaishali | quality-review synchronisation Lead | Cambridge, US | 173 |
16 colleagues wrote full reviews
Anytime Feedback, 10 sites in 4 countriesEach review answers six questions about impact, execution, care, and what to keep or change. The grid shows which of seven themes each colleague's review touches.
What colleagues wrote
How colleagues describe getting work finished and keeping others on track.
“… he successfully drove multiple releases from Golden Thread Traceability to the final Semantic Search Chatbot capability.”
“… consistently following through on every commitment and setting a gold standard for accountability across the entire team.”
“Throughout AI defect-triage assistant, Datta regularly summarized key decisions, clarified ownership, and tracked action items to completion.”
“I do not remember any time we have missed a deadline.”
What colleagues asked me to change
12 of 16 gave a suggestionScale through other people
“… distributing some of these responsibilities to other team members could help develop future leaders, improve scalability, and further accelerate…”
“… the single biggest opportunity to increase his impact is to transition from directly managing operational clarity to empowering and delegating…”
Be more visible, claim the credit, push adoption
“Datta can take up more space, put himself more in the foreground, and be more instructive.”
“… maybe sometimes you can use your authority and influence to claim the credit that is rightfully due to you.”
Tailor the message
“… if you can tailor the messaging to match the expertise and interest levels of stakeholders or team members, it would be fantastic.”
Team practices
“… ensuring the team regularly leverages the board during daily stand-ups”
“… brief retrospectives after stakeholder demos”
Where to focus next
“Where a central team like the engineering group can add value is how do we create an AI Platform for Software Engineering activities that can come alongside our…”
“Datta should familiarize himself with risk management and QMS requirements to help him manage prioritization and escalation of issues identified…”
Awards and recognition
4 recognitions: 2 individual awards and 2 team awards; 1,500 Recognition points on the individual cardsImpact Makers: AI traceability platform team
“This reflects the real impact, speed, and cross-team collaboration you have demonstrated”
| Given by | the engineering group Global Town Hall (announced to the team by a colleague, SVP, Innovation & Design) |
| Received by | The AI traceability platform team, including me |
| Reason | Impact, speed and cross-team collaboration on AI traceability platform |
| Points | Team-award points of 1,000 per member were requested on 13 Jul 2026 as per policy; the records do not confirm they were granted |
| Date | 30 Jun 2026. Date of the congratulations email and of the Viva Engage post by Chad, SVP, Innovation & Design, which says the teams were recognized at "today's the engineering group Connect". The email calls the event the the engineering group Global Town Hall. |
The 16 Jul card for 1,000 points came three days after the points request, and the request asked a colleague among others to award 1,000 points. The card cites the AI traceability platform programme and the the engineering group Connect meeting of Q2 2026 and does not mention the Town Hall, so I have kept the two as separate entries and counted the points only once, on the card. The slide, shown at 48:51 of the 30 Jun recording, names me in the the engineering group group of five and lists four non-IEN colleagues. The post by a colleague, SVP, Innovation & Design, says 6 teams were recognized. The remarks in the recording are about the whole AI traceability platform team, not about me alone.
Recognition award: Learning & Collaboration
“Congratulations on consciously applying AI and delivering the AI compliance platform funded AI traceability platform program as per commitment to the BUs and hence being recognized in the the engineering group Connect meeting of Q2 2026”
| Given by | a colleague |
| Received by | Me |
| Reason | Applying AI and delivering the AI compliance platform-funded AI traceability platform programme as committed to the BUs |
| Points | 1,000 Recognition points · Awarded (card and email) |
| Date | 16 Jul 2026. Date of the Recognition@Philips email. |
Recognition award: Execution & Performance
“Thank you so much for your hard work and dedication! Your commitment and drive are key to the engineering group's success. Sincerely, a colleague and the the engineering group LT”
| Given by | a colleague, SVP, Innovation & Design, with the the engineering group leadership team |
| Received by | Me |
| Reason | Hard work, dedication, commitment and drive |
| Points | 500 Recognition points · Awarded (card and email) |
| Date | 29 Jul 2026. Date of the Recognition@Philips email. |
Impact Makers: AI upskilling programme team
“Thank You for the impact you make.”
| Given by | the engineering group Connect, November 2026 (announced by a colleague, SVP, Innovation & Design) |
| Received by | The AI upskilling programme contributors, including me |
| Reason | Impact of AI upskilling programme across the business units |
| Points | No Recognition points are mentioned in the slide or the announcement |
| Date | 3 Nov 2026. Date of the the engineering group Connect announcement on Viva Engage by Chad, SVP, Innovation & Design, which embeds the recording still of the slide. |
This is the second Impact Makers recognition of the year, after the AI traceability platform team in June. The slide lists 13 of 14 BUs engaged, 11 BUs on the Business Case AI Agent, up to 50% shorter development cycle and up to 70% projected efficiency gains. The slide names me among the contributors. The two screenshots were supplied by me; no email or points record exists for this one. The remarks in the recording are about the whole AI upskilling programme team, not about me alone.
33 sessions, 266 ratings
satisfaction by session across the year; 26 of the 33 sessions have a rating formRating mix, session by session
Share of ratings in each band.
What learners said
Written comments about what went well, coded to themes
Self-rated confidence, a business unit series
Average before and after each session, 1 to 10
Every session and what was taught
materials from the 2026 folders, session by session33 sessions: 32 led alone and 1 led jointly with two colleagues. 5 of the led sessions are not rows in the AI upskilling programme register: the 4 Feb DORA session and four talks, added at my instruction. Totals above count only the led sessions.
| Date | Session | My part | Participants | Score | Materials |
|---|---|---|---|---|---|
| 28 Jan 2026 | Coding with GitHub Copilot | Led | 15 | 7.50 | 3 · 6 slides |
| 4 Feb 2026 | Delivering Performance and Value through DORA | Led · not a register row | 9 | 8.90 | 3 · 13 slides |
| 11 Feb 2026 | Obliterate your technical debt using AI, fast! | Led | 6 | 8.67 | 2 · 6 slides |
| 18 Feb 2026 | AI driven Golden traceability & test case coverage | Led | 80 | 1 · 11 slides | |
| 4 Mar 2026 | Foundational AI awareness - Context engineering - make your AI prompts work for you! | Led | 21 | 8.60 | 6 · 13 slides |
| 11 Mar 2026 | 62304 Standard, why is it essential to you, and how to leverage AI to become compliant? | Led | 18 | 8.91 | 2 · 20 slides |
| 18 Mar 2026 | Mastering Office 365 CoPilot for efficiency and gains | Led | 16 | 9.17 | 1 · 30 slides |
| 26 Mar 2026 | North America Analytics community Call - AI Prompt and Context Engineering - Part 1 | Led | 82 | 8.87 | 1 · 22 slides |
| 20 Apr 2026 | Innovation Impact Week: From vague to verified, AI-powered requirements for faster compliance | Led · not a register row | 2 · 10 slides | ||
| 22 Apr 2026 | a business unit DORA dashboard demonstration | Led · not a register row | |||
| 23 Apr 2026 | Innovation Impact Week: Inside AI compliance platform, AI-powered end-to-end traceability for V&V | Led · not a register row | 1 · 20 slides | ||
| 14 May 2026 | Foundational AI awareness - Context engineering - make your AI prompts work for you! | Led | 10 | 9.33 | 6 · 13 slides |
| 21 May 2026 | 62304 Standard, why is it essential to you, and how to leverage AI to become compliant? | Led | 21 | 9.14 | 2 |
| 11 Jun 2026 | Mastering Office 365 CoPilot for efficiency and gains | Led | 10 | 9.33 | 1 · 30 slides |
| 25 Jun 2026 | IGT-AI Day: AI requirements checker, AI Harness and AI traceability platform (joint with two colleagues) | Led jointly | 95 | 3 · 6 slides | |
| 25 Jun 2026 | North America Analytics community Call : AI Prompt Engineering Part 2 / Using AI as a Thinking Partner | Led | 101 | 9.46 | 1 · 34 slides |
| 26 Jun 2026 | AI traceability platform presented to the PSQ community | Led · not a register row | 1 · 7 slides | ||
| 22 Jul 2026 | Coding with GitHub Copilot | Led | 39 | 9.10 | 3 · 6 slides |
| 5 Aug 2026 | Coding and developing agents with GitHub Copilot | Led | 20 | 9.30 | 1 · 5 slides |
| 12 Aug 2026 | Foundational AI awareness - Context engineering - make your AI prompts work for you! | Led | 27 | 8.71 | 6 · 13 slides |
| 18 Aug 2026 | IT Connect - NA Region (AI for IT) | Led | 56 | 10.00 | 1 |
| 20 Aug 2026 | Delivering performance and value through DORA | Led | 27 | 9.00 | 3 · 13 slides |
| 25 Aug 2026 | a business unit AI Augmented Software Engineering - GitHub CoPilot Refresh | Led | 50 | 8.15 | 1 |
| 27 Aug 2026 | a business unit AI Augmented Software Engineering - Testing | Led | 46 | 7.21 | 1 |
| 27 Aug 2026 | North America Analytics Community: AI Prompt Engineering - Part 3 | Led | 84 | 10.00 | 1 · 32 slides |
| 1 Sept 2026 | a business unit AI Augmented Software Engineering - Prompt & Context Engineering | Led | 45 | 8.17 | 2 |
| 3 Sept 2026 | a business unit AI Augmented Software Engineering - Tech debt reduction | Led | 41 | 8.00 | 1 |
| 9 Sept 2026 | 62304 Standard, why is it essential to you, and how to leverage AI to become compliant? | Led | 29 | 8.00 | 2 |
| 16 Sept 2026 | Mastering Office 365 CoPilot for efficiency and gains | Led | 28 | 8.38 | 1 · 30 slides |
| 5 Oct 2026 | Winning Tips with AI Expert (Microsoft Office 365 CoPilot Tips & Tricks) | Led | 32 | 10.00 | 1 · 17 slides |
| 7 Oct 2026 | Foundational AI awareness - Context engineering - make your AI prompts work for you! | Led | 15 | 8.73 | 6 · 13 slides |
| 4 Nov 2026 | 62304 Standard, why is it essential to you, and how to leverage AI to become compliant? | Led | 58 | 7.70 | 2 · 37 slides |
| 12 Nov 2026 | Mastering Office 365 CoPilot for efficiency and gains | Led | 63 | 8.42 | 1 · 30 slides |
The same session, run again
Foundational AI awareness: context engineering
4 runs, 73 participants
Mastering Office 365 Copilot
4 runs, 117 participants
IEC 62304 and AI
4 runs, 126 participants
GitHub Copilot, then agents
3 runs, 74 participants
North America Analytics Community call
3 runs, 267 participants
a business unit AI-augmented software engineering
4 runs, 182 participants
DORA
2 runs, 36 participants
In learners' words
“… loved it! i especially found the prompt to summarize the last week's activities, extremely useful. i used it to create my 30-day report for my boss.”
“… it was a very useful training and I'm very happy I joined!”
“Learn by doing was implemented and I am walking away from the session not just with definitions or buzz words but also able to create them”
“I have taken 5 AI trainings in the past 3 weeks. GREAT presenter easy to follow. Everyone should take this training with Dattatreya.”
“For me everything, Datta is amazing explaining really difficult things in a really easy way.”
“Great session. This covers almost all 17 hours of training for white belt and a few aspects of yellow belt training as well”
6 Medallia responses
survey scores from customers of my work, 1 to 10Recorded
“The collaboration and communication with Datta and Sundaresan was very good. Several feedbacks that I gave, which were originally not part of the…”
“Extendable framework which can be customizable as per Project needs.”
“Hands-on, relevant, workshop type with good real time activities instead of just lectures. The use of AI tools for learning 62304 was also great.”
“Datta Vellal has been a great partner with the North American Analytics Community. This is a series that is hosted for 120-150 analyst throughout…”
“The output highly and positively impacted the project”
“Overall, we have been extremely satisfied with the the engineering group team's support on AI defect-triage assistant. They demonstrated an excellent understanding of our needs,…”
Everyone else
chats, messages and postsMessages and chats
38 screenshots from 76 people, by what the message was
Viva Engage
10 posts, 34,819 views. Blue: my posts. Pink: posts by others featuring the work.
Viva Engage, full record
every post and comment from the all-activity page, 2026seen 6,128 times Recorded
seen 29,635 times; not added to my own posts' figure
My posts
The "screenshot record" button opens the earlier transcription of the same post; a post shared to several communities is one row
| Date | Post | Actions and projects | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 7 Jan 2026 | Ending 2025 on a great learning note! | the engineering group Software Engineering… | 260 | 13 | 3 | |
| 7 Jan 2026 | A great ending to 2025, reinforcing our the engineering group's efforts towards enabling businesses to find meaningful... | I&D Innovation Engineering (the engineering group) | 135 | 3 | ||
| 7 Jan 2026 | Q1 2026 the engineering group Enabled AI-First Learning, in collaboration with Philips University | the engineering group Software Engineering… | 4,112 | 18 | 5 | |
| 7 Jan 2026 | the engineering group enabled, AI-First learning sessions for Q1 2026, in collaboration with Philips University, have been... | I&D Innovation Engineering (the engineering group) | 140 | 4 | ||
| 24 Mar 2026 | 🤖 AI On-Demand: Accelerating Requirements Compliance with the requirements-review programme' Predefined Prompt 🤖 | Patient Safety and Quality team | 341 | 16 | 12 | |
| 24 Mar 2026 | Writing requirements shouldn’t be a struggle. | I&D Innovation Engineering (the engineering group) | 127 | |||
| 29 Mar 2026 | Why does AI work brilliantly in some cases but fall flat in others? | I&D Innovation Engineering (the engineering group) | 141 | 4 | ||
| 1 May 2026 | Best answer QUESTION Any suggestions on how to get past this? I am getting API error! I am using the NAM… | Claude Community | 171 | 2 | ||
| 26 Jun 2026 | Use AI to think first, then get the work done and see how fast you become! | I&D Innovation Engineering (the engineering group) | 173 | 6 | ||
| 26 Jun 2026 | Subramanya Vellal, Dattatreya on Viva Engage: Use AI to think first, then get the work done and see how... | AI Uncovered | 223 | 3 | ||
| 6 Aug 2026 | Couple of hours, lot of curiosity and plenty of hands-on learning - AI skills & agents | I&D Innovation Engineering (the engineering group) | 177 | 16 | 1 | |
| 19 Aug 2026 | In the series of leveraging AI as a thinking partner, here's a short session I presented to the North… | I&D Innovation Engineering (the engineering group) | 128 | 6 | 1 |
Posts by others that feature the work
| Date | Post | Actions and projects | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 13 Jan 2026 | Kiran: Can some of us confirm if this is indeed an issue? | the engineering group Software Engineering… | 225 | 5 | ||
| 15 Apr 2026 | C: Applying AI to our work in Patient Safety and Quality is part of our overall effort to become more… | Patient Safety and Quality team | 29,102 | 80 | 16 | |
| 30 Apr 2026 | Tes: Inside AI compliance platform Special Edition: AI-Powered End-to-End Traceability! | I&D Research | 62 | 11 | 3 | |
| 18 May 2026 | Dasselaar,: Token limit not resetting? | Claude Community | 246 | 7 |
Posts by others where I commented
| Date | Post | Actions and projects | Community | Seen by | Reactions | Comments |
|---|---|---|---|---|---|---|
| 28 May 2026 | Madani: AI compliance platform Special Edition delivers AI-driven operational efficiency gains! | Innovation & Design | 457 | 25 | 7 | |
| 4 Jun 2026 | Bas: Explore requirements-review programme www.philips.com/kairos | requirements-review programme - Philips AI Platform | 333 | 11 | 3 | |
| 24 Aug 2026 | A colleague: The largest model is not always the safest engineering default. | the engineering group Software Engineering… | 218 | 17 | 4 | |
| 28 Aug 2026 | A colleague: In Opus Should Not Be Your Default, I made the case that model choice should be an engineering decision,... | the engineering group Software Engineering… | 408 | 8 | 2 |
Capacity & Time Investment
Summary
Where the working time went, in two parts. Part 1 is the timesheet: 1,959 booked hours by project code, by month and by day. Part 2 is the calendar: 921 hours of meetings, how the days were shaped, which leadership actions the meetings served, and the hiring interviews.
Key insights
Hours booked
Timesheet: all project work, by code, by month and by day
How the time was spent
1 Jan 2026 to 13 Nov 2026 · 221 days with entries1,959 h booked minus 80 h absence (10 days)
191 h beyond a standard day, in 221 days with entries
1,879 worked hours Estimate
Every day of the year
hours per day, Monday to Sunday by weekWhere the hours sit
project code, then activityMonth by month
Hours booked, by body of work
How long the days were
Days with worked hours, by length.
Effort against output
Each body of work's share of hours and of weekly-report entries
The actions behind the hours
leading leadership actions for each body of workHours are booked by project code, not by action. Each body of work is shown with the actions its weekly entries show most often. Meeting time by action is in Part 2 below.
What teaching cost in time
booked hours on the two training codesThese counts include only sessions booked under these two codes, so they are lower than the session totals elsewhere. The joint IGT-AI Day (95 participants) is booked under AI upskilling programme - Code Modernization, and the four talks outside the register have no training code.
Meeting time and hiring
Calendar: meetings only, by kind, by leadership action and by hour of day, with the hiring interviews
The calendar in numbers
1 Jan 2026 to 8 Nov 2026 · 208 working days4.4 h per working day, from 1,158 meetings Recorded
With overlapping meetings counted once. 90 days had 4 h or more, 30 had 6 h or more Recorded
398 h before 08:00, 520 h from 08:00 to 17:00, 3 h after 17:00 (US Eastern) Recorded
Meeting time by leadership action
each meeting counted once, under its strongest actionHours by action
From the meeting title and kind; 128 h in 152 meetings (learning, company events, untitled) carry no action Estimate
Month by month
Meeting hours per month, by action (*November to the 8th)
Every working day
busy hours in meetings per day, Monday to Sunday by weekBy kind of meeting
Hours by kind of meeting, grouped by words in the title Estimate
Month by month
Meeting hours per month, by kind (*November to the 8th)
When in the day
Meeting hours by weekday and hour
Where the meetings were set up
Hours by the time zone the meeting was created in
Largest recurring commitments
by hours in the year to dateHiring insights
interviews conducted in 2026 and what came of them13.5 h: 10 on the calendar, 1 event from the weekly reports and 1 from the Outlook mailbox (90 minutes each), across 5 roles Recorded
One full-stack contributor (January) and one contract AI engineer (from week 35)
On feedback I gave: one AI Solution Architect no-hire, three software development engineer candidates discarded on feedback, one contract AI engineer declined on competency
I organised 6 check-ins, 3.0 h, 8 Jun to 10 Aug
Interviews by month
Calendar entries, weekly reports and mailbox combined
What came of the interviews
By role. Hire Individual judgments are not reproduced.
A recommendation from the evaluations led to an onboarding decision for added full-stack capacity, with a planned start of 27 January. By week 5 a newly onboarded full-stack contributor had a time-entry account on the AI compliance platform project, with time entry enabled from 2 February.
I completed the 4th-round and the 2nd-round interviews and sent written feedback through the recruiting thread. The recruiting team planned an in-person discussion for 22 April. The sources I could search record no final decision.
I joined the interview panel in March and interviewed in the first round on 1 April. In the panel's wrap-up the second interviewer reported a clear no-hire, which confirmed my earlier assessment and that of the other first-round interviewer.
· also from Outlook mailI asked for a 90-minute conversation with each candidate and interviewed in round 1 on 27 and 29 April. By 28 April three candidates had been discarded on my and the talent partner's feedback, and a new batch went to CV screening. Round 1 interviews continued into June.
· also from Outlook mailI wrote the role description, declined one candidate whose competency did not meet the need, and joined the panel for two AI-engineer positions. I interviewed a candidate on 29 July, and onboarding of a contract AI engineer began in week 35.
· also from Outlook mailAll interviews and hiring meetings
The calendar, the weekly reports and the Outlook mailbox combined: 12 interviews, 3 planning, resource and supplier meetings, and 6 hiring check-ins. The two interviews found outside the calendar are counted as 90-minute events.
| Date | Kind | Role | Round | Minutes | Found in | Detail |
|---|---|---|---|---|---|---|
| 14 Jan | Interview | Full-stack engineer (AI compliance platform capacity) | 30 | Calendar | ||
| 20 Jan | Interview | Senior DevOps / Staff Software Developer | 4 | 60 | Calendar | |
| 20 Jan | Interview | Full-stack engineer (AI compliance platform capacity) | 30 | Calendar | ||
| 11 Feb | Interview | Full-stack engineer (AI compliance platform capacity) | 60 | Calendar | ||
| 17 Feb | Interview | Full-stack engineer (AI compliance platform capacity) | 60 | Calendar | ||
| 17 Mar | Planning meeting | 25 | Calendar | Align on the AI Solution Architect interviews | ||
| 30 Mar | Interview | AI Solution Architect | 90 | Weekly report | AI Solution Architect interview scheduled for 30 March | |
| 1 Apr | Interview | AI Solution Architect | 1 | 60 | Calendar | |
| 15 Apr | Interview | Senior DevOps / Staff Software Developer | 2 | 60 | Calendar | |
| 27 Apr | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Calendar | |
| 29 Apr | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Calendar | |
| 8 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 11 Jun | Resource request | 90 | Calendar | Request for supplier resources | ||
| 16 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 18 Jun | Interview | Software Development Engineer, Software Engineering Excellence | 1 | 90 | Mailbox | Round 1 interview invitation for the software development engineer role |
| 22 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 29 Jun | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 6 Jul | Hiring check-in | 30 | Calendar | Hiring check-in I organised | ||
| 29 Jul | Interview | AI engineer (contract, Bangalore) | 90 | Calendar | ||
| 4 Aug | Supplier introduction | 30 | Calendar | Introduction with the supplier | ||
| 10 Aug | Hiring check-in | 30 | Calendar | Hiring check-in I organised |
The calendar, the weekly reports and the Outlook mailbox are combined into one list. Candidate names and individual judgments are not reproduced.
Project Details
Summary
The 10 projects of the year: where each one stands, when it ran, the goals it serves and the leadership actions it shows.
Key insights
10 projects
where each one standsThe year, project by project
first to last dated eventEach project in numbers
Which goals each project serves
Project pages
choose a project to open its pageAI traceability platform
What it is
Release and submission readiness is slowed by fragmented DHF execution. Requirements, risks, tests and design evidence are disconnected, so traceability reconstruction, impact assessment and 510(k) submission evidence stay manual and prone to gaps.
Ingest and normalize DHF artifacts (requirements from ALMs, test cases and results, release documents), model the relationships in a graph database aligned to the V-model, visualize traceability, impact and requirements-to-test gaps, add AI for gap remediation and natural-language query, with human approval preserved.
AI traceability platform is an AI-powered V&V compliance platform that links design-history evidence in a graph database to give traceability, change-impact analysis and test-gap detection for medical device software.
How it unfolded
26 dated events- 2025-11AI compliance platform project spend starts: an undisclosed amount consumed during November and December 2025.
- 2025-12-12Feature alignment workshop (MVP) with the lead businesses a business unit, a business unit and EI-AV&I. First milestone marked complete.
- 2026-01-07AI traceability platform proposal for the the engineering group AI Accelerator co-authored, describing a queryable living knowledge graph.
- 2026-01-23Golden Thread Traceability milestone (first release); release notes with graph snapshots for three businesses sent 2026-01-27.
- 2026-02-23Milestone 2 report: Impact Assessment released and live; project status On-track.
- 2026-03-06AI traceability platform extension for a business unit test-case generation submitted to AI compliance platform Cohort 5, alongside an Ultrasound proposal.
- 2026-03-08First iteration of test-scenario gap detection and generation goes live (a business unit first).
- 2026-04-01Chatbot release notes and AI compliance platform Cohort 4 closure note: feature development complete. an AI orchestration programme pilot paused 2026-04-03.
18 more events
- 2026-04-08Cohort 4 closing slides prepared (submitted 2026-04-09) listing 90%+, 20% and 20% as expected impact.
- 2026-04-23Inside AI compliance platform graduation readout during Innovation Impact Week (opening virtual session 2026-04-20).
- 2026-05-15a business unit AI traceability platform deployment added to AI upskilling programme reporting; productivity gains to be shown as current state vs new state.
- 2026-05-29NPS of 10 reported from EI-II a business unit (a business unit followed on 2026-06-02).
- 2026-06-12AI traceability platform one-slider and live-data demo to the I&D leadership team (10-minute slot).
- 2026-06-30AI traceability platform team recognised as Impact Makers at the the engineering group Global Town Hall.
- 2026-07-21AI compliance platform leadership showcase Q&A: actual outcome data expected with business release cycles, go-live in December 2026.
- 2026-10-01AI traceability platform impact story presented at the first Innovation Engineering Impact Showcase; AI traceability platform-for-a business unit kickoff meeting held the same day.
- 2026-11-04AI traceability platform deployment in a business unit reported complete; next step is rollout to a business unit project and program stakeholders.
- Wk 6Workshop 2: the traceability tool demonstrated live in AWS; Impact Analysis previewed; businesses ask for orphan-node, filtering and reporting improvements.
- Wk 13Workshop 3: final capability demo and handover discussion; a business unit, a business unit and SRC report limits on immediate adoption. an AI orchestration programme pilot requested (2026-03-24); chat deployed 2026-03-26.
- Wk 14AI traceability platform - Living Knowledge Graph of Engineering Artifacts selected for AI Accelerator Round 2 funding.
- Wk 16a business unit: first ingestion into staging (URS, PRS, ERS, test cases; RMM and DFMEA excluded) and dedicated a business unit AWS account created.
- Wk 17Cohort 5 feedback: the a business unit test-generation extension was not advanced. Direct Windchill ingestion emerges as a proposal.
- Wk 18AI compliance platform AI-powered V&V project records moved to technical closure.
- Wk 21AI traceability platform setup in a business unit AWS account reported complete; Windchill integration meeting held.
- Wk 25AI Accelerator budget for AI traceability platform approved at an undisclosed amount; Windchill document retrieval redirected to staging tests.
- Wk 42Invention disclosure review on AI-assisted traceability, impact analysis and test-gap remediation; AI traceability platform named a valuation pilot for AI FinOps.
Figures
27 more figures
What happened
Golden Thread Traceability (the traceability tool)
Ingests release documents from the businesses and shows end-to-end links (need, requirement, design, risk, test, result) as a graph, upstream and downstream.Impact Assessment (impact analysis)
Shows which requirements, tests and other artifacts are affected when a requirement changes, with severity and a reason why each node appears.Test scenario gap detection and generation
Finds requirements without test coverage and uses generative AI to propose test scenarios. First iteration only; live for a business unit first, SRC and a business unit planned after data validation.2D/3D graph exploration, search, orphan-node view and export
Interactive 2D and 3D graph with node-type filtering, property search, orphaned-node detection and CSV/JSON export of traceability.Gremlin query support and Graph Builder
Advanced users can run Gremlin graph queries; the Graph Builder auto-constructs Gremlin queries.Semantic-search chatbot (natural-language query)
Users ask questions in natural language and get answers based on their ingested data. Described as the final feature planned under the AI compliance platform project; accuracy still being refined.Automated ingestion pipeline
Automated project creation and infrastructure provisioning plus ingestion and gap identification from business documents; completed for SRC, a business unit and a business unit.Self-hosted inner-source platform on AWS (Neptune graph)
Runs in business-managed AWS accounts on a Neptune graph database; inner sourced so any team can extend it.Developer Portal access (no GitHub credentials)
Live the traceability tool data on the internal developer portal so anyone in the organization can open it without GitHub credentials. Staging first; production migration still a next step in Wk 9.15 more
Windchill integration (direct read of DHF documents)
Retrieve controlled documents from Windchill instead of manual upload. Read APIs available and functional account in place; end-to-end flow was redirected to staging for testing.Windchill MCP access
Agent-oriented access to Windchill through MCP is the preferred long-term interface; read-only API is the nearer path and write use cases are not defined.AI traceability platform-native test-case generation engine for a business unit (BDD, RAG)
Proposed Cohort 5 extension to generate BDD test cases from URS/PRS/SRS and regenerate impacted tests. Did not advance in Cohort 5 selection.Q&R compliance checks (policy rulebook / compliance monitoring)
Executable checks of standards (IEC 62304, ISO 13485). A Cohort 5 proposal of about an undisclosed amount, not started in Wk 9, and a speaker-note vision.Living knowledge graph of engineering artifacts (AI Accelerator PoC)
Natural-language-queryable knowledge graph on top of existing ALM systems, funded as an the engineering group AI Accelerator proof of concept; conditional on a joint roadmap with Systems Engineering Excellence.Deployment: a business unit
Release documents ingested into a Neptune graph (4150 nodes, 3150 edges in the 27 Jan snapshot). At Workshop 3, a business unit said priorities and budget prevented immediate handover and asked whether the environment could be paused or archived.Deployment: SRC (a business unit)
1420 nodes and 2360 edges in the 27 Jan snapshot. At Workshop 3 SRC lacked the required a business unit AWS account and asked for cost; the reply was about an undisclosed amount per month for one business cluster. NPS of 10 reported 2 June 2026.Deployment: a business unit (EI-CI-AV&I / EI-II a business unit)
3927 nodes and 8800 edges in the 27 Jan snapshot. Test-scenario generation went live for a business unit first. At Workshop 3 a business unit cited limited capacity and said the project needed to pause for now. Cohort 5 test-generation extension did not advance.Deployment: a business unit
Not an original AI compliance platform sponsor. POC scope was IntraSight URS, PRS, ERS and test cases; first staging ingestion in Wk 16; app setup in a business unit AWS reported complete in Wk 21. Leadership Q&A cites a business unit with a December 2026 go-live.Deployment: a business unit
Next step is a pilot with a business unit stakeholders. Impacts to be added to the AI upskilling programme tracker.Deployment: an AI orchestration programme (pilot)
Requested as a no-cost POC after the the engineering group roadshow, starting with traceability on a release artifact set. Access to S3, Lambda, ECR and Neptune hit setup challenges and the teams were asked to pause on 3 April; later follow-up still showed access open.Deployment: Ultrasound R&D
An Ultrasound team with over 13,000 requirements asked about verifying only new, changed or impacted ones; Impact Assessment was positioned. A benefit-risk PoC was framed as an AI compliance platform extension. In Wk 32 a live demo and DOORS connectivity talk were offered.Deployment: MR
MR appears in the Software Excellence portfolio that includes AI traceability platform, and as a business identified for cross-learning follow-up calls in the AI defect-triage assistant tracker.Deployment: a business unit / product quality review
Demos and stated interest onlyDeployment: NPSS / IT validation
After the 23 April session NPSS asked about AI traceability platform fit for risk-based change management, impact assessment and validation strategy.In their words
“They guesstimated that it could reduce traceability efforts including validation from approximately 40 hours per release to around 10 hours-a substantial and tangible improvement that highlights the solution's real business impact.”
“You did that great AI compliance platform on traceability for projects in PDLM (project Sutro). We are building an agentic framework for VPC. Can I have Willem and Carl meet with you to share what we did so we can look at the PDLM integration of processes from customer need inception? I'd like them to see the Sutro work.”
“The team has successfully deployed the AI traceability platform for a business unit with api(s) integrated for AI features last week. We would like to extend our thanks to all who had assisted us in setting this up.”
“I liked it a lot. Are you including regulators in the development process?”
“This will be very useful for us in identifying impacted test cases. We do see a use of this in our project in automatically identifying the impacted test cases for a given requirement change”
“Impact Analysis flow will be useful for requirement updates in exploring areas and entity types affected and estimating overall efforts, and saving test cases runtime by detecting duplicate test steps.”
14 more
“This platform is remarkable! It will give us a clear data overview and quick access to evidence, estimating the overall effort of change and reducing test case runtime by detecting duplicated test steps.”
“This is fantastic! Great job. It will help improve quality of our documents and products. Especially like the Impact Assessment feature.”
“… this is a very nice initiative and i can already think of many future uses and potential value! good job!”
“This is impressive, what you are able to do with the documents.”
“AI traceability platform, the platform you envisioned as part of the AI compliance platform program, is a highly valuable solution for navigating our businesses' fragmented tooling landscape and enabling a more meaningful, intuitive way to interact with data.”
“You delivered AI traceability platform-this is no small thing. I am amazed and inspired.”
“Because those AI capabilities shipped on time, three business units adopted AI traceability platform in FY 2026, giving the platform its first enterprise-wide footprint and a clear revenue path.”
“I know it's taken significant hard good work to get here in so short time. Good to see we enabled the three BUs and we're also taking steps on how to scale and offer this on sustainable way through the Portal integration. Great progress again.”
“As part of the the engineering group Roadshow, we came across AI traceability platform- Traceability Platform and we would like to do a small POC\pilot with an AI orchestration programme service.”
“This is great to hear - thank you for the update and for partnering with a business unit on this!”
“Well done Subramanya Vellal, Dattatreya! Big change.”
“… great teamwork all around on this!”
“Spot on. Thanks for the last minute juggle.”
“One example was the AI traceability platform/AI compliance platform program, where he successfully drove multiple releases from Golden Thread Traceability to the final Semantic Search Chatbot capability.”
Where it stands
- Request to add AI traceability platform impacts to the AI upskilling programme impact tracker and have them signed off
Jetske, 2026-11-04 - AI traceability platform team recognised as 'Impact Makers' at the the engineering group Global Town Hall
Sundaresan (Program Leader, PMO, Software Engineering Excellence) announcing the town hall award, 2026-06-30 - Team award points requested for AI traceability platform team members (1000 points each per policy)
Sundaresan; policy confirmed by Senthil, 2026-07-13 - Leader asks for a doc or deck to share AI traceability platform with his staff
Peter, 2026-06-12 - AI Accelerator budget for AI traceability platform offered for release
Frank (as reported in the weekly report; condition: confirm proposal still current), 2026-06 (Wk 24) - AI traceability platform AI Accelerator proposal conditionally approved
Weekly report entry (approver not named in the entry), 2026-04 (Wk 14) - Inside AI compliance platform session spotlighting the AI traceability platform project, 400+ attendees
Tes (Viva Engage post, I&D Research), 2026-04-30 - AI traceability platform selected for the Innovation Impact Week opening virtual session
Innovation Impact Week announcement by Shez on Viva Engage (title as forwarded), 2026-03-26 - AI traceability platform platform deployment in a business unit included in AI upskilling programme reporting
Sundaresan, 2026-05-15 - Request for an AI traceability platform video for the engineering group marketing and communications
Jetske, 2026-08-30 - Inside AI compliance platform session created new adoption interest (NPSS and IT validation fit)
Manimaran (as reported in the weekly report), 2026-04 (Wk 17) - NPS for AI compliance platform AI Powered V&V Compliance (AI traceability platform)
10 from EI-Image Informatics - a business unit - NPS for AI compliance platform AI Powered V&V Compliance (AI traceability platform)
10 from a business unit
Training completed in 2026
learning records from the learning management system and the Cornerstone transcript187 learning records are dated 2026 in the learning history, on 34 different days between 6 Jan and 10 Nov 2026. They cover procedures, work instructions, guidelines, quizzes and courses of the quality system, product security and the design and release process. 60 of the records are dated 28 Oct. The first page of the Cornerstone transcript lists 13 completions in 2026.
Records per month
Learning records dated in each month of 2026
By subject
Each record sits under one subject, by its title (rules in tools/learning_rules.json)
| Subject | Records | Items | Quizzes |
|---|---|---|---|
| Design, development and release | 57 | 37 | 7 |
| Quality system, documentation and records | 35 | 24 | 0 |
| Complaints, CAPA and post-market | 25 | 17 | 2 |
| Product security | 23 | 16 | 8 |
| Field actions and correction and removal | 19 | 11 | 0 |
| Product safety and risk management | 18 | 15 | 1 |
| Tools and work instructions | 10 | 5 | 0 |
Cornerstone transcript, completed in 2026
First page of the transcript, newest first. Required means the transcript marks the row as required.
| Completed | Title | Type | Status | Required |
|---|---|---|---|---|
| 9 Nov 2026 | Protecting Patient Health Information under HIPAA - HEA109 | Online Class | Completed | |
| 27 Oct 2026 | Security Fundamentals 2026 | Online Class | Completed | |
| 6 Oct 2026 | Correction and Removal (C&R) Awareness (QMSE-E-CDI001955781_A) | Online Class | Completed | |
| 5 Oct 2026 | Medical Device Software Development following IEC62304 (Starts 10/2/2026) | Session | Completed | |
| 31 Jul 2026 | GEN_ALL EMPLOYEES (QMS0025-000057), requirement QMS0025-Innovation Engineering | Curriculum | Completed | Yes |
| 17 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices (GLOBAL-UL-ISO13485-00... title cut off on the page) | Online Class | Completed | |
| 17 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices (0000-UL-ISO13485_04.1) | Material | Completed | |
| 17 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices (0000-UL-ISO13485_04) | Online Class | Completed | |
| 7 May 2026 | Living Integrity - General Business Principles (GBP) 2026 | Online Class | Completed | |
| 6 May 2026 | Gen AI Ninja Yellow Belt Assessment for Technical Users | Test | Completed | |
| 1 May 2026 | Gen AI Ninja Yellow Belt Assessment for Business Users | Test | Completed Equivalent | |
| 1 May 2026 | Gen AI Ninja Yellow Belt Assessment for Business Users | Online Class | Completed | |
| 25 Feb 2026 | Site Inspection Response Team (SIRT) (Global-E-CDI001394027_D) | Online Class | Completed |
All 2026 completions are covered: the 25 rows supplied reach back to 2025-06-23. The 2026 Gen AI Ninja rows are the same assessments counted in the AI certification bar above.
Show all 187 learning records, newest first
| Date | Title | Code | Status | Subject |
|---|---|---|---|---|
| 10 Nov 2026 | Doc Ctrl n Record_CHANGE NOTICE CN CREATION RESOLUTION AND MAINTENANCE | 0048-2004002272-V3 | Passed | Design, development and release |
| 5 Nov 2026 | Design Input Procedure | 0056-2005000019-Rev 04 | Passed | Design, development and release |
| 5 Nov 2026 | Product Cybersecurity awareness session 2026 | 0056-CDI002602636-A.1 | Passed | Product security |
| 5 Nov 2026 | Quiz - Design Input | 0056-Q-2005000019 | Passed | Design, development and release |
| 28 Oct 2026 | 16.2.10 Manage Product Correction and Removal Procedure | QMS0200-4005000588_01 | Passed | Field actions and correction and removal |
| 28 Oct 2026 | 16.2.12.5 Perform Production and Post- Production Activities Work Instruction | QMS0200-4005000201_01 | Passed | Product safety and risk management |
| 28 Oct 2026 | 16.2.20 Manage Post Market Surveillance Procedure | QMS0200-4005000062_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | 16.2.23 Manage Customer Feedback Guideline | QMS0200-4005000248_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | 16.2.23 Manage Customer Feedback Procedure | QMS0200-4005000246_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | 16.2.23 Manage Customer Feedback Work Instruction | QMS0200-4005000247_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | 16.2.8.2 Investigate and Close Complaint Work Instruction | QMS0200-4005000654_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | AI Security Cookbook (Guideline) | QMS0200-4005000415_01 | Passed | Product security |
| 28 Oct 2026 | Assess and Initiate C&R Work Instruction | QMS0200-4005000636_01 | Passed | Field actions and correction and removal |
| 28 Oct 2026 | Cloud Design and Development Procedure | QMS0200-4005000325_01 | Passed | Design, development and release |
| 28 Oct 2026 | Complaint Handling Procedure | QMS0200-4005000589_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Creation and Localization of User and Service Documentation and Localisation of | QMS0200-4005000256_01 | Passed | Design, development and release |
| 28 Oct 2026 | Data Collection Work Instruction | QMS0200-4005000251_01 | Passed | Design, development and release |
| 28 Oct 2026 | Defect Management Procedure | QMS0200-2005001820_03 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Design and Development of SAMD Procedure | QMS0200-4005000252_01 | Passed | Design, development and release |
| 28 Oct 2026 | EI Design Review Work Instruction | QMS0200-4005000259_01 | Passed | Design, development and release |
| 28 Oct 2026 | EI Guidance - Data Elements for Accompanying Documents | QMS0200-4005000313_01 | Passed | Design, development and release |
| 28 Oct 2026 | EI Usability Engineering Work Instruction | QMS0200-4005000262_01 | Passed | Design, development and release |
| 28 Oct 2026 | FCO Procedure | QMS0200-4005000380_01 | Passed | Field actions and correction and removal |
| 28 Oct 2026 | FMEA Guideline | QMS0200-2005001260_02 | Passed | Product safety and risk management |
| 28 Oct 2026 | Good Documentation Practices Guideline | QMS0200-4005000051_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | IfU Regulatory Requirements Work Instruction | QMS0200-4005000116_01 | Passed | Design, development and release |
| 28 Oct 2026 | Incident Management Work Instruction | QMS0200-4005000397 _01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Information Retention Guideline | QMS0200-4005000052_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | ITSUI_Adobe Sign_Send and Sign Using Esignature | QMS0200-4005000057_01 | Passed | Tools and work instructions |
| 28 Oct 2026 | Label Design Guideline | QMS0200-4005000128_01 | Passed | Design, development and release |
| 28 Oct 2026 | Labeling Procedure | QMS0200-4005000112_01 | Passed | Design, development and release |
| 28 Oct 2026 | Leadership and Milestone Reviews Procedure | QMS0200-4005000254_01 | Passed | Design, development and release |
| 28 Oct 2026 | Manage Post Market Product Security Work Instruction | QMS0200-4005000398_01 | Passed | Product security |
| 28 Oct 2026 | Manage Pre-Market Product Security Work Instruction | QMS0200-4005000399_01 | Passed | Product security |
| 28 Oct 2026 | Non-Philips Product Patch Validation Work Instruction | QMS0200-4005000400 _01 | Passed | Product security |
| 28 Oct 2026 | Non-Product Records Control Work Instruction | QMS0200-4005000047_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Overview of Software Lifecycle Procedure | QMS0200-4005000255_01 | Passed | Design, development and release |
| 28 Oct 2026 | POL 06 - Security Incident Management Policy | QMS0200-POL-PE_006674-06 | Passed | Product security |
| 28 Oct 2026 | Product and Services Security Policy | QMS0200-POL-PE_006668-04 | Passed | Product security |
| 28 Oct 2026 | Product Records Control Work Instruction | QMS0200-4005000048_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Product Security Requirements and Risk Management Framework | QMS0200-POL-00005766-02 | Passed | Product security |
| 28 Oct 2026 | Production Controls Procedure | QMS0200-4005000580_01 | Passed | Design, development and release |
| 28 Oct 2026 | QMS Index List for QMS- 0200 | QMS0200-4005000002_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Quality Event Management Work Instruction (Next Gen) | QMS0200-4005000189_01 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Quality Manual for QMS- 0200 (Enterprise Informatics) | QMS0200-4005000001_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Quiz - 16.2.12.5 Perform Production and Post- Production Activities | QMS0200-Q-4005000201 | Passed | Product safety and risk management |
| 28 Oct 2026 | Quiz - 16.2.20 Manage Post Market Surveillance Procedure | QMS0200-Q-4005000062 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Quiz - Cloud Design and Development Procedure | QMS0200-Q-4005000325 | Passed | Design, development and release |
| 28 Oct 2026 | Quiz - Creation and Localization of User and Service Documentation and Localisat | QMS0200-Q-4005000256 | Passed | Design, development and release |
| 28 Oct 2026 | Quiz - Defect Management Procedure | QMS0200-Q-2005001820 | Passed | Complaints, CAPA and post-market |
| 28 Oct 2026 | Quiz - Design and Development of SAMD Procedure | QMS0200-Q-4005000252 | Passed | Design, development and release |
| 28 Oct 2026 | Quiz - EI Usability Engineering Work Instruction | QMS0200-Q-4005000262 | Passed | Design, development and release |
| 28 Oct 2026 | Quiz - Leadership and Milestone Reviews Procedure | QMS0200-Q-4005000254 | Passed | Design, development and release |
| 28 Oct 2026 | Quiz - Manage Post Market Product Security Work Instruction | QMS0200-Q-4005000398 | Passed | Product security |
| 28 Oct 2026 | Quiz - Manage Pre-Market Product Security Work Instruction | QMS0200-Q-4005000399 | Passed | Product security |
| 28 Oct 2026 | Quiz - Manage Pre-Market Product Security Work Instruction | QMS0200-Q-4005000399 | Passed | Product security |
| 28 Oct 2026 | Quiz - Manage Pre-Market Product Security Work Instruction | QMS0200-Q-4005000399 | Passed | Product security |
| 28 Oct 2026 | Quiz - Manage Pre-Market Product Security Work Instruction | QMS0200-Q-4005000399 | Passed | Product security |
| 28 Oct 2026 | Records Control Procedure | QMS0200-4005000046_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Regulatory Sustainability Product Requirements Guideline (SUS-020) | QMS0200-2006000475_04 | Passed | Design, development and release |
| 28 Oct 2026 | Software Bill of Materials Guideline | QMS0200-4005000417_01 | Passed | Product security |
| 28 Oct 2026 | Training Program Procedure | QMS0200-4005000109_01 | Passed | Quality system, documentation and records |
| 28 Oct 2026 | Validation of Software Tools Procedure | QMS0200-4005000419_01 | Passed | Design, development and release |
| 28 Oct 2026 | Validation of Software Tools Procedure | QMS0200-4005000419-01 | Equivalent credit | Design, development and release |
| 7 Oct 2026 | Correction and Removal (C&R) Awareness | QMSE-E-CDI001955781_A | Passed | Field actions and correction and removal |
| 7 Oct 2026 | Employee Training Work Instructions Update (A- Q2920-00127 Rev. AR) -Test | 0024-Q-A-Q2920-00127_AR | Passed | Quality system, documentation and records |
| 7 Oct 2026 | Quality Manual for QMSID QMS-0024 | 0024-RU-A-Q2920-00053_CU | Passed | Quality system, documentation and records |
| 6 Oct 2026 | Electronic Record and Electronic Signature Requirements | 0024-RU-A-Q2920-00702_L | Equivalent credit | Quality system, documentation and records |
| 6 Oct 2026 | Electronic Record and Electronic Signature Requirements | A-Q2920-00702-K | Passed | Quality system, documentation and records |
| 6 Oct 2026 | Good Documentation Practices On-Line Test | A-Q2920-00069-AM-TEST | Passed | Quality system, documentation and records |
| 6 Oct 2026 | Quality Manual for QMSID QMS-0024 | A-Q2920-00053-CT | Passed | Quality system, documentation and records |
| 6 Oct 2026 | Quality System Overview Training Materials | QSO-A-TGM-01-001 | Passed | Quality system, documentation and records |
| 6 Oct 2026 | Reporting of Customer Feedback Work Instructions | A-Q2920-01767-D | Passed | Complaints, CAPA and post-market |
| 1 Oct 2026 | Usability Engineering Procedure | 0056-2005000904-02 | Passed | Design, development and release |
| 21 Sept 2026 | Complaint _INVESTIGATION WORKFLOW PROCEDURE | 0048-RU-2004000711_07 | Passed | Complaints, CAPA and post-market |
| 10 Sept 2026 | Information Security Management System Scope | EI-ISMS-P-100001-10 | Passed | Product security |
| 10 Sept 2026 | Quality Manual for QMS- 0056 | 0056-2005001165-09 | Equivalent credit | Quality system, documentation and records |
| 10 Sept 2026 | Quality Manual for QMS- 0056 | 0056-2005001165-08 | Passed | Quality system, documentation and records |
| 10 Sept 2026 | Quiz - Information Security Management System Scope | EI-Q-ISMS-P-100001-10 | Passed | Product security |
| 19 Aug 2026 | Azure DevOps Server User Work Instruction | 0024-RU-A-QB300-01035_F | Passed | Tools and work instructions |
| 10 Aug 2026 | 16.2.12.3 Perform product safety risk analysis, risk evaluation, & risk control | 0056-2005001488-05 | Passed | Product safety and risk management |
| 10 Aug 2026 | 16.2.12.3 Perform Product Safety Risk Analysis, Risk Evaluation, and Risk Contro | QMS0200-4005000199_01 | Equivalent credit | Product safety and risk management |
| 10 Aug 2026 | Design and Development Procedure | 0056-2005000005-05 | Passed | Design, development and release |
| 10 Aug 2026 | Design and Development Procedure | 0056-2005000005-05 | Passed | Design, development and release |
| 5 Aug 2026 | Windchill - Users Work Instructions | 0024-RU-A-Q2920-01371_M | Passed | Tools and work instructions |
| 3 Aug 2026 | Labeling of Products Work Instruction | 0056-2005000068-04 | Passed | Design, development and release |
| 3 Aug 2026 | Labeling of Products Work Instruction | 0056-2005000068-04 | Passed | Design, development and release |
| 9 Jul 2026 | 16.2.10 Manage product correction and removal | 0056-2005001466-05 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10 Manage product correction and removal | 0056-2005001466-05 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10.1 Assess & Evaluate Potential C&R | 0056-2005001469-04 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10.2 Establish C&R Strategy Work Instruction | 0056-2005001317-04 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10.3 Develop C&R deliverables Work Instruction | 0056-2005001471-04 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10.4 Initiate & Execute C&R Work Instruction | 0056-2005001472-04 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | 16.2.10.5 Monitor & Close C&R Work Instruction | 0056-2005001474-04 | Passed | Field actions and correction and removal |
| 9 Jul 2026 | Quiz - Creation of User Documentation and Localization of Products Procedure | 0056-Q-2005000015 | Passed | Design, development and release |
| 8 Jul 2026 | Design Output Procedure | 0056-2005000035-04 | Passed | Design, development and release |
| 8 Jul 2026 | Design Output Procedure | 0056-2005000035-04 | Passed | Design, development and release |
| 8 Jul 2026 | Mandatory Roles for Document Creation, Review and Approval WI | 0056-2005000307-09 | Passed | Quality system, documentation and records |
| 14 Jun 2026 | Creation of User Documentation and Localization of Products Procedure | 0056-2005000015_03 | Equivalent credit | Design, development and release |
| 14 Jun 2026 | Creation of User Documentation and Localization of Products Procedure | 0056-2005000015-03 | Passed | Design, development and release |
| 10 Jun 2026 | NC Product _INSTRUCTION FOR THE USE OF THE ISSUE MANAGEMENT SYSTEM | 0048-RU-2004000601_05 | Passed | Complaints, CAPA and post-market |
| 10 Jun 2026 | PROCESS FOR USE OF THE ISSUE MANAGEMENT SYSTEM | 0048-E-2004000594_06 | Passed | Complaints, CAPA and post-market |
| 4 Jun 2026 | Product Security Risk Management Procedure | 0056-2005000023-04 | Passed | Product security |
| 4 Jun 2026 | Quiz - Product Security Risk Management | 0056-Q-2005000023 | Passed | Product security |
| 22 May 2026 | Design Change Procedure | 0056-2005000034-04 | Passed | Design, development and release |
| 22 May 2026 | Design Change Procedure | 0056-2005000034-04 | Passed | Design, development and release |
| 22 May 2026 | Design Change Work Instruction | 0056-2005000080-03 | Passed | Design, development and release |
| 22 May 2026 | Design Change Work Instruction | 0056-2005000080-03 | Passed | Design, development and release |
| 18 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices | 0000-UL-ISO13485_04.1 | Equivalent credit | Quality system, documentation and records |
| 18 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices | GLOBAL-UL-ISO13485-001_03 | Passed | Quality system, documentation and records |
| 18 May 2026 | An Introduction to ISO 13485 The Quality Management System for Medical Devices | 0000-UL-ISO13485_04 | Equivalent credit | Quality system, documentation and records |
| 18 May 2026 | Asset Management Procedure | EI-ISMS-Pr-060012-2.0 | Passed | Product security |
| 18 May 2026 | Complaint _INVESTIGATION WORKFLOW PROCEDURE | 0048-RU-2004000711_06 | Passed | Complaints, CAPA and post-market |
| 18 May 2026 | PROCESS FOR USE OF THE ISSUE MANAGEMENT SYSTEM | 0048-Q-2004000594_05.2 | Passed | Complaints, CAPA and post-market |
| 18 May 2026 | Quiz - Asset Management Procedure | EI-Q-ISMS-Pr-060012 | Passed | Product security |
| 9 May 2026 | Complaint _INVESTIGATION WORKFLOW PROCEDURE | 0048-RU-2004000711_05.1 | Passed | Complaints, CAPA and post-market |
| 9 May 2026 | Complaint _INVESTIGATION WORKFLOW PROCEDURE | 0048-RU-2004000711_05.1 | Passed | Complaints, CAPA and post-market |
| 9 May 2026 | Design Controls_PROCESS FOR THE USE OF THE CHANGE REQUEST MANAGEMENT SYSTEM | 0048-RU-2004001541_02 | Passed | Design, development and release |
| 9 May 2026 | NC Product _INSTRUCTION FOR THE USE OF THE ISSUE MANAGEMENT SYSTEM | 0048-RU-2004000601_04 | Passed | Complaints, CAPA and post-market |
| 7 May 2026 | 16.2.12 Manage product safety, property, and environmental risks | 0056-2005001485-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12 Manage Product Safety, Property, and Environmental Risks Procedure | QMS0200-4005000196_01 | Equivalent credit | Product safety and risk management |
| 7 May 2026 | 16.2.12.1 Create and maintain product safety risk acceptability policy WI | 0056-2005001486-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.1 Create and Maintain Product Safety Risk Acceptability Policy WI | QMS0200-4005000197_01 | Equivalent credit | Product safety and risk management |
| 7 May 2026 | 16.2.12.2 Create product safety risk management file and plan | 0056-2005001487-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.2 Create Product Safety Risk Management File and Plan Work Instruction | QMS0200-4005000198_01 | Equivalent credit | Product safety and risk management |
| 7 May 2026 | 16.2.12.3 Perform product safety risk analysis, risk evaluation, & risk control | 0056-2005001488-04 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.4 Evaluate Overall Residual Risk and Perform Risk Management Review | 0056-2005001490-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.4 Evaluate Overall Residual Risk and Perform Risk Management Review WI | QMS0200-4005000200_01 | Equivalent credit | Product safety and risk management |
| 7 May 2026 | 16.2.12.5 Perform Production and Post- Production Activities WI | 0056-2005001337-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.6 Evaluate product safety risk management process performance WI | 0056-2005001491-03 | Passed | Product safety and risk management |
| 7 May 2026 | 16.2.12.6 Evaluate Product Safety Risk Management Process Performance WI | QMS0200-4005000202_01 | Equivalent credit | Product safety and risk management |
| 7 May 2026 | 16.2.20 Manage Post Market Surveillance Procedure | 0056-2005001767-03 | Passed | Complaints, CAPA and post-market |
| 7 May 2026 | Azure DevOps Server User Work Instruction | A-QB300-01035-E | Passed | Tools and work instructions |
| 7 May 2026 | Compute Environment to Application Compatibility Matrix Guidance (RICI) | QMS0200-2005001167_02 | Equivalent credit | Design, development and release |
| 7 May 2026 | Compute Environment to Application Compatibility Matrix Guideline | 0056-2005001167-Rev 01 | Passed | Design, development and release |
| 7 May 2026 | FCO Procedure | 0056-2005000374-02 | Passed | Field actions and correction and removal |
| 7 May 2026 | FCO Work Instruction | 0056-2005000375-02 | Passed | Field actions and correction and removal |
| 7 May 2026 | Issue impact assessment template for MS-QMS portals | 0056-RU-2005001291-Rev 1 | Passed | Quality system, documentation and records |
| 7 May 2026 | Milestone and Gate Review Procedure | 0056-2005000021-Rev 02 | Passed | Design, development and release |
| 7 May 2026 | PMS Reporting requirements Matrix | 0056-2005001893-01 | Passed | Complaints, CAPA and post-market |
| 7 May 2026 | Portfolio Management Procedure | QMS0200-2005000129_03 | Equivalent credit | Design, development and release |
| 7 May 2026 | Portfolio Management Procedure | 0056-2005000129-02 | Passed | Design, development and release |
| 7 May 2026 | Product safety risk management matrix template | 0056-T-2005001496-04 | Passed | Product safety and risk management |
| 7 May 2026 | Production Controls Procedure | 0056-2005000040-Rev 01 | Passed | Design, development and release |
| 7 May 2026 | Solution Development guidance | 0056-2005000128-01 | Equivalent credit | Design, development and release |
| 7 May 2026 | Solution Development guidance | XP-0309-01-G2/1.0 | Passed | Design, development and release |
| 7 May 2026 | Solutions Design Launch Maintenance Procedure | QMS0200-2005000749_03 | Equivalent credit | Design, development and release |
| 7 May 2026 | Supply Chain Control Board (SCCB) work instruction | 0056-2005000088-04 | Passed | Design, development and release |
| 7 May 2026 | Supply Chain Control Board (SCCB) Work Instruction | QMS0200-4005000614_01 | Equivalent credit | Design, development and release |
| 3 Apr 2026 | 19.4.2 Manage QMS Learning Procedure | 0056-2005001583-03 | Passed | Quality system, documentation and records |
| 3 Apr 2026 | 19.4.2.4 Manage Training Assignments Work Instruction | 0056-2005001592-04 | Passed | Quality system, documentation and records |
| 3 Apr 2026 | 19.4.2.5 Execute Learning Activities Work Instruction | 0056-2005001593-03 | Passed | Quality system, documentation and records |
| 3 Apr 2026 | ITSUI_Lumen_For Individual Actions | QMS0200-4005000102_01 | Equivalent credit | Tools and work instructions |
| 3 Apr 2026 | Lumen ITSUI for Individual actions | 0056-2005002053-01 | Passed | Tools and work instructions |
| 1 Apr 2026 | Windchill - Users Work Instructions | A-Q2920-01371-L | Passed | Tools and work instructions |
| 31 Mar 2026 | BSL 11.1.1 - Secure Development Baseline | EI-ISMS-BSL-11.1.1_03 | Passed | Product security |
| 14 Mar 2026 | QMS-0025 Quality Manual | 0025-RU-8001000169_12 | Passed | Quality system, documentation and records |
| 10 Mar 2026 | 16.2.9 Manage Corrective and or Preventive Actions (CAPA) Procedure (NextGen) | 0056-2005002047-01 | Passed | Complaints, CAPA and post-market |
| 10 Mar 2026 | CAPA Procedure (Next Gen) | QMS0200-4005000186_01 | Equivalent credit | Complaints, CAPA and post-market |
| 10 Mar 2026 | Good Documentation Practices | 0056-2005000124_02 cycled | Equivalent credit | Quality system, documentation and records |
| 10 Mar 2026 | Good Documentation Practices | 0056-2005000124-Rev 02 cycled | Passed | Quality system, documentation and records |
| 10 Mar 2026 | Good Documentation Practices | 0056-2005000124-Rev 02 | Equivalent credit | Quality system, documentation and records |
| 10 Mar 2026 | Good Documentation Practices | 0056-2005000124-02 cycled | Equivalent credit | Quality system, documentation and records |
| 26 Feb 2026 | Site Inspection Response Team (SIRT) | Global-E-CDI001394027_D | Passed | Complaints, CAPA and post-market |
| 21 Feb 2026 | Azure DevOps Server User Work Instruction | A-QB300-01035-E | Passed | Tools and work instructions |
| 20 Feb 2026 | BSL 11.1.1.d - Secure Coding Baseline - Details | EI-ISMS-BSL-11.1.1-03 | Passed | Product security |
| 20 Feb 2026 | Physical Controls for Information Security - Clear Desk Clear Screen Policy | EI-ISMS-P-100010-1.4 | Passed | Product security |
| 20 Feb 2026 | Technological controls for Software Development Policy | EI-ISMS-P-100011-1.5 | Passed | Design, development and release |
| 1 Feb 2026 | 4.2.1 Manage Clinical Evidence and Evaluations | 0056-2005001393-02 | Passed | Quality system, documentation and records |
| 1 Feb 2026 | 4.2.1 Manage Clinical Evidence and Evaluations | 0056-2005001393-03 | Equivalent credit | Quality system, documentation and records |
| 1 Feb 2026 | 4.2.1 Manage Clinical Evidence and Evaluations | 0056-2005001393-02 | Passed | Quality system, documentation and records |
| 1 Feb 2026 | 4.2.1 Manage Clinical Evidence and Evaluations Procedure (II) | QMS0200-2005001393_04 | Equivalent credit | Quality system, documentation and records |
| 1 Feb 2026 | Azure DevOps Server User Work Instruction | A-QB300-01035-E | Passed | Tools and work instructions |
| 29 Jan 2026 | Third Party License Management guideline (SSD) | 0056-2005001889-01 | Passed | Design, development and release |
| 29 Jan 2026 | Third Party License Management Guideline (SSD) | QMS0200-2005001889_02 | Equivalent credit | Design, development and release |
| 28 Jan 2026 | Labeling of Products Work Instruction | 0056-2005000068-03 | Passed | Design, development and release |
| 28 Jan 2026 | Labeling of Products Work Instruction | 0056-2005000068-03 | Passed | Design, development and release |
| 19 Jan 2026 | Maintenance Release Planning and Execution Guideline | 0056-2005000297-02 | Passed | Design, development and release |
| 19 Jan 2026 | Maintenance Release Planning and Execution Guideline | 0056-2005000297-02 | Passed | Design, development and release |
| 19 Jan 2026 | Quality Manual for QMS- 0056 | 0056-2005001165-07 | Passed | Quality system, documentation and records |
| 6 Jan 2026 | 16.2.10 Manage product correction and removal | 0056-2005001466-04 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | 16.2.10.1 Assess & Evaluate Potential C&R | 0056-2005001469-03 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | 16.2.10.2 Establish C&R Strategy Work Instruction | 0056-2005001317-03 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | 16.2.10.3 Develop C&R deliverables Work Instruction | 0056-2005001471-03 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | 16.2.10.4 Initiate & Execute C&R Work Instruction | 0056-2005001472-03 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | 16.2.10.5 Monitor & Close C&R Work Instruction | 0056-2005001474-03 | Passed | Field actions and correction and removal |
| 6 Jan 2026 | Azure DevOps Server User Work Instruction | A-QB300-01035-E | Passed | Tools and work instructions |
13 of the 187 rows repeat another row with the same code, date and status; they are counted here as the history lists them (174 distinct). The history PDF and the transcript are different views and their dates can differ by a day (for example C&R Awareness: 6 Oct on the transcript, 7 Oct in the history). Rows are not merged. Equivalent credit means the history credits an equivalent earlier completion; it is not a separate pass. Raw data: 2026-Learning/learning-history-2026.md, 2026-Learning/cornerstone-transcript-page1.md; sources 2026-Learning/learning-history-lms.pdf and 2026-Learning/cornerstone-transcript-page1.png.