Search NASA⌕ Search

SEARCH · Search NASA

Results for “sharepoint”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

Developing a Business Intelligence Process for a Training Module in SharePoint 2010

Prior to this project, training information for the employees of the National Center for Critical Processing and Storage (NCCIPS) was stored in an array of unrelated spreadsheets and SharePoint lists that had to be manually updated. By developing a content management system through a web application platform named SharePoint, this training system is now highly automated and provides a much less intensive method of storing training data and scheduling training courses. This system was developed by using SharePoint Designer and laying out the data structure for the interaction between different lists of data about the employees. The automation of data population inside of the lists was accomplished by implementing SharePoint workflows which essentially lay out the logic for how data is connected and calculated between certain lists. The resulting training system is constructed from a combination of five lists of data with a single list acting as the user-friendly interface. This interface is populated with the courses required for each employee and includes past and future information about course requirements. The employees of NCCIPS now have the ability to view, log, and schedule their training information and courses with much more ease. This system will relieve a significant amount of manual input and serve as a powerful informational resource for the employees of NCCIPS in the future.

Schmidtchen, Bryce↗

Identity Federation and Its Importance for NASA's Future: The SharePoint Extranet Pilot

My project at Kennedy Space Center (KSC) during the spring 2013 Project Management and Systems Engineering Internship was to functionalJy test and deploy the SharePoint Extranet system and ensure successful completion of the project's various lifecycle milestones as described by NASA Procedural Requirement (NPR) 7 120.7. I worked alongside NASA Project Managers, Systems Integration Engineers, and Information Technology (IT) Professionals to pilot this collaboration capability between NASA and its External Partners. The use of identity federation allows NASA to leverage externally-issued credentials of other federal agencies and private aerospace and defense companies, versus the traditional process of granting and maintaining full NASA identities for these individuals. This is the first system of its kind at NASA and it will serve as a pilot for the Federal Government. Recognizing the novelty of this service, NASA's initial approach for deployment included a pilot period where nearby employees of Patrick Air Force Base would assist in testing and deployment. By utilizing a credential registration process, Air Force users mapped their Air Force-issued Common Access Cards (CAC) to a NASA identity for access to the External SharePoint. Once the Air Force stands up an Active Directory Federation Services (ADFS) instance within their Data Center and establishes a direct trust with NASA, true identity federation can be established. The next partner NASA is targeting for collaboration is Lockheed Martin (LMCO), since they collaborate frequently for the ORION Program. Through the use of Exostar as an identity hub, LMCO employees will be able to access NASA data on a need to know basis, with NASA ultimately managing access. In a time when every dollar and resource is being scrutinized, this capability is an exciting new way for NASA to continue its collaboration efforts in a cost and resource effective manner.

Baturin, Rebecca R.↗

Sharepoint Team Site Configuration

The Data Mining project seeks to bring the capability of data visualization to NASA anomaly and problem reporting systems for the purpose of improving data trending, evaluations, and analyses. Currently NASA systems are tailored to meet the specific needs of its organizations. This tailoring has led to a variety of nomenclatures and levels of annotation for procedures, parts and anomalies making difficult the realization of the common causes for anomalies. Making significant observations and realizing the connection between these causes without a common way to view data is difficult to impossible. The Data Mining project is in its early stages of presenting a common visualization of normalized data through a web based portal. In this paper I detail what I have learned and what I have accomplished during my time as an intern toward the purpose of creating the project portal. I have gone through an iterative process of familiarization with the project and its goals, site design, research, modification and review on the road to creating a common method and location to view the visualized data created under this project.

iss↗

ExMC Technology Watch

The Technology Watch (Tech Watch) project is directed by the NASA Human Research Programs (HRP) Exploration Medical Capability (ExMC) element, and primarily focuses on ExMC technology gaps. The project coordinates the efforts of multiple NASA centers, including the Johnson Space Center (JSC), Glenn Research Center (GRC), Ames Research Center (ARC), and the Langley Research Center (LaRC). The objective of Tech Watch is to identify emerging, high-impact technologies that augment current NASA HRP technology development efforts. Identifying such technologies accelerates the development of medical care and research capabilities for the mitigation of potential health issues encountered during human space exploration missions. The aim of this process is to leverage technologies developed by academia, industry and other government agencies and to identify the effective utilization of NASA resources to maximize the HRP return on investment. The establishment of collaborations with these entities is beneficial to technology development, assessment and/or insertion, and advance NASAs goal to provide a safe and healthy environment for human exploration. In fiscal year 2013, the Tech Watch project maintained student project activity aimed at specific ExMC gaps, completed the gap report review cycle for all gaps through a maturated gap report review process, and revised the ExMC Tech Watch Sharepoint site for enhanced data content and organization. Through site visits, internships and promotions via aerospace journals, several student projects were initiated and completed this past year. Upon project completion, the students presented their results via telecom or WebEx to the ExMC Element as a whole. The upcoming year will continue to forge strategic alliances and student projects in the interest of technology and knowledge gap closure. Through the population of Sharepoint with technologies assessed by the gap owners, the database expansion will develop a more comprehensive technology set for each gap. By placing such data in Sharepoint, the gap report updates in fiscal year 2014 are anticipated to be streamlined since the evaluated technologies will be readily available to the gap owners in a sortable archive, and may be simply exported into the final gap report presentation.

Technology gaps↗

ExMC Technology Watch

The Technology Watch (Tech Watch) project is directed by the NASA Human Research Program's (HRP) Exploration Medical Capability (ExMC) element, and primarily focuses on ExMC technology gaps. The project coordinates the efforts of multiple NASA centers, including the Johnson Space Center (JSC), Glenn Research Center (GRC), Ames Research Center (ARC), and the Langley Research Center (LaRC). The objective of Tech Watch is to identify emerging, high-impact technologies that augment current NASA HRP technology development efforts. Identifying such technologies accelerates the development of medical care and research capabilities for the mitigation of potential health issues encountered during human space exploration missions. The aim of this process is to leverage technologies developed by academia, industry and other government agencies and to identify the effective utilization of NASA resources to maximize the HRP return on investment. The establishment of collaborations with these entities is beneficial to technology development, assessment and/or insertion, and advance NASA's goal to provide a safe and healthy environment for human exploration. In fiscal year 2013, the Tech Watch project maintained student project activity aimed at specific ExMC gaps, completed the gap report review cycle for all gaps through a maturated gap report review process, and revised the ExMC Tech Watch Sharepoint site for enhanced data content and organization. Through site visits, internships and promotions via aerospace journals, several student projects were initiated and completed this past year. Upon project completion, the students presented their results via telecom or WebEx to the ExMC Element as a whole. The upcoming year will continue to forge strategic alliances and student projects in the interest of technology and knowledge gap closure. Through the population of Sharepoint with technologies assessed by the gap owners, the database expansion will develop a more comprehensive technology set for each gap. By placing such data in Sharepoint, the gap report updates in fiscal year 2014 are anticipated to be streamlined since the evaluated technologies will be readily available to the gap owners in a sortable archive, and may be simply exported into the final gap report presentation

Exploration Medical Capability↗

Calysto: Risk Management for Commercial Manned Spaceflight

The Calysto: Risk Management for Commercial Manned Spaceflight study analyzes risk management in large enterprises and how to effectively communicate risks across organizations. The Calysto Risk Management tool developed by NASA's Kennedy Space Center's SharePoint team is used and referenced throughout the study. Calysto is a web-base tool built on Microsoft's SharePoint platform. The risk management process at NASA is examined and incorporated in the study. Using risk management standards from industry and specific organizations at the Kennedy Space Center, three methods of communicating and elevating risk are examined. Each method describes details of the effectiveness and plausibility of using the method in the Calysto Risk Management Tool. At the end of the study suggestions are made for future renditions of Calysto.

Dillaman, Gary↗

NASA Pathways Co-op Tour Johnson Space Center Fall 2013

This report outlines the tasks and objectives completed during a co‐operative education tour with National Aeronautics and Space Association (NASA) at the Johnson Space Center in Houston, Texas. I worked for the Attitude & Pointing group of the Flight Dynamics Division within the Mission Operations Directorate at Johnson Space Center. NASA's primary mission is to support and expand the various ongoing space exploration programs and any research and development activities associated with it. My primary project required me to develop and a SharePoint web application for my group. My secondary objective was to become familiar with the role of my group which was primarily to provide spacecraft attitude and line of sight determination, including Tracking and Data Relay Satellite (TDRS) communications coverage for various NASA, International, and commercial partner spacecraft. My projects required me to become acquainted with different software systems, fundamentals of aerospace engineering, project management, and develop essential interpersonal communication skills. Overall, I accomplished multiple goals which included laying the foundations for an updated SharePoint which will allow for an organized platform to communicate and share data for group members and external partners. I also successfully learned about the operations of the Attitude & Pointing Group and how it contributes to the Missions Operations Directorate and NASA's Space Program as a whole

Masood, Amir↗

Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project

Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.

Systems Engineering environments↗

Tracking the Short Term Planning (STP) Development Process

Part of the National Aeronautics and Space Administration?s mission is to pioneer the future in space exploration, scientific discovery and aeronautics research is enhanced by discovering new scientific tools to improve life on earth. Sequentially, to successfully explore the unknown, there has to be a planning process that organizes certain events in the right priority. Therefore, the planning support team has to continually improve their processes so the ISS Mission Operations can operate smoothly and effectively. The planning support team consists of people in the Long Range Planning area that develop timelines that includes International Partner?s Preliminary STP inputs all the way through to publishing of the Final STP. Planning is a crucial part of the NASA community when it comes to planning the astronaut?s daily schedule in great detail. The STP Process is in need of improvement, because of the various tasks that are required to be broken down in order to get the overall objective of developing a Final STP done correctly. Then a new project came along in order to store various data in a more efficient database. "The SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas."

Price, Melanie↗

Team Collaboration Software

The Ground Resource Allocation and Planning Environment (GRAPE 1.0) is a Web-based, collaborative team environment based on the Microsoft SharePoint platform, which provides Deep Space Network (DSN) resource planners tools and services for sharing information and performing analysis.

Wang, Yeou-Fang↗

Health Maintenance System (HMS) Hardware Research, Design, and Collaboration

The Space Life Sciences division (SLSD) concentrates on optimizing a crew member's health. Developments are translated into innovative engineering solutions, research growth, and community awareness. This internship incorporates all those areas by targeting various projects. The main project focuses on integrating clinical and biomedical engineering principles to design, develop, and test new medical kits scheduled for launch in the Spring of 2011. Additionally, items will be tagged with Radio Frequency Interference Devices (RFID) to keep track of the inventory. The tags will then be tested to optimize Radio Frequency feed and feed placement. Research growth will occur with ground based experiments designed to measure calcium encrusted deposits in the International Space Station (ISS). The tests will assess the urine calcium levels with Portable Clinical Blood Analyzer (PCBA) technology. If effective then a model for urine calcium will be developed and expanded to microgravity environments. To support collaboration amongst the subdivisions of SLSD the architecture of the Crew Healthcare Systems (CHeCS) SharePoint site has been redesigned for maximum efficiency. Community collaboration has also been established with the University of Southern California, Dept. of Aeronautical Engineering and the Food and Drug Administration (FDA). Hardware disbursements will transpire within these communities to support planetary surface exploration and to serve as an educational tool demonstrating how ground based medicine influenced the technological development of space hardware.

Gonzalez, Stefanie M.↗

International Space Station Mechanisms and Maintenance Flight Control Documentation and Training Development

International Space Station (ISS) crew and flight controller training documentation is used to aid in training operations. The Generic Simulations References SharePoint (Gen Sim) site is a database used as an aid during flight simulations. The Gen Sim site is used to make individual mission segment timelines, data, and flight information easily accessible to instructors. The Waste and Hygiene Compartment (WHC) training schematic includes simple and complex fluid schematics, as well as overall hardware locations. It is used as a teaching aid during WHC lessons for both ISS crew and flight controllers. ISS flight control documentation is used to support all aspects of ISS mission operations. The Quick Look Database and Consolidated Tool Page are imagery-based references used in real-time to help the Operations Support Officer (OSO) find data faster and improve discussions with the Flight Director and Capsule Communicator (CAPCOM). A Quick Look page was created for the Permanent Multipurpose Module (PMM) by locating photos of the module interior, labeling specific hardware, and organizing them in schematic form to match the layout of the PMM interior. A Tool Page was created for the Maintenance Work Area (MWA) by gathering images, detailed drawings, safety information, procedures, certifications, demonstration videos, and general facts of each MWA component and displaying them in an easily accessible and consistent format. Participation in ISS mechanisms and maintenance lessons, mission simulation On-the-Job Training (OJT), and real-time flight OJT was used as an opportunity to train for day-to-day operations as an OSO, as well as learn how to effectively respond to failures and emergencies during mission simulations and real-time flight operations.

Daugherty, Colin C.↗

Enterprise Reference Library

Introduction: Johnson Space Center (JSC) offers two extensive libraries that contain journals, research literature and electronic resources. Searching capabilities are available to those individuals residing onsite or through a librarian s search. Many individuals have rich collections of references, but no mechanisms to share reference libraries across researchers, projects, or directorates exist. Likewise, information regarding which references are provided to which individuals is not available, resulting in duplicate requests, redundant labor costs and associated copying fees. In addition, this tends to limit collaboration between colleagues and promotes the establishment of individual, unshared silos of information The Integrated Medical Model (IMM) team has utilized a centralized reference management tool during the development, test, and operational phases of this project. The Enterprise Reference Library project expands the capabilities developed for IMM to address the above issues and enhance collaboration across JSC. Method: After significant market analysis for a multi-user reference management tool, no available commercial tool was found to meet this need, so a software program was built around a commercial tool, Reference Manager 12 by The Thomson Corporation. A use case approach guided the requirements development phase. The premise of the design is that individuals use their own reference management software and export to SharePoint when their library is incorporated into the Enterprise Reference Library. This results in a searchable user-specific library application. An accompanying share folder will warehouse the electronic full-text articles, which allows the global user community to access full -text articles. Discussion: An enterprise reference library solution can provide a multidisciplinary collection of full text articles. This approach improves efficiency in obtaining and storing reference material while greatly reducing labor, purchasing and duplication costs. Most importantly, increasing collaboration across research groups provides unprecedented access to information relevant to NASA s mission. Conclusion: This project is an expansion and cost-effective leveraging of the existing JSC centralized library. Adding key word and author search capabilities and an alert function for notifications about new articles, based on users profiles, represent examples of future enhancements.

Bickham, Grandin↗

Summer Final Report

The summer of 2012 has been filled with many memorable events and activities. As an intern, I had responsibilities that had to be fulfilled. My tour of duty was completed as an administrative student trainee in the Information Technology and Communications Services Business Office (IT-A). In accordance with the Business Objectives and Agreement of the Business Office and my performance plan, I was to provide business office support, improve business, project management, and technical work processes. With this being stated, I supported a project called "The Big Move Project" (TBMP), which will take course over the next several years. The Big Move Project is the planning of the Information Technology (IT) Directorate's relocation to various buildings in the course of upcoming years, when designs and the building of Central Campus have been completed. Working directly with my supervisor and the project manager, I was responsible for gathering both administrative and operational area requirements for the Information Technology (IT) Directorate, along with its outsourced support and contractors, such as IMCS, NICS, and ACES. My first action was to create rubrics that will serve as a guideline for the information that should be given by each branch of IT. After receiving that information via a few KAITS actions, I was able to start the consolidation process, and begin working on a presentation. A SharePoint was created shortly after for others to view the progression of the project, which I managed. During the consolidation ofthis information, I would occasionally present to the IT Deputy Director and IT Chiefs. The draft of this presentation was shown to employees of Center Operations (T A) and stakeholders-IT Chief Officers and contractor managers-in the relocation of IT to make them aware of what requirements must be met that will enable IT to be accommodated appropriately in the design of Central Campus Phase 11-the time in which IT and its contractors are scheduled to be relocated. Besides supporting TBMP, I also supported the Section 508 Policy Compliance Coordinator, R. Liang. Section 508 is a policy that requires employers to implement accessibility assurance of information and technology to disabled communities. On Thursday, July 19, 2012, I was able to go to Camp Boggy Creek-a camp for disabled children-for an education outreach, in collaboration with the Education Office. We shared with them information about how astronauts live and work in space, they were able to ride hovercrafts, build paper rockets, and then launch them outside. Although this outreach was quite fun with the kids at the camp, this was a learning opportunity to gain some insight to those with cognitive and physical disabilities, the problems they typically face, and in tum, how to accommodate those with disabilities in the work environment. In the process of implementing accessibility and Section 508 compliance, I attended various teleconferences, did field runs to supply closed-caption call phones to employees with limited hearing, and helped with the development of the charter ofthe Section 508 Compliance Working Group.

Makidi, Nitou↗

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA (Extravehicular Activity) Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, searchable repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, the one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision control system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, and also for hundreds of other NASA and contract employees. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie↗

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, easy to search repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision controlled system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, as well as hundreds of others that support the EVA. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie S.↗

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, easy to search repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision controlled system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, as well as hundreds of others that support EVA. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie S.↗

Simulation of Mission Phases

This position with the Simulation and Graphics Branch (ER7) at Johnson Space Center (JSC) provided an introduction to vehicle hardware, mission planning, and simulation design. ER7 supports engineering analysis and flight crew training by providing high-fidelity, real-time graphical simulations in the Systems Engineering Simulator (SES) lab. The primary project assigned by NASA mentor and SES lab manager, Meghan Daley, was to develop a graphical simulation of the rendezvous, proximity operations, and docking (RPOD) phases of flight. The simulation is to include a generic crew/cargo transportation vehicle and a target object in low-Earth orbit (LEO). Various capsule, winged, and lifting body vehicles as well as historical RPOD methods were evaluated during the project analysis phase. JSC core mission to support the International Space Station (ISS), Commercial Crew Program (CCP), and Human Space Flight (HSF) influenced the project specifications. The simulation is characterized as a 30 meter +V Bar and/or -R Bar approach to the target object's docking station. The ISS was selected as the target object and the international Low Impact Docking System (iLIDS) was selected as the docking mechanism. The location of the target object's docking station corresponds with the RPOD methods identified. The simulation design focuses on Guidance, Navigation, and Control (GNC) system architecture models with station keeping and telemetry data processing capabilities. The optical and inertial sensors, reaction control system thrusters, and the docking mechanism selected were based on CCP vehicle manufacturer's current and proposed technologies. A significant amount of independent study and tutorial completion was required for this project. Multiple primary source materials were accessed using the NASA Technical Report Server (NTRS) and reference textbooks were borrowed from the JSC Main Library and International Space Station Library. The Trick Simulation Environment and User Training Materials version 2013.0 release was used to complete the Trick tutorial. Multiple network privilege and repository permission requests were required in order to access previous simulation models. The project was also an introduction to computer programming and the Linux operating system. Basic C++ and Python syntax was used during the completion of the Trick tutorial. Trick's engineering analysis and Monte Carlo simulation capabilities were observed and basic space mission planning procedures were applied in the conceptual design phase. Multiple professional development opportunities were completed in addition to project duties during this internship through the System for Administration, Training, and Education Resources for NASA (SATERN). Topics include: JSC Risk Management Workshop, CCP Risk Management, Basic Radiation Safety Training, X-Ray Radiation Safety, Basic Laser Safety, JSC Export Control, ISS RISE Ambassador, Basic SharePoint 2013, Space Nutrition and Biochemistry, and JSC Personal Protective Equipment. Additionally, this internship afforded the opportunity for formal project presentation and public speaking practice. This was my first experience at a NASA center. After completing this internship I have a much clearer understanding of certain aspects of the agency's processes and procedures, as well as a deeper appreciation from spaceflight simulation design and testing. I will continue to improve my technical skills so that I may have another opportunity to return to NASA and Johnson Space Center.

Carlstrom, Nicholas Mercury↗