← 返回教程首页 | 视频图文笔记 第 4 / 5 期

Workday 人员配置模型与职务画像:Position 与 Job Management、Hiring Restrictions、创建 Job Profile 和职位

Staffing Model and Job Profile | Workday HCM Training | ZaranTech

频道:Workday Learner Community(ZaranTech) 时长 1:35:42 发布于 2023-02-26 28 帧对照 · 全片覆盖 原视频 ↗
⏱ 每节的 时间点 对应视频画面,点开原视频拖到该时间即可对照。
实际内容与 YouTube 标题相符:主线是 Staffing Model 与 Job Profile。课程用幻灯片对比两种配置模型(Position Management 控制最强、Job Management 灵活求快),讲招聘限制、配置模型可改的时机、Maintain Staffing Models 任务,并实操创建 Job Profile(Manager, Training)与 Create Position,演示引用画像自动带出资质、职位审批业务流。补充一点:幻灯片只列两种模型,但 Maintain Staffing Models 报表里同时出现 Position / Headcount / Job Management Enabled 三列,说明 Workday 还有 Headcount 模型(本课不展开)。00:18–00:40 有较长一段在排障共享培训租户(Logan McNeil 无法建职位/改角色、找不到可指派角色),属非主线,仅保留一帧作为「用可指派角色改继承角色」的示例。字幕为自动生成,术语误识较多(staffing→staf fing、position→posi tion、HCM→SEM、hire→higher、positions→Physicians、staffing→stuffing 等),正文一律用正确术语,quote_en 保持字幕原样。
5:30

监督型组织的结构骨架

监督型组织的结构骨架
  • Human Resources 组织卡片字段:Type = Supervisory、Organization ID = SUPERVISORY_ORGANIZATION-6-540、Superior Organization = Test WD。
  • 「Subordinates (first 5)」只列前 5 个下级(如 Payroll Administration、Recruitment、Stark sup org、sysco、Test_hk sup org);Workday 首页只显示 top 5,找不全要靠搜索。
  • Members 标签页显示 0 items / No Data,说明监督型组织本身只是层级容器,得把招聘进来的人挂在职位上才会出现成员。
  • 页签依次为 Members、Details、Staffing、Roles、Security Groups、Organization Assignments、Additional Data。

"this is a supervisory organization called Human Resources it has an organization ID it has a superior org it has some subordinates and then there are no members in it because there is nobody is hired into it"— 这是一个叫 Human Resources 的监督型组织,它有组织 ID、上级组织、若干下级组织,而且里面没有成员,因为还没有人被招聘进来。

6:45

本次课的两条主线

本次课的两条主线
  • 幻灯片标题为「DAY 3: Workday HCM Fundamentals」,本次聚焦两个主题:Staffing Models 与 Jobs and Positions。
  • 承接上节的监督型组织(Hierarchy)——有了层级和职位打开,才谈得上如何定义和填充岗位。
  • 讲师口述明确今天的主题是「different staffing models」。

"today what we're looking at is the different Staffing models right"— 今天我们要看的是不同的人员配置模型(Staffing Models)。

7:15

配置模型:必选项,先二选一

配置模型:必选项,先二选一
  • 幻灯片原文:Staffing Model 用于决定岗位如何定义与填充、提供不同层级的管控、支撑不同的人员配置目标。
  • 明确写「Every Supervisory Org must be associated with a staffing model」——每个监督型组织都必须挂一个配置模型,是强制项。
  • 本页只列两种:Position Management 与 Job Management。(后文 Maintain Staffing Models 报表里还会出现 Headcount 一列,本课不展开。)

"Staffing models are used to determine how jobs are defined and filled provide different levels of control over Staffing and support different Staffing goals every supervisory Arc must be associated with a staffing model"— 人员配置模型用来决定岗位如何定义与填充、提供不同层级的管控、支撑不同的人员配置目标;每个监督型组织都必须关联一个配置模型。

8:45

职位驱动:管控最细

职位驱动:管控最细
  • 幻灯片首条:Allows for most control——两种模型里管控最细的一种。
  • 每招一个人就建一个唯一职位(Single position is created to be filled),可在每个职位上单独设招聘规则与限制。
  • 职位会因岗位变动而空出(Positions can open after a job change),也可随人员调岗在监督型组织间移动。
  • 职位若长期不需要可以关闭(Position can be closed if not needed)。

"because it's position driven every time you want to hire somebody into your supervisory org you will create one unique position and on each position you can have separate hiring rules and restrictions"— 因为它是职位驱动的,每次你想往监督型组织里招人,都要建一个唯一的职位,并可以在每个职位上单独设置招聘规则和限制。

16:15

建职位与招聘冻结的入口

建职位与招聘冻结的入口
  • 路径:Actions → Staffing,展开后有三个命令:Create Position、Manage Organization Hiring Freeze、Manage Position Hiring Freeze。
  • 招聘冻结可作用于整个组织(Organization)或单个职位(Position)——预算收紧时没有专门的工作流,实操就是挂这个冻结。
  • 该组织 Staffing model 为 Position Management,Members 显示 0 items,一个职位都还没有。
  • 右上方卡片可见 Primary Location = New York,以及 superior org(如 sysco / Logan McNeil、Test_hk sup org / Joy Banks)。

"so if even if you try to hire somebody the system would not allow you to hire anybody into Human Resources because you don't have a position"— 即便你想招人,系统也不会让你往 Human Resources 里招任何人,因为你还没有职位。

36:15

改继承来的可指派角色

改继承来的可指派角色
  • 新建监督型组织后,manager 等角色是从上级继承来的;要改,讲师给出的路径是 Actions → Rules → Assign Roles。
  • 页面为 Assign Roles 表单(黄色 Save / Cancel 按钮)。
  • 演示想改 Absence Partner,但该共享培训租户里找不到可指派角色——讲师解释培训租户被很多人天天改权限、角色、访问,属常见状况。
  • 要点:改角色靠可指派角色(assignable roles),不是直接改组织本身。

"when I created the supervisory Arc the manager was inherited and I could not change it is there a way we can change the inherited role yeah uh it should be it should be through assignable roles"— 我创建监督型组织时,经理是继承来的、改不了;能不能改这个继承角色?——应该可以通过可指派角色(assignable roles)来改。

41:15

新建下级组织表单

新建下级组织表单
  • 在干净租户 Human Resources 下用 Reorganization → Create Subordinate 新建下级,标题栏显示 Superior = Human Resources。
  • 带红星的必填项是 Availability Date 与 Organization Subtype;本例 Effective Date / Availability Date 为 11/07/2020。
  • Organization Name 正在输入(讲师命名为 Ricky_11_7),Subtype 选 Department。
  • 其余为可选:Include Organization ID / Code / Manager-Leader in Name、Organization Code、External URL、Primary Location。

"right reorganization create a subordinate hit okay go ahead and give it a name let's call it as Ricky underscore 11 underscore what seventh I think and subtype let's call it as a department"— 打开 Reorganization,点 Create a subordinate,给个名字,就叫 Ricky_11_7,Subtype 选 Department。

42:15

新建下级的组织主页

新建下级的组织主页
  • 刚建的 Ricky_11_7 Department:Type = Supervisory、Organization ID = SUPERVISORY_ORGANIZATION-2-355、Superior Organization = Human Resources。
  • Members 仍是 0 items / No Data,因为还没往里招人。
  • View As Of = 11/07/2020(生效查看日期)。
  • 页签与标准组织一致:Members / Details / Staffing / Roles / Security Groups / Organization Assignments / Additional Data。

"you can see that there are no members because we have not hired anybody into it these are the details this is the Staffing it's a position management it inherits it"— 你会看到没有成员,因为我们还没往里招人;这是 Details,这是 Staffing——它是 Position Management,是从上级继承来的。

43:45

改模型的菜单入口

改模型的菜单入口
  • Staffing 标签页直接显示 Staffing Model = Position Management(继承自上级)。
  • 组织卡片:Manager = Joy Banks、Total Headcount = 0、Superior = Human Resources、Primary Location = San Francisco。
  • 改模型入口在 Actions 下拉里(可见 Organization、Reorganization、Reporting、Reports 等),选 Organization 下的 Edit Staffing Model。
  • 讲师问答:上级是 Position Management,下级仍可设成 Job Management——模型可上下不同。

"supervisory organization is position management can you have subordinate as job management yes you could so if you're at the Staffing model you can see you are on position you can switch it to job"— 上级监督型组织是 Position Management,下级能不能是 Job Management?可以。到 Staffing Model 这里能看到当前是 Position,可以把它切换成 Job。

44:45

Job 模型灵活求快

Job 模型灵活求快
  • 幻灯片:Allows for most flexibility and speed——管控弱于 Position,但招聘更快。
  • Hiring restrictions at Org level:招聘限制设在组织层,不是逐个职位。
  • No quantity is defined for the number of jobs:不定义可招聘人数,省掉「先建 N 个职位」这一步。
  • A position no longer exists after a worker is transferred, demoted, promoted or terminated, unless it is moved with the employee——人走了岗位即消失,除非随人一起转移。

"position management we learned it allows for the maximum control now job management allows for most flexibility and speed the hiring restriction is at the organization level"— Position Management 我们讲过它控制最大;Job Management 则主打灵活和速度,招聘限制设在组织这一层。

46:45

招聘限制:限谁、在哪、什么身份

招聘限制:限谁、在哪、什么身份
  • 幻灯片定义:Hiring restrictions 规定 Position 或 Job Management 组织里的规则和条件,用来限制谁能被招进这个组织。
  • 可限制的维度(Restrictions are on):一个或多个 job families、job profiles、locations;Worker Type(emp 或 Contingent);Worker Sub Type;Time Type(full 或 part);也可选 No restrictions。
  • 讲师举例:为旧金山的行政助理建职位却不加地点限制,就可能把人招到 Boston,出问题——所以限制很重要。

"hiring restrictions are that they Define the rules and conditions in a position or job management org and allow you to limit or restrict who is hired into an organization"— 招聘限制规定了 Position 或 Job Management 组织里的规则和条件,让你可以限制谁能被招进这个组织。

48:45

配置模型何时还能改

配置模型何时还能改
  • 幻灯片:Staffing Model 可在建组织时指定,也可建后用独立任务 Edit Staffing Model 修改。
  • 关键限制:一旦建了职位(Position Management)或设了招聘限制(Job Management),Edit Staffing Model 任务就不再可用。
  • 页面把导航写死了:Wealth Of Knowledge → Related Actions → Organizations → Edit Staffing Model。
  • 底部 Demo 行:Set Staffing Models to Training and Course Development Orgs。

"once the position has been created or hiring restrictions have been set the edit Staffing model task is no longer available"— 一旦创建了职位或设置了招聘限制,Edit Staffing Model(编辑人员配置模型)任务就不可用了。

52:45

配置模型报表批量查看

配置模型报表批量查看
  • 顶部说明:用勾选框编辑某监督型组织的 staffing model;若全选组织,一次只能编辑 100 个(共 57 items)。
  • 表头暴露了三种 staffing model 开关:Position Management Enabled、Headcount Management Enabled、Job Management Enabled——说明系统里除 Position/Job 外还有 Headcount 模型。
  • 多数组织勾选 Position Management Enabled;例中「Global Modern Services >> LinkedIn AM Department」勾的是 Job Management Enabled。
  • 列表还包含 Course Development、Learning and Development、Ricky_11_7 Department 等组织。

"there is a task called maintain Staffing models it allows you to view all supervisory orgs that have these Staffing model selected but do not yet have any positions or jobs created"— 有一个叫 Maintain Staffing Models 的任务,它能让你查看所有已选了这类配置模型、但还没创建任何职位或岗位的组织。

53:15

筛选自己新建的组织来翻牌

筛选自己新建的组织来翻牌
  • 在 Organization 搜索框输入「Ricky」,弹出 3 Results:Ricky_11_7、Ricky_JobMgmt、Ricky_PosMgmt Department(均属 Global Modern Services)。
  • 用 Filter 缩小范围后,可在同一张报表里直接翻 Position / Job Management Enabled 勾选来改模型。
  • 前提仍是这些组织没建职位、没设招聘限制,才会出现在这个可编辑列表里。

"and I can just flip them right here job management enabled a position management enabled and you can actually change them right here if you want to switch"— 我就能在这里直接翻牌——Job Management 启用、Position Management 启用——想切换的话就在这儿改。

55:15

课堂小测:五道概念题

课堂小测:五道概念题
  • 题1 控制最强的是哪个模型、题2 最灵活的是哪个(讲师答:Position 控制最强,Job 最灵活)。
  • 题3 判断题「配置模型部署后可随时更改」——答案为 False。
  • 题4 Job Management 下招聘限制设在哪一层(答:组织层 Org level)。
  • 题5 哪个模型要求必须先有空职位才能招/签/转(答:Position Management)。

"Staffing models can be changed at any time following deployment false why because they can only be changed anytime following deployment if we have not created any position or set any hiring restrictions"— 「配置模型部署后可随时更改」——错。原因是只有在你还没创建职位、也没设置招聘限制时,才能改。

59:15

职务画像是岗位地基

职务画像是岗位地基
  • 幻灯片:Positions and Jobs use Job Profiles as their foundation——职位与岗位都以职务画像为基础。
  • 用途:Enables to describe general characteristics of a job or a position(技能、培训、资质等一般特征)。
  • 关系:Can be assigned to multiple positions or workers;可 1:1(如 CEO),也可 1:many(如 Executive Assistant)。
  • 讲师强调:Job Profile 非强制,不挂也能建职位;挂了则能自动带出大量字段,让招聘更省力。

"positions and jobs they both use job profiles as their Foundation the job profile is something it's great to have but it's not mandatory"— 职位和岗位都以职务画像为基础;有 Job Profile 很好,但它不是强制的。

1:01:15

创建画像字段全景

创建画像字段全景
  • 左侧 Profile Details:Effective Date、Job Profile Name*、Job Code、Include Job Code in Name、Job Title Default、Restrict to Country、Management Level、Job Level、Job Family、Job Category、Company Insider Type、Referral Payment Plan、Work Shift Required、Inactive。
  • 右侧 Job Classification 区:Job Classifications、Job Profile Summary、Job Description、Additional Job Description(富文本编辑器)。
  • 本例按 lab 给定值填写,Job Profile Name 已填「Manager, Training」。
  • Pay Rate Types 在本屏之下,要向下滚动才露出来;讲师随后为 UK 和 US 各加一行(UK 选 Salaried)

"give it the job profiler name let's call it as manager training and job code I'm going to call it as ABC and in this case the management level I'm going to say our manager"— 给它起个 Job Profile Name,就叫 Manager Training;Job Code 用 ABC;Management Level 这里选 Manager。

1:01:45

填入编码、层级与职务族

填入编码、层级与职务族
  • Job Code = ABC;Management Level 选到「6 Manager」;Job Family 选「HR-Training」。
  • 讲师说明:Pay Rate Type(salary / daily / hourly 等)是 Workday 自带的;而本例的 HR-Training job family 是培训租户建的,你也可用 Create Job 自建。
  • 屏幕底部状态栏显示所选 job family「HR-Training - 260S60」。
  • Pay Rate Types 此处仍 0 items,UK/US 两条留到往下滚再填。

"just like a job profile you can also have job families yeah there's one here so the job family is there and then pay rate type scroll down you will see the pay rate type and you're going to provide two values one for UK and one for us"— 跟 Job Profile 一样你也可以有 Job Family,这里有一个……选好 Job Family,往下滚到 Pay Rate Type,要给两个值:UK 一个、US 一个。

1:03:45

职务分类、描述与薪资类别

职务分类、描述与薪资类别
  • Job Classifications 已加两条:1135 - Personnel, training and industrial relations managers(British Standard Occupational Classification (SOC)-United Kingdom);1.2 - First/Mid-Level Officials and Managers(United States EEO-1- United States of America)。
  • Job Description 填「Something about the job」。
  • 下方 Pay Rate Types 已加到 2 items,列为 Country 与 Pay Rate Type(UK、US 各一条,值为 salary)。
  • 这些分类/薪资值实际工作中会由组织提供给你,本例是演示租户预置的。

"the pay rate type is provided to you by workday and then you provide the job description and the job description you can say something about the job"— Pay Rate Type 由 Workday 提供给你;然后你填 Job Description,可以随便对这份工作写点什么。

1:04:15

特征、薪酬、工会与教育页签

特征、薪酬、工会与教育页签
  • 本屏是表单更下方的分区:Characteristics(Difficulty to Fill、Critical Job)、Compensation(Compensation Grade、Compensation Grade Profile、Impacted Eligibility Rules)、Unions(Union Membership)。
  • 底部一整排页签:Job Exempt、Worker's Compensation Codes、Certifications、Competencies、Education、Languages、Responsibilities、Skills、Training、Work Experience。
  • 当前停在 Education 页签(1 item,列为 Required / Degree / Field of Study),演示在此填学历要求(Bachelor of Arts)。
  • 讲师提示:本例 compensation 先不填,之后讲到薪酬再回头补这个 Job Profile。

"go to the education Tab and for the education tab you would say the requirement for this is let's say it's Bachelor of Arts there's a job exempt there's a worker compensation code and there is education and we hit done"— 切到 Education 页签,把这岗位的学历要求填成 Bachelor of Arts;还有 Job Exempt、Worker Compensation Code、Education,然后点 Done。

1:04:45

画像创建后的汇总页

画像创建后的汇总页
  • 汇总显示:Job Profile Name = Manager, Training_Ricky(加人名后缀避免与他人重名)、Job Code = ABC、Management Level = 6 Manager、Job Family = HR-Training。
  • Effective Date 与 Date of Last Change 均为 11/07/2020(后者带时间戳 07:14:58.968 AM)。
  • 右侧列出 Job Classifications(US EEO-1 1.2 / UK SOC 1135)、Job Description「Something about the job」、Pay Rate Types 2 items。
  • 关键:此刻只是把画像建好、还没在任何职位上引用它,建职位时再引用。

"what we have done is we have created a job profile not referencing it anywhere but we have a job profile now and we will revisit this"— 我们做的事是建好了一个 Job Profile,还没在任何地方引用它,但现在它已经存在,之后会再回来用它。

1:05:45

三级职务分类层级

三级职务分类层级
  • 幻灯片用三个方框表示自上而下的层级:Job Family Group → Job Family → Job Profile。
  • 讲师举例:Job Family Group = Human Resources;下面 job families 有 HRIS、Benefits;HRIS 下 job profiles 有 HRIS Specialist、HRIS Analyst。
  • 再往下才是 Positions:HRIS Specialist-1 与该画像 1:1;HRIS Analyst-1、Analyst-2 共用一个画像 → 1:many。
  • 本课目前只处理 Job Profile 这一层,暂不展开 job family group / job family 的配置。

"the job family group is human resources it has job families like hris and benefits and the hris has the job profiles of hris specialist and hris analyst"— Job Family Group 是 Human Resources,下面有像 HRIS、Benefits 这样的 job families,而 HRIS 下又有 HRIS Specialist、HRIS Analyst 这些 job profiles。

1:07:15

职位不是孤儿实体

职位不是孤儿实体
  • 幻灯片:Position is created with the context of a supervisory Org——职位必须挂在某个监督型组织下,不是孤儿实体。
  • 用 Position Staffing Model 时,staffing 前必须先有一个 Open Position 可用(培训里很多人卡在这一步)。
  • Task 名为 Create Position;它背后同样有 business process 卡审批,防止有人一口气建 100 个职位。
  • Few mandatory fields(幻灯片列出):Posting Title、the number of positions、Availability Date、Earliest Hire Date。

"when a position is created in workday it is built within the context of a supervisory organization so what that means is a position is not an orphan entity in workday it has to be tied to a supervisory Arc"— 在 Workday 里创建职位时,它是建在某个监督型组织的上下文里的,也就是说职位不是孤儿实体,它必须绑到一个监督型组织。

1:11:00

两个日期决定成败

两个日期决定成败
  • Create Position 的 Hiring Restrictions 页:Number of Positions* = 1,Availability Date* 与 Earliest Hire Date* 均为必填(红*)。
  • 可选限制字段:No Job Restrictions、Job Family、Job Profiles for Job Family、Job Profile、Job Description Summary / Job Description、Location、Time Type、Worker Type、Worker Sub-Type。
  • 讲师重点:整个 Workday 认证实验的判分就压在这两个日期上——Availability Date(职位何时可用)与 Earliest Hire Date(最早哪天能入职),别填错。
  • 底部按钮:Submit / Save for Later / Cancel。

"these dates are very important the whole workday certification exam the actual lab on which you are graded is based on these two dates availability date and higher date"— 这两个日期非常重要——整个 Workday 认证考试的实操实验判分,就基于 Availability Date 和 Hire Date 这两个日期。(字幕把 hire date 误识为 higher date)

1:13:15

引用画像自动带出资质

引用画像自动带出资质
  • 本职位挂在 Supervisory Organization = Ricky_PosMgmt Department,Job Posting Title = Training Manager,Position Request Reason = Create Position > Position Request > Staff New Project。
  • Qualifications 页显示「Qualifications from Job Profile:Education: B.A.」,Education 区自动出现 1 item(Degree = B.A.)——画像里填的学历被带进来了。
  • 讲师解释:手动填学历很麻烦,聪明做法是引用 Job Profile;画像越丰富,建职位时要手填的越少。
  • Skills、Languages 此时仍 0 items / No Data(画像里没配就带不出)。

"we will search for what was it called manager training you can see the job description and if you go to the qualifications you will see the education qualification of Bachelor and arts gets populated"— 我们去搜那个叫 Manager Training 的画像……可以看到 Job Description;再到 Qualifications,就能看到 Bachelor of Arts 这个学历要求被自动带出来了。

1:27:15

用默认用户建职位

用默认用户建职位
  • 因共享租户里 Logan 被移除了某些角色、建职位受阻,讲师改用登录默认用户 Ben Thomas,在 RCK Ricky_11_1(Betty Liu (On Leave) 21008)下建职位。
  • Job Posting Title 填「Training Manager,Ricky」,Number of Positions = 1,Availability Date = 07/11/2020,Earliest Hire Date 留空(它是必填)。
  • 问答:职位建好后可编辑;要「复制」多个同类职位,其实是把 Number of Positions 一次填成比如 5,建出后再逐个改。
  • 引用画像可选:有 Training Manager 画像就引用,没有就直接勾 No Job Restrictions 提交。

"duplicating your position you could actually increase the number of positions if you like you could have like five positions they would all be called same and then you can modify them"— 要复制职位的话,你可以直接增加 Number of Positions,比如一次建 5 个、名字都一样,之后再逐个修改。

1:30:45

审批链:HR 伙伴后到经理

审批链:HR 伙伴后到经理
  • 提交后进入 Create Position 业务流,标题显示「Event skipped / Assign Organizations: Create Position: Training Manager,Ricky」,HR 伙伴那一步被跳过。
  • Up Next 交给 Betty Liu (On Leave)(21008),任务名「Create Position: Training Manager,Ricky - Approval by Manager」,Due Date 09/11/2020。
  • 讲师强调:审批步骤纯由 business process 决定,得清楚每一步该谁批。
  • Related Links 有 Business Policy Document;下方 Details and Process 可展开看流转。

"as you can see there are steps involved in doing this right so it went to the HR partner which was Logan and then it's going to the manager for approval which is Betty Liu"— 可以看到这中间有若干步骤:先到了 HR 伙伴(是 Logan),接着交给经理审批(是 Betty Liu)。

1:34:15

结课要点与两个提醒

结课要点与两个提醒
  • 组织 RCK Ricky_11_1(Betty Liu (On Leave) 21008),Superior 为 Executive Management Group(Steve Mor, 21002),Organization ID = SUPERVISORY_ORGANIZATION-6-7526。
  • 虽然已有职位,但 Members 仍 0 items——职位不等于成员,最终目标仍是把人招进来。
  • 提醒一:一旦建了职位,就不能再改该组织的 Staffing Model(与 00:48:45 的规则呼应)。
  • 提醒二:要改或加职位的招聘限制,进该职位后用 Related Actions 菜单里的 Edit Position Restrictions。

"now when we have created the position we cannot change the Staffing model correct because you have created a position you cannot edit the Staffing model anymore"— 现在我们已经建了职位,就不能再改人员配置模型了对吧——因为建了职位,你就不能再编辑 Staffing Model 了。