Requirement study for the business integration of the new SCADA/EMS system on the AES SONEL network in Cameroon

• DEDICATION
  
• RESUME
  
• ABSTRACT
  
• GENERAL INTRODUCTION
  
  • 1.2.1: History
    
  • 1.2.2: Mission
    
  • 1.2.3: Organization of AES Sonel
    
  • 1.2.3.1: Hierarchical organization of AES Sonel
    
  • 1.2.3.2: Organization of the network operations department
    
  • 1.2.4: Description of the AES Sonel network
    
  • 1.3.1: Existing operations management system
    
  • 1.3.1.1: Processes
    
  • 1.3.1.2: Procedures
    
  • 1.3.1.3: Resources
    
  • 1.3.1.3.1: Human resources
    
  • 1.3.1.3.2: Systems
    
  • 1.3.1.3.2.1: Existing SCADA system
    
  • 1.3.1.3.2.2: Existing telecommunication system
    
  • 1.3.1.3.2.2: Softwares
    
  • 1.3.2: The TSO and the new electricity market system
    
  • 1.4: Scope of work and specific objectives
    
  • 2.2: Systems development life cycle
    
  • The purpose of this a methodology is to specify a set of well-defined steps or phases, coupled with a set of clear, measurable exit criteria, for developing and implementing an information system) [24]. The system development life cycle (SDLC) is a set of steps that serves as the basis for most systems analysis and design methodologies.
    
  • 2.2.1: strengths, weaknesses and limitations
    
  • 2.2.2: The system development life cycle methodology (the waterfall method)
    
  • 2.3: Information systems project implementation
    
  • 2.4: Requirement engineering
    
  • 2.4.1: Requirement gathering
    
  • 2.4.2: Requirement analysis and specifications development
    
  • 2.5: Process engineering
    
  • 2.5.1: Change management
    
  • 2.5.2: Business Process Reengineering (BPR)
    
  • 2.6: Technology transfer
    
  • Technology denotes the broad area of purposeful application of the contents of the physical, life and behavioral sciences [25]. Technology transfer is a long and complex process of innovation, that is, a process of adaptation and change. Technology transfer projects often occur where the recipient culture (technology-pull side) is different from the source culture (technology-push side) and therefore generally long, complicated and extend over an average of two to four years [25].
    
  • 2.7: Technology transfer project management
    
  • 2.7: Adopted methodology
    
  • 2.3: Conclusion
    
  • 3.2.1: Technological requirements
    
  • 3.2.1.1: Pre-requisites for implementation
    
  • The pre-requisites for the implementation of this new SCADA/EMS system are classified under three main categories
    
  • 3.2.1.1.1: Human Resources
    
  • 3.2.1.1.1.1: Implementation
    
  • 3.2.1.1.1.2: Project Follow-up and Handling
    
  • 3.2.1.1.1.3: Systems Operation and Business Integration (BI)
    
  • 3.2.1.1.2: Civil, Construction and adaptation Works
    
  • 3.2.1.1.3: Telecommunication Infrastructure
    
  • 3.2.1.2: QUALITY DATA FOR SYSTEM
    
    • 3.2.1.2.1 Organizational Data
      
    • 3.2.1.2.1.1 Transmission Network Plan
      
    • 3.2.1.2.1.2 Telecommunication Network Infrastructure
      
    • 3.2.1.2.1.3 Profile Data for System users (System Operators and System Administrators)
      
    • 3.2.1.2.1.4 Generation System Owner Data
      
    • 3.2.1.2.1.5 Transmission System Customer/End User data
      
    • 3.2.1.2.2 Referential Data
      
    • 3.2.1.2.3 SCADA Process Data
      
    • 3.2.1.2.3.1 Controls
      
    • 3.2.1.2.3.2 Status
      
    • 3.2.1.2.3.4 Measurements
      
    • 3.2.1.2.4 EMS Process Data
      
    • 3.2.1.2.4.1 Generation Process Data
      
    • All information and data on the status, generating capacity and availability of the different Generating (Power) stations connected and supplying power to the transmission system of the southern grid for dispatching and planning and should include information such as for each generating station
      
    • Also for each of the different generating stations, information for the different generating units such as
      
    • 3.2.1.2.4.2 Network Application Process Data
      
  • 3.2.2 Organizational requirements
    
    • 3.2.2.1 Operations reengineering
      
    • 3.2.2.2 Organizational reengineering
      
  • 3.2.3 Operational requirements
    
  • 3.2.3.1: Systems rollout
    
    • 3. Gradual cutover: which is a combination of direct and parallel cutover and where the idea is to run the new and old systems concurrently and gradually increase the number of transactions handled by the new system. Actually here, data is not processed twice; instead, some transactions are processed by the old system, some are processed by the new system, and the percentage sent to the new system gradually increases until the old system fades away.
      
  • 3.2.3.2: Training
    
    • 3.2.3.2.1 Objective
      
    • 3.2.3.2.2 Training types
      
    • 3.2.3.2.3 Training Plan
      
  • 3.2.4: Maintenance and Support
    
  • 3.2.4.1: Maintenance and Spare Part Replacement Strategy
    
  • 3.2.4.2: Support Strategy
    
  • 3.2.5: Documentation
    
  • 3.2.5.1: Hardware Documentation
    
  • 3.2.5.1.1: Equipment Documentation
    
  • 3.2.5.1.2: Installation Documentation
    
  • 3.2.5.2: Software Documentation
    
  • 3.3.1: Telecommunication systems quality assurance conformance checklist
    
  • 3.3.2: Systems rollout quality assurance conformance checklist
    
  • 3.3.3: Training quality assurance conformance checklist
    
  • 3.3.4: Documentation quality assurance conformance checklist