Implementation Framework Concepts

Library: Track & Trace Documentation Library
Document: Implementation Framework Concepts
Version: 1
Effective date: 04-Oct-2021

Contents

• 1 Framework Description
• 2 Document Objectives and Benefits
  • 2.1 Objectives
  • 2.2 Benefits
• 3 Definitions
• 4 Roles & Responsibilities
• 5 T&T Implementation Framework
  • 5.1 Documents
    • 5.1.1 Standards
    • 5.1.2 Checklists
    • 5.1.3 Questionnaire
    • 5.1.4 Implementation Procedures and Templates
  • 5.2 Application Process
  • 5.3 Process of Revisiting
    • 5.3.1 Document Dependency Linage
    • 5.3.2 Escalation of Framework Document Revisits
• 6 Document Control
  • 6.1 Contact Person
  • 6.2 Revision History
• 7 References

---

1 Framework Description

T&T Implementation Framework defines the documents and processes supporting the implementation of T&T requirements across the production and distribution pillars of JTI operations.

2 Document Objectives and Benefits

2.1 Objectives

Objectives of the framework document are:

• Define the set of documents supporting T&T implementation, their content, and purpose
• Define the process of initiation of T&T Implementation project involving framework documents

2.2 Benefits

The framework enables streamlined implementation of T&T requirements based on clear standards and processes.

3 Definitions

T&T Implementation Project

• The set of activities, which, once applied together and in the correct sequence, bring entities in scope to compliance with applicable T&T Regulation requirements.

Standard

• Definition of the state of the capabilities, processes, infrastructure, systems that must exist by the end of the T&T implementation project in the entity in scope. Standards are based on the best practices established in JTI to comply with T&T regulations in effect.

Questionnaire

• The set of predefined questions collects the facts about the scope and requirements of T&T Implementation. These facts are directly used in further stages of the Implementation project.

Checklist

• The set of predefined questions, which collects facts about the existing state of the entity in scope in correspondence to the given Standard. These facts, together with applicable Standards and Questionnaires determine the scope of work for Implementation projects.

Template

• The set of predetermined activities, document formats, or other project artifacts that, once being filled with the information derived from Standards, Questionnaires and Checklists produce final working documents for the implementation project.

Implementation Procedure

• The definition of practical steps, including Templates when applicable, that lead to the implementation of the component, defined in Standard.

4 Roles & Responsibilities

#	Activity	IT T&T	GSC CP	Entities
1	Define and maintain Framework	A / R	R	I
2	Apply the Framework in the T&T Implementation projects	R	A / R	R

5 T&T Implementation Framework

T&T Implementation framework consists of a set of documents and processes of their application as part of a T&T Implementation project.

The framework also defines the process of revisiting its parts in response to changing or extending requirements of T&T regulation or the introduction of new best practices.

5.1 Documents

5.1.1 Standards

T&T Capabilities

• The Standard presents the holistic view on the expected process capabilities, framed by enacted FCTC-based and known local regulations. Additionally, the document includes also JTI Voluntarity T&T reporting capabilities. The document will document required reporting requirements per regulation.
• The Standard is revisited in the event of a new major regulation introduction or change
• The Standard establishes the framed requirements for all other standards in this Framework. Therefore, changes to the document shall trigger a review of all other Standards of the Framework.

GSC Standard for Manufacturing Equipment and Setup

• The Standard defines components and equipment, including recommended models/vendors if applicable, required engineering setup
• The Standard will cover production and finished goods warehouse

GSC Standard for Manufacturing Processes

• The Standard defines required processes, labeling, registrations of finished goods, rework process, etc. This document only defines the nomenclature and top-level details of the processes – the actual processes definitions will be documented separately, unless already in place

IT Standard for Factory Infrastructure

• This document will define required networking, server equipment, hardware installations, etc. – on the production area, cabinets/computes, finished goods warehouse, cabinets/computes, server rooms, virtual infrastructure and servers, related to T&T

IT Standard for Factory Systems

• This document will define: required software components, overall topology, and connections, component purpose and installation type, per-line / per factory / .., top-level setup definition for each software component.
• The description should cover production, finished goods warehouse, SAP / local ERP;
• This document does not cover the capabilities of Corporate Repository

IT Standard for Distribution Systems

• This document will define required software components, overall topology, and connections, component purpose and installation type, per-location, cloud, SaaS, top-level setup definition for each software component, when relevant. The description should cover market warehouses, JTI-owned, 3PL, Distributors, SAP / local ERP;
• This document does not cover the capabilities of Corporate Repository

5.1.2 Checklists

The framework defines the following checklists, in relation to Standards:

• GSC Standard for Manufacturing equipment and setup – Checklist
• GSC Standard for Manufacturing processes – Checklist
• IT Standard for Factory infrastructure – Checklist
• IT Standard for Factory systems – Checklist
• IT Standard for Distribution systems – Checklist

5.1.3 Questionnaire

The framework introduces the T&T Implementation Questionnaire which will be filled per impacted entity, by type of entity. It covers:

• Market-specific requirements
  • Applicable regulation by Material Group
  • Supply chain details, market
  • Warehouse-specific requirements, to be filled for each market WH in the market supply chain
  • SAP Impact
  • Infrastructure Impact
• Factory-specific requirements, to be filled for each Factory identified in the market supply chain
  • Applicable regulation by Material Group
  • Supply chain details, factories
  • Warehouse-specific requirements
  • SAP Impact
  • Infrastructure Impact

5.1.4 Implementation Procedures and Templates

The framework contains the following Implementation procedures and Templates:

• INEXTO Liz Implementation procedure
• INEXTO Gate Implementation procedure
• INEXTO Vault Implementation procedure
• FC TPM Implementation procedure
• GLA implementation procedure
• Movilizer implementation procedure
• WMS / MOM Integration procedure
• JTI Corporate Repository master data maintenance procedure
• JTI Corporate Repository Compliance Module Implementation procedure

5.2 Application Process

The framework defines the process, involving defined documents. The information flow is presented on the diagram below.

Diagram elements

Factory inputs and standards

• F-6D. Factory Implementation team capabilities
• F-5T. Template project plan: Factory Implementation
• F-4D. Factory IT standards
• F-3D. Factory GSC standards
• F-2T. Factory As-Is Checklist
• F-1T. Factory Implementation Questionnaire

Factory processes and activities

• Adjust template plan
• Factory fit-gap

Market inputs and standards

• M-1T. Market Implementation Questionnaire
• M-2T. Market Warehouse As-Is Checklist
• M-3D. Market IT standards
• M-4T. Template project plan: Market Implementation
• M-5D. Market Implementation team capabilities

Market processes and activities

• Market fit-gap
• Adjust template plan

Output documents

• D1. Factory Implementation project plan
• D2. Market Implementation project plan
• D3. Test plan - Production
• D4. Test plan - Market
• D5. Project charter / Blueprint
• D6. Market Change Management plan
• D7. Factory Change Management plan
• D8. Risk register

Connector annotations

• Market supply chain dependencies
• Target scope
• Deliverables: Production
• Deliverables: Market

Factory-side information flow

F-5T. Template project plan: Factory Implementation
  → Adjust template plan

F-4D. Factory IT standards
  → Factory fit-gap

F-3D. Factory GSC standards
  → Factory fit-gap

F-2T. Factory As-Is Checklist
  → Factory fit-gap

F-1T. Factory Implementation Questionnaire
  → Factory fit-gap

Factory fit-gap
  → Adjust template plan

Adjust template plan
  → D1. Factory Implementation project plan
  → D7. Factory Change Management plan

Factory fit-gap
  → D3. Test plan - Production
  → Deliverables: Production
  → D5. Project charter / Blueprint

D1. Factory Implementation project plan
  → D7. Factory Change Management plan
  → D5. Project charter / Blueprint

D7. Factory Change Management plan
  → D5. Project charter / Blueprint

D3. Test plan - Production
  → D5. Project charter / Blueprint

D8. Risk register
  → D5. Project charter / Blueprint

Market-side information flow

M-1T. Market Implementation Questionnaire
  → Market fit-gap

M-2T. Market Warehouse As-Is Checklist
  → Market fit-gap

M-3D. Market IT standards
  → Market fit-gap

M-4T. Template project plan: Market Implementation
  → Adjust template plan

M-5D. Market Implementation team capabilities
  → Market planning flow

Market fit-gap
  → Adjust template plan
  → D4. Test plan - Market
  → D6. Market Change Management plan
  → Deliverables: Market
  → D5. Project charter / Blueprint

Adjust template plan
  → D2. Market Implementation project plan

D2. Market Implementation project plan
  → D6. Market Change Management plan
  → D5. Project charter / Blueprint

D6. Market Change Management plan
  → D5. Project charter / Blueprint

D4. Test plan - Market
  → D5. Project charter / Blueprint

Shared information flow

• The Target scope route connects fit-gap output to the implementation-document flow, including:
  • D3. Test plan - Production
  • D4. Test plan - Market
  • D8. Risk register
  • D5. Project charter / Blueprint
• The line labelled Deliverables: Production terminates at D5. Project charter / Blueprint
• The line labelled Deliverables: Market terminates at D5. Project charter / Blueprint
• Several dependency lines from capability and standards inputs feed downstream planning and change-management outputs

Diagram preservation note: Some connectors overlap or cross without visible junction markers. The exact direct destinations of F-6D, M-5D, and some shared Target scope lines cannot be determined with complete certainty from the source image. They are therefore not inferred beyond what is visibly supported.

Diagram legend

Colour	Meaning
Yellow	Input for project
Blue	Standards
Orange	Process / activity
Green	Output documents

Application process description

1. Completed Questionnaires, along with Checklists and Standards are used as input to the fit-gap process.
2. Fit-gap process delivers the scope of Implementation Project deliverables
3. Implementation Project deliverables are defined as the need to implement or get to the level of the standard T&T component
4. Identified components delivery are performed based on define Implementation Procedures documents, involving preparation of project plans and configuration templates.
5. Complete scope of documents from Implementation Procedures contribute to project documentation and define Implementation Project scope.
6. Delivery of the Implementation Project scope is subject to standard Project Management practices and out of the scope of this Framework.

5.3 Process of Revisiting

Content of the framework documents is built based on each other requirements. Therefore, the modification of each document will require a revisit of all correlated and dependent documents.

5.3.1 Document Dependency Linage

The linage of the documents’ dependencies is presented in the diagram below.

Source spelling note: The source uses Linage and linage. These terms are preserved rather than silently changed to Lineage.

Diagram labels

• Standard
• Checklist
• Implementation Procedure
• Questionnaire
• Fit-Gap process

Numbered dependencies

#	From	To
1	Standard	Checklist
2	Standard	Implementation Procedure
3	Standard	Questionnaire
4	Implementation Procedure	Questionnaire
5	Standard	Fit-Gap process
6	Checklist	Fit-Gap process
7	Questionnaire	Fit-Gap process
8	Questionnaire	Standard

Dependency flow

                         ┌───────────────────────────┐
                         │             8             │
                         │                           │
                         ▼                           │
Standard ──1──→ Checklist                            │
    │              │                                │
    │              └──6──→ Fit-Gap process          │
    │                        ▲                       │
    ├──2──→ Implementation   │                       │
    │        Procedure       │                       │
    │             │          │                       │
    │             └──4──→ Questionnaire ──7─────────┘
    │                         ▲
    ├──3──────────────────────┘
    │
    └──5──────────────→ Fit-Gap process

Numbered explanations

1. Update of Standard will trigger revisit respective Checklists
2. Update of Standard will trigger revisit or creation Implementation Procedures, related to components of the Standard, process, infrastructure, system
3. Update of the Standard will trigger the Questionnaire. Adding new alternatives into Standard will contribute to the change of options and questions in the Questionnaire.
4. Change or creation of Implementation Procedures will trigger changes of Questionnaire – to ensure that all information for Implementation Procedure is available.
5. Update of the Standard will trigger revisit of associated Fit-Gap process to cover potential changes of analyses from “To-Be” side.
6. Update of the Checklists will trigger revisit of associated Fit-Gap process to cover potential changes of analyses from “As-Is” side
7. Update of the Questionnaire will trigger revisit of associated Fit-Gap process to cover potential changes of analyses from “To-Be” side.
8. Any change of Questionnaire triggered specifically by detection of new requirements from the new T&T Implementation, will trigger revisit of Standards

5.3.2 Escalation of Framework Document Revisits

Once a document is updated, the document maintainer will inform the responsible person for related impacted documents to trigger the revisit and implementing updates if required.

6 Document Control

6.1 Contact Person

07/25: Questions and feedback regarding this standard should be submitted to Ioana Petcu.

6.2 Revision History

Version	Effective date	Purpose of change	Author
1	04-Oct-2021	First version of the document	Sergey Khitrin

7 References

• IMP000 - T&T Capabilities Standard
• IMP001 - GSC Standard for Manufacturing equipment and setup
• IMP002 - GSC Standard for Manufacturing processes
• SYS001 - IT Standard for Factory infrastructure
• IMP004 - IT Standard for Factory systems
• IMP007 - IT Standard for Distribution systems