This document outlines standard drafting and document control procedures used by drafters, engineers, project leads and document control team members at 1601 Bryan Street, Dallas, TX 75201. It describes processes for submitting and processing document requests, searching ProjectWise, creating drawings, revising existing drawings, reviewing and approving drawings, and distributing completed drawings. The document simplifies and standardizes current procedures to ensure compliance.
This document provides guidelines for CSS coding style conventions. It discusses file naming, syntax, indentation, selectors, properties, values, organization, and commenting. The goal is to improve code readability, maintainability, and reuse by standardizing CSS coding practices.
This document provides a framework for developing an organizational or project-based Building Information Modeling (BIM) deployment plan. It outlines key elements to address such as modeling standards, staffing needs, planned models and analyses. The goal is to help users streamline project communications and reduce costs through collaborative planning and BIM implementation. Sections provide guidance on developing a BIM vision and goals, modeling standards, planned model types and analyses, staffing structure and skills requirements. Users can fill in provided templates and tables to develop a customized plan suited to their specific needs and applications of BIM.
Report details the most powerful and only truly scientific development method which was created through a combination of most traditional methods for software, hardware and embedded.
Recent developments have created a new science through combining with control theory to create Project Control. Using Project Control principles we can most quickly create the best and most adaptable solutions.
At odd.enterprises we place tests and facts over opinions and assumptions to identify, correct and prevent errors at the earliest and most efficient time.
This document provides an overview and table of contents for a book about the Open ERP software. The book covers topics such as installing and setting up Open ERP, using Open ERP for sales, customer relationship management and marketing, financial management and accounting, operations management, warehouse and inventory management, manufacturing, and more. Each chapter in the book is dedicated to explaining a different feature or functionality of the Open ERP software.
This document provides a blueprint for configuring SAP FICO for Tata Steel Pvt Ltd. It outlines the organizational structure including the client, company, business areas, and company code to be used. It also describes the master data setup for vendors, customers, house banks, and assets. Finally, it covers the business processes for general ledger, accounts payable, accounts receivable, and asset accounting including configuration details.
This document outlines the project management plan for an unnamed project. It includes sections on the project scope and definition, organization structure, approaches and methods to be used, facilitating processes, project approval process, appendices, references, and document control. The author is listed as Ashok Kumar LalSingh of Taajeer Co. in KSA. Taajeer Co. reserves all rights to modify and use the document, and prohibits unauthorized use for other purposes.
This document provides a blueprint for migrating data from the Beacon system to SAP. It outlines the scope, proposed deployment approach, and data migration strategy for key SAP objects. The strategy addresses cleaning, loading, and replicating data for objects like business partners, sites, installations, devices, and more. It also identifies outstanding issues to resolve for each object's migration. The blueprint aims to guide the effective transfer of critical business data from the legacy system to the new SAP platform.
This document provides details of the "TO BE" business processes and master data for Kasturi & Sons Limited's SAP implementation project. It includes sections on the company's organizational structure, master data setup for finance modules like general ledger, accounts payable, accounts receivable and asset accounting. It also describes key business processes like bill processing, bank reconciliation, payment processes for expenses, donations, rent etc. and configuration requirements for implementing them in SAP.
This document provides guidelines for CSS coding style conventions. It discusses file naming, syntax, indentation, selectors, properties, values, organization, and commenting. The goal is to improve code readability, maintainability, and reuse by standardizing CSS coding practices.
This document provides a framework for developing an organizational or project-based Building Information Modeling (BIM) deployment plan. It outlines key elements to address such as modeling standards, staffing needs, planned models and analyses. The goal is to help users streamline project communications and reduce costs through collaborative planning and BIM implementation. Sections provide guidance on developing a BIM vision and goals, modeling standards, planned model types and analyses, staffing structure and skills requirements. Users can fill in provided templates and tables to develop a customized plan suited to their specific needs and applications of BIM.
Report details the most powerful and only truly scientific development method which was created through a combination of most traditional methods for software, hardware and embedded.
Recent developments have created a new science through combining with control theory to create Project Control. Using Project Control principles we can most quickly create the best and most adaptable solutions.
At odd.enterprises we place tests and facts over opinions and assumptions to identify, correct and prevent errors at the earliest and most efficient time.
This document provides an overview and table of contents for a book about the Open ERP software. The book covers topics such as installing and setting up Open ERP, using Open ERP for sales, customer relationship management and marketing, financial management and accounting, operations management, warehouse and inventory management, manufacturing, and more. Each chapter in the book is dedicated to explaining a different feature or functionality of the Open ERP software.
This document provides a blueprint for configuring SAP FICO for Tata Steel Pvt Ltd. It outlines the organizational structure including the client, company, business areas, and company code to be used. It also describes the master data setup for vendors, customers, house banks, and assets. Finally, it covers the business processes for general ledger, accounts payable, accounts receivable, and asset accounting including configuration details.
This document outlines the project management plan for an unnamed project. It includes sections on the project scope and definition, organization structure, approaches and methods to be used, facilitating processes, project approval process, appendices, references, and document control. The author is listed as Ashok Kumar LalSingh of Taajeer Co. in KSA. Taajeer Co. reserves all rights to modify and use the document, and prohibits unauthorized use for other purposes.
This document provides a blueprint for migrating data from the Beacon system to SAP. It outlines the scope, proposed deployment approach, and data migration strategy for key SAP objects. The strategy addresses cleaning, loading, and replicating data for objects like business partners, sites, installations, devices, and more. It also identifies outstanding issues to resolve for each object's migration. The blueprint aims to guide the effective transfer of critical business data from the legacy system to the new SAP platform.
This document provides details of the "TO BE" business processes and master data for Kasturi & Sons Limited's SAP implementation project. It includes sections on the company's organizational structure, master data setup for finance modules like general ledger, accounts payable, accounts receivable and asset accounting. It also describes key business processes like bill processing, bank reconciliation, payment processes for expenses, donations, rent etc. and configuration requirements for implementing them in SAP.
The performance of heat absorber from zinc on the efficiencyIAEME Publication
The document examines the performance of different sizes of zinc heat absorbers on the efficiency of a double slope solar still, finding that using zinc absorbers covering 10% of the water surface area in the upper layer produced the highest condensed water output of 1.43 liters/day and highest efficiency of 25.99%, while larger 90% coverage produced the lowest efficiency of 15.02%, with efficiency generally decreasing as absorber size increased. Equations and methods are provided for calculating solar radiation, energy transfers, and efficiency of the solar still system.
This document contains contact information for Lauren Taylor, the owner and lead stylist of Dallas Lash Loft located at 3600 Commerce St #101, Dallas, TX 75226. Lauren Taylor can be reached by phone at (214) 377-8979 or by email at lauren@dallaslashloft.com, and more information can be found on the business website at www.dallaslashloft.com.
La Unión Europea ha propuesto un nuevo paquete de sanciones contra Rusia que incluye un embargo al petróleo ruso. El embargo se aplicaría gradualmente durante seis meses para el petróleo crudo y ocho meses para los productos refinados. Los líderes de la UE esperan que estas medidas adicionales aumenten la presión sobre Rusia para que ponga fin a su invasión de Ucrania.
This document describes a student project to develop a prototype file transfer application called Chuck that uses QR codes. The project aims to address the need for easy file transfers between multiple devices. The document outlines the design and development process, including interaction design, technical design of the transmission schema and application, prototype assessment through user testing, iteration of the prototype based on feedback, and evaluation of the effectiveness and future work. Key aspects of the project include creating mockups, building an Android prototype, evaluating it with participants, and improving the prototype based on results.
This document is a software requirements specification for an unnamed project. It provides an introduction, describes the overall product perspective and features, identifies user classes and characteristics, and outlines the operating environment. The document also covers system features, external interface requirements, non-functional requirements, and includes appendices for a glossary, analysis models, and issues list.
This document begins with the details of Concept of Operations (CONOPS) and establishes functionalities & processes that are associated with the MyTacks system.
It builds the foundation for the schedule, budget and resources estimates of the project. In addition, the document highlights the risk factors and its associated mitigation strategies. We also enlist the different Work Packages structured according to the list of identified core components of the MyTacks system. Towards the end, this document covers the calculations of the Project Measurement Metrics for the months of May and June, 2014. Using these two as the windows of reference, we then seek to perform a comparison of the variation of the values and then determine whether the project is currently within the schedule and budget.
This document provides instructions for drafters to revise Process Safety Management (PSM) boundary drawings in ProjectWise and MicroStation. It describes opening the existing PSM boundary drawing, verifying the metadata is correct, applying a standard border if needed, and revising the drawing according to the document request. Drafters are instructed to save the revised drawing and update the metadata before checking it back into ProjectWise.
This document provides a project control plan for a project to develop new oil and gas fields. It outlines the project objectives, background, scope and key interfaces. It then describes the project control organization and responsibilities, early project requirements including planning meetings and interface management, as well as the approaches to cost control, scheduling, progress measurement and reporting. The goal is to deliver the project on baseline cost and schedule through close monitoring and management of schedule, cost, risk and changes.
The project scope document outlines the HRIS with ESS project for GenRays. Key details include:
- The project aims to improve productivity, talent management, reporting capabilities and integrate various systems by consolidating databases and implementing new HRIS modules.
- Stakeholder requirements and acceptance criteria are defined for each system component.
- The work breakdown structure outlines the project deliverables and timeline across initiation, planning, execution, and closing phases.
- The document also addresses the project budget, resources, assumptions, risks and constraints.
The document provides a Software Project Management Plan (SPMP) for developing software for Nirvana National Bank's ATM project. It outlines the project scope, objectives, assumptions, constraints, deliverables, schedule and budget. The SPMP will guide Terasoft's project manager and participants in conducting the software development effort. It describes start-up, work, control, technical, and supporting plans and processes to be followed. The SPMP establishes the initial project baseline and defines how it will be updated and changed over time. It also references various project documents and IEEE software engineering standards that will be adhered to.
This is a sample handover plan aimed at providing ready to use tool in situations where a project manager exits a project before finish and handover to a new project manager. also useful in cases where functional/project managers are pulled out of project due to resource curfew situation and project goes on hold.
This document provides a roadmap for implementing a successful identity management project. It outlines conducting a needs analysis to identify problems with the existing user access administration. Key areas to examine include user productivity, excessive administration costs, inconsistent user data, user service issues, and security vulnerabilities. The roadmap then covers determining technology requirements, organizing the project team, selecting an identity management product, implementing the system through project management best practices, and ongoing administration and reporting after rollout.
- Jyoti Tyagi submitted a project titled "Modification in the behavior of Nova Filter Scheduler to enhance the performance in OpenStack cloud" as part of her MSc in Cloud Computing at the National College of Ireland.
- The project aims to assess the behavior of the nova scheduler in OpenStack with the goal of reducing latency when placing virtual machines. It analyzes the default filters of the nova scheduler to understand limitations and attempts to improve performance and resource allocation.
- An experiment was performed to modify essential filters in the scheduler to prove the concept. Various scheduling filters were analyzed to check their impact on performance by changing default values and metrics.
The document describes a project submission for a Masters student's research dissertation on modifying the nova scheduler in OpenStack to enhance performance. The student aims to reduce latency when launching virtual machines by analyzing how scheduling is affected by factors like CPU cores, memory allocation, and disk usage. The submission sheet provides details of the student's name, ID, program of study, module, supervisor, project title, word count, and certification that the work is original. It also includes submission instructions.
This document is a project report for a blood donation application called Quick Blood Donate (QBD). It was created by four computer engineering students at S.V.I.T. Nashik as part of their Bachelor's degree. The report includes an abstract, introduction, problem definition, project plan, software requirements specification, design documents, implementation details, testing approach, screenshots of the application, and plans for deployment and maintenance. It aims to address the issue of connecting blood donors and hospitals in real-time to ensure blood is available when needed.
The performance of heat absorber from zinc on the efficiencyIAEME Publication
The document examines the performance of different sizes of zinc heat absorbers on the efficiency of a double slope solar still, finding that using zinc absorbers covering 10% of the water surface area in the upper layer produced the highest condensed water output of 1.43 liters/day and highest efficiency of 25.99%, while larger 90% coverage produced the lowest efficiency of 15.02%, with efficiency generally decreasing as absorber size increased. Equations and methods are provided for calculating solar radiation, energy transfers, and efficiency of the solar still system.
This document contains contact information for Lauren Taylor, the owner and lead stylist of Dallas Lash Loft located at 3600 Commerce St #101, Dallas, TX 75226. Lauren Taylor can be reached by phone at (214) 377-8979 or by email at lauren@dallaslashloft.com, and more information can be found on the business website at www.dallaslashloft.com.
La Unión Europea ha propuesto un nuevo paquete de sanciones contra Rusia que incluye un embargo al petróleo ruso. El embargo se aplicaría gradualmente durante seis meses para el petróleo crudo y ocho meses para los productos refinados. Los líderes de la UE esperan que estas medidas adicionales aumenten la presión sobre Rusia para que ponga fin a su invasión de Ucrania.
This document describes a student project to develop a prototype file transfer application called Chuck that uses QR codes. The project aims to address the need for easy file transfers between multiple devices. The document outlines the design and development process, including interaction design, technical design of the transmission schema and application, prototype assessment through user testing, iteration of the prototype based on feedback, and evaluation of the effectiveness and future work. Key aspects of the project include creating mockups, building an Android prototype, evaluating it with participants, and improving the prototype based on results.
This document is a software requirements specification for an unnamed project. It provides an introduction, describes the overall product perspective and features, identifies user classes and characteristics, and outlines the operating environment. The document also covers system features, external interface requirements, non-functional requirements, and includes appendices for a glossary, analysis models, and issues list.
This document begins with the details of Concept of Operations (CONOPS) and establishes functionalities & processes that are associated with the MyTacks system.
It builds the foundation for the schedule, budget and resources estimates of the project. In addition, the document highlights the risk factors and its associated mitigation strategies. We also enlist the different Work Packages structured according to the list of identified core components of the MyTacks system. Towards the end, this document covers the calculations of the Project Measurement Metrics for the months of May and June, 2014. Using these two as the windows of reference, we then seek to perform a comparison of the variation of the values and then determine whether the project is currently within the schedule and budget.
This document provides instructions for drafters to revise Process Safety Management (PSM) boundary drawings in ProjectWise and MicroStation. It describes opening the existing PSM boundary drawing, verifying the metadata is correct, applying a standard border if needed, and revising the drawing according to the document request. Drafters are instructed to save the revised drawing and update the metadata before checking it back into ProjectWise.
This document provides a project control plan for a project to develop new oil and gas fields. It outlines the project objectives, background, scope and key interfaces. It then describes the project control organization and responsibilities, early project requirements including planning meetings and interface management, as well as the approaches to cost control, scheduling, progress measurement and reporting. The goal is to deliver the project on baseline cost and schedule through close monitoring and management of schedule, cost, risk and changes.
The project scope document outlines the HRIS with ESS project for GenRays. Key details include:
- The project aims to improve productivity, talent management, reporting capabilities and integrate various systems by consolidating databases and implementing new HRIS modules.
- Stakeholder requirements and acceptance criteria are defined for each system component.
- The work breakdown structure outlines the project deliverables and timeline across initiation, planning, execution, and closing phases.
- The document also addresses the project budget, resources, assumptions, risks and constraints.
The document provides a Software Project Management Plan (SPMP) for developing software for Nirvana National Bank's ATM project. It outlines the project scope, objectives, assumptions, constraints, deliverables, schedule and budget. The SPMP will guide Terasoft's project manager and participants in conducting the software development effort. It describes start-up, work, control, technical, and supporting plans and processes to be followed. The SPMP establishes the initial project baseline and defines how it will be updated and changed over time. It also references various project documents and IEEE software engineering standards that will be adhered to.
This is a sample handover plan aimed at providing ready to use tool in situations where a project manager exits a project before finish and handover to a new project manager. also useful in cases where functional/project managers are pulled out of project due to resource curfew situation and project goes on hold.
This document provides a roadmap for implementing a successful identity management project. It outlines conducting a needs analysis to identify problems with the existing user access administration. Key areas to examine include user productivity, excessive administration costs, inconsistent user data, user service issues, and security vulnerabilities. The roadmap then covers determining technology requirements, organizing the project team, selecting an identity management product, implementing the system through project management best practices, and ongoing administration and reporting after rollout.
- Jyoti Tyagi submitted a project titled "Modification in the behavior of Nova Filter Scheduler to enhance the performance in OpenStack cloud" as part of her MSc in Cloud Computing at the National College of Ireland.
- The project aims to assess the behavior of the nova scheduler in OpenStack with the goal of reducing latency when placing virtual machines. It analyzes the default filters of the nova scheduler to understand limitations and attempts to improve performance and resource allocation.
- An experiment was performed to modify essential filters in the scheduler to prove the concept. Various scheduling filters were analyzed to check their impact on performance by changing default values and metrics.
The document describes a project submission for a Masters student's research dissertation on modifying the nova scheduler in OpenStack to enhance performance. The student aims to reduce latency when launching virtual machines by analyzing how scheduling is affected by factors like CPU cores, memory allocation, and disk usage. The submission sheet provides details of the student's name, ID, program of study, module, supervisor, project title, word count, and certification that the work is original. It also includes submission instructions.
This document is a project report for a blood donation application called Quick Blood Donate (QBD). It was created by four computer engineering students at S.V.I.T. Nashik as part of their Bachelor's degree. The report includes an abstract, introduction, problem definition, project plan, software requirements specification, design documents, implementation details, testing approach, screenshots of the application, and plans for deployment and maintenance. It aims to address the issue of connecting blood donors and hospitals in real-time to ensure blood is available when needed.
The document provides a functional requirements document for an EA research tool called xELArate. It outlines the following:
1. The tool will automatically research VMware data sources to gather potential EA's associated with a customer and automatically evaluate and prioritize them.
2. It will allow users to save EA relationships for future use and minimize subsequent research needs.
3. The tool will be integrated with VMStar, MyVMware, Oracle and other data sources to perform the research. It will also integrate with the new customer master system.
4. The document describes the in-scope and out-of-scope requirements, proposed system design including the research flow, rule execution, display of results,
Requirements engineering by elizabeth hull, ken jackson, jeremy dick (z lib.org)DagimbBekele
This document provides a summary of the key points from the chapter on requirements engineering:
1) It introduces the concepts of requirements engineering and how it relates to systems engineering and the system development lifecycle. It discusses the importance of requirements traceability and modelling in requirements engineering.
2) It presents a generic process for requirements engineering that involves context establishment, process introduction, information modelling, and detailed process steps.
3) The chapter emphasizes the importance of requirements traceability throughout the lifecycle and discusses approaches like elementary traceability and satisfaction arguments to demonstrate traceability.
This document provides instructions for accessing and filling out Luminant's document request form. It describes how to navigate to the form on the company portal, and outlines the key information to include when submitting a request, such as the project number, requester details, site location, type of request, drafting requirements, document types, distribution list, and requested due date. An example screenshot of a completed form is also included. The instructions are intended to help users efficiently submit documentation requests through the standardized online form.
This document provides a summary of a thesis submitted by Justin M. Ha in partial fulfillment of the requirements for a Bachelor of Applied Science degree. The thesis defines a project management process model for an e-commerce solutions provider engaging in projects to create and launch new websites for clients. It begins with an introduction that provides background on e-commerce and project management. A literature review then covers electronic commerce, project management principles and methodologies, and system development life cycles. The document outlines Ha's research methodology and introduces the e-commerce solutions provider, Novator Systems Ltd. It then presents a new "Standard Web Site Creation Process" model tailored for Novator's project management needs. The conclusion reflects on the outcomes and limitations of the
Are you looking to write down a Project Management Plan and don't how to start.
Here is a free Project Management Plan template with embedded instructions from Simplilearn.
Completely free!! Go ahead and use it!
This document provides a plan for a small IT project. It outlines the project objectives, scope, resources required, estimated costs, and deliverables. The project scope involves developing and implementing a new equipment booking system. Key resources will include a project manager, business analyst, and application developer. The total estimated cost is $XXX, including internal staffing costs and external consulting fees. The main deliverables will be a new booking system with functionality for staff and students.
Proposal for development of Music Distribution Website proposalMakeNET
This User Requirement Specification was commissioned by a major IT vendor. The client wanted a possible way of distributing music legally on compact disk media. Since then the industry has changed and unfortunately the project did not go ahead :(. This was my first attempt as a self employed software engineer.
Proposal for development of Music Distribution Website proposal
ProcessGuide
1. 1601 Bryan Street, Dallas, TX 75201
Document Control and Drafting
Procedures
This guide is designed to standardize and simplify the procedures for requesting
drafting, revising and creating new drawings, and controlling documents.
08Fall
2. Drafting Procedures Rev # 0 Page 2 of 36
Rev Date: 05/01/2015
Drafting Procedures Rev# 0 Document # 1
Use: Reference
Prepared by: Arc Light 4/25/2015
Reviewed by: Drawings and Records Coordinator [Type name and date]
Approved by: Document Control Supervisor [Type name and date]
Effective Date: [Type effective date]
Required Review Frequency: 6 months or as needed
Table of Contents
1. Introduction......................................................................................................4
1.1. Using this document...................................................................................................4
1.2. Using this document: Who should use it ....................................................................4
1.3. Using this Document: Roles and Responsibilities ......................................................5
2. Change Management ......................................................................................6
2.1. Section Description ....................................................................................................6
2.2. Revising the Document ..............................................................................................6
3. Drafting and Document Control Workflow....................................................7
3.1. Section Description ....................................................................................................7
4. Tools.................................................................................................................8
5. Drafting Requirements....................................................................................8
5.1. Section Description ....................................................................................................8
5.2. Drafting Requirements for A/E firms...........................................................................8
5.3. Drafting Requirements for Project Leads ...................................................................8
5.4. Redline/Field Markup Requirements ..........................................................................9
5.5. Drafting Requirements for FES Document Control ....................................................9
6. Requesting Drafting ........................................................................................9
6.1. Section Description ....................................................................................................9
6.2. Submitting Doc Requests.........................................................................................10
6.3. Finding Drafter RACFID in Outlook: .........................................................................14
6.3. Assigning Drafting ....................................................................................................16
6.4. Processing Drafting Requests..................................................................................16
6.5. Completing Drafting..................................................................................................16
7. ProjectWise....................................................................................................18
7.1. Searching ProjectWise for documents .....................................................................18
7.2. Searching from General Tab Using Document File and Folder Data.......................19
7.3. Searching from Attributes Tab Using Additional Metadata.......................................20
7.4. Searching ProjectWise Tips and Tricks....................................................................20
7.5. Adding Hardcopy Drawings to ProjectWise..............................................................21
7.6. Creating a New User (ProjectWise Administrators) .................................................22
8. Existing Drawings .........................................................................................23
8.1. Section Description ..................................................................................................23
8.2. Processing Transmittals from Plants........................................................................23
8.3. Creating a DGN and CIT from a PDF.......................................................................23
3. Drafting Procedures Rev # 0 Page 3 of 36
Rev Date: 05/01/2015
8.4. Creating a New Version of Drawing for Drafting ......................................................25
8.5. Checking In/Out Drawings for Revision....................................................................26
8.6. Voiding and Superseding Drawings .........................................................................26
9. New Drawings................................................................................................27
9.1. Section Description ..................................................................................................27
9.2. Creating a Reserve Drawing “Document” Number...................................................27
9.3. Assigning Drawing Numbers ....................................................................................29
9.4. Applying Standard Borders to New Drawings ..........................................................29
10. Changing Print Level Display.....................................................................29
10.1. Using MicroStation .................................................................................................29
10.2. Using the Settings Menu: .......................................................................................30
11. Review and Approval ..................................................................................31
11.1. Section Description ................................................................................................31
11.2. Emailing Check Prints to Requestors.....................................................................31
11.3. Processing Review Comments ..............................................................................31
12. Signing and Releasing Approved Drawings.............................................31
12.1. Section Description ................................................................................................31
12.2. Changing Drawing State ........................................................................................31
12.3. Creating a PDF File................................................................................................32
12.4. Changing Drawing State to Released ....................................................................32
13. Distribution ..................................................................................................33
13.1. Section Description ................................................................................................33
13.2. Distributing Completed Drawings ...........................................................................33
13.3. Alerting Users Drawing is Available .......................................................................33
14. Revising PSM Boundaries (Oak Grove Only) ...........................................33
14.1. Drafting on Ammonia Drawings..............................................................................33
14.2. Revising PSM Boundaries on Raster Drawings .....................................................34
Index ...................................................................................................................36
4. Drafting Procedures Rev # 0 Page 4 of 36
Rev Date: 05/01/2015
1. Introduction
1.1. Using this document
This document outlines standard Drafting and Document Control
procedures used by drafters, engineers, project leads and Document
Control Team members. This document simplifies and standardizes current
drafting and document control procedures and ensures compliance with
drafting and Document Control requirements.
This document describes the following processes:
• Submitting Doc Requests
• Assigning Doc Requests
• Processing Doc Requests
• Searching ProjectWise
• Adding Hardcopy Drawings to ProjectWise
• Creating new users in ProjectWise
• Creating DGN and CIT files from PDF files
• Creating new versions of drawings
• Processing transmittals from plants
• Checking in and out drawings for revision
• Creating reserve drawing numbers
• Assigning drawing numbers
• Applying standard borders to new drawings
• Changing print level displays on standard borders
• Emailing check prints to requestors
• Signing and releasing approved drawings
• Distributing approved drawings
• Posting PDF drawings
• Voiding and superseding drawings
• Revising PSM boundaries for Oak Grove
1.2. Using this document: Who should use it
• Engineers
• Project Leads
• Drafters
• Document Control Team members
5. Drafting Procedures Rev # 0 Page 5 of 36
Rev Date: 05/01/2015
1.3. Using this Document: Roles and Responsibilities
Engineers/Project
Leads/A/E Firms
• Drafting
Requirements
• Submitting Doc
Requests
• Searching
ProjectWise
• Reviewing Drawings
• Approving Drawings
• Signing off on
Drawings
Drafters
• Processing Drafting
Requests
• Searching Project
Wise
• Creating DGN and
CIT files from PDF
files
• Creating new
versions of drawings
• Checking in and out
drawings
• Applying Standard
Borders
• Changing Print
levels on standard
borders
• Emailing check
prints to requestor
• Completing drafting
• Revising PSM
boundaries (Oak
Grove)
Document control
• Drafting
requirements
• Assigning Doc
Requests
• Processing Doc
Requests
• Searching Project
Wise
• Creating new users
in Project Wise
• Creating DGN and
CIT files from PDF
files
• Creating new
versions of drawings
• Processing
transmittals from
plant
• Creating reserve
drawing numbers
• Assigning drawing
numbers
• Distributing
drawings
• Posting PDF
drawings
• Voiding and
superseding
drawings
6. Drafting Procedures Rev # 0 Page 6 of 36
Rev Date: 05/01/2015
2. Change Management
2.1. Section Description
This section describes who owns this document, the process by which this
document should be revised, and how often it should be revised.
2.2. Revising the Document
• Process Owner: Document Control Supervisor
• Reviewer: Drawings and Records Coordinator
• Approver: Document Control Supervisor
A member of the Document Control Team should review this document for
accuracy every six months. Document Control Team members may
request revisions to this document as needed. All revisions are reviewed
by the Drawings and Records Coordinator and approved by the Document
Control Supervisor.
The process for revising the document is as follows:
• Request revisions
• Complete revisions
• Complete Prepared By section
• Change Rev# to next sequential number
• Send revised document to Drawing and Records Coordinator for
review
• Drawings and Records Coordinator completes Reviewed By section
• Send reviewed document to Document Control Supervisor for
approval
• Document Control Supervisor completes Approved By section
• Post revised document to SharePoint
7. Drafting Procedures Rev # 0 Page 7 of 36
Rev Date: 05/01/2015
3. Drafting and Document Control Workflow
3.1. Section Description
This section illustrates the Drafting and Document control workflow.
8. Drafting Procedures Rev # 0 Page 8 of 36
Rev Date: 05/01/2015
4. Tools
While using this guide, users will require access to the following tools:
• SharePoint
• ProjectWise
• Microsoft Outlook
• MicroStation v8i
• Bentley I/RAS B
5. Drafting Requirements
5.1. Section Description
This section contains drafting requirements for A/E firms, Project Leads,
and FES Document Control.
5.2. Drafting Requirements for A/E firms
• Use Luminant border with title block
• Provide original DGN files (will accept DWG AutoCAD 2004)
• Use document number provided by Luminant
• Submit all final documentation to project lead
• Provide affected document list (all drawings, data sheets, and
manuals associated with project)
• Use approval initials and date on original CAD file (not just signed
hard copy)
• Use the drawing number and sheet number for new drawing file
names (ex. B-1906874-456-0001.dgn)
• Avoid using customer fonts or line styles
• Use default color table for new or modified drawings (level 60-
revision clouds and details; color RGB=255, 0, 0; Line Weight=1;
Line Style=0)
• Merge all reference files into single file
• Avoid using nested cells in submitted AutoCAD files
5.3. Drafting Requirements for Project Leads
• Provide Drafting requirements to A/E firms
• Review all as-built drawings and documents before submitting to
Document Control to ensure they comply with requirements
• Request document number from Luminant Document Control
(docccontrol@luminant.com)
• Submit final as-built drawings before the project closes with
transmittal letter to Luminant Document Control
(doccontrol@luminant.com)
9. Drafting Procedures Rev # 0 Page 9 of 36
Rev Date: 05/01/2015
5.4. Redline/Field Markup Requirements
• Mark prints with colored pens/pencils only
o Red=add
o Green=delete
o Blue=notes to drafter
o Black/pencil=notes to self
• Highlight revisions that are not obvious in pink or yellow
• Include preparer’s name and phone number on print (in case drafter
must call with questions)
• Color-scan and email marked prints to Luminant Document Control
(doccontrol@luminant.com)
• Attach field sketches to marked print when required for clarification
• Avoid using Whiteout fluid on markups
• Include tag numbers for valves and equipment prior to submitting
markup
• Include the correct type valve on the markup and indicate whether the
valve is open or closed (closed valves are colored solid)
• Label on pipe drawings if the pipe is underground (depending on type
of drawing this could be a dashed line or just label the pipe as
‘”underground”)
5.5. Drafting Requirements for FES Document Control
• Include superseded/void note near title block (also include in the
beginning of the title in ProjectWise)
• Make a note on superseded/voided drawings indicating the number
of the new drawing that has superseded the old drawing or
equipment
6. Requesting Drafting
6.1. Section Description
This section describes procedures for submitting, assigning and processing
drafting requests. The Fossil Generation Document Control team uses a
SharePoint list, called Doc Requests, for receiving and managing requests.
We’ve created Doc Requests to better serve the Fossil Fleet.
Use Doc Requests to
• Request drafting
• Create a project folder
• Turn over project documents to operations
• Upload (non-project) documents to ProjectWise or Luminant Docs
10. Drafting Procedures Rev # 0 Page 10 of 36
Rev Date: 05/01/2015
• Update metadata (search fields) for documents
• Receive a Luminant drawing number
• Check out documents to revise
• Distribute documents (mail prints or email PDF’s)
• Scan prints of drawings to add to ProjectWise
• Get help with accessing documents in ProjectWise
6.2. Submitting Doc Requests
1. Open Luminant Connect intranet on Internet browser
2. Select Luminant Portal from Quick Connect drop-down menu
3. Click down arrow on Fossil Generation tab
4. Click FES from Fossil Generation menu
12. Drafting Procedures Rev # 0 Page 12 of 36
Rev Date: 05/01/2015
6. Click Document Control
7. Click the Submit a Doc Request icon
13. Drafting Procedures Rev # 0 Page 13 of 36
Rev Date: 05/01/2015
8. Complete at least three fields marked with a red asterisk (Project # or
description, Site, and Type of Request)
14. Drafting Procedures Rev # 0 Page 14 of 36
Rev Date: 05/01/2015
9. Add any additional information
10. Click Save
6.3. Finding Drafter RACFID in Outlook:
1. Create New Email in Outlook
2. Click To: to open Global Address List
3. Enter user name in Search box in Global Address List
4. Right click on correct user name
5. Click Properties
6. See 4 letter/number RACFID in User ID field
16. Drafting Procedures Rev # 0 Page 16 of 36
Rev Date: 05/01/2015
6.3. Assigning Drafting
1. Enter drafter RACFID in Assigned To field
2. Click Save
6.4. Processing Drafting Requests
1. View assignments in SharePoint
2. Go to Doc Request for this drawing
3. Check number of documents listed matches number of documents
attached
4. Change Task Status to appropriate state
5. Add comments as needed for this drawing
6.5. Completing Drafting
1. Open SharePoint
2. Go to Doc Request for this drawing
17. Drafting Procedures Rev # 0 Page 17 of 36
Rev Date: 05/01/2015
3. Edit the information to reflect that drawing is complete:
4. Change status to Complete
5. Click box to indicate you updated primary attributes
6. Click next box to indicate you updated document contents
7. Type appropriate comments in comment box
8. Create a drawing list if there is no transmittal number
9. Input drawing list and names of people that receive copies of drawing in
Distribution box
18. Drafting Procedures Rev # 0 Page 18 of 36
Rev Date: 05/01/2015
10. Click Save
7. ProjectWise
7.1. Searching ProjectWise for documents
1. Double click ProjectWise icon on desktop to open ProjectWise
2. Set Interface and View to “Drawings”
3. Select Operations folder
4. Select folder of plant you wish to search
5. Right click on the folder
6. Click Advanced Search or Search form (depending upon which is
available)
7. Click OK
19. Drafting Procedures Rev # 0 Page 19 of 36
Rev Date: 05/01/2015
7.2. Searching from General Tab Using Document File and Folder Data
1. Enter Search Criteria
2. Click OK if you will not need to make changes to current search criteria
(search window will close when search is running)
3. Click Apply if you will need to make changes to current search criteria
(search window will remain open)
4. Double click on document you need to view in document preview pane
(top right corner)
20. Drafting Procedures Rev # 0 Page 20 of 36
Rev Date: 05/01/2015
7.3. Searching from Attributes Tab Using Additional Metadata
1. Enter Search Criteria
2. Click OK if you will not need to make changes to current search criteria
(search window will close when search is running)
3. Click Apply if you will need to make changes to current search criteria
(search window will remain open)
4. Double click on document you need to view in document preview pane
(top right corner)
7.4. Searching ProjectWise Tips and Tricks
Use Wild Cards * (Asterisk)
• Use to define unknown characters
• Place before and/or after characters or text
• Place between characters or text
• Use when unsure of text placement in a particular field
Examples:
21. Drafting Procedures Rev # 0 Page 21 of 36
Rev Date: 05/01/2015
§ Document Number: enter “2925-1-510190” or use * for a
partial number such as *2925*5101*
§ Title: enter key words such as “Boiler Feed Pump” or *BFP*
or *Boiler*Pump*
§ Project Number: enter *131N023* or 131*023*
• Leave off “4” to capture project numbers from older systems
• Type “NULL” in attribute field to search for blank attribute field
• Use “clear” button to clear all fields of data entered for search,
including selected folder purposes
7.5. Adding Hardcopy Drawings to ProjectWise
[Section reserved for future process]
22. Drafting Procedures Rev # 0 Page 22 of 36
Rev Date: 05/01/2015
7.6. Creating a New User (ProjectWise Administrators)
1. Search for RACFID in Outlook
2. Open New User template in Outlook
3. Enter user information in appropriate fields
4. Select Security group on “Member Of” tab.
23. Drafting Procedures Rev # 0 Page 23 of 36
Rev Date: 05/01/2015
8. Existing Drawings
8.1. Section Description
This section describes how to process transmittals from plants, create
DGN and CIT files from a PDF, check out drawings for drafting, version
drawings and correctly void/supersede drawings.
8.2. Processing Transmittals from Plants
1. Double check markups against drawings listed on transmittal
2. Prepare drawings for drafting
a. Search for drawing in ProjectWise
b. Verify that the metadata matches info on drawing file
c. Check for additional information on PDF metadata
d. Input missing information
e. Change revision to next highest number or to one (1) if previous
revision was a letter)
f. Remove issue date
g. Add transmittal number and engineer or requestor name
[transmittal number, dash, first initial, last name (no spaces)]
h. Change revision status to Revision in Progress
i. Input Project number and/or MOC Request number
j. Change state now or on all at the end
3. Assign a job number and fill out Job Tracking sheet
8.3. Creating a DGN and CIT from a PDF
1. Change PDF to TIFF:
a. Search ProjectWise to find appropriate PDF file
b. Open PDF
c. Click File
d. Select Export
e. Select Image
f. Select TIFF
g. Save TIFF using assigned drawing number
2. Change TIFF to CIT:
a. Open Microstation v8i
b. Click File
c. Select Raster Manager
d. Click File
e. Select Batch Convert
f. Click Add
g. Browse for TIFF files to convert (created above)
24. Drafting Procedures Rev # 0 Page 24 of 36
Rev Date: 05/01/2015
h. Click on file name(s)
i. Double click to open appropriate file
j. Change format to CIT using drop down menu
k. If the files to be converted show a color mode RGB, check the
invert box
l. Click Convert (batch conversion box will appear)
m. Click OK
3. Create DGN from CIT:
a. Open Microstation v8
b. Click File
c. Select New
d. Browse for CIT file
e. Click on appropriate CIT file
f. Change file extension to DGN
g. Click OK (blank screen should appear)
h. Go to Borders
i. Select border size for DGN
4. Revising CIT file:
a. Load I/RAS B (MDL l I/RAS B)
b. Open CIT file
c. Select Placement by Rectangle
d. Click OK
e. Place rectangle inside border
f. Go to I/RAS B
g. Click File
h. Select Save All Layers
i. Go to File Reference
j. Select Detach All Layers
k. Go to File Reference
l. Select Attach All Layers
m. Unload I/RAS B
5. Revising DGN file:
a. Open ProjectWise
b. Complete advance search for the document number
c. Copy metadata Attributes from PDF
d. Right click on file
e. Select Attributes (with selector on Attributes, a list will appear)
f. Click on Copy Attributes
g. Right click on selected PDF
h. Select Open Folder
25. Drafting Procedures Rev # 0 Page 25 of 36
Rev Date: 05/01/2015
i. Drag and drop CIT and DGN files from desktop into folder (files will
go to the bottom of the page)
j. Right Click DGN file
k. Click Attributes (when highlighted, a small window appears)
l. Click Paste Attributes to copy to DGN file
m. Right click on file
n. Select Properties
o. Edit Attributes to reflect current revision information
p. Add any additional metadata
q. Save DGN file
r. Close DGN file
6. New CIT and DGN files:
a. Copy attributes from DGN and paste to CIT file
b. Save CIT file
c. Close CIT file
d. Highlight CIT and DGN files
e. Right click on files
f. Select Set/Scan Reference
g. Select Link sets
h. Click Next 4 times
i. Uncheck box for Enable Priority Search in top left corner.
j. Click Next 3 times
k. Select Finish (an “e” should appear in the bottom right hand corner
of the DGN file to indicate files are linked
l. Select F5 function key to update
m. Place CIT and DGN in order
8.4. Creating a New Version of Drawing for Drafting
1. Search for drawing in Operations folder using document number
2. Identify the latest revision of the drawing
3. Open files to verify metadata between PDF and DGN (compare and
update metadata if needed)
4. Right click on DGN file
5. Select New
6. Select Version
7. Select OK
8. Right click on new DGN version
9. Select Properties
10.Select Attributes tab
a. Update metadata
b. Delete Issue Date
c. Change Rev. Number (use 0 in front of single digits)
d. Add transmittal number (example: 12345-r,jones)
26. Drafting Procedures Rev # 0 Page 26 of 36
Rev Date: 05/01/2015
e. Change transmittal status to Revision in Progress
f. Add Project Number if available
11.Save file
12.Close File
13.Select the new versioned DGN
14.Right click DGN
15.Change state to Working
16.Click Previous twice
17.Right click to check out DGN to draft.
8.5. Checking In/Out Drawings for Revision
1. Highlight drawing to check in/out in ProjectWise
2. Right click on drawing file name
3. Select “Check Out” or “Check In” as appropriate
8.6. Voiding and Superseding Drawings
1. Search ProjectWise for current revision of drawing to be superseded or
voided
2. Verify metadata matches the drawing
3. Verify PDF metadata is complete
4. Version drawing
5. Update metadata with revision information
6. Title drawing SUPERSEDED by (Name) and superseding drawing number
for superseded drawings
7. Title drawing with VOID in front of existing title for voided drawings
8. Right click to change Document Status to Superseded or Void
9. Right click to check out drawing and edit
10.Insert a large watermark across body of drawing:
27. Drafting Procedures Rev # 0 Page 27 of 36
Rev Date: 05/01/2015
11.SUPERSEDED or VOID in Font: 42 Block_Outline (text size should cover
body of drawing)
12.For superseded drawings, type BY and superseding drawing number with
sheet number (use same font at ½ text size of SUPERSEDED)
a. Revision number
b. Revision block remarks (include superseding drawing number, PID,
and Doc Request/Transmittal number)
13. Process drawing normally (i.e., check prints, approval, replace PDF, etc.)
9. New Drawings
9.1. Section Description
This section describes drafting procedures for new drawings, reserving
drawing numbers and adding standard borders.
9.2. Creating a Reserve Drawing “Document” Number
1. Select folder in ProjectWise where document will reside
2. From menu select, “Document/New/Document
3. Metadata Form will automatically open
28. Drafting Procedures Rev # 0 Page 28 of 36
Rev Date: 05/01/2015
4. Complete ALL of the following information in General Tab:
§ Name = Drawing # “-“Sheet “.file ext”
§ Example – 123456-0003.pdf
§ Use four digits for sheet number
§ Description = Drawing # “-“Sheet
§ Example – 123456-0003
5. Complete ALL of the following information in Attributes Tab
§ Station
§ Station Name
§ Document No.
§ Sheet
§ Controlled Document No. & Sheet (if applicable)
§ Unit - if Known
§ DWG Type – (Examples: Architectural, Civil, Electrical,
Mechanical)
§ Vendor (Who is making the new drawing) (Example: Burns
& McDonnell)
§ Title (Example: New Drawing – Boiler Feed Pump Wiring
Diagram)
§ Transmittal = “Doc Request #-Requestor” (Example – 40052
C.Alston )
§ Transmittal Status = Reserve
§ Project No. (Example 4159L025)
6. Click Save to save New Drawing Metadata
29. Drafting Procedures Rev # 0 Page 29 of 36
Rev Date: 05/01/2015
9.3. Assigning Drawing Numbers
1. Open Operations folder in ProjectWise
2. Select appropriate plant folder
3. Right click to open Advance Search form
4. Search for similar drawing types to drawing for which you need drawing
number
5. Find the last drawing number of similar drawing types
6. Select the next number in the sequence (i.e. if pump 001, 002, 003 exist,
assign pump 004)
9.4. Applying Standard Borders to New Drawings
1. Open ProjectWise
2. Select Luminant folder
3. Select Documents folder
4. Select Luminant folder
5. Select Operations (Controlled Engineering Documents) folder
6. Select 0 - Drafting Standards folder
7. Select Borders folder
8. Select Luminant Reference Borders folder
9. Select New Drawing Templates folder (open borders from this folder)
10.Choose size of border needed
11.Double click to open border
12.Complete all fields with the appropriate information (this will automatically
populate the metadata)
13.Change “Print” level in standard borders
14.Select Level Display
15.Highlight the border reference file
16.Select the applicable print level (Construction, Check, Final)
10. Changing Print Level Display
10.1. Using MicroStation
1. Click Primary Tool box
2. Select Level Display
3. Select Reference Border file
4. Highlight level to turn on/off.
30. Drafting Procedures Rev # 0 Page 30 of 36
Rev Date: 05/01/2015
10.2. Using the Settings Menu:
1. Select Level Manager
2. Select Add and Change Level Data
3. Select appropriate print level
Reference
Border file
31. Drafting Procedures Rev # 0 Page 31 of 36
Rev Date: 05/01/2015
11. Review and Approval
11.1. Section Description
This section describes the procedures for reviewing revised drawings,
adding comments to drawings for further revisions, and approving
completed drawings.
11.2. Emailing Check Prints to Requestors
[Section reserved for future process]
11.3. Processing Review Comments
[Section reserved for future process]
12. Signing and Releasing Approved Drawings
12.1. Section Description
This section describes how to change drawing state, create a PDF of the
approved drawing, release drawings and complete Doc Requests on
SharePoint.
12.2. Changing Drawing State
1. Receive notice that drawing has been approved and the date of approval.
2. Check sign off list for requestors name and initials
3. If not on list, contact requestor and get their 3 initials for sign off
4. Give new name and initials to Janice Stephens to add to the initial list
5. Open ProjectWise
6. Select Operations folder.
7. Right click on appropriate plant folder
8. Click Advanced Search
9. Search by transmittal or Doc Request number in the transmittal number
box with *Wild Card before and after the number
10.Click Apply at bottom of window (drawings will appear behind window)
11.Close window or move it out of the way
12.Right click on DGN file of the drawing you want to sign off
13.Click Properties (window will open)
14.Change transmittal status to Closed
15.Change document status to appropriate state
16.Input Revision Number in appropriate upper and lower boxes
17.Input Revision Date, Revision Description, Initials of Drafter, Checker and
Approver fields with appropriate information
18.Add any other information in the primary and secondary fields
19.Update More Attributes page with additional information
32. Drafting Procedures Rev # 0 Page 32 of 36
Rev Date: 05/01/2015
20.Click Metadata Complete box
21.Click Content Approved box
22.Click Save
12.3. Creating a PDF File
1. Locate DGN file in ProjectWise
2. Right click on name of DGN file
3. Select Attributes (when selector is on Attributes, a list will appear)
4. Click Copy Attributes
5. Right click on CIT file if drawing has one
6. Select Attributes (when highlighted small window appears)
7. Click Paste Attributes
8. Right click on files to check out the drawing and the CIT
9. Double click the DGN file of the drawing to open
10.Check the revision box on the drawing
11.Input date and initials as needed
12.Remove Check Print stamp
13.Create a print of the drawing for distribution
14.Save a PDF of the drawing on your desktop
15.Right click on the DGN file of the drawing
16.Click Open Folder
17.Right click DGN file
18.Click Properties
19.Check the properties of your new revision against the properties of the
previous PDF file to see if any equipment numbers or other information
should be added to the new revision properties
Note: If you make changes, you will need to copy them to the CIT file
so they match.
20. Right click the previous revision PDF file (a box will appear)
21. Create a new version of PDF
23. Copy your attributes from DGN file to the new PDF file.
24. Right click on the new PDF file (a list will appear)
25. Click Properties (a window will open)
26. Click on the General tab.
27. Click Advanced (on right side of window, midway down)
28. Click Import (a window will open asking are you sure you want to replace
document)
29. Click Yes (a box will appear asking if you want to use old filename or use
the new filename)
30. Use new filename.
31. View PDF after you import it to verify that it is the correct PDF
12.4. Changing Drawing State to Released
1. Highlight both DGN & the CIT files
2. Right click on the DGN file
33. Drafting Procedures Rev # 0 Page 33 of 36
Rev Date: 05/01/2015
3. Click Change State
4. Change the state to Released
5. Check the new revision PDF to ensure state is Issue
6. Right click on DGN and CIT files to check in
7. Open SharePoint
8. Locate Doc Request for this drawing
9. Edit the information to reflect that drawing is complete:
10.Change status to Complete
11.Click box to indicate you updated primary attributes
12.Click next box to indicate you updated document contents
13.Type appropriate comments in comment box
14.Create a drawing list if there is no transmittal
15.Input drawing list and names of people that receive copies of drawing in
Distribution field
16.Click Save
13. Distribution
13.1. Section Description
This section describes procedures for distributing completed drawings to
the Distribution list specified on the Doc Request.
13.2. Distributing Completed Drawings
1. Print the Doc Request
2. Include printed Doc Request with all copies of drawings
3. Provide all appropriate documents and prints to Lewis for distribution
4. Contact person who sent Doc Request to inform them the job has been
signed off and distribution is being done
13.3. Alerting Users Drawing is Available
14. Revising PSM Boundaries (Oak Grove Only)
14.1. Drafting on Ammonia Drawings
1. Open ProjectWise
2. Follow folder path: Luminant/Documents/Luminant/Fossil Engineering and
Support/System Engineering/PSM System Boundary Drawings (if Doc
Request does not have “PSM” in description of type of drawing)
3. Select folder for appropriate plant
4. Check list of PDF’s to see if drawing number is in the list.
5. Create PSM Boundary PDF if drawing number is on list
6. Check DGN file notes under the drawing for instructions on how to make a
PSM Boundary PDF
34. Drafting Procedures Rev # 0 Page 34 of 36
Rev Date: 05/01/2015
7. Print out yellow highlighted PSM Boundary drawing (if affected drawing
has never been revised and drawing is a vector drawing)
8. Change vector lines on the drawing to color #5(purple) to indicate the
PSM Boundary
9. Create color Check Print of drawing for Craig Birkenfeld to verify PSM
Boundary is correct
10.Revise drawing once PSM Boundary is correct
11.Cloud revision changes
12.Place clouds and revision number to level 60
13.Input date and initials on Level 60 in Check Print box
14.Change clouds and Check Print box to color #3
15.Create a rectangle box on your working level above the title box
16. Type VERIFY PSM IMPACT into rectangle box in color #2, weight 1, all in
capital letters (see Oak Grove drawing 100334-94900020 as an example)
17.Change color to #5 for revisions on the PSM Boundary to match the
boundary
18.Place initials of drafter and requestor in Check box
19.Send requestor a black and white PDF Check Print for approval
20.Send Craig Birkenfeld a color PDF for final approval once requestor has
approved changes
21.Date and Initial drawing and remove Check Print stamp upon final
approval
22.Print out drawings as needed in black and white
23.Create black and white PDF for Operations folder in ProjectWise
24.Create color code box in drawing before creating color PDF for Boundary
folder
25.Draw rectangle
26.Create small color-filled rectangle in color #5 inside first rectangle
27.Put am equal sin space PSM BOUNDARY to right of color-filled rectangle
(see Oak Grove 10034-94900020 for example)
28.Create color PDF of PSM BOUNDARY drawing to be placed in the
Boundary Folder.
29.Replace existing PSM BOUNDARY PDF with new color PDF
30.Update ProjectWise with updated DGN and updated PDF in Operations
folder
31.Send copies of updated drawings to Lewis for distribution
14.2. Revising PSM Boundaries on Raster Drawings
1. Version drawing
2. Revise drawing as you would a regular raster drawing
3. Cloud revision changes
4. Change clouds and revision number to level 60
5. Input date and initials on Level 60 in Check Print box
6. Change clouds and Check Print box to color #3
7. Create a rectangle box on your working level above the title box
35. Drafting Procedures Rev # 0 Page 35 of 36
Rev Date: 05/01/2015
8. Type VERIFY PSM IMPACT into rectangle box in color #2, weight 1, all in
capital letters (see Oak Grove drawing 100334-94900020 as an example)
9. Create black and white PDF Check Print for the revised drawing.
10.Send requestor a black and white PDF Check Print for approval
11.Send PDF to Craig Birkenfeld for final approval if indicated on Doc
Request
12.Date and Initial drawing and remove Check Print stamp upon final
approval
13.Print out drawings as needed in black and white
14.Create black and white PDF for Operations folder in ProjectWise
15.Create color code box in drawing before creating color PDF for Boundary
folder
16.Draw rectangle
17.Create small rectangle inside first rectangle
18.Put am equal sin space PSM BOUNDARY to right of small rectangle (see
Oak Grove 10034-94900020 for example)
19.Print black and white PDF of PSM Boundary
20.Highlight the color code box in yellow on printed copy
21.Search for existing color PDF in PSM Boundary folder
22.Print existing color PDF
23.Mark boundary lines from existing drawing on new drawing with yellow
highlighter (DO NOT HIGHLIGHT NEW CHANGES)
24.Bring printed black and white PDF to Craig Birkenfeld to have him verify
and highlight changes in yellow
25.Bring highlighted drawing to records room to request a records room team
members create a color PDF of the drawing and email it to you
26.Replace the old color PDF with new color PDF in the PSM BOUNDARY
folder
27.Update ProjectWise with updated DGN and updated PDF in Operations
folder
28.Send copies of updated drawings to Lewis for distribution