This document summarizes an IDS Specialist Project to standardize the spurious analysis process. It includes a project schedule, objectives, and details each step of the process including visualizing the problem, committing resources, prioritizing solutions, characterizing the current process, improving by selecting Spectrasys software, and achieving the goal of a standard template. Spectrasys was chosen over other tools like Matlab, ADS, and Excel as it provides an easy to use interface, truncates low level signals to reduce simulation time, and can import files from other tools. An improved standardized process using Spectrasys is expected to save significant time and money across projects.
This document provides an introduction to computer simulation. It begins with defining key concepts like systems, models, simulation, and discrete event simulation. It discusses how simulation is used to imitate the operations of a system by developing a model and evaluating it numerically. The document then covers topics like the process of developing a simulation model, different types of simulation models, components and organization of discrete event simulation models, and time advance mechanisms used in simulation. Finally, it provides an example of simulating a single server queueing system to estimate performance measures like average delay in queue.
This document discusses Ansoft HFSS simulation software. It provides an overview of HFSS's main features like automatic adaptive meshing and advanced finite element method technology. It also describes getting started with HFSS, provides an example of simulating a microstrip patch antenna, and lists advantages like high productivity for research and development. The document concludes that HFSS is well-suited for simulating planar antennas and designing complex RF components.
The document discusses computer simulation as a tool for process improvement. It defines computer simulation, outlines the basic steps which include defining the problem, mapping the process, defining inputs, building a model, validating the model, performing simulations, and interpreting results. Reasons for using simulation include testing changes without risk or time, understanding bottlenecks, and verifying expected improvements. Simulation should not be used without proper training or understanding, or when simpler methods can be used.
The document discusses computer simulation as a tool for process improvement. It defines computer simulation as using a computer model to simulate a real system. The basic steps for computer simulation are: 1) define the problem, 2) map the process, 3) define inputs, 4) build the model, 5) validate the model, 6) perform simulations, 7) interpret results, and 8) recommend and document solutions. Reasons for using simulation include testing changes without risk or time constraints, understanding bottlenecks, and validating expected improvements. Simulation should not be used without proper training or understanding, or when simpler methods can achieve the goal.
The document provides details of a course registration system project for a university. It includes a project plan with objectives to create an online system to replace the manual paper-based registration currently used. It outlines requirements for the system including functional requirements for student, administrator, teacher and registrar modules. Non-functional requirements around performance, safety and security are also specified. The project will follow a waterfall model for development.
This document provides an introduction to computer simulation. It begins with defining key concepts like systems, models, simulation, and discrete event simulation. It discusses how simulation is used to imitate the operations of a system by developing a model and evaluating it numerically. The document then covers topics like the process of developing a simulation model, different types of simulation models, components and organization of discrete event simulation models, and time advance mechanisms used in simulation. Finally, it provides an example of simulating a single server queueing system to estimate performance measures like average delay in queue.
This document discusses Ansoft HFSS simulation software. It provides an overview of HFSS's main features like automatic adaptive meshing and advanced finite element method technology. It also describes getting started with HFSS, provides an example of simulating a microstrip patch antenna, and lists advantages like high productivity for research and development. The document concludes that HFSS is well-suited for simulating planar antennas and designing complex RF components.
The document discusses computer simulation as a tool for process improvement. It defines computer simulation, outlines the basic steps which include defining the problem, mapping the process, defining inputs, building a model, validating the model, performing simulations, and interpreting results. Reasons for using simulation include testing changes without risk or time, understanding bottlenecks, and verifying expected improvements. Simulation should not be used without proper training or understanding, or when simpler methods can be used.
The document discusses computer simulation as a tool for process improvement. It defines computer simulation as using a computer model to simulate a real system. The basic steps for computer simulation are: 1) define the problem, 2) map the process, 3) define inputs, 4) build the model, 5) validate the model, 6) perform simulations, 7) interpret results, and 8) recommend and document solutions. Reasons for using simulation include testing changes without risk or time constraints, understanding bottlenecks, and validating expected improvements. Simulation should not be used without proper training or understanding, or when simpler methods can achieve the goal.
The document provides details of a course registration system project for a university. It includes a project plan with objectives to create an online system to replace the manual paper-based registration currently used. It outlines requirements for the system including functional requirements for student, administrator, teacher and registrar modules. Non-functional requirements around performance, safety and security are also specified. The project will follow a waterfall model for development.
Receiving data from a source that produces 5-10 GBytes per hour, and presenting analysis results as the data streams in has some interesting challenges.
We used MongoDB running on Amazon EC2 to house the data, map reduce to analyze it and Django-non-rel to present the results in near-real-time.
(Slides from my presentation at MongoDB Boston)
1. The document outlines the process of planning a research project through developing a research model, identifying topics and areas of research, conducting a literature review, executing the research, analyzing results, and reporting findings.
2. It emphasizes the importance of planning through tools like Gantt charts and K-charts to systematically organize the research scope, methods, and expected results.
3. Good planning requires clearly defining the research plan, thoroughly understanding fundamentals, conducting extensive critical reviews, and having sufficient resources and passion to carry out detailed experimentation and thorough analysis.
The document discusses software cost estimation techniques including COCOMO models and function points. It provides details on estimating project size, effort, schedule and costs. The COCOMO models include basic, intermediate and detailed models which take into account factors like project size, development mode and cost drivers. Function point analysis involves counting inputs, outputs, inquiries and files to determine unadjusted function points which are then adjusted based on technical complexity factors. Examples are provided to demonstrate estimating lines of code, effort, schedule and errors using these techniques.
Ultrasonic B Scan Laboratory Experiment GuidanceTony Toole
The document describes the process for remotely conducting an ultrasonic B-scan experiment to analyze a corroded pipe sample. It involves connecting to a university network via VPN, launching a remote desktop application, and using ultrasonic scanning software to capture and analyze a B-scan image of the pipe sample. The steps include initializing the ultrasonic interface, adjusting gain and gate settings, performing a scan to capture the image, and analyzing the image data to locate defects and measure wall thickness.
This document outlines the plan for an online exam system project. It will include objectives like allowing teachers to create exams and track student results. The project team consists of a project manager, software designer, analyst, programmer, and tester. Risks like staff turnover or budget issues are identified along with mitigation strategies. Hardware, software, and other resource requirements are specified. The work is broken down into tasks like contract negotiation, documentation drafting and review, requirements analysis, and implementation.
The document outlines a project plan for developing an online exam system. It discusses objectives to securely connect the system to institutional data and give users exam creation privileges. It also covers the project team roles, risks involving staffing, methodology, budget, and hardware, and software requirements including computers, internet, software licenses, and salaries. The work breakdown includes contracting with clients, drafting and rewriting documentation, requirements analysis, system design, programming, testing and deployment.
Stages of FMEA in Total Quality Management Dr.Raja R
This document outlines the 10 steps for conducting a Process Failure Mode and Effects Analysis (FMEA) as part of a Total Quality Management process. The steps include: 1) reviewing the process using a flowchart, 2) brainstorming potential failure modes, 3) listing potential effects of each failure, 4) assigning severity rankings, 5) assigning occurrence rankings, 6) assigning detection rankings, 7) calculating the Risk Priority Number, 8) developing an action plan, 9) taking action to implement improvements, and 10) recalculating the Risk Priority Number after improvements. Conducting a Process FMEA in a step-by-step manner allows each step to build upon the previous one for systematically analyzing potential failures, effects,
The document summarizes the key features of OMCS International's PMO2000TM Reliability Assurance Software Suite. It allows for reliability centered maintenance, risk analysis, integration with SAP systems, and customizable reporting. The software provides a complete solution for asset reliability from initial analysis through implementation and management.
This document provides an overview of computational fluid dynamics (CFD) and the general methodology for analyzing fluid dynamics problems using CFD. It discusses the three approaches to problem solving - analytical, experimental, and numerical. It describes what CFD is and how it uses numerical methods to obtain approximate solutions to problems involving fluid flow, mass transfer, and heat transfer. The document outlines the basic steps in setting up and solving a CFD problem using a commercial solver like ANSYS Fluent, including pre-processing, defining the physical models and boundary conditions, running the solver, and post-processing the results.
The Automation Firehose: Be Strategic & Tactical With Your Mobile & Web TestingPerfecto by Perforce
The document discusses strategies for effective test automation. It emphasizes taking a risk-based approach to prioritize what to automate based on factors like frequency of use, complexity of setup, and business impact. The document outlines approaches for test automation frameworks, coding standards, and addressing common challenges like technical debt. It provides examples of metrics to measure the effectiveness of test automation efforts.
The document discusses the importance and benefits of structured programming. It outlines seven key concepts of structured programming including structured walkthroughs, stepwise refinement, modular design, bottom-up coding, testing using stubs, white box and black box testing, and generating structured programming documents. It provides examples to illustrate concepts like branching, looping, and modular design. Structured programming helps produce programs that meet requirements, are easy to maintain, and avoid bugs.
This document provides instructions for using various tools within the MATLAB environment, including:
1) The Wavelet Toolbox for 1D and multi-signal wavelet analysis.
2) The Neural Network Toolbox for neural network fitting, clustering, and pattern recognition tools.
3) The Filter Design & Analysis Tool for designing high pass and notch filters.
4) Simulink for designing a PID controller. Step-by-step instructions are provided for using each tool.
- The document is an internship report by Valeria Marisol Cabriales Garza describing her project at OSRAM Opto Semiconductors developing a new measurement program using LabVIEW.
- She worked in the Development division programming an analyzer measurement workspace to modernize the interface and improve usability. The existing program was in an outdated language and did not have friendly interfaces.
- Her project involved designing a new program in LabVIEW to measure current and voltage of components and generate graphs of measurement results. This required managing complex interconnected databases and ensuring all program steps worked dynamically together.
Lte drivetest guideline with genex probeRay KHASTUR
1. Drive testing involves collecting radio frequency data through a test device to evaluate network coverage and quality of service parameters.
2. Major LTE key performance indicators measured include accessibility, retainability, mobility, and integrity. Key parameters measured are RSRP, SINR, and throughput.
3. To perform an effective drive test, the tester must understand parameter definitions, avoid duplicate routes, analyze events like call drops, and strategically test throughput in stable conditions.
1. Methodologies differ for each project and team, so a single methodology does not fit all. Managers need guidance to help teams create their own methodology using an evidence-based approach.
2. Methodologies have both formal parts like processes and meetings, as well as important informal parts like team collaboration. Simply mixing practices haphazardly is not effective.
3. Pattern languages can help by describing what works and what doesn't for a given context, explaining tradeoffs, and allowing the methodology to evolve with changing needs based on evidence.
EELE 5331 Digital ASIC DesignLab ManualDr. Yushi Zhou.docxtoltonkendal
This document outlines the procedures for a lab manual on digital ASIC design. It describes designing a single MOSFET transistor from schematic entry to post-layout simulation. Students are instructed on how to use Cadence software to create a schematic, perform pre-layout simulation using parametric and DC analysis, and generate layout of the transistor. The document provides step-by-step guidance on using key Cadence tools for simulation, layout, and verification of the transistor design.
Assignment Based on two topics:-
1.SRS Library Management`
2. Risks in designing a software
Made by :-
RAJAT MITTAL
JK INSTITUTE OF APPLIED PHYSICS & TECHNOLOGY, UNIVERSITY OF ALLAHABAD
This document provides an overview of problem solving and Python programming. It discusses computational thinking and problem solving, including identifying computational problems, algorithms, building blocks of algorithms, and illustrative problems. It also discusses algorithmic problem solving techniques like iteration and recursion. Finally, it briefly introduces the course titled "GE8151-PROBLEM SOLVING AND PYTHON PROGRAMMING".
GSM UMTS LTE Site Commissioning softwareAhmet Ozturk
Mobile network operators usually use internal macros and excel sheets to create scripts and xml files site commissioning. With Accela Cell Data Manager, it is very easy, fast and accurate to create OSS/M2000/Netact scritps in amos,mml and xml formats.
Receiving data from a source that produces 5-10 GBytes per hour, and presenting analysis results as the data streams in has some interesting challenges.
We used MongoDB running on Amazon EC2 to house the data, map reduce to analyze it and Django-non-rel to present the results in near-real-time.
(Slides from my presentation at MongoDB Boston)
1. The document outlines the process of planning a research project through developing a research model, identifying topics and areas of research, conducting a literature review, executing the research, analyzing results, and reporting findings.
2. It emphasizes the importance of planning through tools like Gantt charts and K-charts to systematically organize the research scope, methods, and expected results.
3. Good planning requires clearly defining the research plan, thoroughly understanding fundamentals, conducting extensive critical reviews, and having sufficient resources and passion to carry out detailed experimentation and thorough analysis.
The document discusses software cost estimation techniques including COCOMO models and function points. It provides details on estimating project size, effort, schedule and costs. The COCOMO models include basic, intermediate and detailed models which take into account factors like project size, development mode and cost drivers. Function point analysis involves counting inputs, outputs, inquiries and files to determine unadjusted function points which are then adjusted based on technical complexity factors. Examples are provided to demonstrate estimating lines of code, effort, schedule and errors using these techniques.
Ultrasonic B Scan Laboratory Experiment GuidanceTony Toole
The document describes the process for remotely conducting an ultrasonic B-scan experiment to analyze a corroded pipe sample. It involves connecting to a university network via VPN, launching a remote desktop application, and using ultrasonic scanning software to capture and analyze a B-scan image of the pipe sample. The steps include initializing the ultrasonic interface, adjusting gain and gate settings, performing a scan to capture the image, and analyzing the image data to locate defects and measure wall thickness.
This document outlines the plan for an online exam system project. It will include objectives like allowing teachers to create exams and track student results. The project team consists of a project manager, software designer, analyst, programmer, and tester. Risks like staff turnover or budget issues are identified along with mitigation strategies. Hardware, software, and other resource requirements are specified. The work is broken down into tasks like contract negotiation, documentation drafting and review, requirements analysis, and implementation.
The document outlines a project plan for developing an online exam system. It discusses objectives to securely connect the system to institutional data and give users exam creation privileges. It also covers the project team roles, risks involving staffing, methodology, budget, and hardware, and software requirements including computers, internet, software licenses, and salaries. The work breakdown includes contracting with clients, drafting and rewriting documentation, requirements analysis, system design, programming, testing and deployment.
Stages of FMEA in Total Quality Management Dr.Raja R
This document outlines the 10 steps for conducting a Process Failure Mode and Effects Analysis (FMEA) as part of a Total Quality Management process. The steps include: 1) reviewing the process using a flowchart, 2) brainstorming potential failure modes, 3) listing potential effects of each failure, 4) assigning severity rankings, 5) assigning occurrence rankings, 6) assigning detection rankings, 7) calculating the Risk Priority Number, 8) developing an action plan, 9) taking action to implement improvements, and 10) recalculating the Risk Priority Number after improvements. Conducting a Process FMEA in a step-by-step manner allows each step to build upon the previous one for systematically analyzing potential failures, effects,
The document summarizes the key features of OMCS International's PMO2000TM Reliability Assurance Software Suite. It allows for reliability centered maintenance, risk analysis, integration with SAP systems, and customizable reporting. The software provides a complete solution for asset reliability from initial analysis through implementation and management.
This document provides an overview of computational fluid dynamics (CFD) and the general methodology for analyzing fluid dynamics problems using CFD. It discusses the three approaches to problem solving - analytical, experimental, and numerical. It describes what CFD is and how it uses numerical methods to obtain approximate solutions to problems involving fluid flow, mass transfer, and heat transfer. The document outlines the basic steps in setting up and solving a CFD problem using a commercial solver like ANSYS Fluent, including pre-processing, defining the physical models and boundary conditions, running the solver, and post-processing the results.
The Automation Firehose: Be Strategic & Tactical With Your Mobile & Web TestingPerfecto by Perforce
The document discusses strategies for effective test automation. It emphasizes taking a risk-based approach to prioritize what to automate based on factors like frequency of use, complexity of setup, and business impact. The document outlines approaches for test automation frameworks, coding standards, and addressing common challenges like technical debt. It provides examples of metrics to measure the effectiveness of test automation efforts.
The document discusses the importance and benefits of structured programming. It outlines seven key concepts of structured programming including structured walkthroughs, stepwise refinement, modular design, bottom-up coding, testing using stubs, white box and black box testing, and generating structured programming documents. It provides examples to illustrate concepts like branching, looping, and modular design. Structured programming helps produce programs that meet requirements, are easy to maintain, and avoid bugs.
This document provides instructions for using various tools within the MATLAB environment, including:
1) The Wavelet Toolbox for 1D and multi-signal wavelet analysis.
2) The Neural Network Toolbox for neural network fitting, clustering, and pattern recognition tools.
3) The Filter Design & Analysis Tool for designing high pass and notch filters.
4) Simulink for designing a PID controller. Step-by-step instructions are provided for using each tool.
- The document is an internship report by Valeria Marisol Cabriales Garza describing her project at OSRAM Opto Semiconductors developing a new measurement program using LabVIEW.
- She worked in the Development division programming an analyzer measurement workspace to modernize the interface and improve usability. The existing program was in an outdated language and did not have friendly interfaces.
- Her project involved designing a new program in LabVIEW to measure current and voltage of components and generate graphs of measurement results. This required managing complex interconnected databases and ensuring all program steps worked dynamically together.
Lte drivetest guideline with genex probeRay KHASTUR
1. Drive testing involves collecting radio frequency data through a test device to evaluate network coverage and quality of service parameters.
2. Major LTE key performance indicators measured include accessibility, retainability, mobility, and integrity. Key parameters measured are RSRP, SINR, and throughput.
3. To perform an effective drive test, the tester must understand parameter definitions, avoid duplicate routes, analyze events like call drops, and strategically test throughput in stable conditions.
1. Methodologies differ for each project and team, so a single methodology does not fit all. Managers need guidance to help teams create their own methodology using an evidence-based approach.
2. Methodologies have both formal parts like processes and meetings, as well as important informal parts like team collaboration. Simply mixing practices haphazardly is not effective.
3. Pattern languages can help by describing what works and what doesn't for a given context, explaining tradeoffs, and allowing the methodology to evolve with changing needs based on evidence.
EELE 5331 Digital ASIC DesignLab ManualDr. Yushi Zhou.docxtoltonkendal
This document outlines the procedures for a lab manual on digital ASIC design. It describes designing a single MOSFET transistor from schematic entry to post-layout simulation. Students are instructed on how to use Cadence software to create a schematic, perform pre-layout simulation using parametric and DC analysis, and generate layout of the transistor. The document provides step-by-step guidance on using key Cadence tools for simulation, layout, and verification of the transistor design.
Assignment Based on two topics:-
1.SRS Library Management`
2. Risks in designing a software
Made by :-
RAJAT MITTAL
JK INSTITUTE OF APPLIED PHYSICS & TECHNOLOGY, UNIVERSITY OF ALLAHABAD
This document provides an overview of problem solving and Python programming. It discusses computational thinking and problem solving, including identifying computational problems, algorithms, building blocks of algorithms, and illustrative problems. It also discusses algorithmic problem solving techniques like iteration and recursion. Finally, it briefly introduces the course titled "GE8151-PROBLEM SOLVING AND PYTHON PROGRAMMING".
GSM UMTS LTE Site Commissioning softwareAhmet Ozturk
Mobile network operators usually use internal macros and excel sheets to create scripts and xml files site commissioning. With Accela Cell Data Manager, it is very easy, fast and accurate to create OSS/M2000/Netact scritps in amos,mml and xml formats.
3. 3
Project Sponsor: Ernest P Caramanis
Specialist: Ali Nassib
Expert Mentor: Brain M Foley
1. Project Objective: To select a standard tool that is easy to use a synthesis
tool for spurious analysis.
2. Estimated Cost of Project: One man month.
3. Source of Funding: e.g. Expedition program.
4. Estimated benefit: Directly related to program synthesis.
5. Project Beneficiary: Both program and future Raytheon programs.
6. Estimated Project Timeline: Two man month.
Six Sigma Specialist Project:
4. 4
Visualize
• Need for change (Problem/Opportunity Statement)
Presently there is no single standard or efficient process to do spurious analysis
the present method is complex is prone to error.
• Vision of the future
A standardized process to do spurious analysis saving time and money for
every one.
5. 5
Commit
• Committed Sponsor: Ernest P Caramanis
• Committed: Ali Nassib
• Stakeholders:
1. Ernest P Caramanis
• Commitment:
– Sponsor commitment made in Nov 2009
– Completion goal is Dec 2009
6. 6
Prioritize
Analysis Tools available for spurious analysis
Matlab
Spectrasys
ADS
Excel and charts
Customer or User attributes
Tool ease of learning
Tool flexibility
Tool interface compatibility
Tool cost
Tool licensing
Technical Accuracy
7. 7
Project Plan
Steps Tasks Start End Hour
s
Who Results
Vision Completed
Commit Completed
Prioritize Completed
Characterize
What do we know now 11/20/09 11/23/09 Ali Nassib Get an idea from the
customer
What is the UDEs and root
cause
11/23/09 11/30/09 Ali Nassib Learn how the software
works and determine
UDEs
Identify High Leverage
Points QFD Matrix
11/30/09 11/03/09 Ali Nassib Compare the
information collected
Improve Spectrasys process 11/03/09 11/08/09 Ali Nassib Spectrasys
Achieve Create a template/process 12/08/09 12/15/09 Ali Nassib Save time
8. 8
Characterize
• Current process for flow chart
Complete the
analysis
by uploading
A matlab
Start
Start writing
the code
Run the
simulation,
graph it
And get a data
Time consuming, complicated, and
High opportunity for clerical error
9. 9
Characterize
• Current State:
Couple of programs are being used to do spurious analysis such as
Matlab, Excel, spurious charts, ADS and Spectrasys.
Therefore there is no single standard process to do spurious analysis
which led the following UDEs.
– Matlab is good for accuracy but its not as easy to use
Each problem requires new or modified code.
It requires also programming knowledge which every one
does not have.
– ADS could be used spurious analysis but it does not truncate the
Lowe level spurious signals, continuous to process insignificant
low level signals this results considerable longer simulation time
and more memory requirements
– Excel and spurious charts may be used however prone to error
due to manual interaction requirement.
10. 10
Characterize
• Root Causes
5 whys to determine the root causes
Engineer came up
a process to do spurious
analysis for every
new designReviewers are required to
use a new tool for
every new design analysis
Every engineer tries
to analyze
Spurious His/her own way
Analysis or
synthesis is too costly
There is no single
Standard process to
Do spurious analysis
Analysis or
synthesis is a time
Consuming task
11. 11
Identify High Leverage Points QFD Matrix
Customer needs
Customer
weight
Spectrasys Matlab ADS Excel & Charts
Tool easy of
learning 3 9 5 7 9
Tool flexibility 4 9 5 8 5
Tool interface
compatibility 5 9 5 8 5
Technical
Accuracy 5 9 9 9 7
Tool cost and
licensing 1 5 5 5 5
Scores 158 110 143 112
% of total 30% 21% 27.3% 21.4%
Ranking 1 4 2 3
As you can see the chart Spectrasys has more capability
then all other tools
12. 12
Spectrasys
Why Spectrasys over ADS
Spectrasys has a capability of truncating Lowe level spurious
signals
ADS does not have this capability and continuous to process
insignificant low level signals this results considerable longer
simulation time and more memory requirements
This also limits maximum number of mixer conversions which can
be handled
Spectrasys traces the origin of the spurious signals by simply
placing the mouse over the graphical spectra this is represented
as M*RF+N*LO
Spectrasys interfaces with a number of tools including ADS
Spectrasys more easily performs system level analysis as the roots
are already written and usable with clickable button
ADS purchased Spectrasys to simplify spectral analysis
13. 13
Improve
• Management and Control Systems
– What will make the implementation permanent?
Incorporate as requirement for PDR/CDR process
– Documentation and/or training requirements
Incorporate training through LMS or vender seminar session
lunch and learning
– How do I know I’ve actually improved anything?
Its when every one starts using spectrasy for spurious
analysis
– What are the metrics showing improvement?
Its when you can not log in easily and need more license
every time you want use spectrasys
14. 14
Improve
• Solution Chosen:
To use Spectrasys as a single standard tool when performing spurious
analysis
• Improvements made
time and money saved
Only one single standard tool needs to be learned to do
spurious
One single analysis could be done both spurious and
system analysis
A file from ADS or HFSS could be imported in to Spectrasys and
do all the analysis you need.
15. 15
Improve
Start spectrasys
Accept the default window
and give name by right clicking
the schematic
Type the name of the parts you
Want in the Filter By window
Which is on you right hand
Corner and place them in the
workspace
Connect the all the parts together
And double click to change
The parameters
Analyze by right clicking the design
And then selecting add and then
Selecting Analysis and then selecting
The type of analysis you want
Adding a graph right click the
Design, then select add, then
Select add graph
Complete the
analysis
16. 16
Process
• Start the Spectrasys
• Select a default from the template window and click okay
• Give a name called mixer by right clicking the schematic.
• Type continuous wave (CW) , Mixer, Power oscillator, Isolator, RF amplifier, Filter and out put port separately a place
called Filter By which is on your right hand corner and then place each part on the workspace.
• Connect all the parts together and then double click the part to change its parameters
• This is how it should look like
CW
Pwr=0dBm
F=60MHz
SRC_RF
Pwr=15dBm
F=580MHz
Part=NationalLMX2531LQ1146E3V@50mA
SRC_LO1
ZO=50Ω
Port_1
IL=0.5dB
Isolator_1
RI
L
LO=15dBm
ConvGain=-8dB
M1
NF=3dB
G=20dB
RFAmp_1
Fhi=550MHz
Flo=490MHz
N=7
IL=1dB
FL1
17. 17
Process
• Add another schematic called filter by right clicking Design then select add, then select design, then select add
schematic
• Type Input port, RF amplifier, Filter and Output port separately in the place called Filter By and then place them on
the new schematic.
• Then this is how it should look like
ZO=50Ω
Port_2
ZO=50Ω
Port_1
Fhi=550MHz
Flo=490MHz
N=7
IL=1dB
FL1
NF=3dB
G=12dB
RFAmp_1
18. 18
Process
• To analysis the filter, right click the design select add, then select analysis, then select add linear analysis, then a
window pops up choose start and stop frequency, type of sweep and number of points then click Calculate now and it
generates a data for you.
• To analysis the mixer, right click the design select add then select analysis then select add RF System analysis then a
window pops up click paths then click add all paths from all sources click options and type -80dBm in the level below
then go back to the general tap and click Calculate now and it then generates data.
• To add a graph, right click the design, then select add, then select add graph, a window pops up then click add button,
then select Spectrum from select type of series then click the linear data and select “S” which is “S21” by default
click okay, click add again then select Spectrum from the select type of series then click System Data and select
POUT which is output power of the mixer then click more measurements then go down and click Pnode which is the
power node then select Pout then click okay then click okay again then you get the graph you see below
20. 20
Achieve
• Spectrasis is a simple and has a robust analysis and should be
used as a common tool for spurious analysis
• A template is created with clear instruction of how to use this
standard tool
• No training is needed for this standard tool
• 0.1 of the time and 30k of money are saved based on 5 analysis
per year on 2.5 years
• We are trying to purchase more licenses
21. 21
R6s Tools Used on Project
• Lists of the R6s tools that is being applied:
– Interviews (Experts)
– UDEs
– Process Flow Chart
– Root Cause Analysis (5 Whys)
– Weighted Solution Matrix / QFD