Step Description SharePoint Fields

1 Gather Files: Oxy Lead gathers PLC program, ICD, PanelView STEP: Gather Files
STATUS: Not started
2 Build IDF – done by developer STEP: Build IDF
Includes fixing or deleting any bad alarms and process data. STATUS: In Progress
3 Build/modify template - done by Core Team STEP: Template
STATUS: ON HOLD
4 Approve IDF - done by Oxy Core Team (Juan Rojas/Leonardo STEP: Approve IDF
Jaime). STATUS: In Progress
• Temporary step while developers getting trained. Will be
removed.
• Purpose: ensure that it won't crash lab svr. This check
does NOT ensure the IDF is complete, so it could be
missing alarms.
5 Lab Testing STEP: Lab Testing
1. Developer does testing.
2. Defects with Iconics 9 configuration added to backlog. Backlog = YES
3. Update the Facilities List in SharePoint (Has Backlog =
YES)
4. Core team reviews IDF to ensure no missing alarms.
6 Process Overview screen built by developer STEP: Overview Screen
• [applies to first facility only] after testing is complete, the
core team teaches the developer how to build graphical
overview screen. This is a 1:1 training session.
7 IDF Review by Core Team STEP: IDF Review
• After the developer is confidant it is done, they send the
files to core team for review again. After it is approved,
the facility can be moved to production. This step still
applies even after first facility.
8 Publish to prod STEP: Publish
1. Publish files to prod svr. Only done after all previous
steps complete. Initially, done by core team. Once we
trust the developer they will do it themselves.
2. Alarm Comparison - Oxy Lead runs tool provided by IT ICO10: YES
ICS. This ensures all alarms from Ico9 are in Ico10 with
similar configurations.
3. Point to Point testing in production
4. Call the call out center to inform them there will be
duplicate alarms from Ico9 and Ico10 temporarily.
5. Verify the call out center sees the duplicate alarms
6. Upload IDF & documentation files in Teams. Includes
Alarm Validation Report (confirms alarms were tested).
7. Update the Facilities List in SharePoint. (Ico10 column =
YES)
Step Description SharePoint Fields
9 QC - done by Oxy Lead. Includes STEP:
1. Oxy lead assigns facilities to a QC checker 1 QC-NOT STARTED
2. Equipment & Instrument review 2-4 QC-REVIEW
a. For each equipment, check all instruments. All 5 QC-TEMPLATE
alarms, points from Ico9 present 6-7 QC-FIX
b. Check process overview & navigation
c. Check trends STATUS: if pending
d. Capture discrepancies in a file template, set to On Hold
3. Oxy Lead/QC helper discuss discrepancies & decide
whether to correct
4. Consult w/ original Developer & decide what to correct
5. For template changes repeat these steps until complete:
a. Consult with Core Team
b. Confirm w/ Ops
6. [whoever fixes]
a. Correct, test in lab, publish to prod, P2P test on
fixed items
b. Inform QC team facility is finished
7. Oxy Lead confirms all corrections made
10 Validation - Done by Oxy Lead STEP
1. Notify Ops screens are ready for them to test for 2 1 VALIDATE-REVIEW
weeks. 2 VALIDATE-FIX
a. Also inform them of known defects carried over
from Iconics 9. Operations Validation Start
b. Update Facilities list in SharePoint (Operations Date=today
Validation Start Date=today)
2. Confirm Ops is satisfied with Iconics 10 aside from Backlog = YES if they
known defects. request changes
a. Correct as needed.
b. Update Facilities list in SharePoint (Backlog = YES
if they request changes)
11 Retire Iconics 9 - Done by Oxy Lead STEP: RETIRE ICO9
1. Stop callouts in Iconics 9 STATUS: COMPLETED
2. Add watermarks in Iconics 9 ICO9 = NO
3. email latest IDF to Field Mobility Team Completed Date = Today
4. Update the Facilities List in SharePoint. (Ico9 column =
NO; Completed Date = Today)
12 Backlog resolution Backlog = NO
1. Developer (outside project team) collaborates with TBD
to resolve questions with Ops
2. In personal environment, developer corrects known
defects, replicates recent changes from Iconics 9 & tests
3. On Dev Svr, developer tests all the changes
4. Oxy Lead asks Core Dev team to validate all changes
5. Developer publishes all changes to Production server
6. Developer performs point to point testing in Production
7. Oxy Lead asks Ops team to validate all changes
8. Oxy Lead confirms validation is complete & marks all
backlog items complete