1 / 6

Standardizing Operational Procedures for DCL Trials

This document aims to standardize DCL trial operational procedures for consistency and efficiency. Assistance is required to address current issues, establish notification processes, and finalize missing procedures. The sections cover introduction, trials operations, outages, certification, configuration management, data collection, and glossary.

leona
Download Presentation

Standardizing Operational Procedures for DCL Trials

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trials Operations Procedures Document Initial DRAFT Review 6/12/13

  2. T.O.P Purpose • This document was created to standardize and have a common place to reference all Operational Procedures that are used in the DCL trials. • Currently there are a mix of procedure out there. Some already well documented and some not so well documented or non existent. • Goal is to get agreement on the procedures that are really being used and make sure they are: • Documented • Easy to find • Repeatable • Managed

  3. What we need from you • Help in resolving current Questions/Issues that are holding up procedures. • Notification process for Major Issues that cause Trial Shutdown • NOTAMs and Advisory was suggested • Missing Software Patch Testing procedures for: • WJHTC Patch Testing (Call into Pete) • Site Patch Functional and Interoperability Testing • Site Acceptance Testing • As Built diagrams and CM process • Do diagrams exist or do we have to crate from scratch? • Flight Coordination • Need final agreement on how flights are coordinated for Limited and Full Trials. • Trial Metrics • Need to agree on what metrics we need to collect and the procedures to do so.

  4. What we need from you (Cont.) • Any procedures missing? • What else should be in document? Some suggestions to date are: • PTR procedures, … • Current procedures correct? • Walk through review

  5. Document Overview • Currently there are 8 section to this document: • Introduction: • Mostly copied from the System Integration Document with minor updates for the basic trials introduction. • Trials Operations: • This section is broken out into limited and full trials. It explains the difference between the two and how the flight coordination will take place. • Scheduled Outages: • Provides the detailed procedures on how to handle schedule outages currently including DTAP Nav DB updates and Software Patch Updates. • Un-Scheduled Outages: • Contains the detailed process on how to handle trial issues and resolve them. Process based off of Flow chart that was presented in last DCIT meeting.

  6. Document Overview (Cont.) • DTAP Certification • Contains the detailed procedures on how to recertify and in what cases to recertify. • Configuration Management • Includes procedure on how to navigate the Harris CM tool, SharePoint, and will go into a CM process for both Hardware and Software. • Trials Data Collection • Intended to include procedures on how to collect data for the production of metrics for the trials. • Glossary • Definition of terms used in the DCL Trials. Copied from The System Integration Document.

More Related