Attachment 42 - TE 1.3 CIRS Manual.pdf

PDF 2 MB Posted

Attached to
Logistics Modernization Integration Support (LMIS) for Defense Logistics Agency (DLA) Distribution Federal contract opportunity
Solicitation number
SP3300-20-R-5002
Issued by
Defense Logistics Agency Distribution

About this file

This document provides details regarding a federal solicitation for logistics modernization integration support services. The Defense Logistics Agency Distribution is seeking proposals to provide Logistics Modernization Integration Support (LMIS) services to support its distribution operations. Offerors should have experience providing logistics IT services, data analytics, and business process engineering. Proposals are due by February 15, 2020, with work expected to begin June 2020 under a single-award IDIQ contract with one base year and four option years. Pricing will be on a firm-fixed-price or time-and-materials basis for individual task orders. The solicitation targets small businesses, with a portion of the contract set aside for 8(a) program participants.

View the file

Other files for this federal contract opportunity

Other files attached to Logistics Modernization Integration Support (LMIS) for Defense Logistics Agency (DLA) Distribution, newest first.
File Type Posted
LMIS RFP SP3300-20-R-5002 Amendment 0010.pdf PDF
RFP SP3300-20-5002 Rev. 4 (03.17.20).pdf PDF
LMIS RFP Questions and Responses Version 4.xlsx XLSX spreadsheet
LMIS RFP Questions and Responses Version 3.xlsx XLSX spreadsheet
RFP SP3300-20-5002 Rev. 3 (02.28.20).pdf PDF
RFP SP3300-20-5002 Rev. 2 (02.19.20).pdf PDF
LMIS RFP SP3300-20-R-5002 Amendment 0006.pdf PDF
RFP SP3300-20-5002 Rev. 2 (02.19.20) (Tracked Changes).docx DOCX document
Attachment 19 - Davis-Bacon Act Wage Determination.pdf PDF
Attachment 43 - TE 1.4 CIRS Tutorial.pdf PDF
Attachment 44 - TE 1.5 Contractor Investigative Request Sep 2016.pdf PDF
Attachment 1 - Basic IDIQ PWS Rev. 1 (01.16.20).pdf PDF
Attachment 8 - Pool 1 Continuation of Supplies Services Instructions Rev. 1 (01.17.20).pdf PDF
RFP SP3300-20-R-5002 Amendment 0003.pdf PDF
LMIS Pre-Proposal Conference Questions & Answers.pdf PDF
LMIS Pre-Proposal Conference Sign-In Sheet (Day 1).pdf PDF
LMIS Pre-Proposal Conference Agenda.pdf PDF
RFP SP3300-20-R-5002 Amendment 0001.pdf PDF
LMIS Pre-Proposal Conference Instructions.pdf PDF
Attachment 13 - Implementation Project Schedule.pdf PDF
Attachment 32 - Pool 2 Continuation of Supplies Services Instructions.pdf PDF
Attachment 2 - Past Performance Questionnaire.docx DOCX document
Attachment 6 - CDRLs (CDRL A002 - Small Business Participation Biannual Progress Report).pdf PDF
Attachment 1 - Basic IDIQ PWS.pdf PDF
Attachment 3 - Subcontracting Plan Template -Includes Elements 1-15.docx DOCX document
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00008 GFE & GFP Report Requirements).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00013 Certificate of Compliance).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMISC-00002 Commercial Manual).pdf PDF
Attachment 8 - Pool 1 Continuation of Supplies Services Instructions.pdf PDF
Attachment 34 - AMHE Drawings (NCDP2_17_01_01_01A_DE_R-.DWG).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMISC-00003 Warranty Information and Technical Representatives List).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMISC-00004 Training Baseline (TB) and Training Materials).pdf PDF
Attachment 6 - CDRLs (CDRL A001 - Monthly Contractor Employee CAC Report).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00010 DoDM 8570 Report Requirements).pdf PDF
Attachment 10 - EDC Modernization Compliance Checklist.xlsx XLSX spreadsheet
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00007 Affirmation of Coding Integrity and Unused Software Services).pdf PDF
Attachment 34 - AMHE Drawings (NCDP2_17_01_01_01A_EX_R-.DWG).pdf PDF
Attachment 7 - Schedule Page (Pool 1).xlsx XLSX spreadsheet
Attachment 36 - AMHE DIDs (DI-DLAMISC-00001 Drawings, Engineering, and Associated Lists).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00001 Hardware Inventory Requirements).pdf PDF
Attachment 34 -AMHE Drawings (NCDP2_17_01_01_01A_PR_R-.DWG).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00012 Project Management Plan).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00014 In-Progress Review (IPR) and Report Requirements).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMISC-00005 Power Requirements).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00005 DoD Architecture Framework Documentation).pdf PDF
Attachment 33 - AMHE SOW.pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00004 Software - Firmware Access Controls, User Roles, and Data Types).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00011 Integrated Master Schedule).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMISC-00006 Design Data and Calculations).pdf PDF
Attachment 36 - AMHE DIDs (DI-DLAMGMT-00009 Physical and Cybersecurity Features of End Devices Provided).pdf PDF
Show all 50

Logistics Modernization Integration Support (LMIS) for Defense Logistics Agency (DLA) Distribution has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Revised 01/12/2018 1

ESAMS Help Desk: (865) 288-7898

Fax: (865) 288-7896 www.hgwllc.com

Contractor Incident Reporting System (CIRS)

User’s Manual

Revised 01/12/2018 2

Finding CIRS

Access Favorite Applications

CIRS – Reporting an Incident Generating the Incident Record

Section 1 – Contract Section 2 – Contractor Contact Information

Finding the Incident Record

Working the Incident Record Incident Information Add an Injury Illness Add a Property Damage

Administrating the Submitted Incident Record

Reviewing the Incident Record Accepting/Declining the Incident Record

CIRS – Process Flow Diagram

CIRS Email Notification Events Links of Interest

Generate Incident

Man Hours Search for Incident(s)

My Self Entries Requested Incidents Active Incidents

Advanced Options Delete an Incident

CIRS Reports Favorite Reports

Dart Rate by UIC Report Dart Rate by CAGE Code Report CIRS Man Hours

CIRS Master Injury Report CIRS Master Near Miss Report

CIRS Master Property Damage Report CIRS Master Summary Report CIRS Status Report

CIRS Analysis Report CIRS Trend

Revised 01/12/2018 3

Contractor Incident Reporting System (CIRS)

The Contractor Incident Reporting System (CIRS) is used to record information about Injury/Illness events

(Mishaps and Property Damage) for contractor personnel that are not listed in the ESAMS database.

Authorized users (CIRS administrators) can document information on these events, such as personnel involved, nature of the mishap, and work days lost.

Finding CIRS

CIRS Administrators can access the CIRS Application from the following link:

“Contractor Incident Reporting (CIRS)” under “Applications” on the navigation bar at the top of the

ESAMS page

Access

CIRS Administrator (Create/Edit/Reports) - has access, within their scope, to view and edit incident records within their scope and to view CIRS reports

CIRS Administrator (Create/Edit/Approve/Reports) - has access, within their scope, to view and edit incident records and to view CIRS reports. Also has access to Approve completed CIRS records.

CIRS Administrator (Reports/Notification) - has access only to view CIRS reports for incidents within their scope.

Revised 01/12/2018 4

Favorite Applications

At the top of the ESAMS Main page, the “Applications” link contains several links for administrators.

Clicking on the “Applications” link expands the area to show all links available to the administrator.

Administrators can note specific application links in the “Applications” area as “Favorites”. These links will be displayed in the “Favorite Applications” area above the normal application links, allowing the administrator to quickly access the application link(s). (example shown below)

1. Click on the “Applications” link.

2. Click on the star icon next to an application link.

3. The application link will now also be displayed in the “Favorite Applications” section.

4. Click on the star icon again or the “X” next to the application link to remove it from the “Favorite

Applications” section.

Revised 01/12/2018 5

CIRS – Reporting an Incident

Generating the Incident Record

1. The CIRS Administrator enters the ESAMS website and accesses the CIRS Application by clicking on the “Contractor Incident Reporting (CIRS)” link.

2. The CIRS Administrator clicks the “Generate Incident” link.

Revised 01/12/2018 6

3. The CIRS Administrator must enter the “Contract” and “Contractor Contact Information” in Section

1 and Section 2 of the CIRS form.

a. Note: Once a contract period has expired, administrators have 30 days to file a

CIRS mishap report. After the 30 days have passed, the contract will no longer be available for selection.

Revised 01/12/2018 7

Section 1 – Contract

b. Prime Contractor – The name of the contractor company by which the involved person is employed. Clicking on the “Search by Prime Contractor” link opens a new window in which the administrator may search and select the Prime Contractor’s name. Entering all or part of the name in the “Prime Contractor” field and clicking the Search icon will bring up a list of all

Prime Contractor names in the system that match the entered information. Clicking on a

Prime Contractor name will populate the name in the field.

c. CAGE Code – The Commercial And Government Entity (CAGE) Code for the contract under which the involved person is employed. These CAGE Codes are associated with the Prime

Contractor selected.

i. If no Prime Contractor has been chosen, the administrator may type the CAGE Code directly into the search field and click the search icon to find the entered code. Note: The

CAGE Code must be entered exactly as listed in the system or it will not be found.

Revised 01/12/2018 8

ii. If a Prime Contractor was selected, the field will change to a drop-down box. Click on the drop-down box to display the CAGE Codes associated with the selected Prime

Contractor. Clicking on a CAGE Code will populate the code in the field. Note: Some

Prime Contractors have only one associated CAGE Code. In these cases, the

CAGE Code will automatically be populated in the field.

d. Contract # – The specific contract number under which the involved person is employed.

These contract numbers are associated with the Prime Contractors and CAGE Codes.

i. If no Prime Contractor/CAGE Code has been chosen, the administrator may type the

Contract # directly into the search field and click the search icon to find the entered code.

Note: The Contract # must be entered exactly as listed in the system or it will not be found.

ii. If a Prime Contractor/CAGE Code was selected, the field will change to a drop-down box.

Click on the drop-down box to display the Contract #’s associated with the selected Prime

Contractor. Clicking on a Contract # will populate the code in the field. Note: Some

Prime Contractors/ CAGE Codes have only one associated Contract #. In these cases, the Contract # will automatically be populated in the field.

Revised 01/12/2018 9

e. Command – The command at which the involved person is employed. Commands are associated with specific Prime Contractors, CAGE Codes and Contract #’s.

i. If no Prime Contractor/CAGE Code/Contract # has been chosen, the administrator may click on the black popup triangle to open a new window in which the administrator must select the Command. Administrators who can view multiple commands will be provided with a search window in which they can enter information and click the “Search” button to find the desired command. Clicking on the command name enters the command into the field. Once the command is chosen, the administrator must then use the drop-down boxes to select the Prime Contractor and other fields.

Revised 01/12/2018 10

ii. If a Prime Contractor/CAGE Code/Contract # was selected, the field will change to a drop-down box. Click on the drop-down box to display the Commands associated with the selected Prime Contractor/CAGE Code/Contract #. Clicking on a Command will populate the code in the field. Note: Some Prime Contractors/CAGE Codes/ Contract

#’s have only one associated Command. In these cases, the Command will automatically be populated in the field.

f. Task Order # – The specific Task Order number within the contract that the employee was tasked with at the time of the incident. These Task Order numbers are determined by the Prime Contractor/CAGE Code/Contract # /Command selected (above). Click on the drop-down box to display available selections. Clicking on a Task Order number will populate the name in the field. Note: Some Prime Contractor/CAGE Code/Contract

#/Commands have only one associated Task Order number. In these cases, the

Task Order number will automatically be populated in the field.

g. These aren’t the Contractors/Contracts you’re looking for… – The administrator can click this link if the Prime Contractor, CAGE Code, Contract #, Command or Task Order cannot be found. The link provides contact information for CIRS Administrators who can authorize the addition of such information to the CIRS database.

Revised 01/12/2018 11

Section 2 – Contractor Contact Information

h. First Name – The first name of the contractor who contacted the CIRS Administrator. Type the name directly into the field.

i. Last Name – The last name of the contractor who contacted the CIRS Administrator. Type the name directly into the field.

j. Phone # – A phone number contact for the contractor who contacted the CIRS Administrator.

Type the number directly into the field. The type of contact number can be chosen by clicking on the drop-down box to the left of the field and selecting “Work”, “Cell”, or “Home”. Clicking on the “Add Additional” link creates extra fields in which the administrator can add additional contact numbers.

k. Is Manual Entry by CIRS Administrator? – The administrator can check this box to note that the CIRS record will be worked by the administrator. (see below).

l. Email – The email address of the CIRS Administrator. Type the address directly into the field.

m. Confirm Email – The email address of the CIRS Administrator, noted again to ensure that the address is correct. Type the address directly into the field.

Revised 01/12/2018 12

n. Date Notified – The date that the CIRS Administrator was notified of the incident. Clicking on the field displays a “Calendar” window in which the administrator selects the date.

4. Once Section 1 and Section 2 are filled out, the administrator may complete the incident generation process by clicking on the “Generate Incident and Begin Work” button in the lower left corner of the form. Clicking the button will generate the CIRS record so that the administrator can access the record and begin entering the incident information.

Revised 01/12/2018 13

5. The “Reset Form” button located in the top right corner of the form can be clicked at any time before the incident generation process is completed. This button will remove information from all fields, allowing the administrator to start a new form without generating an incident record.

Finding the Incident Record

1. Once the CIRS Administrator has completed the generation process and clicked the “Generate

Incident and Begin Work” button, the incident record will be displayed, and the CIRS

Administrator will be able to enter the incident information.

2. CIRS Administrators may view and edit any incident record in their scope that has not yet been completed by clicking on the “CIRS Main” link at the top left of the page and either selecting a record from their hotlist or using the “Search for Incident(s)” link (see below).

Working the Incident Record

Incident Information

Note – All fields noted by a red asterisk (*) on the form are required fields that must be filled before the record can be completed.

1. Section 1 - Contract Information

a. This information has already been entered by the CIRS Administrator in the generation process and is provided here for informational purposes.

Revised 01/12/2018 14

2. Section 2 – Incident Type

a. The user must select the type of incident by checking the box next to the most appropriate selection. The user may click on the “Incident Type Description” link to view a list of descriptions for each Incident Type. Note: Choosing the “Industrial” selection opens a sub-section in which the specific of Industrial Incident must be selected.

3. Section 3 – General Information

a. Date of Accident – The date on which the incident occurred. Select the date by clicking on the field and using the Calendar popup.

b. Time of Accident – The time at which the incident occurred, to the closest 15 minute increment. Select the time by clicking on the field and using the Time popup.

c. Initial Description – A factual description of the incident as known by the user. Note:

No personal descriptions (such as names) or opinions should be entered.

d. Exact Location of Incident – The specific area at which the incident occurred.

(Example – Street side of parking lot of Building 120)

e. Hazardous Material Involved? – The user should note whether or not hazardous material was involved with the incident. If “Yes” is selected, the user must enter an explanation of the specific Hazardous Material(s).

f. Activity at Time of Accident – A description of what actions the involved person(s) was doing at the time of the incident, typed directly into the open text field.

g. Personal Protective Equipment – The user should note whether or not Personal

Protective Equipment (PPE) was present and used during the incident by clicking on the drop-down box and choosing the most appropriate selection. If the user selects

“List Types used:”, a new open text field will be displayed in which the user can enter the types of PPE used.

h. Who Provided Cleanup – Using the drop-down box, the user should note who provided cleanup services at the site of the incident.

Revised 01/12/2018 15

4. Section 4 – Fully Explain What Allowed or Caused the Accident

a. Direct Cause –Any primary action, event, flaw, or force which caused the incident. This information can be typed directly into the open text field.

b. Indirect Cause – Any secondary action, event, flaw, or force which caused the incident.

This information can be typed directly into the open text field.

c. Actions Taken – A description of the actions being taken to prevent further similar incidents, typed directly into the “Description” field. The Begin Date and Estimated End

Date should be included in the description. If multiple actions are being taken, the user can click the “ADD Additional Action” link, which will provide an additional “Description” field. Actions Taken can be removed by clicking the “x” button next to each action. If the user wishes to change the text in the “Actions Taken” field, clicking the “Pencil” icon next to the field opens a new window in which the user may edit the text. Clicking the

“Confirm Edit” button saves these changes.

Revised 01/12/2018 16

5. Section 5 – Contributing Factors

a. Was Visibility Restricted? – The user should enter whether or not the involved person’s visibility was restricted. If “Yes” is selected, the user must enter the distance of restriction as a numerical value (5, 100, etc), then use the drop-down box to select the Unit of measure used (feet, yards, etc). Finally, the user must check the boxes next to each event or material that restricted visibility (Fog, Smoke, etc). The user should check as many events or materials that apply.

b. Lighting Conditions at Site of Mishap – The user should note whether the lighting conditions at the location of the incident was adequate or not, or if the information is unknown.

c. Noise Level a Factor? – The user should note whether or not the local noise level was a factor in the incident, or whether this information is unknown.

d. Carbon Monoxide (CO) was a factor – The user should note whether or not the presence of

Carbon Monoxide was a factor in the incident. If the user selects “Yes”, a new field will be displayed in which the user must enter the name of the manufacturer of the CO alarm at the location of the incident.

Revised 01/12/2018 17

6. Section 6 – Attached Documents

a. Attach File – If the user has a document/file (Word, Excel, pictures, etc) that needs to be associated with the incident record, the files can be attached by clicking on the “Attach File” button. This button opens a new window in which the user can search for the file within the user’s computer by clicking on the “Browse” button, selecting the file to be attached to the record, and finally attaching the file by clicking the “Submit” button. To remove a file, click on the “x” next to the file name on the record. Note: Only the user who attached the file can remove it.

7. Additional Info – This area contains information already entered by the CIRS Administrator during the generation process, or displayed automatically by the CIRS application.

a. Notified – The date upon which the CIRS Administrator was notified, and the person that notified the administrator.

b. Created – The date upon which a person began entering data about the incident, and the name of that person.

c. Submitted – The date upon which a person submitted the complete incident record, and the name of that person

d. Preparer Completing Report – The name of the person who filled out (or is currently filling out) the incident record.

e. Who Initiated Incident – The name and contact information of the CIRS Administrator that

Initiated the incident record.

f. Reporting Contractor – The name and contact information of the Reporting Contractor. Note:

Email will not be displayed if the record was filled by a CIRS Administrator.

g. New/Submitted/Reviewed/Accepted – The Status Bar at the bottom of the form displays the current status of the CIRS record, with the current status noted as a dark gray bubble with yellow text.

Revised 01/12/2018 18

Once all required information has been entered, the user must select either “Continue as an Incident” button or the “Submit Near Miss Incident” button.

8. Continue as an Incident– Once all of the required and relevant information specific to the incident has been entered, the user may click the “Continue as an Incident” button, located in the bottom left corner of the form. Clicking this button displays three options to the user:

a. Add an Injury Illness – The user should click this option to record the injury/illness information for any persons involved with the incident. When entering information for multiple persons involved with the same incident, each person should be input individually by clicking the “Add an Injury Illness” link after the previous person’s information was entered.

b. Add a Property Damage - The user should click this option to record the property damage information for any property or equipment damaged because of the incident (see below, pg

28).

c. …OOOPS I still need to make changes – This option allows the user to return to the involved person’s record and make any changes required before the record is completed.

Revised 01/12/2018 19

d. If the user has incorrectly entered information in any of the required fields, the form will not continue. Instead, a message will be displayed at the top of the page that states the number of errors on the page. Fields with incorrectly entered or missing data will be outlined in red and say “Required” next to the field. Once these fields are corrected, the “Continue” will work as stated above.

9. Submit Near Miss Incident - Once all of the required and relevant information specific to the incident has been entered, the user may click the “Submit Near Miss Incident” button, located in the bottom right corner of the form. Clicking this button displays a window asking if the user does want to submit the record as a Near Miss. Once “Yes” is selected, the record is submitted as a

Near Miss record. No Injury/Illness or Property Damage information can be added to the record.

Revised 01/12/2018 20

Add an Injury Illness

Note – All fields noted by a red asterisk (*) on the form are required fields that must be filled before the record can be completed.

1. Once the user has clicked the “Add an Injury Illness” link, a new page will be display in which the user must enter the injury or illness information for the person involved with the incident.

a. At the top of the form, the user will see multiple “tabs”. The first of these tabs is labeled

“Incident Information”, and clicking on this tab will return the user to the Incident Information portion of the record.

b. A new tab is created each time the user clicks the “Add an Injury Illness” link; these tabs are labeled as “Person 1”, “Person 2” and so on for each person entered into the record. Clicking on a “Person #” link will take the user to the injury/illness portion of the record for that person.

c. Delete this Record – Clicking this button removes the “Person #” portion from the incident record. All data entered for that Person # will be deleted. This should only be used to remove a record that was incorrectly associated with the incident.

2. Section 1 – Injured Data

a. Age – The age of the involved person

b. Gender – The gender of the involved person

c. Prime Contractor – The contractor for which the involved person works. This information is auto-populated by the application

d. Sub Contractor – The sub-contractor for which the involved person works (if any). This information must be typed into the open text field.

Revised 01/12/2018 21

3. Section 2 – General Information

a. Drug or Alcohol Involved? – The user should click on the drop-down box to note whether or not drugs and alcohol were involved with the incident.

b. Who provided first aid – The user should click on the drop-down box to note who provided first aid at the incident.

c. Was Ergonomics a factor? – The user should note whether or not ergonomic issues affected the incident.

4. Section 3 – Injury/Illness/Fatality Information

Revised 01/12/2018 22

a. Severity of Illness/Injury – The user must click the drop-down box and choose the selection that most closely describes the severity of the injury/illness.

b. Were there Days Lost? – The user should note whether or not the involved person lost days due to the injury/illness.

c. Were there Days Hospitalized? – The user should note whether or not the involved person was hospitalized due to the injury/illness.

d. Were there Days Restricted Duty? – The user should note whether or not the involved person was placed on restricted duties due to the injury/illness.

e. Part of Body Affected – Clicking on the black popup triangle opens a new window in which the user must select the body part involved in the injury/illness.

Revised 01/12/2018 23

f. Nature of Injury or Illness – Clicking on the black popup triangle opens a new window in which the user must select the manner in which the injury/illness occurred.

g. Event or Exposure – Clicking on the black popup triangle opens a new window in which the user must select the type of injury/illness.

h. Source of Injury or Illness – Clicking on the black popup triangle opens a new window in which the user must select the object or other source that caused the injury/illness.

Revised 01/12/2018 24

i. General Location Description – Clicking on the black popup triangle opens a new window in which the user must select the general area where the injury/illness occurred.

j. Injury Activity Code (PCN) – Clicking on the black popup triangle opens a new window in which the user must select the activity or job that the involved person was performing at the time of the injury/illness.

Revised 01/12/2018 25

5. Section 4 – License

a. Are appropriate License and Certification/Medical current? – The user should note whether or not the involved person’s appropriate License and Certification/Medical records are current.

b. Attach Image of License or Certification – Any documents or pictures regarding the involved person’s licenses or certifications can be attached in this section, in the same manner as on the “Incident Information” section (see above).

6. Section 5 – Training

a. Was all the contract-required training provided to the employee? – The user should note whether or not the involved person was provided with the training required of that person according to their contractual agreements. In the “Explain” open text field, the user may enter any comment to explain the required/received training.

7. Section 6 – Attached Documents

a. Any documents or pictures regarding the involved person’s injury/illness information can be attached in this section, in the same manner as on the “Incident Information” section (see above, pg 18).

Revised 01/12/2018 26

8. Submit Incident

a. Once all of the required and relevant information specific to the injury/illness of the involved person has been entered, the user must click the “Submit Incident” button, located in the bottom left corner of the form. Clicking this button displays four options to the user:

i. I am Finished – The user should click this option once all information regarding the incident has been entered. This will complete the entry of the record, moving the record to Submit status for review.

ii. Add an Injury Illness – The user should click this option to record the injury/illness information for any additional persons involved with the incident. A new record tab is created and the user must enter in the information as described above.

i. Add a Property Damage - The user should click this option to record the property damage information for any property or equipment damaged because of the incident (see below).

ii. …OOOPS I still need to make changes – This option allows the user to return to the involved person’s record and make any changes required before the record is completed.

b. If the user has incorrectly entered information in any of the required fields, the form will not continue or be submitted. Instead, a message will be displayed at the top of the page that states the number of errors on the page. Fields with incorrectly entered or missing data will be outlined in red. Once these fields are filled/corrected, the “Submit Incident” button will work as stated above.

Revised 01/12/2018 27

Add a Property Damage

Note – All fields noted by a red asterisk (*) on the form are required fields that must be filled before the record can be completed.

1. Once the user has clicked the “Add a Property Damage” link, a new page will be display in which the user must enter the injury or illness information for the person involved with the incident.

a. At the top of the form, the user will see multiple “tabs”. The first of these tabs is labeled

“Incident Information”, and clicking on this tab will return the user to the Incident Information portion of the record. If the user has entered information for injured personnel involved with the incident, the “Person #” tabs will be displayed as well.

b. A new tab labeled “Add a Property Damage” will be displayed. Clicking on the “Add a

Property Damage” link will take the user to the Property Damage portion of the record.

c. Delete this Record – Clicking this button removes the “Property Damage” portion from the incident record. All data entered for all Property Damages for this record will be deleted.

This should only be used to remove a record that was incorrectly associated with the incident.

2. Section 1 – Involved Person Data

a. Age – The age of the involved person

b. Gender – The gender of the involved person

c. Prime Contractor – The contractor for which the involved person works. This information is auto-populated by the application

d. Sub Contractor – The sub-contractor for which the involved person works (if any). This information must be typed into the open text field.

Revised 01/12/2018 28

3. Section 2 – Attached Documents

a. Any documents or pictures regarding the involved person’s injury/illness information can be attached in this section, in the same manner as on the “Incident Information” section (see above).

4. Section 3 – Property Damaged

a. Was anyone injured? – The user should note whether or not a person was injured during the incident.

b. Was a government motor vehicle involved? – The user should note whether or not a government motor vehicle was involved in the property damage.

c. Material/Property Damaged – The user should note specifically what property/material/equipment was damaged in the incident. Clicking on the “Add Property

Detail” button opens a new window in which the user must input the following information:

Revised 01/12/2018 29

i. Property Type – The user must click on the drop-down box and select the type of property damaged (Equipment, Vehicle, Structure, Motorcycle).

ii. Property ID – The user must type the ID of the property (VIN, Serial #, etc.) directly into the open text field.

iii. Detail Description – The user may type a description of the property directly into this open text field.

iv. Property Owned By – The user must click on the drop-down box and select the owner of the property (DOD, Non-Government, Other Government Agency, Privately Owned).

v. Has Tags – If the user selected “Motorcycle” or “Vehicle” in the “Property Type” field, the user may note whether or not the property has tags, what state issued the tags, and the actual tag number.

vi. Est. Cost – The user must type the estimated cost of the damaged property (in US dollars) directly into the open text field.

vii. Lost Days – The user must type the number of days the property is lost or out of commission directly into the open text field.

viii. Clicking the “Add” button will add the information to the record. The window will clear and remain open to add multiple damaged property/material/equipment (if any). Clicking the

“x” in the top right corner of the small window will close the window and return the user to the Property Damage page. The user may click the “x” next to any property record to delete that record.

Revised 01/12/2018 30

ix. Property Detail records can be removed by clicking the “x” button next to each record. If the user wishes to change the text in the “Property Detail” field, clicking the “Pencil” icon next to the field opens a new window in which the user may edit the text. Clicking the

“Update” button saves these changes.

Revised 01/12/2018 31

5. Section 4 License –

a. Are appropriate License and Certification/Medical current? – The user should note whether or not the involved person’s appropriate License and Certification/Medical records are current.

b. Attach Image of License or Certification – Any documents or pictures regarding the involved person’s licenses or certifications can be attached in this section, in the same manner as on the “Incident Information” section (see above).

6. Section 5 – Training

a. Was all the contract-required training provided to the employee? – The user should note whether or not the involved person was provided with the training required of that person according to their contractual agreements. In the “Explain” open text field, the user may enter any comment to explain the required/received training.

Revised 01/12/2018 32

7. Submit Incident

b. Once all of the required and relevant information specific damaged property has been entered, the user must click the “Submit Incident” button, located in the bottom left corner of the form. Clicking this button displays three options to the user:

i. I am Finished – The user should click this option once all information regarding the incident has been entered. This will complete the entry of the record, moving the record to Submitted status for review.

ii. Add an Injury Illness – The user should click this option to record the injury/illness information for any additional persons involved with the incident. A new record tab is created and the user must enter in the information as described above.

i. …OOOPS I still need to make changes – This option allows the user to return to the property damage record and make any changes required before the record is completed.

c. If the user has incorrectly entered information in any of the required fields, the form will not be submitted. Instead, a message will be displayed at the top of the page that states the number of errors on the page. Fields with incorrectly entered or missing data will be outlined in red. Once these fields are filled/corrected, the “Submit Incident” will work as stated above.

Revised 01/12/2018 33

Administrating the Submitted Incident Record

Reviewing the Incident Record

1. Once the incident record has been submitted, the record is moved in to “Submitted” status. CIRS administrators will receive an email stating that an incident has been reported and the record must be reviewed.

2. Administrative View – The “Administrative View” section (already displayed for the CIRS

Administrator while in “New” status) allows the administrator to review and complete the incident record. This administrative section appears on each portion of the incident record (Incident

Information, Person #, and Property Damage). The information entered will be shared in the administrative section of each portion of the record; thus, the information only needs to be entered once to be displayed in each section. Administrative information entered is assumed to relate to the incident record as a whole, not to individual portions of the record.

a. Administrative Attached Documents - Any documents or pictures regarding the incident record’s information can be attached in this section, in the same manner as on the “Incident

Information” section (see above).

b. Standards Violated – The administrator must enter the specific standard(s) that was violated in association with the incident. Clicking on the “Search Standard(s)” link displays the

Standard Search area.

Revised 01/12/2018 34

i. Max # Returned: - The administrator should select the maximum number of results to display.

ii. Select Reference: – Clicking on the black popup triangle opens a new window in which the administrator can search for and select the specific reference for the standard that the administrator wishes to note on the incident record.

iii. Section/Paragraph # (Begins with) – The administrator may enter the beginning or all of the section or paragraph in which the standard that the administrator wishes to note on the incident record is located.

iv. Citation Text Keywords: – The administrator may select one or more “Keywords” within the citation that the administrator wishes to note on the incident record by checking on the box next the keyword(s). Note: These keywords have been preselected. To add additional keywords, create a Data Change Request or otherwise contact ESAMS.

v. Reset – The administrator may click the “Reset” button at any time to remove all information from the Standard Search area and start a new search.

vi. Search – Once the administrator has entered the desired information, clicking the

“Search” button displays a list of all standards that match the information placed in the search fields. Clicking on the title in the “Citation” field will note that standard on the incident record. To remove a standard from the record, click on the red “x” next to the standard to be removed.

c. Was a mishap review board convened for this mishap? – The administrator should note whether or not a mishap review board was convened. If “Yes” is selected, an open text field will be displayed in which the administrator must enter an explanation.

d. Cause Code – The administrator must enter the specific cause behind the incident. Clicking on the black popup triangle opens a new window in which the administrator can select the specific cause.

Revised 01/12/2018 35

e. Occurred on Base? – The administrator should note whether or not the incident occurred on a military base. If “Yes” is selected, the administrator must enter the name of the base on which the incident occurred.

i. Installation – Clicking on the black popup triangle opens a new window in which all available installations are displayed. Clicking on the name of an installation will populate that name in the field

ii. Installation (Freeform) – If an installation is not available in the installation list, the administrator may instead type the name directly into this open text field.

Revised 01/12/2018 36

f. Administrative Comment Log – In this area, administrators may enter individual comments pertaining to the incident record. These comments can be viewed by other administrators, and are “stacked” in order of entry. As the legend below the comment log states:

i. Messages that the record has been “Returned to the Reporting Contractor for More

Information” will be highlighted in pink;

ii. Messages that the record has been “Declined” will be highlighted in red.

3. Save Admin Options – Clicking this button will save any information that has been entered in the

Administrative area without changing the Status or sending any emails.

4. Return to Contractor for More Info – If the administrator decides that the information in the record is incorrect or deficient, clicking the “Return to Contractor for More Info” button will change the

Status of the record to “Returned” and will open the record so that the CIRS Administrator can review the record and enter the correct information.

Revised 01/12/2018 37

5. Reviewed – Once the administrator is satisfied with the information entered in the incident record, clicking the “Reviewed” button changes the status of the record to “Reviewed”

Accepting/Declining the Incident Record

Note: Administrators must have “Approve” access rights to enter this portion of the CIRS application.

1. Once the incident record has been placed in “Reviewed” status, Administrative personnel with

“Approve” access rights will receive an email stating that an incident record has been reviewed and must be accepted or declined.

2. The administrator must search for the incident record in the CIRS Main area (see below).

3. Once the record has been reviewed by the approving administrator, that administrator must choose to accept or decline the incident record using the new buttons found at the bottom of the

“Administrative View” area.

a. Accept – Found at the bottom left corner of the form. Clicking on the “Accept” button changes the status of the record to “Accepted”, removes the record from the Administrator’s

Hotlist (see below), and locks the record so that no changes can be made.

b. Decline – Found at the bottom left corner of the form. Clicking on the “Decline” button changes the status of the record to “Declined”. A window will appear in which the administrator must enter the reason that the record has been declined and click the “Confirm

Decline” button. The record must be reviewed by an administrator again, and then can either be Returned to the Reporting Contactor or listed again as Reviewed (following the directions as listed above).

Revised 01/12/2018 38

CIRS – Process Flow Diagram

Revised 01/12/2018 39

CIRS Email Notification Events

The CIRS application sends several emails during the investigation process. The tables below provide some instruction on when these emails are sent and who should receive them.

EMAILS Generated:

User ID, Password and Deletion Emails (Generated Only For NON- Manual Entry by CIRS Administrator)

Mail Events

(Sent for) Scope of

Notification Contractor

When (Action)

Snap Shot

Deletion Message Contractor X

CIRS

Administrator clicks “Delete” button

Scope:

The Claimancy scope has a single Access Level with common Mail Events.

Claimancy - ESAMS Admin - No restriction – Entire Claimant Reporting Down-Line

The following scopes have common Access Levels (see above) with common Mail Events (see below).

FEAD

Command - Restricted to their local command/organization

Multi-Command - Restricted to specifically identified command/organization

Parent-Command - Restricted to command/organization and their reporting down-Line

FEAD Access Levels:

Create/Edit/Reports - This a Reviewer

Create/Edit/Approve/Reports - This is an OSH Specialist/Approver

Reports/Notification - Only receives email notifications

NOTE: To simplify the chart below we only show the Claimancy and FEAD regardless of actual scope:

Revised 01/12/2018 40

Status Change Email Notifications

When (Action)

Mail Events

(Sent by)

Scope of Notification

Admin

FEAD

Reviewer

OSH

Specialist Approver

FEAD

Notifications

Contractor

Claimancy

Admin

FEAD

Create/Ed it/ Reports

FEAD

Create/Edit/

Approve/ Reports

FEAD

Reports/

Notification

Initial Submission

Contractor

Contract Oversight Upline

X X X X X

FEAD

Reviewer

X X X X X

FEAD

Approver

X X X X X

Claimancy X X X X X

Reviewed

FEAD

Reviewer Contract

Oversight Upline

X X X X X

FEAD

Approver

X X X X X

Claimancy X X X X X

Return to Contractor for More Information

FEAD

Reviewer

Contract Oversight Upline

X X X X X

FEAD

Approver

X X X X X

Claimancy X X X X X

Report Declined

FEAD

Reviewer Contract

Oversight Upline

X X X X X

FEAD

Approver

X X X X X

Claimancy X X X X X

Report Updated Contractor Contract Oversight Upline

X X X X X

Approved

FEAD

Approver

Contract Oversight Upline

X X X X X

Claimancy X X X X X

Revised 01/12/2018 41

Links of Interest

Generate Incident

Clicking on this link creates a new page on which the administrator may begin a new incident record, entering information as described above (see above).

Man Hours

In this section, administrators may enter the Man Hours worked for each contract.

1. Clicking on the “Man Hours” link displays the CIRS Man Hour page.

Revised 01/12/2018 42

2. All UICs/Commands within the administrator’s scope will be listed. Clicking on a command name displays all Prime Contractors that have a contract with the UIC/Command.

3. The administrator should click on the name of a Prime Contractor to view all of that Prime

Contractor’s contracts associated with the UIC/Command.

4. Clicking on the Contract # displays the Man Hour information for that contract.

Revised 01/12/2018 43

5. Clicking on the Contract # will display the Man Hour information of the contract for the previous and current fiscal year, with each year divided into the fiscal quarters.

6. The administrator may enter the total Man Hours worked under the contract for each fiscal quarter. Clicking the “Save Hours” button saves the information entered in the field(s).

7. Note 1: If a contract was not valid during a quarter, that section will be grayed out and the administrator will not be able to enter information in that block.

8. Note 2: If an administrator enters Man Hours for a previous fiscal year, that information cannot be deleted or edited once it is saved.

Revised 01/12/2018 44

Search for Incident(s)

Clicking on this link opens a new window in which the administrator may search for any incident record within the administrator’s scope. The administrator may search using as many or as few of the fields as desired.

Note: If the search results in no records found, the administrator may have entered incorrect information in one or more fields and thereby excluded the record being sought. In these cases, the administrator should attempt to search again using the correct information or fewer search criteria.

Revised 01/12/2018 45

1. Event Type – The user can choose to search for Incidents, Near Misses, or both.

2. Incident Report Number – Each incident record is assigned a number specific to that record.

Entering that number in this field will find that specific record.

3. Installation of Incident – The military installation or base at which the incident occurred. Clicking on the black popup triangle will open a new window in which the administrator may select the desired Installation.

4. Contract Oversight Command – The command of the contract under which the involved person is employed. Clicking on the black popup triangle will open a new window in which the administrator may select the desired Command.

5. Contractor Name – The name of the Contractor company under which the involved person is employed.

6. Contract Number – The number of the Contract under which the involved person is employed.

7. CAGE Code – The Commercial And Government Entity (CAGE) Code of the Contract under which the involved person is employed.

8. Task Order Number – The specific Task Order number within the contract that the employee was tasked with at the time of the incident.

9. Status – The status of the incident (New, Submit, etc)

10. Narrative (contains) – The information entered in the “Initial Description” field on the “Incident

Information” portion of the incident. The administrator may enter some of the narrative information, which the search function will attempt to match to full narratives in the database.

11. Incident Dates – The administrator may enter a set of dates within which the system will search for incident records by clicking on the “From” and “To” fields to use the Calendar popup. For example, the user would enter “From: April 1, 2010” and “To: April 30, 2010” to see all incident records within the administrator’s scope during the month of April.

12. Reset Criteria – Clicking on this link will reset the data fields in the search window, allowing the administrator to perform a new search.

13. Search – Clicking on this button will allow the administrator to find incident records based on the information entered in the search fields. Clicking on an “Incident ID” number will open the incident record.

14. Hide Search Results – Clicking on this link removes the results of the incident search from the

Administrative hotlist area. The administrator must perform another search to see the search results again.

Revised 01/12/2018 46

My Self Entries

In this section of the CIRS Administrative page, the administrator will see a “Hotlist” of all incident records for which the administrator was the reporting person. Note: Incidents in “Accepted” status will not be shown. The following information is displayed:

1. Incident ID – The unique ID number of the incident. Clicking on this number opens the incident record for viewing and editing,

2. Point of Contact – The name of the person who reported the incident to the administrator.

3. Notified Date – The date on which the administrator was notified of the incident.

4. Authorized Date – The date on which the administrator authorized the Reporting Contractor for

CIRS access and/or created the incident record.

5. Incident Date – The date on which the incident actually happened.

6. Status – The current status of the incident record.

7. Installation of Incident – The military base or installation on which the incident occurred.

8. Prime Contractor – The name of the contractor by which the involved person is employed.

Revised 01/12/2018 47

Requested Incidents

In this section of the CIRS Administrative page, the administrator will see a “Hotlist” of all incident records for which an incident record has been created. Once an Administrator accesses the incident record and saves information, thus changing the record to “New” status, the record will no longer show on this “Hotlist”. The following information is displayed:

a. Point of Contact – The name of the person who reported the incident to the administrator.

b. Prime Contractor – The name of the contractor by which the involved person is employed.

c. Contract - Task Order – The Contact # and Task Order # with which the incident is associated.

d. Notified Date – The date on which the administrator was notified of the incident.

e. Authorized Date – The date on which the administrator authorized the Reporting Contractor for

CIRS access and/or created the incident record.

f. Contract Oversight – The name of the command assigned to manage the associated contact.

g. View/Edit – The “View/Edit” link allows administrators to view the email entered for the Reporting

Contractor. This email address can be edited by typing directly into the email field.

Revised 01/12/2018 48

Active Incidents

In this section of the CIRS Administrative page, the administrator will see a “Hotlist” of all incident records within the administrator’s scope. Note: Incidents in “Accepted” status will not be shown. The following information is displayed:

1. Incident ID – The unique ID number of the incident. Clicking on this number opens the incident record for viewing and editing.

2. Type – The type of report being recorded: Incident or Near Miss.

3. Point of Contact – The name of the person who reported the incident to the administrator.

4. Notified Date – The date on which the administrator was notified of the incident.

5. Authorized Date – The date on which the administrator authorized the Reporting Contractor for

CIRS access and/or created the incident record.

6. Incident Date – The date on which the incident actually happened.

7. Status – The current status of the incident record.

8. Authorized By – The name of the CIRS Administrator that authorized/created the incident record.

9. Contract Oversight – The name of the command assigned to manage the associated contact.

10. Installation of Incident – The military base or installation on which the incident occurred.

11. Prime Contractor – The name of the contractor by which the involved person is employed.

Advanced Options

The “Advanced Options” area contains additional resources for administrative users with “CIRS Administrator

(Create/Edit/Approve/Reports)” level access. Clicking on the “Advanced Options” link displays the additional administrative links.

Revised 01/12/2018 49

Delete an Incident

Administrators with “CIRS Administrator (Create/Edit/Approve/Reports)” level access can delete incident records from their Incident Hotlists. This option is normally reserved for incident records that have been entered erroneously (for example, a duplicate of an incident that has already been reported, or a record that was not considered an incident). Note:

Incident records that contain incorrect information should not be deleted, instead these records should be returned to the Reporting

CIRS Administrator for corrections (see above).

To delete an incident, the CIRS Administrator must click on the “Advanced

Options” link under “Links of Interest” on the CIRS Main page. Clicking on this link displays the “Enable Delete” link. This link defaults to “OFF” when an administrator accesses the CIRS application. Clicking on the

“Enable Delete” link changes the link to “ON” and displays a new “Delete” link next to each of the administrators incident records on each of the

Incident Hotlists (My Self Entries, Requested Incidents, and Active

Incidents).

Once the administrator clicks on the “Delete” link next to an incident record, a new window is displayed in which the administrator must note the reason for the deletion by typing the information directly into the open text field. Clicking on the “Confirm Delete” button removes the incident record from the administrator’s

Incident Hotlists, as well as removing the record from ESAMS completely.

Revised 01/12/2018 50

CIRS Reports

These reports are available to users with Contractor Incident Reporting System (CIRS) access, and provide users with data based on information from contractor-specific incident records reported through ESAMS.

Favorite Reports

At the top of the ESAMS Main page, the “Reports” link contains several links for administrators. Clicking on the “Reports” link expands the area to show all links available to the administrator. Administrators can note specific report links in the “Reports” area as “Favorites”. These links will be displayed in the

“Favorite Reports” area above the normal report links, allowing the administrator to quickly…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .