This document provides a functional specification for a Quality Assurance and Inspections Database. It outlines requirements for the user interface, data entry, search functions, reports, and administration. The database will consolidate existing quality inspection data and support electric, gas, vegetation management, and gas high pressure inspections. Requirements cover main screens, forms, checklists, searching, reporting, and user preferences. Section 4 provides specific requirements for electric site audits, including fields, checklists, inspection items, searchable fields, and reports.
This document provides an overview and instructions for using the SATAID Operation Manual. It describes the program environment, how to start and quit the program, main functions for basic and advanced operation including registering and displaying different data types, and additional options for customizing settings and outputs. The manual also covers creating case studies with explanation data and special functions for tropical cyclone analysis.
SAP_HANA_Modeling_Guide_for_SAP_HANA_Studio_enJim Miller, MBA
This document provides guidance on modeling with SAP HANA Studio. It discusses SAP HANA architecture including its in-memory columnar database and parallel processing. It then covers topics like importing data, creating information views using attributes, measures and different types of views. It also discusses working with attributes and measures, creating calculated columns and restricted columns, and assigning semantics. The document is a user guide for developing analytic models with SAP HANA Studio.
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgrading, and service integration. The book provides guidance on working with Launchpad, configuration, views, menus, actions, workflows, wizards, reports, translations, server actions, data import/export, web services, and more.
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgrading, and service integration. The book provides guidance on working with Launchpad, configuration, views, menus, actions, workflows, wizards, reports, translations, server actions, data migration/import/export, web services, and more.
This guide helps developers migrate Java applications from version 1.3 to 5.0. While many 1.3 applications run without changes, some compatibility issues exist as described in this guide. The guide covers runtime issues, deployment issues, and tooling issues to assist with the migration. Developers should consult this guide and release notes for any late-breaking issues when migrating applications to Java 5.0.
This guide helps developers migrate Java applications from version 1.3 to 5.0. While many 1.3 applications run without changes, some compatibility issues exist regarding runtime behavior, deployment changes, and tooling. The guide covers issues for all application developers as well as some primarily for platform implementers and tool developers. Developers should consult the guide and release notes for details on any needed changes.
This document provides an overview and guide for developing applications using Oracle Application Framework (OA Framework). It covers topics such as setting up the development environment, building a basic "Hello World" application, implementing models, views and controllers, internationalization, and more advanced topics like debugging, testing, standards and guidelines. The document contains 10 chapters and several appendices.
The document is the R Language Definition and provides details about the R programming language. It discusses the different types of objects in R like vectors, lists, and data frames. It also describes how expressions are evaluated in R through functions, control structures, arithmetic operations, and indexing. Permission is granted to distribute copies of the manual provided the copyright is preserved.
This document provides an overview and instructions for using the SATAID Operation Manual. It describes the program environment, how to start and quit the program, main functions for basic and advanced operation including registering and displaying different data types, and additional options for customizing settings and outputs. The manual also covers creating case studies with explanation data and special functions for tropical cyclone analysis.
SAP_HANA_Modeling_Guide_for_SAP_HANA_Studio_enJim Miller, MBA
This document provides guidance on modeling with SAP HANA Studio. It discusses SAP HANA architecture including its in-memory columnar database and parallel processing. It then covers topics like importing data, creating information views using attributes, measures and different types of views. It also discusses working with attributes and measures, creating calculated columns and restricted columns, and assigning semantics. The document is a user guide for developing analytic models with SAP HANA Studio.
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgrading, and service integration. The book provides guidance on working with Launchpad, configuration, views, menus, actions, workflows, wizards, reports, translations, server actions, data import/export, web services, and more.
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgrading, and service integration. The book provides guidance on working with Launchpad, configuration, views, menus, actions, workflows, wizards, reports, translations, server actions, data migration/import/export, web services, and more.
This guide helps developers migrate Java applications from version 1.3 to 5.0. While many 1.3 applications run without changes, some compatibility issues exist as described in this guide. The guide covers runtime issues, deployment issues, and tooling issues to assist with the migration. Developers should consult this guide and release notes for any late-breaking issues when migrating applications to Java 5.0.
This guide helps developers migrate Java applications from version 1.3 to 5.0. While many 1.3 applications run without changes, some compatibility issues exist regarding runtime behavior, deployment changes, and tooling. The guide covers issues for all application developers as well as some primarily for platform implementers and tool developers. Developers should consult the guide and release notes for details on any needed changes.
This document provides an overview and guide for developing applications using Oracle Application Framework (OA Framework). It covers topics such as setting up the development environment, building a basic "Hello World" application, implementing models, views and controllers, internationalization, and more advanced topics like debugging, testing, standards and guidelines. The document contains 10 chapters and several appendices.
The document is the R Language Definition and provides details about the R programming language. It discusses the different types of objects in R like vectors, lists, and data frames. It also describes how expressions are evaluated in R through functions, control structures, arithmetic operations, and indexing. Permission is granted to distribute copies of the manual provided the copyright is preserved.
Information extraction systems aspects and characteristicsGeorge Ang
This document provides a survey of information extraction systems and techniques. It discusses the main components and design approaches of information extraction, including manual and automatic pattern discovery. It also reviews several important prior information extraction systems and approaches to wrapper generation, including both supervised and unsupervised methods. The document serves to describe the state of the art in information extraction and provide an overview of the field.
Learn how IBM Redpaper publication is a comprehensive guide covering the IBM Power 770 and Power 780 servers supporting IBM AIX, IBM i, and Linux operating systems.For more information visit,http://ibm.co/Lx6hfc
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains an introduction, table of contents, and six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgradation/testing, and service-based integration. Each part contains multiple chapters that provide detailed information and instructions related to developing applications and customizing the OpenERP platform.
This document discusses various C++ concepts including primitive types, operators, control structures, arrays, pointers, strings, classes, inheritance, polymorphism and streams. It covers topics such as modulus operator, conversion between types, assignment operators, if/else, while loops, declaring and initializing arrays, passing arrays to functions, pointer declaration and arithmetic, constructors, destructors, access specifiers, operator overloading, method overriding, virtual functions, abstract base classes and stream input/output.
This document provides notes from a Linux system administration course. It covers topics like installing Red Hat Linux, configuring XFree86 for graphics, managing software packages, understanding the boot sequence, basic network concepts, kernel functions, configuring services, managing users and groups, working with filesystems, and basic security measures. The document contains detailed sections on partitioning and formatting disks, mounting filesystems, and using common Linux administration tools.
This document provides an overview and instructions for using ManageEngine ServiceDesk Plus, a help desk and asset management software. It covers system requirements and installation, configuration of various modules like requests, problems, changes, assets, and more. The document also discusses API integration, reporting, and other administrative features.
A guide to the top Outlook 2007 tips and tricks. This is the most popular/useful stuff I picked up over years of teaching people how to use Outlook 2007. If you use Outlook 2007 and want to be more productive, you want this document.
Includes links to relevant sections of: http://living-with-outlook.com
This document provides a copyright notice and table of contents for the Parallels Plesk Panel user guide. It details that the guide contains information on topics such as getting started with Plesk Panel, setting up websites and email, managing user accounts and hosting accounts, and configuring technologies like ASP.NET, PHP, and databases. The copyright is held by Parallels, Inc. and distribution of the work without permission is prohibited.
This document provides a service manual for a plasma TV. It includes sections on the tuner, IF part, multi-standard sound processor, video switch, audio amplifier stage, power supply, microcontroller, EEPROM, headphone driver, SAW filters, and descriptions of various integrated circuits used in the TV. Diagrams of the block diagram and circuitry are provided.
This document provides an overview and instructions for using WebHost Manager, a control panel for managing web hosting servers and accounts. It describes how to install and log into WebHost Manager, configure server settings like backups and quotas, and manage user accounts including creating, modifying, suspending, and deleting accounts. The document is organized into sections covering installation, server setup, support, backups, reboots, status checks, and account functions.
StresStimulus Load Testing Tool User Guidestresstimulus
StresStimulus is a stress testing tool which provides an easy way to test websites of any complexity, mobile and enterprise applications. This is the StresStimulus User Guide.
This document provides an overview and introduction to the Data Services Management Console: Administrator Guide. It welcomes the reader to Data Services XI Release 3 and lists the documentation set. It describes how to access the documentation on Windows and UNIX systems as well as from the Business Objects website. Finally, it provides Business Objects' information resources for customer support, consulting, training, and submitting documentation feedback.
This document provides an overview of HTML, CSS, Bootstrap, JavaScript and jQuery. It covers topics such as basic HTML tags and attributes, CSS selectors and properties, Bootstrap's grid system and components, JavaScript keywords and data types, and how to use jQuery. The document is intended as a reference for learning these web development languages and frameworks.
This document is the user guide for EViews 6. It covers copyright information and the disclaimer, then provides a table of contents outlining the guide's chapters which cover topics like the basics of EViews, workfiles, objects, data handling, and more advanced features. The guide is intended to help users learn how to use EViews for tasks like importing data, estimating models, testing hypotheses, and forecasting. It provides instructions and explanations throughout.
Sg247692 Websphere Accounting Chargeback For Tuam Guidebrzaaap
This document provides guidance on implementing IBM Tivoli Usage and Accounting Manager V7.1. It discusses planning the implementation, including account code structure, collector selection, and report requirements. It then covers installing and configuring the application server, database, and collectors. The document provides details on configuring users, clients, rates, and other system elements. Its goal is to help users successfully set up and verify an IBM Tivoli Usage and Accounting Manager V7.1 environment.
This document is the CakePHP Cookbook documentation for version 2.x. It contains 14 chapters that provide tutorials and documentation on getting started with CakePHP, installing and configuring it, building models, views, controllers and using core libraries. The document covers topics such as the MVC framework, routing, debugging, testing, deployment and more. It is intended as a technical reference for developing applications with CakePHP.
The document provides specifications for Seagate Momentus 54 hard disk drives, including the ST94011A, ST92011A, ST94811A, and ST92811A models. It details the drives' formatted capacity, physical organization, recording interface technology, power consumption, environmental tolerances, agency certifications, ATA interface, and compatibility information. Revisions to the document are tracked in a revision status summary sheet.
The document introduces Universal Building Solutions' new construction method called the Integrated Building System (IBS). The IBS uses expanded polystyrene (EPS) insulation and a magnesium oxide coating to produce building materials like wall blocks, flooring panels, and beams. The system aims to provide faster, more affordable and environmentally friendly construction. It claims to reduce costs by 30-50% and construction time by up to 70% compared to conventional methods. The EPS and magnesium oxide materials provide benefits like insulation, fire resistance, and strength. Universal Building Solutions sees opportunities to license their technology globally to address issues like rising construction costs and environmental pollution from brick manufacturing.
The document outlines specifications for a bank management system that allows customers to manage their bank accounts. The system will allow customers to create accounts, deposit and withdraw funds, and view reports. It provides requirements for the system's functionality, users, and hardware/software needs. The system is intended to help banks manage customer accounts and transactions.
Terminology Matching of Requirements Specification Documents and Regulations ...Shinpei Hayashi
The document presents a technique for systematically checking compliance between requirements specifications and regulations by matching terminology. It involves detecting concepts in requirements documents and regulations, instantiating property templates to represent semantic relationships, and checking consistency using a model checker. The technique was implemented and tested on two case studies, demonstrating its ability to identify compliance violations. However, some failures occurred due to structural differences in case frames and relationships between formulas. Future work aims to improve matching accuracy through larger case studies.
This document provides a high-level overview of the design and functional specifications for a STEM (Science, Technology, Engineering, and Math) web application. It describes the application's logical architecture with separate layers for the presentation layer, controller, model, and data layers. It also outlines the key technologies used including ASP.NET, C#, and SQL Server. The document discusses the MVC framework that will be used and defines the roles of controllers and actions. It provides a high-level view of the application components in each layer and describes the user interface elements and processes.
Information extraction systems aspects and characteristicsGeorge Ang
This document provides a survey of information extraction systems and techniques. It discusses the main components and design approaches of information extraction, including manual and automatic pattern discovery. It also reviews several important prior information extraction systems and approaches to wrapper generation, including both supervised and unsupervised methods. The document serves to describe the state of the art in information extraction and provide an overview of the field.
Learn how IBM Redpaper publication is a comprehensive guide covering the IBM Power 770 and Power 780 servers supporting IBM AIX, IBM i, and Linux operating systems.For more information visit,http://ibm.co/Lx6hfc
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains an introduction, table of contents, and six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgradation/testing, and service-based integration. Each part contains multiple chapters that provide detailed information and instructions related to developing applications and customizing the OpenERP platform.
This document discusses various C++ concepts including primitive types, operators, control structures, arrays, pointers, strings, classes, inheritance, polymorphism and streams. It covers topics such as modulus operator, conversion between types, assignment operators, if/else, while loops, declaring and initializing arrays, passing arrays to functions, pointer declaration and arithmetic, constructors, destructors, access specifiers, operator overloading, method overriding, virtual functions, abstract base classes and stream input/output.
This document provides notes from a Linux system administration course. It covers topics like installing Red Hat Linux, configuring XFree86 for graphics, managing software packages, understanding the boot sequence, basic network concepts, kernel functions, configuring services, managing users and groups, working with filesystems, and basic security measures. The document contains detailed sections on partitioning and formatting disks, mounting filesystems, and using common Linux administration tools.
This document provides an overview and instructions for using ManageEngine ServiceDesk Plus, a help desk and asset management software. It covers system requirements and installation, configuration of various modules like requests, problems, changes, assets, and more. The document also discusses API integration, reporting, and other administrative features.
A guide to the top Outlook 2007 tips and tricks. This is the most popular/useful stuff I picked up over years of teaching people how to use Outlook 2007. If you use Outlook 2007 and want to be more productive, you want this document.
Includes links to relevant sections of: http://living-with-outlook.com
This document provides a copyright notice and table of contents for the Parallels Plesk Panel user guide. It details that the guide contains information on topics such as getting started with Plesk Panel, setting up websites and email, managing user accounts and hosting accounts, and configuring technologies like ASP.NET, PHP, and databases. The copyright is held by Parallels, Inc. and distribution of the work without permission is prohibited.
This document provides a service manual for a plasma TV. It includes sections on the tuner, IF part, multi-standard sound processor, video switch, audio amplifier stage, power supply, microcontroller, EEPROM, headphone driver, SAW filters, and descriptions of various integrated circuits used in the TV. Diagrams of the block diagram and circuitry are provided.
This document provides an overview and instructions for using WebHost Manager, a control panel for managing web hosting servers and accounts. It describes how to install and log into WebHost Manager, configure server settings like backups and quotas, and manage user accounts including creating, modifying, suspending, and deleting accounts. The document is organized into sections covering installation, server setup, support, backups, reboots, status checks, and account functions.
StresStimulus Load Testing Tool User Guidestresstimulus
StresStimulus is a stress testing tool which provides an easy way to test websites of any complexity, mobile and enterprise applications. This is the StresStimulus User Guide.
This document provides an overview and introduction to the Data Services Management Console: Administrator Guide. It welcomes the reader to Data Services XI Release 3 and lists the documentation set. It describes how to access the documentation on Windows and UNIX systems as well as from the Business Objects website. Finally, it provides Business Objects' information resources for customer support, consulting, training, and submitting documentation feedback.
This document provides an overview of HTML, CSS, Bootstrap, JavaScript and jQuery. It covers topics such as basic HTML tags and attributes, CSS selectors and properties, Bootstrap's grid system and components, JavaScript keywords and data types, and how to use jQuery. The document is intended as a reference for learning these web development languages and frameworks.
This document is the user guide for EViews 6. It covers copyright information and the disclaimer, then provides a table of contents outlining the guide's chapters which cover topics like the basics of EViews, workfiles, objects, data handling, and more advanced features. The guide is intended to help users learn how to use EViews for tasks like importing data, estimating models, testing hypotheses, and forecasting. It provides instructions and explanations throughout.
Sg247692 Websphere Accounting Chargeback For Tuam Guidebrzaaap
This document provides guidance on implementing IBM Tivoli Usage and Accounting Manager V7.1. It discusses planning the implementation, including account code structure, collector selection, and report requirements. It then covers installing and configuring the application server, database, and collectors. The document provides details on configuring users, clients, rates, and other system elements. Its goal is to help users successfully set up and verify an IBM Tivoli Usage and Accounting Manager V7.1 environment.
This document is the CakePHP Cookbook documentation for version 2.x. It contains 14 chapters that provide tutorials and documentation on getting started with CakePHP, installing and configuring it, building models, views, controllers and using core libraries. The document covers topics such as the MVC framework, routing, debugging, testing, deployment and more. It is intended as a technical reference for developing applications with CakePHP.
The document provides specifications for Seagate Momentus 54 hard disk drives, including the ST94011A, ST92011A, ST94811A, and ST92811A models. It details the drives' formatted capacity, physical organization, recording interface technology, power consumption, environmental tolerances, agency certifications, ATA interface, and compatibility information. Revisions to the document are tracked in a revision status summary sheet.
The document introduces Universal Building Solutions' new construction method called the Integrated Building System (IBS). The IBS uses expanded polystyrene (EPS) insulation and a magnesium oxide coating to produce building materials like wall blocks, flooring panels, and beams. The system aims to provide faster, more affordable and environmentally friendly construction. It claims to reduce costs by 30-50% and construction time by up to 70% compared to conventional methods. The EPS and magnesium oxide materials provide benefits like insulation, fire resistance, and strength. Universal Building Solutions sees opportunities to license their technology globally to address issues like rising construction costs and environmental pollution from brick manufacturing.
The document outlines specifications for a bank management system that allows customers to manage their bank accounts. The system will allow customers to create accounts, deposit and withdraw funds, and view reports. It provides requirements for the system's functionality, users, and hardware/software needs. The system is intended to help banks manage customer accounts and transactions.
Terminology Matching of Requirements Specification Documents and Regulations ...Shinpei Hayashi
The document presents a technique for systematically checking compliance between requirements specifications and regulations by matching terminology. It involves detecting concepts in requirements documents and regulations, instantiating property templates to represent semantic relationships, and checking consistency using a model checker. The technique was implemented and tested on two case studies, demonstrating its ability to identify compliance violations. However, some failures occurred due to structural differences in case frames and relationships between formulas. Future work aims to improve matching accuracy through larger case studies.
This document provides a high-level overview of the design and functional specifications for a STEM (Science, Technology, Engineering, and Math) web application. It describes the application's logical architecture with separate layers for the presentation layer, controller, model, and data layers. It also outlines the key technologies used including ASP.NET, C#, and SQL Server. The document discusses the MVC framework that will be used and defines the roles of controllers and actions. It provides a high-level view of the application components in each layer and describes the user interface elements and processes.
This document provides a functional specification for a Kodak website. It outlines the purpose, scope, assumptions, constraints, and dependencies of the project. It describes the organization developing the website and the intended users. The document also defines sections for functional and non-functional requirements, system requirements, data requirements, external interfaces, and design constraints. It aims to capture all necessary requirements to develop the Kodak website to meet stakeholder needs.
Functional specifications are formal documents that describe a product's intended capabilities, appearance, and user interactions in detail for software developers. They enable expectations to be managed and streamline the development process by providing complete requirements for developers to build from without ambiguity. The functional specification analyzes user requirements, desired look and feel, customization options, and how new users will interact with the website and its business processes. Creating effective functional specifications involves fixing system boundaries, identifying stakeholders, eliciting requirements from them, analyzing gathered requirements, and managing requirements throughout the project.
This document is a functional specification for a project with the purpose of describing the functions and scope. It includes sections for an introduction, scope overview, and a list of functions. The introduction defines the purpose and references other documents. The scope overview describes the project and lists any constraints or assumptions. The list of functions section defines each function with a description, process flow, and field details.
A functional specification describes a product's intended capabilities, appearance, and user interactions in detail for software developers. It includes requirements defined by product planners based on market and customer input, objectives written by designers in response to requirements, a logic specification of code modules and structure, and user documentation derived from previous documents to instruct users. Ideally, the final product fully implements the functional specification and design changes identified during testing.
This document provides an overview of the configuration and advanced operation capabilities of the OMNI 6000/3000 flow computer firmware revisions 22.74 and 26.74. It describes how to configure physical inputs and outputs, meter stations, meter runs, temperature, pressure, density, products, batches, and other parameters using the keypad in program mode. It also covers user-programmable functions including Boolean flags, variables, and display screens. Finally, it details the flow equations and algorithms used to calculate flow rates and properties for liquid hydrocarbons in US customary and SI metric units.
This document is a user guide for the LSI SAS2 Integrated RAID solution. It describes the benefits of the integrated RAID solution such as host interface support, metadata support, SMART support, and Fusion-MPT support. It also provides overviews of how mirrored volumes operate and their key features like resynchronization, hot swapping, hot spares, online capacity expansion, and more. The document includes steps for creating mirrored volumes, managing hot spare disks, and other administrative tasks.
This document provides an overview of upgrading from Windows 2000 to Windows Server 2003. It discusses choosing the best edition of Windows Server 2003 based on equivalent Windows 2000 editions. It also covers verifying system requirements and hardware compatibility. Additional topics include deciding between upgrade, clean installation, or migration and considerations for Active Directory, applications, and server roles.
The document provides an overview of SAP architecture, servers, work processes, and other key components. It discusses the presentation layer, application layer, and database layer. It describes the different types of work processes like dialogue, update, enque, background, message server, and gateway. It also covers servers and instances, and screenshots of SM51 and SM50 are included to show active servers and work process overview.
TortoiseSVN is a Windows client for Subversion version control. It provides features for importing and exporting files to a repository, checking out working copies, committing changes, updating working copies, and viewing project history. The document discusses TortoiseSVN's installation, basic version control concepts, repository creation and management, daily use features like committing and updating, and resolving conflicts. It is intended as a user guide for getting started with and using TortoiseSVN for source control management.
The document provides an overview and administrator guide for OnTime 2008 project management software. It discusses the OnTime product line including OnTime for Windows, Web Edition, VS.NET, Customer Portal, and Remote Server. It also covers installing and setting up OnTime, including planning deployment, installing OnTime and its components, setting up the OnTime database, configuring system options and email notifications.
The Tellurium Automated Testing Framework (Tellurium) is a UI module-based automated testing framework for web applications and it is robust, expressive, flexible, and reusable. This is Tellurium 0.6.0 User Guide.
This document provides guidelines for rating search results from different queries. It discusses understanding the intent of queries, such as whether the user wants factual information, a website to take action, or a specific website to visit. It also discusses the rating scale for evaluating search results from "Vital" to most helpful down to "Off-Topic or Useless." Specific examples are given for properly applying the ratings. The document also provides guidance on when to flag results as spam, pornographic, or malicious.
As a Search Quality Rater, you will work on many different types of rating projects. These guidelines cover just one type of search quality rating – URL rating.
Please take the time to carefully read through these guidelines. The ideas presented here are important for other types of rating. When you can do URL rating, you will be well on your way to becoming a successful Search Quality Rater!
This document provides guidelines for rating search results from various queries. It discusses understanding user intent, such as queries seeking an action, information or navigation. It also covers the rating scale from Vital to Off-Topic or Useless. Specific guidelines are given for rating search results from queries on topics like entities, people and locations. Considerations for non-English queries and landing pages are also covered. The document discusses common rating challenges and provides examples to illustrate how to apply the ratings. It concludes by addressing how to flag spam, pornography or malicious search results.
This document is the Open Object Developer Book, Release 1.0 published by Tiny SPRL. It contains six parts that cover getting started with OpenERP, module development, business process development, advanced business process configuration, migration/upgrading, and service integration. The book provides guidance on working with Launchpad, configuration, views, menus, actions, workflows, wizards, reports, translations, server actions, data migration/import/export, web services, and more.
This document discusses service oriented architecture (SOA) and its application in real world systems. It begins with an introduction to SOA concepts like services, reuse, and loose coupling. It then discusses common architectural capabilities like messaging, workflow, data management and user experience that are important in SOA. The document provides an abstract reference model for SOA and shows how the common capabilities relate to the model's phases of expose, compose and consume. Later chapters discuss specific capabilities like messaging and workflow in more depth and provide examples.
The document provides information about implementing the IBM Storwize V3700 storage system. It includes an overview of the hardware components and features of the Storwize V3700. The document also covers initial configuration tasks such as planning the hardware and network setup, performing the first-time setup, and configuring features like expansion enclosures, alerts, and inventory. It provides guidance on using the graphical and command-line interfaces to manage and monitor the storage system.
Implementing the
IBM Storwize V3700
Easily manage and deploy systems
with embedded GUI
Experience rapid and flexible
provisioning
Protect data with remote
mirroring
This document provides an overview and implementation guide for Juniper's Loop-Free Alternate feature, which provides sub-50ms convergence for OSPF and IS-IS networks. It describes the problem of slow convergence in IGP networks and introduces LFA as a solution. The document outlines the operational theory and implementation of LFA, including configuration steps and verification procedures. It also includes examples and details on how LFA provides backup coverage and fast rerouting in the event of link failures.
This document provides an overview of IBM's MobileFirst strategy and solutions. It describes IBM's MobileFirst platform, which includes tools for developing, integrating, deploying, managing, securing and testing mobile applications. It also discusses IBM's strategy, software and services for enabling enterprise mobility. Practical scenarios demonstrate how to use IBM Worklight to develop a mobile app and integrate it with backend systems and services.
The document is a manual for Tivoli Business Systems Manager Version 2.1. It provides an overview of the product, which allows for end-to-end business impact management through integrated systems management. The manual details the product structure, components, functions, database structure, user interface, and planning requirements for implementation. It is intended to help users understand and implement the key capabilities of Tivoli Business Systems Manager.
ZW3D 2013 includes improvements to the user interface, visualization, data exchange, sketching, modeling, assembly management, layer management, wrapping tools, analysis tools, unfolding tools, and 2D sheet creation. Key updates include a multi-window display, enhanced constraint handling in sketches, a more organized assembly manager, new wrapping functions, an upgraded sheet manager, and improved dimensioning and viewing capabilities.
This document provides an administrator manual for Atoll version 3.1.0. It discusses installing and configuring Atoll and its components, setting up distributed calculation servers, managing licenses, and working with Atoll databases. The manual is divided into several sections covering topics such as supported technologies, installation, license management, database management, and more.
This document provides an overview and best practices for tuning the performance of IBM Content Manager. It introduces Content Manager components and architecture. It covers monitoring and tracing tools, and techniques for troubleshooting performance issues. It provides checklists and details for tuning the base products Content Manager relies on, including DB2, WebSphere Application Server, and Tivoli Storage Manager. Finally, it discusses planning, design, and configuration considerations for optimizing a Content Manager system's performance.
This document appears to be part of a 2003 performance appraisal for an individual contributor. It provides definitions for rating competencies as "role model," "proficient," or "developing." It then lists several competencies - including adaptability, contributing to team success, decision making, building partnerships, communication, customer focus, and technical/professional knowledge. For each competency, it lists key behaviors that characterize someone at the "role model," "proficient," and "developing" levels. The form is for assessing an employee's demonstration of these competencies and determining an overall performance rating.
This document is a 2003 performance appraisal form for an employee. It includes sections for setting goals using SMART criteria, commenting on progress mid-year and achievement at year-end, and assigning weights to individual goals. There are also sections for an individual training plan and an overall summary rating from the manager.
Risk Analysis and Management Process Flow ChartKathy Vinatieri
This document outlines a risk analysis process involving evaluating whether the benefits of an activity outweigh the risks, determining if risks can be reduced, and if overall risks and residual risks are acceptable. It involves identifying hazards, evaluating risks, implementing and documenting risk control measures, and continuing to gather information to re-evaluate risks.
Broadband Solutions Group (BSG) is Sony's organization that provides integration and development services for broadband operators. BSG's engineering staff conduct system analysis, project management, system design, system development, and system integration for customers. Their services include requirements analysis, project planning, distributed system architecture, quality assurance testing, and on-site integration. BSG has enabled technologies for major North American content providers such as video on demand, user interfaces, and set-top box platforms.
The document outlines a process for closing a record in a database. It first checks if the record has unsaved changes and prompts the user to save or discard the changes. If the user clicks discard, it confirms the discard. If the user clicks save, it validates the changes and saves if valid, otherwise warns the user to correct errors. It then notifies the user that changes were saved or discarded before closing the record.
System Center Cloud Services Process Pack Operations GuideKathy Vinatieri
This document provides procedures for common tasks in the System Center Cloud Services Process Pack, including registering and managing tenants, subscribing to and managing cloud resources, and requesting and updating virtual machines. Key terms are also defined, such as tenant, cloud resources, cloud resources subscriptions, and request offerings. The guide contains step-by-step instructions for completing service requests through the Microsoft System Center Service Manager Self-Service Portal.
This document provides instructions for Pacific Sales employees on processing sales orders in their system. It covers entering customer and order information, adding parts and accessories to the order, applying discounts, recording payment methods, and completing the order entry process. The steps provided include finding the customer, adding new customers, entering shipping and payment details, looking up reward accounts, and processing different order types such as cash, check, credit card, or warranty purchases.
The document outlines the deployment process for new IT projects from initial request through final completion. It involves capacity planning, networking design, hardware procurement, rack installation, configuration, testing, and approval stages managed by various teams including the requester, project manager, network manager, network engineer, and datacenter services. The process aims to methodically provision all necessary infrastructure and obtain approvals before new systems go live.
A customer wants to purchase a product. The sales associate checks product inventory and writes up a manual sales order if it is available. They then enter the order into the system. If the store is a standalone store, the front counter enters the purchase. Otherwise, sales staff enter it. The front counter or sales staff then capture customer information, use the release menu to take payment, which generates a release number. They enter this into the shipping screen to complete the transaction.
The system shall provide a user-friendly interface.
Not testable: "User-friendly" is subjective. What criteria define
"user-friendly"?
Rewritten:
The system interface shall:
- Allow navigation using a maximum of 3 mouse clicks between any two screens.
- Provide context-sensitive help accessible from any screen with a single click.
- Use terminology consistent with common user expectations.
- Present information in a format that minimizes eye and cursor movements.
These criteria make "user-friendly" objective and testable.
The document discusses Sony's Broadband Solutions Group (BSG) and the services it provides to help broadband operators succeed. BSG offers a range of consulting, integration, and support services to assist with projects like interactive programming, gaming, customer information applications, and developing new revenue streams like video on demand. BSG leverages Sony's expertise and coordinates with other Sony groups. It has experience helping major cable and satellite providers expand their service offerings and exceed expectations.
System Center Cloud Services Process Pack Administration GuideKathy Vinatieri
The document provides instructions for installing and configuring the System Center Cloud Services Process Pack. It outlines the required prerequisites, including installing System Center 2012 products. It then describes how to install the Cloud Services Process Pack on the Service Manager server and how to install the Cloud Services runbooks on the Orchestrator server. The document provides various configuration and administration tasks that must be completed to fully implement the cloud services solution.
This document outlines the database implementation for Lore 'n' More bookstore. It includes entity relationship diagrams and descriptions of tables like Book, Customer, Sales Order, etc. Form and report designs are also provided like the Customer Entry Form, Sales Order Entry Form, and Retail Sales Report. The goal is to improve tracking of inventory, sales, customers and suppliers with a cloud-based database system.
2. Puget Sound Energy Page 2 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Revision History:
Version Date Description Contributor
v0.01 Mm/dd/2009 Original Draft Business Unit Manager
v0.02 9/22/2009 1
st
Draft uploaded to SharePoint Kathy Vinatieri
3. Puget Sound Energy Page 3 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Table of Contents
1 Introduction.......................................................................................................................................... 6
1.1 Overview.................................................................................................................................. 6
1.2 Purpose ................................................................................................................................... 6
1.3 Audience.................................................................................................................................. 6
2 Overall Description............................................................................................................................... 7
2.1 Product Constraints ................................................................................................................. 7
2.1.1 Hardware Interfaces ................................................................................................ 7
2.1.2 Assumptions and Dependences.............................................................................. 7
2.2 Primary Product Requirements................................................................................................ 7
2.3 User Requirements.................................................................................................................. 8
2.3.1 Electric, Gas Site Audit and Gas High Pressure User Requirements ...................... 8
2.3.2 Vegetation Management User Requirements.......................................................... 9
2.4 User Interfaces ........................................................................................................................ 9
2.4.1 Electric, Gas Site Audit and Gas High Pressure User Interfaces............................. 9
2.4.2 Vegetation Management User Interface .................................................................. 9
2.5 New Release Requirements for Electric, Gas Site Audit and Gas High Pressure ................. 10
2.5.1 Database Consolidation......................................................................................... 10
2.5.2 Database Upload................................................................................................... 10
2.5.3 Fully Displayed Checklist....................................................................................... 10
2.5.4 Cloning an Existing Audit....................................................................................... 10
2.5.5 Reporting Enhancement........................................................................................ 10
2.5.6 Data Tool Enhancement........................................................................................ 10
2.5.7 User Preferences Form ......................................................................................... 10
2.6 Release Requirement - Vegetation Management.................................................................. 10
2.7 Proposed Future Requirements............................................................................................. 10
2.7.1 SAP Enhancement ................................................................................................ 10
3 High Level Requirements................................................................................................................... 11
3.1 User Interface Elements ........................................................................................................ 11
3.1.1 Buttons .................................................................................................................. 11
3.1.2 Special Buttons...................................................................................................... 11
3.1.3 Required Fields ..................................................................................................... 11
3.1.4 Non-applicable Fields ............................................................................................ 11
3.1.5 Window Functionality............................................................................................. 11
3.1.6 Tab Order .............................................................................................................. 11
3.1.7 Print Functionality .................................................................................................. 12
3.1.8 Navigation.............................................................................................................. 12
3.1.9 Background Color.................................................................................................. 12
3.2 Main Screen .......................................................................................................................... 13
3.2.1 Inspection Type ..................................................................................................... 13
3.2.2 Inspector Options/Function Availability.................................................................. 14
3.2.3 Administrator Function Availability......................................................................... 14
3.3 Create Records - Data Entry Form ........................................................................................ 14
3.3.1 Data Entry Form Buttons ....................................................................................... 15
3.3.2 Electric, Gas, Gas HP Data Entry Form Prototype ................................................ 16
4. Puget Sound Energy Page 4 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.3.3 Vegetation Entry Form Prototype .......................................................................... 17
3.4 Checklist................................................................................................................................ 18
3.4.1 Checklist Buttons................................................................................................... 18
3.4.2 Checklist Columns................................................................................................. 18
3.4.3 Checklist Tables .................................................................................................... 18
3.5 Search ................................................................................................................................... 19
3.5.1 Search Buttons...................................................................................................... 19
3.5.2 Electric, Gas, Gas High Pressure Search Filters ................................................... 20
3.5.3 Vegetation Search Filters ...................................................................................... 20
3.6 Data Tool............................................................................................................................... 21
3.6.1 Data Tool Buttons.................................................................................................. 21
3.6.2 Query Results Summary........................................................................................ 22
3.6.3 Inspection Items Summary .................................................................................... 22
3.6.4 Resolution Tracker ................................................................................................ 22
3.7 Reports.................................................................................................................................. 23
3.7.1 Report Selection Screens...................................................................................... 23
3.7.2 Report Criteria Screen........................................................................................... 24
3.7.3 Report Button, Link and Icon ................................................................................. 24
3.7.4 Report View Screen............................................................................................... 25
3.8 Administration........................................................................................................................ 25
3.9 User Preferences Form ......................................................................................................... 25
4 Specific Requirements....................................................................................................................... 26
4.1 Electric Site Audit................................................................................................................... 26
4.1.1 Data Entry Screen Fields....................................................................................... 26
4.1.2 Checklist Columns................................................................................................. 27
4.1.3 Checklist Tables .................................................................................................... 29
4.1.4 Electric Site Audit Inspection Items ....................................................................... 30
4.1.5 Search: Searchable Fields.................................................................................... 31
4.1.6 Data Tool: Searchable Fields ............................................................................... 31
4.1.7 Electric Reports & Queries .................................................................................... 32
4.1.8 Report Terminology Changes................................................................................ 33
4.2 Gas Site Audit........................................................................................................................ 34
4.2.1 Data Entry Screen Fields....................................................................................... 34
4.2.2 Checklist Columns................................................................................................. 35
4.2.3 Checklist Tables .................................................................................................... 37
4.2.4 Gas Site Audit Inspection Items............................................................................. 38
4.2.5 Search: Searchable Fields.................................................................................... 39
4.2.6 Data Tool: Searchable Fields ............................................................................... 39
4.2.7 Reports.................................................................................................................. 40
4.3 Gas High Pressure ................................................................................................................ 42
4.3.1 Data Entry Screen Fields....................................................................................... 42
4.3.2 Checklist Columns................................................................................................. 43
4.3.3 Checklist Table...................................................................................................... 44
4.3.4 Gas High Pressure Inspection Items ..................................................................... 45
4.3.5 Search: Searchable Fields.................................................................................... 46
4.3.6 Data Tool: Searchable Fields ............................................................................... 46
4.3.7 Reports.................................................................................................................. 46
5 Appendix............................................................................................................................................ 49
5.1 Report Prototypes.................................................................................................................. 49
5. Puget Sound Energy Page 5 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
5.1.1 Deviations by Classification................................................................................... 49
6. Puget Sound Energy Page 6 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
1 Introduction
1.1 Overview
The Puget Sound Energy Quality Assurance and Inspections (QA&I) group uses Access
databases with a SQL backend for recording, storing, tracking and reporting audit and inspection
information. The Access databases have been used longer than planned and are near or at
capacity.
Currently Electric, Gas, and Gas High Pressure inspection data is being stored on several Access
databases which are input into three SQL databases. These databases often become out of
synch due to product limitations. The current Access database reporting tools were initially
designed over 5 years ago with the assumption that the technology would not exceed 5 years.
Design limitations are affecting data capture and reporting capabilities.
In the current system the reports and queries are separate. In the new system the reports and
queries should be combined into one single interface.
Vegetation inspection data is currently being stored in Excel spreadsheets. This data needs to be
entered into a database for improved tracking, detailed reporting and data storage.
A new program has been funded to replace the system that uses Access.
1.2 Purpose
This document defines the functionality of the new system.
1.3 Audience
This document is intended for IT, including but not limited to the business unit owner, technical
owner and other supporting entities.
7. Puget Sound Energy Page 7 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
2 Overall Description
QA&I Inspectors perform field audits and inspections of construction and maintenance work. The
results need to be reported to management.
PSE management needs to be able to provide reports to executives and regulatory agencies.
2.1 Product Constraints
Inspectors must have the ability to upload data while within wireless network range.
When out of wireless network range inspectors will have the capability of entering data into a form
that will be up loadable when the inspector reenters wireless network range.
2.1.1 Hardware Interfaces
The client application should reside on inspector’s laptops running Microsoft Windows
Operating System.
2.1.2 Assumptions and Dependences
This program assumes that:
All inspector laptops are running the Windows Operating System
All laptops have wireless capability
2.2 Primary Product Requirements
These are the primary product requirements;
1. Users need to be able to input and edit inspection results onto their laptops while out in the
field.
2. The inspection results must be able to be uploaded to a SQL database via the Internet.
3. Users must be able to create reports when connected to the network.
8. Puget Sound Energy Page 8 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
2.3 User Requirements
2.3.1 Electric, Gas Site Audit and Gas High Pressure User Requirements
These are the user’s primary requirements:
Task Inspector Administrator
Creates new records self and contract inspectors
Creates new records for other inspectors
Views all records, created by self and others.
Edits records created by self <= 7 days old
Edits records created by self > 7 days old with no
unresolved issues
Edits records created by self > 7 days old with
unresolved issues
Edits records created by self <= 7 days old with
unresolved issues
Edits records that were created by someone else
Able to search all records, created by self and others.
Clones all records, created by self and others.
Able to print all records, created by self and others.
Able to email all records, created by self and others.
Deletes records created by self <= 7 days old
Deletes records created by self > 7 days old
Deletes records that were created by others
Maintains all tables including the security table.
The 7-day clock starts when:
Record Type Record Age
Record with no actions required The day the record was created
Record created with unresolved issues The modified date in which last unresolved
issue was resolved
Task Inspector Administrator
Able to use Data Tool
Runs Reports
Inspectors can be able to run reports and/or run queries if they are granted additional privileges.
9. Puget Sound Energy Page 9 of 49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
2.3.2 Vegetation Management User Requirements
TBD
2.4 User Interfaces
2.4.1 Electric, Gas Site Audit and Gas High Pressure User Interfaces
There needs to be unique data entry forms for 1) Electrical Audits, 2) Gas Audits and 3)
Gas High-Pressure Inspections.
All forms should have a similar look and feel. Forms will share some common fields.
The client application should support the following functions:
Save
Print
Automatic Upload
Clone
Email
2.4.2 Vegetation Management User Interface
TBD
10. Puget Sound Energy
Page 10 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
2.5 New Release Requirements for Electric, Gas Site Audit and Gas High Pressure
2.5.1 Database Consolidation
The current SQL/MS Access-based application is a loosely knitted collection of nine
backend databases which are functionally replicated onto client-side machines on an as
needed basis. This architecture results in chaos.
Design and implement a replacement SQL backend as a single construct
Single SQL database for all audit types
User authentication based on Active Directory and User Role
2.5.2 Database Upload
Provide the ability for records to be automatically uploaded when the program is
connected to the SQL server. In cases where connectivity is not available, provide an
automatic upload (synch up) of data immediately upon restoration of connectivity.
Real-time connectivity
Confirmation of upload
2.5.3 Fully Displayed Checklist
The current design requires that each inspection item be entered separately. This feature
needs to be changed into a table display of available inspection items from which all
necessary items can be selected.
The checklist can either be displayed at the bottom of the form, making it a long form, or
it can be a separate window.
2.5.4 Cloning an Existing Audit
Provide the ability to clone an existing audit.
Inspectors and Administrators should be able to clone all records.
2.5.5 Reporting Enhancement
Make it so new reports can be added and existing reports can be modified without
requiring changes to the code. When a change is made, users will automatically have
the ability to run the reports without having to install new version of the program.
2.5.6 Data Tool Enhancement
Make it so users can export queried data to Excel files.
2.5.7 User Preferences Form
Make it so users can save their preferred screen background color on a separate form.
2.6 Release Requirement - Vegetation Management
This is a new inspection program that will capture vegetation management data in the
same way that electric and gas inspection data is captured.
2.7 Proposed Future Requirements
2.7.1 SAP Enhancement
Link with SAP to retrieve existing data. Use the existing web service for SAP Work order
data, and populate corresponding data fields in the QAI application. This feature would
reduce time spent on data entry and reduce the risk for data entry errors.
11. Puget Sound Energy
Page 11 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3 High Level Requirements
The Quality Assurance and Inspection application should provide users the ability to record inspection
data into a database and query the results.
3.1 User Interface Elements
3.1.1 Buttons
Buttons should appear differently depending on whether or not the functionality is
available.
Button Description
Active buttons should be displayed with dark font, a dark boarder
and blue background.
Inactive buttons should be displayed with faded font, faded
boarder and a washed out background.
3.1.2 Special Buttons
Special buttons should appear have a different background.
Button Description
The Edit Record button should be displayed with a yellow
background.
The Delete Record button should be displayed with a red
background.
3.1.3 Required Fields
Required fields should have a green background and red dots.
3.1.4 Non-applicable Fields
Non-applicable fields should be made invisible on all forms.
3.1.5 Window Functionality
Users should have the ability to minimize, maximize and close windows. The close
button should only close the current window.
3.1.6 Tab Order
Users should have the ability to use the tab key to navigate fields. Tab order should go
left to right, and top down.
12. Puget Sound Energy
Page 12 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.1.7 Print Functionality
Whenever a user clicks a print button, the system should display a print window giving
the user the option to select a printer.
3.1.8 Navigation
The system should only be able to have one record open at a time. When a window is
closed, the system should display the previous window. For example, when a checklist is
closed, the data entry window should be displayed.
3.1.9 Background Color
Buttons should allow the user to change the background color of the screens.
Selectable colors should include:
Tan
Light Gray
Gray
White
13. Puget Sound Energy
Page 13 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.2 Main Screen
When the user starts the application there should be a main screen that allows users to select:
Inspection Type
Options
User Preferences
Functionality will be enabled or disabled depending on network connectivity and the individual’s
security profile.
Electric Inspector Options Electric Administrator Options
3.2.1 Inspection Type
If an inspector has permissions for only one Inspection Type, the application will default
to that inspection type.
If a user has permissions for more than one Inspection Type, the user will be required to
select an inspection type to activate the optional buttons.
Note: An Inspection Type does not have to be selected in order for the Administration
button to be active.
14. Puget Sound Energy
Page 14 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.2.2 Inspector Options/Function Availability
Function Connected Disconnected
Create/Edit Records
Search
Data Tool
3.2.3 Administrator Function Availability
Function Connected Disconnected
Create/Edit Records
Search
Data Tool
Reports
Administration
3.3 Create Records - Data Entry Form
The data entry form should give the user the ability to create new records and edit existing
records.
The data entry form should appear when the user clicks the Create Records button. When an
inspector clicks the Create Records button, the data entry form should be displayed as a blank
form ready for user input.
The form should display several required and non-required fields.
Functionality on the data entry form should include;
Save a record
Delete a record
Print a record
Email a record
Clone a record
15. Puget Sound Energy
Page 15 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.3.1 Data Entry Form Buttons
Functions on the data entry form should be made available in button format.
Button Function
When the user clicks the New Record button, the system should open
a new blank data entry form. The New Record button should only be
available when the user is on an existing record.
When the user clicks the Open Checklist button, the system should
open a checklist in a different window. The Open Checklist button
should only be available after all required fields have been entered.
When the user clicks the Email button the application should generate a
report of the current inspection, invoke Outlook, create an automatically
generated email with the report attached in .pdf format. The subject line
of the email should be customized depending on the inspection type
and the message body of the email should also be customized
depending on the inspection type.
When the user clicks the Print button the application should generate a
report of the current inspection and invoke a print dialog box that will
allow the user to select which printer to use.
New feature. When the user clicks the Clone Record button the
application should copy several fields of the record that the user is
currently viewing. Then, the application should present a message that
asks the user if he/she wants continue. Note: This function will not be
implemented in the Vegetation inspection form.
When the user clicks the Edit Record button, the system should unlock
the current record and make it editable. This button toggles to become
the Lock Record Button when clicked.
When the user clicks the Lock Record button, the system should lock
the current record and make it read-only. This button toggles to
become the Edit Record Button when clicked.
When the user clicks the Undo Edits button, the system should discard
changes that have not been saved.
When the user clicks the Delete button, the system should display a
message asking the user to confirm the deletion.
When the user clicks the Save button, the system should check to see if
all required fields are populated and valid.
If this is a new record and the check is successful, the Data Entry Code
should be generated and displayed in the Data Entry Code field.
If the check is not successful, the user should be prompted to complete
all required fields. When all required fields are complete and valid the
record is saved.
16. Puget Sound Energy
Page 16 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.3.2 Electric, Gas, Gas HP Data Entry Form Prototype
This prototype was approved by Dean on 9/23/09.
17. Puget Sound Energy
Page 17 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.3.3 Vegetation Entry Form Prototype
18. Puget Sound Energy
Page 18 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.4 Checklist
The checklist should give inspectors the ability to record detailed inspection results.
3.4.1 Checklist Buttons
Button Function
When the user clicks the Undo Edit button, the system should discard
changes that have not been saved.
The Undo Edits button should only be available after the checklist has
been previously saved and modified.
When the user clicks the Save button, the system should save the
changes.
When the user clicks the Edit Record button, the system should unlock
the current record and make it editable. This button toggles to become
the Lock Record Button when clicked.
When the user clicks the Add button, the system should duplicate the
Inspection Item.
When the user clicks the Minus button, the system should
remove/delete the Inspection Item.
3.4.2 Checklist Columns
Checklist columns vary depending on inspection type. For lists of checklist columns,
refer to the Specific Requirements section of this document.
Electric, Gas Site Audit and Gas High Pressure inspection types should have a column
titled Inspection Item. The order in which the inspection items appear on the checklist
should be determined and controlled by the System Administrator.
3.4.3 Checklist Tables
Checklist tables vary depending on inspection type. For lists of checklist tables, refer to
the Specific Requirements section of this document.
19. Puget Sound Energy
Page 19 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.5 Search
The Search screen should give users the ability to find records based on user-specified criteria.
Criteria options are presented in drop-down lists.
Once the search has been performed, results can be printed and/or emailed. Users should have
the ability to double-click a record, which will then be opened in the Create/Edit Records module.
3.5.1 Search Buttons
Button Function
When the user clicks the Search button, the system
should search the local data and retrieve records matching
the specified criteria.
When the user clicks the View Record button, the system
should open the highlighted record in the Create/Edit
Records module.
When the user clicks the Clear button, the system should
reset the date, reset the radio buttons, clear the search
query and clear the results list.
When the user clicks the Export Results as Spreadsheet
button, the system should export the search criteria and
results to one Excel workbook with two separate
worksheets. One worksheet should contain search criteria
and the other worksheet should contain the search results.
The system should prompt the user to save the
spreadsheet. When saving the spreadsheet, the user
should be able to accept the default name and location or
change the file name and/or location. The default file
name should be QAI_SearchResults_<date>_<time>. The
default location should be the user’s desktop.
After the spreadsheet has been saved, the system should
prompt the user to open the file.
By default, the Export Results as Spreadsheet button
should be disabled when Search is launched. The Export
Results as Spreadsheet button should also be disabled
after there has been a change in the search criteria. The
Export Results as Spreadsheet button should only be
available after the data has been queried.
When the user clicks the Print Each Report Listed
button, the system should individually print all the records
in the results list. If more than 25 records are on the
reports list, the system should prompt the user to continue
or cancel.
20. Puget Sound Energy
Page 20 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Button Function
When the user clicks the Email Each Report Listed
button, the system should initiate an email and attach all
the records in the results list. Attached records should be
in .pdf format. If more than 25 records are on the reports
list, the system should prompt the user to continue or
cancel.
3.5.2 Electric, Gas, Gas High Pressure Search Filters
A user should be able to select one of the following search filter options:
3.5.3 Vegetation Search Filters
A user should be able to select one of the following search filter options:
21. Puget Sound Energy
Page 21 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.6 Data Tool
The Data Tool screen should give users the ability to query data based on user-specified criteria.
This feature does not need to be available when the user is not connected to the network.
The queried data should be presented in a summary format. After the query has been performed,
users should be able to export results into a spreadsheet, print the results or email them.
3.6.1 Data Tool Buttons
Button Function
When the user clicks the Start Query button, the system
should query the database.
By default, the Start Query button should be enabled
when the Data Tool is launched. It should also be
enabled after the query options have been changed.
When the user clicks the Clear all Query Fields button,
the system should clear the search form. By default, the
Clear all Query Fields button should be disabled when
the Data Tool is launched. The Clear all Query Fields
button should be enabled after the selection criteria has
been changed.
When the user clicks the Export Results as
Spreadsheet button, the system should export the
criteria, query results and inspection items to one Excel
workbook with three separate worksheets.
The system should prompt the user to save the
spreadsheet. When saving the spreadsheet, the user
should be able to accept the default name and location or
change the file name and/or location. The default file
name should be QAI_DATA Tool_date_time stamp. The
default location should be the user’s desktop.
After the spreadsheet has been saved, the system should
prompt the user to open the file.
By default, the Export Results as Spreadsheet button
should be disabled when the Data Tool is launched. The
Export Results as Spreadsheet button should also be
disabled after there has been a change in the selection
criteria. The Export Results as Spreadsheet button
should only be available after the data has been queried.
22. Puget Sound Energy
Page 22 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.6.2 Query Results Summary
The Query Results section displays a summary of totals. The data fields displayed will
vary depending on the inspection type.
3.6.3 Inspection Items Summary
The Inspection Items section displays a list of Inspection Items and a total of all the
Inspection Item’s results. The data used in creating this summary is pulled from the
checklists.
3.6.4 Resolution Tracker
The Resolution Tracker section displays the number of items awaiting resolution grouped by
how long the items have been awaiting resolution. Dates used for calculation are as follows:
Inspection Type Dates Used for Calculation
Electric Site Audit Date Audit Sent and query End Date
Gas Site Audit Inspection Date and query End Date
Gas High Pressure Inspection Date and query End Date
23. Puget Sound Energy
Page 23 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.7 Reports
The Reports screen should give users the ability to run a list of pre-defined reports based on
user-specified criteria.
This feature does not need to be available when the user is not connected to the network.
When a user clicks the Reports button on the main menu, the system should display screens that
will lists available reports.
3.7.1 Report Selection Screens
The first screen will have folders; one for each inspection type. The user should double-click the
appropriate folder to view the available reports.
This screen allows the user to select the Classification Breakdown report. When more reports
are added to the program there will a list of several reports. The number of reports will vary
depending on inspection type.
After the report is selected the user can specify criterion to view the report or print the report.
24. Puget Sound Energy
Page 24 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.7.2 Report Criteria Screen
After the user selects a report, then he/she should be prompted to enter criteria for the report.
3.7.3 Report Button, Link and Icon
Button Function
When the user clicks the View Report button, the system
should display the report.
Export
When the user clicks the Export link, the system should
display the export the data to the format chosen by the
user.
When the user clicks the Print icon, the system should
print the report.
Here the user enters the
criteria for the report.
25. Puget Sound Energy
Page 25 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
3.7.4 Report View Screen
This reporting screen should allow users to print or export reports into several formats, including
Excel, CSV and PDF.
3.8 Administration
The Administration screen should give users the ability to maintain all tables. This feature does
not need to be available when the user is not connected to the network.
3.9 User Preferences Form
The User Preferences form should give users the ability to change the background color on their
screen. This feature should work when the user is disconnected from the network.
PDF format
26. Puget Sound Energy
Page 26 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4 Specific Requirements
4.1 Electric Site Audit
4.1.1 Data Entry Screen Fields
The Electric Site Audit data entry screen should allow the user to enter data into the
following fields:
Field Label
Electric Site
Audit
Inspected By
Inspection Date
Date Audit Sent
Audit Type
Inspection Time
Duration in Hours
SAP Number
Order Type Code
MAT Code
Job Address
County
City
Project Name
Crew Employed By
Main Work Center
Crew on Site
Person in Charge
PM or Eng
Joint Facility
Correction Verified
Corrected By
Corr Verif Duration
Corr Verif Dt
Tracker 1
Tracker 2
Comments
Required Field
Applicable Field
27. Puget Sound Energy
Page 27 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.1.2 Checklist Columns
The Electric Audit checklist should display the following columns:
Field Definition Input Type
Add
This column should display a button. When the user
wants the duplicate the inspection item, then he/she
should click the button next to the inspection item.
When an inspection item is duplicated, only the
Inspection Item column should be duplicated. No other
columns should be populated on the new Inspection
Item line.
Button
Del
This column should display a button. When the user
wants to delete an inspection item, then he/she should
click the button next to the inspection item.
Button
Inspection Item
Items that appear in the Inspection Item column vary
depending on inspection type. For lists of inspection
items, refer to the Specific Requirements section of this
document.
Disabled
Drop-down
Item
Applicability
This column should display a drop-down list. The
content of the drop down is drawn from the
Insp_Item_Status table.
Drop-down
Total
Inspections
The Total Inspections field should total the number of
satisfactory and unsatisfactory items.
Display sum of
Satisfactory +
Unsatisfactory
Satisfactory
This column should allow the user to enter a number.
The number should represent the number of items that
were inspected and satisfactory.
Numeric
Unsatisfactory
This column should allow the user to enter a number.
Indicates that one or more of the inspection item checks
do not fully meet PSE requirements/specifications. A
correction may or may not be required depending on the
item.
For those "Unsatisfactory" inspection items where
correction is not required we still need to handle the
problem but we don't have to track the fix like we do
when it pertains to problems with the actual facility
being installed.
Numeric
28. Puget Sound Energy
Page 28 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Field Definition Input Type
Classification
This is a required field anytime a number is entered into
the "Unsat" field. The Inspector selects one of the
options from the drop down box. If more than one
classification applies to a problem the Inspector should
pick the classification that they believe best applies. If
there is more than one "Unsat" number for an
Inspection Item and different classifications would apply
to the problems the Inspector should pick what they
would consider the most serious and classify the
Inspection Item line with that classification. The field
defaults to N/A when the "Unsat" field contains a "0".
Drop-down
Action Required
The Action Required field should allow users to enter a
number. This number represents the number of
Unsatisfactory items that require remediation.
Numeric
Date Resolved This column should allow the user to enter a date. Date
Remarks
This is not a required field and does not need to be
entered in order to complete the Form. Although this
field appears to be small it can hold a great amount of
text (64,000 characters). Details about a specific
Inspection Item should be entered here rather than in
the "Comments Section".
When corrections are required the name of the person
making the corrections (if different than name in the
"Corrected By" field) should entered here along with
verification information.
Remarks should include a description of the problem
along with the proximity of the deviation and its severity.
Clearance deviations should always include the
measurements. The Operating Standard or Procedure
reference should also be stated in this section whenever
a deviation is noted. After a problem has been corrected
the details about the correction should also be put in the
Remarks. The text from the Remarks field is included in
numerous reports. For this reason the preference is that
the text NOT BE ALL CAPITALS.
Text field
29. Puget Sound Energy
Page 29 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.1.3 Checklist Tables
The Electric Audit checklist should display the following tables:
Table Values
Inspection Item For a list of inspection items, refer to the next section.
Item Applicability
Inspection Status field should be defaulted to Not
Applicable and the drop down list should be in this
order:
Not Applicable
Yes – Inspected
Yes – Not Available
Yes – Not Inspected
Classification
Classification field should be defaulted to N/A and the
drop down list should be in this order:
Safety High
Safety Low
Operability
Reliability
Regulatory
N/A
30. Puget Sound Energy
Page 30 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.1.4 Electric Site Audit Inspection Items
These inspection items should appear in the Electric Site Audit inspection checklist.
1. Anchor & Guys
2. Capacitors
3. Clearances - OH
4. Conduit
5. Engineering
6. Facilities Placement
7. Grid Number
8. Grounds / Neutrals UG & OH
9. J-Boxes
10. Locked and Secured
11. Metering
12. OH Conductor
13. OH Switches
14. OH Transformers
15. PM Switch
16. PM Transformer / TUT
17. Pole Framing
18. Pole Installation
19. Primary Metering UG & OH
20. Reclosers
21. Regulators
22. Restoration
23. Riser - Primary & Secondary
24. Sec HH
25. Secondary UG & OH
26. Sectionalizers
27. Services UG & OH
28. Street Lights
29. Termination - Primary & Secondary
30. UG Cable - Primary
31. Vaults
31. Puget Sound Energy
Page 31 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.1.5 Search: Searchable Fields
When a searching Electric Site Audit records, the following fields should be searchable:
Start Date
End Date
Audit Type
Inspected By
SAP Order Number
Data Entry Code
Project Name *
Job Address *
City
County
Crew Employed By
Crew on Site
Person in Charge
PM or Eng
MAT Code
* Make as a wild card search
4.1.6 Data Tool: Searchable Fields
Start Date
End Date
Audit Type
Crew Employed By
City/Unincorporated County
County
Main Work Center
Inspected By
Person in Charge
PM or Eng
Joint Facility
Crew on Site
MAT Code
SAP Order Number
32. Puget Sound Energy
Page 32 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.1.7 Electric Reports & Queries
After a user opens the Electric inspections folder and selects a report, the user should be
able to filter report results by selecting Crew Employed by, Audit Type, Start Date and
End Date.
The following table lists the reports needed for Electric Site Audits and the priority of
need.
Priority Status Report Title Notes
1 Modify
the old
report
Deviation
Classification Report
Include SAP Order Number column in the results.
1 New Deviation Report Change name to "Deviation Report". Remove
Summary table at the top. Include SAP Order Number
column in the results.
1 Duplicate
the old
query
Search for possible
duplicate records
This is a periodic quality control process that allows the
user to search for records that have the same Date,
Order Number, and Inspector, which could indicate that
a duplicate record may have been created.
1 Duplicate
the old
query
StaCon query This query retrieves audit data for the StaCon Report.
In addition to entering the date range remember to
select "Text Delimiter = ~" before running this query.
2 New Quality Assurance
Monthly Report
This report can be created from data queried in the
Data Tool.
2 Duplicate
the old
report
Outstanding
Deviation
Classification Report
2 Duplicate
the old
report
Consistency Report
by County
2 Duplicate
the old
report
Inspector Comp by
MAT Code
This report lists all the Inspectors and compares their
inspections over a specified date range, MAT code,
and Crew Employed By.
2 Modify
the old
report
Inspector Comp This report lists all the Inspectors and compares their
inspections over a specified date range and Crew
Employed By.
2 Duplicate
the old
query
Search for all
uncorrected
deviations being
tracked
2 Duplicate
the old
query
Inspection Items
Being Checked
This query retrieves a list of all Inspection Items
checked during a specified period of time. It shows how
many times an Item was checked along with the
amount Satisfactory, Unsatisfactory and Percent
Satisfactory.
33. Puget Sound Energy
Page 33 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Priority Status Report Title Notes
2 Duplicate
the old
query
StaCon Inspection
Items Being Checked
This query retrieves a list of all Inspection Items
checked during a specified period of time. It shows how
many times an Item was checked along with the
amount Satisfactory, Unsatisfactory and Percent
Satisfactory. StaCon MAT Code table is used in this
query.
3 Duplicate
the old
report
Consistency Report
by MAT Code
4.1.8 Report Terminology Changes
Old Field Name New Field Name
Form Completed By Inspected By
Initial Input Date Record Created
Project Manager/Engineer PM or Eng
Correction Verification Date Corr Verif Dt
34. Puget Sound Energy
Page 34 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2 Gas Site Audit
4.2.1 Data Entry Screen Fields
The Gas Site Audit data entry screen should allow the user to enter data into the
following fields:
Field Label Gas Site Audit
Inspected By
Inspection Date
Audit Type
Inspection Time
Duration in Hours
SAP Number
Order Type Code
MAT Code
Job Address
County
City
Project Name
Crew Employed By
Main Work Center
Crew on Site
Person in Charge
Fuser/Welder 1
Fuser/Welder 2
Fuser/Welder 3
Joint Facility
Facility Inspected
Install Method
Carrier Pipe
Pressure
Correction Verified
Corrected By
Corr Verif Dt
Tracker 1
Tracker 2
Comments
Required Field
Applicable Field
35. Puget Sound Energy
Page 35 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2.2 Checklist Columns
The Gas Site Audit checklist should display the following columns:
Field Definition Input Type
Add
This column should display a button. When the user
wants the duplicate the inspection item, then he/she
should click the button next to the inspection item.
When an inspection item is duplicated, only the
Inspection Item column should be duplicated. No other
columns should be populated on the new Inspection
Item line.
Button
Del
This column should display a button. When the user
wants to delete an inspection item, then he/she should
click the button next to the inspection item.
Button
Inspection Item
Items that appear in the Inspection Item column vary
depending on inspection type. For lists of inspection
items, refer to the Specific Requirements section of this
document.
Drop-down
Item
Applicability
This column should display a drop-down list. The
content of the drop down is drawn from the
Insp_Item_Status table.
Drop-down
Total
Inspections
The Total Inspections field should total the number of
satisfactory and unsatisfactory items.
Display sum of
Satisfactory +
Unsatisfactory
Satisfactory
This column should allow the user to enter a number.
The number should represent the number of items that
were inspected and satisfactory.
Numeric
Unsatisfactory
Indicates that one or more of the inspection item checks
do not fully meet PSE requirements/specifications. A
correction may or may not be required depending on the
item.
For those "Unsatisfactory" inspection items where
correction is not required we still need to handle the
problem but we don't have to track the fix like we do
when it pertains to problems with the actual facility
being installed.
Numeric
36. Puget Sound Energy
Page 36 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Field Definition Input Type
Classification
This is a required field anytime a number is entered into
the "Unsat" field. The Inspector selects one of the
options from the drop down box. If more than one
classification applies to a problem the Inspector should
pick the classification that they believe best applies. If
there is more than one "Unsat" number for an
Inspection Item and different classifications would apply
to the problems the Inspector should pick what they
would consider the most serious and classify the
Inspection Item line with that classification. The field
defaults to N/A when the "Unsat" field contains a "0".
Drop-down
Action Required
The Action Required field should allow users to enter a
number. This number represents the number of
Unsatisfactory items that require remediation.
Numeric
Date Resolved This column should allow the user to enter a date. Date
Remarks
This is not a required field and does not need to be
entered in order to complete the Form. Although this
field appears to be small it can hold a great amount of
text (64,000 characters). Details about a specific
Inspection Item should be entered here rather than in
the "Comments Section".
When corrections are required the name of the person
making the corrections (if different than name in the
"Corrected By" field) should entered here along with
verification information.
Remarks should include a description of the problem
along with the proximity of the deviation and its severity.
Clearance deviations should always include the
measurements. The Operating Standard or Procedure
reference should also be stated in this section whenever
a deviation is noted. After a problem has been corrected
the details about the correction should also be put in the
Remarks. The text from the Remarks field is included in
numerous reports. For this reason the preference is that
the text NOT BE ALL CAPITALS.
Text field
37. Puget Sound Energy
Page 37 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2.3 Checklist Tables
The Gas Site Audit checklist should display the following tables:
Table Values
Inspection Item For a list of inspection items, refer to the next section.
Item Applicability
Inspection Status field should be defaulted to Not
Applicable and the drop down list should be in this
order:
Not Applicable
Yes – Inspected
Yes – Not Available
Yes – Not Inspected
Classification
Classification field should be defaulted to N/A and the
drop down list should be in this order:
Safety High
Safety Low
Operability
Reliability
Regulatory
N/A
38. Puget Sound Energy
Page 38 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2.4 Gas Site Audit Inspection Items
These inspection items should appear in the Gas Site Audit inspection checklist.
1. Clearance - Underground
2. Coatings on Buried Pipe
3. Compaction
4. Cover and Pipe Depth
5. CP Requirements
6. Equipment Calibration Verified
7. Exposed Facility Protected
8. Final Backfill Material
9. Fusion
10. Initial Backfill Material
11. Inserted Pipe
12. Joining Pipe other than Weld or Fuse
13. Leak Testing
14. Locate Wire
15. Manuals on Site
16. Materials Handling, Storage and Transportation
17. Meter Set Assembly
18. Other
19. Painting/Coating Exposed Facility
20. Pipe: General Installation/Retirement Requirements
21. Purging
22. Qualification Card
23. Restoration
24. Service Prerequisites and Route Requirements
25. Squeezing Pipe
26. Tapping/Stopping
27. Valves - Main, Service, Excess Flow
28. Welding
39. Puget Sound Energy
Page 39 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2.5 Search: Searchable Fields
When a searching Gas Site Audit records, the following fields should be searchable:
Start Date
End Date
Audit Type
Inspected By
SAP Order Number
Data Entry Code
Project Name *
Job Address *
City
County
Crew Employed By
Crew on Site
Person in Charge
Fuser/Welder
MAT Code
Carrier Pipe
Pressure
Facility Inspected
* Make as a wild card search
4.2.6 Data Tool: Searchable Fields
When a using the data tool with Gas Site Audit records, the following fields should be
searchable:
Start Date
End Date
Audit Type
Crew Employed By
City/Unincorporated County
County
Main Work Center
Inspected By
Person in Charge
Joint Facility
Crew on Site
MAT Code
Carrier Pipe
SAP Order Number
40. Puget Sound Energy
Page 40 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.2.7 Reports
After a user opens the Gas Site Audit inspections folder and selects a report, the user
should be able to filter report results by selecting Crew Employed by, Audit Type, Start
Date and End Date.
When a user selects a query, the user should be able to select Start Date, End Date,
Audit Type and MAT Code.
The following table lists the reports needed for Gas High Pressure and the priority of
need.
Priority Status Report Title Notes
1 Modify the
old report
Deviation
Classification Report
Include SAP Order Number column in the results.
1 New Deviation Report Change name to "Deviation Report". Remove
Summary table at the top. Include SAP Order
Number column in the results.
1 Duplicate
the old
report
Inspection Item
Applicability Report
1 Duplicate
the old
query
Search for possible
duplicate records
This is a periodic quality control process that allows
the user to search for records that have the same
Date, Order Number, and Inspector, which could
indicate that a duplicate record may have been
created.
1 Duplicate
the old
query
StaCon query This query retrieves audit data for the StaCon
Report. In addition to entering the date range
remember to select "Text Delimiter = ~" before
running this query.
2 New TBD - Dean will let
us know
This report can be created from data queried in the
Data Tool.
2 Duplicate
the old
report
Outstanding
Deviation
Classification Report
2 Duplicate
the old
report
Inspector Comp by
MAT Code
This report lists all the Inspectors and compares their
inspections over a specified date range, MAT code,
and Crew Employed By.
2 Modify the
old report
Inspector Comp This report lists all the Inspectors and compares their
inspections over a specified date range and Crew
Employed By.
2 Duplicate
the old
report
Inspector
Consistency:
Counties
2 Duplicate
the old
query
Jobs Audited More
Than Once
This query lists SAP numbers that occur in more
than one record and the number of occurrences.
41. Puget Sound Energy
Page 41 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Priority Status Report Title Notes
2 Duplicate
the old
query
Inspection Items
Being Checked
This query retrieves a list of all Inspection Items
checked during a specified period of time. It shows
how many times an Item was checked along with the
amount Satisfactory, Unsatisfactory and Percent
Satisfactory.
2 Duplicate
the old
query
StaCon Inspection
Items Being Checked
This query retrieves a list of all Inspection Items
checked during a specified period of time. It shows
how many times an Item was checked along with the
amount Satisfactory, Unsatisfactory and Percent
Satisfactory. StaCon MAT Code table is used in this
query.
2 Duplicate
the old
query
Unresolved Audit List This query allows the user to search for all Inspection
Items that have "Action Req" > 0 and no "Date
Resolved".
3 Duplicate
the old
report
Inspector
Consistency: Crew
on Site
3 Duplicate
the old
report
Inspector
Consistency:
Correction
Verification
Make sure report name on list matches report name
on report.
3 Duplicate
the old
report
Resource Allocation
by County
3 Duplicate
the old
report
Consistency Report
by MAT Code
3 Duplicate
the old
report
Resource Allocation
by MAT Code
3 Duplicate
the old
report
Resource Allocation
by Facilities
Inspected
3 Duplicate
the old
report
Resource Allocation
by Main Work Center
Old Field Name New Field Name
Form Completed By Inspected By
Initial Input Date Record Created
Fuser/Welder/Fitter 1 Fuser/Welder 1
Fuser/Welder/Fitter 2 Fuser/Welder 2
Joint Trench Joint Facility
Installation Method Install Method
Correction Verification Date Corr Verif Dt
42. Puget Sound Energy
Page 42 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.3 Gas High Pressure
4.3.1 Data Entry Screen Fields
The Gas High Pressure data entry screen should allow the user to enter data into the
following fields:
Field Label Gas High Pressure
Inspected By
Inspection Date
Inspection Start Time
Duration in Hours
SAP Order Number
Order Type Code
MAT Code
Job Address
County
City/Unincorporated County
Project Name
Crew Employed By
Main Work Center
Crew on Site
Person in Charge
Fuser/Welder 1
Fuser/Welder 2
Fuser/Welder 3
Joint Facility
Facility Inspected
Install Method
Carrier Pipe
Pressure
Pipe Grade
Pipe Footage Ins
X-Ray Qty
MagParticle Qty
Tracker 1
Tracker 2
Comments
Required Field
Applicable Field
43. Puget Sound Energy
Page 43 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.3.2 Checklist Columns
The Gas High Pressure checklist should display the following columns:
Field Definition Input Type
Add
This column should display a button. When the user
wants the duplicate the inspection item, then he/she
should click the button next to the inspection item.
When an inspection item is duplicated, only the
Inspection Item column should be duplicated. No other
columns should be populated on the new Inspection
Item line.
Button
Del
This column should display a button. When the user
wants to delete an inspection item, then he/she should
click the button next to the inspection item.
Button
Inspection Item
Items that appear in the Inspection Item column vary
depending on inspection type. For lists of inspection
items, refer to the Specific Requirements section of this
document.
Drop-down
Total
Inspections
The Total Inspections field should total the number of
satisfactory and unsatisfactory items.
Display sum of
Satisfactory +
Unsatisfactory
Satisfactory
This column should allow the user to enter a number.
The number should represent the number of items that
were inspected and satisfactory.
Numeric
Unsatisfactory
Indicates that one or more of the inspection item checks
do not fully meet PSE requirements/specifications. A
correction may or may not be required depending on the
item.
For those "Unsatisfactory" inspection items where
correction is not required we still need to handle the
problem but we don't have to track the fix like we do
when it pertains to problems with the actual facility
being installed.
Numeric
Action Required
The Action Required field should allow users to enter a
number. This number represents the number of
Unsatisfactory items that require remediation.
Numeric
Date Resolved This column should allow the user to enter a date. Date
44. Puget Sound Energy
Page 44 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Field Definition Input Type
Remarks
This is not a required field and does not need to be
entered in order to complete the Form. Although this
field appears to be small it can hold a great amount of
text (64,000 characters). Details about a specific
Inspection Item should be entered here rather than in
the "Comments Section".
When corrections are required the name of the person
making the corrections (if different than name in the
"Corrected By" field) should entered here along with
verification information.
Remarks should include a description of the problem
along with the proximity of the deviation and its severity.
Clearance deviations should always include the
measurements. The Operating Standard or Procedure
reference should also be stated in this section whenever
a deviation is noted. After a problem has been corrected
the details about the correction should also be put in the
Remarks. The text from the Remarks field is included in
numerous reports. For this reason the preference is that
the text NOT BE ALL CAPITALS.
Text field
4.3.3 Checklist Table
The Gas High Pressure checklist should display the following table:
Table Values
Inspection Item For a list of inspection items, refer to the next section.
45. Puget Sound Energy
Page 45 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.3.4 Gas High Pressure Inspection Items
These inspection items should appear in the Gas High Pressure inspection checklist.
1. Bending Steel Pipe
2. Boring and Plowing
3. Calibration Check Gas Scope
4. Calibration Check of Gauges & Chart Recorders
5. Calibration Check of Pocket Pot
6. Calibration Check of Pyrometer
7. Clearance - Underground
8. Coatings on Buried Pipe
9. Compaction
10. Correct Weld Procedure Used
11. Cover and Pipe Depth
12. CP Requirements
13. De-watering
14. Erosion Control
15. Final Backfill Material
16. Final Restoration
17. Fusion
18. Gas Field Procedures
19. Gas Operating Standards
20. Guard Post
21. Initial Backfill Material
22. Inserting In New Steel Casing
23. Installing Casing
24. Jeeping
25. Job Site Materials Inspected
26. Joining Pipe other than Weld or Fuse
27. Locate Wire
28. Main - Design & Installation
29. Main As-Built
30. Main Valve
31. Operator Qualification
32. Other
33. Painting/Coating Exposed Facilities
34. Pigging
35. Pipe Handling, Storage and Transportation
36. Plating/Cordoning
37. Preventing Accidental Ignition
38. Purging
39. Qualification Card
40. Radius Bend of PE
41. Rough Cleanup
42. Squeezing PE Pipe
43. Stopping other than Squeezing
44. Tapping Pipe
45. Testing
46. Tie-in
47. Trench Requirements
46. Puget Sound Energy
Page 46 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
4.3.5 Search: Searchable Fields
When a searching Gas High Pressure records, the following fields should be searchable:
Start Date
End Date
Inspected By
SAP Order Number
Data Entry Code
Project Name *
Job Address *
County
City
Crew Employed By
Crew on Site
Person in Charge
Fuser/Welder
MAT Code
Carrier Pipe
Pressure
Facility Inspected
* Make as a wild card search
4.3.6 Data Tool: Searchable Fields
Start Date
End Date
Crew Employed By
City/Unincorporated County
County
Main Work Center
Inspected By
Person in Charge
Joint Facility
Crew on Site
MAT Code
Carrier Pipe
SAP Order Number
4.3.7 Reports
After a user opens the Gas High-Pressure folder and selects a report, the user should be
able to filter report results by selecting Start Date, End Date and Crew Employed by.
47. Puget Sound Energy
Page 47 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
When a user selects a query for Gas High-Pressure inspections, the user should be able
to filter report results by selecting Start Date, End Date and MAT Code.
The following table lists the reports needed for Gas High Pressure and the priority of
need.
Priority Status Report Title Notes
1 Duplicate
the old
report
Inspector
Consistency: Hours
1 Duplicate
the old
report
Resource
Allocation by SAP
Number
2 Duplicate
the old
report
Resource
Allocation by
County
2 New TBD - Dean will let
us know
2 New
Query
Last Upload Report Lists each unique "Inspected By" and the latest upload
date occurring with their records
2 New
Query
Inspection Detail
Report - All
Inspectors
List all inspectors and the quantity (Total Insp) for each
Inspection Item, Pipe Footage, Xray, Mag Particle
2 New
Query
Inspection Detail
Report - By
Inspector
Shows one inspector and the quantity of Total Insp, Sat,
Unsat, Percentage Satisfactory for each Inspection Item.
Provides sum of Pipe Footage, Xray, Mag Particle for all
inspections for that inspector in the specified date range.
3 Duplicate
the old
report
Consistency Report
by MAT Code
3 Duplicate
the old
report
Resource
Allocation by MAT
Code
scrub mat list
3 Duplicate
the old
report
Resource
Allocation by
Facilities Inspected
3 Duplicate
the old
report
Resource
Allocation by Main
Work Center
48. Puget Sound Energy
Page 48 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
Old Field Name New Field Name
Form Completed By Inspected By
Initial Input Date Record Created
Fuser/Welder/Fitter 1 Fuser/Welder 1
Fuser/Welder/Fitter 2 Fuser/Welder 2
Joint Trench Joint Facility
Installation Method Install Method
Pipe Footage Inspected Pipe Footage Ins.
49. Puget Sound Energy
Page 49 of
49
Quality Assurance and Inspections Database
Functional Specification
QAI Functional Specification
5 Appendix
5.1 Report Prototypes
5.1.1 Deviations by Classification