[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-307345-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-307345-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","project-change-order-2","Project Change Order - 2","","Change Order form #2 for a Workday deployment requests, documents, and approves updates to project scope, configurations, schedule, and integrations. It summarizes high-priority functional and technical scope changes for the City of Grand Prairie project, including additions such as bank accounts, benefit groups, customer contracts, sales items, project budgeting, geofencing, testing support, and multiple template/tool enhancements. It also includes business purpose and reason-by-scope updates, plus billing and purchase-order requirements and an acceptance due date of 08/19/2025.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/forms/","Forms",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/project-change-order-2/307345/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/project-change-order-2/307345.png","ImageObject",442,249,{"name":42,"@type":43},"วิน","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-22","2026-09-19",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",10,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the purpose of this Project Change Order form?","Question",{"text":63,"@type":64},"It is used to request, document, and approve changes to the Workday deployment, including scope, configuration elements, timeline/schedule, integration specifications, resource additions, and other deliverable changes.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What type of changes are included in Change Type?",{"text":68,"@type":64},"The change type is listed as Functional and Technical Scope Updates for Existing Functional Areas.",{"name":70,"@type":61,"acceptedAnswer":71},"What changes are requested in the request description?",{"text":72,"@type":64},"The request includes additions and updates such as additional bank accounts, additional benefit groups, project budgets, late and interest fees automation for customers workstream, customer contracts, sales items, alternate fiscal schedule, P-Card integration, internal projects, and multiple templates/tooling additions.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},307345,1791260548,{"code":4,"msg":82,"data":83},"success",[84,89,94,99,104,109,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":86,"show_sort_weight":87,"slug":88},11,"Presentations",90,"presentations",{"id":90,"doc_module":22,"doc_module_name":25,"category_name":91,"show_sort_weight":92,"slug":93},12,"Resumes",80,"resumes",{"id":95,"doc_module":22,"doc_module_name":25,"category_name":96,"show_sort_weight":97,"slug":98},14,"Invoices",70,"invoices",{"id":100,"doc_module":22,"doc_module_name":25,"category_name":101,"show_sort_weight":102,"slug":103},15,"Posters",60,"posters",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},16,"Social Media",50,"social-media",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":111,"slug":112},17,40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":110,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":136,"language":137,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":12,"update_tm":141,"read_time":30},2336475104736,"https://ap-avatar.wpscdn.com/avatar/22000c4c5e0e5b17e70?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786591360781797222","Project Change Order \\# 2  \nThis change order form is used for requesting, documenting and approving changes to the Workday deployment including but not limited to: changes to project scope; changes for a major configuration element; project timeline/schedule changes; integration specifications changes; addition of resources; or any other deliverable change from the originally planned Workday deployment.  \nSummary  \n\n| Client: | City of Grand Prairie |\n| --- | --- |\n| SOW/Project Name: | PROJ_ 62996/City of Grand Prairie-HCM/FINs Big Bang-Launch |\n| Change Order \\#: | GP CO2 |\n| Project Manager (Client): | Laura Adams |\n| Project Sponsor (Client): | Lisa Norris |\n| Engagement Manager: | James Smith |\n| Acceptance Due Date: | 08/19/2025 |\n| Change Type: | Functional and Technical Scope Updates for Existing Functional Areas |\n| Impact Assessed by: | James Smith |\n| Priority: | High |\n| Billing | Bill under current project |\n| Is new PO\\# required? | No new PO\\# needed |\n\nRequest Description  \n1. Add 14 Additional Bank Accounts  \n2. Add 12 Additional Benefit Groups  \n3. Add Project Budgets to Functional Scope  \n4. Add Late Fees and Interest Fees to Scope for Customers Workstream  \n5. Add Customer Contracts to Scope for Customers Workstream  \n6. Add Sales Items  \n7. Add Alternate Fiscal Schedule for One Company  \n8. Add Cost Reimbursables to Functional Scope  \n9. Add P-Card Integration  \n10. Add Internal Projects to Scope  \n11. Add Project Phases and Tasks to Scope  \n12. Add Project Budgeting to Scope  \n13. Add HCM BP Modifications to Scope  \n14. Increase Supplier Qualification Forms Development in Strategic Sourcing  \n15. Add 6RFX Templates to Scope  \n16. Increase Project Milestone Development to Scope  \n17. Add WSS Contracts Tool  \n18. Increase Level of Effort for Strategic Sourcing Approval Groups  \n19. Add Additional Testing Support  \n20. Add Performance Improvement Template to Scope  \n21. Add Disciplinary Action Form Template to Scope  \n22. Add Geofencing to Scope  \n23. Remove Integrations That Will Not Be Developed from Scope  \n24. Add Integrations That Need to Be Brought into Scope  \nBusiness Purpose / Reason for Change  \n1. Add 15 Additional Bank Accounts a. Reason for Change: Client requires 24 Bank Accounts to set up in Workday for operations. b. Reason for Scope Update: SOW limits the number of Bank Accounts to 10.  \n2. Add 12Additional Benefit Groups a. Reason for Change: Client requires 15 Benefit Groups in Workday to meet eligibility and plan differences to accurately administer benefits. b. Reason for Scope Update: SOW is limited to 5 Benefit Groups.  \n3. Add Project Budgets to Functional Scope a. Reason for Change: Client will utilize Project Budgeting functionality in Workday. b. Reason for Scope Update: Project Budgets are explicitly out of scope in the SOW.  \n4. Add Late Fees and Interest Fees to Customers Workstream a. Reason for Change: Client would like to automate adjustments to invoices/contracts to account for late and interest fees in Customer Contracts. b. Reason for Scope Update: Functionality currently out of scope.  \n5. Add Customer Contracts to Customers Workstream a. Reason for Change: Client seeks to further automate billing for recurring invoice fees based on Customer Contracts; requires functionality setup in Workday. b. Reason for Scope Update: Functionality currently out of scope. c. Data conversion limited to 1550 customer contracts.  \n6. Add Sales Items a. Reason for Change: Additional functionality to further automate adding costs to existing contracts. b. Reason for Scope Update: Functionality currently out of scope.  \n7. Add 1 Alternate Fiscal Schedule for One Company a. Reason for Change: Client requires a second fiscal schedule. b. Reason for Scope Update: Original scope includes only one fiscal schedule.  \n8. Add Cost Reimbursables to Functional Scope a. Reason for Change: Accounting functionality our group needs to configure for existing Scope Sync items. b. Reason for Scope Update: No","cbCaihPwxR0v6ylx","https://ap.wps.com/l/cbCaihPwxR0v6ylx","pdf",950328,8,"English","# Summary\n## Request Description\n## Business Purpose / Reason for Change","[{\"question\":\"What is the purpose of this Project Change Order form?\",\"answer\":\"It is used to request, document, and approve changes to the Workday deployment, including scope, configuration elements, timeline/schedule, integration specifications, resource additions, and other deliverable changes.\"},{\"question\":\"What type of changes are included in Change Type?\",\"answer\":\"The change type is listed as Functional and Technical Scope Updates for Existing Functional Areas.\"},{\"question\":\"What changes are requested in the request description?\",\"answer\":\"The request includes additions and updates such as additional bank accounts, additional benefit groups, project budgets, late and interest fees automation for customers workstream, customer contracts, sales items, alternate fiscal schedule, P-Card integration, internal projects, and multiple templates/tooling additions.\"}]","Project Change Order - 2 | PDF",1789848176]