M95494-22-R-0013 (RFP).pdf

SEE ADDENDUM

(No Collect Calls)

M9549422R0013 26-Jan-2022

b. TELEPHONE NUMBER

703-604-0086

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 08 Mar 2022

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

M954949. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

BRANDON M. PAYNE

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

MCICOM HQ

3000 MARINE CORPS PENTAGON

WASHINGTON DC 20350-3000

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$30,000,000

NAICS:

541519

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

M9549422R0013

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 UNDEFINED

FFP Task Orders

FFP

In accordance with the Overarching PWS Tasks under paragraphs 2.0 - 2.8 and

3.0 - 3.5. Specific objectives will vary based on the Task Order.

FOB: Destination

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

0002 UNDEFINED

FFP LOE Task Orders

FFP-LOE

In accordance with the Overarching PWS Tasks under paragraphs 2.0 - 2.8 and

3.0 - 3.5. Specific objectives will vary based on the Task Order.

MAX NET AMT

CEILING PRICE

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED

Travel (NTE $1,300,000)

COST

Travel will be specified in individual task orders. Travel will be reimbursed on a cost reimbursable basis IAW PWS Section 13.0 and will be reimbursed at cost only (no fee). The estimated amount on this CLIN is $1,300,000.

MAX COST

UNIT UNIT PRICE MAX AMOUNT

0004 UNDEFINED

NSP Data

Contract Data Requirements List - Exhibits A001 - A011 in accordance with PWS requirements.

MAX

NET AMT

IDC Constraints

Minimum and Maximum IDIQ Amounts

a. Minimum guarantee per IDIQ Contract: $5,000.00

b. Maximum: TBD at time of award

NOTES:

The minimum guarantee of $5,000.00 is the minimum for the entire 5-year ordering period.

The maximum will be determined at time of contract award. At the time of contract award, each CLIN will be an "estimated" (EST).

PERFORMANCE WORK STATEMENT

Base Indefinite Delivery, Indefinite Quantity (IDIQ) Performance Work Statement (PWS) for Business Information Systems Support Services

1.0 Background

The Technology Services Organization (TSO) provides Business Information Systems (BIS) support for software development, systems engineering, maintenance, and operations of Financial Management (FM) and Human Resource Management (HRM) Business Mission Area (BMA) systems in support of the Deputy Commandant, Programs and Resources (DC P&R), and Deputy Commandant, Manpower and Reserve Affairs (DC M&RA). DC M&RA employs integrated manpower systems across the Service enterprise that attracts, develops, retains, and supports our Marines, their families, and our civilian workforce as they pursue their professional aspirations and personal career goals. Collectively, these systems provide our commanders a picture of the human “steel” necessary to fight and win the Nation’s battles. DC P&R employs financial management and accounting systems across the Marine Corps enterprise that track the distribution of funds and processing of financial transactions. Collectively these systems are part of the FM BMA.

TSO’s portfolio includes integrated Pay & Personnel, FM and accounting systems in support of the United States Marine Corps (USMC), Department of the Navy (DON), and Department of Defense (DoD). Stakeholders under this effort include, but are not limited to: U.S. Air Force Reserve; Air National Guard; U.S. Navy; U.S. Navy Reserve; and the Defense Finance and Accounting Service (DFAS).

1.1 Mission

TSO’s mission includes functional support for BISs, studies, assessments, consulting, program and project management, and the integration and maintenance of the networks that supported BISs operate upon. TSO provides development, design, production, and maintenance support of BISs; particularly pay, personnel and accounting systems, for the Marine Corps as well as DoD components, services, and agencies.

1.2 Scope

TSO owns and stewards several enterprise-level BISs which support hundreds to hundreds of thousands of users.

These BISs are comprised of many dozens of custom Government off the Shelf (GOTS) software applications as well as Commercial off the Shelf (COTS) hardware and software applications. TSO’s GOTS software applications contain a broad spectrum of platforms and technologies as denoted in Appendix A (Attachment 1). TSO builds, operates, and maintains its BISs, their component technologies, their development environments, and their hosting environments primarily with Marine and Civilian Marine personnel in a Government owned, Government operated, contractor supported (GO-GO-CS) operating model.

The purpose of this contract is to provide the maintenance of highly complex, Government-designed and owned enterprise-class business critical systems. The services to be acquired fall within the scope of knowledge-based support services for software analysis, programming, debugging, software testing, software maintenance, software installation, help desk support and management, document conversion, risk management, software process improvement, quality assurance, system operations support, project management, system documentation, training, and maintenance of the systems, subsystems, and networks supported by TSO.

2.0 Tasks

Specific task requirements and deliverables will be included in the Task Orders issued under this contract. Specific taskings may be firm-fixed-priced (FFP), FFP level of effort (LOE), or a combination of the two.

FFP Tasks: At the Task Order level, the fixed labor rates (inclusive of all costs including any overtime, premium time, holiday time, etc) and labor hours for the necessary labor categories will be proposed to authorize a fixed dollar amount to perform the stated requirement in its entirety.

FFP LOE Tasks: At the Task Order level, the fixed labor rates (inclusive of all costs including any overtime, premium time, holiday time, etc) and labor hours for the necessary labor categories will be proposed to authorize a fixed dollar amount to perform a specific LOE over an agreed period of time, generally resulting in a deliverable being provided at the end of the level of effort. The number of hours may be reduced based on actual hours worked.

In such an event, a reduction in the contract price shall be calculated for each affected labor category by multiplying the number of reduced hours by the applicable labor rate. The Contractor shall invoice only actual hours worked at the appropriate labor rate. Any reduction in hours will be reflected in a task order modification at the completion of the Task Order performance period. For FFP LOE tasks only, the ceiling amount for each task order will be the ceiling price stated therein and may not be increased except when authorized by a modification to the delivery/task order.

Software deliverables must be submitted in accordance with Contract Data Requirements List (CDRL) A010 Software Design Description. The Contractor must provide the following services and capabilities in support of the BISs and their associated technologies listed in Appendix A as well as TSO’s overall mission:

2.1 Software Development Lifecycle (SDLC)

Provide Software Development Lifecycle (SDLC) support in line with TSO’s software development methodologies including iterative and agile. TSO’s SDLCs support all aspects of GOTS software applications, including data management systems; middleware integration; application interfaces; and web and mobile user interfaces. SDLC support shall include:

a) BIS requirement gathering, derivation, and documentation

b) System, software, interface, and data architecture designs and documentation

c) Software component engineering designs and documentation

d) Implementation of architecture and engineering designs via software programming

e) Software debugging and testing in accordance with CDRL A011 Software Test Report

f) System and software release management

2.2 Web BIS Infrastructure and Operations

Provide Infrastructure and Operations support to web-based BISs in traditional on-premises data centers and cloud environments. Support shall include:

a) Submittal of a Software Integration Plan, in accordance with CDRL A009, Software Integration Plan

b) Support of Information Technology Service Management (ITSM) processes

c) Provisioning, managing, and decommissioning physical and virtual infrastructure

d) Provisioning, configuring, integrating, leveraging and maintaining Continuous Integration/Continuous

Deployment (CI/CD) tools selected and implemented by TSO

e) Monitoring of system availability and performance

f) Network engineering designs and implementation

g) Routine maintenance and patching

h) Database monitoring and administration

i) Data backup and restoration

j) BIS access management

k) BIS change management

l) Incident/problem management

2.3 Cybersecurity

Provide Cybersecurity support to the Government Information System Security Officers (ISSOs), Information System Security Engineers (ISSEs), and Information System Security Managers (ISSMs) who maintain the USMC Assessment and Authorization (A&A) Process, based on the Risk Management Framework, for TSO. Support shall include:

a) Research, evaluation, and authoring of Committee on National Security Systems (CNSS) Instruction No.

1253 controls.

b) Evaluation of the application and implementation of Security Requirements Guides (SRGs) and Security Technical Implementation Guide (STIGs)

c) Creation, updating, and review of A&A documentation and artifacts

d) A&A package validation (Risk Management Framework Step 4) via a contractor-furnished Marine Corps certified validator

e) Continuous monitoring of the cybersecurity posture of BISs

f) Vulnerability management of BISs firmware, operating systems, middleware, and software.

2.4 Data and Platform Analysis

Provide support for data and analytics platforms used by or interfacing with TSO BISs. Support shall include:

a) Data modeling and report authoring support for data within TSO BISs and external data providers

b) Administering and monitoring business intelligence tools used for analytics, planning, and reporting.

c) Administering and monitoring Extract, Transform, and Load (ETL) processing for TSO data warehouses and other BISs.

2.5 Financial Audit

Provide support for TSO’s financial audit support processes which manage, facilitate, and disseminate data artifacts to financial audit stakeholders. Support shall include:

a) Providing subject matter expertise to assist external stakeholders in understanding TSO BISs.

b) Assisting in identifying, developing, and updating TSO audit support processes.

c) Updating and maintaining Government furnished audit support artifact repositories.

d) Communicating audit requirement response status and any potential road blocks.

e) Providing support, responses, and source documentation for Provided by Client (PBC), Samples, Follow-

Up Questions (FUQ), Observations (OBS), Notice of Findings and Recommendations (NFR) requested by the Independent Public Accountants (IPA).

f) Assisting in drafting of and tracking of Corrective Action Plans (CAPs) .

g) Maintaining audit support metrics.

2.6 Mainframe BIS Operations

Provide Mainframe Operations support to mainframe BISs and technologies. Support shall include:

a) Submittal of a Software Integration Plan, in accordance with CDRL A009, Software Integration Plan

b) Monitoring the execution of mainframe applications in multiple IBM zOS environments;

c) Performance monitoring and tuning

d) Data recovery

e) Database monitoring and administration for databases such as ADABASE and DB2

f) Troubleshooting system problems

g) Updating or creating execution schedules via technologies such as JCL and Control-M

h) Managing inbound/outbound data for a multitude of systems

i) Provisioning, configuring, integrating, leverage, and maintaining Continuous Integration/Continuous

Deployment (CI/CD) tools selected and implemented by TSO

2.7 Business Process Management

Provide Business Process Management (BPM) support, which shall include:

a) Discovery and documentation of existing business processes

b) Analysis and improvement assessments of existing business processes

c) Analysis and recommendation of process implementation within or in conjunction with existing BISs or via other automated methods

d) Support business process automation utilizing artificial intelligence and robotic process automation technologies and tools selected by TSO

2.8 BIS Data Calls

Provide data call support for BISs, their corresponding business processes, and the data contained within those systems. Data calls will come from a variety of sources external to TSO. Support shall include:

a) Data call requirement processing and refinement in order to understand intent, timelines, and required reporting formats

b) Navigation of applicable business processes in order to identify the location of the relevant data

c) Navigation and interaction with applicable business systems at a technical level (including database schemas and table structures) in order to retrieve relevant data

d) Compilation of relevant data in the format required by the data call

In-scope changes to Task Orders under this Contract are anticipated and are primarily driven by law or legislation (e.g. National Defense Authorization Act (NDAA)) and regulatory, policy and procedural requirements (e.g., Joint Staff, DoD, DON, and Commandant of the Marine Corps (CMC), Warfighters, etc.). Other changes result from BPR efforts and technology advances necessary to improve business and technical efficiencies as well as the unpredictable nature of overseas contingencies.

The Contractor must support operational events and schedules such as, but not limited to: software releases/implementations; routine and ad hoc maintenance windows; hardware installation; version upgrades; and patching. Schedule adjustments are anticipated due to business continuity plans for unplanned incidents, federal holidays, furloughs, or shutdowns. The Contractor must perform all assigned tasks regardless of required schedule adjustments.

3.0 Administrative Tasks

Specific administrative task requirements and deliverables will be included in the Task Orders issued under this contract. Specific taskings may be FFP, FFP LOE, or a combination of the two.

3.1 Program Management

The Contractor must meet the requirements of this Contract and its Task Orders in accordance with the Performance Requirements Summary (PRS). The Contractor shall provide a Program Management Plan within 5 days of accepting a task order that includes a summary of the Contractor’s activities to manage this requirement, all scheduled objectives and milestones, and status updates of current Task Orders in accordance with CDRL A004, Program Management Plan.

3.2 Post-Award Conference

The Contractor shall coordinate and conduct the Post-Award Conference within seven (7) business days of contract award at the Government’s Indianapolis site or virtually, as appropriate. The meeting shall provide an introduction between the Contractor and Government personnel who will be involved with the contract. Discussions at the meeting shall include: technical, management, and security issues; travel authorization; and reporting procedures (e.g., initial report suspense dates for all recurring programs; quality assurance; and contract deliverables). Meeting minutes shall be provided to the Government in accordance with CDRL A006, Management Review Meeting Minutes.

3.3 Management Reviews

The Contractor shall coordinate and conduct monthly Management Reviews (MR’s). These reviews must provide a forum for the Contractor, Procuring Contacting Officer (PCO), Contracting Officer Representative (COR) and key Government staff to discuss critical management topics including: Contractor Performance; Workload; Process Improvement; Current funding status; and other topics identified by the Contractor or Government. The Contractor shall prepare and submit an agenda and draft presentation no later than five (5) business days prior to the MR in accordance with CDRL A007, Presentation Material and provide a subsequent memorandum for the record (MFR) that summarizes the critical management topics discussed no later than five (5) business days after each MR to the COR also in accordance with CDRL A006, Management Review Meeting Minutes. MR’s may be held at the BMO Building in Indianapolis or virtually, as appropriate. The Government will review the MR agenda and MFR and provide any revisions (i.e., additional topics) as needed prior to approval and distribution.

3.4 Transition Plan

The Contractor shall implement the Transition Plan and keep the Government fully informed of status throughout the transition period. Throughout the Transition-In/Transition-Out periods, it is essential that interruptions or delays to work in progress, that would impact the mission, be minimized.

a) Transition In – Transition ensures the incoming Contractor the opportunity to maximize capture of the existing pool of expertise, develop a thorough understanding of the existing system life-cycle management processes and system requirements, as well as allow for knowledge transfer with the incumbent Contractor.

The Contractor shall present the Transition Plan at the post-award kick-off meeting and within five (5) business days of the kick-off meeting, provide a finalized Transition Plan that addresses the migration of assigned workload. All transition-in activities will be based on a transition period of no more than ninety

(90) calendar days. The transition shall ensure minimum disruption to TSO operations. The Contractor shall minimize service degradation during and after transition. The Contractor will receive support not only from the Government, but also from the incumbent Contractor who is contractually obligated to support transition activities. Delivery of the Transition In Plan shall be in accordance with CDRL A008, Transition Plan.

The Government reserves the right to identify key positions and to review resumes to ensure that key positions are filled with contractors with adequate training and expertise to accomplish key task requirements. Although specifically identified as Transition-In activities, coordinating and performing facility and Common Access Card (CAC) badge issuance at the Government work location, and monitoring physical security of assigned spaces and visitor access in the Government work location, will continue throughout the life of the contract for all employees including civilians, contractor and military.

b) Transition Out – The Contractor shall provide a draft Transition Out Plan for transitioning work from itself to a follow-on incoming Contractor. The draft Transition Out plan shall address how the Contractor will formally coordinate with the Government and subsequent incoming Contractor management and staff in order to transition services. The Transition Out Plan must ensure no product or service disruption or degradation during and after a transition from this contract to the subsequent contract. Delivery of the Transition Out Plan shall be in accordance with CDRL A008, Transition Plan.

3.5 Quarterly Status Meeting

The Contractor shall plan and conduct Quarterly Status Meetings (QSM’s). The primary purpose of these meetings is to review contract performance status and address contract-related issues. At a minimum, the meeting will include appropriate contractor representative(s), the Contracting Officer, the Contracting Officer’s Representative (COR), and Government technical personnel, as appropriate; however, the contracting officer may choose to include other Government attendees. Meetings will be held via a phone conference call. The Contractor is responsible for setting up the phone conference facilities. Each meeting will cover the following topics, as appropriate:

• Contract/Task Order Performance Status

• Performance Issues encountered or expected (e.g., potential delays)

• Required Government actions

• Compliance with task order staffing/key personnel requirements

• Discussion on Contractor performance against PRS metrics

• CLIN-related issues or funding limitations

• New or in-process modifications

• Potential upcoming task order requests

• Clause compliance (e.g., 52.219-9 Small Business Subcontracting Plan)

• Invoice submission/payment issues

• Contractor Performance Assessment Report System (CPARS) status

• Continuous Improvement ideas for current contract and/or future contract(s)

• List of current employees supporting this contract and its Task Orders

The Contractor shall provide meeting minutes within five (5) days of each QSM to the Contracting Officer and COR. Delivery shall be in accordance with CDRL A006, Management Review Meeting Minutes.

The COR will send out a Task Order Tracker prior to the QSM and if any updates are necessary, the Contractor will provide updates to the Contracting Officer. The Task Order Tracker will include information such as Contractor name, contract number, task order number(s), award date(s), period of performances, teaming partners/subcontractors used by the prime contract along with their business size designations, task order value(s).

Presentation materials shall be delivered in accordance with CDRL A007, Presentation Material.

4.0 Place of Performance

No dedicated place of performance is established at the PWS level, and Contractors will not generally be provided with on-site workspaces. However, the Government suggests Contractor personnel be physically stationed within 50 miles of the following locations, as the Government will not reimburse travel expenses for the issuing of Common Access Cards (CACs) or on-site computer technical support.

• Indianapolis, IN

• Kansas City Information Technology Center (KCITC) in Kansas City, MO

• Marine Corps Base Quantico in Quantico, VA

Specific places of performance, including but not limited to the above locations, or on-site workspace allocations may be defined at the Task Order level.

Performance of tasks under this contract will require access to the Marine Corps Enterprise Network (MCEN).

Access to the MCEN will require a contractor furnished laptop with a Marine Corps Enterprise Desktop Standardization (MCEDS) computer image installed and configured; a Department of Defense CAC, and a stable internet connection allowing Virtual Privacy Network (VPN) connections from the MCEDS laptop to the MCEN VPN servers.

On-site computer technical support for MCEDS computer images, including initial configuration and issue resolution requiring physical MCEN connectivity or touch labor, can only be accomplished at a MCEN service center in the cities listed above. Issuing CACs can only be accomplished at a DEER/RAPIDS site (see https://idco.dmdc.osd.mil/idco/).

5.0 Period of Performance

There will be a five-year ordering period for this requirement beginning on or about 14 November 2022. Periods of performance for task orders awarded under this contract will be designated within the respective task orders. The Government’s core hours are 0900-1500 Eastern Time zone; however, alternate hours of support may be defined at the Task Order level.

6.0 Key Personnel

https://idco.dmdc.osd.mil/idco/

Contractor personnel will be providing services at the Service Component (3-4 Star) and Operational Force level of command. Contractor personnel need to be skilled in developing executive-level correspondence and management programs involving executive level participants. Contractor personnel need to be proficient in briefing to senior Military (e.g., O-6 level and above); Military Commanders and their staffs; organizational leaders; and peers.

Contractor personnel should expect to work with a diverse and often conflicting group of stakeholders from a cross-section of all staff divisions/efforts.

• Program Manager – The Program Manager will work closely with the COR and is responsible for staffing and managing the execution of Task Orders. The Program Manager shall oversee the performance, schedule, and quality of the Task Orders. The preferred experience is as follows.

o Six (6) years or more of program managing enterprise-scale mainframe or web software applications programs;

o Four (4) years or more of program managing BIS programs;

o Demonstrated experience managing programs in multiple software development methodologies such as waterfall, agile, and scrum; and o Program Management Professional certification or similar.

The Key Personnel assigned to this Contract are considered to be essential to the work being performed; however, additional Key Personnel may be defined at the task order level.

6.1 Substitution of Key Personnel

• General Provision – The Contractor agrees to assign to this contract/task order those persons identified as key personnel whose resumes were submitted with its proposal and who are necessary to fulfill the requirements of this contract/task order. No substitutions of key personnel shall be made except in accordance with this clause.

• Guidance on Substitutions – During the first ninety (90) days of the contract/task order performance period, no key personnel substitutions by the Contractor will be made unless substitutions are necessitated by an individual's sudden illness, death, termination of employment or non-acceptance of an offer of employment. In any of these events, the Contractor shall promptly notify the Contracting Officer and provide the information required by Section below. After the initial ninety (90) day period, all proposed substitutions must be submitted to the Contracting Officer and provide information required under this clause, in writing, at least ten (10) days in advance of the proposed substitutions, when possible.

• Request for Substitution – All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution, a resume for the proposed substitute, and any other information requested by the Contracting Officer. All proposed substitutes must have qualifications equal to or higher than the qualifications stated in the PWS. The Contracting Officer or his/her authorized representative will evaluate such requests and promptly notify the Contractor of his/her approval or disapproval thereof.

7.0 Personnel, Training, and Certification Requirements

The Contractor shall ensure that their personnel are eligible for and maintain required conditions of employment;

security clearance eligibility, alternate tokens, and building access passes (if required), for its employees. The Contractor shall be responsible for maintaining training, certification, and specific position requirements for employees and its sub-contractor’s employees under this contract. The Contractor shall return all applicable building access passes upon termination of employment or completion of this contract to the Security Management Office (SMO). Section and certification of receipt shall be obtained. The Contractor shall deliver a report on personnel status, monthly, in accordance with CDRL A001, Contractor’s Personnel Roster.

Contractor Personnel Appearance and Identification

The contractor’s employees shall be easily recognized as contractor employees. This may be accomplished by either

(1) the contractor employee wearing distinctive clothing bearing the company’s name/LOGO and employee’s name, or (2) the contractor employee wearing a Common Access Card (CAC) bearing the company's name and the employee's name, with the badge worn or attached to the employee's outer garment at all times. Clothing or CAC cards shall be provided by the contractor. If the contractor is unable to obtain the employee’s badge for whatever reason, the cognizant Pass and ID Office will be notified within 24 hours. During the contract performance period, contractors shall immediately report instances of lost or stolen badges to the issuing Pass and ID Office. The contractor shall establish and provide dress code and grooming standards for all contract employees. This shall take into account safety aspects of services being render, location of deployment, and consideration of the Marine Corps high standards.

Contractor personnel and their subcontractors must identify themselves as contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract. In email correspondence with the Government, it should be clear that the employee is a contractor employee (i.e., annotate in signature block). Contractor-occupied facilities (on Department of the Navy or other Government installations) such as offices, separate rooms, or cubicles must be clearly identified with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

Removal of Contractor’s Employees

The contractor agrees to utilize only experienced, responsible and capable people in the performance of work. The contractor shall not employ persons for work on this contract if such employee is identified to the contractor by the Contracting Officer as a potential threat to the health, safety, security, general well-being, or operational mission of the command and its population. The Contacting Officer may require that the contractor remove from the Government job employees who endanger persons or property, whose continued employment under this contract is inconsistent with the interest of military security, or who is determined by the Contracting Officer or Contracting Officers Representative as being incapable of rendering the services in accordance with the contract. The removal of an employee from a Department of Defense (DoD) facility shall not relieve the contractor of the requirement to continue performance of any applicable Task Order.

Reporting incidents in the workplace

The contractor shall immediately notify and inform the Government of any major accident or incident resulting in any one or more of the following: causing one or more fatalities, or two ore more disabling injuries; damaging Government property exceeding $10,000; affecting program planning or project schedules; or identifying a potential hazard requiring corrective action. Notification shall be delivered in accordance CDRL A003, Incident Report.

Cyber-security incidents where classified, or Controlled Unclassified Information (CUI), is compromised, or where the contractor’s ability to execute the contract is degraded, shall immediately Notify the COR and initiate reporting procedures in accordance with DFARS 252.204-7012.

7.1 Annual Training

DoD- and DoN-mandated information assurance training may be required under this Contract. The Contractor shall ensure all Contractor personnel complete required annual training as determined by the Government training officer.

Contractor personnel assigned to perform DON IT functions shall receive the requisite information assurance, security awareness, and functional competency training as required by their designated level of access and scope of duties

7.2 Security Training and Education

The Contractor shall provide the following training to all contract personnel:

a) Indoctrination of personnel upon employment by the DON in the basic principles of security

b) Orientation of personnel who will have access to classified information or assignment to sensitive duties (including IT duties) at the time of assignment, regarding command security requirements

c) On-the-job training in specific security requirements for the duties assigned

d) Annual refresher briefings for personnel who have access to classified information

e) Counterintelligence briefings annually for personnel who have access to information classified Secret or above

f) Special briefings as circumstances dictate

g) Debriefing upon termination of access

h) Foreign Travel Briefing prior to personnel traveling for personal or business

i) Foreign Travel Debrief upon return of traveler to provide opportunity to report any incident

7.3 Certification

Contractor personnel supporting specific cybersecurity functions, to include some technical role with elevated privileges or access to sensitive data, must have or obtain the appropriate DoD-approved cybersecurity baseline certification (available at https://public.cyber.mil/cw/cwmp/dod-approved-8570-baseline-certifications/) prior to onboarding and being assigned tasks. No waivers will be authorized. Contractor personnel are required to allow the applicable certification authority to release certification information to the DoD. All Information Assurance Technical (IAT) personnel shall complete technical training (e.g., formal, computer based training (CBT), web-based, or classroom instruction) on the operating system(s) and/or any security devices/services/tools.

The Contractor shall report the status of trained personnel, monthly, and deliver the report in accordance with CDRL A002, Cyber Security Workforce Report.

8.0 Task Order Management

JIRA is a commercial-off-the-shelf (COTS) issues management tool that the Government has tailored to manage the communications of requirements and deliverables for Task Orders under this Contract. JIRA will be used to monitor Task Order progress and completion, deliverable status, and other coordination elements, as required. The flexibility of JIRA has allowed the TSO to manage a large number of business and IT support functions.

The TSO follows both an 18-month iterative SDLC and a monthly Agile SDLC. These SDLC schedules, timelines, and processes will impact work under this contract and will be factored into each Task Orders and subsequent JIRA ticket, as much as practicable.

9.0 PRS

The Contractor shall be evaluated on established Performance Standards (PS’s) and associated Acceptable Quality Levels (AQL’s) as follows:

Service Performance Standard AQL Method of Surveillance

Incentive / Penalty

Timeliness* Tasks completed and deliverables submitted by the required date as provided in the Task Order

95% completed by required date

Inspection CPARS ratings

Accuracy

All defects in deliverables corrected prior to final acceptance.

Deliverables meet the requirements established in each Task Order

Less than 10% defects in deliverables on first submission

Inspection CPARS ratings

Responsiveness Attendance and active participation at all MR's, QSM's, and all meetings defined at the Task Order level

No less than 95% attendance COR Review CPARS ratings

*Note: Deliverables are not counted as late when, on a case by case basis, the COR approves later deliverable submission. The COR’s approval of a late deliverable submission or failure to strictly enforce delivery requirements will not be deemed a waiver of the applicable delivery requirements for future deliverables.

The Contractor must correct and resubmit rejected deliverables within three (3) business days or by the required completion date. A Quality Assurance Report shall be submitted for any rejected deliverable and delivered in accordance with CDRL A005, Quality Assurance Report.

Please note that subsequent Task Orders issued may have their own, separate PRS’s.

10.0 MCEDS Imaging, Government Furnished Information (GFI) and Government Furnished

Equipment (GFE)

10.1 MCEDS Imaging

The Government will provide a MCEDS image for installation and configuration on contractor-furnished laptops per Section 4.0.

10.2 GFI and GFE

GFI may be provided at the Task Order level, as required. The Contractor must follow TSO defined processes, procedures, and practices to safeguard and control all GFI provided. GFE may also be provided at the Task Order level, as required.

11.0 Clearance, Access, and Security Requirements

General

Contractor personnel shall be United States citizens, in accordance with DoD 5220.22-M, National Industrial Security Program, 2-207, 2-208, and 2-209. Exceptions to this requirement may be made in accordance with DoD 52220.22-M, 2-209, Guidelines for Conducting Pre-Nomination Personal Interviews. Eligibility will not be established for persons who hold a foreign passport.

Contractor personnel shall have knowledge of and comply with all standard DoD, Marine Corps, and TSO security procedures, which include those listed under Section 10.0, Applicable Directives. The Contractor shall immediately report any violation of stated regulations to the Contractor’s FSO, the Government Security Manager, and the COR.

11.1 Common Access Card (CAC) Eligibility

All Contractor personnel shall have a minimum of a National Agency Check with Inquiries (NACI) background investigation with a favorable eligibility determination to meet Homeland Security Presidential Directive (HSPD) 12 requirements in order to receive a CAC. Those Contractor personnel who are unable to obtain a favorable or higher eligibility determination will not receive a CAC. Contractor personnel not receiving a “favorable” suitability determination will have their CAC revoked. Contractor personnel ineligible or unable to receive a CAC cannot perform on this Contract

The TSO Security Management Office (SMO) will monitor status and verify successful acceptance Standard Form SF 86s (SF-86) and subsequently track that all Contractor personnel have been appropriately cleared and receive a “favorable” suitability determination.

The contractor shall regularly report the status of clearances, and CAC cards, on CDRL A001 Personnel Roster.

11.2 Information Technology (IT) Requirements

a) IT-I – access to critical sensitive information; employees assigned to Cybersecurity, Network, Database, System Administration, Application Administration, and Production Operations.

b) IT-II – access to non-critical sensitive information or Secret Clearance.

c) IT-III – for personnel who need access to the TSO facilities in Indianapolis, but do not need access to non-critical, sensitive information.

d) Access to classified materials – contractor personnel performing under the cybersecurity tasks of this contract will need access to classified material up to the Secret level in order to view, track, and input responses to cybersecurity threats.

e) No Clearance – Consultants or Professional Services brought in to consult or advise on projects not requiring access to NIPR or sensitive but unclassified information.

Documentation Submission

For access to classified information, the Contractor Facility Security Officer (FSO) will coordinate with the DSS in submitting the SF-86 ,fingerprint, and any other necessary documentation.

11.3 Security Clearances

Security requirements applicable to this contract are described in the Department of Defense Contract Security Classification Specification DD254 (Attachment L-1) which will be incorporated upon award.

At a minimum, contractors are expected to be able to obtain a successfully adjudicated T3 background investigation, and a corresponding secret level clearance. Access to critical sensitive information may be required on an individual Task Order (TO) basis, which requires a T5 background investigation. Pre-investigative (interim) access is generally granted in accordance with DoD 5220.22-M, 2-211 and DoDM 5200.02, when the following criteria are met:

• SF-86: Questionnaire for National Security Positions favorably reviewed

• Acceptable proof of citizenship

• Favorable review of local personnel, base, military police, medical, and security records, as applicable

• An appropriate national security investigation opened by the Investigative Service Provider (ISP) (e.g.

OPM) when an applicant previously held a valid security clearance and has a break in service of not more than 24 months

• Favorable review of FBI Criminal History Report (Special Access Check (SAC)) (fingerprints results)

• Has a Need-to-Know

• Completed SF-312, Non-Disclosure Agreement (NDA) prior to requesting access to the information systems.

All Contractor personnel with access to classified material shall complete and sign an SF 312, “Classified Information Nondisclosure Agreement.” All access to classified material by Contractor Personnel, including oral and visual, will be under the supervision and control of cleared Government personnel. The sponsoring Government activity will provide on-site storage capability for all classified material. Off-site storage of classified material is prohibited.

12.0 Privacy Act and HIPAA

All services performed relative to the requirements identified in this PWS allow access to unclassified or sensitive information covered by the Privacy Act of 1974 and other DoD and USMC regulations. Some information provided by the Contractor during the application process may be subject to the Health Insurance Portability and Accountability Act (HIPAA).

13.0 Travel (CLIN 0003 – COST Only)

The Contractor shall coordinate travel arrangements with the COR. Any travel under this contract must be specifically requested in writing by the Contractor and approved by the COR, prior to incurring any travel expense.

The Contractor shall submit the written request to the COR at least five (5) days in advance of the travel dates, as practicable. The travel request shall include as a minimum, the following:

• Contract number

• Date, time, and place of proposed travel

• Purpose of travel and how it relates to the contract

• Contractor’s estimated cost of travel with a breakdown of the estimated costs of transportation, lodging, meals, and incidentals; and

• Name(s) of individual(s) traveling.

The COR shall review and approve/disapprove (as appropriate) all travel requests submitted giving written email notice of such approval or disapproval to the Contractor.

Travel Reimbursement

The Contractor shall adhere to FAR 31.205-46. Travel costs will be priced separately and funded by the Government on a cost reimbursable basis at the Task Order level. No fee shall be applied. The Contractor will not be reimbursed for travel expenses unless audited records for transportation contain evidence, such as original receipts, substantiating actual expenses incurred for travel. Local travel (50 miles radius from assigned place of performance (per Task Order)) will not be covered under this contract as a travel cost transaction and the Government will not pay for commuting to/from the normal workplace (even if outside of the 50 miles radius and commuting regularly).

Travel reimbursement is limited to travel during performance of the Contract/Task Orders. Travel reimbursement does not include relocation expenses for Contractor employees prior to their start of performance on this Contract/Task Trders.

The contract includes a not-to-exceed funding limitation for travel costs. When the Contractor expects total funding expended for reimbursable travel to reach 85 percent of the total funds available on the travel CLIN, the Contractor shall notify the KO and the COR and any other Government official identified by the KO. The notice shall state the estimated amount of additional funds required to continue performance for the period specified in the contract. The Contractor shall not exceed or incur costs that exceed the amount of funding stated on the reimbursable travel CLIN.

The Government is not obligated to reimburse the Contractor for otherwise reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN.

The Contractor is not obligated to continue performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN unless the KO notifies the Contractor in writing that the funded amount stated under the applicable reimbursable travel CLIN has been increased. In the event notification is made orally, such notification shall be followed up in writing within two working days.

Change orders shall not be considered an authorization to exceed the funded amount stated under the reimbursable travel CLIN unless they contain a statement expressly increasing the funded amount of that reimbursable CLIN by a sufficient amount to cover the change order.

14.0 Non-Personal Services

Contractor employees performing services under this contract and its Task Orders will be controlled, directed, and supervised at all times by Contractor management personnel. Contractor management shall ensure all employees comply with the performance work standards outlined in this PWS. Contractor employees shall perform their duties independent of, and without the supervision of, any Government official or other Defense Contractor. The tasks, duties, and responsibilities set forth in this PWS shall not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying federal policy, obligating the appropriated funds of the United States Government, overseeing the work of federal employees, providing direct personal services to any federal employee, or otherwise violating the prohibitions set forth in Subparts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will grant Contractor access to the facilities and will perform the inspection and acceptance of the completed work.

Ordering Procedures

The following instructions were developed and will be implemented in accordance with FAR 16.505.

A) The contractor shall provide services under this contract only as directed in Task Orders issued by authorized individuals. In accordance with FAR 16.505, each order will include:

1) Date of order;

2) Contract number and order number;

3) Item number and description, quantity, and unit price. Corresponding line item number from the base contract.

4) Delivery or performance schedule;

5) Place of delivery or performance (including consignee);

6) Packaging, packing, and shipping instructions, if any;

7) Accounting and appropriation data;

8) Method of invoicing, payment and payment office, if not specified in the contract;

9) Scope of work

10) Any other pertinent information as appropriate (i.e., TO COR designation, Government Furnished

Property, material or facilities to be made available for performance of the order; security requirements;

etc.)

B) The following individuals (or activities) are authorized to place orders against this contract:

All warranted Marine Corps Installations Command (MCICOM) HQ Contracting Officers are considered designated ordering officials for this IDIQ.

C) Ordering Process:

The order procedures below are provided for informational purposes only. The actual procedures (including response times) may vary according to individual order circumstances.

(a) Single Award Contract Ordering Procedures. It is anticipated that each order will be placed in accordance with the following procedures:

(1) Requirements Documentation. Upon identification of a requirement, the cognizant technical code will develop a draft Performance Work Statement (PWS) and other requirements documents consistent with the technical requirements of this contract and the specific effort. Firm-Fixed-Price type and/or Fixed-Price Level-of-Effort type orders may be issued under this contract.

(2) Task Order Request. The Government will issue a task order request to the Contractor which will contain the finalized requirements…