This document discusses how NASA employed Web 2.0 collaboration tools internally and externally. It provides examples of the DASHlink website, which allows scientists and engineers to disseminate research and collaborate using discussion forums, tagging, and associated content. It also discusses the Trac system for internal collaboration on website development. The document outlines challenges in using these tools at NASA like cultural resistance and policy barriers, and how solutions like community moderation policies and an emphasis on content creation helped overcome these challenges.
The Impact of Web 2.0 on Library WebsitesRachel Vacek
The document discusses how Web 2.0 technologies can enhance library websites. It defines key concepts of Web 2.0 like collaboration, sharing, and user participation. It provides examples of how technologies like wikis, blogs, RSS feeds, social bookmarking, tagging, photo sharing, and video sharing can be used to improve content and services on library websites. The document concludes that Library 2.0 websites engage users by allowing them to create and interact with content in ways that break down barriers and integrate the library more fully into users' lives.
This document provides an introduction to research data management. It discusses what research data management is, why it is important, and best practices. Key points include:
- Research data management involves organizing, storing, and preserving research data throughout its lifecycle. It ensures data is accessible, usable, and adds value.
- It is important due to convergence in research policy around open data and data sharing. Funders now require data management plans and data to be preserved and shared.
- Benefits include securing funding, ensuring research integrity, enabling verification and reuse of data, and increased collaboration and visibility of research outputs. Risks of not properly managing data include loss of data and funding.
- Good practice involves
This document summarizes a presentation given by Katrina Pritchard and Rebecca Whiting on their e-research project. It discusses what e-research is, outlines their approach which included collecting data through alerts and tracking online conversations, and discusses some of the practical and ethical challenges they faced such as managing large amounts of digitally generated data and blurred boundaries between primary and secondary data. Key emergent ideas from their project included tracking online conversations and re-thinking relationships with research participants in an online context.
P T Hacker: Using Technology to Make You a Better PTEric Robertson
Eric Robertson and Tim Noteboom presented on using technology to improve physical therapy practice. Their presentation highlighted [1] barriers to evidence-based practice like a lack of time, [2] web tools that can help with collaboration, learning and productivity like blogs, wikis and Google tools, and [3] case studies of innovative implementations including a student resource wiki and a clinic using social media for communication. The goal was to explore how physical therapists can integrate new technologies into practice to overcome challenges and work more efficiently.
The document discusses how NASA master practitioners learn how to do their jobs. It describes a session where 70 NASA masters were asked how they learn. Their responses were organized into mind maps showing that they learn through experience, mistakes, mentors, teamwork, education and training, conversations, personal networks, and continuing education. The document also presents a learning continuum that shows the importance of different learning methods increases over the course of a career. It concludes by requesting information from others on how they and their teams learn.
This document provides an overview of NASA and JPL's project lifecycle and design practices for flight projects. It describes the phases and key decision points in the project lifecycle. It also outlines JPL's design principles, flight project practices, and processes for managing technical, schedule, and budget margins. Additionally, it introduces the Certification of Flight Readiness process to document adherence to development practices and assess residual risk for mission success.
The document discusses improving project management using formal modeling and architectures. It covers applying enterprise architecture and modeling concepts to project management. Some key topics include modeling perspectives like business, system, and technical modeling; modeling standards and languages like SysML; and using modeling to better organize project information and provide common understanding of objectives, roles, and constraints.
The document discusses the International Space Station Utilization Team at NASA's Kennedy Space Center. The team tests equipment and hardware that will be used to perform experiments on the ISS. Budget cuts and reductions in crew size have posed challenges to project management and keeping expertise. The team is high performing because issues are transparent, customers recognize their quality work, and skills are transferred to new members. Building a high performing team requires recruiting motivated individuals, clearly defining roles, proper training, keeping members informed, celebrating success, and continuing performance evaluation.
The Impact of Web 2.0 on Library WebsitesRachel Vacek
The document discusses how Web 2.0 technologies can enhance library websites. It defines key concepts of Web 2.0 like collaboration, sharing, and user participation. It provides examples of how technologies like wikis, blogs, RSS feeds, social bookmarking, tagging, photo sharing, and video sharing can be used to improve content and services on library websites. The document concludes that Library 2.0 websites engage users by allowing them to create and interact with content in ways that break down barriers and integrate the library more fully into users' lives.
This document provides an introduction to research data management. It discusses what research data management is, why it is important, and best practices. Key points include:
- Research data management involves organizing, storing, and preserving research data throughout its lifecycle. It ensures data is accessible, usable, and adds value.
- It is important due to convergence in research policy around open data and data sharing. Funders now require data management plans and data to be preserved and shared.
- Benefits include securing funding, ensuring research integrity, enabling verification and reuse of data, and increased collaboration and visibility of research outputs. Risks of not properly managing data include loss of data and funding.
- Good practice involves
This document summarizes a presentation given by Katrina Pritchard and Rebecca Whiting on their e-research project. It discusses what e-research is, outlines their approach which included collecting data through alerts and tracking online conversations, and discusses some of the practical and ethical challenges they faced such as managing large amounts of digitally generated data and blurred boundaries between primary and secondary data. Key emergent ideas from their project included tracking online conversations and re-thinking relationships with research participants in an online context.
P T Hacker: Using Technology to Make You a Better PTEric Robertson
Eric Robertson and Tim Noteboom presented on using technology to improve physical therapy practice. Their presentation highlighted [1] barriers to evidence-based practice like a lack of time, [2] web tools that can help with collaboration, learning and productivity like blogs, wikis and Google tools, and [3] case studies of innovative implementations including a student resource wiki and a clinic using social media for communication. The goal was to explore how physical therapists can integrate new technologies into practice to overcome challenges and work more efficiently.
The document discusses how NASA master practitioners learn how to do their jobs. It describes a session where 70 NASA masters were asked how they learn. Their responses were organized into mind maps showing that they learn through experience, mistakes, mentors, teamwork, education and training, conversations, personal networks, and continuing education. The document also presents a learning continuum that shows the importance of different learning methods increases over the course of a career. It concludes by requesting information from others on how they and their teams learn.
This document provides an overview of NASA and JPL's project lifecycle and design practices for flight projects. It describes the phases and key decision points in the project lifecycle. It also outlines JPL's design principles, flight project practices, and processes for managing technical, schedule, and budget margins. Additionally, it introduces the Certification of Flight Readiness process to document adherence to development practices and assess residual risk for mission success.
The document discusses improving project management using formal modeling and architectures. It covers applying enterprise architecture and modeling concepts to project management. Some key topics include modeling perspectives like business, system, and technical modeling; modeling standards and languages like SysML; and using modeling to better organize project information and provide common understanding of objectives, roles, and constraints.
The document discusses the International Space Station Utilization Team at NASA's Kennedy Space Center. The team tests equipment and hardware that will be used to perform experiments on the ISS. Budget cuts and reductions in crew size have posed challenges to project management and keeping expertise. The team is high performing because issues are transparent, customers recognize their quality work, and skills are transferred to new members. Building a high performing team requires recruiting motivated individuals, clearly defining roles, proper training, keeping members informed, celebrating success, and continuing performance evaluation.
The document discusses NASA's Space Life Sciences Directorate's (SLSD) system for innovation which has two key components: 1) A human system risk management process that continuously evaluates human risks across operations and identifies research gaps, and 2) A strategic system to drive innovation through collaboration to optimize SLSD portfolios. It describes how changes in reports like from the Institute of Medicine and Columbia Accident Investigation Board led to developing this system, including creating a master list of 90 human risks and using evidence-based standards and deliverables to mitigate risks.
This document discusses challenges with software scheduling and provides recommendations to improve software schedule estimation and tracking. It notes that software schedules often slip despite experience and process improvements. Common causes of scheduling issues include poor estimates due to undefined requirements, changing requirements, or inexperience. The document recommends that software schedules align with system schedules and allow time for requirements, design, implementation, and testing cycles. It presents techniques like Evidence-Based Scheduling using past performance data to generate realistic schedules and functional progress metrics rather than lines of code to improve schedule tracking.
This document discusses NASA's policies and procedures for decommissioning and disposing of spacecraft at the end of missions. It outlines the governing policies at the national and NASA level that require planning for post-mission disposal to limit orbital debris and environmental risks. Key requirements include developing end-of-mission plans, passivating spacecraft by depleting energy sources, and either de-orbiting from orbit or moving to a storage orbit above 2,000 km. The document reviews the disposal guidelines and regulations regarding debris mitigation and risk management.
This document summarizes key insights from a presentation on viewing project management through the lens of complexity theory. It discusses how complexity theory originated in the study of natural systems and how its concepts like emergence and non-linearity are relevant to project management. It also notes that while general systems theory promised to connect different fields, project management, cybernetics, and systems thinking ultimately diverged. The document reviews different perspectives on categorizing project complexity and shares insights from interviews where project managers discussed experiencing uncertainty, renegotiating plans, and maintaining progress despite radical uncertainty.
The document discusses challenges faced by inventors and innovators in getting their ideas adopted. Some key points:
1) Innovators often face resistance from organizations wedded to the status quo, as change threatens existing structures and ways of doing things. Initiating change is difficult and risky.
2) Inventors do not always make good product champions, as they tend to be independent thinkers who do not easily fit into organizational hierarchies. Their temperaments are not always suited for commercialization efforts.
3) Cultural influences within companies and industries can inhibit innovation, as existing success breeds complacency and risk aversion. Breakthroughs are less likely to emerge from tightly controlled environments.
4) While
This document discusses contracts and requirements. It provides definitions of key contract terms from sources like Aristotle and the Bible. It outlines different types of contracts like firm-fixed-price, cost-plus-fixed-fee, and fixed-price incentive contracts. It discusses how to form contracts and get requirements. It also addresses historical questions for a source board process, working without a contract, and ways to get out of a contract while providing background and addressing damages. The document draws from a variety of sources to discuss contracts and contracting principles.
Risk management is a key program control function that requires an environment fostering open discussion of challenges. Prior programs provide lessons on effective practices like engaged leadership, clear communication across all levels, comprehensive training, well-defined processes, and usable risk management tools. These elements encourage accurate identification and handling of risks to contribute to mission success.
This document discusses NASA's efforts to develop an agency-wide earned value management (EVM) capability that complies with ANSI/EIA-748 guidelines. The objectives are to provide integrated EVM processes, tools, guidance and training across NASA and test the capability on two pilot projects. The approach involves managing the development as a project with formulation, implementation and operations phases. It will establish a steering committee and peer review board and test the capability through pilots on a Constellation Program project and a Science Mission Directorate project. The current state within NASA is that EVM is used on contracts but not for in-house work, and contracted and in-house EVM data are not integrated. Gaps need to be addressed
The document discusses the negative impacts of poor leadership, including $350 billion in lost productivity annually according to a Gallup poll. Poor leadership is also linked to increased health care costs and greater risk of heart disease. Effective leadership involves nurturing trust within the organization, asking for help, avoiding compromising values, reinforcing praise for progress, paying attention to informal leaders, embracing diversity, giving rather than demanding respect, admitting mistakes, focusing on solutions, and connecting people to information. Leaders should maintain perspective, use humor sparingly, and make others feel valued above all.
Enterprise architecture provides a holistic view of a program or project that allows stakeholders to understand how all elements are related and work together. This helps manage complexity and enables change by providing insight into both current and future states. While NASA programs are inherently complex with high risks, enterprise architecture can complement traditional program management approaches by defining people, processes, technology, controls, and strategies. The level of architecture needed depends on a program's size, but typically frameworks are used to capture and relate essential information about the enterprise in a standardized way.
The CoNNeCT project faced several major challenges that threatened its schedule. Requirements were not fully defined, which led to rework. Structural analysis found weak margins, requiring a redesign with more testing. A heritage gimbal design was not suitable and needed significant redesign to meet safety requirements, causing cost growth and schedule delays. Solutions included workshops to finalize requirements, structural testing and redesign, and co-developing a redesigned gimbal with added simulators to prevent schedule impacts. These issues are common on projects and understanding them can help others face similar problems.
The document discusses two concepts of operation (ConOps) related to product data and lifecycle management (PDLM) challenges for NASA projects:
1) An in-flight anomaly scenario where a critical component fails and the project needs specific product data within 4 hours to diagnose and address the issue to prevent mission loss. This scenario illustrates the need to plan for accessing fragmented product data from multiple sources created over a long development period.
2) The large volumes of documentation, CAD models, test data, and other product information created and used during design, development, testing and evaluation phases which can number in the hundreds of thousands of files and terabytes of data. Effective PDLM is needed to manage this "data deluge"
This document discusses integrating technical risk management with decision analysis. It notes that NASA currently manages risks individually without considering overall risk. The document proposes using decision analysis and probabilistic risk assessment to evaluate alternatives based on performance measures related to objectives like safety, cost and schedule. This would allow uncertainty to be considered and provide a more rigorous approach to risk-informed decision making.
The Hypersonic Technology Experiment (HyTEx) was a multi-center, multi-agency project that demonstrated hypersonic flight. It involved broad technical expertise from NASA centers including Ames, Goddard, Langley, and Marshall as well as the Air Force Research Lab. The project achieved success through its core values of mutual respect and trust between team members, leadership that focused on influence rather than management, and fostering relationships through face-to-face meetings and social events.
The document describes a project management toolkit developed by NASA Glenn Research Center to help with space flight projects. The toolkit provides a collection of standardized project planning and management tools accessible through a web portal. It aims to facilitate rigorous and compliant project proposal, planning, execution, and control according to NASA requirements and best practices. The development of the operational toolkit was driven by a strategic goal of delivering project management excellence for successful customer missions.
Dr. Debbie Augustin presented on teams and team development. She discussed Tuckman's stages of team development, which include forming, storming, norming, and performing. During the storming stage, teams experience competition, conflict over leadership, and strained relationships as members work through issues. Leaders should facilitate conflict, encourage participation, and reinforce commitment to help teams progress through this crucial stage.
The document discusses the NASA Johnson Space Center's use of model-based systems engineering (MBSE) to develop and manage requirements for space suits. It outlines their MBSE approach, which includes developing operational concepts, architectural models, and requirements models to define the technical baseline for space suits. The models help ensure traceability, support analysis, and allow impacts from changes to be efficiently identified.
The Constellation Space Transportation Planning Office (CSTP) was established in 2008 to prepare NASA's Constellation Program for the operations and sustaining phase of the Ares I and Orion spacecraft's lifecycle. The CSTP works closely with the Constellation Program to address operability considerations in design and establish the future Constellation Space Transportation Program to manage production, launch, and recovery operations for Ares I/Orion missions to the International Space Station.
The document discusses the benefits and challenges of interagency collaboration for NASA missions, noting that partnerships can improve capabilities, augment budgets, and foster innovation, but developing and sustaining partnerships can be challenging due to differences in agency cultures and competing resource demands. It provides examples of elements needed for successful partnerships, including clear shared goals, ongoing assessment of progress, and real investment and commitment from both partners.
This document provides an overview of implementing an Earned Value Management (EVM) system for the Constellation Program. It discusses the program overview, EVM implementation process, Integrated Baseline Reviews (IBRs), and the path forward. Key aspects covered include defining EVM requirements, establishing organizational roles and responsibilities, developing documentation and tools, conducting IBRs for major projects, and ongoing monitoring to ensure the EVM system provides useful performance data. The overall goal is to fully integrate EVM into the program's processes to facilitate cost and schedule monitoring and control.
RDAP13 Mark Parsons: The Research Data Alliance: Making Data WorkASIS&T
Mark Parsons, Rensselaer Polytechnic Institute
Mark A. Parsons and Francine Berman: "The Research Data Alliance: Making Data Work"
Panel: Global scientific data infrastructure
Research Data Access & Preservation Summit 2013
Baltimore, MD April 4, 2013 #rdap13
NASATalk is a Web 2.0 site where educators can come to share ideas, suggestions, success stories, and even frustrations about using NASA resources to enhance STEM teaching and learning.
The document discusses NASA's Space Life Sciences Directorate's (SLSD) system for innovation which has two key components: 1) A human system risk management process that continuously evaluates human risks across operations and identifies research gaps, and 2) A strategic system to drive innovation through collaboration to optimize SLSD portfolios. It describes how changes in reports like from the Institute of Medicine and Columbia Accident Investigation Board led to developing this system, including creating a master list of 90 human risks and using evidence-based standards and deliverables to mitigate risks.
This document discusses challenges with software scheduling and provides recommendations to improve software schedule estimation and tracking. It notes that software schedules often slip despite experience and process improvements. Common causes of scheduling issues include poor estimates due to undefined requirements, changing requirements, or inexperience. The document recommends that software schedules align with system schedules and allow time for requirements, design, implementation, and testing cycles. It presents techniques like Evidence-Based Scheduling using past performance data to generate realistic schedules and functional progress metrics rather than lines of code to improve schedule tracking.
This document discusses NASA's policies and procedures for decommissioning and disposing of spacecraft at the end of missions. It outlines the governing policies at the national and NASA level that require planning for post-mission disposal to limit orbital debris and environmental risks. Key requirements include developing end-of-mission plans, passivating spacecraft by depleting energy sources, and either de-orbiting from orbit or moving to a storage orbit above 2,000 km. The document reviews the disposal guidelines and regulations regarding debris mitigation and risk management.
This document summarizes key insights from a presentation on viewing project management through the lens of complexity theory. It discusses how complexity theory originated in the study of natural systems and how its concepts like emergence and non-linearity are relevant to project management. It also notes that while general systems theory promised to connect different fields, project management, cybernetics, and systems thinking ultimately diverged. The document reviews different perspectives on categorizing project complexity and shares insights from interviews where project managers discussed experiencing uncertainty, renegotiating plans, and maintaining progress despite radical uncertainty.
The document discusses challenges faced by inventors and innovators in getting their ideas adopted. Some key points:
1) Innovators often face resistance from organizations wedded to the status quo, as change threatens existing structures and ways of doing things. Initiating change is difficult and risky.
2) Inventors do not always make good product champions, as they tend to be independent thinkers who do not easily fit into organizational hierarchies. Their temperaments are not always suited for commercialization efforts.
3) Cultural influences within companies and industries can inhibit innovation, as existing success breeds complacency and risk aversion. Breakthroughs are less likely to emerge from tightly controlled environments.
4) While
This document discusses contracts and requirements. It provides definitions of key contract terms from sources like Aristotle and the Bible. It outlines different types of contracts like firm-fixed-price, cost-plus-fixed-fee, and fixed-price incentive contracts. It discusses how to form contracts and get requirements. It also addresses historical questions for a source board process, working without a contract, and ways to get out of a contract while providing background and addressing damages. The document draws from a variety of sources to discuss contracts and contracting principles.
Risk management is a key program control function that requires an environment fostering open discussion of challenges. Prior programs provide lessons on effective practices like engaged leadership, clear communication across all levels, comprehensive training, well-defined processes, and usable risk management tools. These elements encourage accurate identification and handling of risks to contribute to mission success.
This document discusses NASA's efforts to develop an agency-wide earned value management (EVM) capability that complies with ANSI/EIA-748 guidelines. The objectives are to provide integrated EVM processes, tools, guidance and training across NASA and test the capability on two pilot projects. The approach involves managing the development as a project with formulation, implementation and operations phases. It will establish a steering committee and peer review board and test the capability through pilots on a Constellation Program project and a Science Mission Directorate project. The current state within NASA is that EVM is used on contracts but not for in-house work, and contracted and in-house EVM data are not integrated. Gaps need to be addressed
The document discusses the negative impacts of poor leadership, including $350 billion in lost productivity annually according to a Gallup poll. Poor leadership is also linked to increased health care costs and greater risk of heart disease. Effective leadership involves nurturing trust within the organization, asking for help, avoiding compromising values, reinforcing praise for progress, paying attention to informal leaders, embracing diversity, giving rather than demanding respect, admitting mistakes, focusing on solutions, and connecting people to information. Leaders should maintain perspective, use humor sparingly, and make others feel valued above all.
Enterprise architecture provides a holistic view of a program or project that allows stakeholders to understand how all elements are related and work together. This helps manage complexity and enables change by providing insight into both current and future states. While NASA programs are inherently complex with high risks, enterprise architecture can complement traditional program management approaches by defining people, processes, technology, controls, and strategies. The level of architecture needed depends on a program's size, but typically frameworks are used to capture and relate essential information about the enterprise in a standardized way.
The CoNNeCT project faced several major challenges that threatened its schedule. Requirements were not fully defined, which led to rework. Structural analysis found weak margins, requiring a redesign with more testing. A heritage gimbal design was not suitable and needed significant redesign to meet safety requirements, causing cost growth and schedule delays. Solutions included workshops to finalize requirements, structural testing and redesign, and co-developing a redesigned gimbal with added simulators to prevent schedule impacts. These issues are common on projects and understanding them can help others face similar problems.
The document discusses two concepts of operation (ConOps) related to product data and lifecycle management (PDLM) challenges for NASA projects:
1) An in-flight anomaly scenario where a critical component fails and the project needs specific product data within 4 hours to diagnose and address the issue to prevent mission loss. This scenario illustrates the need to plan for accessing fragmented product data from multiple sources created over a long development period.
2) The large volumes of documentation, CAD models, test data, and other product information created and used during design, development, testing and evaluation phases which can number in the hundreds of thousands of files and terabytes of data. Effective PDLM is needed to manage this "data deluge"
This document discusses integrating technical risk management with decision analysis. It notes that NASA currently manages risks individually without considering overall risk. The document proposes using decision analysis and probabilistic risk assessment to evaluate alternatives based on performance measures related to objectives like safety, cost and schedule. This would allow uncertainty to be considered and provide a more rigorous approach to risk-informed decision making.
The Hypersonic Technology Experiment (HyTEx) was a multi-center, multi-agency project that demonstrated hypersonic flight. It involved broad technical expertise from NASA centers including Ames, Goddard, Langley, and Marshall as well as the Air Force Research Lab. The project achieved success through its core values of mutual respect and trust between team members, leadership that focused on influence rather than management, and fostering relationships through face-to-face meetings and social events.
The document describes a project management toolkit developed by NASA Glenn Research Center to help with space flight projects. The toolkit provides a collection of standardized project planning and management tools accessible through a web portal. It aims to facilitate rigorous and compliant project proposal, planning, execution, and control according to NASA requirements and best practices. The development of the operational toolkit was driven by a strategic goal of delivering project management excellence for successful customer missions.
Dr. Debbie Augustin presented on teams and team development. She discussed Tuckman's stages of team development, which include forming, storming, norming, and performing. During the storming stage, teams experience competition, conflict over leadership, and strained relationships as members work through issues. Leaders should facilitate conflict, encourage participation, and reinforce commitment to help teams progress through this crucial stage.
The document discusses the NASA Johnson Space Center's use of model-based systems engineering (MBSE) to develop and manage requirements for space suits. It outlines their MBSE approach, which includes developing operational concepts, architectural models, and requirements models to define the technical baseline for space suits. The models help ensure traceability, support analysis, and allow impacts from changes to be efficiently identified.
The Constellation Space Transportation Planning Office (CSTP) was established in 2008 to prepare NASA's Constellation Program for the operations and sustaining phase of the Ares I and Orion spacecraft's lifecycle. The CSTP works closely with the Constellation Program to address operability considerations in design and establish the future Constellation Space Transportation Program to manage production, launch, and recovery operations for Ares I/Orion missions to the International Space Station.
The document discusses the benefits and challenges of interagency collaboration for NASA missions, noting that partnerships can improve capabilities, augment budgets, and foster innovation, but developing and sustaining partnerships can be challenging due to differences in agency cultures and competing resource demands. It provides examples of elements needed for successful partnerships, including clear shared goals, ongoing assessment of progress, and real investment and commitment from both partners.
This document provides an overview of implementing an Earned Value Management (EVM) system for the Constellation Program. It discusses the program overview, EVM implementation process, Integrated Baseline Reviews (IBRs), and the path forward. Key aspects covered include defining EVM requirements, establishing organizational roles and responsibilities, developing documentation and tools, conducting IBRs for major projects, and ongoing monitoring to ensure the EVM system provides useful performance data. The overall goal is to fully integrate EVM into the program's processes to facilitate cost and schedule monitoring and control.
RDAP13 Mark Parsons: The Research Data Alliance: Making Data WorkASIS&T
Mark Parsons, Rensselaer Polytechnic Institute
Mark A. Parsons and Francine Berman: "The Research Data Alliance: Making Data Work"
Panel: Global scientific data infrastructure
Research Data Access & Preservation Summit 2013
Baltimore, MD April 4, 2013 #rdap13
NASATalk is a Web 2.0 site where educators can come to share ideas, suggestions, success stories, and even frustrations about using NASA resources to enhance STEM teaching and learning.
Research network engineering: Community kick-off meetingJisc
This document provides an agenda and overview for a kick-off meeting of the Research Network Engineering community. The meeting will include presentations on the Janet Network, lessons from shifting real data from CERN to Lancaster, and Jisc's network performance test tools. The broad goals of the community are to discuss and share best practices in research networking, learn from each other, and help Jisc support the community. Examples of potential activities include looking at applicability of existing tools to other communities, documenting Science DMZ implementations, and testing data transfer tools. Existing resources that can contribute include experience from science communities and material from previous Jisc events.
We'll take a satellite-eye view of hackathons and space apps globally and in Canada. What are they, what business problems and technical challenges can they solve, what is their history and how can the Canadian space industry leverage them to achieve downstream software excellence?
The presentation is about the project overview of the PlanetData Network of Excellence http://www.planet-data.eu/. This presentation was presented by PlanetData partner; Elena Simperl (Karlsruhe Institute of Technology) and Alice Carpentier (Semantic Technology Institute, University of Innsbruck) during the PlanetData project Kick-off Meeting on October 11, 2010 in Palma de Mallorca, Spain.
EarthCube Community Webinar held Tuesday, Dec. 9th at 11:00 PST/2:00 EST for a virtual kick-off of the new 'Demonstration Phase' of EarthCube, including statements from your Leadership Council members and an update from NSF Program Officer, Eva Zanzerkia.
Learning from past infrastructure to embrace friction and create the Research...Research Data Alliance
RDA provides a neutral space for researchers to develop standards and share data across disciplines through working groups and interest groups. It focuses on developing interoperability through deliverables like registries and identifiers. While it doesn't define architecture, it aims to foster connections and provide unity. RDA also takes a "glocal" approach, implementing standards locally while addressing global issues. Friction in collaboration is inevitable but necessary for progress, and RDA provides a place for discussions to work through differences.
Information Technology Infrastructure Committee (ITIC): Report to the NACLarry Smarr
This document summarizes the December 2013 report from the NASA Advisory Council's Information Technology Infrastructure Committee (ITIC). It discusses NASA's transition to a more agile, collaborative agency that brings together experts from multiple centers to solve problems. The report outlines NASA's vision for a "OneNASA" organization enabled by unified IT tools and infrastructure. It also notes that NASA has begun implementing improved IT governance and developing a framework to coordinate IT investments across centers and missions.
This document describes the Science Gateways Community Institute (SGCI), a new NSF-funded institute aimed at helping the scientific community more effectively build online gateways and resources for research. The SGCI will provide consulting services, training, developer support, opportunities for students and educators, and a forum for the gateway community to connect and exchange knowledge. The goal is for the SGCI to become a central resource for all aspects of building and supporting science gateways.
Streamlining Nonprofit Organizations: It's All About the CloudDebra Askanase
This presentation looks at what cloud computing is, reports on how nonprofit organizations are using the Cloud, factors for success, how to evaluate cloud technology solutions, and developing a tech plan. Includes two nonprofit case studies and a survey of cloud tools for enhancing organizational efficiencies.
Streamlining Nonprofit Organizations - It's all About the Cloud!Marc Baizman
You may have heard people talk about the latest advance in technology: “the cloud.” In this presentation, you
will learn what cloud computing is, how it’s changing our work, and how nonprofit organizations can take
advantage of cloud-based services (e.g. Salesforce, Google Docs, Dropbox) to enhance their operations in all parts
of their organizations to become more efficient with their limited resources and time.
There are case studies of nonprofit organizations that are using these tools every day. We will offer a survey of cloud-based
tools that organizations can use within their own organizations in the areas of cross-organizational management,
program management, human resources, marketing and fundraising. At the end of the presentation, you will
have a list of tools and resources for further exploration, and strategies about how to incorporate these
tools into your day-to-day work.
What is eScience, and where does it go from here?Daniel S. Katz
eScience has evolved from focusing on global scientific collaborations enabled by distributed computing infrastructure to emphasizing joint advances in digital infrastructure and how that infrastructure enables new research. This symbiotic relationship between research and infrastructure development could be called Research and Infrastructure Development Symbiosis (RaIDS). Going forward, RaIDS conferences should focus on improving communication between infrastructure developers and researchers to facilitate new collaborations, ensure research publications appropriately attribute enabling infrastructure advances, and standardize catalogs of available infrastructure and research challenges.
This document discusses Network-Enabled Platforms (NEP) and CANARIE's new mandate to fund their development. It provides context on NEPs, outlines CANARIE's objectives and implementation process, and details the requirements and criteria for funding proposals, including that projects must lead to sustainable infrastructure and involve collaboration. Key criteria for proposals are that they address specific user needs, involve multiple institutions, and result in infrastructure that continues after funding. Operators of general research infrastructure may implement platforms and develop shared middleware.
National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Innovative Partnerships Program (IPP) seeks to form partnerships to enhance future mission capabilities. The IPP acts as a facilitator and catalyst by bringing parties together, implementing new approaches, and identifying ways for partnerships to benefit NASA, partners, and taxpayers. The presentation provides an example partnership between NASA and Carnegie Mellon University's Robotics Institute to demonstrate how innovative partnerships can leverage resources and accelerate technology maturation.
This document summarizes a presentation about achieving visibility and insight across OpenStack projects using an integration pilot powered by Wikidsmart. It discusses current challenges with a lack of integration between project content and silos of information. The Wikidsmart demo shows faceted search and tracing a patch across tools. Next steps proposed include offering a public and private Wikidsmart portal to OpenStack members to bridge internal and community content.
Achieving Visibility and Insight across OpenStack Projects.pptOpenStack Foundation
This document discusses achieving visibility and insight across OpenStack projects through an integration pilot powered by Wikidsmart. It describes current challenges with a lack of integration between project content and silos of information. The Wikidsmart demo shows faceted search and tracing a patch across tools. Potential next steps include offering a public Wikidsmart portal for searching and dashboards, and a private portal for corporate members to bridge internal and community content.
This document provides an overview of how social media and Web 2.0 tools can enable mission success for project managers. It defines common social media terms like blogs, wikis, tagging, and social networking. It explains how these tools can improve communication, collaboration, and knowledge sharing to address common causes of project failure like poor communication. The document recommends that project managers use internal collaboration tools like team blogs and wikis as well as social networks to connect with colleagues.
How Social Networking can Enable Mission Success: An overview for Project Man...Robert_
This document provides an overview of how social media and Web 2.0 tools can enable mission success for project managers. It defines common social media terms like blogs, wikis, tagging, and social networking. It explains how these tools can improve communication, collaboration, and knowledge sharing to address common causes of project failure like poor communication. The document recommends that project managers use internal collaboration tools like team blogs and wikis as well as social networking among team members. It also provides examples of NASA resources available for these purposes.
NASA CoCEI Scaling Strategy - November 2023Steve Rader
This document summarizes NASA's efforts to scale up its use of open innovation and open talent initiatives across the agency. It discusses how NASA's Center of Excellence for Collaborative Innovation provides open innovation services and support to NASA programs and other federal agencies. It provides an overview of past and current contracts to access external talent and crowds, and highlights several case studies of open talent projects. It outlines the growth in demand for these services and discusses plans to further scale up and institutionalize open innovation and open talent practices at NASA through initiatives like the Open Innovation Academy, expanded use of digital tools and platforms, and engaging the NASA contractor base.
The document compares the operational complexity and costs of the Space Shuttle versus the Sea Launch Zenit rocket. [1] The Space Shuttle was designed for performance but not operational efficiency, resulting in costly ground, mission planning, and flight operations. [2] In contrast, the Zenit rocket was designed from the start to have automated and robust processes to keep operations simple and costs low. [3] The key lesson is that designing a launch system with operational requirements in mind from the beginning leads to much more efficient operations long-term.
The document provides an overview of project management and procurement at NASA. It discusses the key skills required for project managers, including acquisition management. It notes that 80-85% of NASA's budget is spent on contracts, and procurement processes are complex and constantly changing. The document outlines some common contract types and how they allocate risk between the government and contractor. It also discusses the relationship between contracting officers and project managers, and how successful procurement requires effective communication rather than direct control or authority.
The document introduces the NASA Engineering Network (NEN), which was created by the Office of the Chief Engineer to be a knowledge management system connecting NASA's engineering community. The NEN integrates various tools like a content management system, search engine, and collaboration tools. It provides access to key knowledge resources like NASA's Lessons Learned database and engineering databases. The NEN is working to expand by adding more communities, engineering disciplines, and knowledge repositories.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, tracking satellites, inventory management, procedures viewing, and videoconferencing. Managing laptops in space presents challenges around cooling, power, and software/hardware compatibility in the harsh space environment.
Laptops were first used in space in 1983 on the Space Shuttle, when Commander John Young brought the GRiD Compass portable computer on STS-9. Laptops are now widely used on the Space Shuttle and International Space Station for tasks like monitoring spacecraft systems, planning rendezvous and proximity operations, inventory management, procedure reviews, and communication between space and ground via software like WorldMap and DOUG. Managing laptops in space presents challenges around hardware durability, cooling, and software/data management in the space environment.
This document discusses the use of market-based systems to allocate scarce resources for NASA missions and projects. It provides examples of how market-based approaches were used for instrument development for the Cassini mission, manifesting secondary payloads on the space shuttle, and mission planning for the LightSAR Earth imaging satellite project. The document finds that these applications of market-based allocation benefited or could have benefited from a decentralized, incentive-based approach compared to traditional centralized planning methods. However, it notes that resistance to new approaches and loss of managerial control are barriers to adoption of market-based systems.
The Stardust mission collected samples from comet Wild 2 and interstellar dust particles. It launched in February 1999 and encountered Wild 2 in January 2004, collecting dust samples in aerogel. It returned the samples to Earth safely in January 2006. The spacecraft used an innovative Whipple shield to protect itself from comet dust impacts during the encounter. Analysis of the Stardust samples has provided insights about comet composition and the early solar system.
This document discusses solutions for integrating schedules on NASA programs. It introduces Stuart Trahan's company, which provides Earned Value Management (EVM) solutions using Microsoft Office Project that comply with OMB and ANSI requirements. It also introduces a partner company, Pinnacle Management Systems, that specializes in enterprise project management solutions including EVM, project portfolio management, and enterprise project resource management, with experience in the aerospace, defense, and other industries. The document defines schedule integration and describes some methods including importing to a centralized Primavera database for review or using Primavera ProjectLink for updates, and challenges including inconsistent data formats and levels of detail across sub-schedules.
The document discusses NASA's implementation of earned value management (EVM) across its Constellation Program to coordinate work across multiple teams. It outlines the organizational structure, current target groups, and an EVM training suite. It also summarizes lessons learned and the need for project/center collaboration to integrate schedules horizontally and vertically.
This document summarizes a presentation about systems engineering processes for principle investigator (PI) mode missions. It discusses how PI missions face special challenges due to cost caps and lower technology readiness levels. It then outlines various systems engineering techniques used for PI missions, including safety compliance, organizational communication, design tools, requirements management, and lessons learned from past missions. Specific case studies from NASA's Explorers Program Office are provided as examples.
This document discusses changes to NASA's business practices for managing projects, including adopting a new acquisition strategy approach and implementing planning, programming, and budget execution (PPBE). The new acquisition strategy involves additional approval meetings at the strategic planning and project levels to better integrate acquisition with strategic and budgetary planning. PPBE focuses on analyzing programs and infrastructure to align with strategic goals and answer whether proposed programs will help achieve NASA's mission. The document also notes improvements in funds distribution and inter-center transfers, reducing the time for these processes from several weeks to only a few days.
Spaceflight Project Security: Terrestrial and On-Orbit/Mission
The document discusses security challenges for spaceflight projects, including protecting space assets from disruption, exploitation, or attack. It highlights national space policy principles of protecting space capabilities. It also discusses trends in cyber threats, including the increasing capabilities of adversaries and how even unskilled attackers can compromise terrestrial support systems linked to space assets if defenses are not strong. Protecting space projects requires awareness of threats, vulnerabilities, and strategies to defend, restore, and increase situational awareness of space assets and supporting systems.
Humor can positively impact many aspects of project management. It can improve communication, aid in team building, help detect team morale issues, and influence leadership, conflict management, negotiation, motivation, and problem solving. While humor has benefits, it also has risks and not all uses of humor are positive. Future research is needed on humor in multicultural teams, its relationship to team performance, how humor is learned, and determining optimal "doses" of humor. In conclusion, humor is a tool that can influence people and projects, but must be used carefully and spontaneously for best effect.
The recovery of Space Shuttle Columbia after its loss in 2003 involved a massive multi-agency effort to search a wide debris field, recover crew remains and evidence, and compensate local communities. Over 25,000 people searched over 680,000 acres, recovering 38% of Columbia's weight. Extensive engineering investigations were conducted to identify the causes of failure and implement changes to allow the safe return to flight of Discovery in 2005.
This document summarizes research on enhancing safety culture at NASA. It describes a survey developed to assess NASA's safety culture based on principles of high reliability organizations. The survey was tailored specifically for NASA and has been implemented to provide feedback and identify areas for improvement. It allows NASA to benchmark its safety culture within and across other industries pursuing high reliability.
This document summarizes a presentation about project management challenges at NASA Goddard Space Flight Center. The presentation outlines a vision for anomaly management, including establishing consistent problem reporting and analysis processes across all missions. It describes the current problem management approach, which lacks centralized information sharing. The presentation aims to close this gap by implementing online problem reporting and trend analysis tools to extract lessons learned across missions over time. This will help improve spacecraft design and operations based on ongoing anomaly experiences.
This document discusses leveraging scheduling productivity with practical scheduling techniques. It addresses scheduling issues such as unwieldy schedule databases and faulty logic. It then discusses taming the schedule beast through using a scheduler's toolkit, schedule templates, codes to manipulate MS Project data, common views/filters/tables, limiting constraints, and other best practices. The document provides examples of using codes and custom views/filters to effectively organize and display schedule information.
This document describes Ball Aerospace's implementation of a Life Cycle and Gated Milestone (LCGM) process to improve program planning, execution, and control across its diverse portfolio. The LCGM provides a standardized yet flexible framework that maps out program activities and products across phases. It was developed through cross-functional collaboration and introduced gradually across programs while allowing flexibility. Initial results showed the LCGM supported improved planning and management while aligning with Ball Aerospace's entrepreneurial culture.
This document discusses the importance of situation awareness (SA) for project team members. It defines SA as having three levels: perception of elements in the current situation, comprehension of the current situation, and projection of the future status. Good team SA is achieved by turning individual SAs into shared SA through communication. Teams with strong SA prepare more, focus on comprehending and projecting, and maintain awareness through techniques like questioning assumptions and seeking additional information.
This document discusses theories of leadership and how a project manager's leadership style may impact project success depending on the type of project. It outlines early hypotheses that a PM's competence, including leadership style, is a success factor on projects. It presents a research model linking PM leadership competencies to project success, moderated by factors like project type. Initial interviews found that leadership style is more important on complex projects, and different competencies are needed depending on if a project is technical or involves change. Certain competencies like communication skills and cultural sensitivity were seen as important for different project types and contexts.
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
1. National Aeronautics and Space Administration
EMPLOYING WEB 2.0 IDEAS
IN GOVERNMENT
Presented by Dawn McIntosh
NASA Headquarters
Team Members:
Lead: Elizabeth Foughty, MCT, Inc.,
Francesca Barrientos Ph.D., formerly of RIACS,
Bryan Matthews, SGT, Inc.,
Ashok Srivastava Ph.D., NASA Ames Research Center
www.nasa.gov
2. Outline
• Why Web 2.0? Collaboration of course
• Web Tools applied to NASA
• DASHlink & Trac
• Challenges of Web 2.0 approaches @ NASA
• Example – highlighting unique attributes and
solution‐based approach
• Lessons Learned
• Concluding Remarks
National Aeronautics and Space Administration 2
3. Social Networks & the Workplace
“Research in a number of academic fields has shown that social networks
operate on many levels … and play a critical role in determining the way
problems are solved, organizations are run, and the degree to which individuals
succeed in achieving their goals.”
- Wikipedia, topic ‘Social Networks’
National Aeronautics and Space Administration 3
4. Web 2.0 Collaboration Tools & NASA
1. External benefits:
• Broadens the reach of ongoing research with partners, other NASA
researchers and the public
• Provides an opportunity to identify potential research partners
• Gives the public greater access to research and the ability to
participate
• Brings in students and young people
• Today’s Example: DASHlink website
2. Improves the efficiency of internal design and
development of the website
• Note: Web 2.0 doesn’t have to be public‐facing, there is benefit to
these processes in our internal projects
• Today’s Example: Trac
National Aeronautics and Space Administration 4
5. Some NASA forays into
Web 2.0 collaboration technologies
National Aeronautics and Space Administration 5
6. DASHlink website:
Disseminate. Collaborate. Innovate.
What is DASHlink?
DASHlink is a virtual laboratory for scientists and
engineers to disseminate results and collaborate
on research problems in health management
technologies for aeronautics systems.
https://dashlink.arc.nasa.gov
National Aeronautics and Space Administration 6
7. DASHlink Components
Content Component
• Code (Scientific Web 2.0 Features
Algorithms) •Member Contact
• Datasets (to be used to •Groups
develop new algorithms) •Discussions
• Research topics— •Associating Content
papers, posters, etc… •Tagging
Without the first, there’s nothing to discuss.
Without the second, there’s no added value.
National Aeronautics and Space Administration 7
8. Internal Collaborations -- Trac
• Our Trac system allows our development team, designers,
programmers, and manager to be ‘on the same page’ about
work
• All software code is kept in a versioning system that the
developers use to keep track of changes
• All discussion of the site is done through a ticketing system
(more rigorous than a wiki, and easier to search through)
• Each ticket is attached to a milestone, and we keep a
timeline of milestones
• The Trac site allows us to include and update (version)
website documentation as well, from mockups to terms
and conditions
• This site (and code) is completely open to all of NASA.
National Aeronautics and Space Administration 8
10. Fantastic: Now what? (How do I start?)
• Plan to work closely with:
• Your developers (please)
• Your policy makers and legal team
• Your expected users ‐ especially your internal NASA
users
• Begin with an end in mind
• Off the shelf is NOT always the best solution
• Less flexibility in design
• Not ‘every system’ compatible (sharepoint)
• Ties you to an outside company
National Aeronautics and Space Administration 10
11. Challenges of employing
Social Media and Web 2.0 tools at NASA
• A workforce unfamiliar with or just beginning to
use many social media tools (wikis, blogs etc).
• Cultural resistance to new ways of collaborating.
• Policy and legal barriers, especially as they relate to
freely uploading content to the web. Government
must comply with many rules that private industry
does not contend with.
National Aeronautics and Space Administration 11
12. Example:
Challenges of Community Moderation on a NASA website
To foster open and up‐to‐the‐minute
research collaborations, it was deemed truly
necessary to have a community‐moderated
website rather than the standard NASA
website official moderating site content.
National Aeronautics and Space Administration 12
13. Example (cont):
Challenges of Community Moderation on a NASA website
• Policy!!
• Tentative Users
• Some users were uncertain what could and
could not be posted on a public website
• Some users had concerns about possible abuse
of a nasa.gov website
• Others were unaccustomed to presenting
preliminary and ongoing research
National Aeronautics and Space Administration 13
14. Example (cont):
Challenges of Community Moderation on a NASA website
Solution – Registered Users and an atypical registration process
• Only registered users can post content on DASHlink
• NOTE: Everyone, including the general public, can view and download content
• With the Ames legal team, a new Terms & Conditions was developed. Every time a
registered user posts info, they have to agree to the Terms & Conditions
• DASHlink’s atypical registration process:
• NASA Civil Servants can register themselves
• All others must identify a NASA Civil Servants from the site who can sponsor them. That
sponsor is notified by email and must agree to sponsor the applicant
• NASA Civil Servants are not taking on the responsibility of moderating those they
sponsor. Instead, sponsors are agreeing that they know the applicant and believe that
their contribution to DASHlink would be relevant
National Aeronautics and Space Administration 14
15. Overcoming the challenges---Lessons Learned
1. An agile design process, reformulated to address
the policy and legal questions.
2. Top down encouragement from Project
Management, bottom up encouragement from
Grad students (e.g., younger users).
3. A focus on content creation and community
growth.
4. Make the site incredibly easy to use.
5. …and a bit of persistence, especially working
with policy makers and legal.
National Aeronautics and Space Administration 15
16. 1. Design Process
to identify and implement the Best Tools
Typical Agile Design Process
National Aeronautics and Space Administration 16
17. 1. Design Process
to identify and implement the Best Tools
AAAAAAOur Design Process
Redesign
-or-
Change policy
if no
Work with policy /
legal team to
determine if
design idea can
be
if yes accommodated
National Aeronautics and Space Administration 17
18. 2. Encouragement from All Sides
Grad students put material up
National Aeronautics and Space Administration 18
19. 3. Content Creation & Community Growth
If you fill it, they will come.
Our potential users needed a reason to begin
using the site, beyond the fact the tool was fun
and could “potentially” be incredibly powerful.
By focusing on making it incredibly easy to upload
content, then encouraging certain users to do so
through various methods
• For instance, by running a ‘virtual’ poster session on
DASHlink during an annual conference. This
introduced users to the site, who then began using it
for its intended purpose.
National Aeronautics and Space Administration 19
20. 4. Ease of Use Leads to More Content Creation
• Throughout our design process we strove to
always make using the site as basic and simple as
possible. This often meant forgoing “cooler” tools.
• Even now, we are always responsive when users
comment on our process.
• ‘Feedback’ link for Registered Users on every page. And
a ‘Contact Us’ link for everyone at the bottom of every
page
• As designers, it’s important to remember that just
because WE understand how to use our
wiki/blog/tagging tool doesn’t mean they do.
National Aeronautics and Space Administration 20
21. 5. Work with Policy Makers & Legal Departments
• Don’t implement an idea without getting approval first. It’s
better to work with policy makers than fight against them
• Do have a solid ‘elevator pitch’ ready
• Do think from their perspective, and have a counter
argument prepared
• Do be willing to compromise but not willing to give in
• Do have a Plan B (and C and D) ready to implement if you
can’t move policy
• Do consider unconventional solutions
National Aeronautics and Space Administration 21
22. 5. Stick it out (be persistent)
• It takes government agencies a long time to
change.
• Be willing to compromise, but not
drastically.
• Continually look for new ways to draw users
in…community development is an ongoing
process.
National Aeronautics and Space Administration 22
23. How did we encourage open collaboration at NASA?
• We researched what other sites did:
Most used wikis or forums, along with downloadable
source code, to coordinate efforts.
• We built user friendly tools
• We worked with our policy and legal teams to find
solutions
• We strongly encouraged content creation by
parties we knew to populate the site initially (top
down and bottom up).
National Aeronautics and Space Administration 23
24. End Result
• Web 2.0 @ NASA: Most people see the benefit of
using social media tools – it’s less about
persuading, and more about lowering barriers (to
use, to publishing).
• Project success: DASHlink succeeded in becoming a
public‐facing community‐moderated website which
continues to grow and evolve based on our
community’s needs.
• And DASHlink has experienced continually increasing
site membership and traffic since release (June 2008).
National Aeronautics and Space Administration 24
25. DASHlink Stats*
Others (non-US
Google, NASA
sites, space
interest sites,
etc.)
27.4%
Total Downloads (Dec‐Jan): 12,428
Total Membership: 224 and counting
Sessions from
direct access
Uses of the ‘contact me’ feature (Dec‐Jan): 78
Sessions started
from Google 49.2%
searches
23.4% *Totals refer to the total downloads filtered for
visits by ‘bots or other crawlers. These are, to the
very best of our knowledge, accurate statistics.
National Aeronautics and Space Administration 25
26. Thank You to the DASHlink Team Members
(past and present)
Dr. Francesca Barrientos, formerly of RIACS
Chris Fattarsi, ASANI Solutions, LLC
Elizabeth Foughty, Mission Critical Technologies, Inc.
Dave Kluck, Mission Critical Technologies, Inc.
Bryan Matthews, SGT, Inc.
Dawn McIntosh, NASA HQ
Ray McIntosh, Ames Associate
Dr. Ashok Srivastava, NASA Ames Research Center
Eric Titolo, SGT, Inc.
Sergey Yentus, SGT, Inc.
National Aeronautics and Space Administration 26
27. Questions?
https://dashlink.arc.nasa.gov
http://trac.edgewall.org/
National Aeronautics and Space Administration 27