This presentation will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
In the past we had Corporate asset management systems that originated on the financial side of the business and we had meter record systems that handled all metering test results. Between the two we would have all of our bases covered.
This presentation discusses testing protocols, pitfalls and other solutions developed by various utilities who have gone through the stages of AMI Deployment. Equipment and systems used for this type of testing is also covered. 06/25/2019
This presentation will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
In the past we had Corporate asset management systems that originated on the financial side of the business and we had meter record systems that handled all metering test results. Between the two we would have all of our bases covered.
This presentation discusses testing protocols, pitfalls and other solutions developed by various utilities who have gone through the stages of AMI Deployment. Equipment and systems used for this type of testing is also covered. 06/25/2019
This presentation will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
In the past we had Corporate asset management systems that originated on the financial side of the business and we had meter record systems that handled all metering test results. Between the two we would have all of our bases covered.
This presentation gives insight on managing AMI meter populations and testing continuously evolving communication technology in a post deployment world
This presentation was given during the New York State Meter Engineers Electric Metering Conference and discussed testing protocols, pitfalls, and other solutions developed by various utilities who have gone through the stages of AMI Deployment. Also discussed in this presentation is the equipment used to handle the types of testing used for AMI Deployment. 04.17.19
Measure, Metrics, Indicators, Metrics of Process Improvement, Statistical Software Process Improvement, Metrics of Project Management, Metrics of the Software Product, 12 Steps to Useful Software Metrics
This presentation is the second of a series of three examining how data, the collection of this data and the use of this data have dramatically changed and is continuing to change in our industry as a result of AMI.
We will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docxclarebernice
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PROCESS MODELING- Part I
______________________________________________________________________________________________________
Synopsis
The requirements analysis phase answers the question, "What does the user need and want from a new system?" The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives.
The Data flow diagram (DFD) has gained popularity as a technique for expressing system requirements for two reasons:
• It facilitates development, which often leads to building systems that better
satisfy user needs
• Data flow diagrams and narratives are easy for users to understand.
In this milestone you will first uncover external agents, processes and data flows that define the requirements for the proposed system and document that information. You will use that to build the Context Data Flow Diagrams.
Objectives
After completing this milestone, you should be able to:
• Understand and perform the techniques for requirements discovery.
• Determine external agents (external entities) and their relationship with the
System, identify data flows.
• Construct the Context DFD using VISIO.
Prerequisites
Before starting this milestone, the following topics should be covered:
• The problem analysis phase — Chapters 3 and 5
• PIECES framework — Chapters 3 and 5
• Problem analysis techniques — Chapter 6
• Process modeling techniques — Chapter 9
Assignment
Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business requirements for the system and model them. In this assignment we will use our results of the previous Milestone and transcripts of an interview with the Equipment Depot staff. The results of this activity will identify the system requirements for the proposed system.
Exhibit 3.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1 and 2 for the information necessary to complete the activities.
Activities
1. Identify External entities and relationship with system
2. Identify data flows
3. Prepare Context level Data FlowDiagram
Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 3”.
References
• Transcripts of Interview - Exhibit 3.1 (see below)
Deliverables:
Context level DFD:
Due: __/__/__
Time: _______
ADVANCED OPTIONFor the advanced option, compile the process description to note processes’ input and output.
Due: __/__/__
Time: _______
Milestone’s Poin ...
This presentation examines how AMI data, the collection of this data and the creation of tools to use of this data have dramatically changed and is continuing to change metering operations. We will look at some of the challenges we are facing as we learn how to do business most effectively with this information and these tools.
This presentation shows how meter farms are a new tool for managing AMI meter populations and testing continuously evolving communication technology in a post deployment world.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
This presentation will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
In the past we had Corporate asset management systems that originated on the financial side of the business and we had meter record systems that handled all metering test results. Between the two we would have all of our bases covered.
This presentation gives insight on managing AMI meter populations and testing continuously evolving communication technology in a post deployment world
This presentation was given during the New York State Meter Engineers Electric Metering Conference and discussed testing protocols, pitfalls, and other solutions developed by various utilities who have gone through the stages of AMI Deployment. Also discussed in this presentation is the equipment used to handle the types of testing used for AMI Deployment. 04.17.19
Measure, Metrics, Indicators, Metrics of Process Improvement, Statistical Software Process Improvement, Metrics of Project Management, Metrics of the Software Product, 12 Steps to Useful Software Metrics
This presentation is the second of a series of three examining how data, the collection of this data and the use of this data have dramatically changed and is continuing to change in our industry as a result of AMI.
We will discuss how Asset Tracking for Metering has changed dramatically over the past dozen years and what the term “asset tracking” will mean for meter services in the future.
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PRO.docxclarebernice
CIS 321 Case Study ‘Equipment Check-Out System’MILESTONE 3 – PROCESS MODELING- Part I
______________________________________________________________________________________________________
Synopsis
The requirements analysis phase answers the question, "What does the user need and want from a new system?" The requirements analysis phase is critical to the success of any new information system! In this milestone we need to identify what information systems requirements need to be defined from the system users’ perspectives.
The Data flow diagram (DFD) has gained popularity as a technique for expressing system requirements for two reasons:
• It facilitates development, which often leads to building systems that better
satisfy user needs
• Data flow diagrams and narratives are easy for users to understand.
In this milestone you will first uncover external agents, processes and data flows that define the requirements for the proposed system and document that information. You will use that to build the Context Data Flow Diagrams.
Objectives
After completing this milestone, you should be able to:
• Understand and perform the techniques for requirements discovery.
• Determine external agents (external entities) and their relationship with the
System, identify data flows.
• Construct the Context DFD using VISIO.
Prerequisites
Before starting this milestone, the following topics should be covered:
• The problem analysis phase — Chapters 3 and 5
• PIECES framework — Chapters 3 and 5
• Problem analysis techniques — Chapter 6
• Process modeling techniques — Chapter 9
Assignment
Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business requirements for the system and model them. In this assignment we will use our results of the previous Milestone and transcripts of an interview with the Equipment Depot staff. The results of this activity will identify the system requirements for the proposed system.
Exhibit 3.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1 and 2 for the information necessary to complete the activities.
Activities
1. Identify External entities and relationship with system
2. Identify data flows
3. Prepare Context level Data FlowDiagram
Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 3”.
References
• Transcripts of Interview - Exhibit 3.1 (see below)
Deliverables:
Context level DFD:
Due: __/__/__
Time: _______
ADVANCED OPTIONFor the advanced option, compile the process description to note processes’ input and output.
Due: __/__/__
Time: _______
Milestone’s Poin ...
This presentation examines how AMI data, the collection of this data and the creation of tools to use of this data have dramatically changed and is continuing to change metering operations. We will look at some of the challenges we are facing as we learn how to do business most effectively with this information and these tools.
This presentation shows how meter farms are a new tool for managing AMI meter populations and testing continuously evolving communication technology in a post deployment world.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Read| The latest issue of The Challenger is here! We are thrilled to announce that our school paper has qualified for the NATIONAL SCHOOLS PRESS CONFERENCE (NSPC) 2024. Thank you for your unwavering support and trust. Dive into the stories that made us stand out!
How to Create Map Views in the Odoo 17 ERPCeline George
The map views are useful for providing a geographical representation of data. They allow users to visualize and analyze the data in a more intuitive manner.
Unit 8 - Information and Communication Technology (Paper I).pdfThiyagu K
This slides describes the basic concepts of ICT, basics of Email, Emerging Technology and Digital Initiatives in Education. This presentations aligns with the UGC Paper I syllabus.
How to Split Bills in the Odoo 17 POS ModuleCeline George
Bills have a main role in point of sale procedure. It will help to track sales, handling payments and giving receipts to customers. Bill splitting also has an important role in POS. For example, If some friends come together for dinner and if they want to divide the bill then it is possible by POS bill splitting. This slide will show how to split bills in odoo 17 POS.
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
3. Problem Statement
Semi-processed material misaligned
after pass-through hot furnace
Material Aligned
Material
Misaligned
Assumption:
• The semi-processed material consisted of different types of
material (i.e. thermal coefficient, and expansion rate are
different)
• The furnace is used as material hot tempered process where it
6. Engineering Contradiction
Parameter involved:
Improved parameter : Temperature (#17)
Worsening Parameter : Measurement accuracy (#28),
Manufacturing precision (#29)
If I increased the heating/cooling temperature, the material is
completely melt/harden the material, but ultimately it will cause
material misalignment.
7. Inventive Principle # 24
Intermediary
DRAWBACKS:
Increase the production cost to design and prepare the jig/cap/clipper
Decrease the productivity because the jig/cap/clipper needs to be
attached on the semi-processed material prior load to the furnace
input
8. Physical Contradiction
High Temperature
(to melt the
material)
Low temperature
(to harden the
material)
Control
parameter:
Temperature
In Relation (Upon Condition)
• The furnace is hot if I want to melt the semi-processed material
• The furnace is cold if I want to cool down the semi-processed
material
11. Background Study
The main parameter value (MPV) for the
wheelchair was separated into 3 parts.Customer
requirement
Time
First
MPV
Second
MPV
New
MPV
Target of Part 2
14. Problem Statement
Many community and health facilities are
inaccessible by the patients although the
availability of these facilities is growing.
Community
communication
(Zone of Conflict-
What is the device? Is
hand phone effective?)
Alone
Assisted
15. Su-Field Model
Classifying to be Ineffective Su-Field
Class 2 (Developing the substance-field system), solution 2.1.2
(Double Su-Field Model) under the group of Complex Su-Field was
selected.
S1: Patient S2: Community
F1: Electromagnetic
S1: Patient S2: Community
F1: Electromagnetic
S3 S4
Adding Tracking
System
16. New MPV
Tracking system
◦ On-time update for the location of the patient
to the nearest hospital.
◦ Additional sensors can be added to the
tracking system to monitor the on-time
condition of the patient.
◦ The tracking system can also help to provide
the exact location of the patient for the nearest
transportation services.
◦ The tracking system is also able to build up
the network for the users.
19. Problem Statement
When the customers apply the membership cards from
different retail shops, they will faced the problem of too
many cards in their wallet or purse.
What are the main and interaction causes that the customers
apply so many membership cards?
20. Solving the Problem with TRIZ
Original Problem
to resolve
• Too many loyalty cards
• Heavy wallet or purse
Function
Analysis
• To think about how to stop a harmful action being harmful: too
many membership cards cause heavy wallet or purse.
Cause & Effect
Chain Analysis
• To find the potential fundamental root causes
• Use 39 System Parameters mixed with some of the 40 principles
of the contradiction Matrix.
21. Engineering
Contradiction
• If I increase the number of membership cards, then it’s will
provide more benefits but it ultimately consumers more
space (wallet or purse).
Contradiction
Matrix
• To identify the System Parameters which improve and
worsen; and use the Contradiction Matrix to identify
potential Inventive Principles to help solve the problem.
Special Inventive
Principle
• Once the improving and worsening System Parameters are
identified, then the Contradiction Matrix is used to generate
potential Inventive Principle solutions.
22. Cause & Effect Chain Analysis
Too many membership cards in
the wallet or purse
Provide special and
differentiated service
to best customers
Enhance the
overall value-
proposition of the
product or service
Turn a profit
Potential fundamental root causes
23. Inventive Principle Propose Solution
Principle #10
Preliminary action (Prior action – “Do it in advance”)
Figure 1: Membership card using Data Bank
24. Benefits and Impacts of the Solution
No more bulky wallet or
pocket, carry only one card for
different retail shop on different
loyalty programs
Internet loyalty programs can be deployed across
multiple vendors and the card acts as a secure
central depository for points or rewards.
Easy to track the due date for different
loyalty programs
