1. 1 1 National Aeronautics and Space Administration cFS Workshop Introduction The Johns Hopkins University Applied Physics Laboratory core Flight Software System Workshop October 26, 2015 David McComas – NASA Goddard Space Flight Center

2. 2 Logistics Full day so minimal breaks in the agenda Break room for side discussions Lunch options -Pre-order from APL cafeteria -Lunch trucks

3. 3 cFS Workshop Agenda StartDurationStop TitlePresenterContent 9:000:459:45 Welcome & Community OverviewDave McComasWelcome, cFS Community Overview and Plan, Action Summary 9:450:3010:15 HQ HappeningsMike AguilarSoftware release status, TCAT Debrief 10:150:4511:00 Product ManagementSusie StregeCurrent Configuration Control Board activities and products 11:000:3011:30 Future Products & TechnologyJonathan Wilmot Message ID, EDS, etc. 11:304:454:15 User presentations 0:20 User 1: S&K Global SolutionsMike MonahanCommunity Needs Survey Results 0:45 Lunch 0:20 User 2: Odyssey Space ResearchMatt BensonIntegrated Development Environment 0:20 User 3: Embedded Systems SolutionCharlie Rogers 0:20 User 4: EXB SolutionsPaul CarpenterAutomated Test for NASA cFS 0:20 User 5: LMSCORyan SlabaughInserting Core Flight System 0:20 User 6: TTTechChristian FidicFS OS enhancements for network 0:20 User 7: Johns Hopkins APLChris Monaco 0:20 User 8: NASA ARCCraig Pires 0:20 User 9: NASA GSFCAlan Cudmore 0:20 User 10: NASA JSCLore ProkopAES cFS-based Projects 0:20 User 11: EmergentBrendan O'ConnorcFS Components for Autonomous Missions, FDIR, and Sensor Interactions 0:20 User 12: NASA IVVJustin Morris 0:15 Break 4:301:005:30 Wrap up, Future Plans, Actions, etc.Dave, Gary, LeadsReview feedback and coordinate near-term future plans

4. 4 cFS Workshop Goals Discuss current informal community charter/organization and create a roadmap for establishing a formal charter Get feedback from user community to understand their perspectives, needs, and goals Describe current product management, identify needs, and create a plan forward Describe current communication mechanisms, shortcomings, and create a plan forward Provide path for how to engage and grow the community -Introduce virtual teams Reduce risk of fragmentation!!

5. 5 cFS Workshop Strategy Agenda flow -Where are we now? -Where do we want to be? -How can we get there? Gary Smith is our workshop administrative officer -Take notes and log action items -Inputs via sign up sheets or email: opensat.cfs@gmail.com Compile attendance list: Name, Organization, Location (APL or remote) Virtual team sign up Accept general comments Gary and I will organize the programmatic/technical information to help facilitate our final session of the workshop

6. 6 Before we begin… Questions, suggestions, etc. There are 10 types of people in the world: those who understand binary, and those who don't

7. 7 7 National Aeronautics and Space Administration Community Overview The Johns Hopkins University Applied Physics Laboratory core Flight Software System Workshop October 26, 2015 David McComas – NASA Goddard Space Flight Center

8. 8 Agenda Community -Background -Current state -Next steps Virtual Teams Website Proposal User Scenarios

9. 9 Background < 2007: Birth of core Flight Executive (cFE) -GSFC assessment of FSW reuse to date, heritage analysis, architectural trades -Project independent funding kick started the effort -Operating System Abstraction Layer (OSAL) released as open source 2007: cFE goes to the Moon -LRO launched using OSAL & cFE 2008 – 2014: Birth of core Flight System (cFS) -Developed 12 cFS applications -Leveraged project funding -JSC certified Class A pedigree of cFS targeted to the ARINC-653 2014: Birth of a Community -12 cFS applications released as open source -cFS Workshop (12/15 at GRC) established a NASA-wide repository managed by an inter-center Configuration Control Board (CCB) 2015: Community is growing up -Successful release of cFE 6.4.2 -cFE API is unchanged since LRO -First cFS Workshop

10. 10 cFS Community Purpose Advance the creation, evolution, promotion, and support of a NASA Class B flight software system -Important we stay focused on our domain Cultivate both an open source community and an ecosystem of complementary products, capabilities, and services. -All inclusive in terms of organizations -No constraints on complementary products

11. 11 State of the Community Business Model Funding Model -No institutional funding, Advanced Exploration Systems (JSC) provides a lifeline -Members use ‘local’ funding to support community activities -New release content driven by upcoming member mission needs No formal community charter, by-laws, or operating procedures in place -Original 2012 draft charter never signed -Some original concepts still valid, but top-down funding approach needs rework Product Management is evolving and a management plan needs to be defined to cover -Scope of products controlled by the CCB -Product release strategies and versioning -Product delivery and community feedback

12. 12 State of the Community Communication Mailing Lists -cfs-community@lists.nasa.gov Contains all members -cfs-community-ccb@lists.nasa.gov CCB members Public Websites -https://cfs.gsfc.nasa.gov/ General information and links to all open source code and documents on Sourceforge -https://sourceforge.net/projects/xxx Multiple projects for different cFS components Restricted access (requires NDC account) -https://nsckn.nasa.gov/Community NESC hosted server containing discussion forums, documents, meeting notes… Approved for ITAR and Sensitive But Unclassified (SBU) material -https://babelfish.arc.nasa.gov/ ARC hosted server used for inter-center collaboration Git andTrac used for source code configuration management and change requests Not approved for ITAR material

13. 13 A Few Realities… ITAR (International Traffic in Arms Regulations) and the EAR (Export Administration Regulations) -Export control regulations -Recent ITAR changes have moved some space related items from the U.S. Munitions List (USMAL) to the Commerce Control List (CCL) NASA Software Engineering Requirements, NPR-7150.2B (11/19/14 – 11/19/19) -Establishes the engineering requirements for software acquisition, development, maintenance, retirement, operations, and management consistent with the governance model contained in NASA Policy Directive (NPD) 1000.0, NASA Governance and Strategic Management Handbook. This NASA Procedural Requirements (NPR) supports the implementation of the NASA Policy Directive (NPD) 7120.4. Release of NASA Software, NPR-2210.1C (expired 8/11/15) -Establishes procedures and responsibilities for the reporting, review, assessment, and release of software created by or for NASA Inventions Made By Government Employees, NPD 2091.1B (4/21/08 – 4/21/18) -Civil servant or contractors receiving research and development funding are required to report their findings to the Technology Transfer Office

14. 14 Apps App Libraries OS Abstract OS Abstract PSPs Applications cFE Apps Core Lab Apps Ground Systems Development Tools & APIs Unit Test Performance Table EDS ASIST ITOS COSMOS App Library Executive Platform Abstraction cFE NASA Product Management NASA Controlled AssetsExternal to cFSMember Sponsored Assets cFS Community Government Industry Academia International User Support Users: Feedback, Feature Requests, Bug Reports Contributors: Bug Fixes, Verification Members PSPs OS Abstract OS Abstract Platform Support Package API Platform Support Package API OS Abstraction API OS Abstraction API cFE cFE API

15. 15 cFS Community The power of a community -1993, 2001, 2009 NASA Controlled Assets (NCA) -Assets managed by the NASA CCB -Architectural in nature -Maintained in accordance with NPR-7150.2B Class B requirements Member Sponsored Assets (MSA) -Developed and released by a community member -No NPR-7150.2B requirements -NASA projects would need MSA process to migrate assets to be used on a NASA mission Formalize charter and operational procedures -Mature draft plan and create a plan to get it signed -Steering committee (could be subset of CCB) that meets regularly (quarterly) to mange strategic direction

16. 16 Virtual Teams Groups of people aligned with a common interest -E.g. Multicore processors, Xenomai, Electronic Data Sheets Two types -Integrated Team: Organized as a project -Cooperative: Parallel teams that maintain communication Challenges -Funding source(s) may not agree with producing cFS assets in addition to their own goals. “Think global, act local” doesn’t work in every situation. -Restrictions on sharing information -Aligning teams with NASA Controlled Asset deliverables

17. 17 Virtual Team Topic Area - Architecture Multicore, Partitioned Systems, Memory Protection Software Bus Network Driver Plugins Libraries Non-volatile configurations, EEPROM File System (EEFS) Security

18. 18 Virtual Teams Topic Area - Tools Deployment, Configuration Parameter profiles Automated unit testing Platform-independent build testing Application Certification Electronic Data Sheets Code Generation: Simulink Interface Layer Benchmarks Integrated Development Environment Ground systems

19. 19 Virtual Team Topic Area - Communication Website Training courses Promotional material Business case material Outreach & Education -Learning platforms: Quadcopter, PiSat, …

20. 20 Website Proposal The University of Florida’s Center for High-Performance Reconfigurable Computing (CHREC http://www.hcs.ufl.edu/~george/) offered to host a cFS websitehttp://www.hcs.ufl.edu/~george/ -Initial discussions have defined needs and potential solutions -This workshop can be used help refine ideas Evolutionary approach -Create document repository and discussion forum -Create infrastructure for member sponsored products and collaborative projects -Create infrastructure for NASA controlled products Target a ‘go live’ date after the 12/15 cFE delivery (Early 2016)

21. 21 User Scenarios Identify and prioritize user scenarios that need to be supported by the community 1.Obtain and build the cFS -Locate product and follow instructions -Ask questions 2.Configure and target the cFS to a platform -Learn whether desired target has been done before -Get training 3.Submit a trouble ticket 4.Make a contribution back to a product: NASA or user sponsored 5.Obtain a list of outstanding tickets 6.Get information on future release plans 7.Submit a Member Sponsored Artifact 8.Form a virtual team 9.Create a collaboration project