跳转至

Phase 3: Roles and responsibilities（第三阶段：角色与职责）

The following are new roles and responsibilities for Phase 3 of the Foundry Program team, in addition to the roles established in Phase 1 and Phase 2.

Center of Excellence

Responsibilities

  • The Center of Excellence (CoE) is a rotation rather than a dedicated team; we recommend implementing a group of personnel available from the central Program who are available to fill gaps in knowledge, skill sets, or resourcing bandwidth in Foundry initiatives.
  • These resources embed deeply within the use cases in which they engage, though in most cases should not be a majority of the executional bandwidth on a given project.
  • It is critical that there is ownership by someone who is a long-term participant of the domain in which the use case is contributing; CoE resources are meant to be temporary resources deployed to boost an initiative and cannot be held responsible for long-term ownership.

Implementation examples

  • Embedding a data scientist to develop and deploy a model for a team that is working on a given workflow.
  • Embedding a pipeline expert to help construct an initial data pipeline or particularly difficult integration.
  • Providing a project manager to establish sustainable operational processes and project governance systems alongside a use case owner who will maintain ownership or investment of a given use case.

Roles

  • Project managers
  • Data engineers
  • Front-end developers
  • Data engineers / scientists

Relevant Foundry applications and resources

Dependent on the individual's area of expertise and the requirements of the use case into which they are deployed.

Agent Administrator

Responsibilities

  • Agent Administrators are responsible for the creation and configuration of Data Connection agents and for sharing them with relevant data source owners.
  • As a team, Agent Administrators should own the centralized control of agent installation and configuration that creates enhanced security and control within the Foundry Program.
  • Agent Administrators are often allocated to a specific organizations domain or geography, though the appropriate division of responsibilities will vary depending on organization structure and compliance requirements. We recommend ensuring that Agent Administrators are subject matter experts in the suite of data sources required for ingestion in their specific area.
  • Agent Administrators should work closely with Palantir teams to identify issues upstream and build business and Foundry context ahead of taking more ownership.
  • The Agent Administrators work closely with Data Owners who are the primary points of contact for individual source systems that are ingested for use in Foundry. Data Owners will work closely with Agent Administrators during the configuration of a new data connection, and Data Source Owners will assume responsibility for upstream issues according to agreed upon SLAs and terms.

Profile and required skills

  • Familiarity with agents / VMs / connecting systems
  • Specific technical knowledge of the organization's data sources, IT infrastructure, and internal access processes
  • Data engineering skills (SQL, Python, PySpark/Spark)

Relevant Foundry applications and resources

Head of Platform

Responsibilities

  • The Head of Platform is primarily responsible for data security and permission administration, along with Foundry governance, compliance, performance, and compute/storage cost allocation.
  • The Head of Platform should be a leader within the broader organization's IT space who can build out IT infrastructure for the Foundry Program and appropriately integrate it with holistic IT structures and processes.
  • Build out data security structures, including documentation and trainings on best practices and compliance protocols. This role will work closely with the Permissions Manager to drive requirements and a long-term vision around permission administration and data access controls within Foundry.
  • Over time, work with internal IT teams as well as the Permissions Manager, Head of Data Governance, and IT teams tangential to the Foundry Program to scope and implement the required organizational customization on Foundry to suit business needs. This will include building integration points with existing organization technology to streamline data flows, customizing resource profiles on the platform, and monitoring and managing cluster costs of Foundry.
  • Create comprehensive success metrics and a roadmap for the Platform team, in support of the Foundry Program strategy and growth roadmap. Drive reporting and monitoring on Platform KPIs and work with the Head of Program to socialize successes and regular reporting.

Profile and required skills

  • Experience in leading IT and platform teams
  • Experience building and maintaining relationships with the broader IT organization
  • Written and verbal communication skills
  • Experience partnering with senior leadership as a workstream owner
  • Knowledge of data security and permission administration best practices, in alignment with organizational and broader regulatory policies
  • Strong organizational and project management skills

Relevant Foundry applications and resources

IT Services Owner

Responsibilities

  • The IT Services Owner is responsible for Platform Architecture and cross-platform software integration, which includes how Foundry connects to others systems and how Foundry is positioned in the enterprise's IT ecosystem.
  • Alongside the Head of Technology, the IT Services Owner should create and manage custom configurations to ensure they are in line with company expectations or protocols. These may include Spark profiles, YARN configurations, and changes to Foundry applications.
  • Work with the Head of Platform to establish IT policies and systems in accordance with Program strategies and goals.
  • Collaborate with other teams within the Program to determine their IT needs.
  • Monitor, review, and enforce any upgrade or configuration changes across the platform, and communicate any changes required across workstreams.
  • Work with the Head of Platform to establish cost monitoring and reporting to ensure Foundry costs are transparent and managed.

Profile and required skills

  • Strong individual contributor with an IT background
  • Sound understanding of Foundry architecture
  • Experience in monitoring and controlling budgets for IT services
  • Cross-functional collaboration skills
  • Ability to build strong relationships with organization IT teams external to the Foundry Program

Relevant Foundry applications and resources

Permissions Manager

Responsibilities

  • Permissions Managers run the overall organization of groups within Foundry that dictates how Foundry access is provisioned to different types of users. This may entail integration with identity manager systems specific to the organization, or SAML integration.
  • Regular collaboration with the Head of Data Governance is required; this role should act as the execution layer at the junction of Platform implementation and Data Governance protocols, processes, and controls.
  • Permissions Managers should be subject matter experts on Data Governance requirements and familiar with the implementation-level requirements and data structures to best execute permissions across projects and workflows.
  • Own the overall organization of groups within Foundry, which dictate how Foundry access is provisioned to different types of users.
  • As the platform matures and use cases and the user base continues to expand, own the implementation of Restricted Views and permissions in close collaboration with the Technical Compliance Manager.

Profile and required skills

  • Ability to communicate between technical and non-technical stakeholders
  • Familiarity with organization-wide data access permissions, regulations, and authentication systems (Okta and Active Directory, for example)
  • Programming skills (SQL, Python, PySpark/Spark)
  • Knowledge of data governance best practices
  • Strong technical communicator
  • Knowledge of systems architecture

Relevant Foundry applications and resources

Technical Compliance Manager

Responsibilities

  • The Technical Compliance Manager is responsible for approving projects before development begins. This role is responsible for providing information about the platform to those who request new projects. Approvals should take into account the source data that needs to be leveraged, the purpose of the project, and the breakdown of users who require access to the data and configure permissions.
  • The Technical Compliance Manager role should be aligned with organization data protection policies, as well as broader regulatory regime in which the platform and specific project operate.
  • Additionally, this role ensures the implementation of Restricted Views and defines the standard structure per project type.
  • The Technical Compliance Manager will work closely with the Permissions Manager; at scale, this role may exist in an organization-level domain.

Profile and required skills

  • Familiarity with organization-wide data access permissions, regulations, and authentication systems (Okta and Active Directory, for example)
  • Strong understanding of Foundry permissions architecture
  • Background in implementation and/or policy making in data compliance, data regulation, and data privacy
  • Knowledge of programming practices (SQL, Python, PySpark/Spark)
  • Knowledge of data governance best practices and data protection policies and regulations
  • Strong technical communicator
  • Knowledge of systems architecture

Relevant Foundry applications and resources

Support Services

Responsibilities

  • Support Services are the support teams that handle Foundry questions and user-submitted issues regarding projects for which IT is directly responsible, as well as for general Foundry support and user development support.
  • The structure of this team benefits from flexibility; decisions can be made for what support should be developed internally (within the organization's teams), what should be provided by Palantir, and standard operating procedures to manage the end-to-end resolution of user support issues across both the customer and Palantir.
  • The ultimate goal of this team is to build autonomy; internal teams are enabled by an internal support team that deeply understands the organization's business, structures, workflows, and Foundry architecture. The ultimate goal of Support Services teams is to enable the organization's Foundry usage to scale beyond the use case teams' bandwidth and support capacities, and to build speed by reducing reliance on Palantir support services.
  • The Support Services team requires technical personnel who have a deep understanding of Spark and recognize programming antipatterns.

Profile and required skills

  • Understanding of both business workflows and technical structures and concepts within Foundry
  • Curiosity and strong investigative skills
  • Experience in building and using reporting and monitoring systems for support services
  • Strong written communication skills; should be tasked with contributing to documentation to support workflows and with communicating to development teams or to Palantir support teams when issues require escalation

Relevant Foundry applications and resources

  • Foundry Issues
  • Use Case-specific applications
  • Project-specific documentation

中文翻译

第三阶段：角色与职责

以下是Foundry项目团队在第三阶段新增的角色与职责，补充了第一阶段和第二阶段中已确立的角色。

卓越中心（Center of Excellence）

职责

  • 卓越中心（CoE）采用轮岗制而非固定团队；建议从中央项目中调配一组人员，用于填补Foundry项目在知识、技能或资源带宽方面的缺口。
  • 这些资源深度嵌入其所参与的用例中，但在大多数情况下不应占据某个项目执行带宽的大部分。
  • 关键在于，必须由用例所属领域的长期参与者担任负责人；CoE资源是用于推动项目的临时资源，不能承担长期所有权责任。

实施示例

  • 派驻数据科学家（Data Scientist）为正在处理特定工作流的团队开发和部署模型。
  • 派驻管道专家（Pipeline Expert）协助构建初始数据管道或处理特别复杂的集成工作。
  • 提供项目经理（Project Manager），与将保持所有权或持续投资的用例负责人一起，建立可持续的运营流程和项目治理体系。

角色

  • 项目经理（Project Managers）
  • 数据工程师（Data Engineers）
  • 前端开发人员（Front-end Developers）
  • 数据工程师/科学家（Data Engineers / Scientists）

相关Foundry应用与资源

取决于个人的专业领域以及所部署用例的需求。

代理管理员（Agent Administrator）

职责

  • 代理管理员（Agent Administrators）负责创建和配置数据连接代理（Data Connection agents），并与相关数据源所有者共享。
  • 作为团队，代理管理员应集中控制代理的安装和配置，从而在Foundry项目中增强安全性和管控能力。
  • 代理管理员通常分配到特定组织领域或地理区域，但具体职责划分将根据组织结构和合规要求而有所不同。建议确保代理管理员是其负责区域内所需数据源套件的主题专家（Subject Matter Experts）。
  • 代理管理员应与Palantir团队紧密合作，在承担更多所有权之前，识别上游问题并建立业务和Foundry上下文。
  • 代理管理员与数据所有者（Data Owners）密切合作，数据所有者是用于Foundry摄入的各个源系统的主要联系人。在配置新数据连接时，数据所有者将与代理管理员紧密协作；数据源所有者将根据约定的服务等级协议（SLA）和条款承担上游问题的责任。

画像与所需技能

  • 熟悉代理/虚拟机/系统连接
  • 具备组织数据源、IT基础设施和内部访问流程的具体技术知识
  • 数据工程技能（SQL、Python、PySpark/Spark）

相关Foundry应用与资源

平台负责人（Head of Platform）

职责

  • 平台负责人（Head of Platform）主要负责数据安全和权限管理，以及Foundry的治理、合规、性能以及计算/存储成本分配。
  • 平台负责人应是更广泛组织IT领域的领导者，能够为Foundry项目构建IT基础设施，并将其与整体IT结构和流程适当整合。
  • 构建数据安全结构，包括最佳实践和合规协议的文档与培训。此角色将与权限管理员（Permissions Manager）紧密合作，推动关于Foundry内权限管理和数据访问控制的长期愿景和需求。
  • 随着时间的推移，与内部IT团队以及权限管理员、数据治理负责人（Head of Data Governance）和与Foundry项目相关的IT团队合作，确定范围并在Foundry上实施所需的组织定制化，以满足业务需求。这包括构建与现有组织技术的集成点以简化数据流、定制平台上的资源配置文件，以及监控和管理Foundry的集群成本。
  • 为平台团队创建全面的成功指标和路线图，以支持Foundry项目战略和增长路线图。推动平台关键绩效指标（KPI）的报告和监控，并与项目负责人合作宣传成功案例和定期报告。

画像与所需技能

  • 领导IT和平台团队的经验
  • 建立和维护与更广泛IT组织关系的经验
  • 书面和口头沟通能力
  • 作为工作流负责人与高级领导层合作的经验
  • 了解数据安全和权限管理最佳实践，并与组织及更广泛的监管政策保持一致
  • 强大的组织和项目管理技能

相关Foundry应用与资源

IT服务负责人（IT Services Owner）

职责

  • IT服务负责人（IT Services Owner）负责平台架构（Platform Architecture）和跨平台软件集成，包括Foundry如何连接到其他系统，以及Foundry在企业IT生态系统中的定位。
  • 与技术负责人（Head of Technology）一起，IT服务负责人应创建和管理自定义配置，确保其符合公司期望或协议。这些配置可能包括Spark配置文件、YARN配置以及对Foundry应用的更改。
  • 与平台负责人合作，根据项目战略和目标建立IT策略和系统。
  • 与项目内的其他团队协作，确定其IT需求。
  • 监控、审查并执行平台上的任何升级或配置更改，并跨工作流沟通所需的任何更改。
  • 与平台负责人合作建立成本监控和报告机制，确保Foundry成本透明且可控。

画像与所需技能

  • 具有IT背景的强个人贡献者
  • 对Foundry架构有扎实的理解
  • 监控和控制IT服务预算的经验
  • 跨职能协作能力
  • 能够与Foundry项目外部的组织IT团队建立牢固关系

相关Foundry应用与资源

权限管理员（Permissions Manager）

职责

  • 权限管理员（Permissions Managers）负责管理Foundry内组的整体组织，这些组决定了如何向不同类型的用户授予Foundry访问权限。这可能涉及与组织特定的身份管理系统集成，或SAML集成。
  • 需要与数据治理负责人（Head of Data Governance）定期协作；此角色应在平台实施与数据治理协议、流程和控制的交汇点充当执行层。
  • 权限管理员应是数据治理要求的主题专家，并熟悉实施层面的要求和数据结构，以便在项目和工作流中最佳地执行权限管理。
  • 负责管理Foundry内组的整体组织，这些组决定了如何向不同类型的用户授予Foundry访问权限。
  • 随着平台成熟以及用例和用户群的持续扩展，与技术合规经理（Technical Compliance Manager）紧密合作，负责受限视图（Restricted Views）和权限的实施。

画像与所需技能

  • 能够在技术和非技术利益相关者之间进行沟通
  • 熟悉组织范围的数据访问权限、法规和认证系统（例如Okta和Active Directory）
  • 编程技能（SQL、Python、PySpark/Spark）
  • 了解数据治理最佳实践
  • 强大的技术沟通能力
  • 了解系统架构

相关Foundry应用与资源

技术合规经理（Technical Compliance Manager）

职责

  • 技术合规经理（Technical Compliance Manager）负责在项目开发开始前进行审批。此角色负责向请求新项目的人员提供有关平台的信息。审批应考虑需要利用的源数据、项目目的、需要访问数据的用户细分，并配置权限。
  • 技术合规经理的角色应与组织数据保护政策以及平台和特定项目运营所处的更广泛监管制度保持一致。
  • 此外，此角色确保受限视图（Restricted Views）的实施，并为每种项目类型定义标准结构。
  • 技术合规经理将与权限管理员紧密合作；在规模扩大时，此角色可能存在于组织级别的领域中。

画像与所需技能

  • 熟悉组织范围的数据访问权限、法规和认证系统（例如Okta和Active Directory）
  • 对Foundry权限架构有深入理解
  • 在数据合规、数据监管和数据隐私方面的实施和/或政策制定背景
  • 了解编程实践（SQL、Python、PySpark/Spark）
  • 了解数据治理最佳实践以及数据保护政策和法规
  • 强大的技术沟通能力
  • 了解系统架构

相关Foundry应用与资源

支持服务（Support Services）

职责

  • 支持服务（Support Services）是处理Foundry问题和用户提交的工单的支持团队，涉及IT直接负责的项目，以及一般的Foundry支持和用户开发支持。
  • 该团队的结构受益于灵活性；可以决定哪些支持应在内部（组织团队内）开发，哪些应由Palantir提供，以及制定标准操作程序来管理跨客户和Palantir的用户支持问题的端到端解决。
  • 该团队的最终目标是建立自主性；内部团队由一个深入了解组织业务、结构、工作流和Foundry架构的内部支持团队赋能。支持服务团队的最终目标是使组织的Foundry使用能够扩展到用例团队的带宽和支持能力之外，并通过减少对Palantir支持服务的依赖来提高速度。
  • 支持服务团队需要具备深厚Spark知识并能识别编程反模式的技术人员。

画像与所需技能

  • 理解Foundry中的业务工作流以及技术结构和概念
  • 好奇心和强大的调查能力
  • 构建和使用支持服务报告与监控系统的经验
  • 强大的书面沟通能力；应负责为支持工作流撰写文档，并在需要升级问题时与开发团队或Palantir支持团队沟通

相关Foundry应用与资源

  • Foundry Issues
  • 特定用例应用
  • 项目特定文档