Attachment 2 - Specifications.pdf
PDF 1 MB Posted
- Attached to
- Air Force Base Bulk Fuel Fence Repair
- Solicitation number
- FA441925R0003
About this file
This is a specification document for a high-security fence repair project at an Air Force Bulk Fuel Yard. The project involves demolishing an existing fence with six double swing and two single swing gates, and replacing it with a new fuel yard fence that includes three double swing gates and one single swing gate. The scope also includes grounding the fence to meet Unified Facilities Criteria (UFC) Entry 4-022-03 for Security Fences and Gates, and replacing an existing concrete drainage ditch with a new drainage swale.
The specification details precise requirements for fence components, including chain link fabric with polyvinyl chloride coating in dark bronze, galvanized steel posts, barbed wire supporting arms, and cable reinforcement. Installation specifications mandate specific post setting depths, concrete requirements, and grounding procedures. The fence is to be 7 feet high, with precise installation guidelines for fabric attachment, supporting arms, and barbed tape. Additional technical requirements include cable reinforcement with 3/4-inch steel aircraft cables, deadman anchors, and grounding to ensure electrical continuity with a maximum ground resistance of 25 ohms.
View the file
Other files
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
REPAIR BULK FUELS FENCE F807 AGGN207002
PROJECT TABLE OF CONTENTS
DIVISION 01 - GENERAL REQUIREMENTS
01 11 00 02/24 SUMMARY OF WORK
01 14 00 11/22, CHG 3: 08/24 WORK RESTRICTIONS
01 30 00 11/20, CHG 4: 08/24 ADMINISTRATIVE REQUIREMENTS
01 31 23.13 20 08/23, CHG 1: 02/24 ELECTRONIC CONSTRUCTION AND FACILITY
SUPPORT CONTRACT MANAGEMENT SYSTEM (eCMS)
01 32 01.00 10 08/23, CHG 1: 08/24 PROJECT SCHEDULE
01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES
01 35 26 05/24 GOVERNMENTAL SAFETY REQUIREMENTS
01 35 29.13 11/15, CHG 1: 08/22 HEALTH, SAFETY, AND EMERGENCY RESPONSE
PROCEDURES FOR CONTAMINATED SITES
01 42 00 05/24 SOURCES FOR REFERENCE PUBLICATIONS
01 45 00 08/23, CHG 1: 05/24 QUALITY CONTROL
01 57 19 08/22 TEMPORARY ENVIRONMENTAL CONTROLS
01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND
DISPOSAL
01 78 00 05/19, CHG 1: 08/21 CLOSEOUT SUBMITTALS
01 78 23 05/23 OPERATION AND MAINTENANCE DATA
01 78 24.00 10 05/23 FACILITY DATA REQUIREMENTS
01 78 24.00 20 05/23, CHG 1: 11/23 FACILITY DATA WORKBOOK (FDW)
DIVISION 31 - EARTHWORK
31 00 00 08/23 EARTHWORK
DIVISION 32 - EXTERIOR IMPROVEMENTS
32 31 13.53 11/21 HIGH-SECURITY FENCES (CHAIN LINK AND
ORNAMENTAL) AND GATES
-- End of Project Table of Contents --
PROJECT TABLE OF CONTENTS Page 1
SECTION 01 11 00
SUMMARY OF WORK
02/24
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
Salvage Plan ; G
1.2 WORK COVERED BY CONTRACT DOCUMENTS
1.2.1 Project Description
The work includes Demolish existing fence, including the six double swing and two single swing gates, and replace with a new fuel yard fence.
Install three double swing gates, and a single swing gate. Include grounding to conform to criteria established in Unified Facilities Criteria (UFC) Entry 4-022-03, Security Fences and Gates. Demo existing concrete drainage ditch and construct new drainage swale. and incidental related work.
1.2.2 Location
The work is located at the Bulk Fuels yard , approximately as indicated.
The exact location will be shown by the Contracting Officer.
1.3 OCCUPANCY OF PREMISES
Building(s) will be occupied during performance of work under this Contract.[ Occupancy notifications will be posted in a prominent location in the work area.]
Before work is started, arrange with the Contracting Officer a sequence of procedure, means of access, space for storage of materials and equipment, and use of approaches, corridors, and stairways.
1.4 EXISTING WORK
Remove or alter existing work in such a manner as to prevent injury or damage to any portions of the existing work which remain.
Repair or replace portions of existing work which have been altered during construction operations to match existing or adjoining work, as approved by the Contracting Officer. At the completion of operations, existing work must be in a condition equal to or better than that which existed before new work started.
SECTION 01 11 00 Page 1
1.5 LOCATION OF UNDERGROUND UTILITIES
Obtain digging permits prior to start of excavation, and comply with Installation requirements for locating and marking underground utilities.
Contact local utility locating service a minimum of 14 calendar days prior to excavating, to mark utilities, and within sufficient time required if work occurs on a Monday or after a Holiday. Verify existing utility locations indicated on contract drawings, within area of work.
Identify and mark all other utilities not managed and located by the local utility companies. Scan the construction site with Ground Penetrating Radar (GPR), electromagnetic, or sonic equipment, and mark the surface of the ground or paved surface where existing underground utilities are discovered. Verify the elevations of existing piping, utilities,and any type of underground [or encased ]obstruction not indicated, or specified to be removed, that is indicated or discovered during scanning, in locations to be traversed by piping, ducts, and other work to be conducted or installed. Verify elevations before installing new work closer than nearest manhole or other structure at which an adjustment in grade can be made.
1.5.1 Notification Prior to Excavation
Notify the Contracting Officer at least 14 calendar days prior to starting excavation work.
1.6 GOVERNMENT-FURNISHED MATERIAL AND EQUIPMENT
The Government will furnish the following materials and equipment for installation by the Contractor:
DESIGNATION NO. DESCRIPTION QUANTITY
Quantities indicated for the above-listed items marked with an asterisk are estimates. It is the intention of the Government to furnish all quantities of the asterisk items required to complete the work as specified, and the various quantities will be adjusted when necessary.
Quantities stated for the above items not marked with an asterisk are all that will be furnished by the Government. Provide any additional quantities that are required.
1.6.1 Delivery Schedule
Materials and equipment will be available on or after Notice to Proceed is signed.
1.6.2 Delivery Location
The materials and equipment are located at the East of the airfield .
SECTION 01 11 00 Page 2
1.7 SALVAGE MATERIAL AND EQUIPMENT
Items designated by the Contracting Officer to be salvaged remain the property of the Government. Segregate, itemize, deliver and off-load the salvaged property at the Government designated storage area located within [_____] miles of the construction site.
Provide a salvage plan , listing material and equipment to be salvaged, and their storage location. Maintain property control records for material or equipment designated as salvage. Provide a system for property control in the salvage plan. Store and protect salvaged materials and equipment until disposition by the Contracting Officer.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
-- End of Section --
SECTION 01 11 00 Page 3
SECTION 01 14 00
WORK RESTRICTIONS
11/22, CHG 3: 08/24
PART 1 GENERAL
1.1 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
List of Contact Personnel
SD-07 Certificates
1.2 CONTRACTOR ACCESS AND USE OF PREMISES
1.2.1 Activity Regulations
Ensure that Contractor personnel employed on the Activity become familiar with and obey Activity regulations including safety, fire, traffic and security regulations. Keep within the limits of the work and avenues of ingress and egress. Wear appropriate personal protective equipment (PPE) in designated areas. Do not enter any restricted areas unless required to do so and until cleared for such entry. Ensure all Contractor equipment, include delivery vehicles, are clearly identified with their company name.
1.2.1.1 Subcontractors and Personnel Contacts
Provide a list of contact personnel of the Contractor and subcontractors including addresses and telephone numbers for use in the event of an emergency. As changes occur and additional information becomes available, correct and change the information contained in previous lists.
1.2.1.2 No Smoking Policy
Smoking is prohibited within and outside of all buildings on installation, except in designated smoking areas. This applies to existing buildings, buildings under construction and buildings under renovation. Discarding tobacco materials other than into designated tobacco receptacles is considered littering and is subject to fines. The Contracting Officer will identify designated smoking areas.
1.2.2 Working Hours
Regular working hours will consist of an 12 hour period established by the Contracting Officer, between 6 a.m. and 6 p.m., Monday through Friday , , excluding Government holidays.
1.2.3 Work Outside Regular Hours
Work outside regular working hours requires Contracting Officer approval.
Make application 5 calendar days prior to such work to allow arrangements
SECTION 01 14 00 Page 1 to be made by the Government for inspecting the work in progress, giving the specific dates, hours, location, type of work to be performed, contract number and project title. Based on the justification provided, the Contracting Officer may approve work outside regular hours. During periods of darkness, the different parts of the work must be lighted in a manner approved by the Contracting Officer.
1.2.4 Occupied Building[s]
The Contractor shall be working in an existing building around existing buildings which are occupied. Do not enter the building without prior approval of the Contracting Officer.
The existing buildings and their contents must be kept secure at all times. Provide temporary closures as required to maintain security as directed by the Contracting Officer.
1.2.5 Utility Cutovers and Interruptions
a. Make utility cutovers and interruptions after normal working hours or on Saturdays, Sundays, and Government holidays. Conform to procedures required in paragraph WORK OUTSIDE REGULAR HOURS.
b. Ensure that new utility lines are complete, except for the connection, before interrupting existing service.
c. Interruption to water, sanitary sewer, storm sewer, telephone service, electric service, air conditioning, heating, fire alarm, compressed air, and are considered utility cutovers pursuant to the paragraph
WORK OUTSIDE REGULAR HOURS.
d. Operation of Station Utilities: The Contractor must not operate nor disturb the setting of control devices in the station utilities system, including water, sewer, electrical, and steam services. The Government will operate the control devices as required for normal conduct of the work. The Contractor must notify the Contracting Officer giving reasonable advance notice when such operation is required.
[ 1.3 SECURITY REQUIREMENTS
[ Contract Clause FAR 52.204-2 Security Requirements and Alternate II and the following apply:
] ] PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
SECTION 01 14 00 Page 2
SECTION 01 30 00
ADMINISTRATIVE REQUIREMENTS
11/20, CHG 4: 08/24
PART 1 GENERAL
1.1 REFERENCES
The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.
U.S. ARMY CORPS OF ENGINEERS (USACE)
EM 385-1-1 (2024) Safety -- Safety and Occupational Health (SOH) Requirements
U.S. NATIONAL ARCHIVES AND RECORDS ADMINISTRATION (NARA)
15 CFR 772 Definition of Terms
15 CFR 773 Special Licensing Procedures
1.2 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
View Location Map
Progress and Completion Pictures
SD-04 Samples
Color Boards ; G
1.3 COLOR BOARDS
Submit five sets of color boards within 90 calendar days after Contract Award. Each set of boards must include samples of colors and finishes of interior surfaces, such as walls, floors, and ceilings. Present the samples on 8 by 10-1/2 inches boards (modules) with a maximum spread of 24 by 31-1/2 inches for foldouts. Design modules to fit in a standard loose-leaf, three-ring binder. Where special finishes such as architectural concrete, carpet, or prefinished textured metal panels are required, submit samples not less than 12 inches square with the board.
If more space is needed, more than one board per set may be submitted.
Certify that the color samples have been reviewed in detail, and that the color samples are in strict accordance with contract drawings and specifications, except as may be otherwise explicitly stated. Submittal of color samples does not relieve the Contractor of the responsibility to submit samples required elsewhere herein.
SECTION 01 30 00 Page 1
DEPARTMENT OF THE AIR FORCE
97TH AIR MOBILITY WING (AETC)
ALTUS AIR FORCE BASE OKLAHOMA
Notes: Application is only valid for 30 days after date of initiation. Issue Date of Pass: ____________________________ If this is for Windy Trails Golf Course, Rivers Elementary, Expiration/Denial Date: ________________________ or Education Center, then this will be made as an Altus Pass. FPCON Granted: _____________________________
Issued/Denied By: ____________________________ Approved/Denied until: ________________________
MEMORANDUM FOR 97 SFS/S5D
FROM: _________________________________ (Sponsor)
SUBJECT: Altus Air Force Base (AAFB) Defense Biometric Identification System (DBIDS) Card Application
1. I am requesting to sponsor the below individual for unescorted entry into Altus AFB between the following dates _________ - _________. This person will be conducting these services while on Altus AFB:
___________________________________________ for this company _________________________.
He/she requires base access during these times ________ - ________ and the days checked below:
Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Full Name: ________________________________________________________________
Date of Birth: ______________ State of Birth: _________ Country of Birth: ________________
Hair Color: _______ Eye Color: ________ Height: _____” Weight: ______lbs
Race: Caucasian African American Asian Hispanic
Other (specify): _______________________
Address: Apt #: _____ Street: __________________________ City: ________________
State: ____ Zip/Postal Code #: ____________________
Driver’s License/State ID #: ________________________________ SSN: ____________________
Cell/Home Phone #: __________________ Work/Supervisor’s #: _________________
2. I am sponsoring this person on behalf of ________________________________ (organization). Upon expiration of the pass, termination of their duties, or I am no longer sponsoring this individual, I will ensure my sponsored individual returns their card to Bldg #428/Visitor Center.
3. If there are any questions or concerns in regards to this application or sponsored individual, I can be contacted at my cell/work #: ___________ and/or e-mail at: _________________________. By signing this memorandum I have verified this person’s need for access to the installation and agree to take responsibility of this individual.
(Sponsor’s Signature)
1st Ind, _________________________ (Sponsored Individual’s First & Last Name)
MEMORANDUM FOR 97 SFS/S5D
I authorized the use and release of my personal information to Altus AFB, Oklahoma, to accomplish a national criminal background check to determine my ability to access Altus AFB. If I am denied access to the installation my signature below will constitute as my acknowledgement and is not an admission of guilt. I will receive a copy of this memorandum if denied.
(Sponsored Individual’s Signature)
This document contains FOR OFFICIAL USE ONLY (FOUO) information which must be protected under the Freedom of Information Act (5 U.S.C. 552) and/or the Privacy Act of 1974 (5 U.S.C. 552a).
Unauthorized disclosure or misuse of this PERSONAL INFORMATION may result in disciplinary action, criminal and/or civil penalties.
4. By initialing this section you agree to the terms and conditions of the Defense Biometric Identification System (DBIDS) Card Agreement ___________
PRE-ENROLLMENT
Waiting in line to register for DBIDS?
SCAN ME!
Fill out the application online and provide the confirmation code to the registrar to speed up your enrollment!
https://dbids-global-enroll.dmdc.mil/
1.4 VIEW LOCATION MAP
Submit, prior to or with the first digital photograph submittals, a sketch or drawing indicating the required photographic locations. Update as required if the locations are moved.
1.5 PROGRESS AND COMPLETION PICTURES
Photographically document site conditions prior to start of construction operations. Provide monthly, and within one month of the completion of work, digital photographs, 1600x1200x24 bit true color minimum resolution in JPEG file format showing the sequence and progress of work. Take a minimum of 20 digital photographs each week throughout the entire project from a minimum of ten different viewpoints selected by the Contractor unless otherwise directed by the Contracting Officer. Submit with the monthly invoice two sets of digital photographs, each set on a separate compact disc (CD) or data versatile disc (DVD), cumulative of all photos to date. Indicate photographs demonstrating environmental procedures.
Provide photographs for each month in a separate monthly directory and name each file to indicate its location on the view location sketch. Also provide the view location sketch on the CD or DVD as a digital file.
Include a date designator in file names. Photographs provided are for unrestricted use by the Government.
1.6 MINIMUM INSURANCE REQUIREMENTS
Provide the minimum insurance coverage required by FAR 28.307-2 Liability, during the entire period of performance under this contract. Provide other insurance coverage as required by [State ]law.
1.7 SUPERVISION
1.7.1 Superintendent Qualifications
Provide project superintendent with a minimum of [10][_____] years experience in construction with at least [5][_____] of those years as a superintendent on projects similar in size and complexity. The individual must be familiar with the requirements of EM 385-1-1 and have experience in the areas of hazard identification and safety compliance. The individual must be capable of interpreting a critical path schedule and construction drawings. The qualification requirements for the alternate superintendent are the same as for the project superintendent. The Contracting Officer may request proof of the superintendent's qualifications at any point in the project if the performance of the superintendent is in question.
For projects where the superintendent is permitted to also serve as the Quality Control (QC) Manager as established in Section 01 45 00 QUALITY CONTROL, the superintendent must have qualifications in accordance with that section.
1.7.2 Minimum Communication Requirements
Have at least one qualified superintendent, or competent alternate, capable of reading, writing, and conversing fluently in the English language, on the job-site at all times during the performance of Contract work. In addition, if a Quality Control (QC) representative is required on the Contract, then that individual must also have fluent English communication skills.
SECTION 01 30 00 Page 2
1.7.3 Duties
The project superintendent is primarily responsible for managing subcontractors and coordinating day-to-day production and schedule adherence on the project. The superintendent is required to attend Red Zone meetings, partnering meetings, and quality control meetings. The superintendent or qualified alternative must be on-site at all times during the performance of this contract until the work is completed and accepted.
1.7.4 Non-Compliance Actions
The Project Superintendent is subject to removal by the Contracting Officer for non-compliance with requirements specified in the contract and for failure to manage the project to ensure timely completion.
Furthermore, the Contracting Officer may issue an order stopping all or part of the work until satisfactory corrective action has been taken. No part of the time lost due to such stop orders is acceptable as the subject of claim for extension of time for excess costs or damages by the Contractor.
1.8 PRECONSTRUCTION
Immediately after award, prior to commencing any work at the site, coordinate with the Contracting Officer a time and place to meet for the Preconstruction. The must take place within 15 calendar days after award of the contract, but prior to commencement of any work at the site. The purpose of this is to discuss and develop a mutual understanding of the administrative requirements of the Contract including but not limited to:
daily reporting, invoicing, value engineering, safety, base-access, outage requests, hot work permits, schedule requirements, quality control, schedule of prices or earned value report, shop drawings, submittals, cybersecurity, prosecution of the work, government acceptance, final inspections and contract close-out. Contractor must present and discuss their basic approach to scheduling the construction work and any required phasing.
1.8.1 Attendees
Contractor attendees must include the Project Manager, Superintendent, Site Safety and Health Officer (SSHO), Quality Control Manager and major subcontractors.
1.9 FACILITY TURNOVER PLANNING MEETINGS (Red Zone Meetings)
Meet with the Government to identify strategies to ensure the project is carried to expeditious closure and turnover to the Client. Start planning the turnover process at the Pre-Construction Conference meeting with a discussion of the Red Zone process and convene at regularly scheduled NAVFAC Red Zone Meetings beginning at approximately 75 percent of project completion. Include the following in the facility Turnover effort:
1.9.1 Red Zone Checklist
a. Contracting Officer's Technical Representative (COTR) will provide the Contractor a copy of the Red Zone Checklist template.
b. Prior to 75 percent completion, modify the Red Zone Checklist template
SECTION 01 30 00 Page 3 by adding or deleting critical activities applicable to the project and assign planned completion dates for each activity. Submit the modified Red Zone Checklist to the Contracting Officer. The Contracting Officer may request additional activities be added to the Red Zone Checklist at any time as necessary.
1.9.2 Meetings
a. Conduct regular Red Zone Meetings beginning at approximately 75 percent project completion, or three to six months prior to Beneficial Occupancy Date (BOD), whichever comes first.
b. The Contracting Officer will establish the frequency of the meetings, which is expected to increase as the project completion draws nearer.
At the beginning, Red Zone meetings may be every two weeks then increase to weekly towards the final month of the project.
c. Using the Red Zone Checklist as a Plan of Action and Milestones (POAM) and basis for discussion, review upcoming critical activities and strategies to ensure work is completed on time.
d. During the Red Zone Meetings discuss with the COTR any upcoming activities that require Government involvement.
e. Maintain the Red Zone Checklist by documenting the actual completion dates as work is completed and update the Red Zone Checklist with revised planned completion dates as necessary to match progress.
Distribute copies of the current Red Zone Checklist to attendees at each Red Zone Meeting.
[ 1.10 EXPORT LICENSES FOR OVERSEAS PROJECTS
Obtain individual export licenses and project export licenses required by the Department of Commerce regulations ( 15 CFR 772 and 15 CFR 773 ) so that no delays are experienced in shipping from the United States of America to a foreign country. For additional information, the Contractor may contact one of the U.S. and Foreign Commercial Service District Offices of the Department of Commerce which are located in almost every State.
][ 1.11 WAIVER FOR WORKER'S COMPENSATION
In addition to FAR 52.228-4 Workers' Compensation and War-Hazard Insurance Overseas, the Secretary of Labor has granted a waiver. The waiver does not apply to employees who are hired in the United States, or who are residents, or citizens of the United States.
] 1.12 PARTNERING
[Host the partnering session within 45 calendar days of contract award.
]To most effectively accomplish this Contract, the Contractor and Government must form a cohesive partnership with the common goal of drawing on the strength of each organization in an effort to achieve a successful project without safety mishaps, conforming to the Contract, within budget and on schedule. The partnering team must consist of personnel from both the Government and Contractor including project level and corporate level leadership positions. Key Personnel from the supported command, end user, , Contractor, key subcontractors and the Designer of Record are required to participate in the Partnering process.
SECTION 01 30 00 Page 4
1.12.1 Team-Led (Informal) Partnering
a. The Contracting Officer will coordinate the initial Team-Led (Informal) Partnering Session with key personnel of the project team, including Contractor and Government personnel. The Partnering Session will be co-led by the Government Construction Manager and Contractor's Project Manager.
b. The Initial Team-led Partnering session may be held concurrently with the Pre-Construction meeting. Partnering sessions will be held at a location mutually agreed to by the Contracting Officer and the Contractor, typically at a conference room on-base or at the Contractor's temporary trailer.
c. The Initial Team-Led Partnering Session will be conducted and facilitated using electronic media (a video and accompanying forms) provided by Contracting Officer.
d. The Partners will determine the frequency of the follow-on sessions.
e. Participants will bear their own costs for meals, lodging and transportation associated with Partnering.
1.13 MOBILIZATION
Contractor shall mobilize to the jobsite within [60 calendar days after contract award] [30 calendar days of final site or building design approval]. Mobilize is defined as having equipment AND having a physical presence of at least one person from the contractor's team on the jobsite.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
SECTION 01 30 00 Page 5
SECTION 01 31 23.13 20
ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT MANAGEMENT SYSTEM
(eCMS)
08/23, CHG 1: 02/24
PART 1 GENERAL
1.1 CONTRACT ADMINISTRATION
Utilize the Naval Facilities Engineering Systems Command's (NAVFAC's) Electronic Construction and Facility Support Contract Management System (eCMS) for the transfer, sharing, and management of electronic technical submittals and documents. The web-based eCMS is the designated means of transferring technical documents between the Contractor and the Government. Paper media or email submission, including originals or copies, of the documents are not permitted unless identified within the contract.
All government contracting specialist/officer, legal, and command communications will remain the same.
1.2 USER PRIVILEGES
The Contractor's key staff may be provided access to eCMS. Contact the COR for eCMS account access. Project roles and system roles will be established to control each user's menu, application, and software privileges, including the ability to create, edit, or delete objects.
Additional project roles may be assigned for workflow. The COR makes the final decision on roles for the project. User's ability to view, edit documents may be lowered at the discretion of the COR.
Only one eCMS user account is required regardless of the number of user's projects. Notify the COR within seven calendar days if a contractor user is no longer associated with company or project so they can remove them from any open record and inactivate them from the project.
1.2.1 eCMS Subcontractor Users
If the contractor's user is a subcontractor, the subcontractor must be registered under the name of their company and email. For example it is common for contractors to contract Quality Control Managers. The QC Manager's account should be under their company's name and email reducing the number of eCMS accounts required.
1.2.2 Users with Multiple Roles
Users may have multiple roles associated with their account within eCMS.
Roles are used in workflow. When a user is added to the project, they will be assigned the default role when the user was created. Contact the COR to change or add roles to the user for the project.
1.2.3 Loss of Privilege
Users may lose privilege to access eCMS at the discretion of the Contracting Officer. The eCMS is a collaborative system that allows flexibility of use and does not restrict all inappropriate user actions.
User activities are logged into eCMS in visible and background data
SECTION 01 31 23.13 20 Page 1 collection. Users found to use eCMS in an inappropriate action may have their eCMS access revoked. Examples include, but not limited to, fraudulent representations, sharing user accounts with others, and changing approved records without the consent of the COR. Depending on the severity of the infraction, the users can lose eCMS access for a period of time, permanently for the project, or lose eCMS access for any project. The contractor may appeal the suspension in writing to the contracting officer within 14 calendar days of notice. The appeal must identify the infraction, supporting information, and steps to ensure the infraction will not happen in the future.
1.3 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
List of Contractor's Personnel ; G
For Division 1 government approved Pre-Construction submittals, combine into a single Pre-Construction Submittal Package.
Annotated with SD Type of SD-01. Pre-Construction submittal package approval date will be used as a KPI.
1.4 SYSTEM REQUIREMENTS AND CONNECTIVITY
1.4.1 General
NAVFAC eCMS requires a web-browser (platform-neutral) and Internet connection. For best results, recommend using browser in InPrivate/Incognito mode; Internet speeds greater than 40mbps when uploading files, computers with high RAM and Solid State Drives, "White List" eCMS website, Zip or Split files for better uploading. Non-NAVFAC Users are not to use VPN when using eCMS per NAVFAC IT.
The use of eCMS is required by the Contractor and all associated costs and time necessary to utilize eCMS will be borne by the Contractor with no allowance for time extensions and at no additional cost to the government.
1.4.2 Contractor Personnel List
Within 20 calendar days of contract award, provide to the Contracting Officer a list of Contractor's personnel who will have the responsibility for the transfer, sharing and management of electronic submittals, RFIs, daily reports, and other files and will require access to the eCMS.
Project personnel roles which must be filled as applicable in the eCMS, include, at a minimum, the Contractor's Project Manager (KTR-PM), Superintendent (KTSUPT), Quality Control (QC) Manager (KTR-QC), Principal (KTR-PRIN), and Site Safety and Health Officer (KTR-SSHO). Notify the COR immediately of any personnel changes to the project. The Contracting Officer reserves the right to perform a security check on all potential users.
Internal design deliberations under a D-B contract are managed outside of eCMS. Besides the D-B DOR Representative, D-B design team members are neither required nor encouraged to create user accounts in eCMS. Users
SECTION 01 31 23.13 20 Page 2 are highly recommended to take eCMS live or online training prior to use.
See https://www.navfac.navy.mil/Business-Lines/Design-and- Construction/About-Us/Design-and-Construction-Documents/Electronic- Construction-Management-System-eCMS/ for eCMS useful information
Provide the following information:
Company Name
Name (First, Last)
Email Address
Project Role (CQM, SSHO, Superintendent, CM, PM, Principal)
Existing or New eCMS User
1.5 SECURITY CLASSIFICATION
In accordance with Department of Navy guidance, all military construction contract data are unclassified, unless specified otherwise by a properly designated Original Classification Authority (OCA) and in accordance with an established Security Classification Guide (SCG). Refer to the project's OCA when questions arise about the proper classification of information.
In conformance with the Freedom of Information Act (FOIA), DoD INSTRUCTION 5200.48 CONTROLLED UNCLASSIFIED INFORMATION (CUI), and DoD requirements, any unclassified project documentation uploaded into the eCMS must be designated either "U - UNCLASSIFIED" (U) or "CUI - CONTROLLED UNCLASSIFIED INFORMATION" (CUI).NAVFAC eCMS must only be used for the transaction of unclassified information associated with construction projects. Controlled Unclassified Identification (CUI) documents may be loaded into eCMS with the appropriate markings.
1.5.1 Markings on CUI Documents
Contractor's proprietary information, or documents determined by the originator in accordance with CUI guidance, should be marked CUI.
Proprietary information not marked CUI can be released under the Freedom of Information Act (FOIA). Apply the appropriate markings before any document is uploaded into eCMS. Markings are not required on Unclassified U documents.
1.6 eCMS UTILIZATION
Establish, maintain, and update data and documentation in the eCMS throughout the duration of the contract. Utilize eCMS to transfer all submittals, RFIs, daily reports, and other files required by contract to be forwarded to the government.
Full eCMS use is required. All Submittals/Information to use eCMS Modules including, but not limited to, RFIs, Daily Reports, Meeting Minutes, Communications, Issues, Punch Lists, Checklists, and Flysheets, unless otherwise directed by the COR or Contracting Officer.
1.6.1 Restricted Information
Personally Identifiable Information (PII) transmittal such as credit card, SECTION 01 31 23.13 20 Page 3 driver's license, passport, social security, and payroll number are not permitted in eCMS. Name, address, and email are permitted.
Pre-negotiation information such as cost estimates that require formal negotiations are not allowed. For example, proposed changes over the SAP level of $250k require formal negotiations. Cost estimates for LEAN, ULTRA LEAN, and Design Changes under the SAP level are at the discretion of the COR's or Contract Specialist/Officer's direction. The eCMS must only be used for the transaction of unclassified information associated with construction projects. Controlled Unclassified Identification (CUI) documents may be loaded into eCMS with the appropriate markings.
Uploading of files directly into the Documents folder is not allowed. All documents must be uploaded using an eCMS module.
1.6.2 Naming Convention for Files
Titles of files uploaded are to be descriptive of the purpose and content of the file. For example RFI_ROOF_Leak.doc or for submittals, SUB_LIGHT_FIXTURE.pdf. Titles of file to be uploaded must only contain uppercase letters, lowercase letters, numbers, hyphens (-), underscores (_) and periods (.). Use of any other characters is not allowed and may create an error. When practicable, adding the record number to the title is desired. For example RFI_XYZ12345_ROOF_Leak.doc. Uploading files with the same title will create a new revision in eCMS. Original revision is Rev 0, the first revision is Rev 1. Uploaded files are to use the default file location regardless of the module used unless directed by the COR.
Table 1 also identifies which eCMS application is to be used in the transmittal of data (these are subject to change based on the latest software configuration).
Table 1 - Project Documentation Types
SUBJECT/NAME REMARKS eCMS APPLICATION
As-Built Drawings Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager
Submittals
Building Information Modeling (BIM)
Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager
Submittals
Construction Permits Refer to rules of the issuing activity, state or jurisdiction
Submittals
Construction Schedules (Activities and Milestones)
Submittals
SECTION 01 31 23.13 20 Page 4
SUBJECT/NAME REMARKS eCMS APPLICATION
Construction Schedules Submittals
Construction Schedules (3-Week Look ahead)
Import the schedule file into the scheduling application, and select "Approve" to establish a new schedule baseline
Meeting Minutes
DD 1354 Transfer of Real Property
When applicable, required for final billing.
Submittals
Daily Production Reports
Provide weather conditions, crew size, man-hours, equipment, and materials information
Daily Report
Daily Quality Control (QC) Reports
Provide QC Phase, Definable Features of Work Identify visitors
Daily Report
Designs and Specifications
Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager
Submittals
Environmental Notice of Violation (NOV), Corrective Action Plan
Refer to rules of the issuing activity, state or jurisdiction
Submittals
Environmental Protection Plan (EPP)
Submittals
Invoice (Supporting Documentation)
Applies to supporting documentation only. Invoices are submitted in Wide-Area Workflow (WAWF)
Submittals
Jobsite Documentation, Bulletin Board, Labor Laws, SDS
Redact any PII information when loaded into eCMS
Submittals
Meeting Minutes Meeting Minutes
Modification Documents Provide final modification documents for the project. Upload into Modifications RFPs folder
Communications
SECTION 01 31 23.13 20 Page 5
Operations & Maintenance Support Information (OMSI/eOMSI), Facility Data Worksheet
1. Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager
2. Design reviews will be performed in existing "Dr Checks"
Submittals
Photographs Subject to base/installation restrictions Submittals
QCM Initial Phase Checklists
Meeting Minutes or Checklists
QCM Preparatory Phase Checklists
Meeting Minutes or Checklists
Quality Control Plans Submittals
QC Certifications Submittals
QC Punch List Punch Lists
Red-Zone Checklist Punch List or Checklists
Rework Items List Punch Lists
Request for Information (RFI) Post-Award
RFIs
Safety Plan Submittals
Safety - Activity Hazard Analyses (AHA)
Submittals
Safety - Mishap Reports Daily Report
Shop Drawings Locations of sensitive areas must be labeled as either "Controlled Area" or "Restricted Area" and may be shown on unclassified documents with the approval from Site Security Manager
Submittals
SECTION 01 31 23.13 20 Page 6
Storm Water Pollution Prevention (Notice of Intent - Notice of Termination)
Refer to rules of the issuing activity, state or jurisdiction
Submittals
Submittals and Submittal Register
Submittals
Testing Plans, Logs, and Reports
Submittals
Training/Reference Materials
Submittals
Training Records (Personnel)
Redact any PII information if storing in eCMS
Submittals
Utility Outage/Tie-In Request/Approval
Submittals
Warranties/BOD Letter Submittals
Quality Assurance Reports
Checklists (Government initiated)
Non-Compliance Notices Non-Compliance Notices (Government initiated)
Other Government-prepared documents
GOV ONLY
Letters to government contracting, claims, REAs, and other contracting officer communications eCMS is not the primary tool to use in contracting officer communications. eCMS can only store documents or letters after the submission to the contracting officer is made.
Communications
All Othere Documents Refer to FOIA guidelines and contact the FOIA official to determine whether exemptions exist
As applicable
1.6.3 RFIs Module
Create contractor RFIs using eCMS RFIs module. The contractor must confirm the numbering convention with the COR if different than eCMS default.
SECTION 01 31 23.13 20 Page 7
If the government (GOV) Response has "No" Cost or Schedule Impact, this reply is given with the expressed understanding that it does not constitute a basis for any change in the amount or time of subject contract. Information provided in this response does not authorize work not currently included in the contract. If GOV Response is "Yes" or "Potentially" then this response may require a change to the contract. If the contractor disagrees with either the government's No Cost determination or No Schedule impact determination, or both, the contractor has 14 calendar days to notify the COR and Contracting Officer in writing.
1.6.4 Submittals Module
Create contractor submittals using eCMS Submittals module. The contractor must confirm the numbering convention with the COR if different than eCMS default.
1.6.5 Submittal Packages Module
Create submittal packages using the eCMS Submittal Packages module in lieu of or in addition to Related Objects. Submittal Packages track completion of the packaged submittals and is used in NAVFAC HQ's KPIs.
1.6.6 Communications Module
Create communications using the eCMS Communications module. The Communications module is used to create or document communications that are not a part of other eCMS modules. Use of Communications module will memorialize information into an eCMS record file. The following are Types of Communications:
Memo to File
Face to Face
Telephone
Web Collaboration
Photos
Other Documents
Other
Unless directed by the COR, upload documents or files that do not have a corresponding eCMS module. Choose "Photos" Type for Photos and "Other Documents" for all other documents.
1.6.7 Issues Module
Create or respond to issues using the eCMS Issues module. Respond to CPARS issues using the Issues module.
1.6.8 Meeting Minutes Module
Create or respond to Meeting Minutes using the eCMS Meetings module.
SECTION 01 31 23.13 20 Page 8
Document required contractual meetings. Dates of meetings are used in NAVFAC KPIs. Minimum meetings in eCMS include the following:
Post Award Kickoff (PAK)
Pre-construction (Pre Con)
Initial and Preparatory Three Phases of Control
Quality Control (QC)
1.6.9 Potential Change Items Module
Not used.
1.6.10 Daily Report Module
Create Daily Reports using the eCMS Daily Report Module. The contractor must confirm the numbering convention with the COR if different than eCMS default.
1.6.11 Punchlists Testing Logs (Legacy)
Punchlist Testing Logs is a legacy program that is being replaced by the Punch Lists Module. This module is to be used for reference of past projects. Use the Punch Lists Module for all future work.
1.6.12 Punch Lists Module
The eCMS Punch Lists module is useful more than just for Punchlists. The module includes the capability of batch editing, create items from Optical Character Recognition (OCR) plans, assign tasks and track completion of individual items.
Create the following using the Punch Lists module:
Rework Items List
DFOW List
Punch-Out Inspection
Pre-Final Punchlist Inspection
Final Punchlist Inspection
Testing Logs
1.6.13 FWD UltraLean COAR RFP Module
Not used.
1.6.14 Non-Compliance Notices (NCN) Module
Respond to Non-Compliance Notices listed in the Non-Compliance Notices module.
SECTION 01 31 23.13 20 Page 9
1.6.15 Checklists
Use Checklist listed in the contractor's eCMS menu and as directed by the COR. Checklists capture data and is used in dashboards and KPIs.
1.6.15.1 Partnering Team Health Survey Checklist
Contractor must use the eCMS checklist to document the partnering team health survey. Partnering Team Health Survey is in accordance with the Partnering Specification of this contract.
1.6.16 Flysheets
Use Flysheets listed in the contractor's eCMS menu, if available, and as directed by the COR. Flysheets allow the contractor to print out information from other systems and upload into eCMS. The eCMS will use OCR to capture the information as data. Flysheets capture data and used in dashboards and KPIs.
1.6.17 eCMS Outage
In the case where eCMS is unavailable for 8 hours or more, paper or email may be used in the interim to maintain project schedule.
Once the system is operational, all final records are required to be recreated using the appropriate module. Subject/title of the record to include the type of record i.e., RFI/Submittal/Daily Report/Communication/Other, the identification number(s), and the statement "Processed Outside of eCMS". Example, "RFI 001 Processed Outside of eCMS".
1.6.18 User Account Activity
NAVFAC eCMS captures user data and activities that are directly related to the user's account. The user agrees through the use of eCMS, their account activities will be captured and can be displayed on eCMS printed reports.
1.7 QUALITY ASSURANCE
Requested Government response dates on Submittals must be in accordance with the terms and conditions of the Contract unless previously agreed by the COR. Requesting response dates earlier than the required review and response time, without concurrence by the Government COR, may be cause for rejection.
Incomplete submittals will be rejected without further review and must be resubmitted. Required Government response dates for resubmittals must reflect the date of resubmittal, not the original submittal date.
All submittals and associated attachments must be transmitted to the Government via the COR. Transmittals are no longer required when using eCMS since approval status is tracked on the submittal. Transmittal forms can be attached to submittals if approved by the COR. Submittals requiring government approval are "Transmitted For" "Approval".
Submittals requiring contractor approved submittals, including those designated for Contractor Quality Control approval or Information Only, are "*Transmitted For" "Information Only" in the Submittal Module.
Provide and sign the QC certification or approving statement on the
SECTION 01 31 23.13 20 Page 10 attachment per submittal specification section. When Submittal Packages are required, use eCMS Submittal Packages after creating individual submittals. Importing Submittals from the Submittal Register is optional. Contact the COR for the data conversion requirements.
PART 2 PRODUCTS
Not used.
PART 3 EXECUTION
Not used.
SECTION 01 31 23.13 20 Page 11
SECTION 01 32 01.00 10
PROJECT SCHEDULE
08/23, CHG 1: 08/24
PART 1 GENERAL
1.1 REFERENCES
The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.
AACE INTERNATIONAL (AACE)
AACE 29R-03 (2011) Forensic Schedule Analysis
AACE 52R-06 (2006) Time Impact Analysis - As Applied in Construction
AACE 84R-13 (2015) Planning and Accounting for Adverse Weather
AMERICAN SOCIETY OF CIVIL ENGINEERS (ASCE)
ASCE 67-17 (2017) Schedule Delay Analysis
U.S. ARMY CORPS OF ENGINEERS (USACE)
ER 1-1-11 (2017) Administration -- Project Schedules
1.2 SUBMITTALS
Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:
SD-01 Preconstruction Submittals
Preliminary Project Schedule ; G
Initial Project Schedule ; G
Periodic Schedule Update ; G
1.3 PROJECT SCHEDULER QUALIFICATIONS
Designate an authorized representative to be responsible for the preparation of the schedule and all required updating and production of reports. The Designated Project Scheduler must have prepared and maintained at least three previous construction schedules for projects of similar size and complexity to this contract, using Primavera P6..
Representative must have a comprehensive knowledge of CPM scheduling principles and application.
SECTION 01 32 01.00 10 Page 1
PART 2 PRODUCTS
2.1 SOFTWARE
The scheduling software utilized to produce and update the schedules required herein must be capable of meeting all requirements of this specification.
2.1.1 Government Default Software
The Government uses Primavera P6. Ensure exported schedule files are compatible with the version of P6 used by the Government.
2.1.2 Contractor Software
Scheduling software used by the contractor must be commercially available from the software vendor for purchase with vendor software support agreements available. The software routine used to create the required sdef file must be created and supported by the software manufacturer.
2.1.2.1 Primavera
If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.
2.1.2.2 Other Than Primavera
If the Contractor chooses software other than Primavera P6, that is compliant with this specification, provide for the Government's use two licenses, two computers, and training for two Government employees in the use of the software. These computers will be stand-alone and not connected to Government network. Computers and licenses will be returned at project completion.
PART 3 EXECUTION
3.1 GENERAL REQUIREMENTS
Prepare for approval a Project Schedule, as specified herein, pursuant to FAR Clause 52.236-15 Schedules for Construction Contracts. Show in the schedule the proposed sequence to perform the work and dates contemplated for starting and completing all schedule activities. The scheduling of the entire project is required. The scheduling of construction is the responsibility of the Contractor. Contractor management personnel must actively participate in its development. Subcontractors, and suppliers working on the project must also contribute in developing and maintaining an accurate Project Schedule. Provide a schedule that is a forward planning as well as a project monitoring tool. Use the Critical Path Method (CPM) of network calculation to generate all Project Schedules.
Prepare each Project Schedule using the Precedence Diagram Method (PDM).
3.1.1 Scheduling Expectations Kickoff Meeting(SEKO)
In conjunction with the post award conference or pre construction conference the Government and the Contractor will hold a separate and distinct Scheduling Expectations Kickoff Meeting(SEKO). The intent of this meeting is for the Government to review with the contractor the
SECTION 01 32 01.00 10 Page 2 requirements of the scheduling specification, communicate the Government’s expectations regarding schedule development and management, and answer any questions the Contractor may have regarding the schedule requirements.
3.2 BASIS FOR PAYMENT AND COST LOADING
The schedule is the basis for determining contract earnings during each update period and therefore the amount of each progress payment.
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 .