Attch J-10_TOR Format.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

AEGIS TEST OBSERVATION REPORT (TOR)

Form Version 3.5 Originator Contact Information Originator Full Name Organization E-mail Telephone # JIRA Reporter Email Test Event Information Ship / Hull Project Test Event Date Discovered When Discovered TOR Category Priority Probability EOC Value Safety Code Primary Warfare Secondary Warfare Issue Type Issue Detail Work Center Computer Program ID DX/RX Media Number

HH:MM:SS

Console Submode Human System Integration

JSN

System Element ElementSubsystem Cause of Failure Equip. Status TOR Description Summary (Short Title) Description (Observation) Discrepancy Location Operational Impact Corrective Action & Status (Recommendation) Parts Ordered Failed Part S/N Part Number Nomenclature Quantity Failed Part S/N Part Number Nomenclature Quantity Resolution of Issue Names E-mail Agency Telephone # Closure Mechanism TOR Cross Reference Date Resolved SF Man Hour Expended Deferral Reason Type Avail

AMT ONLY

Names Signature Date

INITIATOR

ELEMENT ENGINEER

NSWCDD REP

AMTCRB CHAIRMAN

For Official Use Only/Controlled Unclassified Information (FOUO/CUI) For Official Use Only/Controlled Unclassified Information (FOUO/CUI)

AEGIS TOR FORM INSTRUCTIONS

Originator must complete all required fields (i.e. Underlined Blocks). Complete Originator Information (As Applicable) with information if known. Include no classified information on this form. Classified information should be documented and submitted separately in accordance with applicable security regulations and marked with the applicable originator log number.

1. JIRA Key: Enter JIRA Key if known. Otherwise leave blank

2. REF #: Enter a local or alternate reference number to help you identify or search for this TOR.

3. Ship/Hull NO Select the ship class and hull number, or the site where the problem was observed;

4. RECOMMENDED/ORIGINATOR PRIORITY The operational priority which the originator recommends: (select one) (1): Prevents the accomplishment of an essential operational capability where no operationally suitable workaround exists, AND any of the following is met: Problem prevents the accomplishment of an ownship or force-level operational or mission critical / essential function under any realistic threat conditions (threat, environment, EA modes, current theater architecture, etc.), OR Problem prevents ship operations (e.g. communications, networks, ISR, air control)from being executed properly without operational restrictions, OR Problem can directly or indirectly result in a catastrophic safety severity level issue as defined in MIL-STD-882E, Appendix A OR Problem prevents meeting a Key Performance Parameter and/or high level specification (e.g., SSTAMDO, ORD, TRL, A-spec) OR Problem that negatively impacts information systems security posture and results in the loss of authority to operate.

(2): 2: Adversely affects the accomplishment of an essential capability where no operationally suitable workaround exists, AND any of the following is met: Problem degrades/adversely affects the accomplishment of an ownship or force-level operational or mission critical / essential function under any realistic threat conditions (threat type, environment, EA modes, current theater communications architectures, etc.), OR Problem degrades/adversely affects ship operations (e.g. communications, networks, ISR, air control) from being executed properly without operational restrictions, OR Problem results in a loss of system redundancy OR Problem can directly or indirectly result in a critical safety severity level issue as defined in MIL-STD-882E, Appendix A OR Problem results in not meeting a Critical Technical Parameter that adversely affects performance of the system, OR Problem degrades/adversely affects information systems security posture and results in a reduced set of capabilities;

(3): Adversely affects the accomplishment of an essential capability where an operationally suitable workaround exists, AND any of the following is met: Problem prevents or degrades/adversely affects the accomplishment of an ownship or force-level operational or mission critical / essential function under any realistic threat conditions (threat, environment, EA modes, current theater architectures, etc.), OR Problem prevents or degrades/adversely affects ship operations (e.g. communications, networks, ISR, air control) from being executed properly without operational restrictions, and for which an operationally suitable workaround exists to achieve Key Performance Parameters and/or high level specification (e.g., SSTAMDO, ORD, TRL, A-spec)and ability to perform mission, OR Problem that degrades/adversely affects information systems security posture but allows an interim authority to operate, OR Problem can directly or indirectly result in a marginal safety severity level issue as defined in MIL-STD-882E, Appendix A OR Problem is a significant impact to an operator's situational awareness or ability to conduct operations (e.g., increases workload or creates distractions to the level that impacts system performance) but does not prevent the accomplishment of an ownship or force-level operational or mission critical / essential function under any realistic threat conditions (threat, environment, EA modes, current theater architecture, etc.).

(4): Problem results in user/operator inconvenience or annoyance and does not affect required operational or mission essential capability,OR Problem results in a minor system degradation that does not prevent ownship or force-level accomplishment of an operational or mission critical/essential function and/or ship operations (e.g. communications, networks, ISR, air control), OR Problem is an operator inconvenience or annoyance but does not degrade operator's situational awareness or ability to conduct operations, OR Problem can directly or indirectly result in a negligible safety severity level issue as defined in MIL-STD-882E, Appendix A;

(5): An error that does not affect the system or operator from accomplishing a function in accordance with system requirements OR a specification error that does not affect the software OR an enhancement to a function is being requested OR an error that does not affect warfare systems operations (e.g. communications, networks, ISR, air control) and mission capability requirements can still be met.

5. PROBABILITY OF OCCURRENCE The probability of occurrence for a TOR having a tactical impact:

A. Issue expected to happen consistently in an operational environment during conditions in which it could occur B. Issue occurs frequently in an operational environment during conditions in which it could occur C. Issue occurs occasionally in an operational environment during conditions in which it could occur D. Issue occurs rarely and is unlikely to occur in an operational environment E. Issue has been observed once in testing and cannot be reproduced and is extremely unlikely to occur or issue has only been reproduced in a test environment and is not expected to be seen during ship operations.

IMPACT GUIDANCE for:

Consistently - Every time or almost every time (more than 80%) Frequently - More than 40% and less than 80% of the time Occasionally - More than 10% and less than 40% of the time Rarely - Less than 10% of the time

6. EOC VALUE

1.0 Fully Operable

0.9 Fully Operable with cosmetic discrepancies

0.8 Fully Operable with no performance impacting discrepancies

0.7 Operable with minor discrepancies that do not impact performance

0.6 Operable with discrepancies that could potentially impact performance in the future; no restrictions

0.5 Operable with discrepancies that effect performance; no restrictions on operation

0.4 Restricted operation; significant discrepancies

0.3 Severely degraded with major operational restrictions

0.2 Repair before operation

0.1 Should not be operated/Battleshort

0.0 Totally inoperative

7. SAFETY CODE

(Blank) = No Safety Hazard X = Safety Hazard

1. Critical Safety or Health Deficiency

2. Serious Safety or Health Deficiency

3. Moderate Safety or Health Deficiency

4. Minor Safety or Health Deficiency

5. Negligible Safety or Health Deficiency

8. PROJECT Select from drop down menu. This identifies the AEGIS team that discovered the issue;

9. TEST EVENT Enter the test event that was occurring when issue was discovered. Include Test procedure number if applicable;

10. DATE DISCOVERED The date the issue occurred on the ship;

11. DATE RESOLVED The date the TOR was closed by resolution of Issue and Closure Mechanism section;

12. PRIMARY WARFARE SYSTEM Select a Primary warfare area (Required) and a Secondary warfare area, (Optional) if applicable;

13. SECONDARY WARFARE SYSTEM Select one to identify a secondary warfare area, enter N/A if not applicable;

14. ISSUE TYPE Select one: Engineering Documentation, Integrated Logistic Support, Hardware, Computer Program

15. ISSUE DETAIL CSSOSS/EOSS;

16. WORK CENTER PHD use only;

17. JSN PHD use only;

18. HUMAN SYSTEM INTEGRATION Select one: OSHA, Habitability, Human Factor, Manpower, Personnel, Survivability, Training;

19. DX/DR Media Number enter data recording media number;

20. HH:MM:SS enter the GMT time the issue occurred;

21. Console Submode Select the console name;

22. BASELINE Identify the baseline installed on system at time of issue discovery;

23. SYSTEM ELEMENT Select the system element the TOR is written against;

24. SUMMARY Title to be entered into STARSYS for TOR. Limit the short title to 35 characters;

25. DESCRIPTION (UNCLASSIFIED only) brief description of the problem observed and the conditions under which the problem occurred.

26. LOCATION Please use compartment location for this field. IE: 01-130-0-C

27. SYSTEM IMPACT Include sufficient information in this block to evaluate operational performance and impacts. Include operator impact and workaround if known;

28. STATUS Block available for hardware disposition status and any CP related status (free form space)

29. PARTS ORDERED Enter part number, Nomenclature and quantity

30. RESOLUTION OF ISSUE Provide the agency and POC identify info that is closing this issue;

31. CLOSURE MECHANISM Select the method and artifact that will close this issue

32. TOR CROSS REFERENCE Enter the number the issue is being tracked in STARSYS/ACCESS ie CPCR, IR, OECR, SPR, SWCR, etc…

How to export data from multiple TOR forms into one MS Excel sheet.

1. Open any TOR form with Adobe Acrobat Pro. (this procedure will not work with Adobe Acrobat Reader)

2. Click on View > Tools > Forms > More Form Options > Manage Form Data >Merge data files into Spreadsheet

3. Click Add Files in the pop-up dialog box.

4. Select one or more TOR form(s) to be exported. Click Open.

5. Click Export.

6. Name file and Save to desired location

9.0.0.2.20120627.2.874785 Originator First Name is a required field.

Organization is a required field.

Originator's E-mail is a required field.

Validation failed.

Ship/Hull is a required field.

"Project" is a required field.

Date Discovered is a required field.

Ship/Hull is a required field.

Priority is a required field.

Probability is a required field.

EOC Value is a required field.

Issue Type is a required field.

Issue Detail is a required field.

System Element is a required field.

System Element is a required field.

System Element is a required field.

Summary is a required field.

Description is a required field.

System Impact is a required field.

Ship/Hull is a required field.