16 Matching Results

Search Results

Advanced search parameters have been applied.

Business System Planning Project, Alternatives Analysis

Description: The CHG Chief Information Officer (CIO) requested a study of alternatives to the current business system computing environment. This Business Systems Planning (BSP) Project Alternatives Analysis document presents an analysis of the current Project Controls, Work Management, and Business Management systems environment and alternative solutions that support the business functions. The project team has collected requirements and priorities from stakeholders in each business area and documented them in the BSP System Requirements Specification (SRS), RPP-6297. The alternatives analysis process identifies and measures possible solutions in each of the business process areas against the requirements as documented in the SRS. The team gathered input from both internal and external sources to identify and grade the possible solutions. This document captures the results of that activity and recommends a suite of software products. This study was to select the best product based on how well the product met the requirements, not to determine the platform or hardware environment that would be used. Additional analysis documentation can be found in BSP project files.
Date: October 30, 2000
Creator: EVOSEVICH, S.
Partner: UNT Libraries Government Documents Department

Business System Planning Project, Preliminary System Design

Description: CH2M HILL Hanford Group, Inc. (CHG) is currently performing many core business functions including, but not limited to, work control, planning, scheduling, cost estimating, procurement, training, and human resources. Other core business functions are managed by or dependent on Project Hanford Management Contractors including, but not limited to, payroll, benefits and pension administration, inventory control, accounts payable, and records management. In addition, CHG has business relationships with its parent company CH2M HILL, U.S. Department of Energy, Office of River Protection and other River Protection Project contractors, government agencies, and vendors. The Business Systems Planning (BSP) Project, under the sponsorship of the CH2M HILL Hanford Group, Inc. Chief Information Officer (CIO), have recommended information system solutions that will support CHG business areas. The Preliminary System Design was developed using the recommendations from the Alternatives Analysis, RPP-6499, Rev 0 and will become the design base for any follow-on implementation projects. The Preliminary System Design will present a high-level system design, providing a high-level overview of the Commercial-Off-The-Shelf (COTS) modules and identify internal and external relationships. This document will not define data structures, user interface components (screens, reports, menus, etc.), business rules or processes. These in-depth activities will be accomplished at implementation planning time.
Date: October 30, 2000
Creator: EVOSEVICH, S.
Partner: UNT Libraries Government Documents Department

Z-Plant material information tracking system (ZMITS) software development and integration project management plan

Description: This document plans for software and interface development governing the implementation of ZMITS and other supporting systems necessary to manage information for material stabilization needs of the Project Hanford Management Contract (PHMC).
Date: September 7, 1999
Creator: IBSEN, T.G.
Partner: UNT Libraries Government Documents Department

Software development guidelines for Visual Basic and SQL Server

Description: Development Guidelines are programming directions that focus not on the logic of the program but on its physical structure and appearance. These directions make the code easier to read, understand, and maintain. These guidelines are put in place to create a consistent set of conventions to follow that will standardize the development process. With these guidelines in place the readability and understanding others have when reviewing the code is greatly enhanced. Use these guidelines as a general rule when writing any set of logical statements. Development Guidelines are put into place in an effort to standardize the structure and style of the development process. They are not intended to limit or channel the developer's own creativity and flexibility. These guidelines will cover general development syntax, organization and documentation. The general information covers the high level areas of development, no matter what the environment. This guide will detail specific Visual Basic guidelines, following the same standard naming conventions set by Microsoft, with some minor additions. The guideline will finish with conventions specific to a Database or Microsoft's SQL Server specific environment.
Date: July 26, 2000
Creator: IBSEN, T.G.
Partner: UNT Libraries Government Documents Department

CH2M Hill Hanford Group, Inc. Standards and Requirements Identification Document (SRID) Requirements Management System and Requirements Specification

Description: The current Tank Farm Contractor (TFC) for the U. S. Department of Energy, Office of River Protection (ORP), River Protection Project (RPP), CH2M Hill Hanford Group, Inc. (CHG), will use a computer based requirements management system. The system will serve as a tool to assist in identifying, capturing, and maintaining the Standards/Requirements Identification Document (S/RID) requirements and links to implementing procedures and other documents. By managing requirements as one integrated set, CHG will be able to carry out its mission more efficiently and effectively. CHG has chosen the Dynamic Object Oriented Requirements System (DOORS{trademark}) as the preferred computer based requirements management system. Accordingly, the S/RID program will use DOORS{trademark}. DOORS{trademark} will replace the Environmental Requirements Management Interface (ERMI) system as the tool for S/RID data management. The DOORS{trademark} S/RID test project currently resides on the DOORSTM test server. The S/RID project will be migrated to the DOORS{trademark} production server. After the migration the S/RID project will be considered a production project and will no longer reside on the test server.
Date: November 30, 2000
Creator: Johnson, A. L.
Partner: UNT Libraries Government Documents Department

River Protection Project information systems assessment

Description: The Information Systems Assessment Report documents the results from assessing the Project Hanford Management Contract (PHMC) Hanford Data Integrator 2000 (HANDI 2000) system, Business Management System (BMS) and Work Management System phases (WMS), with respect to the System Engineering Capability Assessment Model (CAM). The assessment was performed in accordance with the expectations stated in the fiscal year (FY) 1999 Performance Agreement 7.1.1, item (2) which reads, ''Provide an assessment report on the selected Integrated Information System by July 31, 1999.'' This report assesses the BMS and WMS as implemented and planned for the River Protection Project (RPP). The systems implementation is being performed under the PHMC HANDI 2000 information system project. The project began in FY 1998 with the BMS, proceeded in FY 1999 with the Master Equipment List portion of the WMS, and will continue the WMS implementation as funding provides. This report constitutes an interim quality assessment providing information necessary for planning RPP's information systems activities. To avoid confusion, HANDI 2000 will be used when referring to the entire system, encompassing both the BMS and WMS. A graphical depiction of the system is shown in Figure 2-1 of this report.
Date: July 28, 1999
Creator: JOHNSON, A.L.
Partner: UNT Libraries Government Documents Department

Tank Monitoring and Control Sys (TMACS) Acceptance Test Procedure

Description: The purpose of this document is to describe tests performed to validate Revision 11.2 of the TMACS Monitor and Control System (TMCACS) and verify that the software functions as intended by design. The tests will be performed on the development system. The software to be tested is the TMACS knowledge bases (KB) and the I/O driver/services. The development system will not be talking to field equipment; instead, the field equipment is simulated using emulators or multiplexers in the lab.
Date: November 8, 1999
Creator: WANDLING, R.R.
Partner: UNT Libraries Government Documents Department

Hanford year 2000 Business Continuity Plan

Description: The goal of Department of Energy Richland Operations (DOE-RL) Year 2000 (Y2K) effort is to ensure that the Hanford site successfully continues its mission as we approach and enter the 21th century. The Y2K Business Continuity Planning process provides a structured approach to identify Y2K risks to the site and to mitigate these risks through Y2K Contingency Planning, ''Zero-Day'' Transition Planning and Emergency Preparedness. This document defines the responsibilities, processes and plans for Hanford's Y2K Business Continuity. It identifies proposed business continuity drills, tentative schedule and milestones.
Date: November 1, 1999
Creator: VORNEY, S.V.
Partner: UNT Libraries Government Documents Department

Spent Nuclear Fuel Project document control and Records Management Program Description

Description: The Spent Nuclear Fuel (SNF) Project document control and records management program, as defined within this document, is based on a broad spectrum of regulatory requirements, Department of Energy (DOE) and Project Hanford and SNF Project-specific direction and guidance. The SNF Project Execution Plan, HNF-3552, requires the control of documents and management of records under the auspices of configuration control, conduct of operations, training, quality assurance, work control, records management, data management, engineering and design control, operational readiness review, and project management and turnover. Implementation of the controls, systems, and processes necessary to ensure compliance with applicable requirements is facilitated through plans, directives, and procedures within the Project Hanford Management System (PHMS) and the SNF Project internal technical and administrative procedures systems. The documents cited within this document are those which directly establish or define the SNF Project document control and records management program. There are many peripheral documents that establish requirements and provide direction pertinent to managing specific types of documents that, for the sake of brevity and clarity, are not cited within this document.
Date: May 18, 2000
Creator: MARTIN, B.M.
Partner: UNT Libraries Government Documents Department

Solid Waste Information and Tracking System Client Server Conversion Project Management Plan

Description: The Project Management Plan governing the conversion of SWITS to a client-server architecture. The PMP describes the background, planning and management of the SWITS conversion. Requirements and specification documentation needed for the SWITS conversion
Date: February 10, 2000
Creator: GLASSCOCK, J.A.
Partner: UNT Libraries Government Documents Department