"when we actually going to start the navigation, which is the first chapter, since then every one of you are going to get assignment, so each one will get their assignment and they will get their tenant, and then you have to start configuring the stuff whatever we have in our session."— 从第一章 Navigation 开始,每人都会拿到作业和自己的租户,然后把课上讲的内容在租户里配置出来——每节课都跟配置作业挂钩。
"first we will talk about the architecture. Yes, if you are not sure how Workday is built, or what all things to consider before we start learning any concept, so it will be not justified."— 先讲架构——如果连 Workday 是怎么搭起来的都不清楚,那学任何概念都站不住脚。
12:15
What is Workday:一页定义与 HCM 打头阵
幻灯片原文:Workday 是把 HR、payroll、talent、reporting 及其他业务能力统一进一个 system of record 的云端企业平台;在 HCM 里管理 worker data、组织结构、staffing、审批和员工从 hire 到 retire 的全生命周期事务
四条要点原文:Cloud-native enterprise application;Used for Human Capital Management and related functions;Supports real-time transactions, approvals, and analytics;Designed for continuous updates rather than traditional upgrade projects
红笔板书:HCM Application → 2 years → payroll module——演示「先上 HCM 用两年、再实施 payroll」的场景,对应幻灯片 one system of record 的统一说法
"if I am the people partner means I am the HR partner, so my responsibility is to maintain the data of all the employees who are working for New York location."— people partner 就是 HR partner,他负责维护整个纽约办公室所有员工的数据。
14:20
每个生命周期事务都要过审批链
🖼 画面仍停在 What is Workday 一页(00:05-00:22 同一帧,无新增画面),此段为口播内容。
请假也走流程:manager 审批、absence partner 被知会、payroll 被告知是带薪还是不带薪——Workday 里每笔 transaction 都跟着审批过程(business process 的前置概念)
财务视角:某群员工的工资从哪个 cost center 出钱,是组织结构要回答的问题
"Even manager says, then there are different teams which involves. There are people partner who has to approve, then compensation partner has to approve the hike in the compensation and payroll has to process the latest salary."— 就算经理同意了,还有一堆团队要进来:people partner 先批,compensation partner 批涨薪,payroll 再按最新工资处理。
"The foundation to any module in Workday is associated with human capital management. Okay? So, whether you be a functional consultant or you be a technical consultant or you are expert into payroll, but still the entry gate to get into a Workday ecosystem is HCM module"— Workday 任何模块的地基都连着 HCM;不管你以后走 functional、technical 还是 payroll,进 Workday 生态的门都是 HCM 模块。
"I can run and I can say that okay, if for the month of March, how many employees we have hired, what is the iteration rate, which location these employees are coming from, which department they are going to go."— 跑个报表就能看到:3 月份我们录用了多少人、离职率多少、这些员工来自哪个地点、进了哪个部门。(字幕把 attrition 打成了 iteration)
22:30
各国法规 Workday 替你跟:背调的例子
🖼 画面仍停在 What is Workday 一页,此段为口播内容。
同一个 Workday,不同国家规矩不同:美国 background check 是法定必须;印度不强制,有的公司选择 hire 之后再补做背调
"in US, it is mandatory to do a background check. In India, it is not mandatory to do a background check, or some organizations wanted to do a background check, so they will do the background check once the employee is hired."— 在美国做背调是法定的;在印度不强制,有些公司想查,就放到员工入职之后再查。
28:20
零系统要求:一个浏览器跑遍全球
🖼 画面停在 cloud and SaaS 页的基态(同页板书 00:24-00:35 反复),此段为口播内容。
数据在中心:印度、美国、新加坡的用户用同一份数据;从印度跑 India population 的报表得 10,000,从新加坡跑同一个报表得到同样记录——centralized hosting + web 访问
没有任何系统配置要求:不需要装机、不需要问 support 要规格清单,只要网络通 + 浏览器能开;2GB 还是 10GB 内存、多大存储都无所谓
Netflix 类比:片子不存你手机里,存在中心;换手机登录照样能看——SaaS 应用同理
这就是 SaaS 交付形态:consume Workday as a service,取代购买、安装、维护 on-premise 结构(幻灯片正文原句)
"There is no system requirement. The only requirement is that you should have a live internet and you need a browser to use Workday application. If you have these two things, then you can use. Whether you have 2GB of RAM or you have 10GB of RAM, whatever may be your storage, if you are able to use your browser, you can use the Workday application."— 没有系统要求,唯一的门槛是有网、有浏览器。内存 2G 还是 10G、硬盘多大都无所谓,浏览器能开就能用 Workday。
谁维护这套结构?Workday 团队——客户不碰基础设施;这个中心化的载体就叫 data center
幻灯片正文(cloud and SaaS 页):SaaS 意味着集中托管维护、web 访问、云交付模型、browser-based、可扩展且始终最新、客户基础设施负担低
"So, this is my cloud. Now, the question here is who maintains this structure? So, the maintenance is done by Workday team, okay? Workday will do the maintenance"— 这是我画的云。问题来了:谁维护这套结构?答案是 Workday 团队,维护是他们的事。
32:15
数据中心全球分布,按签约总部来选
🖼 画面仍是 00:30:15 那张云图(MAD 0.09 同帧),此段为口播内容。
Workday 数据中心分布:美国若干(couple of)、英国一个、印度在建(coming up with one)、澳大利亚和新西兰各有一个
你落在哪个数据中心,取决于总部在哪、合同从哪个总部签:美国客户进美国 DC,英国/欧洲客户进对应 DC
任何地点的员工都远程访问同一中心应用,这整套结构即 cloud-based SaaS
成本对照(讲师口播「Imagine back in 2000」):当年实施一套软件要先备数据库、买许可、做集成、过 license 审批——云结构下这些开销没有了
"they have couple of data center in US, they have one data center in UK, they have They are coming up with one data center in India. They have their data center in Australia, New Zealand."— 美国有好几个数据中心,英国有一个,印度正在再建一个,澳大利亚和新西兰也各有。(口播数字照录)
40:15
多租户:一个中心切成四家,互不可见
板书:一个 USA 数据中心的轮廓里切出四个格,分别标 Amazon、Netflix、Accenture、IBM——一个 DC 同时服务多家客户,不是 80% 客户就建 80 个中心
幻灯片原文:multi-tenant SaaS,多个客户共享一个物理应用环境,各客户数据留在自己的 tenant 里逻辑隔离(underlying infrastructure is shared)
五条 bullet:One common application platform / Separate customer tenants / Shared infrastructure, isolated data / Common release cycle across customers / Security linked to tenant and user access
"While each customer data remain isolated in its own tenant. What is tenant? The environment wherein the Workday is being used."— 每个客户的数据都隔离在自己的 tenant 里。什么是 tenant?就是你使用 Workday 的那个环境。
"it says that it is WD2. Means it is using data center two. If you are using uh let's say some European customer, you will say that it is WD3. So, this informs that which data center this Workday is coming from."— 地址里写 WD2,就是用 2 号数据中心;欧洲客户会看到 WD3——这一段告诉你这套 Workday 跑在哪个数据中心。
1 万多家客户全部同一版本;升级自动写进合同、不加钱——对比 Microsoft Office 得再掏订阅费;每次发布含 bug fixes、enhancements、new roll out、新特性
"in Workday, since it is part of your contract that all the customers who are using Workday, they will automatically be upgraded with the latest release without any additional cost."— 在 Workday,合同里就写明了:所有客户自动升级到最新 release,不额外收一分钱。
49:15
ABC 公司 1000 人:四种角色四份权限
板书:虚线框标注 ABC Company 1000(人),框内列 Employee、manager、HR Partner、HR Director 四行——四种角色权限各不相同
"you see, roles are same, but their accesses are different. So, what this is, it's a company's responsibility. So, company's stakeholder will determine what sort of access is given to these users"— 角色一样,权限却不一样。这是公司的责任:给这些用户开什么权限,由公司 stakeholder 拍板。
"Release will automatically be there, but the releases are actually are of two type. One is directly available, which is not going to impact any implementation, anything, and the other one is opt-ins."— 发布会自动到,但 release 组件分两类:一类 directly available,不影响你的实施;另一类是 opt-in,要客户自己决定。
"it is 1 month prior, minimum 30 days before the new release, Workday gives you the preview tenant for testing the new features."— 提前一个月、最少发布前 30 天,Workday 会开出 preview tenant 让你先测新特性。
55:20
对象模型:Workday 把数据存成对象
幻灯片原文:Workday 架构用 software objects 和 metadata 定义应用行为,而不是硬啃数据库定制(rather than relying only on rigid database customization)
页面列出六类对象:Worker、Organization、Position、Job Profile、Compensation Package、Business Process——an object is a business entity the system understands
"Workday's architecture uses software objects and metadata to define application behavior rather they rely on rigid database customization."— Workday 用软件对象和元数据来定义应用行为,而不是依赖死的数据库定制。
1:00:10
租户全景表:四种环境各司其职
表格原文:Production = Live system of record used by the business;Sandbox = Safe copy of Production for testing and validation;Sandbox Preview = Preview environment with upcoming feature releases;Implementation = Flexible tenant for configuration, testing, and deployment work
招聘、晋升这类 live 事务只在 production 做;选 Workday 起步至少拿到四种租户,其中 production 只有一个
顾问排障不碰生产:直接在 production 上研究问题「是个 big no」,enable/disable 都可能出事——问题复制到 sandbox 里修
"if I am opting for Workday, so I will get minimum four tenants, okay? There is only one and one production environment."— 选了 Workday,至少给你四种租户;其中 production 环境有且只有一个。
"whatever data you have in sandbox environment will last for 7 days. But, there are some changes you have to do and that is going to take more than 7 days."— 你在 sandbox 里做的一切最多保留 7 天。可有些变更要做的比 7 天长多了。
实施租户可以有 n 个,但每一个都要额外掏钱(on charge base)——只有前三种是固定一个
口播还答了「哪个租户适合有完整配置经验的人」:租户按用途分,不按资历分,顾问本来就全有权限
"production is one, sandbox is one, preview is one. But, you can have n number of implementation environment. Obviously, anything which comes with the cost."— production、sandbox、preview 都只有一个,但 implementation 环境你可以开 N 个——当然,花钱。
"you have to check whether testing is approved, stakeholder is satisfied, 99.9% of the testing cases should be passed, all such scenarios are considered when you deploy things into production environment."— 推上生产前要确认:测试批了没有、stakeholder 满意没有、99.9% 的用例过了没有——这些都要过一遍。
1:12:45
首页 UI 一瞥:下章导航要讲这些地方
画面是 Workday 首页局部:Team Highlights(4 个头像+View More/Team Org Chart)、Announcements 1 of 5「Please complete Objective Setting…completing workday HCM Course with Hand on L…」(截断,原文如此)、Important Dates:JUN 12 Birthday Aaron Davon、Timely Suggestions 标题
"What happens if you click here? What happens if I click here? What is this 99 plus? What is 54? What are these menus?"— 点这里会怎样?点那里会怎样?这个 99+ 是什么?54 又是什么?这些菜单都是啥?
1:15:15
招聘看板实机:绿框圈出搜索栏与角标
画面:My Recruiting Jobs 页;绿笔框出三块——顶部搜索栏、右上通知铃 54 与邮件 99+、中间的职位表
"One customer says we take five steps, second customer will say we take 10 steps to complete the higher."— 一家客户说我们招聘走 5 步,另一家说要走 10 步才完成 hire。(字幕把 hire 打成 higher)
1:18:00
实施第一步:把客户拉进 Workday 词典
🖼 此段画面仍是上一页部署方法论幻灯片基态,无新板书,按口播记录。
签完合同别急着要需求:客户原来用 PeopleSoft,听不懂 business process、compensation package 这些 Workday 概念
术语对照举例:PeopleSoft 叫 workflow 的东西 = Workday 的 business process——开口先说对方的词,再教你的词
不对齐概念的后果:客户要 A、你给 B,需求采集全盘错位
所以方法论的第一动作是教育客户、统一语言,把需求谈准再进配置
"whenever you are saying business process, in PeopleSoft it is workflow. So, you say that okay, the workflows, I need the workflows and when you say workflow, then you say it is business process."— 你说 business process,PeopleSoft 里它叫 workflow。开口要 workflow,回头再告诉对方:这就是 business process。
1:19:20
部署方法论:结构化、发现驱动、快出价值
幻灯片原文:Workday deployment 用结构化方法把客户从 planning 推进到 live operation,controlled and repeatable;Workday Launch 是基于过往成功部署的 preconfigured approach
Include these key ideas 五条原文:Structured deployment framework / Discovery-led planning / Preconfigured starting point in some deployment models / Reduced guesswork and risk / Focus on faster value realization
"We follow a structured methodology to move a customer from planning to live operation in controlled and repeatable way. Yes. Workday Launch is present as a pre-configured approach."— 我们用一套结构化方法,把客户可控、可复现地从计划推进到上线运营;Workday Launch 就是现成的预配置路径。
讲完 discovery 才从预配置起点进部署:business process → security → compensation package
减少 guesswork 的实例(口播数字):流程加 10 级审批,time-to-hire 就要 10 天;有的公司 4-5 天完成 hire——客户不懂 Workday 边界,顾问要把 best practice 讲在前面,不必要审批可改成通知
"What is the scope of customization? If you are raising any ticket, what is the time taken by Workday to resolve the ticket? All such things will be explained before you start getting into the requirement phase."— 定制范围是什么?提了工单 Workday 多久解决?这些都要在进入需求阶段之前先讲明白。
这个「把旧系统全部历史更新进新环境」的过程就叫 data conversion,只是实施的一个子部分(有学员正是做 conversion 项目的)
"I have to have all their data correctly, their hire date, their leave taken, their promotion and record, their performance record. So, I have to map all of these record in the current application."— 这 1000 人的数据必须全对:入职日期、休假记录、晋升记录、绩效记录——都得映射到新系统里。
1:25:45
部署阶段流程图:四段与五段两种说法
流程图原文(画面四个箭头框):Plan → Architect and Configure → Test → Deploy
幻灯片正文:一份指南列四大阶段 Plan / Architect and Configure / Test / Deploy;另一份实施向资料拆成五段 Plan / Architect / Configure and Prototype / Test / Deploy——结构一致:从计划到设计、测试、上线
"if I'm not aware of the methodology, I might say yes to everything and then while deploying, I might say, "Oh, sorry. These two These two requirements cannot be done.""— 不懂方法论就会满口答应,等到部署时才说:抱歉,这两条需求做不了。
1:27:00
五阶段名与 10/50/20/20 投入占比
🖼 画面处于四阶段流程图向阶段清单过渡中(同页无新信息),此段为口播内容。
口播实施阶段清单:planning → architect → configuring → prototype → test → deployment(「in a nutshell」原话)
各阶段工时占比(口播数字):planning 10%、architect+configure 50%、test 20%、deployment 20%(原话「planning is 10%. This is 50%, 20%, and then 20%」,中间 50% 指配置段)
课程承诺:课堂 activity 也照这个部署方法论执行,session 一布置的活动会贯穿各阶段
plan 阶段交付物:scope、stakeholders、timeline、roles、governance 都要确认并拿到 sign-off
"So, planning is 10%. This is 50%, 20%, and then 20%."— 占比大概这样分:计划 10%,(架构+配置)50%,测试 20%,部署 20%。
1:28:20
阶段清单四条:Plan 到 Deploy 各干什么
画面原文:1. Plan – confirm scope, stakeholders, timelines, roles, and governance;2. Architect and Configure – conduct workshops, define requirements, perform data conversion planning, review security, configure integrations and reports;3. Test – validate end-to-end business processes, integrations, roles, and data quality before go-live;4. Deploy – complete training, execute cutover, load production data, transition to operations
允许 10% 变动的理由:法规变化、并购新组织——change is the only constant
实施不是一个人:project manager、测试组、business process 组、security group 开发组共定时线与 governance
"change is the only constant, but the scope should not exceed more than 10 to 15%. So, we need to always have a a scope of 10 to 15% of variation when we are deploying, but 80% of the requirement has to be signed off."— 唯一不变的就是变化本身,但浮动别超过 10 到 15%——80% 的需求必须签字定死。
培训要件:SOP 准备到位、ways of working 写清楚、prod 加载信息说明白、出事故找哪个团队的联系路径
"They'll try to break the system. They'll see that whether the configuration which has been done is meeting their requirement or not."— UAT 时用户会尽力把系统搞坏,看看配出来的东西到不到他们的要求。
1:33:30
基础术语表:七条 Workday 黑话
画面表(Term/Meaning):Worker = 在 Workday 里被跟踪的人,employee 或 contingent worker;Business Process = 完成一个业务目标的任务序列(hire/termination);Security Role = 决定用户能 view 或 do 什么;Inbox / To-Do = 需用户行动的任务与提醒;Job Profile = 定义工作特征(任职资格与 pay 相关设置)
注意:画面上 Supervisory Organization 与 Staffing Model 两行的 Meaning 相同,都写 Defines how jobs or positions are controlled in an organization——疑似幻灯片笔误(待核对);口播的区分是 supervisory org 管职位汇报线、staffing model 管怎么 hire(bulk hire 还是 approval-based)
讲师预告:导航部分会逐条深挖——supervisory organization 怎么建、staffing model 怎么配、business process 怎么开发、security group 怎么收权限
"Supervisory organization, how my jobs and positions are being controlled? Staffing model, how I'm going to hire my employee? Whether I'm going to bulk hire? Whether I'm going to hire an approval base?"— 主管组织:我的 jobs 和 positions 归谁管;staffing model:我的员工怎么招进来——批量招,还是逐级审批着招?
1:35:20
实时实施案例:Core HCM 五步落地
页头原文:实施 Core HCM 的公司从定义 supervisory organizations、worker types、staffing models、security roles 起步,再配 hire/transfer/promotion/termination 四条 business process
讲师承诺课程照单执行:给一家演示公司,定组织、定 security requirement、定 business process、识别层级、配到 completion 并全程留痕
"I have to conquer, divide and conquer my implementation approach that, "Okay, 2 weeks I'm going to work on requirement, four weeks I'm going to deploy, two weeks I'm going to do a testing, and finally I'm going to have a training and give handover to my customer to use the Workday application."— 六个月不能一锅炖,得分而治之:2 周做需求、4 周做部署、2 周做测试,最后培训交接,客户就能用了。
主数据就位后走 mass upload 模板直灌 Workday,即 data conversion 项目;1 万员工不可能手工 hire 进场
技术侧预告:mass hire、跨系统迁移将在功能部分完结后进入 technical 课程
"If I have four companies in legacy system, in my Workday also I have four company. In your legacy system you have 20 job profiles, so in Workday you should have 20 job profiles. You have 10 security roles, you will have 10 security roles."— 旧系统 4 家公司,Workday 里也得建 4 家;旧系统 20 个 job profile,Workday 就配 20 个;10 个安全角色,对应 10 个——一比一映射。