# UKG Kronos Workforce Central Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/ukg-kronos-wfc-private-ai-layer-blueprint-generator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill in your Kronos WFC environment and export an architecture plan for a private, on-prem AI assistant: components, security controls, rollout and open questions.

## Category

on-prem-ai

## Erp

UKG Kronos Workforce Central

## Audience

- CIO
- IT architect
- Security officer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### System version

**Key:** version

**Type:** select

**Options:**

- Workforce Central 7.x
- Workforce Central 8.0
- Workforce Central 8.1

**Default:** Workforce Central 8.0

#### Database engine

**Key:** db

**Type:** select

**Options:**

- SQL Server
- Oracle Database

**Default:** SQL Server

#### Hosting

**Key:** hosting

**Type:** select

**Options:**

- On-prem server
- Private cloud
- Air-gapped

**Default:** On-prem server

#### Named users

**Key:** users

**Type:** number

**Default:** 600

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 3

#### Main use cases

**Key:** usecases

**Type:** textarea

**Default:** Overtime and absence trends by department, schedule coverage gaps, timecard exception summaries for supervisors, questions about pay rules and union agreements.

#### Data that must never leave the site

**Key:** never

**Type:** textarea

**Default:** Biometric data, individual-level personal data outside the user's employee group, pay disputes and disciplinary files. Small groups must be suppressed.

#### GPU available

**Key:** gpu

**Type:** select

**Options:**

- No GPU yet (CPU only for pilot)
- 1 x 24 GB GPU
- 1 x 48 GB GPU
- 2 to 4 x 80 GB data-center GPUs
- 8 or more data-center GPUs

**Default:** 1 x 24 GB GPU

#### Target go-live

**Key:** golive

**Type:** text

**Default:** Pilot in 8 weeks, production in 6 months

**Blocks:**

#### Context

**Body:** Company: {{company}}
System: UKG Kronos Workforce Central, version {{version}}, database {{db}}
Hosting: {{hosting}}
Scale: {{users}} named users across {{sites}} sites
Target: {{golive}}

Goal: add a private AI assistant over the existing system without moving data to a public cloud service and without replacing the system.

#### Use cases in scope

**Body:** {{usecases}}

#### Data that must never leave the site

**Body:** {{never}}

Control: this data is excluded from the index or processed only on {{hosting}} infrastructure, with access logged.

#### Components

**Table:**

**Columns:**

- Component
- Design

**Rows:**

**0:** Data access path

**1:** Read-only replica or reporting database with named, reviewed views; WFC XML API and Integration Interface Manager for live reads

**0:** Retrieval index

**1:** Local index of pay rules, policies and union agreements; numeric questions go to the semantic layer

**0:** Model serving

**1:** Open-weight model on vLLM or Ollama on {{gpu}}

**0:** Tool server

**1:** MCP or HTTP server with parameterized tools such as get_overtime_summary; no free SQL

**0:** Identity and permissions

**1:** Function access profiles and employee groups mapped to the asking user; every query scoped to people they manage

**0:** Audit

**1:** Append-only log with query parameters and row counts; small-group suppression recorded

#### Security controls

**Body:** Aggregates and exceptions only; minimum group size suppression; no decisions about individuals; PII stays on-site; legal and works council review of use cases before go-live; replica credentials read-only.

Hosting mode {{hosting}}: when air-gapped, models, containers and packages enter through a hash-verified transfer and no component calls an external network.

#### Rollout

**Table:**

**Columns:**

- Phase
- Scope
- Exit criteria

**Rows:**

**0:** 1. Read-only questions

**1:** Cited answers over a pilot scope for a small user group on {{gpu}}

**2:** Answers verified by process owners; no permission leaks in tests

**0:** 2. Drafts

**1:** Summaries, comparisons and drafted records a person reviews and enters

**2:** Reviewers accept drafts without major edits in agreed share of cases

**0:** 3. Approved actions

**1:** Narrow actions through the supported API with a named human approver

**2:** Every action logged; rollback path tested; sign-off from system owner

#### Open questions for IT

**Body:** 1. Which Workforce Central version and data dictionary apply, and where is the reporting database?
2. Which access profiles and employee groups define manager scope?
3. What minimum group size will you suppress below?
4. Which countries, works councils or union agreements restrict use?
5. Is a move to a cloud timekeeping product planned, and when?

#### Approvals

**Signatures:**

- IT architect
- Security officer
- System owner

**Notes:** This is a planning document, not a security certification. Component choices (vector store, model size) depend on your pilot measurements; confirm API names and limits against the documentation for your exact version.

## Content

**Intro:** This generator turns a handful of facts about your UKG Kronos Workforce Central environment into a structured architecture plan for a private AI assistant. It covers the components, the security controls tied to your hosting choice, a three-phase rollout and the questions IT has to answer before build.

**Sections:**

#### How to use it

**Body:** Enter your system version, database engine and hosting model, then describe the use cases and the data that must never leave the site. The blueprint fills the context, components, controls and rollout sections, and exports to PDF, Word or Excel. Walk through it with your IT architect and security officer, correct the defaults, and attach it to the project request. Change the GPU field to see how the rollout row for phase one reads on different hardware.

**Bullets:**

- Be specific about restricted data: it becomes a design constraint, not a footnote
- Pick hosting first; it sets the security controls
- Keep use cases to three or four for the pilot
- List the people who can approve write-back

#### What the blueprint assumes

**Body:** The design is the same on every on-prem system: a read-only copy or supported API for data access, a retrieval index that carries permissions, a tool server that exposes only approved read actions, an open-weight model on vLLM or Ollama, and an audit log. Timekeeping users are managers and HR, so named users are low but data sensitivity is high. The components table names the access path for this system, but you must verify the object and API names for your exact version.

**Bullets:**

- Read-only by default
- Permissions mirrored from the system
- Write-back only through supported APIs with human approval
- Everything logged

#### Reading the rollout table

**Body:** Phase one proves the data and permissions work: cited answers over a small scope. Phase two adds drafts that a person reviews. Phase three allows narrow, approved actions through the system's own API. Do not skip phases: most failures come from skipping permission testing in phase one. Exit criteria are examples; replace them with numbers your process owners agree to, such as the share of answers verified correct in a sample of fifty questions.

#### Common mistakes

**Body:** Teams often size the model before they have defined the use case, grant the assistant a powerful service account, or index everything to avoid deciding scope. Another is leaving the open questions unanswered until build starts. Most load is numeric queries, not document retrieval. Use the open-questions section as the agenda for your first IT workshop and assign an owner to each item.

**Bullets:**

- Powerful service account for convenience
- No permission tests with restricted users
- Indexing without scope decisions
- No owner for open questions

**Cta:** Netray designs and runs private AI layers on UKG Kronos Workforce Central with your IT team. If you want a second opinion on your blueprint, we can review it with you.

**Faq:**

#### Does this document commit us to buying anything?

**Answer:** No. The generator runs in your browser and exports a plan you can share internally. It is a starting point for architecture and security review, and every default can be changed.

#### Is the plan valid for air-gapped sites?

**Answer:** Yes. Choose the air-gapped hosting option and the controls section adds transfer and network isolation rules. All components in the table run inside the closed network with no external calls.

#### Why does the plan avoid giving model sizes?

**Answer:** Model size and GPU count depend on concurrency, context length and answer quality targets. Measure them in the pilot, then use the sizing calculator for ranges rather than committing to a number early.

#### Can we reuse the plan for another system?

**Answer:** The structure transfers, but the data access path, permission model and open questions are specific to each system. Generate a separate blueprint for each platform and compare them.

## Search terms

kronos wfc ai architecture, kronos wfc private llm plan, on-prem ai blueprint template, air-gapped ai architecture document, private ai layer architecture template, ai assistant security controls template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json