Solutions Architect - Scheduling

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, job title is not to be repeated as heading. We need to include sections: About the role (purpose of the job), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. From posting: PURPOSE OF THE JOB: description about role. That's "About the role". So we can put

About the role

then

with that text. Then "Job Responsibilities" heading: we have a long list of responsibilities. We'll put

Responsibilities

then

• each bullet. Then "Job Requirements" includes MINIMUM QUALIFICATIONS and Experience, Knowledge & Abilities. We need to separate sections: Requirements (maybe minimum qualifications) and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We have "MINIMUM QUALIFICATIONS:" list: Bachelor's degree, 7 years experience, 3 years scheduling tech, SAP S4/ECC experience, etc. That's qualifications. Then "Experience, Knowledge & Abilities" list: many items like experience in database design, basic knowledge of SAP modules, ability to partner, etc. That could be Skills or Requirements. The instruction includes both Requirements and Qualifications sections. We could put MINIMUM QUALIFICATIONS under Qualifications, and Experience, Knowledge & Abilities under Requirements (or Skills). But we need to decide. Better: Qualifications = formal qualifications (degree, years experience). Requirements = specific experience/knowledge/abilities. Skills = maybe abilities like communication, partnering, etc. However the list includes many abilities. We could create sections: Qualifications (MINIMUM QUALIFICATIONS), Requirements (Experience, Knowledge & Abilities), Skills (maybe communication, partnering, etc). But we need to avoid duplication. Let's extract each bullet. MINIMUM QUALIFICATIONS: - Bachelor’s degree in computer science, information systems, or information technology; equivalent work experience may be considered in lieu of degree. - Minimum of 7 years of experience within Information Technology industry - Minimum of 3 years of experience with scheduling technologies - Prior SAP S4/ECC.6.0 and greater deployment experience in all phases of the SAP project methodology - Prior experience integrating 3rd party applications into SAP S4 or similar platform - Prior experience in SAP production scheduling tools (PP, PP-DS, MRP) Experience, Knowledge & Abilities: - Experience in database design and use - Basic knowledge/understanding of SAP master data and modules (Materials Management-MM, Production Planning-PP) - Ability to partner effectively with team members, business partners, and 3rd party partners - Ability to identify and prioritize tasks to meet project milestones - Ability to adapt and show flexibility as priorities change - Designed all or key modules of a custom business application, including technical design, data relationships, UIs, and system interfaces - Experience working in a highly matrixed structure across functional, business, geographic and cultural boundaries - Strong written and oral communication skills to convey relevant information clearly with confidence; understanding others through active listening; successfully sets and manages expectations - Demonstrated ability to communicate and translate business requirements and technical solutions cross-functionally - Organized and executed IT process development /solution design review with external suppliers - Being innovative – develops and introduces new ideas and approaches to others - Demonstrating curiosity and drive to understand how and why things operate, finds root causes through analysis and questioning - Collaborate and challenge users in support of global solutions. - Willingness to travel periodically as needed in support of larger projects and optimizations (10-20%) Now Benefits, Pay, Schedule: Not mentioned in posting. So we should NOT include those sections. Thus we will have sections: About the role, Responsibilities, Requirements (maybe Experience, Knowledge & Abilities), Qualifications (MINIMUM QUALIFICATIONS), Skills (maybe communication etc). But we need to avoid thin sections. Could combine Requirements and Skills? But we need to follow instruction: use headings for those categories only if there is real specific content. We have content for Requirements (Experience, Knowledge & Abilities) and Qualifications (MINIMUM QUALIFICATIONS). Skills maybe subset of those; but we could also put communication abilities under Skills. However we already have many ability items; we could treat them as Skills. But then Requirements would be empty. Better to treat MINIMUM QUALIFICATIONS as Qualifications, and Experience, Knowledge & Abilities as Requirements (or Skills). Since we have both categories, we can put Requirements = Experience, Knowledge & Abilities (includes abilities). Skills maybe not needed separately. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements (combining experience/knowledge/abilities), Qualifications (education/experience). That's four sections. That seems good. Thus we will not have Skills section separately. Now we need to strip boilerplate: "About Owens Corning" description, equal opportunity employer, etc. Remove that. Also remove "Reports to : GIS Enterprise Manufacturing Team Leader Span of control : Indirect Contributor; indirect leadership of external partners / project resources as needed" - that's metadata, we can fold into a short

  maybe under About the role? Or we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short paragraph under About the role maybe after purpose. Or we could drop it. Safer to include a short

  with that info. Thus About the role section: purpose paragraph plus maybe a short metadata paragraph. Now Responsibilities: we need to break the long paragraph into bullet list items. The responsibilities are described in paragraphs with semicolons. We need to extract each distinct responsibility. Let's parse responsibilities section: "Knowing Our Businesses and Their Strategies Build relationships within the organization, cross-functionally, and with key stakeholders; ensure effective contact to remain aligned with functional objectives Understand the strategic direction of the company’s businesses and execute functional strategies to support and enhance business results; be knowledgeable of the project work that supports this direction and implications to the business. Leverage the values and practices that align customer needs to create enterprise customer solutions Generates Diverse Ideas to Solve Customer Problems; Actively seeks and appreciates diverse perspectives. Bring together multiple information sources and critical thinking to solve complex problems Executing Strategy Collaborate with Domain Architects, Product leader, peers, and other IS leaders in the development and ongoing sustainment of the Scheduling IT Roadmap for the Owens Corning technology environment. Work with process leaders, and project teams to identify and define integration opportunities for the appropriate technologies. Ensure technology that is being delivered is contemporary and aligned with the IT Roadmap. Ensure the performance, support, sustainability, and life cycle management of scheduling solutions are engineered in the design stage. Design and drive the implementation of seamless and efficient scheduling platforms. Leads execution technology assessments & POCs within scheduling function. Manage external providers of development capacity as needed. Collaborate with others to address the feasibility of technology solutions. Identify technical and implementation risks associated with a technology solution. Consult with project planners to develop statements of work for proposed solutions including assumption-based estimates, resources, integration points, and risks for scheduling solutions. Competitively Drives Results: Prioritize work assignments in alignment with team portfolio. IT Project Control & Reporting: Ability to monitor the vital signs of project to manage progress and delivery schedule Project Management: Ability to identify, own, and prioritize tasks to meet project milestones. Evaluate Effectiveness of Products & Initiatives: Improve efficiency and cost-effectiveness with participating stakeholders. Analytics Integration: Integrate analytics to optimize cross-business collaboration and competitive positioning. Influencing in the Function Aligns and updates OC Enterprise Reference Model for business processes within the domain. Maintain the functional specification architecture documentation including the OC Enterprise Reference Model for all scheduling process areas. Drive continuous improvement initiatives within the department and cross-functionally; encourage others to identify areas of waste (process, time, etc.); ideate and execute action plans to create productivity. Summarize complex information so that it is easy to interpret and understand. Identify opportunities to improve the effectiveness, value, and perception of the organization Inventive Flexibility - seeks out ways to leverage investments by integrating new requirements into existing solutions. Developing Talent Provide impactful peer-to-peer leadership to others on the team Assist in building the talent pipeline, mentoring, and developing other team members. Invest in personal growth and development, clearly focused on self-learning. Develops and introduces new ideas and approaches to others Driven to understand how and why things operate, finds root causes through analysis and questioning" We need to turn each bullet into

• . Many are sentences; we can keep them as is. We should avoid duplication. We'll create list items for each distinct responsibility. Let's enumerate: 1. Build relationships within the organization, cross-functionally, and with key stakeholders; ensure effective contact to remain aligned with functional objectives 2. Understand the strategic direction of the company’s businesses and execute functional strategies to support and enhance business results; be knowledgeable of the project work that supports this direction and implications to the business. 3. Leverage the values and practices that align customer needs to create enterprise customer solutions 4. Generates Diverse Ideas to Solve Customer Problems; Actively seeks and appreciates diverse perspectives. Bring together multiple information sources and critical thinking to solve complex problems 5. Collaborate with Domain Architects, Product leader, peers, and other IS leaders in the development and ongoing sustainment of the Scheduling IT Roadmap for the Owens Corning technology environment. 6. Work with process leaders, and project teams to identify and define integration opportunities for the appropriate technologies. 7. Ensure technology that is being delivered is contemporary and aligned with the IT Roadmap. 8. Ensure the performance, support, sustainability, and life cycle management of scheduling solutions are engineered in the design stage. 9. Design and drive the implementation of seamless and efficient scheduling platforms. 10. Leads execution technology assessments & POCs within scheduling function. 11. Manage external providers of development capacity as needed. 12. Collaborate with others to address the feasibility of technology solutions. 13. Identify technical and implementation risks associated with a technology solution. 14. Consult with project planners to develop statements of work for proposed solutions including assumption-based estimates, resources, integration points, and risks for scheduling solutions. 15. Prioritize work assignments in alignment with team portfolio. 16. Ability to monitor the vital signs of project to manage progress and delivery schedule 17. Ability to identify, own, and prioritize tasks to meet project milestones. 18. Improve efficiency and cost-effectiveness with participating stakeholders. 19. Integrate analytics to optimize cross-business collaboration and competitive positioning. 20. Aligns and updates OC Enterprise Reference Model for business processes within the domain. 21. Maintain the functional specification architecture documentation including the OC Enterprise Reference Model for all scheduling process areas. 22. Drive continuous improvement initiatives within the department and cross-functionally; encourage others to identify areas of waste (process, time, etc.); ideate and execute action plans to create productivity. 23. Summarize complex information so that it is easy to interpret and understand. 24. Identify opportunities to improve the effectiveness, value, and perception of the organization 25. Seeks out ways to leverage investments by integrating new requirements into existing solutions. 26. Provide impactful peer-to-peer leadership to others on the team 27. Assist in building the talent pipeline, mentoring, and developing other team members. 28. Invest in personal growth and development, clearly focused on self-learning. 29. Develops and introduces new ideas and approaches to others 30. Driven to understand how and