Returning part of output back to input is considered feedback but this is NOT valid in all cases. This identifies what is missing in a complete FEEDBACK model: The User or Customer of the output. The feedback must come from the User of the output based on using the output. What such user gives is TRUE feedback. Many cases in which feedback works effectively it is because the feedback is TRUE. Such cases are discussed to support this view.
Use this and let me know your cases and how you are using TRUE feedback.
A thermocouple is a temperature-measuring device consisting of two dissimilar conductors that contact each other at one or more spots. It produces a voltage when the temperature of one of the spots differs from the reference temperature at other parts of the circuit.
1. THERMOCOUPLE
∙ Principle of Operation
∙ Materials Used
∙ Advantages
∙ Applications
∙ Comparison with RTD
∙ Limitations
By
AnandBongir
GirjashankarMishra
2. A thermocouple is a junction between two different metals that produces a voltage related to a temperature difference.
3. Principle of Operation
Thermocouples are based on the principle that two wires made of dissimilar materials connected at either end will generate a potential between the two ends that is a function of the materials and temperature difference between the two ends (also called the Seebeck Effect).
4. Seebeck Effect
5.
6. Materials Used
Type K:
Chromel – Alumel
• Range: −200 °C to +1350 °C
• Sensi: 41 µV/°C
Type J:
Iron – Constantan
• −40 to +750 °C
• 55 µV/°C
Type E:
Chromel – Constantan
• 401 to 900° C
• 68 µV/°C
Type N:
Nicrosil – Nisil
• >1200 °C
• 39 µV/°C
7. Advantages
It is rugged in construction
Covers a wide temperature range
Using extension leads and compensating cables, long transmission distances for temperature measurement possible. This is most suitable for temperature measurement of industrial furnaces
Comparatively cheaper in cost
Calibration can be easily checked
Offers good reproducibility
High speed of response
Satisfactory measurement accuracy
8. Limitations
For accurate temperature measurements, cold junction compensation is necessary
The emf induced versus temperature characteristics is somewhat nonlinear
Stray voltage pickup is possible
In many applications, amplification of signal is required
9. Applications
Type B, S, R and K thermocouples are used extensively in the steel and iron industries to monitor temperatures and chemistry throughout the steel making process.
Gas-fed heating appliances such as ovens & water heaters.
In the testing of prototype electrical and mechanical apparatus
I have added a PPT of 50 slides. It gives diagrams which I have not been able to add to text in this PDF.
See the PPT by the same name at www.slideshare.net/putchavn
What is normally called feedback may not be TRUE FEEDBACK. There are conditions to be applied. Only then can one realize the benefits of feedback. This understanding is necessary to design effective business processes that involve machines and humans.
This is an extended abstract for helping interaction. Feel free to email kenablersys@yahoo.com
Introduction, Feature of Control System, Requirement of Good Control System, Types of Control System, Open-loop control system, Closed-loop control system, Comparison of Closed-Loop and Open-Loop Control System, Signal flow graph, Conversion of Block Diagrams into Signal Flow Graphs, and Questions.
This paper outlines fundamental topics related to classical control theory. It moves from modeling simple mechanical systems to designing controllers to manage said system.
A thermocouple is a temperature-measuring device consisting of two dissimilar conductors that contact each other at one or more spots. It produces a voltage when the temperature of one of the spots differs from the reference temperature at other parts of the circuit.
1. THERMOCOUPLE
∙ Principle of Operation
∙ Materials Used
∙ Advantages
∙ Applications
∙ Comparison with RTD
∙ Limitations
By
AnandBongir
GirjashankarMishra
2. A thermocouple is a junction between two different metals that produces a voltage related to a temperature difference.
3. Principle of Operation
Thermocouples are based on the principle that two wires made of dissimilar materials connected at either end will generate a potential between the two ends that is a function of the materials and temperature difference between the two ends (also called the Seebeck Effect).
4. Seebeck Effect
5.
6. Materials Used
Type K:
Chromel – Alumel
• Range: −200 °C to +1350 °C
• Sensi: 41 µV/°C
Type J:
Iron – Constantan
• −40 to +750 °C
• 55 µV/°C
Type E:
Chromel – Constantan
• 401 to 900° C
• 68 µV/°C
Type N:
Nicrosil – Nisil
• >1200 °C
• 39 µV/°C
7. Advantages
It is rugged in construction
Covers a wide temperature range
Using extension leads and compensating cables, long transmission distances for temperature measurement possible. This is most suitable for temperature measurement of industrial furnaces
Comparatively cheaper in cost
Calibration can be easily checked
Offers good reproducibility
High speed of response
Satisfactory measurement accuracy
8. Limitations
For accurate temperature measurements, cold junction compensation is necessary
The emf induced versus temperature characteristics is somewhat nonlinear
Stray voltage pickup is possible
In many applications, amplification of signal is required
9. Applications
Type B, S, R and K thermocouples are used extensively in the steel and iron industries to monitor temperatures and chemistry throughout the steel making process.
Gas-fed heating appliances such as ovens & water heaters.
In the testing of prototype electrical and mechanical apparatus
I have added a PPT of 50 slides. It gives diagrams which I have not been able to add to text in this PDF.
See the PPT by the same name at www.slideshare.net/putchavn
What is normally called feedback may not be TRUE FEEDBACK. There are conditions to be applied. Only then can one realize the benefits of feedback. This understanding is necessary to design effective business processes that involve machines and humans.
This is an extended abstract for helping interaction. Feel free to email kenablersys@yahoo.com
Introduction, Feature of Control System, Requirement of Good Control System, Types of Control System, Open-loop control system, Closed-loop control system, Comparison of Closed-Loop and Open-Loop Control System, Signal flow graph, Conversion of Block Diagrams into Signal Flow Graphs, and Questions.
This paper outlines fundamental topics related to classical control theory. It moves from modeling simple mechanical systems to designing controllers to manage said system.
Biomedical Control Systems - Time Response Analysis (Short Questions & Answers)Mathankumar S
Biomedical Control Systems - Time Response Analysis (Short Questions & Answers) - Its detailed about Standard Test Signals, Time Response Analysis of First and Second Order Systems, Steady state errors and Error constants, Effects of Adding Zero to a system, Damping System and PD & PID Controller.
A system is a group of interrelated components working together toward a common goal by accepting inputs and producing outputs in an organized transformation process.
CMGT 580Introduction to Systems Engineering ManagementClass .docxmary772
CMGT 580
Introduction to Systems Engineering Management
Class 5
Chapter 6 Needs Analysis
Reminder where Needs Analysis fits in process
“there is a feasible approach to fulfilling the need at an affordable cost and within an acceptable level of risk”
Concept Development Stage – Needs Analysis
Originating a new system
Needs-driven example: 1960's new laws for automobiles (fuel economy, safety, pollution control)
Technology-driven new systems (space, computers)
External events (new threats, shift in customer demand, economics)
Since there‘s no preceding phase the inputs come from other sources
Applying the Systems Engineering Method
The focus of attention in this phase is on the system operational objectives and goes no deeper than the subsystem level.”
More detail on next charts
Systems Engineering Method applied to the Needs Analysis Phase
Requirements analysis -- Operations analysis
Clarifying requirements
Functional definition -- Functional analysis
Translating requirements into functions
Allocating requirements
Define interfaces
Physical definition -- Feasibility definition
Develop alternative designs
Perform trade-offs to select a preferred approach
Develop detail for the selected design
Design validation -- Needs validation
Model system environment
Verification
Operations Analysis
Detailed identification of perceived deficiencies in current systems
Obsolescence is a prevalent driving force for new systems
The output of this activity is operational objectives for new system
Functional Analysis
This is an extension of operational studies
Establish if there's a possible technical approach to a system
It's not necessary to visualize a best configuration
Feasibility Definition
Feasibility addresses functional design, physical implementation, cost, external constraints and interactions
No attempt is made to optimize the design
Feasibility can be difficult in technology-driven systems
Needs Validation
Examine the validity of the results of the previous steps
Use an operational effectiveness analysis tool (model) based on a set of scenarios
These simulations are evaluated based on criteria called Measures of Effectiveness
This effectiveness analysis determines if a system concept is feasible and satisfies the operational objectives
MOE and MOP Metrics
Measures of Effectiveness (MOE) – indicates the degree to which the whole system achieves its objectives under specified conditions
Measures of Performance (MOP) – quantitative metric of the whole system’s characteristics or performance of a particular attribute, typically a level of physical performance
Development of Operational Requirements (CONOPS)
Operational distribution or deployment: Where will the system be utilized?
Mission profile or scenario: What must the system do to accomplish its objective?
Performance and related parameters: What are the critical system pa.
Framework for Online Software Evolution FOSE 04AUG22.pdfPutcha Narasimham
Framework for Online Software Evolution: FOSE
Abstract
Business Application Software BAS malfunctions often during early stages of development and deployment. They are inevitable and unavoidable. They are costly and time consuming to fix. There are two kinds of errors that cause BAS malfunction, (1) Errors in Business Policies, Rules, Information and Data (2) Software Errors of BAS. It is here proposed that some means of quick and safe correction and relaunching process be built into software design and operation. There are two separate proposals for (1) and (2). The second is discussed here.
ASIS (current) Process Map shows BAS running on its platform with its actors. The software development system (CI/CD Server) with BAS Developers is NOT connected to BAS or actors of BAS. The proposed Framework for Online Software Evolution FOSE is added to interconnect BAS Developer, CI/CD Server, and Platform of BAS online (while running).
Business Actor of BAS initiates Software Correction Request and online Business Authority (specially added actor of BAS) approves it for transmission to FOSE. Approved Software Correction Requests flow from BAS to FOSE and FOSE to BAS Developer. The BAS Developer then identifies the affected parts of BAS that need correction and works on the source code of BAS available in CI/CD Server. Then he or she corrects parts of BAS and tests them to generate a corrected trial version of BAS. The corrected trial version of BAS is available to the end users of BAS for evaluation of how their requests have been processed and met. The corrected and tested parts of BAS are then released to the Platform of BAS. The framework FOSE is notified of this for updating the status of approved software correction requests maintained in FOSE. Then FOSE allows launch of the new version of BAS. Making end users initiate “software correction requests”, approving them and passing them through FOSE to online BAS Developers in a closed loop, are the key factors for software evolution.
Thus, the BAS together with FOSE, becomes robust BAS continually. Here the software itself is Agile---not the software development. Incomplete software can safely be launched and run without frequent crashes. Unspecified user requirements get systemically captured from the business actors and met.
---III---
See examples and explanation in a separate word document
Normal Business Application Software BAS provides ONLY the business functionality, which is good enough if it works well. However that is never the case particularly for the new functionality offered for the first time. Invariably unforeseen business and software situations arise and the the BAS needs modifications often at design level of the business logic and or the BAS itself. All this has to be done off line. Here it is proposed that both Business Support and Software Development Support be brought ONLINE. Here the Application Software itself becomes AGILE in operation---NOT just the software development process.
This is facilitated by two radical design changes.
First, the BAS it self is restructured and designed to bring Business Authority ONLINE and set up a Business Policy and Rules Repository BPRR.
Second, an additional Framework for Online Software Evolution is provided to bring the BAS Developers and the software development system online.
See how the combination works in this and two supplementary PPTs.
Biomedical Control Systems - Time Response Analysis (Short Questions & Answers)Mathankumar S
Biomedical Control Systems - Time Response Analysis (Short Questions & Answers) - Its detailed about Standard Test Signals, Time Response Analysis of First and Second Order Systems, Steady state errors and Error constants, Effects of Adding Zero to a system, Damping System and PD & PID Controller.
A system is a group of interrelated components working together toward a common goal by accepting inputs and producing outputs in an organized transformation process.
CMGT 580Introduction to Systems Engineering ManagementClass .docxmary772
CMGT 580
Introduction to Systems Engineering Management
Class 5
Chapter 6 Needs Analysis
Reminder where Needs Analysis fits in process
“there is a feasible approach to fulfilling the need at an affordable cost and within an acceptable level of risk”
Concept Development Stage – Needs Analysis
Originating a new system
Needs-driven example: 1960's new laws for automobiles (fuel economy, safety, pollution control)
Technology-driven new systems (space, computers)
External events (new threats, shift in customer demand, economics)
Since there‘s no preceding phase the inputs come from other sources
Applying the Systems Engineering Method
The focus of attention in this phase is on the system operational objectives and goes no deeper than the subsystem level.”
More detail on next charts
Systems Engineering Method applied to the Needs Analysis Phase
Requirements analysis -- Operations analysis
Clarifying requirements
Functional definition -- Functional analysis
Translating requirements into functions
Allocating requirements
Define interfaces
Physical definition -- Feasibility definition
Develop alternative designs
Perform trade-offs to select a preferred approach
Develop detail for the selected design
Design validation -- Needs validation
Model system environment
Verification
Operations Analysis
Detailed identification of perceived deficiencies in current systems
Obsolescence is a prevalent driving force for new systems
The output of this activity is operational objectives for new system
Functional Analysis
This is an extension of operational studies
Establish if there's a possible technical approach to a system
It's not necessary to visualize a best configuration
Feasibility Definition
Feasibility addresses functional design, physical implementation, cost, external constraints and interactions
No attempt is made to optimize the design
Feasibility can be difficult in technology-driven systems
Needs Validation
Examine the validity of the results of the previous steps
Use an operational effectiveness analysis tool (model) based on a set of scenarios
These simulations are evaluated based on criteria called Measures of Effectiveness
This effectiveness analysis determines if a system concept is feasible and satisfies the operational objectives
MOE and MOP Metrics
Measures of Effectiveness (MOE) – indicates the degree to which the whole system achieves its objectives under specified conditions
Measures of Performance (MOP) – quantitative metric of the whole system’s characteristics or performance of a particular attribute, typically a level of physical performance
Development of Operational Requirements (CONOPS)
Operational distribution or deployment: Where will the system be utilized?
Mission profile or scenario: What must the system do to accomplish its objective?
Performance and related parameters: What are the critical system pa.
Framework for Online Software Evolution FOSE 04AUG22.pdfPutcha Narasimham
Framework for Online Software Evolution: FOSE
Abstract
Business Application Software BAS malfunctions often during early stages of development and deployment. They are inevitable and unavoidable. They are costly and time consuming to fix. There are two kinds of errors that cause BAS malfunction, (1) Errors in Business Policies, Rules, Information and Data (2) Software Errors of BAS. It is here proposed that some means of quick and safe correction and relaunching process be built into software design and operation. There are two separate proposals for (1) and (2). The second is discussed here.
ASIS (current) Process Map shows BAS running on its platform with its actors. The software development system (CI/CD Server) with BAS Developers is NOT connected to BAS or actors of BAS. The proposed Framework for Online Software Evolution FOSE is added to interconnect BAS Developer, CI/CD Server, and Platform of BAS online (while running).
Business Actor of BAS initiates Software Correction Request and online Business Authority (specially added actor of BAS) approves it for transmission to FOSE. Approved Software Correction Requests flow from BAS to FOSE and FOSE to BAS Developer. The BAS Developer then identifies the affected parts of BAS that need correction and works on the source code of BAS available in CI/CD Server. Then he or she corrects parts of BAS and tests them to generate a corrected trial version of BAS. The corrected trial version of BAS is available to the end users of BAS for evaluation of how their requests have been processed and met. The corrected and tested parts of BAS are then released to the Platform of BAS. The framework FOSE is notified of this for updating the status of approved software correction requests maintained in FOSE. Then FOSE allows launch of the new version of BAS. Making end users initiate “software correction requests”, approving them and passing them through FOSE to online BAS Developers in a closed loop, are the key factors for software evolution.
Thus, the BAS together with FOSE, becomes robust BAS continually. Here the software itself is Agile---not the software development. Incomplete software can safely be launched and run without frequent crashes. Unspecified user requirements get systemically captured from the business actors and met.
---III---
See examples and explanation in a separate word document
Normal Business Application Software BAS provides ONLY the business functionality, which is good enough if it works well. However that is never the case particularly for the new functionality offered for the first time. Invariably unforeseen business and software situations arise and the the BAS needs modifications often at design level of the business logic and or the BAS itself. All this has to be done off line. Here it is proposed that both Business Support and Software Development Support be brought ONLINE. Here the Application Software itself becomes AGILE in operation---NOT just the software development process.
This is facilitated by two radical design changes.
First, the BAS it self is restructured and designed to bring Business Authority ONLINE and set up a Business Policy and Rules Repository BPRR.
Second, an additional Framework for Online Software Evolution is provided to bring the BAS Developers and the software development system online.
See how the combination works in this and two supplementary PPTs.
Plan Anything personally or professionally. Planning is a preparation for the future with a GOAL for some one. I dentify all of them. There are two major branches: Resource Planning and Action Planning. Planning can be elaborate or simple. Select the factors for quick success of your mission. Drop what is not relevant but do not miss anything vital. Best wishes,
Machine mediated meaning for semantic interoperability pvn 120109 pdfPutcha Narasimham
Definition of meaning applicable in human and machine contexts is proposed. This points out that what is taken as meaning of an expression is an equivalent expression but NOT meaning. Meaning is the result of acting out what is implied in the expression or execution of the expression. This is valid for machines and humans interchangeably.
Relation in set theory of math is flawed. It remains undetected and uncorrected even now. This 11 slide PPT point outs the errors with examples, corrects them, giving a better definition. It may be too elementary but how can math live with errors in fundamentals?
UseCase modeling is very diverse, often inconsistent and erroneous. This is due to imprecise and incomplete definition and specification of UML which does not have any glossary of terms and fails to formally define the terms--UseCase in particular. The very nature of UseCase is undefined and uncertain though all the versions of UML. I noticed these factors and discovered UseCase to be fundamentally a DIALOG of messages which in turn are composed of information and data in 2008. I have been uploading my analyses and proposals to SlideShare since 2010. Here is a new summary of my analyses and proposals in light of BPMN's definition of "conversation" which is essentially the same as my "dialog". The linked in discussions prompted model UseCase as an Association Class and remodel what is called UseCase Diagram as a new Class Diagram without the old misleading "UseCase Ovals" inside System under Consideration. I also recommend treating UML Actor as an External Entity playing multiple roles which is any done by default.
I welcome review and feedback. Thanks
Harmonizing use cases, dialogs or conversations, process maps, usecase diagra...Putcha Narasimham
UseCase concept is unique and profound concept to represent the needs of businesses and users from their view point. Based on UseCase and Actor identification, the System to be Developed can be specified and evolved systematically. This summary updates and integrates many proposals made earlier. It logically integrates all the concepts of the title.
How to study any publication deeply for analysis and research. The process and reporting format are presented with examples. This paves way for incremental discovery and innovation and validation / consolidation.
Allocation of resources to generate high value in services or designing most cost effective means for high customer satisfaction are NOT always done systematically or with quantification. But it is possible and worth doing.
Are there any generic tools to analyze and assess documents? Here are some suggestions including Procedure to Cluster Concepts & Check for their Coupling in a document.
I found it helpful. I suppose something like this or even better would be available.
Describing something new poses very serious problems. Dictionaries and encyclopedia have met this requirement fairly well but those methods and techniques are NOT within the reach of millions of us who have to "describe things or introduce things" for teaching, documenting, modeling for analysis and design etc.
Here is my proposal to do it with a simple table. Yes, it is derived from class definition and description of OOAD but it is very effective for use in general. See how it works and let's help millions of students and teachers who struggle to describe things. Here is a structure to it which solves 80% of the problem. Cheers!
Software is very special. I is grand, spectacular, regenerative and perpetual source of value---like nothing else we know.
Perhaps for this very reason it is misused and wasted. By cooperatively REUSING ALL ARTIFACTS of software, we can reap unheard of benefits repeatedly. Here is an outline of how we can do it. That is ReSAR. Let's start.
Multiple Actors DO interact with the SuC, which is why the SuC exists in the first place, but NO TWO of them can do so through a single UseCase. There can be NO Second Actor in a UseCase.
Each interaction, more appropriately the dialog, can only have two members actively involved in the dialog.
First is the SuC and the second is the associated Actor.
The nature of UseCase and its implications were well discussed in
http://www.slideshare.net/putchavn/usecase-case-is-a-dialog-not-a-process
http://www.slideshare.net/putchavn/use-casesingle-session
http://www.slideshare.net/putchavn/one-use-case-one-actor
Yet there are discussions and justifications for associating multiple actors with the same UseCase.
UseCase is a DIALOG involving only one SuC and One Actor per Session. There is NO scope for another actor to take part in that dialog. Here is an example ATM Cash withdrawal. It needs THREE separate UCs.
This is explained using Process Maps to show the separation and how to separate.
This should end the confusion and persistent misunderstanding and misrepresentation.
Combined UseCase Description, MockUp Screens & System Sequence DiagramPutcha Narasimham
There are different artifacts (documents) for Use Case Description, Mock-up Screens and System Sequence Diagram. That is because each UML diagram (or table or description, Use Case Description has no diagram) can accommodate only a few modeling elements.
Analysts often need a set of UML diagrams and descriptions to evolve and represent concepts. They have to be drawn quickly and iteratively to formulate and express the business concepts and requirements. They need to be created and edited together, not in isolation.
It is here claimed that the contents of these three UML artifacts can be combined into a single text-document with tables & without drawings.
This is a sequel to Pentagon of MEANING. Here we point out that what we generally accept as meaning of text is its most valid interpretation according to published grammar & vocabulary of the language.
Such meaning is arrived at by sharing and negotiation of the text and its interpretation / clarification etc.
The secret of reaching a common meaning is NOT long negotiation but it is: creating most unambiguous text. This is possible with the help of machine aided drafting of text.
This is the subject of full paper by the author "Machine Mediated Meaning for Semantic Interoperability" which will be uploaded shortly.
Please take a look and give your views.
Ogden and Richards published a full book "The Meaning of Meaning" in 1923. It is also a subject of a lot of research by a broad spectrum of scholars & scientists. But they have identified only 3 elements of meaning but we found FIVE. Hence, PENTAGON of Meaning moving from their TRIANGLE of Meaning.
The five elements are: Speaker S, Concept X in her mind, Text T to express X, Listener L, who creates Concept X' from T. Out of these only S, T and L are public, open for observation. The concepts X and X' are private separately to S and L and the meaning is X for S and X' for L. That is subject of this PPT. It is elaborated and discussed.
From here we need to arrive at common and open meaning of T. We have another PPT for that.
There is a full paper Machine Mediated Meaning for Semantic Interoperability, which you can find on slideshare soon.
Please leave a comment.
Concept Maps are very effective for language-free expression and communication of concepts visually. The fundamental structures, which are not all graphic, are also very elegant for encoding knowledge for machine processing.
The building blocks of knowledge (Nodes and Links) are NOT sufficiently "expressive & precise". HyperPlex fills this need. See the PPT by that name in https://www.slideshare.net/putchavn
Both the concepts are explained with examples.
Good for general use and a prerequisite for knowing what is knowledge and how to represent it. Leave a comment.
[1] A view that a UseCase (UC) is a "dialog" between the System under Consideration (SuC) and an Actor (for a specific UC) brings focus to what "messages need to be exchanged between the SuC and Actor to reach UC Goal".
[2] Agreeing on and specifying UC Goal is related to business or application. UC Goal would be the right first step of UC description.
[3] There are many "means" of generating "messages from SuC", through various internal activities within the SuC. They need not be (I would even say should not be) specified in UC Description.
[4] The concept of UseCase is profound and useful because it is a "dialog" but NOT a process. This distinction is not defined and clarified which is why, I think, the full benefits of UC modeling are not widely realized.
[5] This view of UC (as per 1, 2 & 3) clearly separates the "internal processes" of the SuC from UC. The "internal processes" can be hypothesized and evolved separately using UML Sequence Diagrams. All the business / user needs can be specified with sufficient precision and rigor through the “messages” of UC dialog. There are no external dependencies, though constraints may exist and have to be taken care of.
I have REVISED & uploaded the PPT with TWO Sections, Section 2 First.
[6] I would like to study applications and demonstrate how the "dialog" view of UseCase would simplify & clarify UseCase description for the business user as well as system developer without sacrificing precision and usefulness.
02 FEB 14
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
2. Hats off to Pioneers of Feedback
James Watt:
Flyball Governor 1788
James C. Maxwell
Theory of Governors 1867
Norbert Wiener
Cybernetics 1930
H S Black: Feedforward &
Feedback Amplifiers 1927
TRUE Feedback
2
Harry Nyquiat:
Stability Criterion 1932
H W Bode :
Gain & Phase margins 1940
N Minorsky :
PID Controller 1922
Partial list from Lecture Notes
Zhiqiang Gao, MIT
25OCT13
3. Feedback in Biological & Social Systems
Just beginning to study
Thanks to
http://www.linkedin.com/groupItem?
view=&gid=2639211&item=275483709
&type=member&commentID=16667217
3&trk=hb_ntf_COMMENTED_ON_GROU
P_DISCUSSION_YOU_FOLLOWED#comm
entID_166672173
TRUE Feedback
Not aware of all the
significant achievements
Got to know
Perceptual Control Theory
William T. Powers
(August 29, 1926 - May 24, 2013)
Hats off!
25OCT13
3
4. This Presentation has Four Sections
4
This is a companion PPT of PDF
http://www.slideshare.net/putchavn/true-feedback-extendedabstract-pvn-04-jun13
The PDF is not updated….so that may not match this PPT
Section 2
Section
1
TRUE Feedback
Section
3
Section
4
25OCT13
5. Section Contents
5
What is Feedback? In depth review; FOUR known
Section 1 elements, Guessing the missing FIFTH element
Section 2
Section 3
Complete Feedback System. Receiving Feedback In; Using it
to modify system operation; System Internals; Giving
Feedback Out to supplier. What is mistaken as feedback?
Section 4
TRUE Feedback
Where and how is feedback used? The crucial FIFTH
element, RECEIVER of output.The source of TRUE feedback.
Examples of working feedback systems; understanding how
& why feedback works; using & making feedback work.
General definition and model.
25OCT13
6. Section 1
What is Feedback?
In depth review of the concept & its nature
Analysis & Criticism of definitions & diagrams
Understanding FOUR known elements
Guessing the FIFTH vital, missing element
TRUE Feedback
25OCT13
6
7. The Nature & Concept of Feedback
Is it a stand-alone concept?
A monad? Or
A concept built on another
concepts, a dyad or triad?
Or a pentad?
TRUE Feedback
7
Let’s see the
Best of Top Ten
Googled Definitions
Not the best source
but is handy
25OCT13
8. The Best of Top Ten Googled Definitions
Feedback:
the return to the input
a part of the output
of a machine, system,
or process
TRUE Feedback
http://www.merriamwebster.com/dictionary/feedback
See my pdf by this name on
slideshare
Looks OK, but is it?
See the additional necessary
conditions in the next slide
25OCT13
8
9. Graphical Representation of Feedback
Input: Xi
System
TRUE Feedback
Feedback (a triad)
Output: Xo
1. Part of Output Xo
2. Returned directly
to Input Xi
Part of Xo
returned to Xi,
3. Of the same
Which part?
machine, system or
How is it
separated?
process
25OCT13
9
10. Analysis & Criticism of Feedback Definition
Born in
practice
Concept &
theory: Well
developed &
perfected
But….
TRUE Feedback
The definition & graphic model are too
literal, simplistic & incomplete
Part of output is REDIRECTED, but NOT
generated independently
The source of feedback is the system
itself--not independent, not external
Can self-generated feedback be VALID?
25OCT13
10
11. Can Feedback be Self-Generated?
Perhaps,
But it would be
too restrictive
Not general
TRUE Feedback
Xi
+
A
11
Xo
Voltage Follower, Special case of feedback
Works here but NOT in general
25OCT13
12. Should Feedback Return To Input?
What is return to input, adding?
Is it valid and general enough?
Is feedback of the same kind as
output?
Is there a single input & single
output?
TRUE Feedback
12
Definitions &
graphic models
NOT clear & precise
But the practices
seem to work
We will see why
25OCT13
13. Something is Missing
The foregoing analysis,
criticism and corrections
are significant
More important is the
missing FIFTH element
Definitions don’t have it
TRUE Feedback
13
2
System
1
Input
4
Feed
back
3
Output
5
Missing
25OCT13
14. The Missing 5th Element is NOT unknown
But is NOT identified and
represented
Let’s find where
feedback arises & goes
Let’s see how it is used
TRUE Feedback
14
2
System
1
Input
4
Feed
back
3
Output
5
Missing
25OCT13
End
Sec 1
15. Section 2
Where and How is Feedback Used?
Engineering, Biological, Social and Business Systems
Where Feedback Arises and goes
When is Feedback Effective
TRUE Feedback
25OCT13
15
16. Feedback in Engineering Systems
Automatic Control
Systems
Adaptive Control
Systems
Computer and
Communication
Systems
TRUE Feedback
Well developed
Comprehensive &
1
Effective
Input
But the Missing
element is NOT
explicitly identified
16
2
System
4
3
Output
Feed
back
5
Missing
25OCT13
17. Feedback in Biological Systems
17
Known to be
well evolved, Feedback is NOT “mere return of part of the
sensitive,
output to input”….
adaptive &
Biological systems show what real feedback is
robust
and how it works
But…..
TRUE Feedback
25OCT13
18. Feedback is NOT Self Generated
It comes from
External
RECEIVER of
output
Back to the
System
TRUE Feedback
18
There must be some RECEIVER of the output
Feedback is a special message, sent by the
RECEIVER to the System
After using the output
Output and feedback are related but need
NOT be of the same kind, often they should
NOT be
This is NOT very explicit.
25OCT13
19. Feedback in Social and Business Systems
The fifth
element is
Receiver of
Output or
Customer
Is explicitly
identified &
represented
TRUE Feedback
System
Input
Output
Feed
back
The Receiver
of Output
Customer
No mistake about it
25OCT13
19
20. Completing the Feedback System
The FIFTH
element:
Receiver of
output
TRUE Feedback
20
Completes the picture
Shows who or what uses
Output Xo & generates
Feedback In FBin
Separates Xo & FBin
See the next section
25OCT13
End
Sec 2
21. Section 3
Complete Feedback System
Receiver of Output (Customer)
Generation of Feedback
Feedback Processing by the System
Feedback Out to Supplier of Input
TRUE Feedback
25OCT13
21
22. Receiver of Output Gives Feedback
TRUE Feedback
1 Xi
2 System
3 Xo
4 Feedback In
5 Receiver
(Customer)
After using the Output
Back to the System, NOT
to Input
Feedback is NOT Output
Fed Back
Output & Feedback may
NOT be of the same kind
22
25OCT13
23. System
1.Modifies its behavior
to generate right
output 2 Xo (Not shown)
2.Gives Feedback Out
to the Supplier of
input 1 Xi
In general both 1 & 2
are necessary
TRUE Feedback
1 Xi
2 System
2 Xo
Feedback Out
To supplier of Xi
4 Feedback In
5 Receiver
Feedback Triggers Two System Actions
25OCT13
23
24. Cross Coupling is NOT Feedback
24
Often mistaken as feedback
It is a special internal connection
Feedback is valid if it is given
DIRECTLY to the System---Check
The definition of feedback will be
corrected
TRUE Feedback
25OCT13
25. Physical Reaction is NOT Feedback
Reaction is a
property of
materials and
circumstances /
conditions
Predicable with
fair accuracy
TRUE Feedback
25
Feedback is the response generated
on receipt of stimuli,
Particularly when multiple options of
response exist
Not sure if this distinction is rigorous
and valid
25OCT13
26. Feedback Should Go To the System
To receive & process
feedback
see system internals
Return to input is
oversimplified, often
infeasible & cannot work
TRUE Feedback
Graphic model is corrected
1 Xi
3 Xo
2 System
4 Feedback
5 Receiver
(Customer)
System needs a special
26
Definition will be corrected
25OCT13
27. TRUE Feedback
1 Xi
Supplier
1.To control its
internal subprocesses &
generate right
output 2 Xo
2.To give Feedback
Out to the
Supplier of 1 Xi
2 System
Feedback
Out
2 Xo
4 Feedback
In
5 Receiver
Feedback Triggers Two System Actions
25OCT13
27
28. System Internals
1 Xi
2.1
2.3
Controls of sub-processes
2.2
Feedback
Generator
Feedback Out
TRUE Feedback
28
2 System
Internal
Control
Generator
Out going FB data
2 Xo
2.4
Sequence & data
flows--Not shown
2.5
In coming FB data
Feedback
Processor
4 Feedback In
25OCT13
29. That is the Full Picture of Feedback
It has Five essential elements
System needs Port & Module
To receive feedback &
To modify its behavior
System generates & sends
Feedback Out to Supplier
TRUE Feedback
29
We will see examples
of how feedback
actually works when
it works
And how the stated
essentials are met
25OCT13
End
Sec 3
31. HOW and WHY Feedback works
Some examples are
closely discussed to
See where feedback
originates
WHO or WHAT senses
feedback
TRUE Feedback
31
WHO uses Feedback
HOW it is used
WHEN & WHY it works
How feedback
propagates to suppler
25OCT13
32. Feedback for effective door-bell operation
1.It should help caller
and those at home
2.Call button should be
at the entrance door
3.And bell should be
where people stay
TRUE Feedback
Caller
Entrance
Door
O
Door-bell
Button
E
25OCT13
32
33. Ring should reach caller…
Caller
Entrance
Door
O
Door-bell
Button
TRUE Feedback
E
33
1.For him to stop
pressing the button
2.And of course those at
home to hear and
respond
25OCT13
34. Caller needs two kinds of feedback
TRUE Feedback
presses Door-bell
button
Caller
Caller should
know
Bell is ringing &
Some one at
home is
responding
O
34
Electrical Sigal
Sound
should
H
reach
caller’s ear.
Feedback-1
Bell
Some one
at home
Home
Hears the bell and
responds. Feedback-2
25OCT13
35. Air-conditioner Delivers Cooled Air
Air-conditioner
Delivery Unit
Set
Temp
T
Cool Air
Room
R Temp
TRUE Feedback
1. Of Set Temp
2. Output: Cooled Air has
two parameters
Flow rate F &
Temp To
F
Controller
35
3. Feedback is Room Temp,
Not 2
25OCT13
36. What feedback does AC need?
Air-conditioner
Cooler
Cool Air
Fan
Fan
Set Temp
Controller
Room
R Temp
36
1. The Room is the receiver
of Cooled Air
2. Something in the room
must give feedback of
how cool the room is
3. Tempe Sensors (1,2,3.. )
in the room do it
There may be many units in an AC
TRUE Feedback
25OCT13
37. The room may
have different
temperature
zones
May need
Multiple vents
for uniform
cooling
TRUE Feedback
Cool Air
Distributor
Multiple Vents for Uniform Cooling
25OCT13
37
38. Independent Local Vent controls
Each zone
may need
independent
local vent
controller
Only one vent
is shown
TRUE Feedback
Flow rate control signal
Cooled Air
Vent 1
Cool Air
Distributor
38
Vent 1
Controller
Zone1
Feedback: Temperature Sensed
Set Point
Distributor
Zone 1 Local Temp Set Point
25OCT13
39. Feedback in Driving
While driving ahead
Driver is the
Goal Setter,
Feedback Generator &
Controller of car
TRUE Feedback
39
Driver Views & Sets
the Set Points
dynamically
Driver senses Goal
& car position
visually & through
motion
Based on
sensing he
controls the
direction and
speed of his car
25OCT13
40. Feedback for Reversing the Car
40
1. Driver can see the
When driver cannot see,
Another person GUIDE
Takes over the control of
the car remotely
TRUE Feedback
2 Guide
watches and
gets feedback.
Controls car
remotely
guide but NOT
the rear of
his car
3. Driver reverses the
car as per guide’s
instructions
25OCT13
41. Guide: Remote Driver for Reversing Car
Guide
1. Views the gap (goal -- position)
2. Gives reversing instructions
3. Repeats 1 till goal is reached
Guide is the real controller since he
gets the feedback
The actual driver merely drives as
per guide’s instructions
TRUE Feedback
2. Guide
The real
controller
(remote)
1. Driver can see the
guide but NOT
the rear of
his car
3 Driver merely
follows instructions
25OCT13
41
42. Feedback in Interactive PPT Drawing
42
Consider moving objects in PPT 2013,
Selected objects are highlighted
Only they move as we drag
Appropriate guide lines appear
For aligning, centering etc.
Give explicit feedback on key parameters
They disappear after positioning the object
Speeds up drawing – Great help
TRUE Feedback
Result of User
Feedback? +
Innovation?
25OCT13
43. Feedback in Interactive Conversation
Human A
43
Human B
Addresses B & gives message M1
Gets M1 & express B’s understanding U1 of
M1 & conveys U1. This is the first feedback
FB1.
Understands U1 in his own way U2
& Checks if U2 is close to intended
meaning of M1 in A’s mind.
If NOT, A modifies M1 as M1A. This
is FB2 on FB1
Gives his understanding of M1A as U3. This is
FB3 on FB2
---------U3 should be close to intended meaning of
M1. If not, the conversation ends.
All this just gets M1 from A to B. See the need and usefulness of feedback
TRUE Feedback
25OCT13
44. Regulated Voltage Power Supply -- RVPS
Set point Vset
TRUE Feedback
Load
R
Controller
Controllable
Voltage Source
V gen
1. The RVPS delivers power at
Io
2. Constant voltage Vset but
variable Current Io
3. Vset is externally set
manually
Vo
4. Here Vo is fed back (it
depends on Io)
Current
Vo is fed back
25OCT13
44
45. Effective Feedback in RVPS
R
TRUE Feedback
Controller
Controllable
Voltage Source
V gen
5 When Load, RECEIVER draws Io
Current
6 Vo = Vgen -- Io.R
Io
6 If Vo < Vset, Controller pushes
V gen up till Vo=Vset. This
happens when Io is high.
Vo
7 The revers happens if Vo > Vset
maintaining Vo at Vset
Load
Set point Vset
45
Vo is fed back
25OCT13
46. This works only for Constant Vset
And can NOT
deliver constant
current if that is
what is needed
The set point must
set Iset, NOT Vset
TRUE Feedback
46
What is fed back must
correspond to actual
current drawn Io by load,
NOT output voltage
And the controller has to
bring Io back to Iset
And that is NOT ALL!
25OCT13
47. Feedback works Because
The Receiver &
User of output
generates FB &
Sends it to the
right port and
module in the
System
TRUE Feedback
47
The System is capable of:
1. Receiving FB-in &
2. Processing FB-in
3. Modifying internal behavior
4. Generating FB-Out
25OCT13
48. Special Cases of Simple Feedback
48
Such feedback is
In them output is
processed suitably to
affected by receiver
modify the behavior of the
So feeding output
system
back works as true
Feedback Out may not be
feedback
essential in special cases
TRUE Feedback
25OCT13
49. Effective Feedback is TRUE FEEDBACK
49
From these
1.It is here proposed that
examples we find
2.All the elements of a
that
feedback system be
TRUE FEEDBACK is
correctly identified &
used in all effective
feedback-controlled 3.Used in the definitions
and graphic models
systems
TRUE Feedback
25OCT13
End
Sec 4
50. The Meaning of the Definition
Xi
+
S
X = Xi – Xf
-
A
AX
system
Xf=Bxo=ABx
B
B returns part of Xo to input
TRUE Feedback
50
A & B are parts of
Xo the system
A & B are also values
of amplification or
attenuation factors
Xf is feedback but
NOT TRUE Feedback
25OCT13