跳转到内容

PHITE EPC Operating System

业务架构 · Foundation 标准 · 决策记忆 · 实施地图
ReleaseV1.1 Bilingual
Handbook 状态Draft
ERP 证据Frozen V1 subset
VerificationPartial

PHITE OS · PROJECT CONTROL

开发项目状态

所有数字均由 Work Registry 与既有 canonical 页面在构建时派生。

打开 Workboard →
Foundations
12
Active Workstreams
3
Active Work Items
0
关联 Open Decisions
8
Blocked Items
2
Verification Gaps
4

Foundation Portfolio Health

FoundationRulesDataERPUIVerify
EnterprisePartial: Frozen identity, audit, relation, deletion, numbering rulesPartial: Frozen shared masters and technical layersPartial: ImplementedUnknownPartial: Verified metadata scope
ProjectPartial: Frozen Project/contract and issue/status rulesPartial: Frozen Project, assignment, milestone, action, issue, change structuresPartial: ImplementedUnknownPartial: Verified metadata scope
DesignPartial: Frozen deliverable/version/review and document separationPartial: Frozen engineering deliverable, review, change, confirmation structuresPartial: ImplementedUnknownPartial: Verified metadata scope
ProcurementPartial: Frozen sourcing/allocation/version/numbering rulesPartial: Frozen requisition through receipt and supplier issue structuresPartial: ImplementedUnknownPartial: Verified metadata scope
Document ControlPartial: Frozen document/version/attachment/file/evidence separationPartial: Frozen controlled-document and evidence structuresPartial: ImplementedUnknownPartial: Verified metadata scope
Cost ControlUnknownUnknownUnknownUnknownNot Verified
Engineering ChangePartial: Frozen change records; impact workflow OpenPartial: Frozen `project_changes` and `engineering_changes`Partial: ImplementedUnknownPartial: Verified metadata scope
QualityUnknownUnknown beyond generic evidence and selected receipt/issue/test factsUnknownUnknownNot Verified as a Quality Foundation
Construction & CommissioningPartial: Frozen site/commissioning/test/acceptance/warranty/service rulesPartial: Frozen site-to-service structuresPartial: ImplementedUnknownPartial: Verified metadata scope
CommercialPartial: Frozen opportunity/proposal/quotation/contract rulesPartial: Frozen sales and contract structuresPartial: ImplementedUnknownPartial: Verified metadata scope
Planning & ControlsUnknownUnknown beyond milestones/actions/status factsUnknownUnknownNot Verified as a Controls Foundation
KnowledgeDraft content and retrieval principlesDraft frontmatter/manifest modelNot ImplementedHandbook UI implemented; enterprise knowledge UI UnknownHandbook build verification only

阅读规则: 页面存在不等于业务成熟。只有 Source Inventory 提供证据时,内容才可标为 Frozen、Implemented 或 Verified;其他内容保持 Draft、Unknown、Open 或 Not Verified。

flowchart TB
    ENT[ENTERPRISE] --> PRJ[PROJECT]
    PRJ --> SCP[SCOPE / WBS]
    SCP --> DES[DESIGN]
    DES --> DOC[DOCUMENT CONTROL]
    DOC --> PROC[PROCUREMENT]
    PROC --> MFG[MANUFACTURING]
    MFG --> QLT[QUALITY]
    QLT --> LOG[LOGISTICS]
    LOG --> CON[CONSTRUCTION]
    CON --> COM[COMMISSIONING]
    COM --> HND[HANDOVER]

    COMM[COMMERCIAL] -. lifecycle control .-> PRJ
    PLAN[PLANNING & CONTROLS] -. lifecycle control .-> PRJ
    COST[COST CONTROL] -. lifecycle control .-> PRJ
    CHG[ENGINEERING CHANGE] -. impact control .-> DES
    KNW[KNOWLEDGE] -. context and learning .-> PRJ

该图是企业架构框架,不证明每个阶段都有已冻结的 PHITE workflow。详细 authority 边界见 EPC Operating System Architecture

8Draft · 有部分 Frozen / Implemented / Verified 证据
3Concept · Cost、Quality、Planning 关键模型仍待决定
1Knowledge · Handbook 架构已实现,企业 ingestion 未实施

完整逐项证据保留在 Evidence Maturity Matrix,Executive View 不替代详细矩阵。

OD-PRJ-001 · Scope 分解

确认 Scope、WBS、Work Package、Deliverable、责任边界与接口关系。 Open

OD-COST-001 · 成本控制模型

确认 cost code、baseline、commitment、actual/accrual、forecast、EAC 与 margin ownership。 Open

OD-CHG-001 · 变更治理

确认影响 owner 与 approval gates,不冻结缺乏证据的 workflow。 Open

OD-DOC-001 · 文档生命周期

确认 MDR、issue purpose、customer response、resubmission、as-built 与 handover。 Open

实施任何未确认 workflow 或 schema 前,请查阅 Global Open Decision Register

系统 回答的问题 Authority
Normative / Design Starlight Handbook PHITE 应如何运行? Foundation standards、rules、architecture、decisions
Operational NocoBase 与业务系统 当前正在发生什么? 实时项目与交易事实
Implementation GitHub 设计如何实现? Code、schema、tests、migration/deployment artifacts
Contextual GBrain、沟通与历史记录 为什么发生? Context、relationships、lessons;不自动成为 policy

Knowledge access ≠ execution authority。 检索不授予审批、财务、迁移、删除或规则修改权限。