M67861-14-T-0072.doc

Section SF 1449 - CONTINUATION SHEET

ADDENDA

This is a Request for Proposals for commercial Software as a Service Project Time Reporting System for the Marine Corps in accordance with the Statement of Work incorporated herein. The government will solicit and award a single Firm-Fixed-Price contract using Simplified Acquisition Procedures in accordance with FAR Part 12, Acquisition of Commercial Items, and FAR Subpart 13.5, Test Program for Certain Commercial Items.

Addenda to FAR 52.212-1, Instructions to Offerors

This requirement is unrestricted; the applicable North American Industry Classification System (NAICS) Code is 518210 and the standard size is $32.5 mil in annual receipts.

PRESOLICITATION INSTRUCTIONS

A.1. The government will consider proposals submitted under GSA contracts. Any conflicts between this solicitation and the terms and conditions of the GSA contract shall be clearly identified in the Offeror’s proposal.

A.2. Award will be made on an all-or-none basis.

A.3. Type of Contract: The Government contemplates award of a single Firm-Fixed-Price contract with a base year period and four option years as a result of the proposals received from this solicitation. The solicitation will require Offeror’s proposals to price Options which will be included in the overall evaluation of offers for award in accordance with Federal Acquisition Regulation (FAR) 52.212-2.

A.4. Offerors are requested to thoroughly review the requirements of this solicitation and no later than

September 11, 2014 at 2:00PM CST submit any questions, in writing, electronically to Irving Romero at the following email address: irving.romero@usmc.mil . Subject Line shall reference: Questions – M67861-14-T-0072. All questions and answers shall be posted by the government to the Federal Business Opportunities (FBO) website.

This solicitation is only available via Federal Business Opportunities www.fedbizopps.gov; offerors shall:

1.

Check FEDBIZOPPS periodically for amendments.

2.

Ensure they download all documents. This solicitation contains five attachments.

In accordance with DFARS 252.232-7006, invoices under the contract are to be submitted electronically via Wide Area Workflow (WAWF). Specific instructions for invoicing through WAWF are contained in the solicitation.

Offerors shall submit representations and certifications electronically at http://orca.bpn.gov/. Certification is required prior to submission of the quotation. Offerors shall state in their quotation that certification in ORCA is current, complete and accurate as of the date of contractor’s signature or list any changes. Offerors are responsible for reviewing the solicitation document carefully as additional certifications may require completion throughout this document.

A.5. Closing Date. The solicitation closes on September 16, 2014 at 12:00PM CST.

A.6. Submission of Proposals:

Proposals must be returned to the address listed below at the date and time specified in block #8, Page 1 of this solicitation document. Proposals may be submitted via email, hand-carried, or submitted by mail through the U.S. Postal Service or by courier express (FedEx, UPS, etc.). The Government reserves the right to make award solely on initial proposals received. Offerors bear the burden of ensuring that proposals (and signed copies of solicitation amendments, if issued) reach the designated office on time. All portions of the quotation must reach the office before the deadline specified in this solicitation. Proposals shall be delivered as follows:

If hand carried, sent via courier express, or mailed through the U.S. Postal Service:

Marine Forces Reserve

Regional Contracting Office

Attn: SSgt Irving Romero

2000 Opelousas Avenue, New Orleans, LA, 70114

If submitted via email: irving.romero@usmc.mil

A.7. Attachments

(1) TSO Time Labor Reporting Guidelines

(2) Past Performance Questionnaire

(3) LRS ERD

(4) Performance Requirements Summary.

(5) Quality Assurance Surveillance Plan.

A.8. FORMAT AND CONTENT OF PROPOSALS

a.

Proposals are not limited to a minimum or maximum number of pages.

b.

Content of Proposals:

(i) Standard Form of Contract (SF 1449). Blocks 17a, 30b, and 30c of page 1 of Standard forms 1449 shall be completed by offerors and Block 30a shall be signed to show the offeror has read and agrees to comply with all terms, conditions, and instructions provided in the solicitation document.

(ii) Annual Representations & Certifications. Offerors shall provide a statement that certification in On-Line Representations and Certifications Application (ORCA) website, https://orca.bpn.gov/ , is current, complete, and accurate as of the date of the offeror’s signature, or list any changes.

(iii) Amendments. Acknowledgement of all amendments issued.

(iv) Proposals shall address each factor as identified below:

1) Technical Capability – Comprehensive, practical, legible and coherent responses are necessary to evaluate the offeror’s capability to meet the stated requirements. General statements that the offeror can comply with the requirements will not by themselves, be adequate. Responses shall also include the completion of the Section 508 Government Product Accessibility Template.

2) Past Performance. Submit Past Performance information in accordance with Factor (a)(i) under addenda to FAR 52.212-2, ‘Evaluation – Commercial Items’ utilizing Attachment 2.

3) Pricing.

i.

Price proposals shall be evaluated for the presence of ‘unbalanced pricing’ based on a contractor’s attempt to ‘buy in’ to the acquisition. The Contracting Officer shall perform a price proposal analysis to determine fair and reasonable pricing. The Contracting Officer reserves the right to reject an offer if it is determined that the lack of balanced pricing poses an unacceptable risk to the Government in accordance with FAR Part 15.404-1(g).

A.9. Award: The Government reserves the right to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror’s initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received

A.10. Period of Acceptance of Offerors: Offerors agree to hold their prices firm for a period of sixty (60) days.

A.11. Failure to submit any of the information requested by this solicitation may be cause for unfavorable consideration.

Addenda to FAR 52.212-2, Evaluation Factors for Award

A.13. FAR 52.212-2 EVALUATION – COMMERCIAL ITEMS (JAN 1999)

(a) The Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors, listed in descending order of importance, shall be used to evaluate offers:

(i) Technical Capability (includes Section 508 compliance)

(ii) Past Performance – Past performance information, when included as an evaluation factor, to include recent and relevant contracts for the same or similar items and other references (including contract numbers, points of contact with telephone numbers and other relevant information);

(a) Offerors shall supply information to permit the Government in evaluating the Contractor’s past performance. Offerors shall send out copies of the Past Performance Questionnaire, provided as Attachment 2, to at least three of the offeror’s customers (Government Agencies or private businesses) for recent and relevant contracts for the same or similar services. Alternately, if the offeror does not have relevant contracts, it should forward the questionnaire to three of its current customers or three customers it has provided services in the last three years. The customer will complete the questionnaire and submit it directly to the Contract Specialist prior to the due date of quotes. OFFERORS SHALL FOLLOW UP WITH THOSE CUSTOMERS TO ENSURE THEY SUBMIT THE COMPLETED FORMS DIRECTLY TO THE CONTRACT SPECIALIST. Please have your references complete and fax or email past performance questionnaires to: Fax (504) 697-9742 Attn: SSgt Irving Romero or via email to: irving.romero@usmc.mil

(iii) Price

(a) The Government will evaluate for (1) price reasonableness and (2) balanced pricing.

The government will utilize a price evaluation factor based on loss of productivity and time due to retraining and testing of application; the prices for these categories will not be added to the contract price.

Award will be based on the best value to the government utilizing price/technical tradeoff. Technical, and past performance, when combined, are significantly more important than price; however, price will be found to be increasingly more important when offerors receive similar ratings for the non-price factors. Offerors must satisfy the requirements described in the evaluation criteria, as well as all other RFQ requirements. The Government reserves the right to conduct oral presentations. Presentations may be conducted electronically via video teleconference (VTC), webinar, etc.

(b) Options. The Government will evaluate offers for award purposed by adding the total price for all options to the total price for the basic requirement. The Government may determine that an offer is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).

(c) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the Government may accept an offer whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

Replicon TimeBill - Brand name or equal

FFP

Base Year

Time Keeping System

550 seats required

See Performance Work Statement herein for technical specifications

FOB: Destination

MILSTRIP: M0009414RC00025

NET AMT

Initial Configuration/Implementation

FFP

Offerors shall include an itemized break down of all costs associated with setup, configuration, and implementation.

See Performance Work Statement herein for technical specifications

MILSTRIP: M0009414RC00025

NET AMT

FFP

Option Year 1

Time Keeping System

550 seats required

See Performance Work Statement herein for technical specifications

NET AMT

FFP

Option Year 2

Time Keeping System

550 seats required

NET AMT

FFP

Option Year 3

Time Keeping System

550 seats required

NET AMT

FFP

Option Year 4

Time Keeping System

550 seats required

NET AMT

STATEMENT OF WORK

Performance Work Statement PROJECT TITLE: SOFTWARE AS A SERVICE PROJECT TIME REPORTING SYSTEM FOR THE MARINE CORPS TECHNICAL SERVICES ORGANIZATION

1. Background The Marine Corps Technology Services Organization (TSO) develops and maintains Human Resource (HR), Payroll and Financial Management applications that service both active and reserve Marines. These critical applications are developed within strict Capability Maturity Model Integration (CMMI) level 3 standards. All application changes are estimated for effort in all phases of the Software Development Lifecycle (SDLC). Actual hours are tracked per application change and compared against the estimated effort to provide burn reports to software development managers. Non-billable hours are also tracked to include training time, holiday hours, vacation and administrative time off.

The development of Project time reporting systems is not a key competency of the TSO) and, therefore, is not best suited to develop and/or maintain such systems. Additionally, the accreditation and certification process timeline for software installed on Marine Corps hosted systems exceeds the cost of procuring a labor hours tracking system. Procuring a Project Time Reporting system as a service is the most cost effective solution for the Marine Corps TSO project time reporting needs.

A future requirement will be to utilize the Project Time Reporting System Software as a Service (SaaS) to track time-off requests and overtime authorizations for the employees within the TSO. The Project Time Reporting System SaaS will also be utilized to provide a payroll ready file to the DoD’s Civilian Payroll System (DCPS).

2. Concept of Operations

Task – The lowest level of labor hours tracking in the TSO is at the task level. Each project has a specific list of tasks assigned. For standardization the TSO has an approved task list in their Labor Reporting Guidelines (attachment 1). The task list for each labor hour category type will be different. For example a Sustainment labor hour category project will have a different task list from an Operational Support labor hour category project task list. Task lists can vary from project to project, but they must contain the standard list of tasks from the Labor Reporting Guidelines.

Projects – The TSO uses the Labor Reporting System (LRS) to track effort (actual hours) toward a project. In this case a project may be a Systems Change Request (SCR), a Production Trouble Report (PTR), a Software Development Lifecycle SDLC support function, such as Infrastructure build-out or an IT Project, such as implementing a new technology or migrating systems to a different data center. All projects are tracked by a funding category type. Projects frequently affect more than one Automated Information Systems (AIS) and; therefore, must be able to be assigned to more than one AIS.

Automated Information Systems (AIS) – The TSO defines AIS as a system that is developed or maintained by the TSO, for example Marine Corps Total Force System (MCTFS), Standard Accounting, Budgeting and Reporting System (SABRS), Marine On-line (MOL), Unit Diary/ Marine Integrated Personnel System (UD/MIPS), etc. In some instances AIS can also be used to describe an organization, such as the TSO, if the project does not affect a specific AIS.

Funding Source – The method of funding is defined by the customer and references a particular AIS or project. Customers may provide different funding sources for different AIS’s or projects. Typically the funding source is labeled with the Fiscal Year (FY) of the funding appropriation, the customer and AIS that the funding applies to, for example FY14MC Manpower & Reserve Affairs (M&RA).

Customer – Customers are those organizations that fund software development, maintenance or operational support efforts with the TSO. Customers may provide funding across multiple funding sources.

Type of Funding - The type of funding categories include Sustainment, Maintenance, and Operational Support. Sustainment hours are those hours expended to develop software changes. Maintenance hours are those hours expended to perform routine software maintenance and to trouble shoot and fix problems found in an application developed by the TSO. Operational Support hours are those hours expended in support of sustaining and maintaining the software development efforts and any hours expended in a non-chargeable category.

Labor type – Labor hours are tracked for each type of labor, Civilian, Military and Contractor. Labor types are assigned to employees. Occasionally, TSO employees will move between labor types, but labor types are not typically changed within a reporting period.

Direct/In-Direct – Labor hours are tracked by direct or in-direct billing categories. Direct labor hours are always charged to a project. Indirect labor hours, such as annual leave, are not charged to a direct (billable) project.

Labor Hour type – Also known as activities. Types of labor hours are defined in the Labor Reporting Guidelines. The labor hour types will match the Department of the Navy (DoN) time and attendance Type Hour Code found in the DoN time and attendance system.

Reporting Period – Labor hours are reported within a two week period. The labor reporting periods coincide with the Federal Government’s pay periods for federal employees. Reporting periods are discrete sets of hours. Labor hours reported during a reporting period must be validated prior to closing out the reporting period. Once the reporting period has been validated labor hours during that period can’t be changed.

Organization – The employees are assigned within the TSO organizational structure. The organizational structure includes the Organization (TSO, Marine Corps Pay Requirements Directorate (MCPRD), Marine Corps Disbursing Operations and Systems Section (MCDOSS), etc.), Directorate, Division, Branch, and Section or Team. Projects can be assigned at any level of the organization. Projects are typically assigned to AIS’s, but project responsibility is typically assigned by Division. Projects that impact multiple AIS’s can be assigned to multiple Divisions. Additionally, project responsibility is sometimes assigned to Organizations, Branches, Sections, and Teams or individual employees. The ability to report labor hours against a project can also be assigned at any level of the organization from an entire organization to the individual employee.

User – Defined as an employee of an organization that reports labor hours against Projects into a project time reporting system. The user must be associated with the organization and with their corresponding project list. Attributes of the user include their labor type, organization, division, branch, section or team.

Note - (The local American Federal Government Employees (AFGE) union reserves the right to negotiate any change in method used by its employees to record labor hours. Methods other than direct user input, for example and electronic time clock, would require union acceptance.)

3. Use Cases

Use Cases are provided to define business processes and system functionality that exist currently and that must exist in the SaaS.

Administrative Functions – Work is accepted into the TSO and appropriate projects are created.

1. Create/Edit System

a. Administrator logs onto system

b. Administrator inputs system name and system manager information

c. Administrator saves System changes.

2. Create/Edit Project

a. Administrator logs onto system

b. Administrator inputs Project Name, Title, Project Manager, Type of Work/Funding, one or more Systems, Funding Source, who can see the project and charge to it, estimated hours by the project or task, and what the project status is (open/closed).

c. Administrator assigns a predefined Task list by Type of Work

d. Administrator saves the project.

3. Create/Edit Project Task List.

a. Administrator logs onto system

b. Administrator creates Task List for each Type of Work.

c. Administrator saves Task Lists.

4. Create/Edit Activities

a. Administrator logs onto system

b. Administrator inputs Activity Name, Identifier, Description

c. Administrator saves Activity and assigns it to appropriate user groups.

5. Create/Edit User

a. Administrator logs onto system

b. Administrator inputs First, Last, and Middle name, an Email address, employee ID a User ID and password, account status, password change (for maintenance), appropriate organization, division, branch section or team, permission level, supervisor, employee type, start and end dates, Hourly costs, Approval path, substitute user (proxy), Holiday calendar, work week, validation Rules for timesheets.

c. Administrator saves User information.

6. Create/Edit Organizations

7. Create/Edit Email Notifications

a. Administrator logs onto system

b. Administrator selects user

c. Administrator applies desired email notifications.

d. Administrator saves email notification settings.

8. Create/Update Table values

a. Administrator logs onto system

b. Administrator sets labor reporting period rules for two weeks.

c. Administrator sets labor reporting period rules for 80 hour minimum per reporting time period.

9. Lock/ Unlock reporting periods

a. Supervisor notifies Administrator that labor reporting period changes are required for a user’s timesheet that has already been submitted and accepted by the supervisor.

b. Administrator logs onto system.

c. Administrator selects user from list.

d. Administrator unlocks user’s timesheet for edit.

e. Administrator notifies supervisor that timesheet is available for editing.

10. Extract reporting period data.

a. Administrator logs onto system

b. Administrator creates adhoc query for the reporting period extract and runs report

c. Save report into Microsoft EXCEL format and save file to Administrator’s computer using SSL connection.

d. Administrator saves query for future use.

11. End of FY/Beginning of FY Functions.

Financial Manager Functions

1. Create invoices for reimbursable customers.

2. Validate Contract labor billing.

3. Create adhoc reports

User Functions

1. Report Labor Hours

a. Users access the system.

b. Users select applicable Projects and tasks from a pick list customized to their projects. This includes non-chargeable hours such as annual leave or administrative time off. Projects and tasks from previous timesheets should be automatically brought forward to the current timesheet unless specifically deleted.

c. Users input hours that correspond to the actual effort for this task on this project each day. User input effort with .25 hour accuracy, such as .25, .50, and .75). User may add a comment to the task hours submitted for each day.

d. User saves input.

2. Submit Labor Hours

a. Users access system

a. End of reporting period user submits hours to supervisor for approval.

b. If rejected the user will make changes and then re-submit to supervisor again.

3. Select Proxy

a. If user is not available to input or submit time a substitute user (Proxy) can perform these functions.

b. Proxy User signs onto system and selects from list of predefined users to act as a proxy.

c. Proxy User inputs actual effort for appropriate projects and tasks for the unavailable user and submits the time sheet.

d. Proxy User logs out of system.

Supervisor Functions

1. Review Labor Hours

a. Supervisor logs onto system

b. Supervisor selects from a list of timesheets awaiting approval.

c. Supervisor reviews timesheet.

d. Supervisor approves or rejects timesheet.

e. If rejected the supervisor enters reasons and recommended changes into notification to the user.

f. Supervisor saves the changes to the timesheet.

2. Review Labor Hour Reports

2. SCOPE AND OBJECTIVES AND

Scope. The scope of this statement of work is to provide the requirements for a Project Time Reporting system with a SaaS time reporting system for the organization.

Objective. Project Time Reporting Software as a Service (SaaS) will be a software service used by the Marine Corps TSO to report actual hours worked against SDLC tasks for software application changes and application support tasks. The SaaS will be hosted by the vendor and used as a service via the internet. The SaaS system will replace the features of the existing functionality.

(1) Report Sustainment, Operational Support and Maintenance labor hours by SDLC and predefined tasks for each project, for AIS and funding source and customer with .25 hour accuracy in accordance with the TSO Labor Reporting Guidelines directly into the Project Time Report SaaS daily.

(2) Supervisor approval or rejection of the hours submitted by users into the projects and to retrieve burn rate reports by task, project, AIS, funding source and customer. Workflow to facilitate supervisor acceptance or rejection of user's labor hours submission.

(3) Provide administrative function to create and edit projects with Project Name, Title, Project Manager, Type of Work/Funding, one or more Systems, Funding Source, who can see the project and charge to it, estimated hours by the project or task, and what the project status is (open/closed). Administrator assigns a predefined Task list by Type of Work.

(4) Provide administrative function to create and modify user profiles to include First, Last, and Middle name, an Email address, employee ID a User ID and password, account status, password change (for maintenance), appropriate organization, division, branch section or team, permission level, supervisor, employee type, start and end dates, Hourly costs, Approval path, substitute user (proxy), Holiday calendar, work week, validation Rules for timesheets

(5) Provide administrative functions to create standard task lists customized by type of work. Assign task lists to each project created.

(6) Provide administrative functions to create organizational structures to include, organization, Division, Branch and Section or Team. Provide the ability to assign projects to Organizations, Divisions, Branches, Sections or teams or individuals.

(7) Provide administrative functions to apply business rules regarding labor hour and labor reporting period restrictions.

(8) Provide the administrative functions to restrict user access to only specified task, projects or AIS.

(9) Provide an administrative function to unlock supervisor approved time sheets when labor hours changes are required.by the user. The timesheet must follow the approve/reject workflow once the labor hours changes have been completed by the user. .

(10) Provide an adhoc data reporting function to allow supervisors and financial personnel to create custom reports with regard to hours reported by task, project, AIS, customer, funding source, type of work, labor type, organization, Division, Branch, Section or team, Direct or In-Direct, and Labor Hours Type for each reporting period.

(11) Provide the administrative function to create approval, rejection and notification workflows for timesheets submitted at the end of each reporting period. The supervisor will have the ability to reject and return timesheets to employees with notes regarding the necessary changes.

(12) Provide user capability to request leave (annual, sick, credit, etc.) and overtime.

(13) Provide capability for supervisors to approve leave and overtime requests for users under their supervision.

(14) Provide the user and supervisor the ability to assign and login as a proxy user. The user will be able to define which users can login to report and submit labor hours. The supervisor will be able to define which users they can log into to report or submit labor hours or which supervisors they can log on as to approve/reject time sheets.

(15) Provide capability for users and supervisors to input or approve time from a mobile computing device.

3. GENERAL REQUIREMENTS

- All deliverables will include the contractors name, address, and contract number.

- The Project Time Reporting SaaS will be accessed via a standard web browser, for example Microsoft Internet Explorer version 9 or higher, Google Chrome or Firefox. The system will also be accessible via mobile computing devices using standard operating systems, such as Apple, Android or Blackberry devices. Access to the SaaS will be via a secure connection to the service and will be CAC enabled.

· All data in the SaaS must meet the minimum safeguards as directed by the Department of Defense (DoD) and Department of the Navy (DoN) data security regulations.

· All data in the SaaS environment must be backed up daily. Any reported data corruption must be reconciled within 2 hours.

· The SaaS must meet the government’s standards for handicap accessibility as outline in Section 508 of the Rehabilitation Act.

· The SaaS must comply with Fair Labor Standards Act regulations for hours, overtime and time off recording and auditing.

4. SPECIFIC TASKS

The service provider will meet the following specific tasks in the form of a Project Time Reporting System.

A. A summary of the products and services the vendor shall provide follows. (reference attached data table requirements)

(1) Provide the capability for the user to report Sustainment, Operational Support and Maintenance labor hours during the software development life cycle to predefined tasks for each project, AIS, funding source and customer with .25 hour accuracy in accordance with the TSO Labor Reporting Guidelines directly into the Project Time Report SaaS daily.

(2) Provide the capability to automatically carry projects and tasks forward from previous time sheets to the current timesheet unless specifically deleted by the user.

(3) Provide the user the capability to select projects, and tasks from a customized list specifically assigned to the user, team, section, branch, division or organization.

(4) Provide the user the capability of saving any changes to the timesheet.

(5) Provide the user the capability to submit their timesheet for approval to their supervisor. This workflow should restrict the user from editing the timesheet unless the supervisor returns the timesheet for corrections.

(6) Provide the supervisor the capability to review user submitted timesheet and approve or reject labor hours submitted on the timesheet. The acceptance workflow will lock the timesheet for the reporting period from further modification. The rejection workflow will allow the supervisor to provide reasons for the rejection and action required to correct the timesheet. The rejection workflow will unlock the timesheet for the user in order to make necessary corrections

(7) Provide an administrative function to unlock and lock time sheets submitted and approved by a supervisor that need changes. This function is restricted to the previous reporting period.

(8) Provide user capability to request leave (annual, sick, credit, etc.) and overtime.

(9) Provide the supervisor the capability to approve leave and overtime requests for users under their supervision.

(10) Provide workflow for the leave and overtime approval process that routes the request to the supervisor. The workflow should include notification back to the user once the supervisor has approved or denied the users request.

(11) Provide the user and supervisor the ability to assign and login as a proxy user. Once defined the user will be able to select a user to report and submit labor hours on behalf of. Once defined the supervisor will be select a user to report or submit labor hours on behalf of or select a supervisor they can approve/reject time sheets on behalf of.

(12) Provide capability for users and supervisors to input or approve time from a mobile computing device.

(13) Provide the administrative function to create roles and permissions for administrator, user, supervisor/approver and financial manager.

(14) Provide administrative function to create and edit projects with Project Name, Title, Project Manager, Type of Work/Funding, one or more Systems, Funding Source, who can see the project and charge to it, estimated hours by the project or task, and what the project status is (open/closed). Administrator assigns a predefined Task list by Type of Work.

(15) Provide administrative function to create and modify user profiles to include First, Last, and Middle name, an Email address, employee ID a User ID and password, account status, password change (for maintenance), appropriate organization, division, branch section or team, permission level, supervisor, employee type, start and end dates, Hourly costs, Approval path, substitute user (proxy), Holiday calendar, work week, validation Rules for timesheets

(16) Provide administrative functions to create standard task lists customized by type of work. Assign task lists to each project created.

(17) Provide administrative functions to create organizational structures to include, organization, Division, Branch and Section or Team. Provide the ability to assign projects to Organizations, Divisions, Branches, Sections, or teams or individuals.

(18) Provide administrative functions to apply business rules regarding labor hour and labor reporting period restrictions. Reporting period equals two weeks and coincide with the Federal Government posted pay periods.

(19) Provide the administrative functions to restrict user access to only specified task, projects or AIS.

(20) Provide an adhoc data reporting function to allow supervisors and financial personnel to create custom reports with regard to hours reported by task, project, AIS, customer, funding source, type of work, labor type, organization, Division, Branch, Section or team, Direct or In-Direct, and Labor Hours Type for each reporting period.

(21) Provide the administrative function to create approval, rejection and notification workflows for timesheets submitted at the end of each reporting period. The supervisor will have the ability to reject and return timesheets to employees with notes regarding the necessary changes.

(22) Provide an administrative function to assign users to teams, sections, branches, divisions, and organizations with the labor reporting system.

(23) Provide an administrative function to allow the assignment of users to their supervisor and alternate supervisor.

(24) Provide the administrative function to control access to the views of data by task, project, AIS, funding source, customer or employee type.

(25) Provide an administrative function to create an interface file in the format specified in the LRS Labor File layout which is included as attachment (3). The file must be in a comma-delimited or Excel format.

(26) Provide an administrative function to create and edit labor hours types or activities and to categorize labor hour types as direct (billable) or indirect (non-billable).

(27) Provide an administrative function to prevent modification of labor hours after the end of reporting period.

(28) Provide the capability to display burn rates as spreadsheet reports or in graphical charts.

(29) Provide the capability to customize data fields to accommodate user defined data collection and reporting requirements. For example specialized funding requirements.

(30) Provide an administrative function to capture salary rates and create labor rates for each employee and the organization.

(31) Provide an administrative function to create time off requests and/or overtime authorizations workflow for supervisor approval or rejection.

(32) Provide a mechanism to securely transfer and load existing labor hours and related data elements into the Project Time Reporting SaaS in accordance with the attached data format.

(33) Provide a mechanism to securely transfer and load existing leave balances and related data elements into a Project Time Reporting System SaaS.

(34) Provide the Marine Corps with a configured Project Time Reporting SaaS and that is capable of meeting the reporting and adhoc query needs outlined in the enumerated Functional and Technical requirements, Data Model and Use Cases.

(35) Provide the ability to generate the following reports:

Direct Tasks

Why:

Verify that no one is charging Leave to a Project.

For:

TSO

Filters: Date Range: Pay Period (two week interval)

Project (Indirect)

Activities (Direct Time (example Regular Graded))

Output fields:

System Name, Project Name, Type of Work, Task Name, Activity Name, Timesheet Start Date, Timesheet End Date, User Name, Login Name, Employee Type, Total Hrs., Org Code, Project / Task (Full Path)

Indirect Tasks

Verify that employee is not charging Regular hours to a Leave category.

Type of Work (not Indirect)

Activities (Indirect Time (example Annual Leave))

System Name, Project Name, Type of Work, Task Name, Activity Name, Timesheet Start Date, Timesheet End Date, User Name, Login Name, Employee Type, Total Hrs., Org Code, Project / Task (Full Path)

Time Sheet Status

Verify that everyone has submitted and approved Timesheets for the Period.

Approval Status (not Approved)

Timesheet Period, Org Code, User Name, Supervisor Name, Approval Status, Total Hrs

Labor Metrics

Produce tracking and oversight reports for TSO and Customer.

TSO and Customers

System Name, Project Name, Type of Work, Task Name, Activity Name, Timesheet Start Date, Timesheet End Date, User Name, Login Name, Employee Type, Total Hrs., Org Code

Project Status

Find Status on the projects

TSO and Customers

Filters: As requested Usually Date Range and Project(s)

Output fields:

Project Name, Task or Expense, Total Hrs., Project Estimated Hrs., Task Name, User Name

SLDCADA

Compare with payroll to confirm both are correct.

Filters: As requested, Usually Date Range and Department

Timesheet Period, Org Code, User Name, Activity Name, Days of Pay period (10-21-13 thru 11-1-13) hours charged, Full Summary (total of hours)

Supervisor Listing

Ensure employees attached to a departing Supervisor are changed to a new supervisor.

Admin

Filters: User name (Supervisor)

Supervisor Name, User Name, Employee Type

B. Systems Requirements – The service provider will meet the following minimum system requirements.

(1) Availability – The application will be available at a minimum of 99%. Agreed upon maintenance windows and connectivity issues outside of the service providers control will be excluded from availability calculation. The application will have redundant equipment or load balancing to increase survivability from equipment failures or natural disasters. The service provider will have a documented Continuity of Operations Plan (COOP) that will restore access to the application and data within 72 hours of a disruption.

(2) Upgrades – All application and database changes must be published with at least 30 days notice prior to implementing upgrades. All upgrades must tracked through a documented and disciplined change management and release management process which include regression testing to minimize application disruption or data corruption.

(3) Performance – The service provider will meet the agreed upon application response times of no more than 5 seconds between screen refreshes. The database will provide adhoc queries within the agreed upon response time of no more than 30 seconds response time for adhoc queries.

(4) Support – Application support will be available 24 hours a day 7 days a week. Incident response will also be available 24 hours a day 7 days a week. The service provider will use an incident reporting systems to track reported incidents. The service provider will provide escalation procedures for reported incidents to the customer. The service provider will have an automated system to notify the customer of service degradation or interruption.

(5) Security – The application website will use SSL for both login and data transfer between the customer and the application. The data base will be encrypted. The data center housing the customer’s data will have 24 hours a day 7 days a week secure access with fire protection and suppression systems. The data center will be monitored 24 hours a day 7 days a week and a log of all personnel accessing the data center will be provide to the customer upon request. All personnel with access to the customer’s data will sign a non-disclosure statement.

(6) Data backup – The service provider will perform a full back up of the database each week. The service provider will perform an incremental back up of that day’s changes to the database each day. The current weekly and daily back up will be stored at least 30 miles away from the data center. Restore procedures will be performed quarterly to verify the validity of the back up process and media.

5. DELIVERABLES- The service provider will provide the following items prior to the implementation of the application.

(1) Transfer of Marine Corps data via a secure file transfer to the service provider

(2) Application configuration to meet the needs of the Marine Corps for data field names, approval work flows, and adhoc reporting.

(3) Application Administrator training to assist the administrators with the tasks of loading employee's roles and permissions, establishing tasks, projects, AIS, funding source and customers.

(4) Employee training to assist the user with accessing the application, inputting hours and setting up tasks.

(5) Supervisor training to assist the supervisor with assigning tasks, approving reported hours and creating adhoc reports.

Post implementation deliverables.

(1) Monthly burn rate reports with the number of users, cost per seat and total monthly charges.

(2) Monthly incident report that outlines incidents reported by the customer and their resolution.

(3) Changes or updates to incident reporting procedures or points of contact.

(4) 30-day notice of any software upgrades or database changes.

(5) Monthly up time report.

6. POINTS OF CONTACT

The regional contracting office is:

POC: SSgt Irving Romero

Phone: (504) 697-9026

Fax: (504) 697-9742

Email: irving.romero@usmc.mil The responsible officer and the Subject Matter Expert (SME) for approving work against this statement of work are:

Shall be provided in award document

RO: TBD

Phone: TBD

Fax: TBD

Email: TBD

8. PERIOD OF PERFORMANCE

One base year with four option years. Base year must start on September 30, 2014.

9. ATTACHMENTS

(1) TSO Time Labor Reporting Guidelines

(2) Past Performance Questionnaire

(3) LRS ERD

(4) Performance Requirements Summary.

(5) Quality Assurance Surveillance Plan.

SECTION 508

Section 508 Program Need

Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for the following program need: " Software as a Service Time Bill."

Section 508 Deliverable Requirements

The activity to be performed relates to or requires the use of EIT. Section 508 must be considered as a requirement for Systems Administration outputs/deliverables to ensure that it considers specific Section 508 accessibility requirements. Further, Systems Administration outputs/deliverables should not adversely affect accessibility features of existing EIT technologies. Technical standards from 36 CFR part 1194 Subpart B have been determined to apply to this acquisition. Solicitation respondents must describe how their background and experience will enable them to at least meet those technical provisions identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

Software as a Service Time Bill outputs/deliverables should meet applicable accessibility requirements and should not adversely affect accessibility features of existing EIT technologies.

Functional performance criteria from 36 CFR part 1194 Subpart C have been determined to apply to this acquisition. Solicitation respondents must describe how their Solicitation respondents must describe how their background and experience will enable them to at least meet those functional performance criteria identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

Information, documentation, and support requirements from 36 CFR part 1194 Subpart D have been determined to apply to this acquisition. Solicitation respondents must describe how the information, documentation, and support proposed for Software as a Service Time Bill outputs/deliverables will meet at least those information, documentation, and support requirements identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

Section 508 Evaluation Factors

Responses to this solicitation will only be considered for award after it has been determined that the proposal adequately addresses the requirements for Section 508. Only proposals which contain adequate information to document their responsiveness to the Section 508 requirements (e.g. accessibility capabilities and past performance) will be eligible for any additional merit consideration.

Section 508 Acceptance Criteria

Date and Information Services outputs/deliverables resulting from this solicitation will be accepted based in part on satisfaction of identified Section 508 requirements for accessibility. Software as a Service Time Bill outputs/deliverables must include a completed GPAT, a sample of which is included as a part of this solicitation.

Data and Information Services outputs/deliverables should meet applicable accessibility requirements and should not adversely affect accessibility features of existing EIT technologies.

Government Product Accessibility Template for Software as a Subscription Time Bill

Summary

· Column one involves consideration of all the Sections of the Standard that might apply to any deliverable. The total number of provisions within each Section of the Standard is shown in parentheses.

· Column two identifies the total number of provisions that typically apply to a deliverable of this type. Some of these may not be features of the vendor’s deliverable. Conversely, others not noted may be features of the vendor’s deliverable. If the deliverable involves consideration of additional features, the accessibility of these features must also be considered.

· Column three is for general notes about the Sections of the Standard. Some apply to all deliverables and some are specific to the deliverable.

· Column four is a summary of the vendor’s response to applicable provisions and additional deliverable features from the Sections of the Standard.

· Column five is where the vendor can note explanations for any of the preceding columns, e.g. there are differences between expected applicable provisions and actual product features.

Section 1194.22 Web-based Internet and Intranet Information and Applications (16 provisions)

Section 1194.23 Telecommunications Products (14 provisions)

Section 1194.24 Video and Multi-media Products (5 provisions)

Section 1194.25 Self-Contained, Closed Products (13 provisions)

Section 1194.26 Desktop and Portable Computers (4 provisions)

Section 1194.31 Functional Performance Criteria

(6 provisions)

Section 1194.41 Information, Documentation and Support (3 provisions)

Subpart B -- Technical Standards

Note: If there is a possibility that the provision applies, the default value is “Yes”.

· Column one is the full text of the provision from the Standard.

· Column two documents the agency’s accessibility requirement based on common characteristics of the EIT deliverable. Place a Yes or No in this column based on program need and actual characteristics of your expected deliverable (i.e., Is this provision seen as applicable to the expected deliverable?)

· Column three provides explanatory information about the provision to help both the agency in determining applicability and the vendor in providing accessibility information.

· Column four is for the vendor to check off whether the deliverable meets, partially meets or does not meet the specific provision.

· Column five is for the vendor to provide an explanation of how the deliverable meets or does not meet the specific provision. It is also an opportunity to explain why a deliverable does not have an applicable feature or why it has a feature that was not identified as applicable.

Section 1194.21 Software applications and operating systems

__Partially __No

__Fully

__Fully

__Fully

__Fully

__Fully