B08_Atch_6_-_Proj_Mgt_Software_and_Electronic_Payrolls_Requirement.pdf

Attachment to the Specifications:

PROJECT MANAGER SOFTWARE PROGRAM

The Contractor shall provide a project management program that has real-time work management features that support Task Management, Team Collaboration and Document Management. The project management program shall be software stored, managed and processed on a network of remote servers hosted on the Internet in which software is accessed online via subscription. Example programs include but are not limited to: Procore; Project Team;

Wrike; etc.

At a minimum program features shall include:

1) Project Document Management:

a. Unlimited Storage;

b. Unlimited Users;

c. Document Tracking – disposition of documents in review, pending actions from users per workflow, revisions, etc.;

d. Document and Folder Permissions granted to administrators who can choose the level of access and permissions for users per each project;

i. Administrators will be Owner/National Park Service (NPS) personnel;

ii. Users will include NPS personnel and external NPS personnel;

iii. External NPS entities include the Construction Contractor (Contractor), Construction Management Representative (CMR), and Architect-Engineer (AE);

e. Provide access to the program 24 hours per day, 7 days a week, except for maintenance activities. Maintenance activities shall be coordinated to occur outside of normal working hours, with email notification to users at least 48 hours prior to any activities that limit user document access;

f. Ability to reference/link/tag project documents to other project documents to establish a record link; and

g. Allow for the search of names, description, document type, document disposition, and contents of documents within the documents tool.

h. Provide ability for administrators and permissible users to cancel a workflow and/or identify documents as obsolete.

i. Promotes ability to manage documents remotely using mobile devices.

j. Promotes ability to manage documents using email only, without logging into/accessing the system.

2) Project Directory/post-log-in view/Dashboard:

a. Provide access to multiple projects per each user as defined by administrators;

b. Provide user directory with emails and ability to assign to an organization (i.e. NPS, Contractor, CMR, or AE);

c. Provide access to Submittals, Requests for Information (RFIs), Schedule, Drawings, Specifications, Meeting Minutes, Daily Reports/Logs, and Photographs; and

d. Provide a listing or access to a listing or report of and with linkages to submittals, RFIs, tasks, etc. that are pending user action/input including the date the task is due per Submittal or RFI workflows.

3) Submittals:

a. General

i. Provide ability to upload, download, view, and automatically route Informational and Action Submittal documents per each workflow;

ii. Provide user ability to select submittal disposition type when routing.

iii. Provide administrators ability to manage user permissions to modify workflow duration dates and default review periods per each project;

iv. Provide administrators ability to manage user permissions to modify email notification settings to include other users per each project;

v. Provide notifications when an item becomes a user’s responsibility including the due date of the item and ability to provide more frequent notifications as selected by administrators;

vi. Provide ability to sort submittals by specification section, information or action submittal, date, or submittal disposition;

vii. Provide ability to track and document workflow processes, user action(s), document sent/received times/dates, document disposition etc.; and

b. Informational Submittals:

i. The Default Informational Submittal Workflow is as follows:

1. Start workflow – Contractor can create/start, then route to NPS

2. Option for NPS to assign/route to Contractor, or AE;

3. If routed to Contractor, or AE, they route back to NPS and

4. From NPS to Contractor – end workflow.

ii. Default Informational Submittal review duration:

1. NPS Information Submittal workflow of ten (10) days.

iii. The NPS selects the disposition type during their transmittal to the contractor in the workflow, with disposition types as follow:

1. Accept; or

2. Reject;

c. Action Submittals:

i. The Default Action Submittal sequential workflow is as follows:

1. Start workflow – Contractor can create/start, then route to NPS

2. Option for NPS to assign/route to AE or Disapprove and route to Contractor for their re-submittal;

3. If routed to the AE, the AE routes back to NPS; and

4. NPS selects deposition and routes to Contractor – end workflow.

ii. Default Action Submittal review durations:

1. NPS Action Submittal workflow of thirty (30) days;

2. NPS Action Re-Submittal workflow of thirty (30) days; and

3. AE review time for Action Submittal workflow of twelve (12) days.

iii. The AE selects disposition types during their transmittal in the workflow and the NPS concurs with the transmittal to the contractor in the workflow, with disposition types as follow:

1. Approved;

2. Approved with Notations;

3. Disapproved – Resubmit;

4) RFIs:

a. Provide ability to upload, download, view, and automatically route RFI documents per the following default sequential workflow;

i. Start workflow – Contractor, NPS, or CMR can create/start, then route to NPS

ii. Option for NPS to route back to Contractor or AE;

iii. If routed to the AE, the AE routes back to NPS and;

iv. From NPS to Contractor – end workflow;

b. Provide administrators ability to modify workflow duration dates per each project;

i. Default NPS review time for RFI workflow is fourteen (14) days;

ii. Default AE review time for RFIs is seven (7) days;

c. Provide administrators ability to modify email notification settings to include other users per each project;

d. Provide notifications when an item becomes a user’s responsibility including the due date of the item and ability to provide more frequent notifications as selected by administrators;

e. Provide ability to track and document workflow processes, user action(s), document sent/received times/dates, etc.; and

f. Provide ability to track and document review comments and responses.

5) Project Schedule:

a. Provide ability to upload baseline schedule and schedule updates from, but not limited to, Primavera P6 and Microsoft Project file formats;

b. Provide ability to view uploaded schedules in Gant or calendar (i.e. user-selectable by year, month, week, and day) formats, including activity starts/ends and milestone dates; and

c. Provide ability for users to view multiple project schedules that they have permissions/access to within a view or report.

6) Drawings:

a. Provide ability to upload, download, and view drawings.

7) Specifications:

a. Provide ability to upload, download, and view specifications.

8) Meeting Minutes:

a. Provide ability to upload, download, and view meeting agendas and minutes.

9) Daily Reports/Logs

a. Provide ability to upload, download, and view daily logs, site visit memos, inspection reports, testing documents, etc.

10) Punch-List Items:

a. Provide ability to upload, download, and view Punch-List items

11) Photographs:

a. Provide ability to upload, download, and view photographs;

b. Allow attachment/linking of photos to drawings, punch list items, and other records;

c. Support the capture and upload of photos from mobile devices; and

d. Automatically aggregate project photos captured in other documents such as daily logs into the photo album.

Access to the website, from any internet-connected device, 24 hours a day, 7 days a week, is required for all project participants and collaborators at no additional costs.

The CO shall determine permission and access for each party.

The Contractor shall establish and submit personnel security requirements for Project Management Program staff to the Government for review and approval.

Data Ownership: The Government shall retain ownership of all data. The system shall permit stakeholders the ability to download a copy of the data at any time. Within 14 days of Substantial Completion the Contractor shall download all stored data and email it to the Contracting Officer and COR. In addition, the Government shall be able to access the site up to 3 months after issuance of Substantial Completion.

CONTRACTOR TO SUPPLY AND USE AN ELECTRONIC SOFTWARE FOR

PROCESSING WAGE RATES (CONSTRUCTION) CERTIFIED PAYROLLS IN

COMPLIANCE WITH FAR 52.222-8, PAYROLLS AND BASIC RECORDS AND FAR

52.222-13, COMPLIANCE WITH WAGE RATES (CONSTRUCTION) AND RELATED

REGULATIONS.

The contractor shall submit post award the proposed software systems that comply with the performance requirements above via CM-16 for COR and CO review.