ࡱ> Q mbjbjaa E e ed/U!U!U!U!U!i!i!i!8!5"i!Fb""""" $Va$}$FFFFFFF$HK?FU!$ $ $$$?FU!U!""4TF'''$FU!"U!"ME'$F''g?A"FG$R3@9EjF0FM@:L%%ZL4AA&LU!A$$'$$$$$?F?F&6$$$F$$$$L$$$$$$$$$  : SECTION 013200 CONSTRUCTION PROGRESS DOCUMENTATION Maintain Section format, including the UH master spec designation and version date in bold in the center columns of the header and footer. Complete the header and footer with Project information. Revise this Section by deleting and inserting text to meet Project-specific requirements. This Section uses the term "Architect." Change this term to match that used to identify the design professional as defined in the General and Supplementary Conditions. Verify that Section titles referenced in this Section are correct for this Project's Specifications; Section titles may have changed. Delete hidden text after this Section has been edited for the Project. GENERAL RELATED DOCUMENTS Drawings and general provisions of the Contract, including General and Supplementary Conditions and other Division01 Specification Sections, apply to this Section. The Contractor's attention is specifically directed, but not limited, to the following documents for additional requirements: The current version of the Uniform General Conditions for Construction Contracts, State of Texas, available on the web site of the Texas Facilities Commission. The 91Ƶs Supplemental General Conditions and Special Conditions for Construction. SUMMARY A Construction Project Management (CPM) schedule is a mutually-agreed construction plan that demonstrates to the Owner that the Contractor has considered all elements of the construction process, has conformed to the requirements of the Contract, and can and will execute the activities within the contractual time frames. The CPM schedule also may be used as a tool for communication, re-examination of methodology and settlement of disputes. Section includes administrative and procedural requirements for CPM project scheduling. DEFINITIONS Owners Designated Representative (ODR): As defined in the Uniform General Conditions (UGC). This term is used interchangeably with Owner. Architect/Engineer: As defined in the UGC. Contractor: As defined in the UGC. The Contractor is generally the responsible party for maintaining the Schedule as defined in this document and in the contract agreement. ORGANIZATIONAL STRUCTURE (OS) The OS defines scheduling team members and provides a hierarchy based on each team members role. The organizational breakdown follows this structure: Owners Designated Representative (ODR) Architect/Engineer (A/E) Contractor PRODUCTS SOFTWARE Microsoft Project and Oracle Primavera P6 are the only acceptable methods for providing scheduling data to the Owner. Certain terms may be used in the scheduling sections that only apply to a specific scheduling software and are clearly identified. PROJECT SCHEDULE (DETAILED REQUIREMENTS) OVERVIEW Develop the schedule using the Critical Path Method. Represent the work for each phase or area by at least one summary activity that cumulatively indicates the entire Construction Schedule. Clearly identify and adhere to milestone dates on the schedule. Do not change milestone dates without written approval of the Owner. Do not include constraints unless specifically allowed in this specification. Submit any use of constraints that are unavoidable in writing for the Owners approval. Clearly identify in the schedule the activities necessary to accomplishment of the time(s) for completion of the Project and set forth in the Contract. If the schedule indicates earlier completion time(s) than set forth in the Contract, the difference between the schedule and Contract dates shall be considered part of the total float available. This float is a resource available to both Owner and Contractor or as otherwise defined in the applicable Owner-Contractor agreement. Incorporate 10% float into the schedule as a single activity at the end of all construction activities and just preceding Substantial Completion. Submit a written request to the Owner for approval prior to use of float time. The Contractor is responsible for assuring that applicable work activities, as well as those of consultants and trade contractors at all sub-tiers, are included in the schedule. Show in the schedule the sequence and interdependence of activities required for complete performance of the Work. The Contractor is responsible for assuring that all work sequences are logical and the schedule shows a logical plan of work and critical path. Consider and include normal weather conditions in the planning and scheduling of all work influenced by high or low ambient temperatures, wind and/or precipitation to ensure completion of all work within the contract time. In assessing normal weather conditions, refer to average historical climatic conditions based on locality as maintained by the National Oceanic and Atmospheric Administration (NOAA) for the William P. Hobby Airport. Use NOAA data as the basis for determining the number of weather days permitted in the schedule. Proposed durations assigned to each activity shall be the best estimate of time required to complete the activity considering the scope and resources planned for the activity. If using Primavera P6, define each activity with as many activity codes as applicable. The global activity codes will be preset and will not be modified unless the scheduling group agrees to those changes. If requested by the Owner, furnish a written narrative of the determination of durations for critical activities. Include the number of crews, crew composition, number of shifts per day, number of hours in a shift and the number of workdays per week. Provide a list of the major construction equipment intended for use during operations including types, number of units, unit capacities and the proposed time each piece of equipment will be on the job. Key the equipment list to the activities that the equipment will support. LEVEL OF DETAIL REQUIRED. The level of detail shall be a function of the complexity of the work involved. The total number of activities shall be subject to approval by the Owner. Activity Durations: The smallest increment of time allowed is one (1) full day or is represented as a milestone with a zero (0) day duration activity. Construction activities shall represent the continuous work of a definable crew in a defined work area or location and have a duration not longer than ten workdays, unless deviation is approved by the Owner. Non-construction activities (such as design, procurement, fabrication, etc.) may have durations in excess of ten workdays. Procurement Activities: Include activities associated with the submittal, approval, procurement, fabrication and delivery of long lead materials, equipment, fabricated assemblies and supplies. Long lead procurement activities are those with an anticipated procurement sequence of more than 90 calendar days. Mandatory Detail Overall Milestones: At minimum, list the following activities at the top of the schedule: Contract Dates Activity to be linked to Contract Start and Completion milestone Contract Start Date A constrained milestone Contract Duration Base Bid & Alternates Contract Completion Date Substantial Completion, a constrained milestone Contract Delay Claimed by Contractor Contract Delay Awarded by Owner Current Contract Completion Date by Owner Linked to Contract Completion Date and Contract Delay Awarded by Owner Current Project Completion Date by Contractor Linked to Contractors actual progress schedule Owner Milestones: Design Review Meetings Design Approvals UH Fire Marshal Inspection UH Fire Marshal Approval Substantial Completion Inspections FFE Installation Move-In Artwork Installation Design Milestones: Include at a minimum the following milestones. Schematic Design: Start of Schematic Design Phase 100% SD Submission Owner Design Review (two weeks) Design Review Meetings (one week) Owner Approval of 100% SD Package Design Development: Start of Design Development Phase 50% DD Submission Owner Design Review (two weeks) Design Review Meetings (one week) Owner Approval of 50% DD Package 100% DD Submission Owner Design Review (two weeks) Design Review Meetings (one week) Owner Approval of 100% DD Package Construction Documentation: Start of Construction Documentation Phase 50% CD Submission Owner Design Review (two weeks) Design Review Meetings (one week) Owner Approval of 50% CD Package 90% CD Submission Owner Design Review (two weeks) Design Review Meetings (one week) Owner Approval of 90% CD Package Issuance of Construction Package Construction Milestones: Include at minimum the following milestones: GMP: GMP Submittal Approval of GMP Trade Contractor Procurement: 100% CDs (Finish Milestone) Bid Day Submittal/Material Procurement: Submittals Complete Doors, Frames, Hardware Approved Door Frame Delivery Windows Approved Curtain Wall Approved Steel Approved AHUs Approved Structure: 1st Pier Pour 1st Slab Pour Concrete Structure Top Out Tower Crane Up Tower Crane Down Man/Material Hoist Up Man/Material Hoist Down Structural Steel Top Out Dry-In: Exterior Wall Start Window Start Curtain Wall Start Roof Start Temporary Dry In Dry In Interior Construction: MEP Overhead Start Interior Studs Start Permanent Power Conditioned Air On 1st In Wall Inspection 1st Wall Cover-Up Approval 1st Overhead Inspection 1st Overhead Cover Up Approval Elevator Temporary Use Start Completion: 1st Contractor Punch List 1st A/E Punch List TAB Start Commissioning Start Substantial Completion Owner Move-In Final Completion LINKAGE REQUIREMENTS: The following requirements are meant to eliminate duplication of data and possible inconsistencies, while maintaining data integrity and responsibility. Links within an Individual Schedule File: The Contractor shall create and update predecessor and successor links within an individual schedule. These links will be subject to review by the parties outlined in the Organizational Structure above. No activity shall have less than one predecessor and one successor, unless it is the first or last activity in the entire schedule. Use of Lag: Do not use Start-to-Finish relationships. Use of Negative Float: Do not include Negative Float in the baseline schedule. STATUS SCHEDULES Submit schedules as to their current status by updating the latest data as often as the responsible party feels necessary to maintain accurate records and presentations, but no less frequently than the timeline and requirements below. Design Schedule: Update the design schedule by the last Friday of the month. The data date to be used shall be at least the first of the month, if not more current. The Architect/Engineer shall perform the design schedule update. Baseline Schedule: Include data about the Project that represents its state before the work actually began. In Microsoft Project, a baseline is a copy of the Start, Finish, Work, and Cost for all the Resources and Assignments, plus Duration for all the Tasks in the Project. Preconstruction Schedule: Update the preconstruction schedule by the last Friday of the month. The data date to be used shall be at least the first of the month, if not more current. The Contractor shall perform the update. Construction Schedule: Update the construction schedule by the last Friday of the month. The data date to be used shall be at least the first of the month, if not more current. The Contractor performs the update: Provide a narrative describing the changes from the previous months version Should the schedule fall behind, submit an appropriate recovery plan in addition to the requirements above. Current Schedule: Once a month, the scheduling team shall meet to update the schedule. All schedules shall be opened and updated. This process will not change the data date of the individual files, but will incorporate all changes from all schedules. The purpose of these meetings is to analyze the overall changes to the schedule and determine the cause of the variances. Should the schedule fall behind, the Contractor shall submit an appropriate recovery plan. GMP Milestone Schedule: Include major project activities and significant project milestones in the GMP milestone schedule. CALENDARS Three calendars may be considered for use. The Contractor shall designate which calendar is used when submitting the baseline schedule. Additional calendars may be added as the need arises, subject to Owner approval. Working Calendar: A 5-day/work week calendar, including all holidays. Use this calendar for all activities not affected by inclement weather. All design and Owner activities will use this schedule. Generally, all construction activities taking place within the confines of an enclosed building will use this schedule. Weather Calendar: A 5-day/work week calendar, including all holidays and weather days. Use this calendar for all activities that could be affected by inclement weather. This schedule is reserved exclusively for the use of the construction team. Contractual Calendar: A 7-day/week calendar. Use this calendar for all activities whose durations are defined by the language of the Contract. APPROVALS Schedules will be reviewed and approved as part of Project development. This section describes those approvals, based on the type of schedule. Schedules will not be considered approved unless the Owner has provided a letter to the Contractor or design professionals. Upon approval, the schedule will be established as the baseline and may not be altered without the Owners written approval. All submissions require submittal of the following reports in electronic PDF format and two hard copies. Predecessor/Successor Report Total Float Report Complete Schedule with Critical Path Outline Design Schedule Approval: The Architect/Engineer shall submit a detailed design schedule to the Owner within 10 calendar days of the Notice to Proceed for design. Construction Schedule Approvals: The Contractor shall submit all construction schedules to the Owner for review prior to approval of the first payment application at the appropriate corresponding phase of the Project. Schedules required for submission are: Preconstruction/Design Schedule GMP Milestone Schedule(s) Detailed Baseline Construction Schedule SCHEDULING SUBMITTALS Design Schedule: The Architect/Engineer shall submit for the Owners review and approval an updated, detailed design schedule. The detailed design schedule shall include: Design Milestones (as outlined in the contract documents) Document submissions for review and approval by the Owner Document submissions to the Contractor for bidding and construction Critical deadlines for Owner approvals Scheduled interactions with Owner Anticipated Design Review Sessions with Owner If the schedule has the potential to affect Substantial Completion, the team shall determine possible mitigation strategies including fast tracking and multiple bid packages. Preconstruction Schedules: The Architect/Engineer or Contractor, as applicable, shall submit a Preconstruction Schedule for the Owners review and approval. The Preconstruction Schedule shall be updated monthly, consistent with Section 3.3. The Preconstruction Schedule shall cover the following phases and activities: Proposed Preconstruction activities prior to issuing the GMP Identify activities including budgeting, GMP Pricing and approvals, and subcontractor procurement in a format sufficient to directly relate to the current Design Schedule. At each successive design milestone (100%SD, 50% DD, 100% DD, 50% CD and 90% CD), update the preconstruction activities to coincide with the current direction on the design package. Proposed Procurement activities to be accomplished during the first ninety (90) calendar days after the GMP Identify activities including mobilization, key shop drawings, sample submittals, fabrication and delivery of long-lead elements. Dates should reflect realistic durations. Incorporate procurement activities into the GMP Schedule including all requested revisions. Construction Summary activities to be accomplished during the construction phase(s) Identify activities necessary to properly indicate the approach to scheduling the work areas or phases of the work. Show the approximate duration for each summary activity. Owner shall use the Preconstruction Schedule in the preliminary review of time extension request(s) while the GMP Schedule is being developed. Within fourteen (14) calendar days after receipt by the Owner, the Owner shall notify the appropriate party of its acceptance or concerns. The Architect/Engineer or Contractor, as appropriate, shall respond to the concerns to the satisfaction of the Owner before submittal of the GMP Milestone Schedule. GMP Milestone Schedule: With each submission of a GMP (whether stand alone or part of multiple GMPs), the Contractor shall submit a GMP Schedule for Owner review and approval. Detailed Baseline Construction Schedule: Within seven (7) calendar days following the Notice to Proceed for construction, the Contractor shall submit to the Owner a detailed Baseline Construction Schedule in precedence format (as described in Section 5) for the construction work scope. Schedule shall conform to the requirements outlined in the technical requirements in Part 3. The Construction Schedule shall be reviewed in the following manner: Within fourteen (14) calendar days after receipt by the Owner, the Owner shall notify the Contractor of any comments or concerns. Within seven (7) calendar days after receipt of the Owners request for revisions, with adequate justification, activities, durations, manpower or cost loading, the Contractor shall submit a revised schedule, to the satisfaction of the Owner. The Owner will have final review and acceptance of the schedule. Upon acceptance of the Contractors Construction Schedule, the Owner shall issue a baseline schedule acceptance letter. This letter will outline acceptance of the construction schedule for use as the baseline for evaluation of all Work to be performed. Accepted activities shall not be deleted from the construction schedule. In the event that an activity is no longer appropriate, either by change order or otherwise, the activity shall be given a status with zero (0) duration as of the date such determination is made. The Contractor shall submit an electronic copy of the schedule to the Owner with each presentation. In addition, the Contractor shall submit accompanying schedule reports and graphics as specified in Section 3.8, Required Reports. REQUIRED REPORTS As part of the Detailed Construction Schedule submittals, as well as for each schedule update, the Contractor shall submit the following reports and graphics as indicated (unless otherwise requested by the Owner): Graphics: Detailed CPM Schedule with critical path highlighted (Initial Submittal and Revisions) Executive Summary bar chart (Initial Submittal and Monthly Updates) Short-Interval bar chart including one week look back and three-week look ahead (Weekly) Schedule Reports: Activity listing report showing all schedule activities, sorted by activity number (Initial Submittal) Milestone Summary Report showing both Contract Milestones and Interim Milestones (Initial Submittal) Precedence Report including activity predecessors and successors, sorted by activity number (Initial Submittal and Revisions) Total Float Report sorted by total float (Initial Submittal and Monthly Updates) Early Start Report grouped and sorted by early start date. (Monthly Updates) Variance Report comparing current dates to baseline dates (Monthly Updates) Narrative Schedule Report: Description of the actual work accomplished during the reporting period (Monthly Updates) Description of any problem areas (Initial Submittal and Monthly Updates) Description of current and anticipated delays with recommended corrective actions to mitigate delays (Monthly Updates) Digger Report (only applies to Primavera P6 scheduling) including a list of explanations of proposed modifications, addition, deletions and changes in logic to the approved construction schedule. If modifications are proposed, submit a revised schedule demonstrating the effects of such modifications. (Monthly Updates) SCHEDULE MEETINGS Monthly Schedule Meetings: Once monthly, on a day mutually agreed to by the Owner, Architect/Engineer and Contractor, conduct a meeting to assess the progress achieved during the previous month. The Contractor shall submit a progress schedule listing all the activities completed and in progress for the previous month and activities schedule for the succeeding three weeks. A bar chart directly derived from the Detailed Construction Schedule shall be used to generate the three-week window. Use the same activity numbers and descriptions in the Short Interval Schedule as shown in the Construction Schedule. The Contractor may add further details to monitor this Short Interval Schedule. Project Schedule Review Meetings: Review each project schedule in depth as part of the Projects periodic (weekly or biweekly, depending on the project) Owner/Architect/Contractor meetings. Schedule issues left unresolved during these meetings will be elevated to discussion at the Monthly Schedule Meetings. SCHEDULE MODIFICATIONS If the Construction Schedule no longer represents the actual execution and progress of the Work, the Owner may require the Contractor to submit a revision to the Construction Schedule. The Contractor may also request revisions to the Construction Schedule in the event that planning for the Work is revised. If revisions to the Construction Schedule are required, the Contractor shall submit the proposed changes along with a written narrative of the proposed changes. Such revisions to the Schedule shall not alter any of the Project Milestone dates. If accepted by the Owner, the Contractor shall incorporate the changes into the Construction Schedule. Submit schedule revisions using a copy of the updated Construction Schedule, modified with proposed changes and a narrative explanation of the change(s). Upon acceptance of a revision, the revised Construction Schedule shall be the basis for evaluating future status, impact and/or changes. The Owner shall confirm acceptance in a formal letter to the Contractor. Updating the Construction Schedule to reflect actual progress shall not be considered a revision to the Construction Schedule. SCHEDULE IMPACTS, DELAYS AND TIME EXTENSIONS During the course of the Project, it may be appropriate to revise the schedule to incorporate impacts or delays into the Project Schedule. If the Contractor feels there is a schedule impact that warrants a time extension, the Contractor shall notify and present to the Owner a proposed revised Schedule supporting the claim within forty-eight (48) hours of the occurrence causing the proposed change. Adhere to the following procedure for incorporating impacts into the schedule: Create a schedule activity (or activities) that represent the scope of the change or delay Assign durations to the new activity or activities Determine appropriate schedule logic ties for activities. Assign predecessors and successors to tie into the existing schedule activities. Every effort to mitigate the potential delay by either isolating the impact of the delay or planning work-around approaches to the work shall be considered and incorporated where effective. Load these activities into a copy of the updated schedule that immediately preceded the impact issues time frame. For instance, if an impact issue occurs during mid-April, enter the new activities into the March 31 (status date) update. After the Schedule is recalculated with these impact activities, the Owner shall review the effect on the Project Milestones to determine if the time extension is merited. Submit the impacted Schedule, along with the narrative describing the new schedule activities and logic ties that comprise the impact or delay issues, to the Owner for review and approval. If approved, these impact or delay issues will become a permanent part of the Project Schedule. The Contractor may not unilaterally change the Project Schedule to justify schedule impacts without the approval of the Owner. Activity delays shall not automatically mean that an extension of the Contract Time is warranted or due to the Contractor. It is possible that an impact or delay will not affect the critical activities or cause non-critical activities to become critical. An impact or delay may result in absorbing a part of the available total float. Float is not for the exclusive use of the Contractor. The Owner will grant contract time extensions only to the extent that equitable time adjustments to the activity (activities) affected by the impact or delay exceeds the total float along the critical path of activities at the time of the delay. The Contractor shall request use of float in writing for approval by the Owner in accordance with the Contract Documents. Weather Days not used in previous months may be allocated for the purpose of mitigating the schedule. The Contractor shall use Saturday as a make-up for approved rain day impacts. SCHEDULE LOGS Maintain a schedule log that outlines the following: Identifies conflicts and deviations from the Baseline Project Schedule for the selected package. Provides justification for deviations from the Baseline Project Schedule for the selected package. Aids in the creation of a mitigation plan for recovery of the Baseline Project Schedule. Update the schedule log for review by the Owner, Architect/Engineer and Contractor on a monthly basis. END OF SECTION 013200     91Ƶ Master Specification   Construction Progress Documentation013200 -  PAGE \* MERGEFORMAT 7AE Project #: UH Master: 01.2024   56^ }  " W z   ; l p q Խ{tptpltpththyIhXhta hpdh h9hIhh!hI6h;gh+5h;g6 h+5h;ghIhwOhQP4 h"h"hHh"< h"<h>"<hJh C5B*aJphDrhJh CB*aJphDr hwO0J- h_0J- hh!0J- hjt0J- h%hwO(6U   *6Sgdgd9~gd9~gdS)gd")gd Cgdh!)*6`sz{EGQRSzƿ՛}Ɨ}yr h3gfhph7W h'h' h'hl hd1hLXh,*hK=hl h_hh3gfhM$hO2hChjth >? "#3>orzRXgmwžźŶŲŮhahpdhXh hhh h%h9~h7- hK=hK=h<*rhK=h9~hH h3gfh= h3gfh' h3gfh7WD'(34@IPX`f@AJE[rt%3KV L\#%'./RShlhC(KhpdhfQ=hH h4 hhh[hahXh h<*r hNhM    % ? @ A B K!M!!!!!!!!"""""""1#c#z#######$$$H$I$h$i$$$$;%N%v%%%%%%%%%% hD-/hnhpdh~u hnhnhn hg&Lh9~ hg&Lhn h5Chg&LhfQ=hO2hHh9~hhvjh7-hg&L h88888888888889 939ǿǻ˿ǿhwOh@` hp2h'hl hUh~: hUhShShh!h~: h,*h,*hh,*hhDJ3949I9M9999999:.:1:2:@:a:i:::::::: ;;T;U;];^;g;h;v;w;;;*<A<Q<R<<<<<<<%=-=1=<=F=J=O=S=T=[=\=]=y=z=========>>>!>=>]>^>~>>>>>?hh`h:Lh\ h,*hhwOhh!hlh'hDh@` h~:Ph;]={===_>b?????[@@@@@AgAAAgBZCCCDgdb1!gdngdngdngdfQ=gdvjgdvjgdvjgdgdSgdS?1?2?8?9?a?b?e?q?x???????????????@@@ @@@Z@[@@@@@@@@@@A?A}AAAAAAAAAAAAB B,B¾ hUhr hUh][ hUh` hUh& hUh3hhyIh:Lh3 h^47h h^47h3 h$`hS h$`h3 h][h][ h][h`hwOh`hhh][8,BKBeBfBgBBBBBBBBBBCUCVCYCZCCCCCCCCDDDDDDDDDDDDEEEE&F`FmFFFGGGGGGGGGGGMHNH]HbHHHHHHHHHӿӳӳ׳ӳ˳˯˳˳ϳhUohvUhd1hhyIhhwOh,hShJh h:LhTh][hr hUh& hUh` hUh][EDGEE`FFGGGNHI2JRKKKvLiMM"NNOPgdgdgd~ugd~ugd~fgd~fgd~fgdM$gd. gd. gdegdzgdzgdGgd[=Ngd[=NHHHHH IHINIkIuIIIIIIIIIIJ.J1J2J;JDJhJlJvJJJJJJJJJJJKKK/K0KKKKKKL L%L,L1L6L=LNLXLhLkLlLtLuLvLLLLLLLLLM%MbMcMgMiMhhl#qh]hH~_h[K hUohUo hUoh,hzh`YhUoh:LhvUh,hULiMsMMMMMMNNNNNNNNNOZOdOrOOOOOOOOOOOP PPP5PLPOP_P`PgPPPPPPPPPPQQ}Q~QQQQMRQRdRiRjRRSSMS_SkT{TTɻɴɭ­­ h Rh, h RhwO h Rh h RhN h Rh8hwOheh]hzh8h&hzhd1hh`YhH~_hl#qCPPQQQ*RRRRaSS0T}TTT>UUU?WQW Z?[W[\]^V__`gd,*gd,*gd,*TUUV'VVV+W,W?WPWQWjWmWWWWWWWWWX$XXX3Y4YCYGYrYYYYZZ Z,Z4ZaZbZZZZZZZ[4[?[N[O[U[V[W[[[[[[[\\b\ȽȤȠȤhZBhN h]hwO h]h@) h]h. h]h6hd1h6hh$` hNhNh] hNhwO hNh+^ hUohUoh+^hl#qh,?b\c\f\h\z\{\\\a]]]]]]]]^^4^6^ ___0_C_U_p`q`````` aaa)a0a2avaaaaaaaaaZbfbbbccccldrddddeYeaedeeeeeeeeeeff/f3fxfffhehDhnQhyhwO h@)h@)h]h@)hd1hNhZBh6hO`aa>cd۱fijjjklllllljfjjjjjjjjjjj k k kk?k@kGkHkPkQkmknkkkkkkklll ll l!l+l/l6l7lHlZldlh]h^47hZBh. h,*hCh$`h_whwOh hnQhnQhehnQhyMdlklllllllllllllllllllll mmmmmmm*mNmXmYmompmqmrmsmtmmmmmmm¼˼¼˳ܦ}v} hyI5CJ h'h`hzCJmHnHujh'h`CJUhh`5CJh'h`CJhGhih_^J h;gCJhz~h;gCJ hz~h;ghh;g5CJhih`^JhjhU h_whh!h_whh!+lllllllll4$ H$Ifa$gd;g4 H$Ifgd;gGkd$$Ifl$h% t644 lap yt4$ H$Ifa$gd;ggdOr> h*PR2$ & F *$@&a$6O6 h*PR3$ & F*$@&a$6O6 h*PR4$ & F*$@&a$66 h*PR5$ & F*$@&a$8b8 h*TB1$ *$^ a$8r8 h*TB2$`*$^`a$88 h*TB3$*$^a$88 h*TB4$*$^a$88 h*TB5$ *$^ a$88 h*TF1 $ *$^ a$88 h*TF2!$`*$^`a$88 h*TF3"$*$^a$88 h*TF4#$*$^a$88 h*TF5$$ *$^ a$&R& h*TCH%*$6b6 h*TCE&p*$^`p0Or0 h*EOS'$*$a$<< h*ANT($*$a$ >*B* ph:O: Bh*CMT)$*$a$ B*ph"/" h*CPR^J"/" h*SPN^J"/" h*SPD^J"o" h*NUM^J"/" h*NAM^J*/* h*SI B* ^Jph*/* h*IP B*^Jph,, h*RJUST1$a$>/!> SAhyperlink>*B*^Jphl :U 1:  Hyperlink>*B*^Jph4@B4 50Header 4 H$2/Q2 40 Header Char^J4 @b4 70Footer 6 H$2/q2 60 Footer Char^JHH 9 Balloon Text8CJOJQJ^JaJN/N 8Balloon Text CharCJOJQJ^JaJttjt List Paragraph": 5$7$8$9DH$^CJOJQJ^JmHnHuh h H No Spacing; & F^` CJOJQJ^J_HmH sH tH B' B 5Comment ReferenceCJaJ88 >5 Comment Text=CJF/F =5Comment Text Char OJQJ^J@j@ @5Comment Subject?5\R/R ?5Comment Subject Char5OJQJ\^J.X . @Emphasis6]>/!> ) CCMT CharB*CJOJQJphPK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭VGRU1a$N% ʣꂣKЛjVkUDRKQj/dR*SxMPsʧJ5$4vq^WCʽ D{>̳`3REB=꽻Ut Qy@֐\.X7<:+& 0h @>nƭBVqu ѡ{5kP?O&Cנ Aw0kPo۵(h[5($=CVs]mY2zw`nKDC]j%KXK 'P@$I=Y%C%gx'$!V(ekڤք'Qt!x7xbJ7 o߼W_y|nʒ;Fido/_1z/L?>o_;9:33`=—S,FĔ觑@)R8elmEv|!ո/,Ә%qh|'1:`ij.̳u'k CZ^WcK0'E8S߱sˮdΙ`K}A"NșM1I/AeހQתGF@A~eh-QR9C 5 ~d"9 0exp<^!͸~J7䒜t L䈝c\)Ic8E&]Sf~@Aw?'r3Ȱ&2@7k}̬naWJ}N1XGVh`L%Z`=`VKb*X=z%"sI<&n| .qc:?7/N<Z*`]u-]e|aѸ¾|mH{m3CԚ .ÕnAr)[;-ݑ$$`:Ʊ>NVl%kv:Ns _OuCX=mO4m's߸d|0n;pt2e}:zOrgI( 'B='8\L`"Ǚ 4F+8JI$rՑVLvVxNN";fVYx-,JfV<+k>hP!aLfh:HHX WQXt,:JU{,Z BpB)sֻڙӇiE4(=U\.O. +x"aMB[F7x"ytѫиK-zz>F>75eo5C9Z%c7ܼ%6M2ˊ 9B" N "1(IzZ~>Yr]H+9pd\4n(Kg\V$=]B,lוDA=eX)Ly5ot e㈮bW3gp : j$/g*QjZTa!e9#i5*j5ö fE`514g{7vnO(^ ,j~V9;kvv"adV݊oTAn7jah+y^@ARhW.GMuO "/e5[s󿬅`Z'WfPt~f}kA'0z|>ܙ|Uw{@՘tAm'`4T֠2j ۣhvWwA9 ZNU+Awvhv36V`^PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!g theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] e! ...1z%A-f339?,BHiMTb\fdlmm79;<=?DFGIJLMOPRSYS%(`*+X-h;DP`llmsmmm8:>@ABCEHKNQTUVWX1!@ @H 0(  0(  B S  ? _Hlk14437444 _Hlk156062062 _Hlk134707556deeedddddddddeeHAUAdddddddddee3pq & & XXmwPXttL\[[!!" """b#f###$$$$dddddeeXereeepq & & XXmwPXttL\[[!!" """b#f###$$$$ddeee ›2. ^`Z).vi+C4io*C @` b1!h!M$&k),*Oq+>,8<1Z]1p2QP4?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\]^_`abdefghijklmnopqrstuvwxyz{|}~Root Entry FZG@Data [1TablecLWordDocument ESummaryInformation(DocumentSummaryInformation8MsoDataStoreFGFGGWQPIXFA==2FGFGItem  PropertiesUCompObj r   F Microsoft Word 97-2003 Document MSWordDocWord.Document.89q