|
|
|
Resources
|
|
Below is a list of 15 resource documents that are directly associated with the type of services provided by Pedalion. Please click on the thumbnail images to the right of the page to download the PDF files.
|
|
|
Masters Research Thesis (Vol I) - Conceptualisation and Automatic Generation of Test & Evaluation Master Plans (TEMPs) for Defence Acquisition Test Programs (DATPs)
This thesis investigates a method to support an important facet of the Test & Evaluation (T&E) process, in particular, the conceptualisation and consequent automation via the assistance of a computer, the manual generation of Test & Evaluation Master Plans, from the functional requirements specification of any defence acquisition test program, for the real-time test & evaluation (T&E) of complex systems, such as the highly instrumented fighter aircraft F/A-18 Hornet of the RAAF. The aim of the research was to reduce the performance risk associated with Systems Engineering (SE), Test & Evaluation (T&E) processes via a process known as Master Planned Test & Evaluation (MPT&E) for non-traditional regimented systems. A further aim was to produce a set of generic principles for applying as a set of guidelines to the various SE, T&E processes that would set up a framework in which to carry out performance risk management to any given process.
|
Masters Thesis (PDF 1.64M)
|
|
Back to top
|
|
|
Chapter One
Chapter 1 gives an introduction to the research undertaken, the aim of the research, a detailed background of the research and its contribution to Australia, and structure of the Thesis. The thesis details the work accomplished on the research project “Performance Risk Reduction for Systems Engineering, Test & Evaluation Processes”. John S. Nissyrios, working under the guidance of Professor Peter Sydenham at the Australian Centre for Test & Evaluation (ACTE) conducted this work. This research was conducted on a full-time basis at the Levels Campus of the University of South Australia (UniSA), over 1997 to 1999 inclusive.
|
Chapter 1
(PDF 40.4k)
|
|
Back to top
|
|
|
Chapter Two
The origins of Test & Evaluation are described in Chapter two, where the history, types of T&E, interests, reasons, importance, objectives and the need for conducting T&E are discussed. This Chapter hypothesises that T&E is essentially a process and synonymous to the systems engineering process, and as the phrase implies, a two part process, i.e., testing and evaluating.
|
Chapter 2
(PDF 163.6K)
|
|
Back to top
|
|
|
Chapter Three
Chapter three then outlines a brief genealogy of the discipline of this research, i.e., aircraft flight testing, giving a short introduction to flight test, flight test planning, test resources, and telemetry formats used in flight testing that could assist in the design of telemetry data formats. This Chapter reveals that T&E practitioners are taking more measurements than are required, and as a consequence increasing the cost of testing not to mention human resources required to carry out these tests, hence the importance of keeping tests simple, small, economical and manageable, i.e., adhering to the philosophy of parsimony.
|
Chapter 3
(PDF 217.1K)
|
|
Back to top
|
|
|
Chapter Four
Chapter four analyses and compares two most prominent T&E structures and processes, namely, that of the United States of America and Australia. It is determined that one of best documented T&E systems in the world, is that originating from to the United States of America and due to this fact, many non-US based countries have adopted its basic principles, terminology, and structure.
|
Chapter 4
(PDF 147K)
|
|
Back to top
|
|
|
Chapter Five
Chapter five gives a concise description on the research methodology utilised in the attempt to conceptualise and automate the Australian T&E process. The importance of adhering to and regularly updating a Test & Evaluation Master Plan (TEMP) is emphasised as the most vital part of any defence acquisition test program, as it outlines very crucial elements that all such test should adhere to.
|
Chapter 5
(PDF 129K)
|
|
Back to top
|
|
|
Chapter Six
Chapter six describes the results of this research, namely, a software tool known as AutoTEMP© Beta 2.0, outlining descriptions of all three modules, namely, the US defence phased acquisition process tutorial, the TEMP generation module, and the automatic generation of the TEMP document. It was designed to comply to the Australian Defence Force Capital Equipment Procurement Manual, often referred to as the CEPMAN 1, instruction.
|
Chapter 6
(PDF 430K)
|
|
Back to top
|
|
|
Chapter Seven
Chapter seven is essentially the conclusion and the recommendations for further research. This research was considered important as it was the first time ever that this problem has been researched using an academic methodology, as opposed to picking up from something well known. The development of this project has provided a tool that can save the agencies involved in high volume testing, hundreds of millions of dollars, due to a reduction in time, cost, and effort taken to manually produce a TEMP, whilst offering more thorough and reliable testing, as well as increasing confidence in the safety and predictability of complex systems, such as the highly instrumented fighter aircraft, F/A-18 Hornet.
|
Chapter 7
(PDF 39.9K)
|
|
Back to top
|
|
|
US Systems Engineering Fundamentals Guide 2001
This book provides a basic, conceptual-level description of engineering management disciplines that relate to the development and life cycle management of a system. For the non-engineer it provides an overview of how a system is developed. For the engineer and project manager it provides a basic framework for planning and assessing system development. The book is divided into four parts: Introduction; Systems Engineering Process; Systems Analysis and Control; and Planning, Organizing, and Managing .
|
US Systems
Engineering
Fundamentals
2001
(PDF 1.31M)
|
|
Back to top
|
|
|
Defence Test & Evaluation Guide 2008
The CDF has stated that his vision for the ADF is a ‘balanced, networked, and deployable force, staffed by dedicated and professional people, that operates within a culture of adaptability and excels at joint, interagency, and coalition operations. The aim of the Defence Test and Evaluation (T&E) Roadmap is to review the current Defence T&E capability, Defence’s strategic planning for future operating environments, and the future capability acquisition plan as detailed in the DCP 2006–2016, to ensure Defence’s T&E direction and resources will be adequate to assist in the delivery of the CDF’s vision. This document explains the benefits of T&E to Defence and how it can assist the capability development process. It considers Defence’s current T&E capability and policy, the level at which T&E is being performed, when it is undertaken, and what T&E resources are utilised. Importantly, the Roadmap considers the extent of the gaps and overlaps in the delivery of T&E which may impact on the delivery of DCP projects, and the resources that will be required to deliver these projects into service.
|
 Defence Test
&
Evaluation
Roadmap_2008
(PDF 9.35M)
|
|
Back to top
|
|
|
US Test & Evaluation Management Guide 2001
This book is one of many technical management educational guides written from a Department of Defense (DoD) perspective; i.e., non-Service peculiar. They are intended primarily for use in the courses at the Defense Systems Management College (DSMC), Defense Acquisition University (DAU), and secondarily as a desk reference for program and project management personnel. These guidebooks are written for current and potential acquisition management personnel who are familiar with basic terms and definitions employed in program offices. They are designed to assist government and industry personnel in executing their management responsibilities relative to the acquisition and support of defense systems.
|
US Test
&
Evaluation
Management
Guide 2001
(PDF 2.19M)
|
|
Back to top
|
|
|
US SMC Systems Engineering Handbook 2004
This Systems Engineering handbook is written to provide the US Air Force Space and Missile Systems Center (SMC) personnel with fundamental systems engineering concepts and techniques as they apply to space and launch systems and the SMC environment. The handbook was written with prior recognition that Systems Engineering subject matter is very broad and approaches to performing Systems Engineering varies greatly. This exposition is not intended to cover them all. It addresses general concepts and common processes, tools, and techniques that are mostly familiar to SMC. It also provides recommended Systems Engineering practices and pitfalls to avoid. Many references are provided for the reader to consult for more in-depth knowledge.
|
SMC Systems
Engineering
Handbook
(PDF 2.553M)
|
|
Back to top
|
|
|
NASA Systems Engineering Handbook 2007
This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. The handbook’s scope properly includes systems engineering functions regardless of whether they are performed by a manager or an engineer, in-house, or by a contractor.
|
NASA Systems Engineering Handbook 2007 (PDF 8.50M)
|
|
Back to top
|
|
|
Engineering Complex Systems
This book describes how to combine text descriptions and rigorous modeling to analyze and describe large or small complex systems. The systems engineering work begins with the needs of users, owners, and operators and with the realities of the marketplace. The systems engineering work transforms these needs into a description of a system architecture and design that specifies the components to be designed, implemented and integrated. The fundamental process for the engineering of systems is an optimization process. That process finds a near optimal solution for the system out of a multitude of possible solutions. The process produces rigorous descriptions of the near optimal solution by defining what the components are, what they must do, and how they interact to perform as a system. This book focuses on the technical engineering work of transforming needs to a near optimal system solution for complex systems that require multiple engineering disciplines to do the work.
|
Engineering
Complex Systems
(PDF 2.763M)
|
| Back to top |
|
|
Project Management Body of Knowledge 2000
Project Management is an emerging profession. The primary purpose of this document is to identify and describe that subset of the PMBOK that is generally accepted. Generally accepted means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. Generally accepted does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the Project management team is always responsible for determining what is appropriate for any given project. This document is also intended to provide a common lexicon within the profession and practice for talking and writing about project management. Project management is a relatively young profession, and while there is substantial commonality around what is done, there is relatively little commonality in the terms used. This document provides a basic reference for anyone interested in the profession of project management. This includes, but it not limited to:
- Senior executives.
- Managers of project managers.
- Project managers and other project team members.
- Project customers and other project stakeholders.
- Functional managers with employees assigned to project teams.
- Educators teaching project management and related subjects.
- Consultants and other specialists in project management and related fields.
- Trainers developing project management educational programs.
|
PMBOK
2000
(PDF 1.92M)
|
|
Back to top
|
|
|
