OSI PI TO Tempo MES Integration Discovery Document

Client: [Client Name]
Date: [Date]
Prepared by: ApprenticeFS
Participants: [List attendees]

EXECUTIVE SUMMARY

This document captures the technical and business requirements for integrating OSI PI (AVEVA PI System) with Tempo MES. The information gathered will inform the integration architecture, project scope, timeline, and implementation approach.

1. CURRENT OSI PI INFRASTRUCTURE

1.1 System Configuration

What version of OSI PI (AVEVA PI System) are you currently running?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

How many PI servers (DA and AF) do you have, and what's the architecture (centralized vs distributed)?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

1.3 System Ownership

Who currently manages your PI system (IT, automation team, operations, etc.)?
Response: ______________________________________________________________________
Primary Contact: ________________________________________________________________
Notes: ________________________________________________________________________

2. DATA SCOPE & REQUIREMENTS

2.1 Equipment & Data Points

Which equipment/production lines need to connect to Tempo MES through PI?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

What specific data points (tags) need to flow to Tempo (process values, alarms, events)?
Response: ______________________________________________________________________
Estimated tag count: ____________________________________________________________
Notes: ________________________________________________________________________

2.2 Data Flow & Frequency

Are there specific process parameters critical for batch records or genealogy tracking?
Response: ______________________________________________________________________
Examples: ______________________________________________________________________
Notes: ________________________________________________________________________

2.3 Bidirectional Communication

Do you need bidirectional data flow (writing setpoints or commands back to PI)?
Response: ______________________________________________________________________
Use cases: _____________________________________________________________________
Notes: ________________________________________________________________________

3. INTEGRATION ARCHITECTURE

3.2 Network & Security

Are there network segmentation or firewall considerations between where the PI Web API resides and Tempo?
Response: ______________________________________________________________________
Network diagram available: [ ] Yes [ ] No
Notes: ________________________________________________________________________

3.3 Additional Systems

Do you have OPC UA servers configured in addition to PI?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

Are there other systems (LIMS, ERP, DeltaV) that also interface with PI?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

4. USE CASES & BUSINESS OBJECTIVES

4.1 Primary Drivers

What's the primary driver for this integration?
[ ] Real-time process monitoring
[ ] Automated batch record generation
[ ] Advanced analytics and trending
[ ] Regulatory compliance documentation
[ ] OEE calculations
[ ] Other: _____________________________________________________________________

4.2 Tempo MES Integration

Will PI data support Config Lock/PQ execution scenarios in Tempo?
Response: ______________________________________________________________________
Notes: ________________________________________________________________________

Do you need PI data for OEE calculations, genealogy, or compliance documentation?
Response: ______________________________________________________________________
Specific requirements: __________________________________________________________
Notes: ________________________________________________________________________

4.4 Regulatory Requirements

Are there specific regulatory requirements driving real-time data capture (PAT, CPV, continuous verification)?
Response: ______________________________________________________________________
Regulatory framework: [ ] FDA [ ] EMA [ ] Other: ___________________________
Notes: ________________________________________________________________________

5. DATA GOVERNANCE & COMPLIANCE

5.1 Data Retention

What's your data retention policy for PI data vs Tempo batch records?
PI retention: __________________________________________________________________
Tempo retention: _______________________________________________________________
Notes: ________________________________________________________________________

6.3 Environment Strategy

What's your planned approach for development, test, and production environments?
Development: ___________________________________________________________________
Test/Validation: _______________________________________________________________
Production: ____________________________________________________________________
Notes: ________________________________________________________________________

6.4 Data Standards

Do you have documented PI tag naming conventions and standards?
Response: ______________________________________________________________________
Documentation available: [ ] Yes [ ] No
Notes: ________________________________________________________________________

7. PROJECT LOGISTICS

7.1 Resources & Governance

Do you have dedicated resources for PI system configuration support?
Name/Role: _____________________________________________________________________
Availability: __________________________________________________________________
Notes: ________________________________________________________________________

What's your change control process for PI system modifications?
Response: ______________________________________________________________________
Approval timeline: _____________________________________________________________
Notes: ________________________________________________________________________

7.2 System Changes

Are there planned PI upgrades that could impact the integration timeline?
Response: ______________________________________________________________________
Planned date: __________________________________________________________________
Notes: ________________________________________________________________________

7.3 Stakeholder Alignment

Who are the key stakeholders from both the PI and MES sides?

PI System:
Name: ________________________________ Role: __________________________________
Name: ________________________________ Role: __________________________________

MES/Operations:
Name: ________________________________ Role: __________________________________
Name: ________________________________ Role: __________________________________

IT/Infrastructure:
Name: ________________________________ Role: __________________________________
Name: ________________________________ Role: __________________________________

8. ADDITIONAL INFORMATION

8.1 Known Challenges or Constraints
Response: ______________________________________________________________________

Notes: ________________________________________________________________________

8.2 Integration Timeline Expectations
Target completion date: _________________________________________________________
Critical milestones: ____________________________________________________________

Notes: ________________________________________________________________________

8.3 Success Criteria
What would make this integration successful?
Response: ______________________________________________________________________

Notes: ________________________________________________________________________

9. NEXT STEPS

ACTION ITEMS:
[ ] Review and complete all sections of this discovery document
[ ] Obtain PI system architecture diagrams and documentation
[ ] Schedule technical deep-dive with PI administrators
[ ] Identify test environment availability
[ ] Review and provide network/security documentation
[ ] Other: _____________________________________________________________________

FOLLOW-UP MEETING:
Date/Time: _____________________________________________________________________
Participants: __________________________________________________________________
Agenda: ________________________________________________________________________

DOCUMENT CONTROL

Version Date Author Changes
1.0 [Date] ApprenticeFS Initial draft

DISTRIBUTION:
[Name/Role]
[Name/Role]

This document is confidential and proprietary to ApprenticeFS and [Client Name]