Public Safety Master Scheduler
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Job title appears: "IT PROJECT SPECIALIST - 95710". Not to be used as heading. We must not put Job ID / requisition numbers as headings; we can fold minor metadata into short
or drop it. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real specific content. Let's parse content: - Intro about OTI: description of mission, benefits, chance to work on projects, cutting-edge tech, etc. This could be "About the role" or maybe "About the organization". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put the OTI description under "About the role". That seems appropriate. - Responsibilities: a long list of duties for Public Safety IT Master Scheduler. Those are responsibilities. - Requirements: Minimum Qualifications (education/experience). That's qualifications. - Skills: Preferred Skills list. - Benefits: The posting mentions "At OTI, we offer great benefits". No specifics given. It says "great benefits" but no detail. According to rule: never create Benefits section unless posting actually states them. It states "we offer great benefits" but no specifics. Is that enough? It says "great benefits" but not enumerated. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not details. However, we should include a Benefits section only if there is real specific content. "great benefits" is vague; maybe we should not include Benefits section because no specific benefits listed. The instruction: "Prefer a few substantive sections over many thin ones." So likely omit Benefits. - Pay: Not mentioned. So omit. - Schedule: The posting includes "HOURS/SHIFT Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be required to work various shifts such as weekends and/or nights/evenings." That's schedule info. So we can include Schedule section. Also there is "WORK LOCATION Brooklyn, NY". That's location; could be part of About the role or maybe separate but not a prescribed heading. We could include location in About the role paragraph. Also there is "TO APPLY" etc which are application instructions; we must remove. Also there is "Additional Information" about EEO etc; remove. Also there is "Residency Requirement New York City Residency is not required for this position". That's a detail; could be part of Requirements or Qualifications? It's not a qualification but a requirement. Could be included in Requirements section. We must preserve all substantive information; we should not drop location, shift info, residency requirement. We need to format using
headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes into which section.
Let's outline:
About the role: include OTI mission description, benefits statement, location, maybe residency? Actually residency is a requirement, not about role. We'll put location in About the role.
Responsibilities: the long list of duties.
Requirements: maybe include Minimum Qualifications and Residency Requirement? Actually Minimum Qualifications are qualifications. The heading "Requirements" could be used for eligibility like residency, shift availability, etc. But we have also "Qualifications" heading. The instruction list includes both Requirements and Qualifications. We need to decide what goes where. Typically Requirements could be mandatory eligibility (e.g., residency, shift availability, etc.) and Qualifications could be education/experience. But we can also put education/experience under Qualifications. Let's follow: Requirements: shift availability (hours/shift), residency requirement, work location? Actually location is not a requirement but info. We'll put shift and residency under Requirements.
Qualifications: Minimum Qualifications (education/experience equivalents). Also maybe mention "specialization in a relevant technology, process, methodology and/or domain". That's part of qualifications.
Skills: Preferred Skills list.
Schedule: maybe we already put shift under Requirements; but we have a Schedule heading. The shift info is schedule. Could put under Schedule. But we already have shift info; we could put under Schedule. The requirement about shift could be considered schedule. Let's put schedule under Schedule heading. Then Requirements could contain residency requirement only? But we also might include "Work location" maybe not needed. Let's think.
We have schedule info: "HOURS/SHIFT Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be required to work various shifts such as weekends and/or nights/evenings." That's schedule.
We have residency requirement: "New York City Residency is not required for this position."
We have work location: "Brooklyn, NY".
We could include location in About the role paragraph.
Thus:
About the role: OTI description, benefits statement, location.
Responsibilities: list of duties.
Requirements: residency requirement (maybe also mention that candidate must be able to work various shifts? but that's schedule). We'll keep just residency.
Qualifications: Minimum Qualifications (the four options).
Skills: Preferred Skills list.
Schedule: shift info.
We must not create Pay/Benefits sections unless specific content. Benefits only said "great benefits" no detail; we omit.
Now we need to ensure we don't include boilerplate like EEO, application instructions, etc.
We need to preserve all substantive information: The OTI description includes: "The Office of Technology and Innovation (OTI) leverages technology to drive opportunity, improve public safety, and help government run better across New York City. From delivering affordable broadband to protecting against cybersecurity threats and building digital government services, OTI is at the forefront of how the city delivers for New Yorkers in the 21st century. Watch our welcome video to see our work in action, follow us on social media NYCOfficeofTech, and visit www.oti.nyc.gov to learn more. At OTI, we offer great benefits, and the chance to work on projects that have a meaningful impact on millions of people. You'll have the opportunity to work with cutting-edge technology and collaborate with other passionate professionals who share your drive and commitment to making a difference through technology."
We should keep that but maybe remove the "Watch our welcome video..." and social media links? Those are not boilerplate but could be considered navigation? They are promotional but still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The video/social media links are not those; they are part of OTI description. We can keep them.
But we might consider that they are not essential job info; but they are part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them.
Thus About the role paragraph will include all that.
Now Responsibilities: we need to convert the long paragraph into a list of duties. The text after "Responsibilities will include:" then a series of clauses separated by semicolons. We need to make each clause a
- . Ensure we preserve all details.
Let's extract each duty:
1. Organize, implement and maintain the scheduling management system supporting identified projects and their plans;
2. Assist setting up tasks and sub tasks to ensure satisfactory realization of project requirements as scheduled;
3. Log project time-lines and maintain a master, integrated schedule of tasks and their status;
4. Roll up individual project plans and dependencies into an Integrated Master Schedule (IMS) and provide summary level schedule visuals for coordination and reporting purposes;
5. Interact with project staff to schedule work, coordinate assignments and identification of variances from original/baseline plans;
6. Evaluate project schedule progress and performance and identify developing problem areas;
7. Analyze critical path and constraints to determine effect of changes to schedule and recommend work-around;
8. Develop and update weekly short interval/upcoming milestone schedule;
9. Assist project teams to develop and maintain periodic status reports to keep management informed on project progress regarding schedule;
10. Conduct what-if analyses to determine alternative courses of action or recovery on slipped schedules;
11. Define and implement the change control management processes for identifying, organizing, assessing, and executing updates to project scope and any related deliverables or solution components, ensure that projects adhere to the change control management processes and that change control is properly governed;
12. Work in conjunction with the Program Director and Project Management team to manage change control and ensure consistency and alignment of change control management across the program;
13. Ensure that the risk associated with each change is well understood by ensuring that the Change Board has the necessary functional and business representation plus comprehensive impact information from the appropriate project teams;
14. Ensure that changes are performed in an efficient and effective manner with minimal disruption, and are recorded, evaluated, authorized, prioritized, planned, communicated, tested, implemented, documented and reviewed in a consistent and controlled manner;
15. Perform special projects and initiatives as assigned.
We need to keep the semicolons removed; each
- ends with a period.
Now Requirements: residency requirement: "New York City Residency is not required for this position." Could be a
.
Also maybe we need to include that candidate must be able to work various shifts? That's schedule.
Thus Requirements section: just that line.
Qualifications: Minimum Qualifications: The text includes four options separated by "or". We need to preserve all detail. Could present as a
- each option.
Let's extract:
- A baccalaureate degree from an accredited college in computer science, engineering, human computer interaction, interactive media, digital and graphics design, data visualization, communication or a related field, and four years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- An associate degree from an accredited college in computer science, engineering, human computer interaction, interactive media, digital and graphics design, data visualization, communication or a related field, and six years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- A baccalaureate degree from an accredited college, and eight years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- Education and/or experience which is equivalent to "1", "2", or "3" above.
We need to keep the quotes? The original includes quotes around "1", "2", or "3". We'll keep as is.
Now Skills: Preferred Skills list: bullet points preceded by "-". We'll convert to
- .
List:
- IT project planning/management or scheduling experience
- Strong interpersonal, collaboration and communication skills
- Strong negotiation skills with the ability to resolve conflicts and problems and follow through to completion
- Pro-active with high levels of energy, tenacity and enthusiasm to deliver results
- Exceptional focus on quality and strong attention to detail
- Competent in the use of Microsoft PowerPoint, Word and Excel
- Ability to collaborate with team members, multi-task, and adapt to change
- Excellent communication skills are imperative
- Experience in Microsoft Project is strongly preferred.
Note there is duplication: "Strong interpersonal, collaboration and communication skills" and later "Excellent communication skills are imperative". Both are separate bullet points; we keep both.
Now Schedule: The shift info: "HOURS/SHIFT Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be
for prose. We need to decide which content goes into which section. Let's outline: About the role: include OTI mission description, benefits statement, location, maybe residency? Actually residency is a requirement, not about role. We'll put location in About the role. Responsibilities: the long list of duties. Requirements: maybe include Minimum Qualifications and Residency Requirement? Actually Minimum Qualifications are qualifications. The heading "Requirements" could be used for eligibility like residency, shift availability, etc. But we have also "Qualifications" heading. The instruction list includes both Requirements and Qualifications. We need to decide what goes where. Typically Requirements could be mandatory eligibility (e.g., residency, shift availability, etc.) and Qualifications could be education/experience. But we can also put education/experience under Qualifications. Let's follow: Requirements: shift availability (hours/shift), residency requirement, work location? Actually location is not a requirement but info. We'll put shift and residency under Requirements. Qualifications: Minimum Qualifications (education/experience equivalents). Also maybe mention "specialization in a relevant technology, process, methodology and/or domain". That's part of qualifications. Skills: Preferred Skills list. Schedule: maybe we already put shift under Requirements; but we have a Schedule heading. The shift info is schedule. Could put under Schedule. But we already have shift info; we could put under Schedule. The requirement about shift could be considered schedule. Let's put schedule under Schedule heading. Then Requirements could contain residency requirement only? But we also might include "Work location" maybe not needed. Let's think. We have schedule info: "HOURS/SHIFT Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be required to work various shifts such as weekends and/or nights/evenings." That's schedule. We have residency requirement: "New York City Residency is not required for this position." We have work location: "Brooklyn, NY". We could include location in About the role paragraph. Thus: About the role: OTI description, benefits statement, location. Responsibilities: list of duties. Requirements: residency requirement (maybe also mention that candidate must be able to work various shifts? but that's schedule). We'll keep just residency. Qualifications: Minimum Qualifications (the four options). Skills: Preferred Skills list. Schedule: shift info. We must not create Pay/Benefits sections unless specific content. Benefits only said "great benefits" no detail; we omit. Now we need to ensure we don't include boilerplate like EEO, application instructions, etc. We need to preserve all substantive information: The OTI description includes: "The Office of Technology and Innovation (OTI) leverages technology to drive opportunity, improve public safety, and help government run better across New York City. From delivering affordable broadband to protecting against cybersecurity threats and building digital government services, OTI is at the forefront of how the city delivers for New Yorkers in the 21st century. Watch our welcome video to see our work in action, follow us on social media NYCOfficeofTech, and visit www.oti.nyc.gov to learn more. At OTI, we offer great benefits, and the chance to work on projects that have a meaningful impact on millions of people. You'll have the opportunity to work with cutting-edge technology and collaborate with other passionate professionals who share your drive and commitment to making a difference through technology." We should keep that but maybe remove the "Watch our welcome video..." and social media links? Those are not boilerplate but could be considered navigation? They are promotional but still substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The video/social media links are not those; they are part of OTI description. We can keep them. But we might consider that they are not essential job info; but they are part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them. Thus About the role paragraph will include all that. Now Responsibilities: we need to convert the long paragraph into a list of duties. The text after "Responsibilities will include:" then a series of clauses separated by semicolons. We need to make each clause a
. Also maybe we need to include that candidate must be able to work various shifts? That's schedule. Thus Requirements section: just that line. Qualifications: Minimum Qualifications: The text includes four options separated by "or". We need to preserve all detail. Could present as a
- each option.
Let's extract:
- A baccalaureate degree from an accredited college in computer science, engineering, human computer interaction, interactive media, digital and graphics design, data visualization, communication or a related field, and four years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- An associate degree from an accredited college in computer science, engineering, human computer interaction, interactive media, digital and graphics design, data visualization, communication or a related field, and six years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- A baccalaureate degree from an accredited college, and eight years of satisfactory full-time experience related to the area(s) required by the particular position and a specialization in a relevant technology, process, methodology and/or domain;
- Education and/or experience which is equivalent to "1", "2", or "3" above.
We need to keep the quotes? The original includes quotes around "1", "2", or "3". We'll keep as is.
Now Skills: Preferred Skills list: bullet points preceded by "-". We'll convert to
- . List: - IT project planning/management or scheduling experience - Strong interpersonal, collaboration and communication skills - Strong negotiation skills with the ability to resolve conflicts and problems and follow through to completion - Pro-active with high levels of energy, tenacity and enthusiasm to deliver results - Exceptional focus on quality and strong attention to detail - Competent in the use of Microsoft PowerPoint, Word and Excel - Ability to collaborate with team members, multi-task, and adapt to change - Excellent communication skills are imperative - Experience in Microsoft Project is strongly preferred. Note there is duplication: "Strong interpersonal, collaboration and communication skills" and later "Excellent communication skills are imperative". Both are separate bullet points; we keep both. Now Schedule: The shift info: "HOURS/SHIFT Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be