Project Manager, Capital Delivery

We need to output HTML fragment with sections: About the role? The posting includes a job summary, duties & responsibilities, minimum requirements & qualifications, preferred experience & skills, job conditions, supervision maybe, etc. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We must preserve all substantive information. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. We need to decide which sections to include: About the role (maybe job summary), Responsibilities (duties & responsibilities), Requirements/Qualifications (minimum requirements & qualifications), Skills (maybe preferred experience & skills), Benefits (none given), Pay (none), Schedule (maybe job conditions includes availability to work all shifts, but schedule not explicit). The posting mentions "Availability to work twenty-four (24) hours per day, seven (7) days per week." That's schedule info. So we could include Schedule section with that detail. Benefits: none mentioned. Pay: none. So we omit those. We also have Supervision section maybe but could be part of Responsibilities. The posting includes "Supervision Will indirectly oversee and supervise support personnel." That's a duty. Could be under Responsibilities. We need to avoid duplication: there are repeated sentences like "Provide monthly and/or quarterly updates of project schedules and budgets." appears twice. We should keep only one instance? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should remove duplicated lines. So we need to deduplicate. Also need to remove boilerplate like "Disclaimers And Definitions", "General Disclaimer", "Application Completion", etc. Also remove "Job Conditions" maybe we keep as Schedule? Actually Job Conditions includes many items like ability to read/comprehend, age, commute, etc. Those are substantive. We could include a section "Job Conditions" as heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not limited to those; we can use other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings only? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be implying those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it". So we should only use those headings. So we need to map content to those headings. Thus we have: - About the role: job summary paragraph. - Responsibilities: duties & responsibilities (list). - Requirements: minimum requirements & qualifications (list). - Qualifications: maybe we could combine Requirements and Qualifications? But they are separate headings; we could put minimum requirements under Requirements, and preferred experience & skills under Qualifications? Or Skills? The examples include both Requirements and Qualifications. Could treat Requirements as minimum, Qualifications as preferred? Or Skills as preferred skills. Let's decide: We have Minimum Requirements & Qualifications (that's a combined heading). Then Preferred Experience & Skills. So we could put Minimum Requirements & Qualifications under "Requirements". And Preferred Experience & Skills under "Skills". Or we could put both under Requirements and Qualifications respectively. Since we have both headings, we can split: Requirements = minimum requirements; Qualifications = preferred experience & skills? But the heading "Qualifications" could be for qualifications (maybe both). However the examples list both Requirements and Qualifications separately. We'll assign: - Requirements: Minimum Requirements & Qualifications (the bullet list). - Qualifications: Preferred Experience & Skills (the bullet list). - Skills: maybe we could also include specific skills like proficiency with Microsoft Office etc. But those are already in minimum requirements. Could put under Skills as well but we already used Skills for preferred. Might be duplication. Better to follow: Requirements = minimum requirements; Skills = preferred experience & skills (since they are skills). Qualifications maybe we could omit if not needed. But we need to only include sections when posting has real specific content. We have content for both minimum and preferred. So we could include Requirements and Skills. Qualifications maybe not needed. But we could also include Qualifications as the same as Requirements? Might be redundant. Safer to include Requirements and Skills, omit Qualifications. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section? But they gave both as examples; we can choose to include both if we have distinct content. We have distinct content: minimum vs preferred. So we can include both. Thus sections: - About the role (job summary) - Responsibilities (duties & responsibilities) - Requirements (minimum requirements & qualifications) - Qualifications (preferred experience & skills) - Schedule (availability to work 24/7, all shifts, etc.) Maybe also Job Conditions? But we have Schedule covering shift availability; other job conditions like ability to commute, read/comprehend English, age 18, etc. Those are also substantive. Could we put them under Schedule? Not exactly. Could we create a section "Job Conditions"? Not in allowed headings. Could we put them under Responsibilities? Not appropriate. Could we put them under About the role? Not ideal. Perhaps we can include them under Requirements? They are not requirements but conditions. Could we create a section "Schedule" and include all job conditions there? The heading Schedule is for schedule info; but we could also include other conditions under Schedule? Might be stretching. Alternatively, we could omit those generic conditions as they are somewhat boilerplate? But they are specific: ability to commute to Boston metro area, ability to read/comprehend English, be at least 18, ability to work all shifts, ability to uphold rights, etc. Some are generic but still part of posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. These conditions are not boilerplate; they are job conditions. So we should preserve them. We could create a section "Job Conditions" but not in allowed headings. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests these are examples, not an exhaustive list. So we could use other headings like "Job Conditions". But to be safe, we could use "Schedule" for shift availability and maybe add a separate section "Job Conditions" if allowed. Since they said e.g., I think we can use other headings. But to follow the spirit, maybe we should stick to those headings only. Then we need to fit job conditions somewhere. Could we put them under "About the role"? That section is for job summary; we could add a paragraph about conditions. But that might mix. Better to create a section "Job Conditions" as a heading; it's reasonable. The instruction didn't forbid other headings, just gave examples. So I'll include Job Conditions. Thus sections: - About the role - Responsibilities - Requirements - Qualifications - Job Conditions - Schedule (maybe overlapping with Job Conditions; but we can keep Schedule for shift availability and Job Conditions for other conditions). However there may be duplication: shift availability appears in both. We'll avoid duplication: put shift availability under Schedule, and other conditions under Job Conditions. Now we need to extract content. Let's parse the posting. Job Summary paragraph: "At the MBTA, we envision a thriving region enabled by a best-in-class transit system. Our mission is to serve the public by providing safe, reliable, and accessible transportation. MBTA’s core values are built around safety, service, equity, sustainability, culture, and accessibility, and each employee that works for the MBTA performs their roles based on our vision, mission, and values. This includes attendance, participation, and contribution in local safety committee meetings as needed. Job Summary The Capital Delivery group is seeking a Project Manager who will manage the development of MBTA Capital Delivery projects from project inception (planning) through the design phase (conceptual, preliminary, and final) and the construction phase (including project close-out), with full responsibility for quality and control of schedule and budget." We need to preserve all substantive information. The first sentences about vision, mission, values are part of the posting; we should keep them. Then the Job Summary sentence. We should not repeat the job title as heading. So we will not include "Project Manager" as heading. Now Duties & Responsibilities: a long list. We need to convert to

  • . Remove duplicated lines like "Provide monthly and/or quarterly updates of project schedules and budgets." appears twice. Also "Coordinate project tasks or activities with other Capital Programs personnel..." appears maybe once. We'll deduplicate. We need to preserve all substantive info, but we can remove exact duplicate sentences. Let's list duties: - Responsible for the project’s technical and financial directions and for ensuring external and internal customer satisfaction with project results. - Administer professional service, design and construction contracts, including involvement in design contract and amendment negotiations. - Establish initial project budgets, cost estimates, cash flow projections. - The Project Manager is the main contact between the MBTA and consultant or contractor. - Manage assigned Capital projects in accordance with all MBTA Manuals, policies and procedures as may be amended from time to time, or program-specific delivery protocols and procedures including but not limited to: Standard Operating Procedures (SOP) Manual; Project Controls Manual; Quality Assurance Manual; Construction Change Management Manual , Field Staff Manual; Contract Administration Policies and Procedures; MBTA Directives published on the MBTA web page or provided directly by the Authority, as well as FTA Circular 4220.1F Third Party Contracting. - Assist in the development of Capital Programs project scopes, budgets, and schedules as part of the capital planning process. - Assist in the procurement of consultants and contractors, as required. - Negotiate project assignments, task orders, amendments, change orders and use of contingency and make recommendations for approval for values above delegated authority. - Ensure that all work has been completed, and necessary approvals have been obtained prior to advertising projects for construction, including budget approval, environmental permits and approvals, real estate actions and approvals, force accounts (e.g., utility, traffic, railroad operator), other agency and municipal agreements (e.g., MOU's, MOA's, Interagency Agreements) and other third-party agreements. - Provide monthly and/or quarterly updates of project schedules and budgets. - Monitor project schedules and budgets to ensure financial and schedule milestones are met. - Review, analyze and approve monthly payment and schedule submissions from consultants and contractors. - Coordinate and participate in Project Design Group meetings, value engineering sessions, constructability reviews and risk workshops, as required. - Coordinate project tasks or activities with other Capital Programs personnel, including contract administration, field staff and other project coordinators, as required. - Coordinate project tasks with other Departments, including but not limited to Capital Program Support Department, Finance, Engineering and Maintenance and Railroad Operations, as required. - Coordinate project activities with outside agencies, abutters, utility companies, community groups and other third parties affected by the project, as required. - Manage the construction project process from advertisement to contract closeout to ensure the project is completed on time and within budget. - Resolve any conflicts that may occur throughout the life of the project. - Manage on-call and/or emergency repair contracts. - Proactively identifying and resolving potential field issues. - Analyze all contract proposals or bids and provide recommendations for senior management approval. -