TE 25 GFEBS Field Requirments.pdf

Installation Management Command integrates and delivers base support to enable readiness for a globally-responsive Army

We are the Army’s Home Serving the Rugged Professional

DPW / BOID / BOB

UNCLASSIFIED

1 of 25 02 December 2020

DPW GFEBS REQUIRED FIELDS

DPW - BOID

UNCLASSIFIED

2 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements:

GFEBS NOTIFICATIONS: DMO (A001), OWO (A004)

• Non-contractor orders – Utilities and other service contracts.

• P1 – Emergency.

• P2 – Urgent.

• P3 – Routine.

• GFEBS information shall be input as real time.

3 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Notification creation and update:

1. Priority - Required field:

DMOs, OWOs - Emergency, Urgent or Routine

2. Start Date and End Date - Automatic in GFEBS, and update if needed.

3. Text - Description and Subject long fields:

Description field - Brief Description of the problem starting with a verb and Acronyms established by the Government.

Ex. FWP RPL DR CLOSER BY OFFICE Ex. BOM RPR INOP DOOR TO EXTERIOR MECH RM Ex. MO RPR BROKEN WINDOW DOOR Ex. RPR CLOGGED URINAL #4 IN MALE LATRINE RM126 Ex. Lacking hot water in Room 239.

Ex. Request to clean vents and filters in room 104B.

Subject Long Text field - Include the name of the order requester (if different from the POC), Log events and statuses of the notification. Ex. appointment setup with POC, GFEBS was down, POC not available, etc.

Include events of status of notification, i.e. appointment setup with POC, etc.

Text - Use upper case letters for start of sentence and for acronyms.

Log of events - Shall start with most recent event followed by the later event.

Event format - Shall start with the date followed by the sentence.

Ex: 2018.05.18 Responded, Setup appointment with POC to inspect vents and filters.

Date format - Include year, month, and day. Use periods in between the year, the month and day (yyyy.mm.dd).

Ex. 2018.05.18

Sentence shall start with an action verb followed by the name of item, room number, latrine, floor num., etc.

Ex. 2018.05.20 Inspected vents and filters in room 104B.

Ex. 2020.07.01 RPR TOILET #2 FEMALE LATRINE RM 120

Include room number (if applicable).

No abbreviations allowed. Acronyms are allowed and shall provide a crosswalk list to the government.

4. Functional Location –

Functional location shall be captured at the facility/building number.

Ex. Functional location will be in 48125.0077

GFEBS NOTIFICATIONS: DMO (A001), OWO (A004)

4 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Notification creation and update:

5. Point of Contact Information - Shall include:

Complete name: Last, First name Ex. Ortega, Mercedes Telephone number and/or cell number: 10 digit and separated by dashes (-).

Ex. 915-568-2121 Complete email address.

Ex. mercedes.ortega2.civ@mail.mil Complete Street Address (if available) Ex. 1733 Pleasonton Road

6. WBS - Verify:

DMOs – verify system populates field.

OWOs – Populate Additional Data Tab.

7. User field - Status of the notification. DPW required codes:

Appointment Req.

Appointment set.

Convert to an IJO Convert to SOO.

Subject to available Funds.

Tied to Existing Order.

8. Planner Group: Customer ID

9. Work center - Main work center (if applicable).

10. Plant – BLIS.

11. Reported by – Identify the order using the following:

WEBORDER, CALLIN, WALKIN, EMAIL, ArMA.

FLWUP and SCHED

12. Malfunction Date - Date customer reported the request when GFEBS is unavailable.

Populate this field with the date of the order request.

13. Sort Field: Enter the ArMA number.

14. Notification shall be converted into an order the same day and time.

mailto:mercedes.ortega2.civ@mail.mil

5 of 25DPW / BOID / BOB 02 December 2020

1. Priority: Emergency, Urgent or Routine, and Reg. Ops for OWOs.

3. Text fields:

a) Description: Short Description of problem.

b) Full Name of the Order Requester (If different than the POC).

c) Subject Long Text: Log of events and status of notification.

2. Start and End Date.

4. Functional Location.

DPW REQUIREMENTS FOR GFEBS NOTIFICATION CREATION AND UPDATE

6 of 25DPW / BOID / BOB 02 December 2020

5. POC information.

a) Full Name

b) Street Address (if applicable)

c) Telephone Number

d) E-mail Address

7 of 25DPW / BOID / BOB 02 December 2020

6. WBS

GFEBS NOTIFICATIONS: DMO (A001), OWO (A004)

13. Sort Field

8 of 25DPW / BOID / BOB 02 December 2020

8 & 9 & 10. Planner Group, Main Work Center, and Plant = BLIS.

7. User field: Status of notification.

11. Reported by: WEBORDER, CALLIN, WALKIN, EMAIL, FLWP, SCHED.

9 of 25DPW / BOID / BOB 02 December 2020

GFEBS NOTIFICATIONS: DMO (A001), OWO (A004)

12. Malfunction Date.

10 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Order and Sub-Order Creation:

1. Priority - Required field:

DMOs, OWOs- Emergency, Urgent or Routine.

2. Start Date and End Date - Update dates to actual start and end date.

3. Functional Location:

Functional location shall be the facility/building number.

DMOs, OWOs, PMOs, PWOs.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

4. Defect - Enter the defect code.

Defect codes are selected from the list in

GFEBS.

DMOs, OWOs, PWOs.

4a. Short text: Enter code only when directed by Government.

Ex. COVID19 – Cleaning.

5. Notification number.

6. Planner Group - Customer ID

7. Main Work center - Main work center.

11 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Order and Sub-Order Creation:

8. Text – Subject long fields:

Subject Long Text field: Description of the work required.

The description of the work must be the first lines followed by the log of events.

Log events leading to the completion of the order. Ex. material estimate arrival date, appointment setup with POC, GFEBS was down, POC not available, reference DMO #, etc.

Text – Use upper case letters for start of sentences and acronyms.

Log of events - Shall start with most recent event followed by the later event.

Reference sub-order in main order.

Event format - Shall start with the date followed by the sentence.

Ex: 2018.05.22 Requested assistance for cleaning vents and filters.

Date format - Include year, month, and day. Use periods in between the year, the month and day (yyyy.mm.dd).

Ex. 2018.05.20

Sentence shall start with an action verb followed by the name of item, room number, floor num.

etc.

Ex. 2018.05.20 Inspect vents and filters in room 104B.

In PWOs enter the initial DMO as reference.

Include room number (if applicable).

No abbreviations allowed. Acronyms are allowed and shall provide a crosswalk list to the government.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

12 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Order and Sub-Order Creation:

8. Text – Subject long fields: Continuation for PWOs only:

Description of the scope of the Project from

4283 and include 4283 number.

Ex. FE10050J – The scope of the work entails the following … See example to the side.

8a. PWOs – Short text Delivery Order number followed by the

Project title.

13 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Order and Sub-Order Creation:

9. Operations tab – Enter assigned work center (s):

Work centers (shop numbers).

Activity Type (s) shall correspond to the positions of the work center; update if different.

10. Operation Short Text:

Short description of the performing operation performing the task.

No abbreviations allowed. Acronyms are allowed and shall provide a crosswalk list to the government.

Ex. Request to clean vents.

11. Work Labor Hours:

Estimated/ Planned hours to perform the work per work center, if available.

12. User field - status of the order in GFEBS:

DPW required codes: Convert to IJO, Convert to

SOO, Subcontractor, Awaiting Materials, Supplies received, Cancelled, Awaiting Permit, Awaiting approval, Warranty and Housing crisis 2019.

PWOs: DMOs converted into a PWOs shall have the status code “Convert to IJO”.

Other available Codes - see GFEBS or appendix A.

If not sure, contact DPW.

14 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Order and Sub-Order Creation :

13. WBS - Confirm this field is populated in every order:

Additional Data Tab:

DMOs : WBS is populated automatically.

OWOs : Enter Government provided

WBS’s for each service provider by FY.

PWOs : Enter WBS from the 4283.

Location tab: Populates automatically as the functional location is entered.

14. Sort Field – Contractor Order Number.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

15. Sub-Orders Only:

Main order and sub-order must not have the same priority.

Main order must be final confirmed prior creating the sub-order.

Do not technically complete main order until all sub-orders are technically completed.

16. Attachments: Attach documentations to the orders.

Ex: PWO package, Key Memo, Digging permit, etc.

15 of 25DPW / BOID / BOB 02 December 2020

6 & 7. Planner Group, Main Work Center and Plant

= BLIS.

1. Priority: Emergency, Urgent or Routine.

3. Functional Location.

5. Notification number.

8. Text - shall be in following format:

a) Description: Short Description of problem.

b) Subject Long Text: Log of events.

2. Start Date and End Date.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

DPW REQUIREMENTS FOR GFEBS ORDER OR SUB-ORDER CREATION

4. – Defect Code

4a. – Short text field - Code

16 of 25DPW / BOID / BOB 02 December 2020

Double click on “created on”0

11. Work hours.

9 & 10. Work center (Shop), operation short text, Act Type.

12. User Field.

DPW REQUIREMENTS FOR GFEBS ORDER OR SUB-ORDER CREATION

17 of 25DPW / BOID / BOB 02 December 2020

13. WBS.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

DPW REQUIREMENTS FOR GFEBS ORDER OR SUB-ORDER CREATION

14. Sort Field

18 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field Requirements for Confirmation:

1. Actual worked hours for the date confirming.

No lump sums. Ex. 40 hrs. in one confirmation.

Work hours is Total Labor hours worked by each technician. Ex. If the order required two technicians, there should be two lines of confirmations for each technician.

2. Actual Work center(s).

Shop number(s) performing the work.

3. Actual Activity Type(s).

Activity type(s) performing the work.

4. Work Start Date - single confirmation (Start of Execution Date - collective confirmation):

Response start date and time.

5. Work Finish Date - single confirmation (End of Execution Date - collective confirmation): Response end date and time.

Date when work was performed.

Confirmation shall be entered in GFEBS the day work was performed.

6. Confirmation Text: Include number of operators to perform the operation.

Ex. Two technicians in site visit.

Use confirmation field for additional information.

Ex. Cleaned additional vents.

Ex. Cancelled DMO per POC.

7. Final confirmation – Check when work is complete.

8. Technically complete order after labor, materials, equipment and/or subcontract confirmations have been done in GFEBS.

TECO must be completed within 2-weeks after final confirmation and any sub-order created has been TECO.

TECO cannot be done until all sub-orders have been completed.

19 of 25DPW / BOID / BOB 02 December 2020

1. Actual work hrs.

8. Technically Complete on completed orders.

2 & 3. Actual work center(s) and Act Type(s)

4. Work Start Date

Replaced Additional Vents

6. Confirmation Text.

7. If order is complete, select final confirmation.

5. Work Finish Date

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

DPW REQUIREMENTS FOR GFEBS ORDER CONFIRMATION

Single Confirmation)

20 of 25DPW / BOID / BOB 02 December 2020

(Option: Collective Confirmation)

Cleaned additional vents

122563 10000123456

6. Confirmation text.

Confirmation num., Order num., Operation num., Plant

1. Actual work hours

1184 BLIS C00100

2 & 3. Actual Work Center(s), and Act Type(s)

7. If order is complete, select final confirmation

07/08/18

5. End Execution Date.

122563 10000123456 0010 2 HR

122563 10000123456 0010 2 HR 1185 BLIS C00380

07/06/18

4. Start Execution Date.

DPW REQUIREMENTS FOR GFEBS ORDER CONFIRMATION

21 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field MIGO Requirements Confirmation:

1. Goods Issue – Material, Subcontract and Rental equipment.

2. Document type: Other.

3. Movement 261.

4. Material - Shall be itemized and provide a master list part number to government for a crosswalk.

Material: Material(s) used to complete the order.

Ex. One line item for paint.

Subcontract: Service(s) subcontracted to complete the order per company.

Equipment Rental: Equipment rented for the order per company.

Contractor Equipment: Equipment Owned, Financed or Leased. Do not include hand tools or shop equipment anchored to the shop.

5. Use the following part numbers for reporting cost:

Material: 30038687 Subcontract: 30038688 Equipment Rental: 30139872 Contractor Equipment (Owned/Financed/Leased): See DPW Other part numbers might be added during the contract. See DPW.

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

6. Quantity - Total amount in dollars per line item.

Material: Enter total cost for each material line item.

Subcontract: Enter total cost for the service per company.

Equipment Rental: Enter total cost for the rental for the company.

Contractor Equipment: Enter zero cost ($0).

7. Order number.

8. WBS element number – See DPW for the WBS number.

9. Plant – Blis

10. Storage Location - WH1.

22 of 25DPW / BOID / BOB 02 December 2020

DPW GFEBS Field MIGO Requirements Confirmation:

Equipment Rental - Enter in the following format:

Type Name of Equipment; Rental Rate ($);

Time (hr(s), day(s), week(s), month(s)) Ex. Pressure wash Rental; $56.9; 20 hrs Ex. Man lift rental; $150; 2 days

Contractor Equipment – Enter in the following format:

Equipment – Heavy or specialized equipment to perform the order.

Type Name of Equipment; Time Utilized (hr(s)) Ex. Backhoe 60HP; 20 hrs Ex. Semi-Truck with Flatbed; 2 hrs

GFEBS ORDER: DMO (A001), OWO (A004), PWO (A003)

11. Text field - Enter the following information:

Acronyms are allowed and shall provide a crosswalk list to the government.

Materials - Enter Quantity followed by contractor part number and separated by dot (.).

Contractors number Ex. 2.23546789-4321

Subcontractor Service - Enter in the following format:

Type Service; Labor Rate ($); Time (hr(s)) Ex. Extraction Service; $31.50; 14 hrs Ex. Window installation service; $64; 8 hrs

23 of 25DPW / BOID / BOB 02 December 2020

4 & 5. Material or Equipment or Subcontractor number.

Example (30038687, 30038688, 30139872, etc.)

3. Movement type = 261

2. Document type:

Other or Order

1. Goods issue

DPW REQUIREMENTS FOR GFEBS ORDER MATERIAL, EQUIPMENT

24 of 25DPW / BOID / BOB 02 December 2020

6. Itemized Total cost per line item

UOM = $$

25 of 25DPW / BOID / BOB 02 December 2020

7. Order number.

26 of 25DPW / BOID / BOB 02 December 2020

11. Text Field:

a) Material: Quantity and Number.

b) Subcontract: Service, Rate and Time.

c) Equipment Rental: Equipment, Rate and Time.

d) Contractor Equipment: Equipment and Time.

8. WBS element.

9 & 10. Plant and storage location.

27 of 25DPW / BOID / BOB 02 December 2020

End of Brief

28 of 25DPW / BOID / BOB 02 December 2020

SAF Subj to Avail Funds AWP Awaiting Permit AA Awaiting Approval APST Appointment Set APV Approved AWB Awaiting Bids CANC Cancelled CCC Credit Card Transaction CIJO Convert to IJO CSOO Convert to SOO EXT Extended HC19 Housing Crisis 2019 HLD On Hold INSP Inspection in Progress ITC Issued to Contractor

NFW Non-Fair Wear & Tear NRW Needs Rework NXS Inaccessible NXS1 1st – No Access to Building NXS2 2nd – No Access to Building NXS3 3rd – No Access to Building QAC Quality Assurance check REC Supplies Received RFP Request for Proposal RFQ Request for Quote SHP In Shop SUB Subcontractor WAR Warranty WIP Work in Progress WMAT Awaiting Materials WTST Awaiting Test Result

GFEBS ORDER: Appendix A: User Codes