Statement of Work Sub-Task: Tracking Data Reader/Writer
Statement of Work Sub-Task: Tracking Data Reader/Writer
Statement of Work Sub-Task: Tracking Data Reader/Writer
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Statement</strong> <strong>of</strong> <strong>Work</strong><strong>Task</strong>: GMAT Navigation ComponentDevelopment<strong>Task</strong> Order: 28<strong>Task</strong> Modification: 7I. Summary <strong>of</strong> Changes in this <strong>Task</strong> ModificationThis task modification continues development and testing support required for the GeneralMission Analysis Tool (GMAT). The PoP for this mod ends Nov. 1, 2013 A task has been added for tracking data reading and writing A task has been added to test and further develop GMAT navigation componentsII.Summary <strong>of</strong> <strong>Work</strong>This statement <strong>of</strong> work describes support to be provided by the Flight Dynamics SupportServices (FDSS) contractors for testing, documentation, and new development <strong>of</strong> GMATnavigation functionality.III.Period <strong>of</strong> PerformanceThe period <strong>of</strong> performance for this task is from May 01, 2013 through Nov. 01, 2013.IV.<strong>Sub</strong>task Descriptions<strong>Sub</strong>-<strong>Task</strong>: <strong>Tracking</strong> <strong>Data</strong> <strong>Reader</strong>/<strong>Writer</strong><strong>Task</strong> Scope: The contractor shall(1) Modify FDF tracking data processors to write out CCSDS TDM formatted data files givenraw TRK-2-34 Sequential Range, and Doppler <strong>Data</strong>, and selected UTDF data types.(2) Write a CCSDS TDM file reader in C++ and integrate the file reader into existing trackingdata and measure models in GMAT.Staffing Requirements: This task shall be staffed with individuals knowledgeable intracking data formats, tracking data pre-processing, and s<strong>of</strong>tware systems used by the FDFto pre-process and reformat tracking data. The task shall also be staffed with s<strong>of</strong>twareengineers for integration <strong>of</strong> file reader into GMAT.Assumptions: The contractor shall make maximum use <strong>of</strong> existing tracking dataprocessing tools to repackage tracking data in CCSDS consistent formats. When TDM
formats for specific data types are not fully specified, the contractor shall extend theformats using established CCSDS and FDF standards.<strong>Sub</strong>-<strong>Task</strong>: Navigation Component Development<strong>Task</strong> Scope: The contractor shall resume development <strong>of</strong> GMAT navigation components bydocumenting, refactoring, and testing selected navigation components developed, but notcompleted, under previous development efforts. The contractor shall also implement newfunctionality identified below. Upon completion <strong>of</strong> this effort, the selected navigationcomponents will be fully documented, tested, and free <strong>of</strong> critical bugs.The primary activities are:(1) Review and document the status <strong>of</strong> the estimation subsystem and providerecommendations for refactoring and modularization to support extensibility for newestimators, data types, and solve-for parameters.(2) Perform selected, high priority re-factorizations <strong>of</strong> GMAT navigation components. . Thecontractor shall prioritize re-factorizations to support extensibility in the areas <strong>of</strong> newmeasurement data types, , new solve-for parameters.(3) Perform V&V, update documentation, test, and resolve critical defects for selected,existing navigation subsystem components.Batch least squares estimatorMeasurement simulatorSensorso Transmittero Transpondero Antennao Receiver<strong>Tracking</strong> Systems/Measurement Modelso USN• Two-way rangeo TDRSS• 4-way range(4) Implement at minimum one <strong>of</strong> the following new tracking data models by direction <strong>of</strong>the task monitorTDRSS differenced one-way DopplerTDRSS five-leg, two-way DopplerTDRSS two-leg two-way tone range measurements from the TT&C linkProcess Requirements: The contractor shall use standard GMAT processes fordocumentation, test procedures, issue tracking, and regression testing.Staffing Requirements: This task shall be staffed with a team composed <strong>of</strong> senior s<strong>of</strong>twareengineers trained in C++ and s<strong>of</strong>tware engineering practices, advanced working knowledgein GMAT’s design and implementation, s<strong>of</strong>tware testers, and technical writers for end-userdocumentation.
Assumptions: GUI interfaces for navigation components will be removed from GMAT andnavigation functionality will only available via the script interface for this effort.V. Deliverable Items and SchedulesAt a minimum, the contractor shall deliver the items specified below. The contractor shallalso provide interim deliverables as required by the TM.Note: Because the re-factorization plan that will determine what re-factorizations should beperformed is itself a deliverable, changes to the contents (but not scope) <strong>of</strong> the refactorizationdeliverables may occur by the TM. In short, this is a best guess.DeliverableDue DateRe-factorization plan and recommendations July 15, 2013Re-factorization milestone 1: architectural components/MeasurementsRe-factorization milestone 2: Estimators/solve-forparametersAug. 15, 2013Oct. 15, 2013V&V and docs for sensor components July 15, 2013V&V and docs tracking system components July 15, 2013V&V and docs for estimator and simulator components Aug. 30, 2013CCSDS TDM <strong>Reader</strong> (not integrated but unit tested) July 30, 2013.CCSDS TDM <strong>Writer</strong> Sept. 1, 2013CCSDS TDM <strong>Reader</strong> (integrated and system tested) Nov. 1, 2013TDRSS <strong>Data</strong> Type 1 July 30, 2013TDRSS <strong>Data</strong> Type 2 Nov. 1, 2013Critical bug resolutions Nov. 1, 2013Status reportingWeekly via meetingminutes and issuetrackerVI.Management Approacha. Staff Allocation, Expertise, and Skill MixThe contractor shall staff this effort with a team <strong>of</strong> individuals with the following skills: Senior s<strong>of</strong>tware engineer with extensive C++ development experience. Engineer with background in tracking data formats and systems in use in the FDF S<strong>of</strong>tware engineer for implementing selected components. Engineer for documentation and testing <strong>of</strong> selected components
Tech writer for writing the user guide for selected components.The contractor shall designate one individual as the single point <strong>of</strong> contact for coordination<strong>of</strong> the contractor's efforts on the task with the Government's <strong>Task</strong> Monitor (TM). Withconcurrence from the TM, the contractor may augment its skill mix with journeyman andapprentice-level staff as appropriate to accomplish certain specific objectives <strong>of</strong> particularwork items, and/or to assist with overall task coordination and management activities.As directed by the TM, the contractor shall maintain separate cost accounts for subtasksand/or subtask work items funded from different Government accounting codes.b. Configuration ManagementThe contractor shall use existing repositories on SourceForge and Jazz server and existingprocesses for maintenance <strong>of</strong> current and historical versions <strong>of</strong> all products resulting fromthis task.c. FacilitiesAppropriate Information Technology devices to support the analyses, specificationdevelopment, and report development are required. It shall be the contractor’sresponsibility to provide and set up local workstations and network connections at thecontractor’s <strong>of</strong>f-site facilities as required, and to install any required tools and utilities onthe contractor’s equipment.d. Risk Management and Best PracticesThe contractor shall manage risk using the JIRA project management tool where all GMATrisks are reported and monitored. The contractor shall identify issues well in advance <strong>of</strong>negative consequences, recommending corrective action to the TM, and implementingcorrective actions with the compliance <strong>of</strong> the TM.e. Performance MetricsThe TM will evaluate the work performed for this task based on technical merit. The TM willutilize detailed performance metrics that reflect the contractor’s performance in meetingresearch analysis, specific task requirements, deliverables and delivery schedule, and thecontractor’s cost. The TM's technical evaluation <strong>of</strong> the task performance will be a subjectivecombination <strong>of</strong> performance metrics, technical quality <strong>of</strong> deliverables, cost control,significant events, innovations and meeting requirements set forth in the SOW.The primary performance tracking mechanism for this task shall be GMAT’s JIRA issuetracking system.f. Government Furnished Facilities, Equipment, S<strong>of</strong>tware, and Other ResourcesThe Government will provide account and passwords to government-furnishedworkstations where existing versions <strong>of</strong> various relevant s<strong>of</strong>tware packages shall bemaintained. The government shall also supply a single license for the Clarizen projectmanagement s<strong>of</strong>tware. It shall be the contractor’s responsibility to complete any GSFCrequired security-related training courses.g. Method <strong>of</strong> DeliveryAll documentation, specifications, data, and source code related to improvements and/orenhancements, even minor enhancements, shall not be released to the public and shall be
delivered directly to repositories and storage locations behind the GSFC firewall. Thecurrent delivery locations behind the GSFC firewall are SVN repositories on the JAZZ serverand directories on the GSFC mesa-file server and the AETD Wiki. These locations and toolsmay change, but new locations and tools shall remain behind the GSFC firewall and thecontractor shall deliver data to those storage locations.All status reports, including meeting minutes and ticket system updates shall occur via theproject’s public documentation mechanisms (currently a Wiki, a JIRA ticket system, andGoogle docs). Deliverables related to s<strong>of</strong>tware approved for public release by the GSFCS<strong>of</strong>tware Release Authority, that clarify or further document the contents <strong>of</strong> GMAT R2013aor previous releases, shall be made to the project’s public interfaces (currently SourceForge,a Wiki, a Forum, and Google Docs). Those deliverables include updates and clarifications todesign documentation, functional and interface specifications, plans and procedures, testsystem updates, bug fixes, user documentation, and compiler documentation.VII.TravelThis SOW requires two, one-week onsite technical interchange meetings.VIII. <strong>Work</strong> LocationThis work shall be performed primarily at the contractor’s facility, but the contractor maybe required to perform some work at the Goddard Space Flight Center.IX.Reporting RequirementsThe contractor shall report status on a weekly basis via existing status reportingmechanism on the GMAT forum. Reports shall include informal presentation <strong>of</strong> interimresults, status <strong>of</strong> development activities, and status <strong>of</strong> risks, issues, and other action items.The contractor shall also support the TM in the preparation <strong>of</strong> status reviews for internaland external funding agencies. The contractor shall comply with any and all additionalrequests for status meetings and reports. The contractor shall deliver all documents bycommitting them to the appropriate location in either the SourceForge or Jazz SVNrepositories. All bugs and s<strong>of</strong>tware defects found during testing will be reported in theproject’s JIRA database.X. Security RequirementsThis task shall comply with IT security requirements as documented in the FDF IT securityplan for all systems located in the FDF. FDF systems shall be maintained under the FDFSustaining Engineering <strong>Task</strong>. Systems located outside <strong>of</strong> the FDF shall be covered under theCode 590 security plan and the Code 590 sustaining engineering support or the contractorsustaining engineering support depending on system location.
XI.RightsThis SOW shall adhere to the RIGHTS IN DATA – special works (FAR 52.227-17) as modifiedby NFS 1852.227-17.XII.None.References
Change language