220606 CON-MS PWS.pdf

CON-MS PWS

Page 1 of 9 – 6 June 2022

Performance Work Statement For

Contracting Management System (CON-MS)

1.0 INTRODUCTION/BACKGROUND. Contracting Units are responsible for executing and managing cradle-to-grave procurement activities in support of multiple customers throughout the Air Force in addition to Department of Defense (DoD) mission partners. The Department of the Air Force 365 (DAF365) network serves as a reliable, centralized location to store, retrieve and maintain information, policies, guidance, and templates. DAF365 is located on a private network, which is based on the Microsoft Office 365 environment. This environment will host the contractors work product.

2.0 OBJECTIVE. The objective of this contract is to provide developmental services for CON- MS, a cloud based cradle-to-grave contract management tool. The contractor shall provide services to develop CON-MS utilizing available resources utilizing DAF365 tools as defined in para 4.2.1.5 and integrate current data from our MS Access database titled “Contract Management System” (CMS).

3.0 TASK REQUIREMENTS. The Contractor (CTR) shall provide one (1) full-time employee (FTE) for the base and each option year for CON-MS as follows:

3.1 CON-MS Operations and Maintenance

3.1.1 CON-MS Daily Operation. Provide day-to-day maintenance and support of CON-MS operations. Add new users and respond to existing user system access requests within one (1) day of user request. Maintain a list of authorized users and provide to the government upon request.

Track all user help requests through the CON-MS website and report open and unresolved status to the Functional Services Manager (FSM) and/or the Contracting Officer’s Representative (COR) weekly (para. 3.4.1). Perform debugging and problem resolution as needed.

3.1.2 Production Data/Developmental Data Sites. All builds and upgrades shall be developed and tested prior to incorporation into production. No build or upgrade shall be applied to the production without approval from the FSM or COR.

3.1.3 CON-MS site Development. Continue development and upgrade of the CON-MS tool.

Coordinate with and receive approval from the FSM or COR before development of any changes/upgrades that affect customer interaction/usability/processes within CON-MS.

3.1.3.1 Validation/Testing. Perform testing (verification, validation, and effectiveness) of CON- MS changes, upgrades, and enhancements on a test site. Provide results of testing to the FSM and COR, in writing.

3.1.3.2 CON-MS Ad Hoc Report Generation. Enhance ad hoc report generator that allows users to view, sort, download, and print fields based on user requirements.

3.1.4 Data Analysis and Requirements Recommendation. Perform data analysis and provide the Government recommended website upgrades based on customer requirements. Analysis and recommendations shall be provided to the Government on the Monthly Status Report and in weekly status meetings (para. 3.4.1).

Page 2 of 9 – 6 June 2022

3.1.5. User Manual. Provide access to a CON-MS User Manual via the CON-MS SharePoint site. Maintain and update the User Manual to include approved and fielded system process changes are published concurrent with release to production tool. Access to DAF365 resource is controlled by the 6th Contracting Squadron Information Assurance Officers (IAO).

3.2 Administration.

3.2.1 Customer Training. Schedule and provide customer reoccurring CON-MS training, typically twice a month for 1 – 1 ½ hours; one (1) class shall be tailored for new users and a second class will be tailored on the use of specific functions (MIPR, funding, COR tracking, etc.)

or any changes made to CON-MS.

3.2.2 Document, Track, and Analyze Customer Requirements. Gather and document customer requirements, through both the CON-MS website help feature and face-to-face interaction with customers. Log CON-MS user-submitted Requirement Request Documents (RRD) and provide a copy to the FSM or COR for review. User Group meeting shall occur monthly, unless otherwise directed by the FSM or COR. Record minutes during CON-MS customer meetings and post on SharePoint site within three (3) business days of meeting. Track and analyze customer enhancement/issue requests and anomalies.

3.3 Track/Record Status.

3.3.1 Weekly Status Meeting. Meet weekly with the FSM/COR. Provide feedback verbally and hardcopy or electronically via email on website development, customer requests, and any issues on CON-MS operation/upgrade.

3.3.2 Monthly Status Report. Provide a monthly status report to the Government by the 5th of each month, showing the major tasks accomplished during the previous month, current issues with CON-MS, any deviations in the projected schedule, and projected tasks that will be accomplished during the upcoming month. The report shall also provide a financial spreadsheet displaying both funded and expended finances.

3.4 Reach-back Capability.

3.4.1. The contractor shall maintain a reach-back capability for employee(s) performing tasks under paragraph 3.0. The reach-back capability shall have knowledge of specialized programming/database skills related tasks covered in paragraphs 3.1, 3.2, and 3.3.

3.5 Contingency Plan.

3.5.1. The contractor shall develop and maintain a contingency plan to ensure continuous operation of CON-MS in the event of temporary absence of employee(s). The plan shall provide continuous services in paragraphs 3.1 through 3.3. A copy of the contingency plan shall be delivered to the FSM and COR within 30 days of contract award, reviewed annually, and updated as required.

3.6 Knowledge Skills and Abilities (KSAs).

Page 3 of 9 – 6 June 2022

3.6.1. Qualification Summary. The contractor shall develop and submit to the Government a qualification summary with the KSAs needed for the programmer; current language, framework, and techniques used in CON-MS development are listed in Table 1. The qualification summary shall be incorporated into the contract.

3.6.2. Qualifications. The contractor shall hire employees with the technical education and experience necessary to perform all services in Section 3 and Table 3. Position vacancies shall not exceed 14 calendar days unless approved in writing or otherwise directed in advance by the CO. A vacancy begins the calendar day following departure of incumbent employee and ends the calendar day the new employee arrives at the place of performance.

Table 1

Frameware and Techniques Microsoft Office Products Power Apps Power Automate Power BI Teams

3.7 Deliverables. The contractor shall provide deliverables in a format mutually agreed upon by the Government and the contractor. All deliverables will be provided to the FSM and COR in electronic format, except when otherwise directed by the CO, COR, or this PWS. If a deliverable due date falls on a non-business day, the contractor shall provide the deliverable on the first business day prior to that date (i.e., if due on Saturday, the 5th day of the month, provide deliverable on Friday, the 4th day of the month).

Table 2

Deliverables PWS Paragraph Due Date Meeting Minutes 3.3.2 Within 3 business days of each meeting Weekly Status Update 3.3.1 Every Wednesday Monthly Status Report 3.3.2 5th calendar day of each month Contingency Plan 3.5 At contract award User Manual 3.1.5 Updated concurrent with upgrade release to production

3.8 Services Summary.

Table 3 Services Summary

Performance Objective

PWS

paragraph

Performance Threshold

Contractor provides stable workforce

3.0 Performance is acceptable when the contractor provides:

- Qualified and technical competent employees, and,

- No vacancy exists for more than 14 calendar days

- Employee turnover does not exceed 1 turnovers in a 2 year timeframe

Contractor provides all deliverables

Table 2 Performance is acceptable when the contractor provides deliverables:

- On time, and,

- In the correct format, and, Page 4 of 9 – 6 June 2022

Services Summary

Performance Objective

PWS

paragraph

Performance Threshold

- To the appropriate party, and,

- All critical information is accurate

Contractor responds to new user requests and help requests

3.1 Performance is acceptable when the contractor:

- Responds to 95% of new user requests within 1 business day, and,

- Responds to 95% of new help requests within 1 business day, and,

- Follows up according to existing help requests 95% of the time based on their criticality

Contractor coordinates application or system updates with designated personnel

3.1.3 Performance is acceptable when the contractor:

- Coordinates 100% of application or system updates with designated personnel prior to upload

4.0 GOVERNMENT FURNISHED RESOURCES.

4.1 Government Publications. Publications applicable to this PWS are listed in Table 4. The dates are the most current as of this writing; however, the contractor shall comply with the latest editions of mandatory documents when published.

Table 4

Publication Identifier Title or Publication Description Date DoD Travel Regulations The Joint Travel Regulations (JTR) 1 Jun 2022 Mandatory

DOD INSTRUCTION

5200.48

Controlled Unclassified Information (CUI) 6 Mar 2020 Mandatory

4.2 Government-Provided Equipment/Services. All Government-provided products and facilities remain the property of the Government and shall be returned prior to contract end.

Personnel supporting this requirement will return all items that were used during the performance of these requirements prior to contract end. Modification and distribution of end products for use at other installations will be at the discretion of the Government.

4.2.1 Government-Provided Equipment.

4.2.1.1 Office space, meeting rooms, and visual display equipment.

4.2.1.2 Office supplies (paper, pens, pencils, etc.) if on-site support is required.

4.2.1.3 Various documents, strategic plans, databases, and other data as required. This information will be used for general reference.

4.2.1.4 Common Access Card.

Page 5 of 9 – 6 June 2022

4.2.1.5 Computer and all required software to perform tasks stated within this PWS. Current software available to develop CON-MS is listed in Table 6 via the DAF365 services.

Table 6

Current Government-Provided Software SharePoint Teams Power Apps Power Bi Power Automate Microsoft Office

4.2.2 Government Provided Services. The contractor shall use these Government furnished services only in matters related to the performance of this contract. The Government may limit or restrict these services at any time.

4.2.2.1 Local area network to include electronic mail and Internet access.

4.2.2.2 Telephone and fax capability.

5.0 DATA. The Government retains unlimited rights to all deliverables of this contract to include intellectual property rights.

6.0 PROGRAM TRAVEL. The Contractor shall perform all on-base travel necessary to accomplish the tasks contained in this contract on the installation. At a minimum, the Contractor shall be prepared to travel in conjunction with studies, vendor site visits, and to provide support at Government meetings on the installation and supported annexes in the vicinity of Tampa, Florida. No temporary duty (TDY) assignments are anticipated.

7.0 SECURITY REQUIREMENTS.

7.1 Non-Disclosure Agreement (NDA). Due to the sensitive nature of material being worked with or contained within databases and related documents, the contractor’s employee shall be required to sign an NDA. The vendor shall not use such information for any purpose other than the performance of the work required in this PWS.

7.2 Computer Security. Employees must complete the Information Assurance Users Course (CBT) prior to gaining access to “.mil” domains.

7.3 Security Clearance. Applicants will not be eligible to perform services under this task order if they have any of the following:

Pending criminal or civil charges (including divorce/child custody proceedings) Felony arrest record Alcohol related arrest within the last five years Any type of moral turpitude arrest record/history (including, but not limited to, prostitution, pandering, voyeurism, public indecency) Any type of involvement in hate crimes History of violence Involvement in any group or organization that espouses extralegal violence as a legitimate means to achieve an end

Page 6 of 9 – 6 June 2022

7.4 Clearance Requirements. The highest level of security clearance required for this effort is SECRET. The Government will issue a DD-254 form as part of this contract.

7.5 NIPRNet Systems. Contractor employees supporting requiring access to classified information will be cleared at the start of the contract. Contractor will require access to NIPRNET computer systems only at government facilities.

7.6 Installation Access Control. Prior to an individual commencing work under this contract, the contractor shall perform necessary background/records checks to ensure they have no history of derogatory information, which preclude the employee from being allowed to enter the installation.

Further, the Government may also perform a background/records check on Contractor employees.

The contract administrator shall complete a “Request for Identification Credential form” for the contractor requiring access to MacDill AFB. The requests shall be submitted to Pass and Registration. The Contractor shall be required to obtain a Common Access Card (CAC). The Government reserves the right to have the Contractor remove any employee from the work area that the Government deems to be unsuitable and the Contractor will comply with Government request to remove an employee.

7.7 Controlled Unclassified Information (CUI). The contractor shall comply with regulations, which set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material.

7.7 Physical Security. The contractor shall be responsible for safeguarding all Government property and controlled forms provided for contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

7.9 Reporting Requirements. Contractor personnel shall report to an appropriate authority any information or circumstances they are aware of which may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

8.0 ADMINISTRATION CONSIDERATIONS.

8.1 Place of Performance. Services identified within this contract will be performed at 2610 Pink Flamingo Ave, MacDill AFB FL 33621-5119 (Bldg. 147)

8.1.1 Alternate Work Location. Alternate work location is authorized only during absence of Government in the place of performance (paragraph 8.1). Alternate work location shall be coordinated with the FSM and approved by the COR prior to performing work at alternate work locations. A list of work performed at alternate work location shall be forwarded to the COR the following duty day.

8.2 Duty Hours. Normal duty hours are 0700-1600, Monday through Friday. The contractor shall use 1920 hours as a full time man-year, with Federal Holidays being observed. The contractor shall not exceed 1920 hours per year per FTE. Known changes to duty hours will be coordinated 48 hours in advance and shall conform to a schedule agreed upon by the contractor and the Government COR/FSM.

8.2.1 Invoices: Invoice for services shall only reflect hours worked.

Page 7 of 9 – 6 June 2022

8.2.2 Contractor Identification. Each contractor employee shall, while on duty, wear in plain view on the upper portion of the outer garment, a metal or plastic identification badge to be furnished by the contractor, containing the company name, employee name, and the section where the employee works. Contractor employees shall clearly identify themselves as "contractors" at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other contractor personnel, or with the public. Contractors with access to the base LAN or with an official Government e-mail address shall include their company name in the signature block and the designation "CTR" in the global address. The contractor shall notify the Government if the "CTR" designation is not included in the global address.

8.3 Federal Holidays. Federal holidays are observed under this contract in accordance with https://www.opm.gov.

8.4 Kick-off Meeting. The contractor shall schedule a kick-off meeting with the customer’s representative within seven (7) business days of contract start date and will provide date, time, and location via email notification to the FSM, COR, and supporting staff at least three (3) business days prior to the scheduled meeting.

9.0 MANPOWER REPORTING.

9.1 Contractor Manpower Reporting. In accordance with Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Action, 2011, the contractor shall report ALL labor hours required for performance of services provided under this task order via the secure Defense Data Center site. The contractor is required to completely fill in all required data fields at: https://www.sam.gov/SAM/ (formerly https://www.ecmra.mil).

Reporting inputs shall be for the labor executed during the period of performance for each Government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The contractor may direct questions to the CMRA help desk. The prime contractor is responsible to ensure all subcontractor data is reported.

9.2 Uses and Safeguarding of Information. Information from the secure web site is considered to be proprietary in nature when the contractor number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

10.0 QUALITY ASSURANCE.

10.1 COR Designation. The CO will provide the contractor with a COR Designation Memorandum to inform the contractor of the designated COR on the contract. Contractor performance is subject to COR surveillance to ensure PWS compliance. The contractor shall comply with the following:

10.2 Access. The contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The contractor shall provide support, and not interfere with the CO, CORs, state, federal, and other designated personnel in the performance of their official duties. Access shall be provided as soon as possible, but not to exceed one (1) workday after the request.

Page 8 of 9 – 6 June 2022

10.3 Non-conformances. Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence. Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time frames specified by the CO.

This contract identifies two types of non-conformances: Minor and Major.

10.3.1 Minor Non-conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. It normally does not increase risk to the Government.

Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.

10.3.2 Major Non-conformance. A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form with a suspense date for the contractor’s corrective action plan. As a minimum, the contractor’s corrective action plan will address:

- Action taken to fix the immediate problem

- Root cause analysis of the problem to determine cause

- Corrective action on the cause of the problem

- Actions taken to prevent recurrence

11.0 GOVERNMENT USE OF DATA

11.1. Reference DFARS clause 252.227-7013(b)(1)(ii) Rights in Technical Data – Noncommercial Items: The Government shall have unlimited rights to "Studies, analyses, test data, or similar data produced for this contract, when the study, analysis, test or similar work was specified as an element of performance."

12.0 COVID-19

12.1. Contractor personnel shall comply with all Center for Disease Control (CDC), DoD, Air Force, and installation measures to combat the spread of COVID 19. Contractor personnel shall practice social distancing measures and wear appropriate contractor provided face coverings.

Face coverings shall be a single color and not contain any logos, designs or text.

12.2. The contractor shall immediately notify the COR if any employee is exposed to or diagnosed with COVID 19. The contractor shall provide contact-tracing details of on base

Page 9 of 9 – 6 June 2022 personnel who may have been exposed by the affected contractor employee.

12.3. To limit potential exposure to Contractor and DoD personnel and to comply with CDC social distancing guidelines, contractor personnel may be permitted to tele-work up to 100% of scheduled duty time. A Government provided computer will be issued to contractor personnel on a hand receipt. Contractor personnel are responsible for safeguarding Government provided equipment and shall immediately notify the COR if the equipment is damaged, lost or stolen.

The contractor is responsible for the cost of tele-work Internet connections and telephones. The Contractor shall not be entitled to an equitable adjustment under FAR 52.249-14, Excusable Delays, FAR 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items, other such clauses or the CARES Act, for its failure to diligently perform work under a task order(s).

12.4. Contractor personnel may be required to attend on-base meetings during approved tele-work periods at no additional cost to the Government. While attending meetings, Contractor personnel shall practice social distancing measures and wear appropriate contractor provided face coverings.