1. Standard Design Process (SDP) Software Tom Czerniewski Entergy Nuclear

2. Agenda – SDP Software General Requirements
Specific Software Considerations
Challenges and Lessons Learned
SDP Panel Preview

3. SDP Software - General Requirements
SDP Efficiency Bulletin 17-06
“The industry procedure IP-ENG-001, Standard Design Process, provides a streamlined and graded approach to the design change process. This initiative also suggests the use of standardized (i.e. compatible reader) software to facilitate compatibility and training to support implementation of the new process. …”
Desired end-state— “The standard design change procedure IP-ENG-001, supported by standardized software, is used across the industry to the benefit of each stakeholder. …”

4. SDP Software - General Requirements (cont.)
SDP Efficiency Bulletin 17-06
Value proposition (vision of excellence)— “…Standardized software to facilitate compatibility will streamline the implementation of the new procedure.”
Measure of effectiveness— “…Sharing of engineering changes: Utilities will post their design change abstracts in the software tool located on shared electronic database that will facilitate sharing throughout the industry. …”
Company Actions “…Project plan for implementation of the company’s chosen standardized design software (i.e., base software package as a minimum) by December 31, 2018*. …” *Note: Due date is based on draft Rev. 1 of EB.

5. SDP Software - General Requirements (cont.)
Summary of General Requirements
EB does not mandate any one specific software solution
Standardized, compatible reader software (e.g., can output to pdf or other compatible format)
Supports posting of design change abstracts to facilitate industry sharing
Implement base software package as a minimum (i.e., interfaces with other utility software applications are optional)

6. Specific Software Considerations
Automation of the SDP Where Possible
Design Attribute Review (use software to identify impacts, build Department Interfaces table and trigger review actions)
Change Package Development and Approvals (enter data in software which produces electronic forms and signatures)
Impact Reviews and Meetings (use software to track reviews, initiate and manage meetings)
Review Comments (reviewers provide comments electronically, versus use of hardcopy form)
Industry Sharing (auto-generate, populate, share EC abstract)
Field Change Requests, Advance Work Authorization
Cloning / Copying of ECs

7. Specific Software Considerations (cont.)
Interfaces with Other Utility Software Applications
Enterprise Asset Management System (such as for Modification Requests, ECs, Work Orders, Affected Documents, Affected Components, etc.)
Electronic Document Management System (such as for EC Record File, Document Markups, Document Images, etc.)
Other Software Applications

8. SDP Software - Challenges and Lessons Learned
Need to Have Clear Understanding of Current Utility and New Software Process Workflows (for ECs, Documents, etc.) to Ensure Proper Integration
Need to Engage IT and Business Support Personnel Early in the Process and Develop Realistic Schedule
Contract with software vendor (approvals may take time)
Interfaces (may require significant and varied resources to configure)
Configuration of user IDs and authentication against single sign-on management system (if applicable)
Software testing

9. Software Panel Preview
Representatives from Software Pilot and Other Utilities That Have Implemented (or are Implementing) SDP Software Solutions of Various Types
TVA
Exelon
Southern Nuclear
Ameren
Energy Northwest
Discuss Experiences Relative to SDP Software Implementation, Including Key Insights and Lessons Learned
Answer Questions

10. QUESTIONS?