Racial Equity Committee 2023 Work Plan Summary

Racial Equity Committee 2023 Work Plan Summary
Slide Note
Embed
Share

Draft work plan for the Racial Equity Committee focused on continuing recommendations and goals for 2023, emphasizing data analysis, collaboration with HUD, training initiatives, and staff diversity. The plan highlights ongoing efforts to incorporate racial equity tools, analyze intersectionality data, provide input to HUD on race and ethnicity data processes, advocate for broader homelessness definitions, and identify key performance measures.

  • Racial equity
  • Work plan
  • Data analysis
  • Collaboration
  • Training

Uploaded on Mar 16, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Document ID ET.IDV.05.00.SMT.00005 Author: Alessandro Variola Document type Status Verified: Alessandro Variola Validated: Alessandro Variola ET Symposium Slides Approved Configuration Alessandro Variola, INFN sezione Roma1 ET XIII Symposium Cagliari, T Hotel, 10/05/2023 .

  2. Changing. 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 2

  3. At present PBS CDR We started the process concerning the functional layouts We have, as priority, to provide the civil infrastructure TDR In this phase it is crucial that all the stakeholders share a unique coherent scenario, to allow everybody work assuming the same assumptions, constraints, parameters . This needs a BASELINE configuration 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 3

  4. Configuration - In SE the configuration is defined as a snapshot of the project, in ALL its phases. In the preliminary phase it is so important to freeze a baseline asdesigned configuration to have a well-defined reference. - For this reason it is a f(t)! - It is represented by a set of characteristics and functional relationships that DEFINE a final deliverable. - In this framework the configuration assures the ACCURACY and CONSISTENCY of our deliverable knowledge, during the project lifecycle - It is therefore mandatory that the configuration assures that, in the lifecycle, changes are managed by processes that guarantee their individuation, analysis, proposal, approval, integration and record for their traceability as an f(t) 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 4

  5. How to build the configuration The configuration is defined by the CONFIGURATION ITEMS (CI) These are not pre defined objects or categories but are project-related characteristics (no golden rule to define them!) Parameters tables, requirements, functional layouts, physical layouts, drawings, specifications .all these provide a description of the project, of its systems or elements. All of them must be TRACEABLE Modification has to be managed 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 5

  6. CI can be very different! They need only to be well defined Hardware/Devices Software/Applications Communications/Networks Integration and functional layouts Databases Services Risks Documentation People (Staff, vendors, buyers and contractors) THE QUESTION IS HOW WE WANT TO DEFINE THE CONFIGURATION (WHAT ARE THE NEEDED CI) TO MANAGE THE PROJECT & THE CONFIGURATION CHANGES 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 6

  7. Goal: configuration management triangle Takes into account the correspondence between what we have in our mind (requirements), what is illustrated in the documentation (as design, as built) and what exist in the reality. 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 7

  8. The CM-SW tools domains 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 8

  9. What configuration for ET? To be defined As far as the PO is concerned, three main actors: 1) Configuration Manager Christian Olivetto 2) Quality Manager - Luca Latronico 3) Technical Coordinator Alessio Rocchi 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 9

  10. What we can do now? To define a change process we need to define a baseline Not ready to specify the full configuration framework We can start working on the main parameters of the PBS systems and elements (the ones already existing in the CDR has to be identified) For each PBS unit we can assess a table of parameters AT LEAST : - Functional parameter: p.ex -> for a pump is the pumping speed (or other). Not the power supply power - Integration parameter: all parameters linked to the integration (beams diameter, FP cavity lengths, needed pressure, ventilation etc etc ). We have this priority. These can be defined for all the defined elements and for the systems-subsystems. Where not existing the element need to be further developed. At the end we will have a parameter oriented- as designed configuration. Associated to the layouts it can be seen as a first (important) step towards the configuration definition TEMPLATES WILL BE PROVIDED 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 10

  11. Processes - In theory the CDR should represent a perfect basis for the CI definition (a representation of it..) - Unfortunately there are still some unconsistencies in the parameters and layouts definition. To be clarified towards a baseline - So the reference document for the parameters table has to be the CDR. When conflicts arise the unit responsible shall be responsible of a proposal. He will be responsible also to propose values for parameters that are missing. - A solid approval process flowchart shall be provided, to get the final approved result 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 11

  12. Start PBS unit identification PBS unit CDR description Verification Validation Table Analysis. Definition of the CI parameters table for this unit CI Table Integration in the as designconfiguration 0.1 Association with the PBS End 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 12

  13. Methodology We worked well with the WG configuration Starting from the PBS we can defined responsible and PARAMETERS CI Fill tables (always waiting for databases) Link layouts (when possible and available) At the end a parameters based configuration baseline will be available But this time we need also to define a shared, coherent and solid process for the baseline approval 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 13

  14. To be done and discussed Elements parameters ID Responsibles Templates Tables PBS links Parameters verification and approval flow Baseline approval flow 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 14

  15. Simple template can be(to trigger suggestions) Where applicable INTEGRATION PARAMETER PBS UNIT NAME PBS ID FUNCTIONAL PARAMETERS Parameter 1Dimensions 2Dimensions 3Dimensions 4Dimensions 5Power 6Water 7Cryo 8Gas 9 .. 10 Value Units Description Parameter Value Units Description 1 2 3 4 5 6 7 8 9 10 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 15

  16. Discussion 16/03/2025 Alessandro Variola, INFN Roma1, ET XIII Symposium 16

Related


More Related Content